Search results

happy to hear it's fixed ;)

let's try to manually connect : # iscsiadm -m discovery -t st -p 192.9.201.10 # iscsiadm -m node -l ALL

try # iscsiadm -m node session # iscsiadm -m node -l ALL the second command should connect the iSCSI

try on both machine : # pvesm list -a you should see the same things

for Windows 2008 : just use the standard Windows backup tool You backup the VM and you restore it to a server using the Windows 2008 Installation CD http://msdn.microsoft.com/en-us/library/cc770266(v=ws.10).aspx

I've had the same problem of Win2k8 + TS + Xenapp randomly crashing..with BSOD 0x0000000a I've made tests with IDE and VIRTIO disks, e1000 with fresh Intel drivers, Virtio nic, 1 or 2 cores : always the same troubles.. :( I didn't notice anything in kernel.log I had no other choice than...

great ;) thanks

So nobody has any hint or advice on AMD? Am I wrong to worry? :)

Hi, I'm going to buy 2 Dell R415 with 2x AMD Opetron 4174HE (6 cores) It would be my first time with AMD (I only have Intel servers) and I wonder if there is a risk of using AMD or if I can go with AMD for Proxmox VE with Debian and Win2k8 VM's under KVM? Thanks for your answers ;)

FYI it's working for me out owithout any modification with Chrome 7.0.503.1 dev

just put your servers in a PVE cluster : it will allow shared storage and machines migrations http://pve.proxmox.com/wiki/Proxmox_VE_Cluster

I was meaning : MY question could be stupid, not yours ;)

tried also (from pvetest on Monday) => same problem tried on a non-hyperthreaded machine also => idem win32k.sys or ntkrlnmp.exe are the cause of the cras (says windbg)

I got the same kind of troubles with a Win2k8 x64... I've tried in VIRTIO and IDE : same error 0x0000000a My storage is on iSCSI but didn't try with 1 Core only... (I should maybe open another post as far as it's on Win2k8?) neptune2:~# pveversion -v pve-manager: 1.5-10 (pve-manager/1.5/4822)...

stupid question maybe? why don't you use a Proxmox ISO or install a Debian distrib?

Re: Feature request - allow a startup delay to be specified (or dependency on another why don't you run on the bdServer at the end of the start process a ssh command to the PVE server to make it run the VM's ?

on an fr machine it sometimes happens that in vnc console mode the . key is in fact on the : key ... ;) donno why...but it happens ;)

just to be sure everything is well understood : * your PVE's are iscsi initiators. (clients that connect to an iSCSI target) * they must connect to an iSCSI target (a server providing LUN's) that's why you don't need to install iscsitarget on your PVE's some questions : * what kind of iSCSI...

hmm... I can see it seems iscsi isn't properly configured if you don't have this file... # cat /etc/iscsi/initiatorname.iscsi you should get something like : # dpkg -l | grep iscsi you should get something like

are you able to ping 10.0.0.3 ?