Fedora 17 Dom-U booting issue

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

Fedora 17 Dom-U booting issue

kk s
Hi Folks,

I have upgraded Fedora 16 to 17 on one of Xen HVM Dom-U and it refuses to boot fine and getting the below error on console,

--------
Booting 'Fedora (3.6.1-1.fc17.x86_64)'

Loading Fedora (3.6.1-1.fc17.x86_64)
Loading initial ramdisk ...
[   0.000000] Cannot get hvm parameter 18: -22!
---------

The dom0 is running with Xen 3.4.3.

Any help much appreciated!


_______________________________________________
Xen-users mailing list
[hidden email]
http://lists.xen.org/xen-users
Reply | Threaded
Open this post in threaded view
|

Re: Fedora 17 Dom-U booting issue

Ian Campbell-10
Adding xen-devel and the relevant maintainers.

On Tue, 2012-10-16 at 20:24 +0100, kk s wrote:

> Hi Folks,
>
>
> I have upgraded Fedora 16 to 17 on one of Xen HVM Dom-U and it refuses
> to boot fine and getting the below error on console,
>
>
> --------
> Booting 'Fedora (3.6.1-1.fc17.x86_64)'
>
>
> Loading Fedora (3.6.1-1.fc17.x86_64)
> Loading initial ramdisk ...
> [   0.000000] Cannot get hvm parameter 18: -22!

HVM parameter 18 is HVM_PARAM_CONSOLE_EVTCHN.

I'm not sure it's related but commit 5842f5768599 "xen/hvc: Check
HVM_PARAM_CONSOLE_[EVTCHN|PFN] for correctness." looks a bit dogy to me,
in particular:
+       /*
+        * If the toolstack (or the hypervisor) hasn't set these values, the
+        * default value is 0. Even though mfn = 0 and evtchn = 0 are
+        * theoretically correct values, in practice they never are and they
+        * mean that a legacy toolstack hasn't initialized the pv console correc
+        */

The only reason 0 isn't used is pure coincidence because libxl (and
presumably xend) do:
    state->store_port = xc_evtchn_alloc_unbound(ctx->xch, domid, state->store_domid);
    state->console_port = xc_evtchn_alloc_unbound(ctx->xch, domid, state->console_domid);

so the store happens to become port 0 and the console port 1, but I
think relying on this never changing is pretty fragile.

If this is being relied on then I suggest that a patch to the hypervisor
to reject port 0 as a console port would be wise in case someone decides
to refactor this code and inadvertently changes the order of the
allocation. At the same time perhaps making the default be some invalid
port number on the hypervisor side would be a good idea for future
proofing.


> ---------
>
>
> The dom0 is running with Xen 3.4.3.
>
>
> Any help much appreciated!
>
>





_______________________________________________
Xen-users mailing list
[hidden email]
http://lists.xen.org/xen-users
Reply | Threaded
Open this post in threaded view
|

Re: Fedora 17 Dom-U booting issue

Stefano Stabellini-3
On Wed, 17 Oct 2012, Ian Campbell wrote:

> Adding xen-devel and the relevant maintainers.
>
> On Tue, 2012-10-16 at 20:24 +0100, kk s wrote:
> > Hi Folks,
> >
> >
> > I have upgraded Fedora 16 to 17 on one of Xen HVM Dom-U and it refuses
> > to boot fine and getting the below error on console,
> >
> >
> > --------
> > Booting 'Fedora (3.6.1-1.fc17.x86_64)'
> >
> >
> > Loading Fedora (3.6.1-1.fc17.x86_64)
> > Loading initial ramdisk ...
> > [   0.000000] Cannot get hvm parameter 18: -22!
>
> HVM parameter 18 is HVM_PARAM_CONSOLE_EVTCHN.

-22 is EINVAL, that Xen would return only if:

- the requested parameter is out of range
this is not the case, 18 < 30

- the domain is not actually an HVM domain
can you please post your VM config file?



> I'm not sure it's related but commit 5842f5768599 "xen/hvc: Check
> HVM_PARAM_CONSOLE_[EVTCHN|PFN] for correctness." looks a bit dogy to me,
> in particular:
> +       /*
> +        * If the toolstack (or the hypervisor) hasn't set these values, the
> +        * default value is 0. Even though mfn = 0 and evtchn = 0 are
> +        * theoretically correct values, in practice they never are and they
> +        * mean that a legacy toolstack hasn't initialized the pv console correc
> +        */
>
> The only reason 0 isn't used is pure coincidence because libxl (and
> presumably xend) do:
>     state->store_port = xc_evtchn_alloc_unbound(ctx->xch, domid, state->store_domid);
>     state->console_port = xc_evtchn_alloc_unbound(ctx->xch, domid, state->console_domid);
>
> so the store happens to become port 0 and the console port 1, but I
> think relying on this never changing is pretty fragile.
>
> If this is being relied on then I suggest that a patch to the hypervisor
> to reject port 0 as a console port would be wise in case someone decides
> to refactor this code and inadvertently changes the order of the
> allocation. At the same time perhaps making the default be some invalid
> port number on the hypervisor side would be a good idea for future
> proofing.

Even if the toolstack didn't set HVM_PARAM_CONSOLE_EVTCHN, or if the
check for 0 is not correct, the guest shouldn't get -EINVAL. I don't
think the error is related to this issue.

_______________________________________________
Xen-users mailing list
[hidden email]
http://lists.xen.org/xen-users
Reply | Threaded
Open this post in threaded view
|

Re: Fedora 17 Dom-U booting issue

Ian Campbell-10
On Thu, 2012-10-18 at 14:42 +0100, Stefano Stabellini wrote:

> On Wed, 17 Oct 2012, Ian Campbell wrote:
> > Adding xen-devel and the relevant maintainers.
> >
> > On Tue, 2012-10-16 at 20:24 +0100, kk s wrote:
> > > Hi Folks,
> > >
> > >
> > > I have upgraded Fedora 16 to 17 on one of Xen HVM Dom-U and it refuses
> > > to boot fine and getting the below error on console,
> > >
> > >
> > > --------
> > > Booting 'Fedora (3.6.1-1.fc17.x86_64)'
> > >
> > >
> > > Loading Fedora (3.6.1-1.fc17.x86_64)
> > > Loading initial ramdisk ...
> > > [   0.000000] Cannot get hvm parameter 18: -22!
> >
> > HVM parameter 18 is HVM_PARAM_CONSOLE_EVTCHN.
>
> -22 is EINVAL, that Xen would return only if:
>
> - the requested parameter is out of range
> this is not the case, 18 < 30

The hypervisor here is 3.4.3 where the largest hvm param is:
$ grep define.HVM_PARAM xen-3.4-testing.hg/xen/include/public/hvm/params.h | sort -k3 -n | tail -n 3
#define HVM_PARAM_ACPI_S_STATE 14
#define HVM_PARAM_VM86_TSS     15
#define HVM_PARAM_VPT_ALIGN    16

Ian.


_______________________________________________
Xen-users mailing list
[hidden email]
http://lists.xen.org/xen-users
Reply | Threaded
Open this post in threaded view
|

Re: Fedora 17 Dom-U booting issue

Stefano Stabellini-3
On Thu, 18 Oct 2012, Ian Campbell wrote:

> On Thu, 2012-10-18 at 14:42 +0100, Stefano Stabellini wrote:
> > On Wed, 17 Oct 2012, Ian Campbell wrote:
> > > Adding xen-devel and the relevant maintainers.
> > >
> > > On Tue, 2012-10-16 at 20:24 +0100, kk s wrote:
> > > > Hi Folks,
> > > >
> > > >
> > > > I have upgraded Fedora 16 to 17 on one of Xen HVM Dom-U and it refuses
> > > > to boot fine and getting the below error on console,
> > > >
> > > >
> > > > --------
> > > > Booting 'Fedora (3.6.1-1.fc17.x86_64)'
> > > >
> > > >
> > > > Loading Fedora (3.6.1-1.fc17.x86_64)
> > > > Loading initial ramdisk ...
> > > > [   0.000000] Cannot get hvm parameter 18: -22!
> > >
> > > HVM parameter 18 is HVM_PARAM_CONSOLE_EVTCHN.
> >
> > -22 is EINVAL, that Xen would return only if:
> >
> > - the requested parameter is out of range
> > this is not the case, 18 < 30
>
> The hypervisor here is 3.4.3 where the largest hvm param is:
> $ grep define.HVM_PARAM xen-3.4-testing.hg/xen/include/public/hvm/params.h | sort -k3 -n | tail -n 3
> #define HVM_PARAM_ACPI_S_STATE 14
> #define HVM_PARAM_VM86_TSS     15
> #define HVM_PARAM_VPT_ALIGN    16

OK, we know that the console is not working because it is not provided
by the hypervisor.
However that shouldn't prevent the domain from booting, the emulated
serial should work fine.

_______________________________________________
Xen-users mailing list
[hidden email]
http://lists.xen.org/xen-users
Reply | Threaded
Open this post in threaded view
|

Re: Fedora 17 Dom-U booting issue

Konrad Rzeszutek Wilk
On Thu, Oct 18, 2012 at 05:21:06PM +0100, Stefano Stabellini wrote:

> On Thu, 18 Oct 2012, Ian Campbell wrote:
> > On Thu, 2012-10-18 at 14:42 +0100, Stefano Stabellini wrote:
> > > On Wed, 17 Oct 2012, Ian Campbell wrote:
> > > > Adding xen-devel and the relevant maintainers.
> > > >
> > > > On Tue, 2012-10-16 at 20:24 +0100, kk s wrote:
> > > > > Hi Folks,
> > > > >
> > > > >
> > > > > I have upgraded Fedora 16 to 17 on one of Xen HVM Dom-U and it refuses
> > > > > to boot fine and getting the below error on console,
> > > > >
> > > > >
> > > > > --------
> > > > > Booting 'Fedora (3.6.1-1.fc17.x86_64)'
> > > > >
> > > > >
> > > > > Loading Fedora (3.6.1-1.fc17.x86_64)
> > > > > Loading initial ramdisk ...
> > > > > [   0.000000] Cannot get hvm parameter 18: -22!
> > > >
> > > > HVM parameter 18 is HVM_PARAM_CONSOLE_EVTCHN.
> > >
> > > -22 is EINVAL, that Xen would return only if:
> > >
> > > - the requested parameter is out of range
> > > this is not the case, 18 < 30
> >
> > The hypervisor here is 3.4.3 where the largest hvm param is:
> > $ grep define.HVM_PARAM xen-3.4-testing.hg/xen/include/public/hvm/params.h | sort -k3 -n | tail -n 3
> > #define HVM_PARAM_ACPI_S_STATE 14
> > #define HVM_PARAM_VM86_TSS     15
> > #define HVM_PARAM_VPT_ALIGN    16
>
> OK, we know that the console is not working because it is not provided
> by the hypervisor.
> However that shouldn't prevent the domain from booting, the emulated
> serial should work fine.

Maybe it does? Mr. KK can you boot your guest with this in guest config:

serial='pty'

and on your Linux line, do 'loglevel=8 initcall_debug console=ttyS0,115200 debug' please?

_______________________________________________
Xen-users mailing list
[hidden email]
http://lists.xen.org/xen-users
Reply | Threaded
Open this post in threaded view
|

Re: Fedora 17 Dom-U booting issue

kk s
Hi,

Looks like the serial='pty' parameter already passed which doesn't work. Though I can't add do 'loglevel=8 initcall_debug console=ttyS0,115200 debug' since its Xen HVM and without booted the VM we can't add anything in grub.conf file.

The default kernel that comes from Fedora iso is booting fine and this latest kernel only having issue. I'll try with serial=pty later today and provide you the result.

Fyi. The fedora version designed to install as pv-on-hvm itself which means it uses xen network and disk devices. So I already tried to pass netfront type and tried pci passthrough none of it helped.

I guess its something issue with Fedora kernel.


On Fri, Oct 19, 2012 at 7:51 PM, Konrad Rzeszutek Wilk <[hidden email]> wrote:
On Thu, Oct 18, 2012 at 05:21:06PM +0100, Stefano Stabellini wrote:
> On Thu, 18 Oct 2012, Ian Campbell wrote:
> > On Thu, 2012-10-18 at 14:42 +0100, Stefano Stabellini wrote:
> > > On Wed, 17 Oct 2012, Ian Campbell wrote:
> > > > Adding xen-devel and the relevant maintainers.
> > > >
> > > > On Tue, 2012-10-16 at 20:24 +0100, kk s wrote:
> > > > > Hi Folks,
> > > > >
> > > > >
> > > > > I have upgraded Fedora 16 to 17 on one of Xen HVM Dom-U and it refuses
> > > > > to boot fine and getting the below error on console,
> > > > >
> > > > >
> > > > > --------
> > > > > Booting 'Fedora (3.6.1-1.fc17.x86_64)'
> > > > >
> > > > >
> > > > > Loading Fedora (3.6.1-1.fc17.x86_64)
> > > > > Loading initial ramdisk ...
> > > > > [   0.000000] Cannot get hvm parameter 18: -22!
> > > >
> > > > HVM parameter 18 is HVM_PARAM_CONSOLE_EVTCHN.
> > >
> > > -22 is EINVAL, that Xen would return only if:
> > >
> > > - the requested parameter is out of range
> > > this is not the case, 18 < 30
> >
> > The hypervisor here is 3.4.3 where the largest hvm param is:
> > $ grep define.HVM_PARAM xen-3.4-testing.hg/xen/include/public/hvm/params.h | sort -k3 -n | tail -n 3
> > #define HVM_PARAM_ACPI_S_STATE 14
> > #define HVM_PARAM_VM86_TSS     15
> > #define HVM_PARAM_VPT_ALIGN    16
>
> OK, we know that the console is not working because it is not provided
> by the hypervisor.
> However that shouldn't prevent the domain from booting, the emulated
> serial should work fine.

Maybe it does? Mr. KK can you boot your guest with this in guest config:

serial='pty'

and on your Linux line, do 'loglevel=8 initcall_debug console=ttyS0,115200 debug' please?


_______________________________________________
Xen-users mailing list
[hidden email]
http://lists.xen.org/xen-users
Reply | Threaded
Open this post in threaded view
|

Re: [Xen-devel] Fedora 17 Dom-U booting issue

Pasi Kärkkäinen
On Sun, Oct 21, 2012 at 12:03:47AM +0530, kk s wrote:
>    Hi,
>    Looks like the serial='pty' parameter already passed which doesn't work.
>    Though I can't add do 'loglevel=8 initcall_debug console=ttyS0,115200
>    debug' since its Xen HVM and without booted the VM we can't add anything
>    in grub.conf file.
>

Open the VNC console for the HVM guest and edit grub settings / kernel parameters?


>    The default kernel that comes from Fedora iso is booting fine and this
>    latest kernel only having issue. I'll try with serial=pty later today and
>    provide you the result.
>    Fyi. The fedora version designed to install as pv-on-hvm itself which
>    means it uses xen network and disk devices. So I already tried to pass
>    netfront type and tried pci passthrough none of it helped.
>    I guess its something issue with Fedora kernel.

You can control if pv-on-hvm is used from dom0, see:
http://wiki.xen.org/wiki/Xen_Linux_PV_on_HVM_drivers

-- Pasi

>    On Fri, Oct 19, 2012 at 7:51 PM, Konrad Rzeszutek Wilk
>    <[1][hidden email]> wrote:
>
>      On Thu, Oct 18, 2012 at 05:21:06PM +0100, Stefano Stabellini wrote:
>      > On Thu, 18 Oct 2012, Ian Campbell wrote:
>      > > On Thu, 2012-10-18 at 14:42 +0100, Stefano Stabellini wrote:
>      > > > On Wed, 17 Oct 2012, Ian Campbell wrote:
>      > > > > Adding xen-devel and the relevant maintainers.
>      > > > >
>      > > > > On Tue, 2012-10-16 at 20:24 +0100, kk s wrote:
>      > > > > > Hi Folks,
>      > > > > >
>      > > > > >
>      > > > > > I have upgraded Fedora 16 to 17 on one of Xen HVM Dom-U and it
>      refuses
>      > > > > > to boot fine and getting the below error on console,
>      > > > > >
>      > > > > >
>      > > > > > --------
>      > > > > > Booting 'Fedora (3.6.1-1.fc17.x86_64)'
>      > > > > >
>      > > > > >
>      > > > > > Loading Fedora (3.6.1-1.fc17.x86_64)
>      > > > > > Loading initial ramdisk ...
>      > > > > > [   0.000000] Cannot get hvm parameter 18: -22!
>      > > > >
>      > > > > HVM parameter 18 is HVM_PARAM_CONSOLE_EVTCHN.
>      > > >
>      > > > -22 is EINVAL, that Xen would return only if:
>      > > >
>      > > > - the requested parameter is out of range
>      > > > this is not the case, 18 < 30
>      > >
>      > > The hypervisor here is 3.4.3 where the largest hvm param is:
>      > > $ grep define.HVM_PARAM
>      xen-3.4-testing.hg/xen/include/public/hvm/params.h | sort -k3 -n | tail
>      -n 3
>      > > #define HVM_PARAM_ACPI_S_STATE 14
>      > > #define HVM_PARAM_VM86_TSS     15
>      > > #define HVM_PARAM_VPT_ALIGN    16
>      >
>      > OK, we know that the console is not working because it is not provided
>      > by the hypervisor.
>      > However that shouldn't prevent the domain from booting, the emulated
>      > serial should work fine.
>
>      Maybe it does? Mr. KK can you boot your guest with this in guest config:
>
>      serial='pty'
>
>      and on your Linux line, do 'loglevel=8 initcall_debug
>      console=ttyS0,115200 debug' please?
>
> References
>
>    Visible links
>    1. mailto:[hidden email]

> _______________________________________________
> Xen-devel mailing list
> [hidden email]
> http://lists.xen.org/xen-devel


_______________________________________________
Xen-users mailing list
[hidden email]
http://lists.xen.org/xen-users
Reply | Threaded
Open this post in threaded view
|

Re: [Xen-devel] Fedora 17 Dom-U booting issue

Stefano Stabellini-3
On Sat, 20 Oct 2012, Pasi Kärkkäinen wrote:
> On Sun, Oct 21, 2012 at 12:03:47AM +0530, kk s wrote:
> >    Hi,
> >    Looks like the serial='pty' parameter already passed which doesn't work.
> >    Though I can't add do 'loglevel=8 initcall_debug console=ttyS0,115200
> >    debug' since its Xen HVM and without booted the VM we can't add anything
> >    in grub.conf file.
> >
>
> Open the VNC console for the HVM guest and edit grub settings / kernel parameters?

If the disk image is in raw format you can also mount it in dom0, using
lomount if it is a file or kpartx if it is a physical device.

On the latest version of Xen you can even mount non-raw disks in dom0,
simply calling xl block-attach on them, specifying 0 as the target
domain.
_______________________________________________
Xen-users mailing list
[hidden email]
http://lists.xen.org/xen-users