Luceo Astrum
2012-Jul-20 07:56 UTC
RuntimeError: Unable to find partition containing kernel
Hardware: 2x Intel Xeon Quad-Core 2.33GHz 24GB FBDIMM RAM 2x 2TB HDD in RAID-1 Intel Server Board S5400SF Setup: Arch Linux x86_64 Xen 4.1.2 Grub2 Multiboot Synopsis: I set up a new VM for Debian Squeeze following instructions here: howtoforge.com/installing-debian-squeeze-6.0-domu-on-centos-5.5-x86_64-dom0. Partitioning & installation completed correctly. When I tried to run the VPS afterwards, I got this output: | [root@srv0 xen]# xm create -c /etc/xen/xm-debian.cfg | Using config file "/etc/xen/xm-debian.cfg". | Error: Boot loader didn''t return any data! I''ve attached a more complete log output at the end of the mail. This is the first VM I have tried to create on this setup. Additional: I can mount the partition within the lvm: | [root@srv0 xen]# kpartx -av /dev/VPS/fennec | add map VPS-fennec1 (253:2): 0 83881984 linear /dev/VPS/fennec 2048 | [root@srv0 xen]# mount /dev/mapper/VPS-fennec1 /mnt | [root@srv0 xen]# cd /mnt | [root@srv0 mnt]# ls | bin etc lib lost+found opt sbin sys var | boot home lib32 media proc selinux tmp vmlinuz | dev initrd.img lib64 mnt root srv usr | [root@srv0 mnt]# cd boot | [root@srv0 boot]# ls | config-2.6.32-5-amd64 initrd.img-2.6.32-5-amd64 vmlinuz-2.6.32-5-amd64 | grub System.map-2.6.32-5-amd64 | initrd vmlinuz | [root@srv0 boot]# cd grub | [root@srv0 grub]# cat menu.lst | timeout 5 | default 0 | | title Linux | kernel /boot/vmlinuz root=/dev/xvda1 | initrd /boot/initrd As you can see, the kernel (which is 2.6.32) and vmlinuz (also 2.6.32) exist in the /boot directory. Pygrub: Attempting to pygrub the VPS LVM gives the following output: | [root@srv0 /]# pygrub --kernel=/boot/vmlinuz --ramdisk=/boot/initrd /dev/VPS/fennec | Traceback (most recent call last): | File "/usr/bin/pygrub", line 774, in <module> | raise RuntimeError, "Unable to find partition containing kernel" | RuntimeError: Unable to find partition containing kernel domU Config File: | name = "fennec" | memory = 1024 | maxmem = 1024 | cpus = "2-7" | disk = [ | ''phy:/dev/VPS/fennec,xvda,w'', | ''phy:/dev/VPS/fennec-swap,xvdb,w'' | ] | vif = [''''] | bootloader = "pygrub" | bootargs = "--kernel=/boot/vmlinuz --ramdisk=/boot/initrd" I have tried this with and without the bootargs line without any success. About The Filesystem: /dev/VPS is a vg on a RAID-1 array /dev/VPS/fennec is an lv on VPS vg The fennec lv has a single ext3 partition of 40GB xend.log Output: [2012-07-20 09:35:17 907] DEBUG (XendDomainInfo:103) XendDomainInfo.create([''vm'', [''name'', ''fennec''], [''memory'', 1024], [''maxmem'', 1024], [''on_xend_start'', ''ignore''], [''on_xend_stop'', ''ignore''], [''vcpus'', 1], [''cpus'', ''2-7''], [''oos'', 1], [''bootloader'', ''/usr/bin/pygrub''], [''bootloader_args'', ''--kernel=/boot/vmlinuz --ramdisk=/boot/initrd''], [''image'', [''linux'', [''videoram'', 4], [''tsc_mode'', 0], [''nomigrate'', 0]]], [''s3_integrity'', 1], [''device'', [''vbd'', [''uname'', ''phy:/dev/VPS/fennec''], [''dev'', ''xvda''], [''mode'', ''w'']]], [''device'', [''vbd'', [''uname'', ''phy:/dev/VPS/fennec-swap''], [''dev'', ''xvdb''], [''mode'', ''w'']]], [''device'', [''vif'']]]) [2012-07-20 09:35:17 907] DEBUG (XendDomainInfo:2498) XendDomainInfo.constructDomain [2012-07-20 09:35:17 907] DEBUG (balloon:187) Balloon: 22794808 KiB free; need 16384; done. [2012-07-20 09:35:17 907] DEBUG (XendDomain:476) Adding Domain: 17 [2012-07-20 09:35:17 907] DEBUG (XendDomainInfo:2836) XendDomainInfo.initDomain: 17 256 [2012-07-20 09:35:17 25157] DEBUG (XendBootloader:113) Launching bootloader as [''/usr/bin/pygrub'', ''--output=/var/run/xend/boot/xenbl.15844'', ''--kernel=/boot/vmlinuz'', ''--ramdisk=/boot/initrd'', ''/dev/VPS/fennec'']. [2012-07-20 09:35:17 907] ERROR (XendBootloader:214) Boot loader didn''t return any data! [2012-07-20 09:35:17 907] ERROR (XendDomainInfo:488) VM start failed Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/xen/xend/XendDomainInfo.py", line 474, in start XendTask.log_progress(31, 60, self._initDomain) File "/usr/lib/python2.7/site-packages/xen/xend/XendTask.py", line 209, in log_progress retval = func(*args, **kwds) File "/usr/lib/python2.7/site-packages/xen/xend/XendDomainInfo.py", line 2838, in _initDomain self._configureBootloader() File "/usr/lib/python2.7/site-packages/xen/xend/XendDomainInfo.py", line 3285, in _configureBootloader bootloader_args, kernel, ramdisk, args) File "/usr/lib/python2.7/site-packages/xen/xend/XendBootloader.py", line 215, in bootloader raise VmError, msg VmError: Boot loader didn''t return any data! [2012-07-20 09:35:17 907] DEBUG (XendDomainInfo:3071) XendDomainInfo.destroy: domid=17 [2012-07-20 09:35:17 907] DEBUG (XendDomainInfo:2406) No device model [2012-07-20 09:35:17 907] DEBUG (XendDomainInfo:2408) Releasing devices [2012-07-20 09:35:17 907] ERROR (XendDomainInfo:108) Domain construction failed Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/xen/xend/XendDomainInfo.py", line 106, in create vm.start() File "/usr/lib/python2.7/site-packages/xen/xend/XendDomainInfo.py", line 474, in start XendTask.log_progress(31, 60, self._initDomain) File "/usr/lib/python2.7/site-packages/xen/xend/XendTask.py", line 209, in log_progress retval = func(*args, **kwds) File "/usr/lib/python2.7/site-packages/xen/xend/XendDomainInfo.py", line 2838, in _initDomain self._configureBootloader() File "/usr/lib/python2.7/site-packages/xen/xend/XendDomainInfo.py", line 3285, in _configureBootloader bootloader_args, kernel, ramdisk, args) File "/usr/lib/python2.7/site-packages/xen/xend/XendBootloader.py", line 215, in bootloader raise VmError, msg VmError: Boot loader didn''t return any data! Appreciate any suggestions. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org lists.xen.org/xen-users
Maybe Matching Threads
- domUs doesn''t boot after upgrade to xen 3.2
- Successfully running VM, subsequently startup gives this error -- VmError: Boot loader didn''t return any data!
- Bug#644100: pygrub error if the root disk value is not the first in the list.
- Bug#644100: Boot loader didn't return any data! if reboot domU with disk DRBD
- [Q] VmError: Disk isn''t accessible with tap2:tapdisk:vhd