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] Qemu/Bios/Devices different in xm and xl?

To: Carsten from Virtastic <carsten@xxxxxxxxxxxxx>
Subject: Re: [Xen-users] Qemu/Bios/Devices different in xm and xl?
From: "Fajar A. Nugraha" <list@xxxxxxxxx>
Date: Sat, 30 Jul 2011 10:58:42 +0700
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 29 Jul 2011 21:00:22 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <B6C8DD68-6E4B-4B84-96FB-D77B00DC1854@xxxxxxxxxxxxx>
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: <B6C8DD68-6E4B-4B84-96FB-D77B00DC1854@xxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On Sat, Jul 30, 2011 at 7:32 AM, Carsten from Virtastic
<carsten@xxxxxxxxxxxxx> wrote:
> Hi guys,
> I've just migrated a bunch of servers from CentOS 5.6 / Xen 3.4.3 to CentOS 
> 6.0 / Xen 4.1.1  (Kernel w/ pvops, "Jeremy Edition" :))
> For some guests, in particular FreeBSD HVM guests, I notice a difference 
> between "xm" and "xl", more precisely they fail to detect the second block 
> device (LVM backend) with "xl" and terminate with kernel panic, whereas they 
> start just fine with "xm". Now, "xm" is going to be deprecated soon.
> Does anyone know what the actual difference is? This is the domain 
> configuration, which should be easy and straight-forward enough...

There are some known bugs in xl, which has been continually improved.
IMHO the best way to handle your problem is to try latest
xen-unstable, compile it, and see if it fix your problem. If not, then
report the problem to xen-devel.


Xen-users mailing list

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