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 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:"" 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
> 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
Etienne V. Depasquale
2008-Oct-26 19:23 UTC
Re: vncviewer reporting connection refused (146)
I''m attaching the output of the virt-install command with the -d option. This machine is an X4140 so GLDv3 NIC prereq is satisfied. I had tried setting the default-nic option to nge0 (then refreshed, restarted xvm/xend) but to no avail. I think I don''t have VNC properly configured....will look into this. -- This message posted from opensolaris.org
Try :- virt-install . . . . . -c /export/home/isos/winxp.iso -d -- This message posted from opensolaris.org
Tested just now on SNV 98 :- bash-3.2# virt-install -n windows -r 2048 --hvm --vnc -f /export/home/images/win.img -s 5 \> -c /dev/dsk/c0t0d0s2 -dMon, 27 Oct 2008 06:55:23 DEBUG Disk path not found: Assuming file disk type. Mon, 27 Oct 2008 06:55:23 DEBUG DistroInstaller location is a local file/path: /dev/dsk/c0t0d0s2 Mon, 27 Oct 2008 06:55:23 DEBUG Path is block file: Assuming Block disk type. Starting install... Mon, 27 Oct 2008 06:55:23 DEBUG Path is block file: Assuming Block disk type. Creating storage file... 100% |=========================| 5.0 GB 00:00 Mon, 27 Oct 2008 06:55:23 DEBUG Creating guest from ''<domain type=''xen''> . . . . . . Brought up VNC window and started install with no problems -- This message posted from opensolaris.org
> 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.Sun Oct 26 20:18:57 2008 main: unable to connect to host: Connection refused (146) Sun, 26 Oct 2008 20:19:02 DEBUG Restarted guest, looking to see if it is running Sun, 26 Oct 2008 20:19:02 DEBUG Launching console callback ***************************************** Virt-install wants 5901 per debug report ***************************************** Sun, 26 Oct 2008 20:19:02 DEBUG VNC Port: 5901; VNC host: localhost VNC Viewer Free Edition 4.1.2 for X - built Jun 20 2008 17:50:40 Copyright (C) 2002-2005 RealVNC Ltd. See http://www.realvnc.com for information on VNC. Sun Oct 26 20:19:03 2008 main: unable to connect to host: Connection refused (146) -- This message posted from opensolaris.org
Would also try install via hvm profile. If domain gets loaded, then i can run :- # vncviewer localhost:0(1) and see where it seets. -- This message posted from opensolaris.org
Etienne V. Depasquale
2008-Oct-27 21:11 UTC
Re: vncviewer reporting connection refused (146)
Thank-you for the help. I didn''t want to use the iso image as the source of the installation as it''s unwieldy. As regards port 5901, that probably arose because port 5900 was in use by a previous run of virt-install. These installations were dying because I had omitted the --os-type=windows option, leading the HVM to be created without the APIC device. I eventually gave up trying to persuade the vnc server embedded in xend to respond to the vnc viewer called by virt-install. Instead, I used vncviewer 127.0.0.1, as you indicated in your last post and was able to continue with the Windows HVM installation. Cheers -- This message posted from opensolaris.org
please, run # svcs -a |grep xvm to make sure all xvm services are online. --- On Mon, 10/27/08, Etienne V. Depasquale <edepa@ieee.org> wrote: From: Etienne V. Depasquale <edepa@ieee.org> Subject: Re: [xen-discuss] vncviewer reporting connection refused (146) To: xen-discuss@opensolaris.org Date: Monday, October 27, 2008, 5:11 PM Thank-you for the help. I didn''t want to use the iso image as the source of the installation as it''s unwieldy. As regards port 5901, that probably arose because port 5900 was in use by a previous run of virt-install. These installations were dying because I had omitted the --os-type=windows option, leading the HVM to be created without the APIC device. I eventually gave up trying to persuade the vnc server embedded in xend to respond to the vnc viewer called by virt-install. Instead, I used vncviewer 127.0.0.1, as you indicated in your last post and was able to continue with the Windows HVM installation. Cheers -- This message posted from opensolaris.org _______________________________________________ xen-discuss mailing list xen-discuss@opensolaris.org