similar to: [PATCH libguestfs v3] lib: Handle slow USB devices more gracefully.

On Tue, Jan 19, 2016 at 05:00:27PM +0000, Daniel P. Berrange wrote: > On Tue, Jan 19, 2016 at 04:18:46PM +0000, Richard W.M. Jones wrote: > > Libvirt has a fixed 15 second timeout for qemu to exit. If qemu is > > writing to a slow USB key, it can hang (in D state) for much longer > > than this - many minutes usually. > > > > The solution is to check specifically

On Tue, Jan 19, 2016 at 04:18:46PM +0000, Richard W.M. Jones wrote: > Libvirt has a fixed 15 second timeout for qemu to exit. If qemu is > writing to a slow USB key, it can hang (in D state) for much longer > than this - many minutes usually. > > The solution is to check specifically for the libvirt EBUSY error when > this happens, and retry the virDomainDestroyFlags operation

Hi, we experienced a strange, non-reproducible error after a successful migration to another host. When we called virDomainDestroyFlags with VIR_DOMAIN_DESTROY_GRACEFUL flag after the migration on the source host, we got VIR_ERR_OPERATION_INVALID (code 55) error. The same with repeated virDomainDestroyFlags calls. Normally, we would expect either success or VIR_ERR_NO_DOMAIN error. `virsh

"Daniel P. Berrange" <berrange@redhat.com> writes: > On Fri, Mar 17, 2017 at 11:55:13AM +0100, Milan Zamazal wrote: >> Hi, we experienced a strange, non-reproducible error after a successful >> migration to another host. When we called virDomainDestroyFlags with >> VIR_DOMAIN_DESTROY_GRACEFUL flag after the migration on the source host, >> we got

Since v1: - Base64 decode the Ceph secret before passing it to libvirt. - Don't call virSecretFree (NULL) [libvirt bug?] - Small cleanups.

Hi, I have started one node through libvirt API using its start method. I am trying to stop that node using the *destroy *method provided by the API but I am not able to do so. Instead, I am getting one message saying: *libvir: error: internal error Child process (vmrun -T player stop /root/test_folder/myImage.vmx soft) unexpected exit status 255* Can anybody tell me why I am not able to stop

Implement the GUESTFS_ADD_DRIVE_OPTS_SECRET argument of guestfs_add_drive_opts. For libvirt we have to save the secret in libvirtd first, get a UUID, and then pass the UUID back through the domain XML. --- src/launch-libvirt.c | 227 ++++++++++++++++++++++++++++++++++++++++++++++++++- 1 file changed, 224 insertions(+), 3 deletions(-) diff --git a/src/launch-libvirt.c b/src/launch-libvirt.c

In case you configure libguestfs with a custom QEMU, e.g.: $ ./configure [...] QEMU=/path/to/qemu then the libvirt backend did not use to override it, launching the appliance with the default QEMU for libvirt. This does not change the manual emulator overriding using set-hv. Pino Toscano (2): launch: libvirt: get default QEMU from domcapabilities launch: libvirt: fix custom hypervisor

When stop a qemu vm via libvirt api, I call virDomainShutdown, I can seen the vm shutdown process, But I call virDomainDestroyFlags with VIR_DOMAIN_DESTROY_GRACEFULL ,I can't seen the vm shutdown process, virDomainDestroyFlags with VIR_DOMAIN_DESTROY_GRACEFULL is gave vm driver process a SIGTERM , how vm driver process SIGTERM signal (like qemu). Thanks

This preliminary patch series adds a libvirt backend to libguestfs. It's for review only because although it launches the guest OK, there are some missing features that need to be implemented. The meat of the patch is in part 4/4. To save you the trouble of interpreting libxml2 fragments, an example of the generated XML and the corresponding qemu command line are attached below. Note the

On Fri, Mar 17, 2017 at 11:55:13AM +0100, Milan Zamazal wrote: > Hi, we experienced a strange, non-reproducible error after a successful > migration to another host. When we called virDomainDestroyFlags with > VIR_DOMAIN_DESTROY_GRACEFUL flag after the migration on the source host, > we got VIR_ERR_OPERATION_INVALID (code 55) error. The same with > repeated virDomainDestroyFlags

On Fri, Mar 17, 2017 at 02:07:11PM +0100, Milan Zamazal wrote: > "Daniel P. Berrange" <berrange@redhat.com> writes: > > > On Fri, Mar 17, 2017 at 11:55:13AM +0100, Milan Zamazal wrote: > >> Hi, we experienced a strange, non-reproducible error after a successful > >> migration to another host. When we called virDomainDestroyFlags with > >>

Possibly for post 1.40. Rich.

Let's actually compile and test the patch this time, rather than trusting the RHEL 7.6 patch to apply directly to head ... Rich.

v3: - Various changes to dhclient/dhcpcd as discussed on the mailing list.

Hi, Sometimes when stopping a virtual domain using virDomainDestroy(), I come across a domain that is already stopped. (For example when someone already stopped the domain manually using virsh or because the guest OS issued a shutdown.) This is a special case that I absolutely need to catch and handle. Unfortunately, when this happens, and I call virGetLastError() afterwards, I always just

Unlink the sockets in the shutdown callback, instead of right before creating a new ones. This makes sure we are unlinking the right sockets. --- src/launch-libvirt.c | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/src/launch-libvirt.c b/src/launch-libvirt.c index 185b44b..8a5d93e 100644 --- a/src/launch-libvirt.c +++ b/src/launch-libvirt.c @@ -397,7 +397,6 @@

This rounds off hotplugging support by allowing you to add and remove drives at any stage (before and after launch). Rich.

libguestfs usually needs qemu. However it only requires an emulator for the same architecture, not for all architectures. libvirt-daemon-kvm pulls in qemu which pulls in emulators for all architectures, as well as a bunch of other stuff we don't need at all like network interface support and nwfilter. There are no Fedora TCG-only arches, so drop the conditional section. I also made support

v2: - Make virbr0 configurable. - Fix the tests.