Thanks for the response. I did see that much :) Correct me
if I'm wrong; but, it appears that xm create pulls the configuration
and formats it (among other things) and passes the configuration to
qemu-dm or in this case stubdom-dm. It also seems that qemu-dm expects
'tls' as an argument and not 'tls=whatever'. The 'tls' argument was
being auto generated in '/etc/xen/stubdom' (I think by the updated
stubdom-dm script) and not something I had manually appended to the
configuration of the VM; and occurs when (vnc-tls 1) is uncommented.
I was able to patch image.py and create.py to pass the
information to stubdom-dm. Which leaves me with:
INFO (image:394) spawning device models:
/usr/lib64/xen/bin/stubdom-dm ['/usr/lib64/xen/bin/stubdom-dm', '-d',
'23', '-domain-name', 'windowsxp', '-videoram', '4', '-vnc', '
127.0.0.1:1,tls,x509=/etc/xen/vnc',
'-vcpus', '1', '-boot', 'd', '-acpi', '-usbdevice', 'tablet', '-net',
'nic,vlan=1,macaddr=00:16:3e:0a:12:15,model=rtl8139', '-net',
'tap,vlan=1,ifname=tap23.0,bridge=xenbr0', '-M', 'xenfv']
Home