xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Jeroen Groenewegen van der Weyden <groen692@grosc.com>
To: xen-devel@lists.xensource.com
Cc: Christoph.Egger@amd.com, eddie.dong@intel.com
Subject: Nested Virtualisation question
Date: Mon, 04 Apr 2011 08:49:56 +0200	[thread overview]
Message-ID: <4D996A14.10601@grosc.com> (raw)
In-Reply-To: <4D996983.7010501@grosc.com>

Hello,

I have A question about nested virtualisation, the xen user list 
suggested to post the question here.
I need nested virtualisation to run an application on out en 
environment, which uses kvm it-self.

I suppose I have to apply these patches:
- 
http://xen.markmail.org/search/?q=nested%20vmx#query:nested%20vmx+page:1+mid:z33lihxnbdjghua5+state:results
-  or http://xenbits.xen.org/ext/cegger/nestedhvm/

Is it correct these patches are now in the xen-unstable branch?
Anything else to get me on my way.


My goal is

DOM0
  openSUSE 11.4 with xen 4.X

DOMU1
  SLES 11 SP1
   kvm guest HVM domu1a (propetary OS)
   kvm guest HVM domu1b (sles 10 sp3)
   kvm guest HVM domu1c (sles 10 sp3)
   kvm guest HVM domu1b (sles 10 sp3)

> Op 3-4-2011 23:29, Todd Deshane schreef:
>> On Sun, Apr 3, 2011 at 8:32 PM, Jeroen Groenewegen van der Weyden
>> <groen692@grosc.com>  wrote:
>>> I now am in the position to start testing your suggestion.
>>>
>>> An additional question, is it correct the patches you mention here 
>>> are part
>>> of the xen4.2-unstable branch?
>>> are these patches for vt-x or for svm only? the developer seems to 
>>> be from
>>> amd. My machines are running on intel.
>>>
>> The latest patch series is here:
>> http://xen.1045712.n5.nabble.com/PATCH-00-12-Nested-Virtualization-Overview-td3415672.html 
>>
>>
>> Not sure if it has been accepted yet or not. You can email the
>> developer and/or devel list for confirmation.
>>
>> Thanks,
>> Todd
>>
>>> mfg,
>>> Jeroen
>>>
>>> Op 15-2-2011 16:21, Todd Deshane schreef:
>>>> On Tue, Feb 15, 2011 at 6:47 AM, Jeroen Groenewegen van der Weyden
>>>> <groen692@grosc.com>    wrote:
>>>>> The why is a good question,
>>>>> We use xen as out main virtualisation platform. But now there are
>>>>> applications that use virtualisation it self. In my case I have an
>>>>> application that uses kvm. So to put it on our xen server it needs 
>>>>> to be
>>>>> nested. I guess in the future more of these situation will appear.
>>>>>
>>>>> I read somethings about nested virtualisation and I wonder If 
>>>>> somebody
>>>>> has
>>>>> any experience with it.
>>>>>
>>>> To run KVM inside of a guest you need virtualization support within
>>>> the guest (running nested xen doesn't require the double nested
>>>> (unless you want to do HVM within the nested of course))
>>>>
>>>> Patches can be found here:
>>>>
>>>> http://xen.markmail.org/search/?q=nested%20vmx#query:nested%20vmx+page:1+mid:z33lihxnbdjghua5+state:results 
>>>>
>>>>
>>>> I believe KVM should also have support for nested vmx and nested svm.
>>>>
>>>> The use cases are fairly slim, so finding users/testers is often
>>>> difficult.
>>>>
>>>> Please report any bugs you find to the appropriate devel lists and cc
>>>> the appropriate nested virtualization maintainers .
>>>>
>>>> Hope that helps.
>>>>
>>>> Thanks,
>>>> Todd
>>>>
>>>> _______________________________________________
>>>> Xen-users mailing list
>>>> Xen-users@lists.xensource.com
>>>> http://lists.xensource.com/xen-users
>>>>
>>>
>>
>>
>

  reply	other threads:[~2011-04-04  6:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4D596513.90504@grosc.com>
     [not found] ` <AANLkTim4d14oK-KOwOG2YZzb-n3jyqj6SttM0xMzxC9a@mail.gmail.com>
     [not found]   ` <4D5A2175.3090309@grosc.com>
     [not found]     ` <AANLkTinuoLdRwVEzWUp3-O5Qtjhs4fW8e2+-RacrNjYu@mail.gmail.com>
     [not found]       ` <4D98D969.3050101@grosc.com>
     [not found]         ` <BANLkTi=-8XmWcrx_8Q1ai0DgjnUoiKB+ZQ@mail.gmail.com>
2011-04-04  6:47           ` [Xen-users] Nested Virtualisation question Jeroen Groenewegen van der Weyden
2011-04-04  6:49             ` Jeroen Groenewegen van der Weyden [this message]
2011-04-04  9:51             ` Tim Deegan
2011-04-04 10:08               ` Jeroen Groenewegen van der Weyden
2011-04-07  5:36               ` Re: [Xen-users] " Jeroen Groenewegen van der Weyden
2011-04-07  7:09                 ` Keir Fraser
2011-04-07  7:14                   ` Keir Fraser
2011-04-07 10:29                     ` Tim Deegan
2011-04-09  5:07                       ` Jeroen Groenewegen van der Weyden
2011-04-09  6:22                         ` Keir Fraser
2011-04-09 10:18                           ` Jeroen Groenewegen van der Weyden
2011-04-09 11:15                             ` Keir Fraser
2011-04-09 13:32                               ` Jeroen Groenewegen van der Weyden
2011-04-09 14:31                                 ` Keir Fraser
2011-04-07  9:09                   ` Christoph Egger
2011-04-07  9:30                     ` Keir Fraser
2011-04-07  9:04                 ` Christoph Egger
2011-04-07 10:15                   ` Jeroen Groenewegen van der Weyden

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=4D996A14.10601@grosc.com \
    --to=groen692@grosc.com \
    --cc=Christoph.Egger@amd.com \
    --cc=eddie.dong@intel.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 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).