Re: HVM hypercalls

[Jeremy Fitzhardinge <jeremy@goop.org>]

  On 08/03/2010 12:48 PM, Ruslan Nikolaev wrote:
> I've just tried to configure newever version (2.6.32.16) from repositary. However, boot fails because no root device is found. I am using disk image (the line in HVM config is disk = [ 'file:/home/ruslan/fs1.img,hda,w' ])
> I also tried to compile kernel with 'blktap' driver which is disabled in default kernel config, but it does not help.

What is your root= parameter?  If you're using pv-on-hvm drivers, then 
the device will be named /dev/xvd[a-d] (for the moment).  It's very 
strongly recommended that you don't use a device-based root name (ie, 
use LABEL= UUID= or LVM for your root device) so that your config is 
failsafe against root device name changes.

     J

> The previous version (2.6.31.13) worked fine with the same disk image and default configuration.
>
> Thanks,
> Ruslan.
>
> --- On Sat, 7/31/10, Jeremy Fitzhardinge<jeremy@goop.org>  wrote:
>
>> From: Jeremy Fitzhardinge<jeremy@goop.org>
>> Subject: Re: [Xen-devel] HVM hypercalls
>> To: "Ruslan Nikolaev"<nruslan_devel@yahoo.com>
>> Cc: xen-devel@lists.xensource.com
>> Date: Saturday, July 31, 2010, 4:07 AM
>>    On 07/30/2010 09:06 AM, Ruslan
>> Nikolaev wrote:
>>> I have 2 kernels:
>>>
>>> 1. From Xen repositary pvops-git (2.6.31.13).
>> You want 2.6.32.16 from xen.git - the branch is
>> xen/stable-2.6.32.x
>>
>>       J
>>
>>> 2. From kernel.org: 2.6.32.16
>>>
>>> Thank you!
>>> Ruslan.
>>>
>>>
>>> --- On Thu, 7/29/10, Jeremy Fitzhardinge<jeremy@goop.org>
>> wrote:
>>>> From: Jeremy Fitzhardinge<jeremy@goop.org>
>>>> Subject: Re: [Xen-devel] HVM hypercalls
>>>> To: "Ruslan Nikolaev"<nruslan_devel@yahoo.com>
>>>> Cc: xen-devel@lists.xensource.com
>>>> Date: Thursday, July 29, 2010, 11:47 PM
>>>>     On 07/29/2010 11:55 AM, Ruslan
>>>> Nikolaev wrote:
>>>>> Thank you very much! I'll try this. BTW is it
>> required
>>>> to do this for every module with HVM hypercalls or
>> there is
>>>> some shared initialization code in HVM guest
>> (Linux) similar
>>>> to one used in paravirtualized guests?
>>>>> If it's supposed to be in a module, is there
>> any good
>>>> example I can look at?
>>>>> AFAIK hypercall_page is being initialized on
>> Xen side
>>>> with appropriate vmcall/vmmcall code. Is this
>> CPUID
>>>> mechanism a standard way to obtain hypercall_page
>> reference
>>>> on HVM domain?
>>>>
>>>> What kernel are you working with?  There's
>> already
>>>> code to implement pv-on-hvm support for various
>> recent pvops
>>>> kernels, so you can just base your work on those.
>>>>
>>>>        J
>>>>
>>>>
>>>
>>>
>>> _______________________________________________
>>> Xen-devel mailing list
>>> Xen-devel@lists.xensource.com
>>> http://lists.xensource.com/xen-devel
>>>
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
>>
>
>
>