Yes, as Mats indicated, we are running VT on Unisys/one with SLES10RC2.5
updated to unstable changeset 10641.
We also cannot boot a Darn :) Small Linux VMX and qemu-dm.xxx.log shows:
Booting from CD-Rom...
Trap (0x6) while in real mode
eax 10CFDD ecx FF5F edx 3C5 ebx D5090002
esp D6A94 ebp D0250 esi 4038 edi D6A96477
eip 9978 eflags 33006 cs F000 ds 0
es 0 fs 0 uss 0 uesp 7A46
ves B800 vds 0 vfs F000 vgs F000
trapno 6 errno 0
cr0 50032 cr2 0 cr3 0 cr4 651
Halt called from %eip 0xD0382
I opened xensource bug #698.
> Thanks,
> Sue Krysan
> Linux Systems Group
> Unisys Corporation
>
-----Original Message-----
From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx]On Behalf Of Petersson,
Mats
Sent: Friday, July 07, 2006 4:23 AM
To: jimm@xxxxxxxxxxxxxxx; xen-users@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-users] can't create WinXP or Win2003 VMX
> -----Original Message-----
> From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
> [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of
> James Miller
> Sent: 06 July 2006 23:13
> To: xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: RE: [Xen-users] can't create WinXP or Win2003 VMX
>
> > -----Original Message-----
> > From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
> > [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx]On Behalf Of
> Krysan, Susan
> > Sent: Thursday, July 06, 2006 4:29 PM
> > To: xen-users@xxxxxxxxxxxxxxxxxxx
> > Subject: [Xen-users] can't create WinXP or Win2003 VMX
> >
> >
> > When I try to create WinXP or Win2003 VMX, the boot hangs.
> > Running on x86_64 with changeset 10641.
> >
> > qemu-dm.xxx.log shows:
> >
> > Booting from CD-Rom...
> > should never reach here in function address():
> > entry=0x0000000000000000, mode=1, seg=0x000022F3,
> > offset=0x000014F8
This error-message comes from vmxassist/vm86.c, line 85 (in the current
version). I can't really say what causes it tho' (other than obviously
that it wasn't meant to happen). It is possibly caused by confusion
between the modes, since Intel hasn't got "paged realmode", they have to
use virtual 8086 mode to run real-mode, which causes some problems when
it comes to mixing real-mode and protected mode... It's most likely
fixable, but it would be necessary to figure out why it happens first,
and I'm not THAT familiar with either the code in vm86.c or the
boot-loader of Windows to know what's going on at this point, even to
have a guess (other than my assumptions above - which may of course be
wrong!!).
> >
> > Halt called from %eip 0xD3AAA
> >
>
> I don't recognize the error and I'm not expert (yet). But it would be
> helpful to know:
> 1. Which version of Xen are you using? I have had success
> with pulling
> xen-unstable.tar.gz and updating with mercurial.
> 2. Which Linux distribution are you use? I've had success with FC5
> 3. What hardware are you using? Does both the motherboard
> and CPU(s) have
> VT support?
The other questions are good, but: Supposedly, if they didn't, there
wouldn't be an error-message from QEMU, as QEMU wouldn't be started if
the there's no HVM-capable processor in the system - "xm create" will
error out long before it gets to QEMU.
--
Mats
> 4. What does your configuration file look like?
>
>
>
>
> --Jim
>
>
>
>
>
>
> _______________________________________________
> 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
|
Home