Search results

I have found a problem on our IMS system. Fencing will not work. When I will try to fence node timo: fence_node timo -vv I will get: fence timo dev 0.0 agent fence_intelmodular result: error from agentagent args: port=3 nodename=timo agent=fence_intelmodular ipaddr=xxx.xxx.xxx.xxx...

Why I don't know. It just doesn't. I have tryed it on multiple machines, without any luck

Ok found the fix: nano /etc/default/grub and activate 640x480 by editing this: GRUB_CMDLINE_LINUX_DEFAULT="quiet" to: GRUB_CMDLINE_LINUX_DEFAULT="quiet video=VGA-1:640x480" after this, run. update-grub Maybe interresting to add it to the code (or in a wiki)? text mode is more for...

after the /dev line the resolution will go up. It is very annoing, because in the datacenter there are some old lcd, that don't go that high. I have tried toms howto, but it still will scale the resolution up after the loading of /dev (I think...) I have tried to set the GFX...

I will test tonight!

Yes this works! Finally live migrations will work! And for the technical background. What do we change exactly, and why does that work? I have searched on the internet but the only thing I can find is: So we change the 1 to 0.1 seconds. But why does the transfer stall when the maximum...

That is exactly the same as our problem. The only difference that it is with Linux 2.6/3.0 as we don't have any windows VM's

Re: AW: Updates for Proxmox VE 2.2 - including QEMU 1.3 http://forum.proxmox.com/threads/12239-Live-migartion-fails-in-KVM-1-3 Can you look at this threat, and if it similar post there.

If I transfer from Rembo to Timo Timo -> Rembo the transfer fails. syslog sint Syslog Rembo: Dec 20 20:19:58 rembo pvestatd[2907]: WARNING: unable to connect to VM 305 socket - timeout after 31 retriesDec 20 20:19:58 rembo pvedaemon[2701]: WARNING: unable to connect to VM 305 socket -...

Dec 20 17:38:37 timo pvedaemon[2067]: worker 62327 finishedDec 20 17:38:37 timo pvedaemon[2067]: starting 1 worker(s) Dec 20 17:38:37 timo pvedaemon[2067]: worker 65033 started Dec 20 17:38:49 timo pvedaemon[64588]: WARNING: unable to connect to VM 108 socket - timeout after 31 retries Dec 20...

I can look if I can schrink the image so you can download it, because I think that is the only solution so you can see it.

Ok but I can reproduce it, I have told you the steps.

Ok what is then the best method?

Ok with the latest version on both nodes of QEMU(pve-qemu-kvm: 1.3-10), the test VM will also stall during migration.

It is a gigabit network inside the IMS. The iperf without transfer: ------------------------------------------------------------Client connecting to 10.221.184.62, TCP port 5001 TCP window size: 23.8 KByte (default) ------------------------------------------------------------ [ 3] local...

Ok, I can send you the VM image. But here is the step by step: 1. Disable HA for VM 2. Offline migration VM from QEMU 1.2 to QEMU 1.3 3. Start of VM 4. When VM is running Live migrate from qemu1.3 old host to qemu1.3 new host 5. STATUS: Dec 20 08:59:36 starting migration of VM 200 to node 'timo'...

Dec 20 09:00:53 migration status: active (transferred 3506597511, remaining 1577824256), total 8598913024) No same problem. Looks like it can't handle a large load/large RAM. If I copy the VM with no load and therefore almost no RAM allocated it transfered without a problem.

What is the correct method to roll back to QEMU 1.2??

Some VM will Live migrate, but if there under load or have a large sum of allocated RAM it will fail...

Re: AW: Updates for Proxmox VE 2.2 - including QEMU 1.3 I have opened a new thread so I don't hijack this thread. The VMID.conf and quest os is at: http://forum.proxmox.com/threads/12239-Live-migartion-fails-in-KVM-1-3?p=66472