public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Olney <aolney-lg4TTeReta+Vc3sceRu5cw@public.gmane.org>
To: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: XP installation speed: KVM vs Xen
Date: Wed, 28 Feb 2007 12:10:08 -0600	[thread overview]
Message-ID: <1172686208.5261.52.camel@localhost.localdomain> (raw)
In-Reply-To: <45E5B07A.3040700-atKUWr5tajBWk0Htik3J/w@public.gmane.org>

The Xen installed image is "Standard PC". I erased the KVM installed
image unfortunately, so  I can't check that easily.

The KVM installed image did require the -no-acpi flag, and the Xen image
does not, so that is consistent with your explanation: the Xen install
is a faster, non-acpi HAL.

The speed difference is quite noticeable on a core 2 1.66


On Wed, 2007-02-28 at 18:40 +0200, Avi Kivity wrote:
> Andrew Olney wrote:
> > I'd almost swear that KVM is faster with an XP raw image that was
> > installed by Xen, than it is with a raw image installed by KVM.
> >
> >   
> 
> That may well be.  Perhaps the images have different HALs.
> 
> Compare the values under My Computer | Properties | Hardware | Device 
> Manager | Computer.  Maybe one uses the "Standard PC" HAL (faster)
> and 
> the other the ACPI HAL (slower).  You can also change HALs (required 
> reboot).
> 
> 
> > On Wed, 2007-02-28 at 09:10 +0200, Avi Kivity wrote:
> >   
> >> Andrew Olney wrote:
> >>     
> >>> I've been migrating from Xen to KVM for a wide variety of reasons.
> >>>
> >>> I've noticed, however, that XP installs much much faster with Xen
> (3.03
> >>> xen-image-xen0-2.6.17-6-generic-xen0 ubuntu) than with KVM (14).
> >>>   
> >>>       
> >> btw, as both Xen and kvm use qemu, Xen full virtualization images
> should 
> >> work without change in kvm.
> >>
> >>
> >>
> >>     
> >
> >   
> 
> 
> -- 
> error compiling committee.c: too many arguments to function
> 
> 


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

      parent reply	other threads:[~2007-02-28 18:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-27 20:46 XP installation speed: KVM vs Xen Andrew Olney
     [not found] ` <1172609205.6539.9.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2007-02-28  0:05   ` Andreas Hasenack
     [not found]     ` <200702272105.18311.ahasenack-y7mWNqJcIDpfJ/NunPodnw@public.gmane.org>
2007-02-28  0:06       ` Anthony Liguori
2007-02-28  0:09   ` Anthony Liguori
2007-02-28  7:02   ` Avi Kivity
2007-02-28  7:10   ` Avi Kivity
     [not found]     ` <45E52AEE.6030107-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-02-28 16:16       ` Andrew Olney
     [not found]         ` <1172679377.5261.38.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2007-02-28 16:40           ` Avi Kivity
     [not found]             ` <45E5B07A.3040700-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-02-28 18:10               ` Andrew Olney [this message]

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=1172686208.5261.52.camel@localhost.localdomain \
    --to=aolney-lg4ttereta+vc3sceru5cw@public.gmane.org \
    --cc=avi-atKUWr5tajBWk0Htik3J/w@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