[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] HVM hypercalls


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: Ruslan Nikolaev <nruslan_devel@xxxxxxxxx>
  • Date: Fri, 6 Aug 2010 14:58:20 -0700 (PDT)
  • Delivery-date: Fri, 06 Aug 2010 15:00:05 -0700
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=Rii2q9cMnb/3o+dolsMEdDc8+mk1cqelSewESAZIE5xZ45wxmTi4og6XoYE4zcE8fJr0Xf/Z4Ff+IA2BO36jupLcSq56k8kSXjBtUoHSQXESP2PAsem6xSFrXaEkXSFlITC/4OMRlozb8quEeWNWPRCL9MqpPRO7HRezg97tNwo=;
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

I tried these configs. The same result - it does not find root device.

However, if I disable 'CONFIG_XEN_PLATFORM_PCI', everything works. I can see my 
disk as /dev/sda.

If CONFIG_XEN_PLATFORM_PCI is enabled (by default), virtual ATA device appears, 
I can see GRUB, load the kernel. But when kernel tries to mount root device, it 
cannot find it. There is no /dev/xvda*, no /dev/hda*, no /dev/sda*, nothing! 
Apparently, it's a problem with actual kernel disk driver (not configuration). 
I get the same result also if I specify physical device.

Also, I noted weird messages in dom0:
XENBUS: Unable to read cpu state

P.S. For HVM domain I use Ubuntu 9.04

Thanks,
Ruslan.



--- On Thu, 8/5/10, Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx> wrote:

> From: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
> Subject: Re: [Xen-devel] HVM hypercalls
> To: "Ruslan Nikolaev" <nruslan_devel@xxxxxxxxx>
> Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Jeremy 
> Fitzhardinge" <jeremy@xxxxxxxx>
> Date: Thursday, August 5, 2010, 2:31 PM
> On Wed, 4 Aug 2010, Ruslan Nikolaev
> wrote:
> > Yes, I tried this but it does not seem to work. BTW in
> paravirtualized mode it works fine, the problem is only with
> HVM.
> > 
> > I tried to specify root=/dev/xvda (my disk image has
> no partitions, entire disk image is a single file system).
> > 
> 
> If your disk file represents a single partition and in your
> pv config file you
> have a disk entry like this one:
> 
> disk = [ 'file:/home/ruslan/fs1.img,xvda1,w' ]
> 
> then your disk is not going to work in HVM mode.
> Qemu must be able to handle your disk otherwise the
> bootloader won't be
> able to boot your kernel.
> 
> 
> > My config is (I also tried to comment out device model
> but it does not help):
> > 
> > import os, re
> > arch = os.uname()[4]
> > if re.search('64', arch):
> >     arch_libdir = 'lib64'
> > else:
> >     arch_libdir = 'lib'
> > 
> 
> remove this part if you are using xl
> 
> > kernel = "/usr/lib/xen/boot/hvmloader"
> > 
> > builder='hvm'
> > 
> > vcpus=1
> > 
> > memory = 1024
> > shadow_memory = 8
> > name = "xenhvm1"
> > disk = [ 'file:/home/ruslan/fs1.img,xvda,w' ]
> 
> Even though xvda is currently supported it would be better
> to specify
> hda here if you only have one disk, because you need at
> least an IDE
> interface to boot.
> 
> > device_model = '/usr/' + arch_libdir +
> '/xen/bin/qemu-dm'
> 
> device_model='qemu-dm' especially if you are using xl
> 
> 
>






_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.