From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stefan Kaltenbrunner Subject: Re: VMX status report 10680:f692a0a476c5 Date: Fri, 14 Jul 2006 18:01:32 +0200 Message-ID: <44B7BFDC.3000508@kaltenbrunner.cc> References: <096FBD6A74E0CF4B9E0AB042EA18F59C43187E@pdsmsx412.ccr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <096FBD6A74E0CF4B9E0AB042EA18F59C43187E@pdsmsx412.ccr.corp.intel.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Zheng, Jeff" Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Zheng, Jeff wrote: > > We have tested the latest xen on VT platform with Intel 915/E8500 > chipset. > > > Here is the test summary: > > > Issues: > > - Cannot boot Four VMX at same time on IA32 host > - Cannot boot Windows XP SP1/SP2 on IA32e host > - Create IA32-PAE VMX on IA32e host will make VMX kernel panic > - Create IA32 VMX on IA32e host will make VMX hang > - Destroying VMX with 4G memory may make xend hang on IA-32e FYI: on my Pentium D920 box with a 64bit hypervisor WinXP SP2 is broken on -unstable for a while now: (XEN) ff, This opcode isn't handled yet! (XEN) handle_mmio: failed to decode instruction (XEN) mmio opcode: va 0xb8216, gpa 0xb8216, len 3: ff 77 16 (XEN) domain_crash_sync called from platform.c:857 (XEN) Domain 6 (vcpu#0) crashed on cpu#0: (XEN) ----[ Xen-3.0-unstable Not tainted ]---- (XEN) CPU: 0 (XEN) RIP: c000:[<0000000000003c09>] (XEN) RFLAGS: 0000000000033006 CONTEXT: hvm (XEN) rax: 00000000000f0060 rbx: 0000000000000200 rcx: 00000000000f0005 (XEN) rdx: 0000000000000000 rsi: 0000000000000000 rdi: 00000000000d0500 (XEN) rbp: 00000000000dffcc rsp: 000000000000ffb8 r8: 0000000000000000 (XEN) r9: 0000000000000000 r10: 0000000000000000 r11: 0000000000000000 (XEN) r12: 0000000000000000 r13: 0000000000000000 r14: 0000000000000000 (XEN) r15: 0000000000000000 cr0: 0000000000050032 cr3: 00000000183b8000 (XEN) ds: b800 es: 0000 fs: 0010 gs: 0010 ss: 0000 cs: c000 the very same issue affects my Fedora Core 5 VMX domain. Stefan