Re: [RFC PATCH 07/12] qemu: migration: Forbid migration with memory modules lacking info

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Jan 30, 2015 at 02:21:04PM +0100, Peter Krempa wrote:
> Make sure that libvirt has all vital information needed to reliably
> represent configuration of guest's memory devices in case of a
> migration.
> 
> This patch forbids migration in case the required slot number and module
> base address are not present (failed to be loaded from qemu via
> monitor).

What would cause us to fail to load them from QEMU ? Is there a way we
can assign the address upfront like we do for other device types, so we
can avoid the need to query QEMU & thus avoid failure scenario too ?

Regards,
Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|

--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list




[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]