[Xen-users] Re : Re : Re : Re : Which kernel may I compile ?

[David TECHER <davidtecher@xxxxxxxx>]

The last solution is to put UUID off

vim /etc/default/grub to disable UUID

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
GRUB_DISABLE_LINUX_UUID=true

then

update-grub

if it does not succeed, I have no more suggestion

Sorry

---

De : David TECHER <davidtecher@xxxxxxxx>
À : Emmanuel COURCELLE <emmanuel.courcelle@xxxxxxxxxxxxxxxx>; "xen-users@xxxxxxxxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxxxxxxxx>
Envoyé le : Jeudi 5 Janvier 2012 16h43
Objet : Re : [Xen-users] Re : Re : Re : Which kernel may I compile ?

Try 

dom0_mem=2048MB

It should be enough (do not forget 'MB' )

you need to have enough memory to handle the init process

---

De : Emmanuel COURCELLE <emmanuel.courcelle@xxxxxxxxxxxxxxxx>
À : xen-users@xxxxxxxxxxxxxxxxxxx
Cc : David TECHER <davidtecher@xxxxxxxx>
Envoyé le : Jeudi 5 Janvier 2012 15h58
Objet : Re: [Xen-users] Re : Re : Re : Which kernel may I compile ?

Le 05/01/2012 14:01, David TECHER a écrit :

Emmanuel,

Do you've got

"Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)" ???????

Yes David, it is this message. However I carefully executed the command:

mkinitramfs -o initrd.img-2.6.32.50 2.6.32.50,

which does the same thing as the command explained by ubuntu.

Well, I think that the problem is that I have put some parameters on the xen command line, as explained here: http://wiki.xen.org/wiki/XenBestPractices
(I did this because I had a crash of dom0 when I tried to give too much memory to my domU, and this indeed solved my problem).

If I use the following grub command (generated by update-grub)

        echo    'Loading Linux 2.6.32.50 ...'
	multiboot       /boot/xen-4.0-amd64.gz placeholder
	module  /boot/vmlinuz-2.6.32.50 placeholder root=UUID=3bb2e67b-19c8-4916-9977-4ff87983164d ro  quiet
	echo    'Loading initial ramdisk ...'
	module  /boot/initrd.img-2.6.32.50

The machine boots fine, BUT if I use the following grub command:

        echo    'Loading Linux 2.6.32.50 ...'
	multiboot       /boot/xen-4.0-amd64.gz placeholder dom0_mem=512
	module  /boot/vmlinuz-2.6.32.50 placeholder root=UUID=3bb2e67b-19c8-4916-9977-4ff87983164d ro  quiet
	echo    'Loading initial ramdisk ...'
	module  /boot/initrd.img-2.6.32.50

it hangs with the message Unable to mount root fs etc.
The funny thing is that everything works perfectly well with the initial Debian kernel (2.6.32-5-xen-amd64).

So, is there a solution, or do I have to avoid any parameter on the xen boot command ?

-- 
Emmanuel COURCELLE                emmanuel.courcelle@xxxxxxxxxxxxxxxx
L.I.P.M. (UMR CNRS-INRA 2594/441) tel (33) 5-61-28-54-50
B.P.52627 - 31326 CASTANET TOLOSAN Cedex - FRANCE 

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