<HTML>
<HEAD>
<TITLE>Re: [Openstack] Ubuntu run instance error + xen</TITLE>
</HEAD>
<BODY>
<FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Here is also the libvirt.xml section that might be useful:<BR>
<BR>
$ more instance-00000033/libvirt.xml <BR>
<domain type='xen'><BR>
<name>instance-00000033</name><BR>
<memory>524288</memory><BR>
<os><BR>
<type>linux</type><BR>
<root>/dev/xvda</root><BR>
<kernel>/home/ctoteam/nova/nova/..//instances/instance-00000033/kernel</kernel><BR>
<cmdline>ro</cmdline><BR>
</os><BR>
<features><BR>
<acpi/><BR>
</features><BR>
<vcpu>1</vcpu><BR>
<devices><BR>
<disk type='file'><BR>
<driver type='raw'/><BR>
<source file='/home/ctoteam/nova/nova/..//instances/instance-00000033/disk'/><BR>
<target dev='sda' bus='scsi'/><BR>
</disk><BR>
<BR>
<BR>
<BR>
On 8/22/11 11:28 AM, "Joshua Harlow" <<a href="harlowja@yahoo-inc.com">harlowja@yahoo-inc.com</a>> wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Attempting to follow your notes.<BR>
<BR>
I have the following ubuntu kernel.<BR>
<BR>
Linux version 2.6.35-24-virtual<BR>
<BR>
This is just a standard ubuntu UEC image.<BR>
<BR>
With command line options.<BR>
<BR>
Command line: root=/dev/xvda ro<BR>
<BR>
I’ve got a dom0 running with the following.<BR>
<BR>
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-xen-amd64 and XEN 4.0-amd64' --class debian --class gnu-linux --class gnu --class os --class xen {<BR>
<BR>
Which seems to be right. <BR>
<BR>
The following error still occurs.<BR>
<BR>
[ 0.190303] md: Waiting for all devices to be available before autodetect<BR>
[ 0.190315] md: If you don't use raid, use raid=noautodetect<BR>
[ 0.190508] md: Autodetecting RAID arrays.<BR>
[ 0.190520] md: Scanned 0 and added 0 devices.<BR>
[ 0.190528] md: autorun ...<BR>
[ 0.190534] md: ... autorun DONE.<BR>
[ 0.190629] VFS: Cannot open root device "xvda" or unknown-block(0,0)<BR>
[ 0.190641] Please append a correct "root=" boot option; here are the available partitions:<BR>
[ 0.190658] ca00 1441792 sda driver: vbd<BR>
[ 0.190671] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)<BR>
[ 0.190683] Pid: 1, comm: swapper Not tainted 2.6.35-24-virtual #42-Ubuntu<BR>
[ 0.190693] Call Trace:<BR>
<BR>
When switching it to sda it works though. Following your notes it seems like the dom0 kernel version shouldn’t be having this issue?<BR>
<BR>
<a href="http://lists.debian.org/debian-l10n-english/2010/12/msg00059.html">http://lists.debian.org/debian-l10n-english/2010/12/msg00059.html</a> <BR>
<BR>
On 8/20/11 6:53 AM, "Thomas Goirand" <<a href="thomas@goirand.fr">thomas@goirand.fr</a>> wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>On 08/20/2011 05:40 AM, Joshua Harlow wrote:<BR>
> So what I’ve figured out is the following seems to work with xen4.<BR>
<BR>
The naming of sda vs xvda has nothing to do with the hypervisor, and a<BR>
lot to do with your kernel.<BR>
<BR>
Thomas<BR>
<BR>
<BR>
</SPAN></FONT></BLOCKQUOTE></BLOCKQUOTE>
</BODY>
</HTML>