From: "Łukasz Oleś" <lukaszoles@gmail.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: kernel BUG at drivers/xen/balloon.c:528!
Date: Mon, 19 Jul 2010 15:12:07 +0200 [thread overview]
Message-ID: <AANLkTimqPURWH5nDebTEJ9XP4OCiO1yio1jPcKEKPhTt@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1007161640150.21432@kaball-desktop>
W dniu 16 lipca 2010 18:39 użytkownik Stefano Stabellini
<stefano.stabellini@eu.citrix.com> napisał:
> On Fri, 16 Jul 2010, Łukasz Oleś wrote:
>> W dniu 15 lipca 2010 19:41 użytkownik Stefano Stabellini
>> <stefano.stabellini@eu.citrix.com> napisał:
>> > On Thu, 15 Jul 2010, Jeremy Fitzhardinge wrote:
>> >> On 07/15/2010 04:07 AM, Łukasz Oleś wrote:
>> >> > Hi,
>> >> >
>> >> > I'm getting kernel panic during boot latest xen/next.
>> >> >
>> >>
>> >> Booting PV or HVM?
>> >>
>> >
>> > This bug is caused by backend drivers trying to initialize in a PV on
>> > HVM guest.
>> > The last port of my series on xen/next should have the right fix.
>> >
>>
>> Now I have problem with vbd and vifs.
>>
>> vbd vbd-51712: 28 granting access to ring page
>> vbd vbd-51712: 28 xenbus_dev_probe on device/vbd/51712
>> vbd: probe of vbd-51712 failed with error -28
>> vbd vbd-51728: 28 granting access to ring page
>> vbd vbd-51728: 28 xenbus_dev_probe on device/vbd/51728
>> vbd: probe of vbd-51728 failed with error -28
>> vbd vbd-51744: 28 granting access to ring page
>> vbd vbd-51744: 28 xenbus_dev_probe on device/vbd/51744
>> vbd: probe of vbd-51744 failed with error -28
>>
>> Initialising Xen virtual ethernet driver.
>> #### netfront can't alloc tx grant refs
>> vif vif-0: 12 creating netdev
>> vif vif-0: 12 xenbus_dev_probe on device/vif/0
>> vif: probe of vif-0 failed with error -12
>> #### netfront can't alloc tx grant refs
>> vif vif-1: 12 creating netdev
>> vif vif-1: 12 xenbus_dev_probe on device/vif/1
>> vif: probe of vif-1 failed with error -12
>> #### netfront can't alloc tx grant refs
>> vif vif-2: 12 creating netdev
>> vif vif-2: 12 xenbus_dev_probe on device/vif/2
>> vif: probe of vif-2 failed with error -12
>>
>> Full log in attachment, vm config is posted in earlier message.
>>
>
> The warnings are due to the fact that CONFIG_XEN_PLATFORM_PCI is not
> enabled in your config but the kernel tries to initialize the pv
> frontends anyway, the patch I have just sent to the list should fix this
> issue.
Yes, their gone now
>
> In any case you should enable CONFIG_XEN_PLATFORM_PCI in your kernel
> config, otherwise the pv frontends won't load properly and you are not
> going to have any benefits running a PV on HVM kernel.
>
> I am not sure why you cannot mount your root device, maybe you didn't
> specify the correct root= in your kernel command line options?
It works fine on bare metal and ESX. It looks like in initrd system
doesn't see any disks.
When I enabled option CONFIG_XEN_PLATFORM_PCI I was finally able to
boot my sytem. Is this suposed to work in this way?
--
Łukasz Oleś
next prev parent reply other threads:[~2010-07-19 13:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-15 11:07 kernel BUG at drivers/xen/balloon.c:528! Łukasz Oleś
2010-07-15 17:34 ` Jeremy Fitzhardinge
2010-07-15 17:41 ` Stefano Stabellini
2010-07-16 10:53 ` Łukasz Oleś
2010-07-16 16:39 ` Stefano Stabellini
2010-07-19 13:12 ` Łukasz Oleś [this message]
2010-07-19 14:19 ` Stefano Stabellini
2010-07-19 14:54 ` Łukasz Oleś
2010-07-19 16:39 ` Stefano Stabellini
2010-07-20 8:02 ` Łukasz Oleś
2010-07-20 14:47 ` Stefano Stabellini
2010-07-21 11:51 ` Łukasz Oleś
2010-07-21 13:30 ` Stefano Stabellini
2010-07-25 20:58 ` Łukasz Oleś
2010-07-26 10:06 ` Łukasz Oleś
2010-07-26 16:01 ` Stefano Stabellini
2010-07-26 16:28 ` Łukasz Oleś
2010-07-26 16:33 ` Stefano Stabellini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTimqPURWH5nDebTEJ9XP4OCiO1yio1jPcKEKPhTt@mail.gmail.com \
--to=lukaszoles@gmail.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).