WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Problem with WinXP install. Can start but not connect vi

To: Benny Pfitzner <pfitzner-lug@xxxxxxx>
Subject: Re: [Xen-users] Problem with WinXP install. Can start but not connect via vnc
From: Ryan Worsley <R.C.Worsley@xxxxxxxxxxxx>
Date: Wed, 20 Dec 2006 19:15:16 +0000
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 20 Dec 2006 11:15:22 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1166634888.12820.11.camel@xxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <1166624485.30094.7.camel@xxxxxxxxxxxxxxxxxxxxx> <45895EF9.6040202@xxxxxxxxxxxx> <1166634888.12820.11.camel@xxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.5.0.8 (Windows/20061025)
Benny Pfitzner wrote:
Am Mittwoch, den 20.12.2006, 16:04 +0000 schrieb Ryan Worsley:
Hi Benny,

Benny Pfitzner wrote:
Hi,

I run debian etch with xen packages provided by debian. They are running
fine.
Today I tryed to install Windows XP. Here is my config:
***********************************************
kernel = "/usr/lib/xen-3.0.3-1/boot/hvmloader"
builder = 'hvm'
memory = 512
name = "winxp"
vcpus = 1
vif = [ 'type=ioemu, bridge=xenbr0' ]
disk = [ 'file://vserver/images/domains/winxp/winxp.img,ioemu:hda,w' ]
device_model = '/usr/lib/xen/bin/qemu-dm'
#cdrom='/dev/hda'
cdrom='/vserver/images/domains/winxp/winxp.iso'
The cdrom= lines had no effect for me, I think they're obsolete now or something, instead I have a disk line that looks like this;

disk = [ 'phy:/dev/sys_vg/windows_os,ioemu:hda,w', 'file:/vserver/images/domains/winxp/winxp.iso,hdc:cdrom,r' ]

Thank you very much Ryan,

you are totally right. They changed it in version 3.0.3.

I added vncviewer=1 and sdl=1 to my configfile and started the domain
again.

You're welcome man. I think it's intended that you use EITHER the vnc viewer OR the SDL viewer and not both simultaneously. Maybe someone can clear up the technicality of this?
Then I automatically I got vncviewer running my WinXP install screen.
After formatting the image and so on Windows want's to reboot.

Since then I don't have connection to the domain.
Is it the VNC viewer you've got or an SDL viewer, the top of the window should give it away. You say it reboots but you have no connection to the domain, this may be something to do with having both vnc and sdl on at the same time. In my experience with SDL, you get a new window pop up after the reboot. Not so sure with VNC though.
I posted my netstat -l output here because I just can't find the port:
http://pastebin.ca/raw/286397

The only line pertaining to VNC looks like this one;

tcp        0      0 localhost.localdom:5900 *:*                     LISTEN



But that said, this is more than likely just the vncserver you have running on Dom0. So it looks to me that perhaps having both vnc and sdl enabled might be causing problems!
My logs don't show anything regarding vnc.
Here is the output of the most recent qemu-log:
*************************************************
domid: 7
qemu: the number of cpus is 1
shared page at pfn:1ffff, mfn: 1d24b
buffered io page at pfn:1fffd, mfn: 1d24d
*************************************************

Here I posted the last couple of lines from the xend.log file.
http://pastebin.ca/286403
This all looks fine to me.

Thanks,

Ryan.

Thanks Ben

ne2000=0
boot='d'
vif  = [ 'ip=192.168.0.205' ]
vnc=1
vncviewer=0
Do you not have to set vncviewer to 1 to get it create the window for you? I personally used SDL instead (sdl=1). You also say your domain is 17, I think when I experimented with VNC I found it to create the listening port on something like 4017 or whatever. I used netstat -l to find out what port it was actually on.

Ben, lastly, could you check your /var/log/xen folder for error messages, specifically check the most recent qemu log.

Thanks,

Ryan.
***********************************************

When I try to start the domain it seems to run fine:
***********************************************
pfitzner:/etc/xen# xm create winxp2 Using config file "winxp2".
Started domain winxp
***********************************************

But when I try to connect to the domain via vnc I get the message that
the viewer can't connect:
***********************************************
pfitzner:/vserver/images/domains# vncviewer pfitzner:17
vncviewer: ConnectToTcpAddr: connect: Connection refused
Unable to connect to VNC server
***********************************************

P.S.:
17 is the ID of the domain and I have a Intel Pentuim D with VT:
pfitzner:/vserver/images/domains# xm dmesg | grep VMX
(XEN) VMXON is done
(XEN) VMXON is done


Does somebody might have a idea what I did do wrong?

Tanks Ben


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users