Re: [Xen-devel] kernel BUG at drivers/xen/balloon.c:528!

[Łukasz Oleś <lukaszoles@xxxxxxxxx>]

W dniu 19 lipca 2010 18:39 użytkownik Stefano Stabellini
<stefano.stabellini@xxxxxxxxxxxxx> napisał:
> On Mon, 19 Jul 2010, Łukasz Oleś wrote:
>> W dniu 19 lipca 2010 16:19 użytkownik Stefano Stabellini
>> <stefano.stabellini@xxxxxxxxxxxxx> napisał:
>> > On Mon, 19 Jul 2010, Łukasz Oleś wrote:
>> >> >
>> >> > 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?
>> >>
>> > but you should be able
>> > to mount /dev/hd* just fine without CONFIG_XEN_PLATFORM_PCI.
>>
>> This one is not true on my system.
>>
>> If something in my initrd fails it launches  busybox then I can run
>> fdisk -l or cat /proc/partitions and they return nothing.  Whats more
>> intresting at the system start I can see:
>>
>> Probing IDE interface ide0...
>> hda: QEMU HARDDISK, ATA DISK drive
>> hdb: QEMU HARDDISK, ATA DISK drive
>> hda: host max PIO4 wanted PIO255(auto-tune) selected PIO2
>> hda: MWDMA2 mode selected
>> hdb: host max PIO4 wanted PIO255(auto-tune) selected PIO2
>> hdb: MWDMA2 mode selected
>> Probing IDE interface ide1...
>> hdc: QEMU HARDDISK, ATA DISK drive
>> hdc: host max PIO4 wanted PIO255(auto-tune) selected PIO2
>> hdc: MWDMA2 mode selected
>> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
>> ide1 at 0x170-0x177,0x376 on irq 15
>> ide-cd driver 5.00
>>
>> but later disks disappear. Full log in earlier mail
>>
>
> Yes, I have seen that.
> I am not sure what is the cause of the problem because if you see
> those messages it means no unplug has been done so you should be able to
> access the emulated disks without any issues.
> Just to be sure, could you please add this patch to your kernel and tell
> me if it gets printed?
>
>
>
> diff --git a/arch/x86/xen/platform-pci-unplug.c 
> b/arch/x86/xen/platform-pci-unplug.c
> index 2f7f3fb..4513202 100644
> --- a/arch/x86/xen/platform-pci-unplug.c
> +++ b/arch/x86/xen/platform-pci-unplug.c
> @@ -98,8 +98,10 @@ void __init xen_unplug_emulated_devices(void)
>                }
>        }
>        /* Now unplug the emulated devices */
> -       if (!(xen_emul_unplug & XEN_UNPLUG_IGNORE))
> +       if (!(xen_emul_unplug & XEN_UNPLUG_IGNORE)) {
>                outw(xen_emul_unplug, XEN_IOPORT_UNPLUG);
> +               printk("DEBUG unplug %x\n", xen_emul_unplug);
> +       }
>        xen_platform_pci_unplug = xen_emul_unplug;
>  }
>

dmesg output from busybox and qemu log are in attachment

-- 
Łukasz Oleś

Attachment: qemu.log
Description: Text Data

Attachment: dmesg.log
Description: Text Data

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel