Carsten from Virtastic
2011-Jul-30 00:32 UTC
[Xen-users] Qemu/Bios/Devices different in xm and xl?
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 2.6.32.43 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"
builder=''hvm''
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
vnc=1
vnclisten="0.0.0.0"
vncdisplay=3
serial=''pty''
=====
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!
Cheers
Carsten
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Fajar A. Nugraha
2011-Jul-30 03:58 UTC
Re: [Xen-users] Qemu/Bios/Devices different in xm and xl?
On Sat, Jul 30, 2011 at 7:32 AM, Carsten from Virtastic <carsten@virtastic.com> 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 2.6.32.43 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. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users