WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] domU inside another domU?

To: "Ferreira, N. L. (Nuno)" <n.l.ferreira@xxxxx>
Subject: Re: [Xen-users] domU inside another domU?
From: "Fajar A. Nugraha" <fajar@xxxxxxxxx>
Date: Fri, 6 Feb 2009 22:29:42 +0700
Cc: xen-users <xen-users@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 06 Feb 2009 07:30:34 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <498C55D6.1020301@xxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <498C55D6.1020301@xxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On Fri, Feb 6, 2009 at 10:23 PM, Ferreira, N. L. (Nuno)
<n.l.ferreira@xxxxx> wrote:
> My idea was to create a domU with enough resources (say, 6 vcpu's and 2 GB
> RAM per vcpu).
> Then, I can give to the students the root passwd for this domU, and they can
> start to build some VM's inside of it.
> Is this idea feasible?


No.

You PROBABLY can :
- have a normal linux kernel running
- install virtualbox or vmware
- create virtualbox/vmware linux guests with 2 CPU (or whatever max
cpu it can give) and 2GB ram
- give students password to virtualbox guests
- install Xen with PV domU on virtualbox guests. HVM is not possible.

Regards,

Fajar

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>