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

Re: [Xen-devel] VMX status report. Xen: #17304 & Xen0: #496 -- no new is

To: "Li, Haicheng" <haicheng.li@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] VMX status report. Xen: #17304 & Xen0: #496 -- no new issue
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Fri, 28 Mar 2008 14:02:19 +0000
Delivery-date: Fri, 28 Mar 2008 07:03:41 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <FC1D1B23302A22499C60C967336B2AE002951B79@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AciQpKWD0nUpLcYoQJO5vdBPtedtsQAAGYrCAARoKiAACWpq/Q==
Thread-topic: [Xen-devel] VMX status report. Xen: #17304 & Xen0: #496 -- no new issue
User-agent: Microsoft-Entourage/11.4.0.080122
On 28/3/08 13:37, "Li, Haicheng" <haicheng.li@xxxxxxxxx> wrote:

> 1. Hvm guest with generic kernel 2.6.18 cannot boot up,  the serial log
> shows "io.c:198:d1 MMIO emulation failed @ 0060:c01af276: 0f 6f 06 0f 6f
> 4e". http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1196.

Can you provide the vmlinux file for this kernel, or otherwise find out what
code is at address 0xc01af276 in that kernel. Either we are emulating
something we should not emulate, or the kernel really is accessing I/O
memory with SSE instructions, and we'll need to emulate them.

> 2. on RHEL5.1, "insmod balloon.ko" shows error as below:
> 
> Xen version 3.3.
> Hypercall area is 1 pages.
> xen_mem: Initialising balloon driver.
> kobject_add failed for memory with -EEXIST, don't try to register things
> with the same name in the same directory.

Does RHEL5.1 already have a directory /sys/devices/system/memory/? If so
what is under there? Could you 'ls -lR' that directory and send us the
output?

I don't think anyone actually uses our balloon driver sysfs interface, so we
could just rename it to something a bit more Xen-specific.

 Thanks,
 Keir



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