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] Convert CentOS system to Xen image?

To: Tiago Cruz <tiagocruz@xxxxxxxxxxxx>
Subject: Re: [Xen-users] Convert CentOS system to Xen image?
From: James Pifer <jep@xxxxxxxxxxxxxxxx>
Date: Wed, 02 Apr 2008 15:36:21 -0400
Cc: Xen List <xen-users@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 02 Apr 2008 12:37:31 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1207163388.27447.32.camel@xxxxxxxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <20080401195421.GJ2937@xxxxxxx> <1207081039.8297.52.camel@xxxxxxxxxxxxxxxxxxxxxxxx> <20080401223507.GA4561@xxxxxxx> <1207140100.8297.59.camel@xxxxxxxxxxxxxxxxxxxxxxxx> <20080402133214.GU4561@xxxxxxx> <1207144984.8297.61.camel@xxxxxxxxxxxxxxxxxxxxxxxx> <20080402142504.GX4561@xxxxxxx> <1207154400.8297.70.camel@xxxxxxxxxxxxxxxxxxxxxxxx> <20080402170005.GD4561@xxxxxxx> <1207157714.8297.75.camel@xxxxxxxxxxxxxxxxxxxxxxxx> <20080402181120.GE4561@xxxxxxx> <1207160833.8297.82.camel@xxxxxxxxxxxxxxxxxxxxxxxx> <1207161210.27447.24.camel@xxxxxxxxxxxxxxxxxxx> <1207162751.8297.93.camel@xxxxxxxxxxxxxxxxxxxxxxxx> <1207163388.27447.32.camel@xxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On Wed, 2008-04-02 at 16:09 -0300, Tiago Cruz wrote:
> On Wed, 2008-04-02 at 14:59 -0400, James Pifer wrote:
> 
> > Screenshot of error here:
> > http://www.obrien-pifer.com/screenshot.jpg
> 
> Maybe I can be wrong, but if you would like to virtualize one Red Hat
> v4, you don't can use "Paravirtualization". You must to use
> "Full-Virtualization".
> 
> If you guest OS (domU) was one RHEL5, you will can use "ParaVirt"
> 

Okay, tried again with "Full-Virtualization". Now it tries to boot but
gives an error about missing OS. :-( At this point I was just trying to
make it work on principal and futrue reference. Maybe I'll just do as
Ross suggested and build a new domain and bring the configs over. 

This has probably been covered a million times, but... what is the
preferred method, "Paravirtualization" or "Full-Virtualization"? I'm
guessing Full-Virtualization because it's using VT enabled in the
processor.

Thanks to all. 

James


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

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