Hi,
I am trying to accomplish the following:
- The hardware is a recent HP workstation xw6400 with a dual core Xeon
processor. HVM is enabled in bios. 2Gb Ram available.
- Dom0 is Centos 5, x86 (on xen 3.0.3 with redhat''s modifications)
- I would like to migrate a Qemu Windows XP installation to a xen hvm
I figured this should not be too hard, because full virtualisation uses the
same (or allmost the same?) device model as qemu and under qemu, my Windows
XP installation is working fine.
I have created a config file (see below), and started the guest domain with
xm create /etc/xen/WinXP.hvm
xm then tells me that the domain was started succesfully, and xm list does
show it:
[root@localhost ~]# xm list
Name ID Mem(MiB) VCPUs State Time(s)
Domain-0 0 1488 2 r----- 185.5
WindowsXP 6 517 1 ------ 0.0
However, I can''t find a way to connect to it via vnc. I tried
vncviewer localhost:10
But this returns immediatly with
VNC Viewer Free Edition 4.1.2 for X - built Mar 14 2007 22:51:02
Copyright (C) 2002-2005 RealVNC Ltd.
See http://www.realvnc.com for information on VNC.
Thu May 31 22:53:15 2007
main: unable to connect to host: Connection refused (111)
What is happening here ?
Below is my Guest domain''s config. I have set the options to match the
original qemu config as close as possible.
# -*- mode: python; -*-
#===========================================================================#
Python configuration setup for ''xm create''.
# This script sets the parameters used when a domain is created using
''xm
create''.
# You use a separate script for each domain you want to create, or
# you can set the parameters for the domain on the xm command line.
#===========================================================================import
os, re
arch = os.uname()[4]
if re.search(''64'', arch):
arch_libdir = ''lib64''
else:
arch_libdir = ''lib''
kernel = "/usr/lib/xen/boot/hvmloader"
builder=''hvm''
memory = 512
shadow_memory = 8
name = "WindowsXP"
vcpus=2
#pae=0
#acpi=0
#apic=0
vif = [ ''type=ioemu, mac=00:18:32:6c:00:ba, bridge=xenbr0'' ]
disk = [ ''file:/var/images/winxp.qcow,hda,w'',
'',hdc:cdrom,r'' ]
device_model = ''/usr/'' + arch_libdir +
''/xen/bin/qemu-dm''
sdl=0
vnc=1
vncdisplay=10
vncconsole=0
vncpasswd=''''
stdvga=1
serial=''pty''
soundhw=''sb16''
usb=1
usbdevice=''tablet''
keymap=''be''
Geert
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Try vncviewer localhost::5910 Any luck then? Cheers, Mark On Thursday 31 May 2007, Geert Janssens wrote:> Hi, > > I am trying to accomplish the following: > - The hardware is a recent HP workstation xw6400 with a dual core Xeon > processor. HVM is enabled in bios. 2Gb Ram available. > - Dom0 is Centos 5, x86 (on xen 3.0.3 with redhat''s modifications) > - I would like to migrate a Qemu Windows XP installation to a xen hvm > > I figured this should not be too hard, because full virtualisation uses the > same (or allmost the same?) device model as qemu and under qemu, my Windows > XP installation is working fine. > > I have created a config file (see below), and started the guest domain with > xm create /etc/xen/WinXP.hvm > > xm then tells me that the domain was started succesfully, and xm list does > show it: > [root@localhost ~]# xm list > Name ID Mem(MiB) VCPUs State Time(s) > Domain-0 0 1488 2 r----- 185.5 > WindowsXP 6 517 1 ------ 0.0 > > However, I can''t find a way to connect to it via vnc. I tried > vncviewer localhost:10 > > But this returns immediatly with > VNC Viewer Free Edition 4.1.2 for X - built Mar 14 2007 22:51:02 > Copyright (C) 2002-2005 RealVNC Ltd. > See http://www.realvnc.com for information on VNC. > > Thu May 31 22:53:15 2007 > main: unable to connect to host: Connection refused (111) > > What is happening here ? > > Below is my Guest domain''s config. I have set the options to match the > original qemu config as close as possible. > # -*- mode: python; -*- > #=========================================================================>== # Python configuration setup for ''xm create''. > # This script sets the parameters used when a domain is created using ''xm > create''. > # You use a separate script for each domain you want to create, or > # you can set the parameters for the domain on the xm command line. > #=========================================================================>== import os, re > arch = os.uname()[4] > if re.search(''64'', arch): > arch_libdir = ''lib64'' > else: > arch_libdir = ''lib'' > kernel = "/usr/lib/xen/boot/hvmloader" > builder=''hvm'' > memory = 512 > shadow_memory = 8 > name = "WindowsXP" > vcpus=2 > #pae=0 > #acpi=0 > #apic=0 > vif = [ ''type=ioemu, mac=00:18:32:6c:00:ba, bridge=xenbr0'' ] > disk = [ ''file:/var/images/winxp.qcow,hda,w'', '',hdc:cdrom,r'' ] > device_model = ''/usr/'' + arch_libdir + ''/xen/bin/qemu-dm'' > sdl=0 > vnc=1 > vncdisplay=10 > vncconsole=0 > vncpasswd='''' > stdvga=1 > serial=''pty'' > soundhw=''sb16'' > usb=1 > usbdevice=''tablet'' > keymap=''be'' > > > Geert > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users-- Dave: Just a question. What use is a unicyle with no seat? And no pedals! Mark: To answer a question with a question: What use is a skateboard? Dave: Skateboards have wheels. Mark: My wheel has a wheel! _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Martin Goldstone
2007-Jun-01 07:46 UTC
Re: [Xen-users] Setup WinXP with HVM and qemu image
Have you tried setting the cdrom to some device or file (ie disk = [ ''file:/var/images/winxp.qcow,hda,w'', ''file:/isoimage.iso,hdc:cdrom,r'' ])? Martin Geert Janssens wrote:> Hi, > > I am trying to accomplish the following: > - The hardware is a recent HP workstation xw6400 with a dual core Xeon > processor. HVM is enabled in bios. 2Gb Ram available. > - Dom0 is Centos 5, x86 (on xen 3.0.3 with redhat''s modifications) > - I would like to migrate a Qemu Windows XP installation to a xen hvm > > I figured this should not be too hard, because full virtualisation uses the > same (or allmost the same?) device model as qemu and under qemu, my Windows > XP installation is working fine. > > I have created a config file (see below), and started the guest domain with > xm create /etc/xen/WinXP.hvm > > xm then tells me that the domain was started succesfully, and xm list does > show it: > [root@localhost ~]# xm list > Name ID Mem(MiB) VCPUs State Time(s) > Domain-0 0 1488 2 r----- 185.5 > WindowsXP 6 517 1 ------ 0.0 > > However, I can''t find a way to connect to it via vnc. I tried > vncviewer localhost:10 > > But this returns immediatly with > VNC Viewer Free Edition 4.1.2 for X - built Mar 14 2007 22:51:02 > Copyright (C) 2002-2005 RealVNC Ltd. > See http://www.realvnc.com for information on VNC. > > Thu May 31 22:53:15 2007 > main: unable to connect to host: Connection refused (111) > > What is happening here ? > > Below is my Guest domain''s config. I have set the options to match the > original qemu config as close as possible. > # -*- mode: python; -*- > #===========================================================================> # Python configuration setup for ''xm create''. > # This script sets the parameters used when a domain is created using ''xm > create''. > # You use a separate script for each domain you want to create, or > # you can set the parameters for the domain on the xm command line. > #===========================================================================> import os, re > arch = os.uname()[4] > if re.search(''64'', arch): > arch_libdir = ''lib64'' > else: > arch_libdir = ''lib'' > kernel = "/usr/lib/xen/boot/hvmloader" > builder=''hvm'' > memory = 512 > shadow_memory = 8 > name = "WindowsXP" > vcpus=2 > #pae=0 > #acpi=0 > #apic=0 > vif = [ ''type=ioemu, mac=00:18:32:6c:00:ba, bridge=xenbr0'' ] > disk = [ ''file:/var/images/winxp.qcow,hda,w'', '',hdc:cdrom,r'' ] > device_model = ''/usr/'' + arch_libdir + ''/xen/bin/qemu-dm'' > sdl=0 > vnc=1 > vncdisplay=10 > vncconsole=0 > vncpasswd='''' > stdvga=1 > serial=''pty'' > soundhw=''sb16'' > usb=1 > usbdevice=''tablet'' > keymap=''be'' > > > Geert > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
...> xm then tells me that the domain was started succesfully, and xm list does > show it: > [root@localhost ~]# xm list > Name ID Mem(MiB) VCPUs State Time(s) > Domain-0 0 1488 2 r----- 185.5 > WindowsXP 6 517 1 ------ 0.0 > > However, I can''t find a way to connect to it via vnc. I tried > vncviewer localhost:10 > > But this returns immediatly with > VNC Viewer Free Edition 4.1.2 for X - built Mar 14 2007 22:51:02 > Copyright (C) 2002-2005 RealVNC Ltd. > See http://www.realvnc.com for information on VNC. > > Thu May 31 22:53:15 2007 > main: unable to connect to host: Connection refused (111) > > What is happening here ?You can check what ports are opened with command: # netstat -lnp -A inet> [root@localhost ~]# xm list > Name ID Mem(MiB) VCPUs State Time(s) > Domain-0 0 1488 2 r----- 185.5 > WindowsXP 6 517 1 ------ 0.0Also, It seems strange to me that WindowsXP Time = 0.0. If the domain were running that field AFIAK would not be equal to 0.0 -- WBR, i.m.chubin _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Another idea. In this line:> disk = [ ''file:/var/images/winxp.qcow,hda,w'', '',hdc:cdrom,r'' ]you specify winxp.qcow file to use as disk for Xen domain. AFAIK you must use raw images, but not qcow. To convert qcow image to raw format you can use the command: qemu-img convert winxp.qcow -O raw winxp.img After that you can check that winxp.img is correct raw image with fdisk command (fdisk should show partition table on the image). fdisk -l winxp.img -- WBR, i.m.chubin _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Mark, Martin and Igor,
Thank you for your quick responses. I got a little further already.
I converted my qcow diskfile to raw as suggested by Igor, I explicitly added a
device for the cdrom entry, I also removed the cdrom entry completely...
vncviewer localhost::5910 results in the same error message (connection
refused). I assume this means the vnc server isn''t running ?
Then I noticed that qemu-dm.<pid>.log contains this:
domid: 5
qemu: the number of cpus is 1
shared page at pfn:1ffff, mfn: 18dc2
buffered io page at pfn:1fffd, mfn: 18dc4
xs_read(): vncpasswd get error.
/vm/89bf518d-a688-d763-30ba-b3755f934861/vncpasswd.
Could not read keymap file: ''/usr/share/xen/qemu/keymaps/be''
I searched for the missing keymap, and indeed, "be" isn''t
listed. "nl-be" is,
so I used that.
With these changes, the vnc console pops up by itself (Yay!), but after a very
short time only shows me a black screen. The top command shows that qemu-dm
is using 100% cpu on one of the cores. When I remove the keyboard parameter,
it''s slightly different: the vnc console pops up, it detects my primary
HD,
then prints "Booting from Hard Disk..." and then just sits there,
again with
qemu-dm taking 100% cpu on one core.
qemu-dm.<pid>.log now contains:
domid: 7
qemu: the number of cpus is 1
shared page at pfn:1ffff, mfn: 1cdc2
buffered io page at pfn:1fffd, mfn: 1cdc4
xs_read(): vncpasswd get error.
/vm/430a79b5-d4d5-92a7-82ef-b8be59f62749/vncpasswd.
char device redirected to /dev/pts/5
False I/O request ... in-service already: 0, pvalid: 0, port: 0, data: 0,
count: 0, size: 0
xm list gives:
[root@localhost ~]# xm list
Name ID Mem(MiB) VCPUs State Time(s)
Domain-0 0 1488 2 r----- 1639.8
WindowsXP 7 517 1 ------ 0.2
So there seems to be slightly more activity (0.2), although this time
doesn''t
increase anymore.
I have no idea how to proceed here. Any ideas ?
By the way: although I explicitly set vncdisplay, the vncserver continues to
look for an unused port, as ps shows:
root 12440 1 0 11:27 ? 00:00:00
/usr/lib/xen/bin/xen-vncfb --unused --listen 0.0.0.0
--domid 7 --title WindowsXP
I tried to add vncunused=0, but that resulted in an error message when
creating the domain:
Error: unsupported input type(s) for operand +: ''int'' and
''str''.
But this doesn''t really matter anymore for my setup, so I disabled it
again.
Regards,
Geert
On Thursday 31 May 2007 23:07, you wrote:> Hi,
>
> I am trying to accomplish the following:
> - The hardware is a recent HP workstation xw6400 with a dual core Xeon
> processor. HVM is enabled in bios. 2Gb Ram available.
> - Dom0 is Centos 5, x86 (on xen 3.0.3 with redhat''s modifications)
> - I would like to migrate a Qemu Windows XP installation to a xen hvm
>
> I figured this should not be too hard, because full virtualisation uses the
> same (or allmost the same?) device model as qemu and under qemu, my Windows
> XP installation is working fine.
>
> I have created a config file (see below), and started the guest domain with
> xm create /etc/xen/WinXP.hvm
>
> xm then tells me that the domain was started succesfully, and xm list does
> show it:
> [root@localhost ~]# xm list
> Name ID Mem(MiB) VCPUs State Time(s)
> Domain-0 0 1488 2 r----- 185.5
> WindowsXP 6 517 1 ------ 0.0
>
> However, I can''t find a way to connect to it via vnc. I tried
> vncviewer localhost:10
>
> But this returns immediatly with
> VNC Viewer Free Edition 4.1.2 for X - built Mar 14 2007 22:51:02
> Copyright (C) 2002-2005 RealVNC Ltd.
> See http://www.realvnc.com for information on VNC.
>
> Thu May 31 22:53:15 2007
> main: unable to connect to host: Connection refused (111)
>
> What is happening here ?
>
> Below is my Guest domain''s config. I have set the options to match
the
> original qemu config as close as possible.
> # -*- mode: python; -*-
>
#=========================================================================>==
# Python configuration setup for ''xm create''.
> # This script sets the parameters used when a domain is created using
''xm
> create''.
> # You use a separate script for each domain you want to create, or
> # you can set the parameters for the domain on the xm command line.
>
#=========================================================================>==
import os, re
> arch = os.uname()[4]
> if re.search(''64'', arch):
> arch_libdir = ''lib64''
> else:
> arch_libdir = ''lib''
> kernel = "/usr/lib/xen/boot/hvmloader"
> builder=''hvm''
> memory = 512
> shadow_memory = 8
> name = "WindowsXP"
> vcpus=2
> #pae=0
> #acpi=0
> #apic=0
> vif = [ ''type=ioemu, mac=00:18:32:6c:00:ba,
bridge=xenbr0'' ]
> disk = [ ''file:/var/images/winxp.qcow,hda,w'',
'',hdc:cdrom,r'' ]
> device_model = ''/usr/'' + arch_libdir +
''/xen/bin/qemu-dm''
> sdl=0
> vnc=1
> vncdisplay=10
> vncconsole=0
> vncpasswd=''''
> stdvga=1
> serial=''pty''
> soundhw=''sb16''
> usb=1
> usbdevice=''tablet''
> keymap=''be''
>
>
> Geert
--
Kobalt W.I.T.
Web & Information Technology
Brusselsesteenweg 152
1850 Grimbergen
Tel : +32 479 339 655
Email: info@kobaltwit.be
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
On Fr, Jun 01, 2007 at 11:44:30 +0200, Geert Janssens wrote:> Mark, Martin and Igor, > > Thank you for your quick responses. I got a little further already. > > I converted my qcow diskfile to raw as suggested by Igor, I explicitly added a > device for the cdrom entry, I also removed the cdrom entry completely... > > vncviewer localhost::5910 results in the same error message (connection > refused). I assume this means the vnc server isn''t running ? > > Then I noticed that qemu-dm.<pid>.log contains this: > domid: 5 > qemu: the number of cpus is 1 > shared page at pfn:1ffff, mfn: 18dc2 > buffered io page at pfn:1fffd, mfn: 18dc4 > xs_read(): vncpasswd get error. > /vm/89bf518d-a688-d763-30ba-b3755f934861/vncpasswd. > Could not read keymap file: ''/usr/share/xen/qemu/keymaps/be'' > > I searched for the missing keymap, and indeed, "be" isn''t listed. "nl-be" is, > so I used that. > > With these changes, the vnc console pops up by itself (Yay!), but after a very > short time only shows me a black screen. The top command shows that qemu-dm > is using 100% cpu on one of the cores. When I remove the keyboard parameter, > it''s slightly different: the vnc console pops up, it detects my primary HD, > then prints "Booting from Hard Disk..." and then just sits there, again with > qemu-dm taking 100% cpu on one core. > > qemu-dm.<pid>.log now contains: > domid: 7 > qemu: the number of cpus is 1 > shared page at pfn:1ffff, mfn: 1cdc2 > buffered io page at pfn:1fffd, mfn: 1cdc4 > xs_read(): vncpasswd get error. > /vm/430a79b5-d4d5-92a7-82ef-b8be59f62749/vncpasswd. > char device redirected to /dev/pts/5 > False I/O request ... in-service already: 0, pvalid: 0, port: 0, data: 0, > count: 0, size: 0 > > xm list gives: > [root@localhost ~]# xm list > Name ID Mem(MiB) VCPUs State Time(s) > Domain-0 0 1488 2 r----- 1639.8 > WindowsXP 7 517 1 ------ 0.2 > So there seems to be slightly more activity (0.2), although this time doesn''t > increase anymore. > > I have no idea how to proceed here. Any ideas ?My idea is try to run the domain from bootable cd (not from image) and look what happens. You must determine is the problem related to your image (which you have converted) or from something else. When you boot from CD system doesn''t concern about your virtual disk image (but it must exist if you have specified it in the domU config file).> > By the way: although I explicitly set vncdisplay, the vncserver continues to > look for an unused port, as ps shows: > root 12440 1 0 11:27 ? 00:00:00 > /usr/lib/xen/bin/xen-vncfb --unused --listen 0.0.0.0 > --domid 7 --title WindowsXP > > I tried to add vncunused=0, but that resulted in an error message when > creating the domain: > Error: unsupported input type(s) for operand +: ''int'' and ''str''. > But this doesn''t really matter anymore for my setup, so I disabled it again. >AFAIK, there is parameter in xend-config.sxp which regulates what port (or screen number) Xen vnc must use. -- WBR, i.m.chubin _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Geert Janssens
2007-Jun-01 11:11 UTC
Re: [Xen-users] Re: Setup WinXP with HVM and qemu image
On Friday 1 June 2007 12:22, Igor Chubin wrote:> > qemu-dm.<pid>.log now contains: > > domid: 7 > > qemu: the number of cpus is 1 > > shared page at pfn:1ffff, mfn: 1cdc2 > > buffered io page at pfn:1fffd, mfn: 1cdc4 > > xs_read(): vncpasswd get error. > > /vm/430a79b5-d4d5-92a7-82ef-b8be59f62749/vncpasswd. > > char device redirected to /dev/pts/5 > > False I/O request ... in-service already: 0, pvalid: 0, port: 0, data: 0, > > count: 0, size: 0 > > > > xm list gives: > > [root@localhost ~]# xm list > > Name ID Mem(MiB) VCPUs State > > Time(s) Domain-0 0 1488 2 > > r----- 1639.8 WindowsXP 7 517 > > 1 ------ 0.2 So there seems to be slightly more activity (0.2), > > although this time doesn''t increase anymore. > > > > I have no idea how to proceed here. Any ideas ? > > My idea is > > try to run the domain from bootable cd (not from image) > and look what happens. > > You must determine is the problem related to your image (which you > have converted) or from something else. >So I tried your suggestion. I changed the disk line to disk = [ ''file:/var/images/winxp.img,hda,w'', ''phy:/dev/cdrom,hdc:cdrom,r'' ] and set boot="dc" I put a bootable Knoppix CD in the CD-drive (which I know works on real hardware). After xm create, I get a vnc console that now shows a QEMU Harddisk and a QEMU CD/DVD rom (ata0 master and ata1 master respectively, the slaves are reported as Unknown device). Then the CD spins up, but nothing else happens. The cd just slows down again after a moment. This same thing happens when I only have the CDROM device, and no disk image: CDROM drive is recognised, CD spins up, but nothing else. Regards, Geert -- Kobalt W.I.T. Web & Information Technology Brusselsesteenweg 152 1850 Grimbergen Tel : +32 479 339 655 Email: info@kobaltwit.be _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Petersson, Mats
2007-Jun-01 11:24 UTC
RE: [Xen-users] Re: Setup WinXP with HVM and qemu image
> -----Original Message----- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of > Geert Janssens > Sent: 01 June 2007 12:12 > To: xen-users@lists.xensource.com > Subject: Re: [Xen-users] Re: Setup WinXP with HVM and qemu image > > On Friday 1 June 2007 12:22, Igor Chubin wrote: > > > qemu-dm.<pid>.log now contains: > > > domid: 7 > > > qemu: the number of cpus is 1 > > > shared page at pfn:1ffff, mfn: 1cdc2 > > > buffered io page at pfn:1fffd, mfn: 1cdc4 > > > xs_read(): vncpasswd get error. > > > /vm/430a79b5-d4d5-92a7-82ef-b8be59f62749/vncpasswd. > > > char device redirected to /dev/pts/5 > > > False I/O request ... in-service already: 0, pvalid: 0, > port: 0, data: 0, > > > count: 0, size: 0 > > > > > > xm list gives: > > > [root@localhost ~]# xm list > > > Name ID Mem(MiB) > VCPUs State > > > Time(s) Domain-0 0 > 1488 2 > > > r----- 1639.8 WindowsXP > 7 517 > > > 1 ------ 0.2 So there seems to be slightly more > activity (0.2), > > > although this time doesn''t increase anymore. > > > > > > I have no idea how to proceed here. Any ideas ? > > > > My idea is > > > > try to run the domain from bootable cd (not from image) > > and look what happens. > > > > You must determine is the problem related to your image (which you > > have converted) or from something else. > > > So I tried your suggestion. I changed the disk line to > disk = [ ''file:/var/images/winxp.img,hda,w'', > ''phy:/dev/cdrom,hdc:cdrom,r'' ] > and set > boot="dc" > > I put a bootable Knoppix CD in the CD-drive (which I know > works on real > hardware). > After xm create, I get a vnc console that now shows a QEMU > Harddisk and a QEMU > CD/DVD rom (ata0 master and ata1 master respectively, the > slaves are reported > as Unknown device). > > Then the CD spins up, but nothing else happens. The cd just > slows down again > after a moment. > > This same thing happens when I only have the CDROM device, > and no disk image: > CDROM drive is recognised, CD spins up, but nothing else.What are the settings for PAE, APIC and ACPI in your guest config? Try turning for example APIC off (this will essentially make your system single-CPU, but if you are on an older version of Xen, you won''t be able to run SMP HVM guests anyways). -- Mats> > Regards, > > Geert > -- > Kobalt W.I.T. > Web & Information Technology > Brusselsesteenweg 152 > 1850 Grimbergen > > Tel : +32 479 339 655 > Email: info@kobaltwit.be > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Geert Janssens
2007-Jun-01 12:53 UTC
Re: [Xen-users] Re: Setup WinXP with HVM and qemu image
On Friday 1 June 2007 13:24, you wrote:> What are the settings for PAE, APIC and ACPI in your guest config? > > Try turning for example APIC off (this will essentially make your system > single-CPU, but if you are on an older version of Xen, you won''t be able > to run SMP HVM guests anyways). >PAE, APIC and ACPI were commented out in the guest config. I have uncommented them and set them in all possible combinations of 0''s and 1''s. I don''t see a change. The CD doesn''t spin up anymore either. (Note: I did switch to sdl because with vnc I had to click away a small dialog about a broken connection each time I shut down the guest. After 30 or so attempts at starting and stopping the guest this became annoying). The guest''s screen always ends up black. xm dmesg shows this (for the last guest): (XEN) (file=hvm.c, line=197) Allocated port 3 for hvm. (XEN) vmx_do_launch(): GUEST_CR3<=001a5da0, HOST_CR3<=55da7000 (XEN) printk: 22 messages suppressed. (XEN) DOM0: (file=mm.c, line=594) Non-privileged (46) attempt to map I/O space ffffffff (XEN) DOM0: (file=mm.c, line=594) Non-privileged (46) attempt to map I/O space ffffffff (XEN) DOM0: (file=mm.c, line=594) Non-privileged (46) attempt to map I/O space ffffffff (XEN) DOM0: (file=mm.c, line=594) Non-privileged (46) attempt to map I/O space ffffffff (XEN) DOM0: (file=mm.c, line=594) Non-privileged (46) attempt to map I/O space ffffffff (XEN) DOM0: (file=mm.c, line=594) Non-privileged (46) attempt to map I/O space ffffffff (XEN) DOM0: (file=mm.c, line=594) Non-privileged (46) attempt to map I/O space ffffffff (XEN) DOM0: (file=mm.c, line=594) Non-privileged (46) attempt to map I/O space ffffffff (XEN) DOM0: (file=mm.c, line=594) Non-privileged (46) attempt to map I/O space ffffffff (XEN) DOM0: (file=mm.c, line=594) Non-privileged (46) attempt to map I/O space ffffffff (XEN) (GUEST: 46) HVM Loader (XEN) (GUEST: 46) Detected Xen v3.0.3-rc5-8.1.4.el (XEN) (GUEST: 46) Writing SMBIOS tables ... (XEN) (GUEST: 46) Loading ROMBIOS ... (XEN) (GUEST: 46) Loading Standard VGABIOS ... (XEN) (GUEST: 46) Loading VMXAssist ... (XEN) (GUEST: 46) VMX go ... (XEN) (GUEST: 46) VMXAssist (Apr 9 2007) (XEN) (GUEST: 46) Memory size 512 MB (XEN) (GUEST: 46) E820 map: (XEN) (GUEST: 46) 0000000000000000 - 000000000009F000 (RAM) (XEN) (GUEST: 46) 000000000009F000 - 00000000000A0000 (Reserved) (XEN) (GUEST: 46) 00000000000A0000 - 00000000000C0000 (Type 16) (XEN) (GUEST: 46) 00000000000F0000 - 0000000000100000 (Reserved) (XEN) (GUEST: 46) 0000000000100000 - 000000001FFF0000 (RAM) (XEN) (GUEST: 46) 000000001FFF0000 - 000000001FFFA000 (ACPI Data) (XEN) (GUEST: 46) 000000001FFFA000 - 000000001FFFD000 (ACPI NVS) (XEN) (GUEST: 46) 000000001FFFD000 - 000000001FFFE000 (Type 19) (XEN) (GUEST: 46) 000000001FFFE000 - 000000001FFFF000 (Type 18) (XEN) (GUEST: 46) 000000001FFFF000 - 0000000020000000 (Type 17) (XEN) (GUEST: 46) 00000000FEC00000 - 0000000100000000 (Type 16) (XEN) (GUEST: 46) (XEN) (GUEST: 46) Start BIOS ... (XEN) (GUEST: 46) Starting emulated 16-bit real-mode: ip=F000:FFF0 (XEN) (GUEST: 46) rombios.c,v 1.138 2005/05/07 15:55:26 vruppert Exp $ (XEN) (GUEST: 46) Remapping master: ICW2 0x8 -> 0x20 (XEN) (GUEST: 46) Remapping slave: ICW2 0x70 -> 0x28 (XEN) (GUEST: 46) VGABios $Id: vgabios.c,v 1.61 2005/05/24 16:50:50 vruppert Exp $ (XEN) (GUEST: 46) HVMAssist BIOS, 1 cpu, $Revision: 1.138 $ $Date: 2005/05/07 15:55:26 $ (XEN) (GUEST: 46) (XEN) (GUEST: 46) ata0-0: PCHS=11987/16/63 translation=lba LCHS=752/255/63 (XEN) (GUEST: 46) ata0 master: QEMU HARDDISK ATA-7 Hard-Disk (5900 MBytes) (XEN) (GUEST: 46) ata0 slave: Unknown device (XEN) (GUEST: 46) ata1 master: QEMU CD-ROM ATAPI-4 CD-Rom/DVD-Rom (XEN) (GUEST: 46) ata1 slave: Unknown device (XEN) (GUEST: 46) (XEN) (GUEST: 46) Booting from CD-Rom... (Note: in this case, I did reenable the harddisk image, but even without it, the output was similar). xend.log has this on the latest guest creation: [2007-06-01 14:37:59 xend.XendDomainInfo 25412] DEBUG (XendDomainInfo:190) XendDomainInfo.create([''vm'', [''name'', ''WindowsXP''], [''memory'', 512], [''shadow_memory'', 8], [''vcpus'', 1], [''image'', [''hvm'', [''kernel'', ''/usr/lib/xen/boot/hvmloader''], [''device_model'', ''/usr/lib/xen/bin/qemu-dm''], [''vcpus'', 1], [''boot'', ''d''], [''serial'', ''pty''], [''stdvga'', 1], [''soundhw'', ''sb16''], [''vncdisplay'', 10], [''vncunused'', 1], [''vncconsole'', 1], [''sdl'', 1], [''display'', '':0''], [''xauthority'', ''/root/.xauthtxU52s''], [''usb'', 1], [''usbdevice'', ''tablet''], [''vncpasswd'', '''']]], [''device'', [''vbd'', [''uname'', ''file:/var/images/winxp.img''], [''dev'', ''hda''], [''mode'', ''w'']]], [''device'', [''vbd'', [''uname'', ''phy:/dev/cdrom''], [''dev'', ''hdc:cdrom''], [''mode'', ''r'']]], [''device'', [''vif'', [''bridge'', ''xenbr0''], [''mac'', ''00:18:32:6c:00:ba''], [''type'', ''ioemu'']]], [''device'', [''vkbd'']], [''device'', [''vfb'', [''type'', ''sdl''], [''xauthority'', ''/root/.xauthtxU52s''], [''display'', '':0'']]]]) [2007-06-01 14:37:59 xend.XendDomainInfo 25412] DEBUG (XendDomainInfo:296) parseConfig: config is [''vm'', [''name'', ''WindowsXP''], [''memory'', 512], [''shadow_memory'', 8], [''vcpus'', 1], [''image'', [''hvm'', [''kernel'', ''/usr/lib/xen/boot/hvmloader''], [''device_model'', ''/usr/lib/xen/bin/qemu-dm''], [''vcpus'', 1], [''boot'', ''d''], [''serial'', ''pty''], [''stdvga'', 1], [''soundhw'', ''sb16''], [''vncdisplay'', 10], [''vncunused'', 1], [''vncconsole'', 1], [''sdl'', 1], [''display'', '':0''], [''xauthority'', ''/root/.xauthtxU52s''], [''usb'', 1], [''usbdevice'', ''tablet''], [''vncpasswd'', '''']]], [''device'', [''vbd'', [''uname'', ''file:/var/images/winxp.img''], [''dev'', ''hda''], [''mode'', ''w'']]], [''device'', [''vbd'', [''uname'', ''phy:/dev/cdrom''], [''dev'', ''hdc:cdrom''], [''mode'', ''r'']]], [''device'', [''vif'', [''bridge'', ''xenbr0''], [''mac'', ''00:18:32:6c:00:ba''], [''type'', ''ioemu'']]], [''device'', [''vkbd'']], [''device'', [''vfb'', [''type'', ''sdl''], [''xauthority'', ''/root/.xauthtxU52s''], [''display'', '':0'']]]] [2007-06-01 14:37:59 xend.XendDomainInfo 25412] DEBUG (XendDomainInfo:397) parseConfig: result is {''shadow_memory'': 8, ''start_time'': None, ''uuid'': None, ''on_crash'': None, ''on_reboot'': None, ''localtime'': None, ''image'': [''hvm'', [''kernel'', ''/usr/lib/xen/boot/hvmloader''], [''device_model'', ''/usr/lib/xen/bin/qemu-dm''], [''vcpus'', 1], [''boot'', ''d''], [''serial'', ''pty''], [''stdvga'', 1], [''soundhw'', ''sb16''], [''vncdisplay'', 10], [''vncunused'', 1], [''vncconsole'', 1], [''sdl'', 1], [''display'', '':0''], [''xauthority'', ''/root/.xauthtxU52s''], [''usb'', 1], [''usbdevice'', ''tablet''], [''vncpasswd'', '''']], ''on_poweroff'': None, ''bootloader_args'': None, ''cpus'': None, ''name'': ''WindowsXP'', ''backend'': [], ''vcpus'': 1, ''cpu_weight'': None, ''features'': None, ''vcpu_avail'': None, ''memory'': 512, ''device'': [(''vbd'', [''vbd'', [''uname'', ''file:/var/images/winxp.img''], [''dev'', ''hda''], [''mode'', ''w'']]), (''vbd'', [''vbd'', [''uname'', ''phy:/dev/cdrom''], [''dev'', ''hdc:cdrom''], [''mode'', ''r'']]), (''vif'', [''vif'', [''bridge'', ''xenbr0''], [''mac'', ''00:18:32:6c:00:ba''], [''type'', ''ioemu'']]), (''vkbd'', [''vkbd'']), (''vfb'', [''vfb'', [''type'', ''sdl''], [''xauthority'', ''/root/.xauthtxU52s''], [''display'', '':0'']])], ''bootloader'': None, ''cpu'': None, ''maxmem'': None} [2007-06-01 14:37:59 xend.XendDomainInfo 25412] DEBUG (XendDomainInfo:1264) XendDomainInfo.construct: None [2007-06-01 14:37:59 xend.XendDomainInfo 25412] DEBUG (XendDomainInfo:1296) XendDomainInfo.initDomain: 46 1.0 [2007-06-01 14:37:59 xend 25412] DEBUG (image:329) args: boot, val: d [2007-06-01 14:37:59 xend 25412] DEBUG (image:329) args: fda, val: None [2007-06-01 14:37:59 xend 25412] DEBUG (image:329) args: fdb, val: None [2007-06-01 14:37:59 xend 25412] DEBUG (image:329) args: soundhw, val: sb16 [2007-06-01 14:37:59 xend 25412] DEBUG (image:329) args: localtime, val: None [2007-06-01 14:37:59 xend 25412] DEBUG (image:329) args: serial, val: pty [2007-06-01 14:37:59 xend 25412] DEBUG (image:329) args: std-vga, val: 1 [2007-06-01 14:37:59 xend 25412] DEBUG (image:329) args: isa, val: None [2007-06-01 14:37:59 xend 25412] DEBUG (image:329) args: vcpus, val: 1 [2007-06-01 14:37:59 xend 25412] DEBUG (image:329) args: acpi, val: None [2007-06-01 14:37:59 xend 25412] DEBUG (image:329) args: usb, val: 1 [2007-06-01 14:37:59 xend 25412] DEBUG (image:329) args: usbdevice, val: tablet [2007-06-01 14:37:59 xend 25412] DEBUG (image:329) args: k, val: None [2007-06-01 14:37:59 xend 25412] DEBUG (balloon:127) Balloon: 546568 KiB free; need 546000; done. [2007-06-01 14:37:59 xend 25412] INFO (image:136) buildDomain os=hvm dom=46 vcpus=1 [2007-06-01 14:37:59 xend 25412] DEBUG (image:282) dom = 46 [2007-06-01 14:37:59 xend 25412] DEBUG (image:283) image = /usr/lib/xen/boot/hvmloader [2007-06-01 14:37:59 xend 25412] DEBUG (image:284) store_evtchn = 1 [2007-06-01 14:37:59 xend 25412] DEBUG (image:285) memsize = 512 [2007-06-01 14:37:59 xend 25412] DEBUG (image:286) vcpus = 1 [2007-06-01 14:37:59 xend 25412] DEBUG (image:287) pae = 0 [2007-06-01 14:37:59 xend 25412] DEBUG (image:288) acpi = 0 [2007-06-01 14:37:59 xend 25412] DEBUG (image:289) apic = 0 [2007-06-01 14:37:59 xend 25412] DEBUG (image:435) hvm shutdown watch registered [2007-06-01 14:37:59 xend 25412] DEBUG (blkif:24) exception looking up device number for hda: [Errno 2] No such file or directory: ''/dev/hda'' [2007-06-01 14:37:59 xend 25412] DEBUG (DevController:110) DevController: writing {''backend-id'': ''0'', ''virtual-device'': ''768'', ''device-type'': ''disk'', ''state'': ''1'', ''backend'': ''/local/domain/0/backend/vbd/46/768''} to /local/domain/46/device/vbd/768. [2007-06-01 14:37:59 xend 25412] DEBUG (DevController:112) DevController: writing {''domain'': ''WindowsXP'', ''frontend'': ''/local/domain/46/device/vbd/768'', ''dev'': ''hda'', ''state'': ''1'', ''params'': ''/var/images/winxp.img'', ''mode'': ''w'', ''online'': ''1'', ''frontend-id'': ''46'', ''type'': ''file''} to /local/domain/0/backend/vbd/46/768. [2007-06-01 14:37:59 xend 25412] DEBUG (blkif:24) exception looking up device number for hdc: [Errno 2] No such file or directory: ''/dev/hdc'' [2007-06-01 14:37:59 xend 25412] DEBUG (DevController:110) DevController: writing {''backend-id'': ''0'', ''virtual-device'': ''5632'', ''device-type'': ''cdrom'', ''state'': ''1'', ''backend'': ''/local/domain/0/backend/vbd/46/5632''} to /local/domain/46/device/vbd/5632. [2007-06-01 14:37:59 xend 25412] DEBUG (DevController:112) DevController: writing {''domain'': ''WindowsXP'', ''frontend'': ''/local/domain/46/device/vbd/5632'', ''dev'': ''hdc'', ''state'': ''1'', ''params'': ''/dev/cdrom'', ''mode'': ''r'', ''online'': ''1'', ''frontend-id'': ''46'', ''type'': ''phy''} to /local/domain/0/backend/vbd/46/5632. [2007-06-01 14:37:59 xend 25412] DEBUG (DevController:110) DevController: writing {''state'': ''1'', ''backend-id'': ''0'', ''backend'': ''/local/domain/0/backend/vif/46/0''} to /local/domain/46/device/vif/0. [2007-06-01 14:37:59 xend 25412] DEBUG (DevController:112) DevController: writing {''bridge'': ''xenbr0'', ''domain'': ''WindowsXP'', ''handle'': ''0'', ''script'': ''/etc/xen/scripts/vif-bridge'', ''state'': ''1'', ''frontend'': ''/local/domain/46/device/vif/0'', ''mac'': ''00:18:32:6c:00:ba'', ''online'': ''1'', ''frontend-id'': ''46'', ''type'': ''ioemu''} to /local/domain/0/backend/vif/46/0. [2007-06-01 14:37:59 xend 25412] DEBUG (DevController:110) DevController: writing {''state'': ''1'', ''backend-id'': ''0'', ''backend'': ''/local/domain/0/backend/vkbd/46/0''} to /local/domain/46/device/vkbd/0. [2007-06-01 14:37:59 xend 25412] DEBUG (DevController:112) DevController: writing {''frontend-id'': ''46'', ''domain'': ''WindowsXP'', ''frontend'': ''/local/domain/46/device/vkbd/0'', ''state'': ''1'', ''online'': ''1''} to /local/domain/0/backend/vkbd/46/0. [2007-06-01 14:37:59 xend 25412] DEBUG (DevController:110) DevController: writing {''state'': ''1'', ''backend-id'': ''0'', ''backend'': ''/local/domain/0/backend/vfb/46/0''} to /local/domain/46/device/vfb/0. [2007-06-01 14:37:59 xend 25412] DEBUG (DevController:112) DevController: writing {''domain'': ''WindowsXP'', ''frontend'': ''/local/domain/46/device/vfb/0'', ''xauthority'': ''/root/.xauthtxU52s'', ''state'': ''1'', ''online'': ''1'', ''frontend-id'': ''46'', ''type'': ''sdl'', ''display'': '':0''} to /local/domain/0/backend/vfb/46/0. [2007-06-01 14:37:59 xend 25412] INFO (image:418) spawning device models: /usr/lib/xen/bin/qemu-dm [''/usr/lib/xen/bin/qemu-dm'', ''-d'', ''46'', ''-m'', ''512'', ''-boot'', ''d'', ''-soundhw'', ''sb16'', ''-serial'', ''pty'', ''-std-vga'', ''-vcpus'', ''1'', ''-usb'', ''-usbdevice'', ''tablet'', ''-domain-name'', ''WindowsXP'', ''-net'', ''nic,vlan=1,macaddr=00:18:32:6c:00:ba,model=rtl8139'', ''-net'', ''tap,vlan=1,bridge=xenbr0'', ''-vncviewer''] [2007-06-01 14:37:59 xend 25412] INFO (image:420) device model pid: 25909 [2007-06-01 14:37:59 xend.XendDomainInfo 25412] DEBUG (XendDomainInfo:715) Storing VM details: {''shadow_memory'': ''8'', ''uuid'': ''8144837d-046b-2450-c981-599627763434'', ''on_reboot'': ''restart'', ''start_time'': ''1180701479.64'', ''on_poweroff'': ''destroy'', ''name'': ''WindowsXP'', ''xend/restart_count'': ''0'', ''vcpus'': ''1'', ''vcpu_avail'': ''1'', ''memory'': ''512'', ''on_crash'': ''restart'', ''image'': ''(hvm (kernel /usr/lib/xen/boot/hvmloader) (device_model /usr/lib/xen/bin/qemu-dm) (vcpus 1) (boot d) (serial pty) (stdvga 1) (soundhw sb16) (vncdisplay 10) (vncunused 1) (vncconsole 1) (sdl 1) (display :0) (xauthority /root/.xauthtxU52s) (usb 1) (usbdevice tablet) (vncpasswd ))'', ''maxmem'': ''512''} [2007-06-01 14:37:59 xend.XendDomainInfo 25412] DEBUG (XendDomainInfo:750) Storing domain details: {''console/port'': ''2'', ''name'': ''WindowsXP'', ''console/limit'': ''1048576'', ''vm'': ''/vm/8144837d-046b-2450-c981-599627763434'', ''domid'': ''46'', ''cpu/0/availability'': ''online'', ''memory/target'': ''524288'', ''store/ring-ref'': ''130499'', ''store/port'': ''1''} [2007-06-01 14:37:59 xend 25412] DEBUG (image:458) hvm_shutdown fired, shutdown reason=None [2007-06-01 14:37:59 xend.XendDomainInfo 25412] DEBUG (XendDomainInfo:940) XendDomainInfo.handleShutdownWatch [2007-06-01 14:37:59 xend 25412] DEBUG (DevController:143) Waiting for devices vif. [2007-06-01 14:37:59 xend 25412] DEBUG (DevController:149) Waiting for 0. [2007-06-01 14:37:59 xend 25412] DEBUG (DevController:471) hotplugStatusCallback /local/domain/0/backend/vif/46/0/hotplug-status. [2007-06-01 14:37:59 xend 25412] DEBUG (DevController:485) hotplugStatusCallback 1. [2007-06-01 14:37:59 xend 25412] DEBUG (DevController:143) Waiting for devices usb. [2007-06-01 14:37:59 xend 25412] DEBUG (DevController:143) Waiting for devices vbd. [2007-06-01 14:37:59 xend 25412] DEBUG (DevController:149) Waiting for 768. [2007-06-01 14:37:59 xend 25412] DEBUG (DevController:471) hotplugStatusCallback /local/domain/0/backend/vbd/46/768/hotplug-status. [2007-06-01 14:37:59 xend 25412] DEBUG (DevController:471) hotplugStatusCallback /local/domain/0/backend/vbd/46/768/hotplug-status. [2007-06-01 14:37:59 xend 25412] DEBUG (DevController:485) hotplugStatusCallback 1. [2007-06-01 14:37:59 xend 25412] DEBUG (DevController:149) Waiting for 5632. [2007-06-01 14:37:59 xend 25412] DEBUG (DevController:471) hotplugStatusCallback /local/domain/0/backend/vbd/46/5632/hotplug-status. [2007-06-01 14:37:59 xend 25412] DEBUG (DevController:485) hotplugStatusCallback 1. [2007-06-01 14:37:59 xend 25412] DEBUG (DevController:143) Waiting for devices irq. [2007-06-01 14:37:59 xend 25412] DEBUG (DevController:143) Waiting for devices vkbd. [2007-06-01 14:37:59 xend 25412] DEBUG (DevController:149) Waiting for 0. [2007-06-01 14:37:59 xend 25412] DEBUG (DevController:471) hotplugStatusCallback /local/domain/0/backend/vkbd/46/0/hotplug-status. [2007-06-01 14:37:59 xend 25412] DEBUG (DevController:485) hotplugStatusCallback 1. [2007-06-01 14:37:59 xend 25412] DEBUG (DevController:143) Waiting for devices vfb. [2007-06-01 14:37:59 xend 25412] DEBUG (DevController:149) Waiting for 0. [2007-06-01 14:37:59 xend 25412] DEBUG (DevController:471) hotplugStatusCallback /local/domain/0/backend/vfb/46/0/hotplug-status. [2007-06-01 14:37:59 xend 25412] DEBUG (DevController:485) hotplugStatusCallback 1. [2007-06-01 14:37:59 xend 25412] DEBUG (DevController:143) Waiting for devices pci. [2007-06-01 14:37:59 xend 25412] DEBUG (DevController:143) Waiting for devices ioports. [2007-06-01 14:37:59 xend 25412] DEBUG (DevController:143) Waiting for devices tap. [2007-06-01 14:37:59 xend 25412] DEBUG (DevController:143) Waiting for devices vtpm. [2007-06-01 14:37:59 xend 25412] INFO (XendDomain:370) Domain WindowsXP (46) unpaused. I noticed in there, there are two errors for the blockdevices: DEBUG (blkif:24) exception looking up device number for hda: [Errno 2] No such file or directory: ''/dev/hda'' and DEBUG (blkif:24) exception looking up device number for hdc: [Errno 2] No such file or directory: ''/dev/hdc'' They don''t seem to be critical. For the rest, qemu-dm contintues to use 100% cpu on one core, but nothing happens. What is going on there ? Geert -- Kobalt W.I.T. Web & Information Technology Brusselsesteenweg 152 1850 Grimbergen Tel : +32 479 339 655 Email: info@kobaltwit.be _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Petersson, Mats
2007-Jun-01 14:38 UTC
RE: [Xen-users] Re: Setup WinXP with HVM and qemu image
> -----Original Message----- > From: Geert Janssens [mailto:info@kobaltwit.be] > Sent: 01 June 2007 13:54 > To: Petersson, Mats > Cc: xen-users@lists.xensource.com > Subject: Re: [Xen-users] Re: Setup WinXP with HVM and qemu image > > On Friday 1 June 2007 13:24, you wrote: > > What are the settings for PAE, APIC and ACPI in your guest config? > > > > Try turning for example APIC off (this will essentially > make your system > > single-CPU, but if you are on an older version of Xen, you > won''t be able > > to run SMP HVM guests anyways). > > > PAE, APIC and ACPI were commented out in the guest config. I > have uncommented > them and set them in all possible combinations of 0''s and > 1''s. I don''t see a > change. The CD doesn''t spin up anymore either. > > (Note: I did switch to sdl because with vnc I had to click > away a small dialog > about a broken connection each time I shut down the guest. > After 30 or so > attempts at starting and stopping the guest this became annoying). > > The guest''s screen always ends up black. xm dmesg shows this > (for the last > guest): > (XEN) (file=hvm.c, line=197) Allocated port 3 for hvm. > (XEN) vmx_do_launch(): GUEST_CR3<=001a5da0, HOST_CR3<=55da7000 > (XEN) printk: 22 messages suppressed. > (XEN) DOM0: (file=mm.c, line=594) Non-privileged (46) attempt > to map I/O space > ffffffff > (XEN) DOM0: (file=mm.c, line=594) Non-privileged (46) attempt > to map I/O space > ffffffff > (XEN) DOM0: (file=mm.c, line=594) Non-privileged (46) attempt > to map I/O space > ffffffff > (XEN) DOM0: (file=mm.c, line=594) Non-privileged (46) attempt > to map I/O space > ffffffff > (XEN) DOM0: (file=mm.c, line=594) Non-privileged (46) attempt > to map I/O space > ffffffff > (XEN) DOM0: (file=mm.c, line=594) Non-privileged (46) attempt > to map I/O space > ffffffff > (XEN) DOM0: (file=mm.c, line=594) Non-privileged (46) attempt > to map I/O space > ffffffff > (XEN) DOM0: (file=mm.c, line=594) Non-privileged (46) attempt > to map I/O space > ffffffff > (XEN) DOM0: (file=mm.c, line=594) Non-privileged (46) attempt > to map I/O space > ffffffff > (XEN) DOM0: (file=mm.c, line=594) Non-privileged (46) attempt > to map I/O space > ffffffff > (XEN) (GUEST: 46) HVM Loader > (XEN) (GUEST: 46) Detected Xen v3.0.3-rc5-8.1.4.el > (XEN) (GUEST: 46) Writing SMBIOS tables ... > (XEN) (GUEST: 46) Loading ROMBIOS ... > (XEN) (GUEST: 46) Loading Standard VGABIOS ... > (XEN) (GUEST: 46) Loading VMXAssist ... > (XEN) (GUEST: 46) VMX go ... > (XEN) (GUEST: 46) VMXAssist (Apr 9 2007) > (XEN) (GUEST: 46) Memory size 512 MB > (XEN) (GUEST: 46) E820 map: > (XEN) (GUEST: 46) 0000000000000000 - 000000000009F000 (RAM) > (XEN) (GUEST: 46) 000000000009F000 - 00000000000A0000 (Reserved) > (XEN) (GUEST: 46) 00000000000A0000 - 00000000000C0000 (Type 16) > (XEN) (GUEST: 46) 00000000000F0000 - 0000000000100000 (Reserved) > (XEN) (GUEST: 46) 0000000000100000 - 000000001FFF0000 (RAM) > (XEN) (GUEST: 46) 000000001FFF0000 - 000000001FFFA000 (ACPI Data) > (XEN) (GUEST: 46) 000000001FFFA000 - 000000001FFFD000 (ACPI NVS) > (XEN) (GUEST: 46) 000000001FFFD000 - 000000001FFFE000 (Type 19) > (XEN) (GUEST: 46) 000000001FFFE000 - 000000001FFFF000 (Type 18) > (XEN) (GUEST: 46) 000000001FFFF000 - 0000000020000000 (Type 17) > (XEN) (GUEST: 46) 00000000FEC00000 - 0000000100000000 (Type 16) > (XEN) (GUEST: 46) > (XEN) (GUEST: 46) Start BIOS ... > (XEN) (GUEST: 46) Starting emulated 16-bit real-mode: ip=F000:FFF0 > (XEN) (GUEST: 46) rombios.c,v 1.138 2005/05/07 15:55:26 > vruppert Exp $ > (XEN) (GUEST: 46) Remapping master: ICW2 0x8 -> 0x20 > (XEN) (GUEST: 46) Remapping slave: ICW2 0x70 -> 0x28 > (XEN) (GUEST: 46) VGABios $Id: vgabios.c,v 1.61 2005/05/24 > 16:50:50 vruppert > Exp $ > (XEN) (GUEST: 46) HVMAssist BIOS, 1 cpu, $Revision: 1.138 $ > $Date: 2005/05/07 > 15:55:26 $ > (XEN) (GUEST: 46) > (XEN) (GUEST: 46) ata0-0: PCHS=11987/16/63 translation=lba > LCHS=752/255/63 > (XEN) (GUEST: 46) ata0 master: QEMU HARDDISK ATA-7 Hard-Disk > (5900 MBytes) > (XEN) (GUEST: 46) ata0 slave: Unknown device > (XEN) (GUEST: 46) ata1 master: QEMU CD-ROM ATAPI-4 CD-Rom/DVD-Rom > (XEN) (GUEST: 46) ata1 slave: Unknown device > (XEN) (GUEST: 46) > (XEN) (GUEST: 46) Booting from CD-Rom...I see nothing wrong here.> > > (Note: in this case, I did reenable the harddisk image, but > even without it, > the output was similar). >[snip big xend.log]> > I noticed in there, there are two errors for the blockdevices: > DEBUG (blkif:24) exception looking up device number for hda: > [Errno 2] No such > file or directory: ''/dev/hda'' > and > DEBUG (blkif:24) exception looking up device number for hdc: > [Errno 2] No such > file or directory: ''/dev/hdc''I think this is when it''s trying to DESTROY the devices before restarting the guest - which isn''t, as you say, particularly critical.> > They don''t seem to be critical. > > For the rest, qemu-dm contintues to use 100% cpu on one core, > but nothing > happens. What is going on there ?Try doing a "gdb" and "attach nnnn" where nnnn is the process id fo the QEMU-DM that is running at 100%. I don''t guarantee that you''ll find anything useful, but I guess this will at least tell you where qemu-dm may be spending it''s time [this assumes you understand a bit about running gdb - if this doesn''t mean ANYTHING to you, then you''re probably not suited to try this]. Can you remind me which version of Xen this is? -- Mats> > Geert > > -- > Kobalt W.I.T. > Web & Information Technology > Brusselsesteenweg 152 > 1850 Grimbergen > > Tel : +32 479 339 655 > Email: info@kobaltwit.be > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Geert Janssens
2007-Jun-01 14:56 UTC
Re: [Xen-users] Re: Setup WinXP with HVM and qemu image
On Friday 1 June 2007 16:38, Petersson, Mats wrote:> > For the rest, qemu-dm contintues to use 100% cpu on one core, > > but nothing > > happens. What is going on there ? > > Try doing a "gdb" and "attach nnnn" where nnnn is the process id fo the > QEMU-DM that is running at 100%. I don''t guarantee that you''ll find > anything useful, but I guess this will at least tell you where qemu-dm > may be spending it''s time [this assumes you understand a bit about > running gdb - if this doesn''t mean ANYTHING to you, then you''re probably > not suited to try this]. >I have been doing some debugging in the past (it''s been a while though), so I''ll give it a shot, hopefully later this weekend.> Can you remind me which version of Xen this is? >3.0.3, the Red Hat edition (meaning 3.0.3 with custom patches applied by Red Hat) Thanks, Geert> -- > Mats > > > Geert > > > > -- > > Kobalt W.I.T. > > Web & Information Technology > > Brusselsesteenweg 152 > > 1850 Grimbergen > > > > Tel : +32 479 339 655 > > Email: info@kobaltwit.be > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users-- Kobalt W.I.T. Web & Information Technology Brusselsesteenweg 152 1850 Grimbergen Tel : +32 479 339 655 Email: info@kobaltwit.be _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Geert Janssens
2007-Sep-05 09:53 UTC
Re: [Xen-users] Re: Setup WinXP with HVM and qemu image
A very late follow-up on this old thread of mine (about a qemu-created WinXP setup that won''t boot in Xen HVM) for those who might get stuck in a similar situation. Because I couldn''t get it to work properly in Xen, I returned to qemu and continued to work with Qemu. After a few issues there, I finally discovered that my WinXP installation (and my qemu configuration) both were setup using acpi. I disabled acpi in WinXP and qemu, and my problems went away. I didn''t have time yet to try the same thing in xen, but I''m pretty sure this acpi thing was causing the original failure. To all that offered advice and suggestions: thanks and sorry for the wrong starting information. Regards, Geert -- Kobalt W.I.T. Web & Information Technology Brusselsesteenweg 152 1850 Grimbergen Tel : +32 479 339 655 Email: info@kobaltwit.be _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
David Morris
2007-Sep-05 20:03 UTC
RE: [Xen-users] Re: Setup WinXP with HVM and qemu image
Good conclusion ... same answer I found here: http://kbase.redhat.com/faq/FAQ_42_10986.shtm> -----Original Message----- > From: Geert Janssens [mailto:info@kobaltwit.be] > Sent: Wednesday, September 05, 2007 2:54 AM > To: xen-users@lists.xensource.com > Subject: Re: [Xen-users] Re: Setup WinXP with HVM and qemu image > > > A very late follow-up on this old thread of mine (about a > qemu-created WinXP > setup that won''t boot in Xen HVM) for those who might get > stuck in a similar > situation. > > Because I couldn''t get it to work properly in Xen, I returned > to qemu and > continued to work with Qemu. After a few issues there, I > finally discovered > that my WinXP installation (and my qemu configuration) both > were setup using > acpi. I disabled acpi in WinXP and qemu, and my problems went away. > > I didn''t have time yet to try the same thing in xen, but I''m > pretty sure this > acpi thing was causing the original failure. > > > To all that offered advice and suggestions: thanks and sorry > for the wrong > starting information. > > Regards, > > Geert >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
David Morris
2007-Sep-05 21:57 UTC
[Xen-users] 32bit domU on amd64 dom0, Xen 3.1, domU kernel panic
We are having a heck of a time trying to host 32 bit paravirtual guests on a
amd64 Xen host.
The base OS is debian/etch. We have upgraded Xen to 3.1 (as required to make
32bit guests work).
The 64bit host xen hypervisor (xen-3.1-1-amd64) and kernel (2.6.18-5-xen-amd64)
of course do not have pae enabled because it doesn''t apply to 64 bit
systems. The 32bit kernels we''ve tried (2.6.18-{4,5}-xen-686 are stock
debian and have pae enabled. We''re going to try a new kernel w/o pae as
the 32bit guest. Does that make sense, or is there another issue?
I''ve attached the kernel panic output .... I''ve tried with
both sda1/sda2 and hda1/hda2 devices ... the only obvious difference was the
panic call stack trace.
Dave Morris
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users