[Xen-bugs] [Bug 728] New: cannot boot multipleVMX guests

[bugzilla-daemon@xxxxxxxxxxxxxxxxxxx]

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=728

           Summary: cannot boot multipleVMX guests
           Product: Xen
           Version: unstable
          Platform: x86-64
        OS/Version: Linux-2.6
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HVM
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: krysans@xxxxxxxxxx


I am running Xen unstable changeset 10949 on Unisys ES7000/one with VT, x86_64,
with 16 processors and 64 GB RAM.  I can successfully boot one vmx guest at a
time.  I have booted rhel4u3 x86_64 and I have also booted winXP.  However,
when I have one vmx booted and attempt to boot a second one, the system
crashes. 

Here is the tail serial console output when the rhel4u3 vmx is booted and I
attempt to boot xinXP:
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 000000000000000c ffff830000f0c080
(XEN) Xen call trace:
(XEN)    [<ffff83000013be35>] free_shadow_page+0x165/0xba0
(XEN)    [<ffff83000013d34f>] free_shadow_pages+0x23f/0x2d0
(XEN)    [<ffff83000013d434>] clear_all_shadow_status+0x54/0xe0
(XEN)    [<ffff8300001636ed>] vmx_set_cr0+0x6ad/0x8a0
(XEN)    [<ffff83000016536b>] vmx_vmexit_handler+0xa1b/0x1480
(XEN)    [<ffff83000015efd8>] vmx_intr_assist+0xa8/0x440
(XEN)    [<ffff830000115135>] do_softirq+0x55/0x70
(XEN)    [<ffff830000165df5>] vmx_asm_vmexit_handler+0x25/0x30
(XEN)
(XEN) Pagetable walk from 0000000000000000:
(XEN)  L4 = 0000000000000000 ffffffffffffffff
(XEN)
(XEN) ****************************************
(XEN) Panic on CPU 12:
(XEN) CPU12 FATAL PAGE FAULT
(XEN) [error_code=0000]
(XEN) Faulting linear address: 0000000000000000
(XEN) ****************************************
(XEN)
(XEN) Reboot in five seconds...

Here is the tail serial console output when the winxp vmx is booted and I
attempt to boot win2003:
(XEN)    0000000000100000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000feffd0 0000000000feffd8 0000000000feffe0
(XEN)    0000000000feffe8 0000000000000003 ffff830000ef8080
(XEN) Xen call trace:
(XEN)    [<ffff83000013be35>] free_shadow_page+0x165/0xba0
(XEN)    [<ffff83000013d34f>] free_shadow_pages+0x23f/0x2d0
(XEN)    [<ffff83000013d434>] clear_all_shadow_status+0x54/0xe0
(XEN)    [<ffff8300001636ed>] vmx_set_cr0+0x6ad/0x8a0
(XEN)    [<ffff83000016536b>] vmx_vmexit_handler+0xa1b/0x1480
(XEN)    [<ffff83000015efd8>] vmx_intr_assist+0xa8/0x440
(XEN)    [<ffff830000165df5>] vmx_asm_vmexit_handler+0x25/0x30
(XEN)
(XEN) Pagetable walk from 0000000000000000:
(XEN)  L4 = 0000000000000000 ffffffffffffffff
(XEN)
(XEN) ****************************************
(XEN) Panic on CPU 3:
(XEN) CPU3 FATAL PAGE FAULT
(XEN) [error_code=0000]
(XEN) Faulting linear address: 0000000000000000
(XEN) ****************************************
(XEN)
(XEN) Reboot in five seconds...


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