Hidetoshi Nishi
2007-Apr-17 12:53 UTC
[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@lists.xensource.com http://lists.xensource.com/xen-devel
Graham, Simon
2007-Apr-18 12:31 UTC
RE: [Xen-devel] High-load Domain0 cause guest domian panic.
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@lists.xensource.com on behalf of Hidetoshi Nishi Sent: Tue 17/04/2007 8:53 AM To: xen-devel@lists.xensource.com 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@lists.xensource.com http://lists.xensource.com/xen-devel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Keir Fraser
2007-Apr-18 13:08 UTC
Re: [Xen-devel] High-load Domain0 cause guest domian panic.
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 On 18/4/07 13:31, "Graham, Simon" <Simon.Graham@stratus.com> 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@lists.xensource.com on behalf of Hidetoshi Nishi > Sent: Tue 17/04/2007 8:53 AM > To: xen-devel@lists.xensource.com > 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@lists.xensource.com > http://lists.xensource.com/xen-devel > > > > _______________________________________________ > 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
Graham, Simon
2007-Apr-18 14:37 UTC
RE: [Xen-devel] High-load Domain0 cause guest domian panic.
Unfortunately, the time required seems to be very variable and (Dom0) load dependant. When I saw this, the problem was that vif & vbd hot plug in Dom0 were serialized and sometimes vif hot-plug was taking a really long time; I wonder if we need to find a way to not start the timeout for a device until hot plug actually starts in dom0? Simon ________________________________ From: Keir Fraser [mailto:Keir.Fraser@cl.cam.ac.uk] Sent: Wed 18/04/2007 9:08 AM To: Graham, Simon; Hidetoshi Nishi; xen-devel@lists.xensource.com Subject: Re: [Xen-devel] High-load Domain0 cause guest domian panic. 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 On 18/4/07 13:31, "Graham, Simon" <Simon.Graham@stratus.com> 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@lists.xensource.com on behalf of Hidetoshi Nishi Sent: Tue 17/04/2007 8:53 AM To: xen-devel@lists.xensource.com 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@lists.xensource.com http://lists.xensource.com/xen-devel ________________________________ _______________________________________________ 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
Hidetoshi Nishi
2007-Apr-19 11:35 UTC
RE: [Xen-devel] High-load Domain0 cause guest domian panic.
Hi Keir-san, Simon-san
Thank you for your replies.
I think although we set timer be longer, guest domain will mount
the sysroot in init sequence of initrd before xenbus state be
connected.
Then we need the way to make init sequence be stayed until
the device is ready, I think.
Thank you. Nishi
>Unfortunately, the time required seems to be very variable and (Dom0) load
>dependant.
>
>When I saw this, the problem was that vif & vbd hot plug in Dom0 were
>serialized and sometimes vif hot-plug was taking a really long time; I
>wonder if we need to find a way to not start the timeout for a device until
> hot plug actually starts in dom0?
>
>Simon
>
>________________________________
>
>From: Keir Fraser [mailto:Keir.Fraser@cl.cam.ac.uk]
>Sent: Wed 18/04/2007 9:08 AM
>To: Graham, Simon; Hidetoshi Nishi; xen-devel@lists.xensource.com
>Subject: Re: [Xen-devel] High-load Domain0 cause guest domian panic.
>
>
>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
>
>On 18/4/07 13:31, "Graham, Simon" <Simon.Graham@stratus.com>
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@lists.xensource.com on behalf of Hidetoshi
Nishi> Sent: Tue 17/04/2007 8:53 AM
> To: xen-devel@lists.xensource.com
> 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@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
>
>
>________________________________
>
> _______________________________________________
> 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
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Hidetoshi Nishi
2007-Jul-12 10:14 UTC
Re: [Xen-devel] High-load Domain0 cause guest domian panic.
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. > > -- KeirPlease 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@stratus.com> 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@lists.xensource.com on behalf of Hidetoshi Nishi >> Sent: Tue 17/04/2007 8:53 AM >> To: xen-devel@lists.xensource.com >> 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@lists.xensource.com >> http://lists.xensource.com/xen-devel >> >> >> >> _______________________________________________ >> 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
Keir Fraser
2007-Jul-12 10:20 UTC
Re: [Xen-devel] High-load Domain0 cause guest domian panic.
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@jp.fujitsu.com> 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@stratus.com> 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@lists.xensource.com on behalf of Hidetoshi Nishi >>> Sent: Tue 17/04/2007 8:53 AM >>> To: xen-devel@lists.xensource.com >>> 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@lists.xensource.com >>> http://lists.xensource.com/xen-devel >>> >>> >>> >>> _______________________________________________ >>> 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
Hidetoshi Nishi
2007-Jul-12 10:33 UTC
Re: [Xen-devel] High-load Domain0 cause guest domian panic.
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@jp.fujitsu.com> 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@stratus.com> 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@lists.xensource.com on behalf of Hidetoshi Nishi >>>> Sent: Tue 17/04/2007 8:53 AM >>>> To: xen-devel@lists.xensource.com >>>> 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@lists.xensource.com >>>> http://lists.xensource.com/xen-devel >>>> >>>> >>>> >>>> _______________________________________________ >>>> 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