Hello,
I compiled xen on ubuntu, but at the bot i got the kernel panic message.
I enabled the support to ext4 fs.
This is kernel panic error:
EXT3-fs: unable to read superblock
ETX4-fs (md0): unable to read superblock
FAT: unable to read boot vector
Kernel panic - not syncing: VFS: Unable to read superblock(9,8)
My grub.cfg generated by update-grup:
menuentry ''Ubuntu, with Linux 2.6.35-22-generic-pae'' --class
ubuntu --class
gnu-linux --class gnu --class os {
recordfail
insmod part_msdos
insmod ext2
set root=''(hd0,msdos1)''
search --no-floppy --fs-uuid --set
2639d272-73f6-4508-af4b-d648a877a39b
linux /vmlinuz-2.6.35-22-generic-pae
root=UUID=f1f592a2-5415-4825-bf7e-3b0bdf45276b ro quiet
initrd /initrd.img-2.6.35-22-generic-pae
}
menuentry ''Ubuntu GNU/Linux, with Linux 2.6.32.27 and XEN 4.0''
--class
ubuntu --class gnu-linux --class gnu --class os --class xen {
insmod part_msdos
insmod ext2
set root=''(hd0,msdos1)''
search --no-floppy --fs-uuid --set
2639d272-73f6-4508-af4b-d648a877a39b
echo ''Loading Linux 2.6.32.27 ...''
multiboot /xen-4.0.gz placeholder
module /vmlinuz-2.6.32.27 placeholder root=/dev/md0 ro quiet
}
How can i fix?
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Hi, they look like drive controller related errors. You could boot on a boot disk and rebuild the kernel again, make menuconfig and make sure you have your hard drive controllers available. My 2c, I am not sure, Regards, Randy On 2/28/2011 2:17 AM, dky hax wrote:> Hello, > > I compiled xen on ubuntu, but at the bot i got the kernel panic message. > I enabled the support to ext4 fs. > > This is kernel panic error: > > EXT3-fs: unable to read superblock > ETX4-fs (md0): unable to read superblock > FAT: unable to read boot vector > Kernel panic - not syncing: VFS: Unable to read superblock(9,8) > > My grub.cfg generated by update-grup: > > menuentry ''Ubuntu, with Linux 2.6.35-22-generic-pae'' --class ubuntu > --class gnu-linux --class gnu --class os { > recordfail > insmod part_msdos > insmod ext2 > set root=''(hd0,msdos1)'' > search --no-floppy --fs-uuid --set > 2639d272-73f6-4508-af4b-d648a877a39b > linux /vmlinuz-2.6.35-22-generic-pae > root=UUID=f1f592a2-5415-4825-bf7e-3b0bdf45276b ro quiet > initrd /initrd.img-2.6.35-22-generic-pae > } > > menuentry ''Ubuntu GNU/Linux, with Linux 2.6.32.27 and XEN 4.0'' --class > ubuntu --class gnu-linux --class gnu --class os --class xen { > insmod part_msdos > insmod ext2 > set root=''(hd0,msdos1)'' > search --no-floppy --fs-uuid --set > 2639d272-73f6-4508-af4b-d648a877a39b > echo ''Loading Linux 2.6.32.27 ...'' > multiboot /xen-4.0.gz placeholder > module /vmlinuz-2.6.32.27 placeholder root=/dev/md0 ro quiet > } > > How can i fix? > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Mon, Feb 28, 2011 at 5:17 PM, dky hax <dkyhax@gmail.com> wrote:> Hello, > > I compiled xen on ubuntu, but at the bot i got the kernel panic message. > I enabled the support to ext4 fs. > > This is kernel panic error: > > EXT3-fs: unable to read superblock > ETX4-fs (md0): unable to read superblock > FAT: unable to read boot vector > Kernel panic - not syncing: VFS: Unable to read superblock(9,8) > > My grub.cfg generated by update-grup: > > menuentry ''Ubuntu, with Linux 2.6.35-22-generic-pae'' --class ubuntu --class > gnu-linux --class gnu --class os { > recordfail > insmod part_msdos > insmod ext2 > set root=''(hd0,msdos1)'' > search --no-floppy --fs-uuid --set > 2639d272-73f6-4508-af4b-d648a877a39b > linux /vmlinuz-2.6.35-22-generic-pae > root=UUID=f1f592a2-5415-4825-bf7e-3b0bdf45276b ro quiet > initrd /initrd.img-2.6.35-22-generic-pae > } > > menuentry ''Ubuntu GNU/Linux, with Linux 2.6.32.27 and XEN 4.0'' --class > ubuntu --class gnu-linux --class gnu --class os --class xen { > insmod part_msdos > insmod ext2 > set root=''(hd0,msdos1)'' > search --no-floppy --fs-uuid --set > 2639d272-73f6-4508-af4b-d648a877a39b > echo ''Loading Linux 2.6.32.27 ...'' > multiboot /xen-4.0.gz placeholder > module /vmlinuz-2.6.32.27 placeholder root=/dev/md0 ro quiet > } > > How can i fix?Shouldn''t there be another "module" line there, with your initrd in it? -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Mon, Feb 28, 2011 at 9:11 PM, dky hax <dkyhax@gmail.com> wrote:>> > menuentry ''Ubuntu GNU/Linux, with Linux 2.6.32.27 and XEN 4.0'' --class >> > ubuntu --class gnu-linux --class gnu --class os --class xen { >> > insmod part_msdos >> > insmod ext2 >> > set root=''(hd0,msdos1)'' >> > search --no-floppy --fs-uuid --set >> > 2639d272-73f6-4508-af4b-d648a877a39b >> > echo ''Loading Linux 2.6.32.27 ...'' >> > multiboot /xen-4.0.gz placeholder >> > module /vmlinuz-2.6.32.27 placeholder root=/dev/md0 ro quiet >> > } >> > >> > How can i fix? >> >> Shouldn''t there be another "module" line there, with your initrd in it?> Maybe, i''m not sure.Why aren''t you sure? How did you come up with that setup? Following a tutorial? Something you made up? Following http://wiki.xensource.com/xenwiki/XenCommonProblems, there''s a grub2 entry example here: http://xen.1045712.n5.nabble.com/Strange-interaction-from-grub2-and-XEN-td2573358.html -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users