Search results

I had to kill vztar because it hung. vzdump said "everything" is OK at the end of backup operation. Aug 24 02:00:08 INFO: Starting Backup of VM 101 (qemu) Aug 24 02:00:09 INFO: running Aug 24 02:00:09 INFO: status = running Aug 24 02:00:10 INFO: backup mode: snapshot Aug 24 02:00:10 INFO...

In short: 1) policy (allow shutdown without login) 2) screen saver bug http://forum.proxmox.com/threads/2341-KVM-(Windows)-Backup-in-stop-mode

Just install acpid

Was it ubuntu server or desktop?

It looks like sata-compatible mode is enabled in bios.

Follow the link: http://forum.proxmox.com/threads/2341-KVM-(Windows)-Backup-in-stop-mode

More information is here: http://support.microsoft.com/kb/910617 Problem was fixed in SP3 for Windows XP and SP2 for Windows 2003.

Roberto, it seems similar to this one: http://forum.proxmox.com/threads/3530-Problems-with-Windows-live-migration-using-KVM

Yes, as I see. There is a problem with kvm and kernel 2.6.24. It works with kernel 2.6.18, but there is another problem with it - machine is freezing during migration and unfreezing after migration end.

Hello fluke, hello everybody, Today I have an experiment with a real system and I got that I was exatly right. Here is my steps to reproduce. 1. Virtual Windows XP is working on virt1 2. I stop virt2. 3. Create directory test1 and file test1.txt on the "Virtual Windows XP". 4. Stop virt1. 5...

proxmox-ve-2.6.24 - doesn't help proxmox-ve-2.6.18 - helps (windows machine doesn't hang now) but live migration hang machine during migration (in my case is about 17 seconds) and release after migration done.

Ok, thank you. I'll try to install proxmox-ve-2.6.24 and tell you back about results.

Second strange thing is that proxmox-ve (any version) insn't installed by default. Is it normal? # dpkg -l | grep proxmox-ve ... nothing to show

That's strange because I installed server virt2 from lastest (version 1.5) LiveCD and did "aptitude full-upgrade" after that. By default it use kernel 2.6.24. Should I use 2.6.32? As I know it doesn't provide OpenVZ. # dpkg -l | grep pve ii libpve-storage-perl 1.0-10...

Hi Tom, I never installed any new kernel. I always just use "aptitude full-upgrade". Did I wrong way?

Hello everybody, We have two servers virt1 and virt2. 1 Windows XP works correctly on both. 2. Live migration Windows XP from virt2 to virt1 always goes well. 3. Live migration Windows XP from virt1 to virt2 usualy hang or reboot machine. It seems as memory corruption. BSOD message: STOP...

I'm not really sure bu I think it works in the folowing way at the moment: 1. Both server shutted down. 2. I start one of them. In accroding to "wfc-timeout 15;" and "become-primary-on both;" after 15 seconds this server become MASTER. 3. I start another one and in according to "after-sb-1pri...

Because when I stop server it works in this way: 1. umount devices if mounted 2. stop drbd 3. stop network That's not true. I've tried to do device in use and then I successfuly stopped drbd sevice on the other server.

I think it's wrong way cause it's different of shutdown process. I think the right way is (more similar to shutdown): 1. Stop drbd on virt1. 2. Disconnect network on virt1. 3. Do modifications on virt2. 4. Stop drbd on virt2. 5. Disconnect network on drbd2. 6. Start network on virt1. 7. Start...

I did modifications to the drbd device on the server which have drbd running. Why do you think stoping drbd service and stoping server have a difference? Do you mean that the proxmox service do somthing to the drbd while it's in shutting down? I don't think so.