Hi, all,
We were running OpenStack with Ubuntu and libvirt 0.9.10. We found that
libvirt monitor command not working well.
There were a lot of error in libvirtd.log like this
2013-02-07 06:07:39.000+: 18112: error :
qemuDomainObjBeginJobInternal:773 : Timed out during operation: cannot
acquire
Dear all,
I have observed the virsh responds slowly with "virsh list" and used
"strace virsh list" will find that it is waiting on the socket. I also use
"netstat |grep libvirt" and see an opened socket /var/run/libvirt-sock-ro
is always on and will not disappear. Is it caused by an abnormal
termi
/2012 04:24 AM, Chun-Hung Chen wrote:
> > Dear all,
> >
> > I am planning to use live block migration with one VM running on local
> disk
> > and also attached additional disk from iSCSI or other shared storage.
> > When block migration, not only local VM disk is c
Hi Eric,
Glad to hear your reply. I would wait and check. Thanks.
Regards,
Arnose
On Wed, Jul 11, 2012 at 7:37 AM, Eric Blake wrote:
>
>
> Unfortunately, block migration during migration is an all-or-none
> prospect. And qemu 1.1 does not provide enough tools to do anything
> differently, shor
Dear all,
I am planning to use live block migration with one VM running on local disk
and also attached additional disk from iSCSI or other shared storage.
When block migration, not only local VM disk is copied to the destination
but also the attached additional disk from shared storage. It is not
Dear all,
I am planning to use live block migration with one VM running on local disk
and also attached additional disk from iSCSI or other shared storage.
When block migration, not only local VM disk is copied to the destination
but also the attached additional disk from shared storage. It is not
