Re: [Xen-devel] High-load Domain0 cause guest domian panic.

[Hidetoshi Nishi <nishi.hidetoshi@xxxxxxxxxxxxxx>]

Hi Keir-san,

Thank you for your quick return.

We will make PV on HVM and test it.

Thanks a lot.                                 Nishi

>Well, there was a race where we did not wait until the root disk's partition
>table had been read. So you may find the problem is fixed by changeset 82 in
>linux-2.6.18-xen.hg.
>
> -- Keir
>
>On 12/7/07 11:14, "Hidetoshi Nishi" <nishi.hidetoshi@xxxxxxxxxxxxxx> wrote:
>
>> Hi Keir-san, Simon-san
>> 
>> Even now I have concern about this problem.
>> 
>> Keir-san said,
>>> The domU kernel will already wait for all devices it discovers to enter
>>> connected state. If that timeoutÂs not long enough we could make it longer,
>>> or configurable on the domU command line.
>>> 
>>> -- Keir
>> 
>> Please let me know how to fix this problem on domU in detail.
>> We will try to convert the logic with domU to with domVTx and domVTi.
>> 
>> 
>> Thank you.                                           Nishi
>> 
>> 
>>> 
>>> On 18/4/07 13:31, "Graham, Simon" <Simon.Graham@xxxxxxxxxxx> wrote:
>>> 
>>>> See http://lists.xensource.com/archives/html/xen-devel/2006-12/msg00136.
>>>> html
>>>> for some discussion on this - no resolution though.
>>>>  
>>>>  Simon
>>>> 
>>>> 
>>>> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx on behalf of Hidetoshi Nishi
>>>> Sent: Tue 17/04/2007 8:53 AM
>>>> To: xen-devel@xxxxxxxxxxxxxxxxxxx
>>>> Subject: [Xen-devel] High-load Domain0 cause guest domian panic.
>>>> 
>>>> 
>>>> 
>>>> Hi all.
>>>> 
>>>> Currently we are investigating guest domain panic.
>>>> 
>>>> When guest domain whose root disk is VBD is created,
>>>> domain0 with high-load gets late to initiate the
>>>> back-end driver. And guest domain can not mount
>>>> his root file system and goes into panic.
>>>> 
>>>> We think domain initial sequence have to wait to be ready
>>>> of special device(root disk, etc).
>>>> And we should be able to specify special device in config file.
>>>> 
>>>> Do you have any idea ?
>>>> 
>>>> 
>>>> Thank you.                    Nishi
>>>> 
>>>> 
>>>> 
>>>> 
>>>> _______________________________________________
>>>> Xen-devel mailing list
>>>> Xen-devel@xxxxxxxxxxxxxxxxxxx
>>>> http://lists.xensource.com/xen-devel
>>>> 
>>>> 
>>>> 
>>>> _______________________________________________
>>>> Xen-devel mailing list
>>>> Xen-devel@xxxxxxxxxxxxxxxxxxx
>>>> http://lists.xensource.com/xen-devel
>>> 
>> 
>> 



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