All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir@xensource.com>
To: "You, Yongkang" <yongkang.you@intel.com>,
	"Zhao, Yunfeng" <yunfeng.zhao@intel.com>,
	xen-devel@lists.xensource.com
Subject: Re: vmx status report against cset 14912 - 1 fixedissue, 4 old issues
Date: Wed, 25 Apr 2007 12:27:15 +0100	[thread overview]
Message-ID: <C254F9A3.DD1F%keir@xensource.com> (raw)
In-Reply-To: <094BCE01AFBE9646AF220B0B3F367AABCD9FDF@pdsmsx413.ccr.corp.intel.com>

On 25/4/07 12:09, "You, Yongkang" <yongkang.you@intel.com> 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

  reply	other threads:[~2007-04-25 11:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <823A93EED437D048963A3697DB0E35DE2A1EEB@pdsmsx414.ccr.corp.intel.com>
2007-04-25  8:51 ` vmx status report against cset 14912 - 1 fixed issue, 4 old issues Zhao, Yunfeng
2007-04-25  8:56   ` Keir Fraser
2007-04-25  9:27     ` Zhao, Yunfeng
2007-04-25  9:34       ` Keir Fraser
2007-04-25  9:44         ` Zhao, Yunfeng
2007-04-25 11:09         ` vmx status report against cset 14912 - 1 fixedissue, " You, Yongkang
2007-04-25 11:27           ` Keir Fraser [this message]
2007-04-25 15:19             ` You, Yongkang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=C254F9A3.DD1F%keir@xensource.com \
    --to=keir@xensource.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=yongkang.you@intel.com \
    --cc=yunfeng.zhao@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.