From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Jeff Carr <basilarchia-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [KVM] ANNOUNCE: new kvm userspace release
Date: Fri, 10 Nov 2006 17:47:44 +0200 [thread overview]
Message-ID: <45549F20.3030209@qumranet.com> (raw)
In-Reply-To: <45540464.4010508-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Jeff Carr wrote:
> On 11/09/06 07:23, Avi Kivity wrote:
>
>> Changes:
>> - much easier to get running, see updated HOWTO
>> - now just one download, get yours while supplies last
>> - single qemu binary for kvm and non-kvm runs (Anthony Liguori)
>> - accompanying external kernel module package has all bugfixes folded
>> in (plus a bit of cosmetics)
>>
>> http://kvm.sourceforge.net
>>
>>
>
> The patch you put up on Nov 2 was a really easy to work with. Nicely
> done! I installed it here and it ran successfully. It booted a windows
> 2003 server image successfully. I attached a screenshot.
>
>
Thanks for the success report. It makes a welcome change from the bug
reports :)
> Time runs at about half speed inside a linux guest.
>
Hmm. What are the guest's and host's CONFIG_HZ?
> Between qemu+kvm and just qemu (on the same hardware) there doesn't
> seem to be an obvious difference in speed. I didn't look around much
> more than just booting a few images so far; so that's all I'm basing
> that unscientific estimate on.
>
It depends on the hardware. We find that the Core 2s and the AMDs do
very well.
The planned MMU optimization will improve the speed considerably.
> For me, this Nov 11 tarball is a lot harder to work with. For the
> kernel module, I can't tell by inspection what patches have been
> applied from the mailing list. For qemu, the whole qemu upstream is
> extracted in there so if I want to get a clean patch now I would have
> to guess which version to start will and make my own diff.
>
The intent was to reduce the amount of downloading and compilation
needed to make it work. I guess one size does not fit all.
For the record, the modified qemu is based on Fedora's qemu-0.8.2 and
the external kernel module is equvalent to all patches posted up to date
plus a couple of cosmetic fixes.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
next prev parent reply other threads:[~2006-11-10 15:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-09 15:23 [KVM] ANNOUNCE: new kvm userspace release Avi Kivity
[not found] ` <4553480C.8090100-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2006-11-10 4:47 ` Jeff Carr
[not found] ` <45540464.4010508-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2006-11-10 15:47 ` Avi Kivity [this message]
[not found] ` <45549F20.3030209-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2006-11-10 23:59 ` Jeff Carr
[not found] ` <45551246.6010706-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2006-11-12 8:15 ` Avi Kivity
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=45549F20.3030209@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=basilarchia-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox