On 07/09/2009 01:43 AM, Chris Lalancette wrote:
Yeah, that's just not going to work. In theory it might work, but it's never been tested, so I'm not surprised it doesn't. In general migration is extremely finicky when it comes to CPU versions, and versions of the software.
If you are interested in debugging it more, I would suggest stopping libvirtd on both sides, starting them back up by hand with:
LIBVIRT_DEBUG=1 /usr/sbin/libvirtd --verbose --listen
And then re-running your test. That will dump lots of debugging information on both machines, and you might be able to get somewhat of a better idea of what is happening.
Host 1: [root@vm1 ~]# rpm -q libvirt libvirt-0.6.2-12.fc11.x86_64 [root@vm1 ~]# uname -r 2.6.29.5-191.fc11.x86_64 Host 2: [root@vm2 ~]# rpm -q libvirt libvirt-0.6.2-12.fc11.x86_64 [root@vm2 ~]# uname -r 2.6.29.5-191.fc11.x86_64 Host 2 doesn't want to start with --verbose: 08:16:44.859: debug : virEventInterruptLocked:635 : Skip interrupt, 0 0 08:16:44.859: debug : virEventAddHandleImpl:111 : Add handle 11 13 0x412c70 0x13368a0 08:16:44.859: debug : virEventInterruptLocked:635 : Skip interrupt, 0 0 08:16:44.868: error : Cannot access CA certificate '/etc/pki/CA/cacert.pem': No such file or directory What's weird is, if I start the service it works fine. It only errors about that cacert if I do it raw. I can't find any reference to cacert in my config. Help! -- Scott Baker - Canby Telcom System Administrator - RHCE - 503.266.8253