All of lore.kernel.org
 help / color / mirror / Atom feed
* RE: Minix as an HVM guest crashes
@ 2006-05-16 20:55 Petersson, Mats
  2006-05-16 21:29 ` Jonathan M. McCune
  0 siblings, 1 reply; 4+ messages in thread
From: Petersson, Mats @ 2006-05-16 20:55 UTC (permalink / raw)
  To: Jonathan M. McCune, xen-devel

Jon, 

Is Minix a 16-bit or 32-bit OS? If it's 16-bit, it's most likely the
cause of problems. There are a lot of places in Xen where it's assumed
that the base of a segment is zero unless in real-mode... 

Just a thought... 

--
Mats

> -----Original Message-----
> From: xen-devel-bounces@lists.xensource.com 
> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of 
> Petersson, Mats
> Sent: 16 May 2006 21:35
> To: Jonathan M. McCune; xen-devel@lists.xensource.com
> Subject: RE: [Xen-devel] Minix as an HVM guest crashes
> 
>  
> 
> > -----Original Message-----
> > From: xen-devel-bounces@lists.xensource.com
> > [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of 
> Jonathan 
> > M. McCune
> > Sent: 16 May 2006 21:09
> > To: xen-devel@lists.xensource.com
> > Subject: [Xen-devel] Minix as an HVM guest crashes
> > 
> > Hello Xen community,
> > 
> > I have tried to boot Minix 3.1.2 as an HVM guest on Xen 3.0.2 on a 
> > system with AMD SVM extensions, but it crashes.  I have 
> successfully 
> > booted Linux and Windows XP as HVM guests on this system.  I have 
> > included here the output of `xm dmesg` after attempting to boot the 
> > Minix domain.  Here is my minix.xm file:
> > 
> > kernel = "/usr/lib/xen/boot/hvmloader"
> > builder='hvm'
> > memory = 512
> > name = "Minix"
> > disk = [ 'file:/minix/disk.img,ioemu:hda,w' ] vif = [ 'type=ioemu, 
> > bridge=xenbr0' ] device_model = '/usr/lib/xen/bin/qemu-dm'
> > memmap = '/usr/lib/xen/boot/mem-map.sxp'
> > cdrom='/minix/IDE-3.1.2.iso'
> > boot='d'
> > sdl=1
> > vnc=0
> > 
> > 
> > The command I executed in dom0 to boot the minix.xm domain 
> > was `xm create -f minix.xm`.  The HVM guest window opens, and 
> > minix boots to the point where it asks whether I want to 
> > configure for "Large" or "Small" 
> > memory.  Regardless of my choice, the HVM guest window 
> > "blinks out of existence" shortly thereafter, and 
> > automatically restarts itself once, before crashing again in 
> > exactly the same way.  I chose Large both times.  This 
> > auto-restart behavior is why there are two guests in the `xm 
> > dmesg` output below:
> > 
> > Does anybody know why it crashes?  Is this a Minix bug? Xen bug?  
> > Admittedly, I haven't tried the latest xen-unstable yet, so 
> > perhaps the issue is already solved.
> > 
> > Thanks,
> > -Jon
> > 
> > 
> This is a typical dump of a unimplemented opcode in hvm/platform.c. 
> 
> I'm not quite sure which opcode it's trying to execute, but I'm sure
> this is why it's failing. I'm also confused as to the base address of
> the instruction, because the 31A7 instruction is a "add $10, %esp",
> which shouldn't be page-faulting. One possibility is that the base of
> the CS register isn't zero, in which case the dump of the instruction
> bytes is bogus... 
> 
> I doubt that the Latest Xen will fix anything.
> 
> --
> Mats
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 
> 

^ permalink raw reply	[flat|nested] 4+ messages in thread
* RE: Minix as an HVM guest crashes
@ 2006-05-16 20:34 Petersson, Mats
  0 siblings, 0 replies; 4+ messages in thread
From: Petersson, Mats @ 2006-05-16 20:34 UTC (permalink / raw)
  To: Jonathan M. McCune, xen-devel

 

> -----Original Message-----
> From: xen-devel-bounces@lists.xensource.com 
> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of 
> Jonathan M. McCune
> Sent: 16 May 2006 21:09
> To: xen-devel@lists.xensource.com
> Subject: [Xen-devel] Minix as an HVM guest crashes
> 
> Hello Xen community,
> 
> I have tried to boot Minix 3.1.2 as an HVM guest on Xen 3.0.2 
> on a system with AMD SVM extensions, but it crashes.  I have 
> successfully booted Linux and Windows XP as HVM guests on 
> this system.  I have included here the output of `xm dmesg` 
> after attempting to boot the Minix domain.  Here is my minix.xm file:
> 
> kernel = "/usr/lib/xen/boot/hvmloader"
> builder='hvm'
> memory = 512
> name = "Minix"
> disk = [ 'file:/minix/disk.img,ioemu:hda,w' ] vif = [ 
> 'type=ioemu, bridge=xenbr0' ] device_model = 
> '/usr/lib/xen/bin/qemu-dm'
> memmap = '/usr/lib/xen/boot/mem-map.sxp'
> cdrom='/minix/IDE-3.1.2.iso'
> boot='d'
> sdl=1
> vnc=0
> 
> 
> The command I executed in dom0 to boot the minix.xm domain 
> was `xm create -f minix.xm`.  The HVM guest window opens, and 
> minix boots to the point where it asks whether I want to 
> configure for "Large" or "Small" 
> memory.  Regardless of my choice, the HVM guest window 
> "blinks out of existence" shortly thereafter, and 
> automatically restarts itself once, before crashing again in 
> exactly the same way.  I chose Large both times.  This 
> auto-restart behavior is why there are two guests in the `xm 
> dmesg` output below:
> 
> Does anybody know why it crashes?  Is this a Minix bug? Xen bug?  
> Admittedly, I haven't tried the latest xen-unstable yet, so 
> perhaps the issue is already solved.
> 
> Thanks,
> -Jon
> 
> 
This is a typical dump of a unimplemented opcode in hvm/platform.c. 

I'm not quite sure which opcode it's trying to execute, but I'm sure
this is why it's failing. I'm also confused as to the base address of
the instruction, because the 31A7 instruction is a "add $10, %esp",
which shouldn't be page-faulting. One possibility is that the base of
the CS register isn't zero, in which case the dump of the instruction
bytes is bogus... 

I doubt that the Latest Xen will fix anything.

--
Mats

^ permalink raw reply	[flat|nested] 4+ messages in thread
* Minix as an HVM guest crashes
@ 2006-05-16 20:09 Jonathan M. McCune
  0 siblings, 0 replies; 4+ messages in thread
From: Jonathan M. McCune @ 2006-05-16 20:09 UTC (permalink / raw)
  To: xen-devel

Hello Xen community,

I have tried to boot Minix 3.1.2 as an HVM guest on Xen 3.0.2 on a 
system with AMD SVM extensions, but it crashes.  I have successfully 
booted Linux and Windows XP as HVM guests on this system.  I have 
included here the output of `xm dmesg` after attempting to boot the 
Minix domain.  Here is my minix.xm file:

kernel = "/usr/lib/xen/boot/hvmloader"
builder='hvm'
memory = 512
name = "Minix"
disk = [ 'file:/minix/disk.img,ioemu:hda,w' ]
vif = [ 'type=ioemu, bridge=xenbr0' ]
device_model = '/usr/lib/xen/bin/qemu-dm'
memmap = '/usr/lib/xen/boot/mem-map.sxp'
cdrom='/minix/IDE-3.1.2.iso'
boot='d'
sdl=1
vnc=0


The command I executed in dom0 to boot the minix.xm domain was `xm 
create -f minix.xm`.  The HVM guest window opens, and minix boots to the 
point where it asks whether I want to configure for "Large" or "Small" 
memory.  Regardless of my choice, the HVM guest window "blinks out of 
existence" shortly thereafter, and automatically restarts itself once, 
before crashing again in exactly the same way.  I chose Large both 
times.  This auto-restart behavior is why there are two guests in the 
`xm dmesg` output below:

Does anybody know why it crashes?  Is this a Minix bug? Xen bug?  
Admittedly, I haven't tried the latest xen-unstable yet, so perhaps the 
issue is already solved.

Thanks,
-Jon


 __  __            _____  ___   ____  
 \ \/ /___ _ __   |___ / / _ \ |___ \ 
  \  // _ \ '_ \    |_ \| | | |  __) |
  /  \  __/ | | |  ___) | |_| | / __/ 
 /_/\_\___|_| |_| |____(_)___(_)_____|
                                      
 http://www.cl.cam.ac.uk/netos/xen
 University of Cambridge Computer Laboratory

 Xen version 3.0.2 (root@ece.cmu.edu) (gcc version 4.0.3 20051201 (prerelease) (Debian 4.0.2-5)) Mon Apr 17 16:42:06 EDT 2006
 Latest ChangeSet: Sat Apr  8 12:14:27 2006 +0100 9598:1bce05ff1e52

(XEN) Console output is synchronous.
(XEN) Physical RAM map:
(XEN)  0000000000000000 - 000000000009e000 (usable)
(XEN)  000000000009e000 - 00000000000a0000 (reserved)
(XEN)  00000000000d0000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 0000000097e80000 (usable)
(XEN)  0000000097e80000 - 0000000097e89000 (ACPI data)
(XEN)  0000000097e89000 - 0000000097f00000 (ACPI NVS)
(XEN)  0000000097f00000 - 00000000a0000000 (reserved)
(XEN)  00000000e0000000 - 00000000f0000000 (reserved)
(XEN)  00000000fec00000 - 00000000fec10000 (reserved)
(XEN)  00000000fff80000 - 0000000100000000 (reserved)
(XEN) System RAM: 2430MB (2488440kB)
(XEN) Xen heap: 10MB (10544kB)
(XEN) Using scheduler: Simple EDF Scheduler (sedf)
(XEN) PAE disabled.
(XEN) found SMP MP-table at 000f6f80
(XEN) DMI present.
(XEN) Using APIC driver default
(XEN) ACPI: RSDP (v000 PTLTD                                 ) @ 0x000f6f50
(XEN) ACPI: RSDT (v001 PTLTD    RSDT   0x06040000  LTP 0x00000000) @ 0x97e83356
(XEN) ACPI: FADT (v001 ATI    Piranha  0x06040000 ATI  0x000f4240) @ 0x97e88c56
(XEN) ACPI: TCPA (v002 AMD             0x06040000 PTEC 0x00000000) @ 0x97e88cca
(XEN) ACPI: SSDT (v001 PTLTD  POWERNOW 0x06040000  LTP 0x00000001) @ 0x97e88cfc
(XEN) ACPI: MADT (v001 PTLTD  	 APIC   0x06040000  LTP 0x00000000) @ 0x97e88f08
(XEN) ACPI: MADT (v001 PTLTD  	 APIC   0x06040000  LTP 0x00000000) @ 0x97e88f66
(XEN) ACPI: MCFG (v001 PTLTD    MCFG   0x06040000  LTP 0x00000000) @ 0x97e88fc4
(XEN) ACPI: DSDT (v001    ATI    SB400 0x06040000 MSFT 0x0100000e) @ 0x00000000
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: 2 duplicate APIC table ignored.
(XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
(XEN) Processor #0 15:3 APIC version 16
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
(XEN) Processor #1 15:3 APIC version 16
(XEN) ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
(XEN) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 2, version 33, address 0xfec00000, GSI 0-23
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 21 low level)
(XEN) ACPI: IRQ9 used by override.
(XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) Initializing CPU#0
(XEN) Detected 2387.844 MHz processor.
(XEN) CPU0: AMD Flush Filter disabled
(XEN) CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
(XEN) CPU: L2 Cache: 1024K (64 bytes/line)
(XEN) CPU 0(2) -> Core 0
(XEN) AMD SVM Extension is enabled for cpu 0.
(XEN) Intel machine check architecture supported.
(XEN) Intel machine check reporting enabled on CPU#0.
(XEN) CPU0: AMD Engineering Sample stepping 01
(XEN) Booting processor 1/1 eip 90000
(XEN) Initializing CPU#1
(XEN) CPU1: AMD Flush Filter disabled
(XEN) CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
(XEN) CPU: L2 Cache: 1024K (64 bytes/line)
(XEN) CPU 1(2) -> Core 1
(XEN) AMD: Disabling C1 Clock Ramping Node #0
(XEN) AMD SVM Extension is enabled for cpu 1.
(XEN) Intel machine check architecture supported.
(XEN) Intel machine check reporting enabled on CPU#1.
(XEN) CPU1: AMD Engineering Sample stepping 01
(XEN) Total of 2 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN) ..TIMER: vector=0x31 apic1=0 pin1=0 apic2=-1 pin2=-1
(XEN) checking TSC synchronization across 2 CPUs: 
(XEN) CPU#0 had 0 usecs TSC skew, fixed it up.
(XEN) CPU#1 had 0 usecs TSC skew, fixed it up.
(XEN) Platform timer is 1.193MHz PIT
(XEN) Brought up 2 CPUs
(XEN) Machine check exception polling timer started.
(XEN) Using IPI Shortcut mode
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Domain 0 kernel supports features = { 0000001f }.
(XEN) Domain 0 kernel requires features = { 00000000 }.
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN)  Dom0 alloc.:   02800000->03000000 (260096 pages to be allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN)  Loaded kernel: c0100000->c043d394
(XEN)  Init. ramdisk: c043e000->c064b800
(XEN)  Phys-Mach map: c064c000->c074c000
(XEN)  Start info:    c074c000->c074d000
(XEN)  Page tables:   c074d000->c0750000
(XEN)  Boot stack:    c0750000->c0751000
(XEN)  TOTAL:         c0000000->c0800000
(XEN)  ENTRY ADDRESS: c0100000
(XEN) Dom0 has maximum 2 VCPUs
(XEN) Initrd len 0x20d800, start at 0xc043e000
(XEN) Scrubbing Free RAM: .........................done.
(XEN) Xen trace buffers: disabled
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen).
(XEN) (GUEST: 1) HVM Loader
(XEN) (GUEST: 1) Loading ROMBIOS ...
(XEN) (GUEST: 1) Loading Cirrus VGABIOS ...
(XEN) (GUEST: 1) SVM go ...
(XEN) (GUEST: 1)  rombios.c,v 1.138 2005/05/07 15:55:26 vruppert Exp $
(XEN) HVM_PIT: guest freq in cycles=119392099
(XEN) (GUEST: 1) VGABios $Id: vgabios.c,v 1.61 2005/05/24 16:50:50 vruppert Exp $
(XEN) (GUEST: 1) HVMAssist BIOS, 1 cpu, $Revision: 1.138 $ $Date: 2005/05/07 15:55:26 $
(XEN) (GUEST: 1) 
(XEN) (GUEST: 1) ata0-0: PCHS=4096/16/63 translation=lba LCHS=1024/64/63
(XEN) (GUEST: 1) ata0 master: QEMU HARDDISK ATA-2 Hard-Disk (2016 MBytes)
(XEN) (GUEST: 1) ata0  slave: Unknown device
(XEN) (GUEST: 1) ata1 master: QEMU CD-ROM ATAPI-4 CD-Rom/DVD-Rom
(XEN) (GUEST: 1) ata1  slave: Unknown device
(XEN) (GUEST: 1) 
(XEN) (GUEST: 1) Booting from CD-Rom...
(XEN) Code bytes around(len=256) 607038:
(XEN) 00607000:31 ed 8b 04 24 8d 54 24 04 8d 4c 84 08 bb 30 16 
(XEN) 00607010:00 00 81 fb 40 16 00 00 73 13 f6 c3 03 75 0e 81 
(XEN) 00607020:3b 53 53 53 53 75 06 89 1d a8 0e 00 00 8b 1d a8 
(XEN) 00607030:0e 00 00 89 0b 51 52 50 0f 01 e0 a8 04 0f 94 05 
(XEN) 00607040:50 3d 00 00 e8 07 00 00 00 50 e8 1e 67 00 00 f4 
(XEN) 00607050:55 89 e5 83 ec 3c 56 57 6a 00 6a 00 6a 00 68 58 
(XEN) 00607060:3d 00 00 6a 0c e8 8e 5e 00 00 83 c4 14 89 45 d0 
(XEN) 00607070:85 c0 74 15 ff 75 d0 68 34 01 00 00 68 58 01 00 
(XEN) 00607080:00 e8 ba 5d 00 00 83 c4 0c e8 1c 17 00 00 e8 59 
(XEN) 00607090:40 00 00 68 30 01 00 00 e8 bf 61 00 00 59 be 70 
(XEN) 006070a0:3d 00 00 81 fe 30 af 00 00 73 14 83 3e 00 74 07 
(XEN) 006070b0:56 e8 c8 0b 00 00 59 81 c6 d8 02 00 00 eb e4 8d 
(XEN) 006070c0:45 dc 50 68 ce 7a 00 00 e8 e7 66 00 00 59 59 89 
(XEN) 006070d0:45 d4 85 c0 0f 84 cc 00 00 00 ff 75 d4 68 14 01 
(XEN) 006070e0:00 00 68 2c 01 00 00 e8 54 5d 00 00 83 c4 0c e9 
(XEN) 006070f0:b2 00 00 00 e8 94 17 00 00 eb a3 ff 75 dc e8 d9 
(XEN) Code bytes around(len=256) 31a9:
(XEN) 00003100:be 5e 79 39 d8 7e 31 0f b7 56 74 85 d2 75 07 56 
(XEN) 00003110:e8 99 fe ff ff 59 0f be 46 7b 01 c7 0f be 46 78 
(XEN) 00003120:48 0f be c0 88 46 78 0f b7 56 74 85 d2 75 1d 56 
(XEN) 00003130:e8 e6 fd ff ff 59 eb 14 0f be 46 7b 0f be 5e 7a 
(XEN) 00003140:29 c3 f7 db 01 df 8a 4e 7b 88 4e 7a e8 3d 3a 00 
(XEN) 00003150:00 81 c6 d0 00 00 00 eb 82 83 ff 64 7d 07 b8 64 
(XEN) 00003160:00 00 00 eb 02 89 f8 89 45 f8 68 cc 20 00 00 e8 
(XEN) 00003170:3c 0f 00 00 03 45 f8 50 68 14 15 00 00 e8 38 0f 
(XEN) 00003180:00 00 83 c4 0c 5f 5e c9 c3 55 89 e5 83 ec 04 e8 
(XEN) 00003190:f8 39 00 00 6a 10 ff 75 0c ff 75 08 ff 35 04 2c 
(XEN) 000031a0:00 00 e8 ca f7 ff ff 83 c4 10 89 45 fc e8 dc 39 
(XEN) 000031b0:00 00 8b 45 fc c9 c3 55 89 e5 e8 cd 39 00 00 ff 
(XEN) 000031c0:75 08 e8 54 fd ff ff 59 e8 c1 39 00 00 c9 c3 55 
(XEN) 000031d0:89 e5 0f be 05 94 2c 00 00 85 c0 78 0b ff 75 08 
(XEN) 000031e0:e8 c9 fd ff ff 59 eb 13 e8 9f 39 00 00 ff 75 08 
(XEN) 000031f0:e8 b9 fd ff ff 59 e8 93 39 00 00 c9 c3 55 89 e5 
(XEN) handle_mmio: failed to get instruction length
(XEN) domain_crash_sync called from platform.c:788
(XEN) Domain 1 (vcpu#0) crashed on cpu#1:
(XEN) ----[ Xen-3.0.2    Not tainted ]----
(XEN) CPU:    1
(XEN) EIP:    0007:[<000031a7>]
(XEN) EFLAGS: 00000246   CONTEXT: hvm
(XEN) eax: 00000700   ebx: 00000000   ecx: 00000050   edx: 00000000
(XEN) esi: 00000000   edi: 00000fa0   ebp: 0000df14   esp: 0000df08
(XEN) cr0: 80000019   cr3: 75bbd000
(XEN) ds: 000f   es: 0017   fs: 000f   gs: 000f   ss: 000f   cs: 0007
(XEN) (GUEST: 2) HVM Loader
(XEN) (GUEST: 2) Loading ROMBIOS ...
(XEN) (GUEST: 2) Loading Cirrus VGABIOS ...
(XEN) (GUEST: 2) SVM go ...
(XEN) (GUEST: 2)  rombios.c,v 1.138 2005/05/07 15:55:26 vruppert Exp $
(XEN) HVM_PIT: guest freq in cycles=119392099
(XEN) (GUEST: 2) VGABios $Id: vgabios.c,v 1.61 2005/05/24 16:50:50 vruppert Exp $
(XEN) (GUEST: 2) HVMAssist BIOS, 1 cpu, $Revision: 1.138 $ $Date: 2005/05/07 15:55:26 $
(XEN) (GUEST: 2) 
(XEN) (GUEST: 2) ata0-0: PCHS=4096/16/63 translation=lba LCHS=1024/64/63
(XEN) (GUEST: 2) ata0 master: QEMU HARDDISK ATA-2 Hard-Disk (2016 MBytes)
(XEN) (GUEST: 2) ata0  slave: Unknown device
(XEN) (GUEST: 2) ata1 master: QEMU CD-ROM ATAPI-4 CD-Rom/DVD-Rom
(XEN) (GUEST: 2) ata1  slave: Unknown device
(XEN) (GUEST: 2) 
(XEN) (GUEST: 2) Booting from CD-Rom...
(XEN) Code bytes around(len=256) 607038:
(XEN) 00607000:31 ed 8b 04 24 8d 54 24 04 8d 4c 84 08 bb 30 16 
(XEN) 00607010:00 00 81 fb 40 16 00 00 73 13 f6 c3 03 75 0e 81 
(XEN) 00607020:3b 53 53 53 53 75 06 89 1d a8 0e 00 00 8b 1d a8 
(XEN) 00607030:0e 00 00 89 0b 51 52 50 0f 01 e0 a8 04 0f 94 05 
(XEN) 00607040:50 3d 00 00 e8 07 00 00 00 50 e8 1e 67 00 00 f4 
(XEN) 00607050:55 89 e5 83 ec 3c 56 57 6a 00 6a 00 6a 00 68 58 
(XEN) 00607060:3d 00 00 6a 0c e8 8e 5e 00 00 83 c4 14 89 45 d0 
(XEN) 00607070:85 c0 74 15 ff 75 d0 68 34 01 00 00 68 58 01 00 
(XEN) 00607080:00 e8 ba 5d 00 00 83 c4 0c e8 1c 17 00 00 e8 59 
(XEN) 00607090:40 00 00 68 30 01 00 00 e8 bf 61 00 00 59 be 70 
(XEN) 006070a0:3d 00 00 81 fe 30 af 00 00 73 14 83 3e 00 74 07 
(XEN) 006070b0:56 e8 c8 0b 00 00 59 81 c6 d8 02 00 00 eb e4 8d 
(XEN) 006070c0:45 dc 50 68 ce 7a 00 00 e8 e7 66 00 00 59 59 89 
(XEN) 006070d0:45 d4 85 c0 0f 84 cc 00 00 00 ff 75 d4 68 14 01 
(XEN) 006070e0:00 00 68 2c 01 00 00 e8 54 5d 00 00 83 c4 0c e9 
(XEN) 006070f0:b2 00 00 00 e8 94 17 00 00 eb a3 ff 75 dc e8 d9 
(XEN) Code bytes around(len=256) 31a9:
(XEN) 00003100:be 5e 79 39 d8 7e 31 0f b7 56 74 85 d2 75 07 56 
(XEN) 00003110:e8 99 fe ff ff 59 0f be 46 7b 01 c7 0f be 46 78 
(XEN) 00003120:48 0f be c0 88 46 78 0f b7 56 74 85 d2 75 1d 56 
(XEN) 00003130:e8 e6 fd ff ff 59 eb 14 0f be 46 7b 0f be 5e 7a 
(XEN) 00003140:29 c3 f7 db 01 df 8a 4e 7b 88 4e 7a e8 3d 3a 00 
(XEN) 00003150:00 81 c6 d0 00 00 00 eb 82 83 ff 64 7d 07 b8 64 
(XEN) 00003160:00 00 00 eb 02 89 f8 89 45 f8 68 cc 20 00 00 e8 
(XEN) 00003170:3c 0f 00 00 03 45 f8 50 68 14 15 00 00 e8 38 0f 
(XEN) 00003180:00 00 83 c4 0c 5f 5e c9 c3 55 89 e5 83 ec 04 e8 
(XEN) 00003190:f8 39 00 00 6a 10 ff 75 0c ff 75 08 ff 35 04 2c 
(XEN) 000031a0:00 00 e8 ca f7 ff ff 83 c4 10 89 45 fc e8 dc 39 
(XEN) 000031b0:00 00 8b 45 fc c9 c3 55 89 e5 e8 cd 39 00 00 ff 
(XEN) 000031c0:75 08 e8 54 fd ff ff 59 e8 c1 39 00 00 c9 c3 55 
(XEN) 000031d0:89 e5 0f be 05 94 2c 00 00 85 c0 78 0b ff 75 08 
(XEN) 000031e0:e8 c9 fd ff ff 59 eb 13 e8 9f 39 00 00 ff 75 08 
(XEN) 000031f0:e8 b9 fd ff ff 59 e8 93 39 00 00 c9 c3 55 89 e5 
(XEN) handle_mmio: failed to get instruction length
(XEN) domain_crash_sync called from platform.c:788
(XEN) Domain 2 (vcpu#0) crashed on cpu#0:
(XEN) ----[ Xen-3.0.2    Not tainted ]----
(XEN) CPU:    0
(XEN) EIP:    0007:[<000031a7>]
(XEN) EFLAGS: 00000246   CONTEXT: hvm
(XEN) eax: 00000700   ebx: 00000000   ecx: 00000050   edx: 00000000
(XEN) esi: 00000000   edi: 00000fa0   ebp: 0000df14   esp: 0000df08
(XEN) cr0: 80000019   cr3: 557bd000
(XEN) ds: 000f   es: 0017   fs: 000f   gs: 000f   ss: 000f   cs: 0007

^ permalink raw reply	[flat|nested] 4+ messages in thread
end of thread, other threads:[~2006-05-16 21:29 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-05-16 20:55 Minix as an HVM guest crashes Petersson, Mats
2006-05-16 21:29 ` Jonathan M. McCune
  -- strict thread matches above, loose matches on Subject: below --
2006-05-16 20:34 Petersson, Mats
2006-05-16 20:09 Jonathan M. McCune

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.