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/
Home Products Support Community News


Re: [Xen-users] PV on Centos 5 64-bit

To: Jens-Petter Salvesen <jens-petter.salvesen@xxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-users] PV on Centos 5 64-bit
From: Nico Kadel-Garcia <nkadel@xxxxxxxxx>
Date: Wed, 14 Nov 2007 12:33:14 +0000
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 14 Nov 2007 04:32:27 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; bh=Zichc5enympc8gF8w2CTDM7KjGuf4IKSxw5EkOC6Jto=; b=NxinHLCm/YYaCz35T6hvIL+sI532dVltUShhvJNlqoYWRg6ku4QFarWC7S9WgKZ9fQ9l7ICgdUpSFugDgwa8JhKRFiQMHlwk15EL/EEX3l5+6Ku7Hrsq41HImWuIZyCS/fTarEKhsGB/ZO5qUkJS9G+RE0pKmQKMiJrFmmPHaaA=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=KZYQa5LPipXlAdpGONVhLce5cYnLmuib/GdpIxb5RHca454dgPhzP4xJxXfcZ58M8+B8T2zO3RrEbuZjOYivpTbnCk5muuKzunMF7J+PKh0oyNxRnD5KXZqpM+L2ecGVePqW3dEhqYjMr79V/SJSdH1gbVqABCeUKpU0uT0WPNE=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <5A6326FE9B1B3244AC5255B47DA262A13A05FF@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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: <5A6326FE9B1B3244AC5255B47DA262A13A05FD@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <473ADB5A.1050801@xxxxxxxxx> <5A6326FE9B1B3244AC5255B47DA262A13A05FF@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird (Windows/20070728)
Jens-Petter Salvesen wrote:
Nico wrote:
Jens-Petter Salvesen wrote:
I'm having a very difficult time getting paravirtualized Xen running on Centos 5 64bit and I'm hoping someone can spot what I'm doing
I've been attemping to do this for a few days now and I'm really not seeing what I'm doing wrong. Here's what I've done: 1. Installed Centos 5 64-bit on the Dom0 2. Installed a fully virtualized DomU running Centos 5 64-bit.
3. Created a new configuration file that will create a
paravirtualized >
Why aren't you using virt-install? Did you want to duplicate the
virtual system entirely?

I would prefer to be able to select upon boot-time if the VM is going to
run as fully virtualized or paravirtualized. That would enable me to
evaluate both solutions. I thought that it was possible to just make two
different config files that boot two different kernels for the same VM?

To my understanding, a fully virtualized VM must _not_ run a xen-enabled
kernel while a paravirtualized VM _requires_ a compatible xen-enabled
kernel. Is this correct?
Oh, no. A fully virtualized VM can certainly run a Xen enabled kernel (barring some oddnesses with particular kernels). But the initrd certainly needs the right drivers to do so. I think you'll find that a fully virtual VM needs different device drivers than a para-virtualized one.

Also, if you're using pygrub, you don't have to state a kernel. I don't
know if it breaks things, but it's confusing at best.

I know. That kernel= statement is just a leftover from debugging.
Got it. One thing I've done when doing a restoration from a system image, to get the grub set up, is to delete the kernel from the guest domain and do a virt-install "upgrade" on top of it.

Xen-users mailing list

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