[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-users] Problem with WinXP install. Can start but not connect via vnc


  • To: "Benny Pfitzner" <pfitzner-lug@xxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "Petersson, Mats" <Mats.Petersson@xxxxxxx>
  • Date: Wed, 20 Dec 2006 18:18:14 +0100
  • Delivery-date: Wed, 20 Dec 2006 09:18:27 -0800
  • List-id: Xen user discussion <xen-users.lists.xensource.com>
  • Thread-index: AcckWm+M4/+1PbuUTiG2yFo/FbeIKgAAB27g
  • Thread-topic: [Xen-users] Problem with WinXP install. Can start but not connect via vnc

 

> -----Original Message-----
> From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx 
> [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of 
> Benny Pfitzner
> Sent: 20 December 2006 17:15
> To: xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-users] Problem with WinXP install. Can 
> start but not connect via vnc
> 
> 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.
> 
> 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.
> 
> I posted my netstat -l output here because I just can't find the port:
> http://pastebin.ca/raw/286397
> 
> 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

I bet you don't have a qemu-dm process for some reason... Try starting
the domain from scratch (booting from the hard-disk, not CD-ROM this
time). 

If starting it again doesn't work, can you show the qemu-log from the
new vm?

--
Mats
> 
> 
> 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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.