race. Whatever your system has that reads block devices
(udev?) may or may not have completed by the time you disconnect
/dev/nbd0. If it wins the race and your disconnect is slow enough,
you get no messages.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
he kernel module?
Can you add a --trace parameter to qemu-nbd to cause it to log more
details about what is going on?
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
a sample command
line.
> >>
> >> access to the E: drive is extremely slow and the system events report
> >> many storahci (129: reinit \device\RaidPort0 sent) and disk (153: I/O
> >> @0x3f on disk 1 \device\0001f replayed) warnings.
> >>
> >> regards.
> >>
> >
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
to consider having a tar filter, either in place of or in addition
to, the tar plugin (similar to how we recently converted nbdkit's ext4
support from a plugin to a filter) - having a tar filter would allow you
to read a compressed ova file (by combining the xz and tar filters to
decompress then extract a
r, the 4.0 commands
block-dirty-bitmap-{enable,merge,disable} (or their 3.1 counterparts
x-block-dirty-bitmap-*) are essential to the workflow of differential
backups (without being able to manage bitmaps yourself, you can only get
the weaker incremental backup, and that means qemu itself is clearing
the
isk over NBD rather than qemu pushing
them); I even have a working demo of preliminary libvirt code driving
that which I presented at last year's KVM Forum.
> Workaround: Couldnot achieve this. So if an incremental fails after block
> jobs succeed before i can ensure success(have to do some
guest-visible data is consistent. BDRV_O_NO_IO is our promise that we
are reading only metadata, not guest-visible data. So that change makes
sense.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
signature.asc
Description: OpenPGP digital signature
nted and supported (so we DO have a
safe fallback, regardless of when 'qemu-img create -u ... size' actually
lands).
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
signature.asc
Description: OpenPGP digital signature
ause it makes more sense to implement the
working feature than to document the workaround to a missing feature.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
signature.asc
Description: OpenPGP digital signature
th ways. Maybe:
qemu-img query-max-size -O qcow2 --size 20G
qemu-img query-max-size -O qcow2 -f raw input.raw
--
Eric Blake eblake redhat com+1-919-301-3266
Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
mu-i386 version 2.4.90, Copyright (c) 2003-2008 Fabrice Bellard
>
> with the referenced commit reverted apt-get and maple work fine.
I don't see how that commit would expose any core dumps - it was just
deleting unused code. Showing more details about the crash would help
diagnose what's g
qemu returning a status with 0 progress
but equal to the block job size, and libvirt interpreting it as job
complete with a result of failing the command; splitting the job into
distinct parts was indeed the right workaround as it prevented hitting
the window. See libvirt commit eae5924
--
Eric
reply; instead, to learn if the command was successful, you
must listen to the ordinary QMP monitor for an event notification
corresponding to the change in guest state.
Libvirt already handles this interaction correctly.
--
Eric Blake eblake redhat com+1-919-301-3266
Libvirt virtualization
of the
migration), then doing the live migration, then tearing down the NBD
mirroring link.
--
Eric Blake eblake redhat com+1-919-301-3266
Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
the guest.
What steps do i have to follow for windows ?
The same steps - qemu-guest-agent is available for both Linux and
Windows guests.
--
Eric Blake eblake redhat com+1-919-301-3266
Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
. It would be simpler to have
a CentOS SIG build this, but it hasn't happened yet.
--
Eric Blake eblake redhat com+1-919-301-3266
Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
CentOS, I'd look into finding the qemu-kvm-rhev package
(the default qemu-kvm package is intentionally shipped with fewer
supported features, and you have run into one of those features).
--
Eric Blake eblake redhat com+1-919-301-3266
Libvirt virtualization library http://libvirt.org
-built binary.
--
Eric Blake eblake redhat com+1-919-301-3266
Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
. There is no guest_ping command, only
guest-ping. It's a bug in libvirt that guest-agent-command doesn't
output a useful error message when attempting to run a non-existing
command, but you'll never hit that bug if you pass valid commands to the
agent in the first place.
--
Eric Blake eblake redhat com+1-919-301
19 matches
Mail list logo
