Re: [Xen-users] Kernel panic on Xen 4.0.1 + Debian Squeeze

[Ilya Kozlov <unicast.ru@xxxxxxxxx>]

I added option "iommu=off", becouse without it system show black screen and reboots.

> What partition is root? I believe "set root='(hd0,msdos1)'" is wrong

> (dependant on if you actually have the partition setup as msdos!?) --

> should be more like "set root='(hd0,1)"

I tried this option with the same result

2010/9/18 Mike Viau <viaum@xxxxxxxxxxxxxxx>

> On Date: Fri, 17 Sep 2010 17:55:15 +0100 <mark@xxxxxxxxxxxxxxxxxx> wrote:
>
> What partition is root? I believe "set root='(hd0,msdos1)'" is wrong
> (dependant on if you actually have the partition setup as msdos!?) --
> should be more like "set root='(hd0,1)'"

It seems to work out of the box with msdos based entries in squeeze.

I am running a grub similar to this and it works.

The only un standard part is " iommu=off "


-M

>
> On Fri, Sep 17, 2010 at 06:05:30PM +0400, Ilya Kozlov wrote:
>> Hi.
>>
>> I'm trying to run Xen 4.0.1 with Debian Squeeze in Dom0
>> My grub config:
>> menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-xen-amd64 and XEN
>> 4.0-amd64' --class debian --class gnu-linux --class gnu --class os --class
>> xen {
>> insmod part_msdos
>> insmod ext2
>> set root='(hd0,msdos1)'
>> search --no-floppy --fs-uuid --set e719719a-35aa-4ada-8ab5-9b6c676bc89e
>> echo 'Loading Linux 2.6.32-5-xen-amd64 ...'
>> multiboot /boot/xen-4.0-amd64.gz placeholder iommu=off
>> module /boot/vmlinuz-2.6.32-5-xen-amd64 placeholder
>> root=UUID=e719719a-35aa-4ada-8ab5-9b6c676bc89e ro quiet
>> echo 'Loading initial ramdisk ...'
>> module /boot/initrd.img-2.6.32-5-xen-amd64
>>
>> After boot i see in console:
>> Failed to execute /init
>> Kernel panic - not syncing: No init found. Try passing init= option to
>> kernel
>> Pid: 1, comm: swapper Not tained 2.6.32-5-xen-amd64 #1
>>
>> Initramfs unpacking failed: junk in compressed archve
>> registering netback
>> Kernel panic - not syncing: VFS: Unable to mount root fs on
>> unknown-block(0,0)
>>
>> Kernel vmlinuz-2.6.32-5-xen-amd64 without xen boots normaly.
>>
>> My "trouble" server is IBM HS-22 (2x Xeon E5530, 36 GB RAM, LSI SAS).
>> The same configuration works correctrly on other machine (supermicro-based).
>> But this is not "bad hardware" trouble - i tried two different HS-22
>>
>>
>> --
>> WBR, Kozlov Ilya AKA unicast AKA Lin
>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-users
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users

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

-- 
WBR, Kozlov Ilya AKA unicast AKA Lin

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