<div dir="ltr">The OpenSUSE image and target device (xvda) are meant to be used with xen. In fact KVM does not know about xen virtual devices (xvd*)<div><br></div><div style>Can you send me the output of:</div><div style><br>
</div><div style>$ file <span style="font-size:13px;font-family:arial,sans-serif">/var/lib/one/datastores/1/</span><span style="font-size:13px;font-family:arial,sans-serif">19f921a2c46ac299b7a02bc79d6055</span><span style="font-size:13px;font-family:arial,sans-serif">9e</span></div>
<div style><span style="font-size:13px;font-family:arial,sans-serif"><br></span></div><div style><span style="font-size:13px;font-family:arial,sans-serif">That problem with CentOS is a bit more strange.</span></div><div style>
<span style="font-size:13px;font-family:arial,sans-serif"><br></span></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Mar 27, 2013 at 10:21 PM, Martin Klepáč <span dir="ltr"><<a href="mailto:klepamar@gmail.com" target="_blank">klepamar@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br><br>I have recently installed OpenNebula 3.8.3 on three hosts (one acting as the frontend, two hosts running KVM hypervisor - all Ubuntu 12.04). I have downloaded several images from the C12G marketplace such as ttylinux, Ubuntu 12.04, Debian Squeeze, CentOS or OpenSuse. While ttylinux, Ubuntu and CentOS are successfully instantiated, I have problems booting Debian and OpenSuse.<br>
<br>VNC reveals that the systems cannot boot from the designated image.<br>"Booting from Hard Disk...<br>Boot failed: could not read the boot disk"<br><br>Both Debian and Opensuse images have a non-default disk device as shown in marketplace:<br>
OpenSuse (xvda): <a href="http://marketplace.c12g.com/appliance/4feb28bc8fb81d63da000001" target="_blank">http://marketplace.c12g.com/appliance/4feb28bc8fb81d63da000001</a><br>Debian (sda): <a href="http://marketplace.c12g.com/appliance/5000348d8fb81d4ba8000001" target="_blank">http://marketplace.c12g.com/appliance/5000348d8fb81d4ba8000001</a><br>
<br>Debian disk image as registered in my cloud:<br>$ oneimage show 9<br>IMAGE 9 INFORMATION <br>ID : 9 <br>NAME : debian <br>
USER : oneadmin <br>GROUP : oneadmin <br>DATASTORE : default <br>TYPE : OS <br>REGISTER TIME : 03/26 20:15:51 <br>PERSISTENT : No <br>
SOURCE : /var/lib/one/datastores/1/19f921a2c46ac299b7a02bc79d60559e<br>PATH : /images/debian/debian.img<br>SIZE : 8G <br>STATE : used <br>RUNNING_VMS : 1 <br>
<br>PERMISSIONS <br>OWNER : um- <br>GROUP : --- <br>OTHER : --- <br><br>IMAGE TEMPLATE <br>
DEV_PREFIX="hd"<br><br>OpenSuse image as registered in my cloud:<br>$ oneimage show 11<br>IMAGE 11 INFORMATION <br>ID : 11 <br>
NAME : opensuse <br>USER : oneadmin <br>GROUP : oneadmin <br>DATASTORE : default <br>TYPE : OS <br>REGISTER TIME : 03/26 22:21:35 <br>
PERSISTENT : No <br>SOURCE : /var/lib/one/datastores/1/365ba4bf05f157eca6e45507867a185a<br>PATH : /images/opensuse/opensuse.img<br>SIZE : 8G <br>STATE : used <br>
RUNNING_VMS : 1 <br><br>PERMISSIONS <br>OWNER : um- <br>GROUP : --- <br>OTHER : --- <br>
<br>IMAGE TEMPLATE <br>DEV_PREFIX="hd"<br><br><br>Instead of relying on templates, I use the following files for instantiating respective images. I assumed that adding TARGET variable in DISK section would do the trick, but obviously I am missing something...<br>
$ cat debian_new.one<br>NAME = debian<br>CPU = 1<br>VCPU = 2<br>MEMORY = 512<br>DISK = [ IMAGE_ID = 9,<br> target = "sda" ]<br><br>OS = [ ARCH = "x86_64" ]<br><br>NIC = [ NETWORK_ID = 1 ]<br>
<br>FEATURES=[ acpi="no" ]<br><br>GRAPHICS=[ type = "vnc",<br> listen = "0.0.0.0" ]<br><br>RAW = [ type = "kvm", data = " <serial type='pty'> <source path='/dev/pts/3'/> <target port='1'/> </serial>" ]<br>
<br><br>$ cat opensuse_new.one<br>NAME = opensuse<br>CPU = 1<br>VCPU = 2<br>MEMORY = 512<br><br>OS = [ ARCH = "x86_64" ]<br><br>DISK = [ IMAGE_ID = 11,<br> TARGET = xvda ]<br><br>NIC = [ NETWORK_ID = 1 ]<br>
<br>FEATURES=[ acpi="no" ]<br><br>GRAPHICS=[ type = "vnc",<br> listen = "0.0.0.0" ]<br><br><br>Then, I instantiate the VM by issuing $ onevm create {debian_new.one|opensuse_new.one}<br>
The instance turns into running state, but VNC discloses the issue depicted above.<br><br><br>BTW - as setting up OpenNebula is a part of my bachelor's thesis (comparison of private IaaS clouds), I would say that in comparison to other solutions such as OpenStack OpenNebula is very user-friendly in terms of installation complexity. However, I do not understand why the images provided in the marketplace do not have a compulsory template to them ;(<br>
<br><br>Thank you for any suggestions,<br><br>Martin Klepac<br>
<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"><div><br></div>-- <br>Javier Fontán Muiños<br>Project Engineer<br>OpenNebula - The Open Source Toolkit for Data Center Virtualization<br><a href="http://www.OpenNebula.org" target="_blank">www.OpenNebula.org</a> | <a href="mailto:jfontan@opennebula.org" target="_blank">jfontan@opennebula.org</a> | @OpenNebula
</div>