qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Mark Williamson <mark.williamson@cl.cam.ac.uk>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] About qemu emulation speed (a question) and supported OS
Date: Tue, 13 Sep 2005 23:27:39 -0500	[thread overview]
Message-ID: <4327A6BB.1040509@us.ibm.com> (raw)
In-Reply-To: <200509140448.24354.mark.williamson@cl.cam.ac.uk>

Mark Williamson wrote:

>>>No, I got the impression that Fabrice was taking about virtualization the
>>>way VMware, old plex86, and vmbear (new FOSS x86 virtualizer in the
>>>works) do it.
>>>      
>>>
>>The x86 cannot be "virtualized" in the Popek/Goldberg sense, so there's
>>a couple of fast emulation techniques that are possible.  Other than a
>>hand coded dynamic translator, I reckon qemu + kqemu is about as good as
>>it can get (unless I'm missing something here).  Do you have
>>    
>>
>
>Well, VMware does manage direct execution of some kernel code, I believe.  
>VMware's real super-cunningness is doing this as much as they can, instead of 
>emulating all the stuff.  That said, I think with suitable optimisations 
>emulating all the kernel code could be acceptable.
>
>The unfortunate thing is that the guest can still tell it's in a VMware 
>machine (I'm not clear how) so it's not really *full* virtualisation, it's 
>just about epsilon away from it :-)  VT / SVM will solve this properly.
>  
>
I reckon kqemu has this same problem... Technically, even in ring 3, if 
you run natively, you violate the Popek/Goldberg requirements because of 
cpuid.  It's just not possible to trap it but it shouldn't matter for 
most software.

>They have a (crazy but cool) idea that they'll one day be able to live-migrate 
>(i.e. without more than a few hundred ms downtime) virtual machines between 
>L4 hypervisors and Xen hypervisors.
>  
>
Yeah, how cool is that :-)

Regards,

Anthony Liguori

>Cheers,
>Mark
>
>  
>
>>>>FWIW, Xen is already using QEMU in this way.  It would be very neat to
>>>>see this technique applied to a Type II VMM.
>>>>        
>>>>
>>>Do you have any details on this?
>>>      
>>>
>>Mark did a really good job of summarizing the current architecture.
>>
>>Regards,
>>
>>Anthony Liguori
>>
>>    
>>
>>>>Regards,
>>>>
>>>>Anthony Liguori
>>>>
>>>>
>>>>_______________________________________________
>>>>Qemu-devel mailing list
>>>>Qemu-devel@nongnu.org
>>>>http://lists.nongnu.org/mailman/listinfo/qemu-devel
>>>>        
>>>>
>>_______________________________________________
>>Qemu-devel mailing list
>>Qemu-devel@nongnu.org
>>http://lists.nongnu.org/mailman/listinfo/qemu-devel
>>    
>>
>
>  
>

  reply	other threads:[~2005-09-14  4:30 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-13 12:36 [Qemu-devel] About qemu emulation speed (a question) and supported OS Alexandre Leclerc
2005-09-13 13:08 ` Adrian Smarzewski
2005-09-13 18:02   ` Alexandre Leclerc
2005-09-13 13:38 ` Jim C. Brown
2005-09-13 14:58   ` Anthony Liguori
2005-09-13 21:48     ` Jim C. Brown
2005-09-14  0:18       ` Mark Williamson
2005-09-14  2:48       ` Anthony Liguori
2005-09-14  3:48         ` Mark Williamson
2005-09-14  4:27           ` Anthony Liguori [this message]
2005-09-14  4:58             ` Mike Swanson
2005-09-14 13:39             ` Jim C. Brown
2005-09-14 18:46               ` Anthony Liguori
2005-09-14 22:42                 ` Jim C. Brown
2005-09-14 13:37         ` Jim C. Brown
2005-09-14 15:47           ` Henrik Nordstrom
2005-09-14 17:53             ` Mark Williamson
2005-09-14 17:18           ` John R. Hogerhuis
2005-09-14 22:34             ` Jim C. Brown
2005-09-14 17:46           ` Mark Williamson
2005-09-15 21:26           ` Karl Magdsick
2005-09-15 23:24             ` Mark Williamson

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=4327A6BB.1040509@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=mark.williamson@cl.cam.ac.uk \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).