From: Nivedita Singhvi <nsnix@comcast.net>
To: Ed Smith <esmith@virtualiron.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Testing status of fully virtualized guests (Intel VT) on 32bit XEN unstable
Date: Sat, 06 May 2006 11:19:09 -0700 [thread overview]
Message-ID: <445CE89D.2000101@comcast.net> (raw)
In-Reply-To: <445B743F.20609@virtualiron.com>
Ed Smith wrote:
> 4. The RHEL3 UP tests ran OK however they took 12 hours
> to complete where on RHEL4 UP the run for ~4 hours.
> There seems to be some performance issue running a
> 2.4 kernel fully virtualized guest.
We've seen this, and is one of the factors driving the push for
a new device model for fully virtualized guests. I'm not sure if
anyone is looking into shorter term investigation/hacks for it
or taking 2.4 based guests very seriously at this point.
thanks,
Nivedita
next prev parent reply other threads:[~2006-05-06 18:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-05 15:50 Testing status of fully virtualized guests (Intel VT) on 32bit XEN unstable Ed Smith
2006-05-06 18:19 ` Nivedita Singhvi [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-05-10 19:51 Ed Smith
2006-05-06 18:21 Ed Smith
2006-05-03 23:19 Ed Smith
2006-05-02 23:23 Ed Smith
2006-05-02 20:51 Ed Smith
2006-05-03 6:44 ` Keir Fraser
2006-05-01 23:33 Ed Smith
2006-04-30 1:45 Zhao, Yunfeng
2006-04-29 15:57 Ed Smith
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=445CE89D.2000101@comcast.net \
--to=nsnix@comcast.net \
--cc=esmith@virtualiron.com \
--cc=xen-devel@lists.xensource.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.