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] Re: Setup WinXP with HVM and qemu image

To: "Geert Janssens" <info@xxxxxxxxxxxx>
Subject: RE: [Xen-users] Re: Setup WinXP with HVM and qemu image
From: "Petersson, Mats" <Mats.Petersson@xxxxxxx>
Date: Fri, 1 Jun 2007 16:38:26 +0200
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 01 Jun 2007 07:37:54 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <200706011453.35728.info@xxxxxxxxxxxx>
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>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcekS+ryqsBXfXkYRrW/szsLAn+nAgADhu1w
Thread-topic: [Xen-users] Re: Setup WinXP with HVM and qemu image
> -----Original Message-----
> From: Geert Janssens [mailto:info@xxxxxxxxxxxx] 
> Sent: 01 June 2007 13:54
> To: Petersson, Mats
> Cc: xen-users@xxxxxxxxxxxxxxxxxxx
> 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@xxxxxxxxxxxx
> 
> 
> 



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