<div dir="ltr">Hi<div><br></div><div>Can you send the deployment.0 file generated by opennebula, and the one that you are using for 'xm create' to succeed ? <br><br></div><div>Cheers<br><br>Ruben<br></div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Fri, May 3, 2013 at 11:12 AM, Sam Ho <span dir="ltr"><<a href="mailto:sammhho@gmail.com" target="_blank">sammhho@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Hi there,<div><br></div><div>Could someone please shed some light ? I'm stuck with this for more than a week now.</div><div>Suggestions on how I go about debugging is good enough.</div><div>
<br></div><div>Have OpenNebula 3.8.3 installed using the official .deb, on a Ubuntu 12.04.2 LTS as Xen Dom0.</div><div>Trying to boot into several DomUs created with xen-tools 'xen-create-image', on the same machine.</div>
<div>DomUs are Ubuntu Lucid and Centos-5.</div><div>I can boot into these DomUs using 'xm create' through Pygrub or kernel, and they run perfectly fine.</div><div>But when I do 'onevm create' or 'onetemplate instantiate', they either won't boot (for pygrub cases) or stop at the initramfs shell (for kernel boot cases).</div>
<div><br></div><div>For the kernel boot case, 'onevm list' show the DomU running, but when I do 'xm console' into it it says:</div><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px">
<div><div>[ 0.725043] registered taskstats version 1</div></div><div><div><b>[ 0.725051] XENBUS: Device with no driver: device/vbd/51714</b></div></div><div><div><b>[ 0.725053] XENBUS: Device with no driver: device/vbd/51713</b></div>
</div><div><div><b>[ 0.725056] XENBUS: Device with no driver: device/vif/0</b></div></div><div><div><b>[ 0.725058] XENBUS: Device with no driver: device/console/0</b></div></div><div><div>
[ 0.725068] Magic number: 1:252:3141</div></div><div><div>[ 0.725076] /build/buildd/linux-2.6.32/drivers/rtc/hctosys.c: unable to open rtc device (rtc0)</div></div><div><div>[ 0.725081] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found</div>
</div><div><div>[ 0.725083] EDD information not available.</div></div><div><div>[ 0.731969] Freeing initrd memory: 22736k freed</div></div><div><div>[ 0.735010] Freeing unused kernel memory: 808k freed</div>
</div><div><div>[ 0.735151] Write protecting the kernel read-only data: 7840k</div></div><div><div>Loading, please wait...</div></div><div><div>Begin: Loading essential drivers... ...</div>
</div><div><div>Done.</div></div><div><div>[ 0.757035] udev: starting version 151</div></div><div><div>Begin: Running /scripts/init-premount ...</div></div><div><div>Done.</div>
</div><div><div>Begin: Mounting root file system... ...</div></div><div><div>Begin: Running /scripts/local-top ...</div></div><div><div>Done.</div></div><div><div>[ 0.839045] blkfront: xvda2: barriers enabled</div>
</div><div><div>[ 0.849632] blkfront: xvda1: barriers enabled</div></div><div><div><b>Begin: Running /scripts/local-premount ...</b></div></div><div><div><b>Done.</b></div></div><div>
<div><b>[ 30.834922] end_request: I/O error, dev xvda2, sector 2</b></div></div><div><div><b>[ 30.834955] EXT3-fs: unable to read superblock</b></div></div><div><div><b>[ 30.841804] end_request: I/O error, dev xvda2, sector 2</b></div>
</div><div><div><b>[ 30.841832] EXT2-fs: unable to read superblock</b></div></div><div><div><b>[ 30.849824] end_request: I/O error, dev xvda2, sector 2</b></div></div><div><div><b>[ 30.849855] EXT4-fs (xvda2): unable to read superblock</b></div>
</div><div><div><b>mount: mounting /dev/xvda2 on /root failed: Invalid argument</b></div></div><div><div>Begin: Running /scripts/local-bottom ...</div></div><div><div>Done.</div></div><div>
<div>Done.</div></div><div><div>Begin: Running /scripts/init-bottom ...</div></div><div><div>mount: mounting /dev on /root/dev failed: No such file or directory</div></div><div><div>
Done.</div></div><div><div>mount: mounting /sys on /root/sys failed: No such file or directory</div></div><div><div>mount: mounting /proc on /root/proc failed: No such file or directory</div></div>
<div><div>Target filesystem doesn't have /sbin/init.</div></div><div><div>No init found. Try passing init= bootarg.</div><div><div>BusyBox v1.13.3 (Ubuntu 1:1.13.3-1ubuntu11) built-in shell (ash)</div>
<div>Enter 'help' for a list of built-in commands.</div><div><br></div><div>(initramfs)</div></div></div></blockquote><div><div><br></div><div>I read from somewhere that the XENBUS lines could be fine, </div>
<div>so what's the problem about <b>unable to read superblock</b>?</div><div><br></div><div>Here is the onetemplate, kernels were copied from inside the DomU to the /boot in Dom0,:</div></div><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px">
<div><div><div>NAME = vm02</div></div></div><div><div><div>CPU = 1</div></div></div><div><div><div>MEMORY = 512</div></div></div><div><div><div>
<br></div></div></div><div><div><div>#OS = [ bootloader = /usr/lib/xen-default/bin/pygrub,</div></div></div><div><div><div>OS = [ kernel = /boot/vmlinuz-2.6.32-46-server,</div></div></div>
<div><div><div> initrd = /boot/initrd.img-2.6.32-46-server,</div></div></div><div><div><div> root = "xvda2",</div></div></div><div><div><div> KERNEL_CMD = "ro" ]</div>
</div></div><div><div><div><br></div></div></div><div><div><div>DISK = [ IMAGE_ID = 3 ]</div></div></div><div><div><div><br></div></div></div><div><div><div>
DISK = [ type = swap,</div></div></div><div><div><div> size = 512,</div></div></div><div><div><div> target = "xvda1",</div></div></div><div><div><div>
readonly = "no" ]</div></div></div><div><div><div><br></div></div></div><div><div><div>NIC = [ IP="147.8.183.150", MAC="08:00:27:C8:EB:ED", bridge=xenbr0 ]</div>
</div></div><div><div><div>RAW = [ type="xen", data="on_crash='restart'" ]</div></div></div></blockquote><div><div><div><br></div><div>And the disk image was imported with:</div>
</div></div><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px"><div><div><div><div>NAME = "vm02_img"</div></div></div></div><div><div><div><div>
PATH = /home/xen/domains/vm02/disk.img</div></div></div></div><div><div><div><div>TYPE = OS</div></div></div></div><div><div><div><div>DEV_PREFIX = "xdv"</div>
</div></div></div><div><div><div><div>TARGET = "xvda2"</div></div></div></div><div><div><div><div>DRIVER = file:</div></div></div></div></blockquote><div><br>
</div><div>I compared the xend.log messages for successful boot by 'xm create' with failed boot by 'onevm create', doesn't seem to have much difference...</div><div><br></div><div>For the Pygrub boot case, there seem to be no way to pass '<b>root=/dev/xvda2 ro</b>' to Pygrub from OpenNebula? </div>
<div>In xend.log it says:</div><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px"><div>[2013-05-03 01:10:38 20461] DEBUG (XendBootloader:113) Launching bootloader as ['/usr/lib/xen-default/bin/pygrub', '--output=/var/run/xend/boot/xenbl.15718', '-q', '/var/lib/one//datastores/0/17/disk.0'].</div>
</blockquote><div><br></div><div>And eventually it returns:</div><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px"><div><div>[2013-05-03 01:10:38 15927] ERROR (XendBootloader:214) Boot loader didn't return any data!</div>
</div><div><div>[2013-05-03 01:10:38 15927] ERROR (XendDomainInfo:488) VM start failed</div></div><div><div>Traceback (most recent call last):</div></div><div><div> File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendDomainInfo.py", line 474, in start</div>
</div><div><div> XendTask.log_progress(31, 60, self._initDomain)</div></div><div><div> File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendTask.py", line 209, in log_progress</div></div>
<div><div> retval = func(*args, **kwds)</div></div><div><div> File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendDomainInfo.py", line 2838, in _initDomain</div></div><div><div>
self._configureBootloader()</div></div><div><div> File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendDomainInfo.py", line 3285, in _configureBootloader</div></div><div><div> bootloader_args, kernel, ramdisk, args)</div>
</div><div><div> File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendBootloader.py", line 215, in bootloader</div></div><div><div> raise VmError, msg</div></div><div><div>
VmError: Boot loader didn't return any data!</div></div></blockquote><div><div><br></div></div><div>Where in a successful boot with 'xm create' it is:</div><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px">
<div>[2013-05-03 01:13:01 20522] DEBUG (XendBootloader:113) Launching bootloader as ['/usr/lib/xen-default/bin/pygrub', <b>'--args=root=/dev/xvda2 ro '</b>, '--output=/var/run/xend/boot/xenbl.9704', '-q', '/home/xen/domains/vm02/disk.img'].</div>
</blockquote><div><br></div><div>Any suggestions on how I can debug these?</div><div>Sorry for writing such a long post...</div><div><br></div><div>Best regards,</div><div>Sam Ho</div><div>
<br></div><div><br></div><div><br></div></div>
<br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opennebula.org">Users@lists.opennebula.org</a><br>
<a href="http://lists.opennebula.org/listinfo.cgi/users-opennebula.org" target="_blank">http://lists.opennebula.org/listinfo.cgi/users-opennebula.org</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>Ruben S. Montero, PhD<br>Project co-Lead and Chief Architect<br>OpenNebula - The Open Source Solution for Data Center Virtualization<br><a href="http://www.OpenNebula.org" target="_blank">www.OpenNebula.org</a> | <a href="mailto:rsmontero@opennebula.org" target="_blank">rsmontero@opennebula.org</a> | @OpenNebula
</div>