[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] Qemu/Bios/Devices different in xm and xl?

  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Carsten from Virtastic <carsten@xxxxxxxxxxxxx>
  • Date: Sat, 30 Jul 2011 01:32:34 +0100
  • Delivery-date: Fri, 29 Jul 2011 17:34:21 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=virtastic.com; h=from :content-type:content-transfer-encoding:subject:date:message-id :to:mime-version; q=dns; s=selector1; b=M2ZIp79kmoPQP/Hm1Y3VGE/w njl1BEMoTKVv2WkQhOqkVD8Zzfrn5BngHiIcPqTwt8ZvEoCavCzlXMlP9J9DB31B fSKo99olSNlmcyHXJvcGIPHrAxmXzWWDw8KRnX7NTHu7kNJ2eHI/fPEzqUnc86Qj HjAjdUtsP5iz+Eevvkg=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

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...


kernel = "/usr/lib/xen/boot/hvmloader"
device_model = '/usr/lib/xen/bin/qemu-dm'

memory = 2048
name = "db2"

vif = [ 'bridge=xenbr0.127', 'bridge=xenbr1.127' ]
disk = [ 'phy:/dev/disk2/db2.root,hda,w', 
         'phy:/dev/disk2/db2.mysql,hdb,w' ]
vcpus = 2



Guest is running FreeBSD 8.2, XENHVM-kernel, amd64 (or x86_64 in Linux terms)

The whole issue is not critical at the moment, because I can still fire the 
guests up with "xm", but I'd rather stick to the recommendations/standards, 
which would be "xl" for Xen 4.1+.

Thanks guys!


Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.