https://bugzilla.novell.com/show_bug.cgi?id=352320 Summary: Handling of the 'vncdisplay' parameter is broken for fully virtualized VMs Product: openSUSE 10.3 Version: Final Platform: PC OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Xen AssignedTo: cgriffin@novell.com ReportedBy: nice@titanic.nyme.hu QAContact: qa@suse.de Found By: Other As I wrote in https://bugzilla.novell.com/show_bug.cgi?id=349999 the 'vncdisplay' option is quite undocumented. Since then I also realized that it's also broken in case of fully virtualized (qemu-dm assisted) VMs. If I create a fully virtualized VM by a command (e.g. xm new windowsvista), that VM will correctly use the its assigned VNC port (defined by the vncdisplay option) only until restarting xend (e.g. by restarting the computer entirely)! After restarting xend, fully virtualized domains start to behave somewhat similar to a VM having 'vncunused=1' set. I have to delete and recreate the vm in order to make it use the proper tcp port for vnc connections. Beside deleting and recreating the VM there is another workaround: Making the ports 5900 and 5901 engaged some way will also help sometimes. Xend may be broken someway. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.