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

[Xen-bugs] [Bug 1259] New: booting windows guest causes Xen HV crash

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 1259] New: booting windows guest causes Xen HV crash
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Thu, 22 May 2008 02:50:26 -0700
Delivery-date: Thu, 22 May 2008 02:50:41 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1259

           Summary: booting windows guest causes Xen HV crash
           Product: Xen
           Version: unstable
          Platform: All
        OS/Version: Windows
            Status: NEW
          Severity: blocker
          Priority: P1
         Component: Hypervisor
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: haicheng.li@xxxxxxxxx


paste serial log here:

(XEN) HVM4: Press F10 to select boot device.
(XEN) HVM4: Booting from Hard Disk...
(XEN) HVM4: unsupported PCI BIOS function 0x0E
(XEN) HVM4: int13_harddisk: function 15, unmapped device for ELDL=81
(XEN) HVM4: *** int 15h function AX=E980, BX=0082 not yet supported!
(XEN) vlapic.c:604:d4 Notice: Local APIC write with len = 1
(XEN) vlapic.c:727:d4 Local APIC Write to read-only register 0x30
(XEN) irq.c:235: Dom4 PCI link 0 changed 5 -> 0
(XEN) irq.c:235: Dom4 PCI link 1 changed 10 -> 0
(XEN) irq.c:235: Dom4 PCI link 2 changed 11 -> 0
(XEN) irq.c:235: Dom4 PCI link 3 changed 5 -> 0
(XEN) ----[ Xen-3.3-unstable  x86_32p  debug=n  Not tainted ]----
(XEN) CPU:    4
(XEN) EIP:    e008:[<ff17b76d>] sh_remove_all_mappings+0x2d/0x1a0
(XEN) EFLAGS: 00210287   CONTEXT: hypervisor
(XEN) eax: 00000000   ebx: f67fffe8   ecx: 26b00000   edx: ffffffff
(XEN) esi: 00000025   edi: ff1c2080   ebp: ffbb7080   esp: ff1dfe7c
(XEN) cr0: 8005003b   cr4: 000026f0   cr3: 00bc8c80   cr2: f67ffff0
(XEN) ds: e010   es: e010   fs: 0000   gs: 0033   ss: e010   cs: e008
(XEN) Xen stack trace from esp=ff1dfe7c:
(XEN)    00000000 fa000000 00000000 ff179c4e feda4e80 00000004 ff1164b7
000fa001
(XEN)    00000025 ff1c2080 000fa025 ff17dda4 ffbb7080 ffffffff ff1dff20
ff136e56
(XEN)    f984c050 ffbde080 00000004 ff1cb428 00000020 ffbc8c80 ffbc8cc8
ffbde080
(XEN)    bfa34750 00000000 00000000 00000000 00000005 00000000 ff13894a
f97db490
(XEN)    001fe786 000f002c 0000000f ff1c2bf0 b7d3f3f3 00000004 fed2e030
00000030
(XEN)    ffbde080 00000004 f97db490 ffbb7080 00000006 00000000 00305000
ff160444
(XEN)    ff1c2080 000fa000 00000025 bfa34750 00000000 ff1cf020 fa000004
ffffffff
(XEN)    000fa000 00000000 00000025 00000000 bfa34750 00000000 00000020
002032ae
(XEN)    ff1dffb4 ff1cf024 00000002 ffbc8080 0000007b 0000007b 00305000
ff18d824
(XEN)    00000006 bfa34700 b7485000 00000000 00000000 00305000 00000006
bfa34700
(XEN)    b7485000 00000000 00000000 00305000 00000022 00fc0000 c0101447
00000061
(XEN)    00200282 e1ac7ec4 00000069 0000007b 0000007b 00000000 00000033
00000004
(XEN)    ffbc8080
(XEN) Xen call trace:
(XEN)    [<ff17b76d>] sh_remove_all_mappings+0x2d/0x1a0
(XEN)    [<ff179c4e>] p2m_gfn_to_mfn+0xde/0x1e0
(XEN)    [<ff1164b7>] add_entry+0x57/0x140
(XEN)    [<ff1c2080>] acpi_numa_memory_affinity_init+0x130/0x3d0
(XEN)    [<ff17dda4>] shadow_track_dirty_vram+0x674/0x9a0
(XEN)    [<ff136e56>] get_page_from_pagenr+0x26/0x70
(XEN)    [<ff13894a>] do_update_descriptor+0x1ea/0x240
(XEN)    [<ff1c2bf0>] disable_acpi_irq+0x30/0x40
(XEN)    [<ff160444>] do_hvm_op+0x174/0xbe0
(XEN)    [<ff1c2080>] acpi_numa_memory_affinity_init+0x130/0x3d0
(XEN)    [<ff18d824>] tracing_off+0x7/0xe
(XEN)    
(XEN) Pagetable walk from f67ffff0:
(XEN)  L3[0x003] = 000000020658f001 0002598f
(XEN)  L2[0x1b3] = 0000000000000000 ffffffff 
(XEN) 
(XEN) ****************************************
(XEN) Panic on CPU 4:
(XEN) FATAL PAGE FAULT
(XEN) [error_code=0000]
(XEN) Faulting linear address: f67ffff0
(XEN) ****************************************
(XEN) 
(XEN) Reboot in five seconds...

------- Comment #1 From Zhang, Li 2008-05-22 16:16:53 ------- 
   This bug is caused by cs #17693. I am looking into it.


-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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

<Prev in Thread] Current Thread [Next in Thread>