From: konrad wilk <konrad.wilk@oracle.com>
To: "Ren, Yongjie" <yongjie.ren@intel.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
"Xu, Dongxiao" <dongxiao.xu@intel.com>,
xen-devel <xen-devel@lists.xensource.com>,
"Zhang, Xiantao" <xiantao.zhang@intel.com>
Subject: Re: nested virtualization test report for Xen 4.3-RC1
Date: Thu, 27 Jun 2013 16:20:25 -0400 [thread overview]
Message-ID: <51CC9E89.5010809@oracle.com> (raw)
In-Reply-To: <1B4B44D9196EFF41AE41FDA404FC0A1001B2623F@SHSMSX102.ccr.corp.intel.com>
On 6/27/2013 9:27 AM, Ren, Yongjie wrote:
>> -----Original Message-----
>> From: Pasi Kärkkäinen [mailto:pasik@iki.fi]
>> Sent: Thursday, June 27, 2013 8:47 PM
>> To: George Dunlap
>> Cc: Ren, Yongjie; Xu, Dongxiao; xen-devel; Zhang, Xiantao
>> Subject: Re: [Xen-devel] nested virtualizaiton test report for Xen 4.3-RC1
>>
>> On Thu, Jun 27, 2013 at 12:37:56PM +0100, George Dunlap wrote:
>>> On Fri, May 10, 2013 at 12:07 PM, Ren, Yongjie <yongjie.ren@intel.com>
>> wrote:
>>>> Hi All,
>>>> This the a nested virtualization test report for Xen 4.3-RC1 on Intel
>> hardware. We use Linux 3.9.1 as Dom0.
>>>> a. Virtual EPT and VMCS shadowing features can work fine.
>>>> b. Xen, KVM and VMware can basically work on top of L0 Xen.
>>>> c. 32bit/64bit Linux and Windows are covered as L2 guests.
>>> Sorry I just saw this -- thanks for the nice enumeration.
>>>
>>> Two questions. First, I don't see the Win7 "XP compatibility mode" on
>>> this list -- that would be L0 Xen, L1 Win7, L2 XP. This seems like
>>> probably the most likely actual real-world use of nested virt. Is
>>> that on your radar at all?
>>>
> So far, I didn't test this case.
> That's a good use case. I'll add this case in my next report about nested virt.
>
>>> Secondly, what do you think is the primary use case for Xen-on-Xen (or
>>> KVM-on-Xen, &c)? Who would want to use it and why?
>>>
> I'm not sure which type of nested virt is more important. But I heard some use cases as following.
>
> 1. public cloud (e.g. Amazon EC2: if they can provide virtual VMX to the VMs, that can be a value-added service.)
>
> 2. QA: Nested virt can make QAs easy to set up the testing env (especially: virt/cloud areas).
> In a Ovirt Workshop, I heard some guys have been testing Ovirt in KVM nested virtualization.
> Some OpenStack guys also told me that they want to test OpenStack in a VM not on physical host.
And also development. I do use that for some of the low-level assembler
coding - as I can trigger QEMU to dump the CPU state when printing out
to the debug port. Quite useful when I was poking in suspend/resume logic.
I was quite happy to see Xen 4.3 + Fedora 18 allow me to nicely boot
under Xen an Xen HVM OS. Didn't try yet to run an HVM guest within the
HVM context.
prev parent reply other threads:[~2013-06-27 20:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-27 13:27 nested virtualization test report for Xen 4.3-RC1 Ren, Yongjie
2013-06-27 20:20 ` konrad wilk [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=51CC9E89.5010809@oracle.com \
--to=konrad.wilk@oracle.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=dongxiao.xu@intel.com \
--cc=xen-devel@lists.xensource.com \
--cc=xiantao.zhang@intel.com \
--cc=yongjie.ren@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.