Guillaume Rousse
2009-Dec-11 17:12 UTC
[Xen-devel] vncunused=0 option prevent additional hvm hosts to run
Hello list. I''m trying to achieve an easy mapping between my HVM guests and their corresponding VNC display number. Using automatic affectation, through usage of vncunused option set to 1, relies on launch order, which isn''t practical when you have a large guests number. The doc seems to says than setting vncunused=0 will revert to static affectation, as defined by vncdisplay option, whose default value is supposed to be dom ID number. But when trying this option, the first guest uses display number 0, and all the following one refuse to start, probably because the port is already allocated. And the resulting message is quite misleading: [root@sequoia xen]# xm create mdv20090-i86 Using config file "./mdv20090-i86". Error: name ''domid'' is not defined [2009-12-11 18:03:10 5421] INFO (image:394) spawning device models: /usr/lib64/xen/bin/qemu-dm [''/usr/lib64/xen/bin/qemu-dm'', ''-d'', ''50'', ''-domain-name'', ''mdv20090-i86'', ''-videoram'', ''4'', ''-k'', ''fr'', ''-vnc'', ''127.0.0.1:0'', ''-vcpus'', ''1'', ''-boot'', ''cn'', ''-serial'', ''pty'', ''-acpi'', ''-net'', ''nic,vlan=1,macaddr=00:16:3e:00:00:46,model=e1000'', ''-net'', ''tap,vlan=1,ifname=tap50.0,bridge=services'', ''-M'', ''xenfv''] [..] [2009-12-11 18:03:10 5421] WARNING (image:493) domain mdv20090-i86: device model failure: pid 16680: exited with nonzero status 1; see /var/log/xen/qemu-dm-mdv20090-i86.log It seems actually vndisplay default to 0, and there is no way to manually set it to a dynamic value (vndisplay=domid doesn''t work). I''m using xen 3.4.2 on mandriva linux. -- BOFH excuse #228: That function is not currently supported, but Bill Gates assures us it will be featured in the next upgrade. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel