Re: migration of vnlink VMs

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

 



On Wed, May 11, 2011 at 03:28:30PM +0300, Dan Kenigsberg wrote:
> Sorry for hijacking the thread for something more general than vnlink:
> 
> 
> It just occured to me today that the concept of virtual network should
> be used also in the <graphics> section. Currently, if you specify
> <graphics listen="some-ip-address"> you make the domain practically
> unmigratable.
> 
> There should be a method to specify a simbolic network name, to be
> evaluated to IP on the destination host, something like
> 
> <graphics listenNetwork="some-virtual-network">

Yep, I pretty much agree, but we'll need more help from QEMU
todo that. A virtual network may have multiple IP addresses
and so we'll need to be able to specify multiple IPs to the
VNC server.

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]