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

[Xen-devel] RE: [New Update] VMX status report against cset #16366

To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>
Subject: [Xen-devel] RE: [New Update] VMX status report against cset #16366
From: "You, Yongkang" <yongkang.you@xxxxxxxxx>
Date: Tue, 13 Nov 2007 17:40:17 +0800
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 13 Nov 2007 01:41:00 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <094BCE01AFBE9646AF220B0B3F367AAB026647D1@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: AcglEYBBLfQGtVr0SiqUrTl5UwQ8KgAxoirQ
Thread-topic: [New Update] VMX status report against cset #16366
Hi Keir,

>1) Can not insert module "xen-platform-pci.ko" in the 2.6.18 
We found this case is not the issue of PV drivers. It is a wrong
reporting by case.
But I found it is because another bug. 

In (and before) xen-unstable #16157, 64bit Dom0 can do a chroot into a
32bit root file system. 
But since #16281, when doing chroot from 64 Dom0 to 32bit root file
system, it would report "Segmentation Fault".

I tried with Native 64bit Linux, this operation is okay. So I think it
is a new issue. Could you double check?
The reproduce steps,
1. /dev/sda1 is 64bit Dom0 system; sda2 is a 32bit Linux system.
2. Boot to sda1 Dom0.
3. mount /dev/sda2 /mnt/sda2
4. chroot /mnt/sda2

Best Regards,
Yongkang You
 

>-----Original Message-----
>From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx 
>[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of 
>You, Yongkang
>Sent: Monday, November 12, 2007 5:51 PM
>To: xen-devel
>Subject: [Xen-devel] VMX status report against cset #16366 & 
>linux-xen #310
>
>Hi all,
>
>We add 10 VT-d testing cases into our nightly testing from 
>this changeset. There are 5 failed VT-d cases, which are 
>related with PCI e100 NIC assignment. But they can pass in 
>changeset #16281. 
>
>We also verified Windows timer issue has been fixed by using 
>timer_mode=1 in HVM config file. 
>
>There are still 3 opened major issues. 
>
>New issues:
>=================================================
>1) Can not assign PCI e100 NIC to guest 
>
>Fixed issues:
>=================================================
>1) Time latency is a negative number on window guest when vcpu > 1
>         http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=895
>
>Old issues :
>=================================================
>1) Can not insert module "xen-platform-pci.ko" in the 2.6.18 
>HVM Linux guest
>        http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1101
>2) Can not boot up win2000 guest on PAE
>        http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1102
>3) Can not install 32bit Fedora 7 with vcpu > 1
>         http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1084
>

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