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/
Home Products Support Community News


RE: [Xen-devel] Testing Report for Xen 3.0.3 rc1

To: "Steven Smith" <sos22-xen@xxxxxxxxxxxxx>
Subject: RE: [Xen-devel] Testing Report for Xen 3.0.3 rc1
From: "Xu, JiajunX" <jiajunx.xu@xxxxxxxxx>
Date: Sat, 30 Sep 2006 11:29:17 +0800
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, sos22@xxxxxxxxxxxxx
Delivery-date: Fri, 29 Sep 2006 20:29:54 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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: Acbj0kaBn+Col8ZdRMSrqKLwUVq9+AAa8vkg
Thread-topic: [Xen-devel] Testing Report for Xen 3.0.3 rc1
Thanks for your comments, I have verified these issues and see my comments 

Best Regards,

>-----Original Message-----
>From: Steven Smith [mailto:sos22@xxxxxxxxxxxxxxxx] On Behalf Of Steven Smith
>Sent: 2006年9月29日 22:19
>To: Xu, JiajunX
>Cc: xen-devel@xxxxxxxxxxxxxxxxxxx; sos22@xxxxxxxxxxxxx
>Subject: Re: [Xen-devel] Testing Report for Xen 3.0.3 rc1
>> Here are issues found in our tests, For the first 6 issues, I think it's
>> better to be fixed in 3.0.3:
>> 1. Para-virtualization driver doen't work for HVM guests
>> The hvm guest always hanged or met kernel panic when trying to load
>> xenbus.ko. So vbd and vnif don't work on IA32 and IA32e HV.
>Should be fixed by cset 11672 on unstable.
Yes, it should be fixed in the latest cset. We tested cset 11678 and it works 

>> 5. Booting VMX with vcpus=16, but in guest it shows only 8 CPUs
>> We found the issue on Paxville, which machine has 16 LP. Setting
>> vcpus=16 in configuration file and then starting VMX.
>> When VMX starts up, only 8 cpus found in guest OS through /proc/cpuinfo,
>> and "xm vcpu-list" shows
>> that 8 vcpu are in status "r" and 8 are in status of "p".
>Linux, by default, will only use the first 8 processors in the system.
>What's NR_CPUS in your kernel config?
After set NR_CPUS to 16, we can boot up 16 vcpus in Guest. It's due to our env 
mistake. Thanks for your hints.

>> 6. Using vi in VMX hangs guest
>> It's an old issue which always makes our work hard. But I think it
>> should be fixed in 3.0.3 since VI is very popular command, isn't it?
>That's not good.  I'm optimistic that it was fixed by csets 11622 and
>11624 of xen-unstable, but I've never been able to reproduce this
>reliably enough to test.  Could you have another go, please?
I have tried cset 11624 and using vi still will make Guest hang. If you work in 
text mode and use vi, it's easy to reproduce it.

>> 8. Can not input number from speail number keys (when Open Num Lock)
>> It's also a user experience issue, sometimes the keyboard will work and
>> sometimes not.
>Is this HVM guests using the vnc viewer?
The issue exists in both vnc and sdl mode. We found it in Windows Guest and 
Xwindows mode in Linux Guest.

>> 12. Can't set acoustic on VMX IDE
>Acoustic as in noise control, yes?  Why would you ever need to?
Yes. It is an IDE hard disk feature. We can set it in Native Linux. But can not 
in VMX domain. So we report it, although it is harmless. 


Xen-devel mailing list