> I'm running snv93. > > I'm trying to install a windows hvm domU using the > virt-install command: > > /usr/bin/virt-install -n windowsts -r 2048 -s 20 -f > /data/domU/windowsts --hvm --vnc -c > /dev/dsk/c0t0d0s2 \ -d
Check output. > > The vncviewer is unable to open a connection to the > xend VNC server and is failing with the Connection > refused (146) error message. > > xend is set up with the following properties: > > config/vnc-listen=astring:"0.0.0.0" > config/vncpasswd=astring:"newroot" > config/default-nic=astring:"" SNV Dom0 requires GLDv3 NIC. I guess default-nic should be defined as xend service property :- bash-3.2# dladm show-dev LINK STATE SPEED DUPLEX aaaaa up 100Mb full svccfg -s xvm/xend setprop config/default-nic="aaaaa" svcadm refresh xvm/xend svcadm restart xvm/xend or try via virt-manager and see would it provide NIC for you automatically > > The problem seems to be that the VNC server is > starting at a later time than that at which the VNC > viewer is attempting to connect to it. After the > virt-install command fails, I run netstat -an|grep > 590 and find that there really is a VNC server > listening on tcp/5900. I can even run vncviewer from > the CLI and authenticate using the newroot password. > > I've tried all the options I can think of and > searched fora for help on this but haven't been > successful so far. Any pointers would be greatly > appreciated. > > Cheers -- This message posted from opensolaris.org _______________________________________________ xen-discuss mailing list [email protected]
