Leopoldo Mauricio
2013-Jan-22 19:04 UTC
Re: Problems to start a xen DomU using a logical volume.
Hi guys,
I followed this article to install my first xen project to compare its
CPU/memory and I/O performance with a kvm domain on CentOS 6.4.
http://www.virtuatopia.com/index.php/Building_a_Xen_Virtual_Guest_Filesystem_on_a_Disk_Image_%28Cloning_Host_System%29
In the initial tests whit super.pi benchmarck the CPU performance of my xen
domai was extremely worst than my kvm domain.
Well, I am think that maybe, something was wrong in my xen setup. So I
decided to boot a new xen guest using a logical volume filesystem instead a
disk image, to see whether CPU performance will be better. But this setup
is not working
That is the error (when I try to create a guest domain with a logical
volume filesystem):
Anyone knows what i need to do tho solve this problem?
[root@xen]# xm create xen-pv01.cfg -c
Using config file "./xen-pv01.cfg".
.
.
.
EXT3-fs (xvda1): mounted filesystem with ordered data mode
dracut: Mounted root filesystem /dev/xvda1
*dracut: chroot: failed to run command `/sbin/load_policy'': No such
file or
directory*
dracut: Switching root
*Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100*
Pid: 1, comm: switch_root Not tainted 3.7.1-3.el6xen.x86_64 #1
Call Trace:
[<ffffffff8149d541>] panic+0xc4/0x1d6
[<ffffffff81047131>] do_exit+0x3a5/0x834
[<ffffffff8111e70f>] ? vfs_write+0xd2/0x10a
[<ffffffff8104763d>] do_group_exit+0x7d/0xa5
[<ffffffff8104767c>] sys_exit_group+0x17/0x1b
[<ffffffff814a6899>] system_call_fastpath+0x16/0x1b
I''ve created a logical volume for my Xen guest system following the
instructions of this article:
http://www.virtuatopia.com/index.php/Building_a_Xen_Virtual_Guest_Filesystem_using_Logical_Volume_Management_%28LVM%29
And that is my Xen configuration file:
name = "xen-pv01"
kernel = "/boot/vmlinuz-3.7.1-3.el6xen.x86_64"
ramdisk = "/boot/initrd-3.7.1-3.el6xen.x86_64-no-scsi.img"
memory = 4000
vif = [''bridge=xenbr0, ip=192.168.0.20'']
vcpus = 1
disk = [''phy:vg_xen/lvxenteste,xvda1,w'']
root = "/dev/xvda1 ro"
And my Dom0 configuration:
default=0
timeout=5
selinux=0
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title CentOS (3.7.1-3.el6xen.x86_64)
root (hd0,0)
kernel /xen.gz dom0_mem=40000M cpufreq=xen dom0_max_vcpus=1
dom0_vcpus_pin
module /vmlinuz-3.7.1-3.el6xen.x86_64 ro
root=/dev/mapper/vg_xen-lvroot rd_NO_LUKS LANG=en_US.UTF-8 KEYBOARDTYPE=pc
KEYTABLE=us-acentos rd_NO_MD SYSFONT=latarcyrheb-sun16 crashkernel=auto
rd_LVM_LV=vg_xen/lvroot rd_NO_DM rhgb quiet
module /initramfs-3.7.1-3.el6xen.x86_64.img
*Am I missing something*
--
Leomauricio
_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
Leopoldo Mauricio
2013-Jan-22 19:05 UTC
Problems to start a xen DomU using a logical volume.
> Hi guys, > > I followed this article to install my first xen project to compare its > CPU/memory and I/O performance with a kvm domain on CentOS 6.4. > > > http://www.virtuatopia.com/index.php/Building_a_Xen_Virtual_Guest_Filesystem_on_a_Disk_Image_%28Cloning_Host_System%29 > > In the initial tests whit super.pi benchmarck the CPU performance of my > xen domai was extremely worst than my kvm domain. > > Well, I am think that maybe, something was wrong in my xen setup. So I > decided to boot a new xen guest using a logical volume filesystem instead a > disk image, to see whether CPU performance will be better. But this setup > is not working > > That is the error (when I try to create a guest domain with a logical > volume filesystem): > Anyone knows what i need to do tho solve this problem? > > > [root@xen]# xm create xen-pv01.cfg -c > Using config file "./xen-pv01.cfg". > . > . > . > EXT3-fs (xvda1): mounted filesystem with ordered data mode > dracut: Mounted root filesystem /dev/xvda1 > *dracut: chroot: failed to run command `/sbin/load_policy'': No such file > or directory* > dracut: Switching root > >-- Leopoldo Mauricio Tel: 2483-6474 _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
Leopoldo Mauricio
2013-Jan-24 23:59 UTC
Re: Problems to start a xen DomU using a logical volume.
Hey, I finaly found the source problem. The kernel panic error was happening and the dracut was complaining *"dracut: chroot: failed to run command `/sbin/load_policy'': No such file or directory"* because some lib64 packages that chroot needs to have a perfect behavior was not included inside guest filesystem that I had created When these pachages were included into /lib64 of the guest root filesystem everything worked well. 2013/1/22 Leopoldo Mauricio <leopoldo@corp.globo.com>> Hi guys, > > I followed this article to install my first xen project to compare its > CPU/memory and I/O performance with a kvm domain on CentOS 6.4. > > > http://www.virtuatopia.com/index.php/Building_a_Xen_Virtual_Guest_Filesystem_on_a_Disk_Image_%28Cloning_Host_System%29 > > In the initial tests whit super.pi benchmarck the CPU performance of my > xen domai was extremely worst than my kvm domain. > > Well, I am think that maybe, something was wrong in my xen setup. So I > decided to boot a new xen guest using a logical volume filesystem instead a > disk image, to see whether CPU performance will be better. But this setup > is not working > > That is the error (when I try to create a guest domain with a logical > volume filesystem): > Anyone knows what i need to do tho solve this problem? > > > [root@xen]# xm create xen-pv01.cfg -c > Using config file "./xen-pv01.cfg". > . > . > . > EXT3-fs (xvda1): mounted filesystem with ordered data mode > dracut: Mounted root filesystem /dev/xvda1 > *dracut: chroot: failed to run command `/sbin/load_policy'': No such file > or directory* > dracut: Switching root > *Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100* > > Pid: 1, comm: switch_root Not tainted 3.7.1-3.el6xen.x86_64 #1 > Call Trace: > [<ffffffff8149d541>] panic+0xc4/0x1d6 > [<ffffffff81047131>] do_exit+0x3a5/0x834 > [<ffffffff8111e70f>] ? vfs_write+0xd2/0x10a > [<ffffffff8104763d>] do_group_exit+0x7d/0xa5 > [<ffffffff8104767c>] sys_exit_group+0x17/0x1b > [<ffffffff814a6899>] system_call_fastpath+0x16/0x1b > > > > I''ve created a logical volume for my Xen guest system following the > instructions of this article: > > > http://www.virtuatopia.com/index.php/Building_a_Xen_Virtual_Guest_Filesystem_using_Logical_Volume_Management_%28LVM%29 > > And that is my Xen configuration file: > > name = "xen-pv01" > kernel = "/boot/vmlinuz-3.7.1-3.el6xen.x86_64" > ramdisk = "/boot/initrd-3.7.1-3.el6xen.x86_64-no-scsi.img" > memory = 4000 > vif = [''bridge=xenbr0, ip=192.168.0.20''] > vcpus = 1 > disk = [''phy:vg_xen/lvxenteste,xvda1,w''] > root = "/dev/xvda1 ro" > > > And my Dom0 configuration: > > default=0 > timeout=5 > selinux=0 > splashimage=(hd0,0)/grub/splash.xpm.gz > hiddenmenu > title CentOS (3.7.1-3.el6xen.x86_64) > root (hd0,0) > kernel /xen.gz dom0_mem=40000M cpufreq=xen dom0_max_vcpus=1 > dom0_vcpus_pin > module /vmlinuz-3.7.1-3.el6xen.x86_64 ro > root=/dev/mapper/vg_xen-lvroot rd_NO_LUKS LANG=en_US.UTF-8 KEYBOARDTYPE=pc > KEYTABLE=us-acentos rd_NO_MD SYSFONT=latarcyrheb-sun16 crashkernel=auto > rd_LVM_LV=vg_xen/lvroot rd_NO_DM rhgb quiet > module /initramfs-3.7.1-3.el6xen.x86_64.img > > > *Am I missing something* > > > -- > Leo > >_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users