From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: vmx status report against cset 14912 - 1 fixedissue, 4 old issues Date: Wed, 25 Apr 2007 12:27:15 +0100 Message-ID: References: <094BCE01AFBE9646AF220B0B3F367AABCD9FDF@pdsmsx413.ccr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <094BCE01AFBE9646AF220B0B3F367AABCD9FDF@pdsmsx413.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: "You, Yongkang" , "Zhao, Yunfeng" , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 25/4/07 12:09, "You, Yongkang" wrote: > Which kernel and guest did you use? I meet issues in 2.6.16 kernel (I build a > new kernel for the guest). Both UP and SMP has VBD problem in 64bit system. > But IA32 kernel (2.6.16) is okay. > > I tried your suggestion way in SMP system. I notice after doing kernel build > for a while, the interrupts number won't increase any more, and the kernel > build command is hung there. > > When I tried UP 64bit guest, the command hang when doing mount VBD disk. > > Would it be the issue of guest kernel? I rebuild a 2.6.16 Linux kernel and > used it in RHEL4U3. Well it sounds 64-bit guest specific doesn't it. I tested with a 32-bit guest. Also I did not do a kernel build, just specjbb. -- Keir