From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: 3.0.4 and 3.1-rc4 based dom0 won't boot with acpi=off Date: Mon, 12 Sep 2011 11:06:06 -0400 Message-ID: <20110912150606.GC15778@oracle.com> References: <20110911002807.GA9989@oracle.com> <4E6C0473.8090905@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline In-Reply-To: <4E6C0473.8090905@gmail.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Sven =?iso-8859-1?Q?K=F6hler?= Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Sun, Sep 11, 2011 at 02:44:35AM +0200, Sven K=F6hler wrote: > Am 11.09.2011 02:28, schrieb Konrad Rzeszutek Wilk: > > On Sun, Sep 11, 2011 at 12:43:18AM +0200, Sven K=F6hler wrote: > >> Hi, > >> > >> when using acpi=3Doff in the kernel or xen command line, the system = won't > >> boot. On real hardware, I saw a few interrupt related warnings from = the > >> usb drivers. The system then seemed to lock up when trying to do I/O= via > >> AHCI. Same in virtualbox. System won't come up. > >=20 > > Not surprised. Without the ACPI we can't find parse the interrupt tab= le, > > so you don't get any interrupts. >=20 > Thanks for explaining. Now what about the future? Will there be some > solution for the acpi=3Doff case? No. >=20 > I'm a bit confused, since your words don't sound like there is a way to > boot with acpi=3Doff. But other dom0 kernels actually boot with acpi=3D= off. Sure. > So after all, some other way for setting up interrupts seems to exist. The older kernels (XenOLinux) made it possible by copying a lot of the generic code in its own and making it work. That is not possible with the upstream kernel. Well, maybe it is possible, but I am not sure if it is worth the effort. >=20 > > This is result of the reboot issue you have been seeing with your box= ? >=20 > Yes. >=20 > > You might want to try some parameters on the Xen line to alter how > > it is suppose to reboot. > >=20 > > /* > > * reboot=3Db[ios] | t[riple] | k[bd] | n[o] [, [w]arm | [c]old] >=20 > Thanks for the list. > I guess, both reboot=3Dbios and reboot=3Db is accepted? > BTW: "no" is missing in the list below. acpi is missing in the list > above. And actually what's the source for list? Xen hypervisor source. I just did a quick search for 'reboot=3D' > (I never find any documentation about the hypervisor options, which is > pretty frustrating sometimes) >=20 > > * warm Don't set the cold reboot flag > > * cold Set the cold reboot flag > > * bios Reboot by jumping through the BIOS (only for X86_32) > > * triple Force a triple fault (init) > > * kbd Use the keyboard controller. cold reset (default) > > * acpi Use the RESET_REG in the FADT > > */ >=20 > So in fact, xen is doing the reboot, and not the dom0 kernel, right? Yes. Dom0 triggers it though (by invoking an hypercall that tells Xen to reboot/shutdown the machine). > (Some people have claimed otherwise) >=20 > Could you imagine to adapt xen's reboot code to the one of linux 3.0 > (which was tweaked quite a lot for maximum compatibility) I can imagine it.. but without any ideas of why your machine is not reboo= ting it is a bit .. difficult. You could also try on the Xen hypervisor line (Ctlr-A three times) try th= e 'R' and see if it does anything. >=20 >=20 >=20 > Regards, > Sven >=20