On Wed, May 11, 2011 at 01:37:25PM +0100, Daniel P. Berrange wrote: > 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. That would be nice, but I think that a semantics where libvirt is in charge of telling which qemu process is to listen on which of the network IP addresses is as reasonable (and may potentially better, as libvirt has more knowledge of the host) Anyway, if the virtual network is bridge-based, I could live with passing the single IP of the bridge for qemus that do not support this feature. Regards, Dan. -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list