[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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



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 <konrad.wilk@xxxxxxxxxx> 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-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.