Re: [libvirt] guest clock offset, configuration
On Wed, Jun 9, 2010 at 3:28 AM, Eric Blake ebl...@redhat.com wrote: On 06/07/2010 08:55 AM, Jakub Hrozek wrote: Hi, I'm having some trouble with guests booting up with huge clock offset (4 hrs). The offset is always the same which leads me to suspecting a configuration issue rather than a bug. I looked around libvirt documentation and so far checked these: * the hosts clock is correct (ntpd, manually verified) * the timezones are correct (and the same) on both host and guest * the clock element in the guest xml seems to be correct for a Linux guest - clock offset='utc'/ Is there anything else I should check? FWIW, hosts are Fedora 12, guests are a mix of recent Fedoras. Which version of libvirtd? 0.8.0 added some new clock features into the XML for better control; the documentation is not yet complete, but here's a snapshot to the work in progress: https://www.redhat.com/archives/libvir-list/2010-May/msg00393.html Eric, we're using libvirt-0.7.1-16.fc12, but I'll check the link you included. Thanks! -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
[libvirt] guest clock offset, configuration
Hi, I'm having some trouble with guests booting up with huge clock offset (4 hrs). The offset is always the same which leads me to suspecting a configuration issue rather than a bug. I looked around libvirt documentation and so far checked these: * the hosts clock is correct (ntpd, manually verified) * the timezones are correct (and the same) on both host and guest * the clock element in the guest xml seems to be correct for a Linux guest - clock offset='utc'/ Is there anything else I should check? FWIW, hosts are Fedora 12, guests are a mix of recent Fedoras. Thanks for any pointers, Jakub -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
[libvirt] virsh migrate with libvirt-0.5.1: failed to start listening VM
Hello, I was trying to migrate a KVM/QEMU VM running on a Fedora 10 host to another F10 host. Both machines have identical architectures (x86_64) and are running identical versions of libvirt and KVM (libvirt-0.5.1-2.fc10.x86_64, kvm-74-10.fc10.x86_64). However, the migration fails: # virsh migrate jhrozek-f11-minimal qemu+ssh://someothersystem.example.com/system libvir: QEMU error : operation failed: failed to start listening VM On the target host, the logfile /var/log/libvirt/qemu/jhrozek-f11-minimal.log says: qemu: could not open disk image /var/lib/libvirt/images/jhrozek-f11-minimal.img Which seems rather odd, isn't libvirt supposed to copy the image file? Is this supposed to work? Is there any way to debug the problem? I skimmed through RH Bugzilla and googled a bit but haven't found much clue. Help is appreciated, Jakub -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
