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

["Li, Haicheng" <haicheng.li@xxxxxxxxx>]

Keir Fraser wrote:
> On 28/3/08 07:23, "Li, Haicheng" <haicheng.li@xxxxxxxxx> wrote:
> 
>> 4. PV drivers broken again: module xen-vnif.ko inserting failed.
> 
> Is there a ticket for this issue? Or just post the error printed on
> insertion failure. I can probably work out a fix from that.
> 
>  -- Keir

Hi Keir,

I rechecked this issue on c/s 17304, and found it had been fixed; I
recalled we found this issue on c/s 17058, "insmod xen-vnif.ko" shew one
unknown symbol on that c/s.

However, I found another two issues on c/s 17304 when I tested pv
driver: 

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.

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.

Call Trace:
 [<ffffffff80141148>] kobject_add+0x16e/0x199
 [<ffffffff8846fa43>] :xen_balloon:balloon_sysfs_init+0x12/0xbb
 [<ffffffff8810d0cb>] :xen_balloon:balloon_init+0xcb/0xf1
 [<ffffffff800a29da>] sys_init_module+0x16a6/0x1857
 [<ffffffff8000c1a5>] _atomic_dec_and_lock+0x39/0x57
 [<ffffffff8005b28d>] tracesys+0xd5/0xe0
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1197.

-- haicheng

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