Search results

Spirit, One of the errors comes from different library. Can you help to debug that? QemuServer.pm: die "unable to find configuration file for VM $vmid - no such machine\n"

No, sleep 1 second is not a solution at least not reliable work around. 1. I copied all the files to nodes 3 and 4, then restarted pvedaemons but tasks with logged sleep have not shown up until I rebooted the nodes 3 and 4. 2. Error still remains when I migrate from 3 to 4 and back task...

Spirit, I really appreciate your help. Since it works for you and per this thread I am not the only one with the issue, can you post your cluster configuration ? Also I am interested in firewall settings which perhaps can affect multicast communications. Thanks again, Sent from my...

File is / was getting there all the time because I can / could resume every time on the proper target machine. I rebooted one of the boxes and kept sleep 1 on both nodes. Now I tried reproducing the problem and I cannot, not within two nodes I experimenting with. Does it mean that pvdaemon...

Added logging, here is the task log task started by HA resource agent Oct 13 07:24:03 starting migration of VM 101 to node 'virt2n2-la' (38.102.250.229) Oct 13 07:24:03 copying disk images Oct 13 07:24:03 starting VM 101 on remote node 'virt2n2-la' Oct 13 07:24:05 starting ssh migration tunnel...

added sleep and restarted pvedaemon. Change had no effect. Still can reproduce it .

Sorry for the late reply. Other then DRBD9 developers have no time to produce an updated document for their own code and their priority is to complete project for paying customer (not DRBD9 related) nothing.

Here you go cat 101.conf bootdisk: virtio0 cores: 2 hotplug: disk,network ide2: none,media=cdrom localtime: 1 memory: 2048 name: monitor1n1-la.siptalk.com net0: virtio=AE:5E:BD:28:73:51,bridge=vmbr0,firewall=1,queues=4 net1: virtio=CE:A2:78:60:F3:C5,bridge=vmbr1,firewall=1 numa: 1 ostype: l26...

Is anything available from git I could install today / tomorrow? I hate to push but this thing is a show stopper for me. Sent from my SM-G900V using Tapatalk

Thank you, let me know if you need any help.

Thom, Dietmar, do you have any feedback on this. If this is not fixed any time soon perhaps I need to migrate back to 3.4 which would be a huge waste of time for me as I have invested some time into getting cluster to this stage. Please let me know if you need to test a fix, I would be happy...

It looks like this message is related to vm 101 no longer present on the source node. Could it be that during the migration with ha when machine is no longer on the source your system thinks it is not there at all and throws an exception? Error: unable to find configuration file for VM 101...

BTW, Regardless of how I do migration, via qm, ha-manager, or web, I notice web interface for a short duration pops an error 500, machine 101 doesn't exist. Message then disappears Not sure if it has any correlation to a problem or is part of normal process.

Yes I did. Sent from my SM-G900V using Tapatalk

The post I am referring to is PVE 4 KVM Live migration problem. Sent from my SM-G900V using Tapatalk

Sorry but I am not good. I am having trouble with live migration under ha period. The reason you see 101 now is because I cloned it (complete copy) from 100. Vm 100 is gone. The only one vm there is 101 and it is in ha mode. This problem shown here is in addition to my earlier post...

It is hard to say what happen but as of now: ha-manager status quorum OK master virt2n1-la (active, Sat Oct 10 17:26:49 2015) lrm virt2n1-la (active, Sat Oct 10 17:26:47 2015) lrm virt2n2-la (active, Sat Oct 10 17:26:50 2015) lrm virt2n3-la (active, Sat Oct 10 17:26:46 2015) lrm virt2n4-la...

About to give up for now but it feels like there is a certain timer in HA mode tells qemu to not resume. I run multiple migrations in HA mode and some times from faster to slower node (hardware CPU wise) I had a successful migration. Logs that I watch (syslog) shows no difference between good...

I ran few more tests and it actually comes to HA being a root of the problem. Here is what I did. I cloned vm 100 to vm 101. I removed vm 100 from HA group, deleted resource and then deleted 100 completely I started vm 101. I did 5 -6 successful migrations. CPU kvm64, no HA at this point...

On the target machine I see in case of error in syslog. Would this be a systemd issue? Oct 10 12:30:24 virt2n2-la pmxcfs[1580]: [status] notice: received log Oct 10 12:30:25 virt2n2-la qm[11675]: <root@pam> starting task UPID:virt2n2-la:00002DA4:000516CC:56196751:qmstart:100:root@pam: Oct 10...