Hello,
System is unbuntu 10.4 LTS, running on a single proc 4 core XEON.
I compiled and installed XEN 4.0.0 following the recipes found here:
http://virtually-a-machine.blogspot.com/2009/12/experimental-xen-and-ubuntu-part-1.html
http://virtually-a-machine.blogspot.com/2009/12/experimental-xen-and-ubuntu-part-2.html
(using a xen 4.0.0 tarball though).
Now this site instructs me to add an entry to /etc/grub.d/ so that it
gets included in grub.conf when I run update-grub
The exact example given on the site above didn''t work, so I googled a
bit in order to find out how I was supposed to do this. I settled on
adding a 40_custom file to /etc/grub.d, with the following content:
#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the ''exec tail'' line above.
menuentry ''Xen 4 Ubuntu 2.6.31.6-xen1''{
insmod raid
insmod mdraid
insmod ext2
set root=''(md0)''
multiboot (md0)/xen-4.0.0.gz dummy=dummy dom0_mem=1024M
module (md0)/vmlinuz-2.6.31.13xen-kvb-1 dummy=dummy
root=/dev/mapper/thunersee_root-root ro
module (md0)/initrd.img-2.6.31.13xen-kvb-1
}
My problem is that this does get added to grub.conf, but does not
appear in the boot menu. When I add a copy of an existing entry to
40_config it does get added as a boot option, so it must be something
with the content/syntax of my menuentry. However I have no idea. The
grub site doesn''t even mention what the correct syntax for menuentry
is.
Does anybody have an idea what is wrong? What I should change so that
I can actually boot xen?
Thanks in advance,
Krist
--
krist.vanbesien@gmail.com
krist@vanbesien.org
Bremgarten b. Bern, Switzerland
--
A: It reverses the normal flow of conversation.
Q: What''s wrong with top-posting?
A: Top-posting.
Q: What''s the biggest scourge on plain text email discussions?
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
after modifying /etc/grub.d/40_custom run `update-grub` which repopulates /boot/grub/grub.cfg Krist van Besien wrote:> Hello, > > System is unbuntu 10.4 LTS, running on a single proc 4 core XEON. > I compiled and installed XEN 4.0.0 following the recipes found here: > > > http://virtually-a-machine.blogspot.com/2009/12/experimental-xen-and-ubuntu-part-1.html > http://virtually-a-machine.blogspot.com/2009/12/experimental-xen-and-ubuntu-part-2.html > (using a xen 4.0.0 tarball though). > > Now this site instructs me to add an entry to /etc/grub.d/ so that it > gets included in grub.conf when I run update-grub > > The exact example given on the site above didn''t work, so I googled a > bit in order to find out how I was supposed to do this. I settled on > adding a 40_custom file to /etc/grub.d, with the following content: > > #!/bin/sh > exec tail -n +3 $0 > # This file provides an easy way to add custom menu entries. Simply type the > # menu entries you want to add after this comment. Be careful not to change > # the ''exec tail'' line above. > menuentry ''Xen 4 Ubuntu 2.6.31.6-xen1''{ > insmod raid > insmod mdraid > insmod ext2 > set root=''(md0)'' > multiboot (md0)/xen-4.0.0.gz dummy=dummy dom0_mem=1024M > module (md0)/vmlinuz-2.6.31.13xen-kvb-1 dummy=dummy > root=/dev/mapper/thunersee_root-root ro > module (md0)/initrd.img-2.6.31.13xen-kvb-1 > } > > > My problem is that this does get added to grub.conf, but does not > appear in the boot menu. When I add a copy of an existing entry to > 40_config it does get added as a boot option, so it must be something > with the content/syntax of my menuentry. However I have no idea. The > grub site doesn''t even mention what the correct syntax for menuentry > is. > Does anybody have an idea what is wrong? What I should change so that > I can actually boot xen? > > Thanks in advance, > > Krist > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I was confirming that those steps are all you normaly have to do and that the config file should be grub.cfg not grub.conf. Please also check that you have +x (executable) permission on 40_custom otherwise it will not be ran. If you continue to have problems, show output for dpkg -l "grub*" Krist van Besien wrote:> On Mon, May 17, 2010 at 9:06 PM, listmail <listmail@triad.rr.com> wrote: > >> after modifying /etc/grub.d/40_custom run `update-grub` which repopulates >> /boot/grub/grub.cfg >> > > I did just that, as I mentioned in my mail. May problem is not that > the entry is not added, it is, my problem is that the entry is ignored > for some reason. > I''ve tested this by copying another menuentry from grub.conf in to > 40:_custom, running update-grub and this entry was displayed upon > boot. > So there is something with my menuentry syntax that causes grub to > ignore it. However I am not given any clues as to whay grub is > ignoring this entry, nor do I find any information on the web. > > So what am I missing here? > > > > Krist > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Here is my current dom0 40_custom entry:
menuentry "Xen 4.0 / Ubuntu 10.4 kernel 2.6.32.10-xen7 pvops" {
insmod raid
insmod mdraid
insmod lvm
insmod ext2
set root=''(dom0lvm-xenserver-root)''
search --no-floppy --fs-uuid --set 53920e10-f9e4-47c8-ba0f-a5a1e3fef975
multiboot /boot/xen-4.0.gz dummy=dummy iommu=0 dom0_mem=1024M
module /boot/vmlinuz-2.6.32.10-xen7 dummy=dummy
root=/dev/mapper/dom0lvm-xenserver--root ro
module /boot/initrd.img-2.6.32.10-xen7
}
And yours:
menuentry ''Xen 4 Ubuntu 2.6.31.6-xen1''{
insmod raid
insmod mdraid
insmod ext2
set root=''(md0)''
multiboot (md0)/xen-4.0.0.gz dummy=dummy dom0_mem=1024M
module (md0)/vmlinuz-2.6.31.13xen-kvb-1 dummy=dummy
root=/dev/mapper/thunersee_root-root ro
module (md0)/initrd.img-2.6.31.13xen-kvb-1
}
Richie wrote:> I was confirming that those steps are all you normaly have to do and
> that the config file should be grub.cfg not grub.conf. Please also
> check that you have +x (executable) permission on 40_custom otherwise
> it will not be ran.
>
> If you continue to have problems, show output for dpkg -l "grub*"
>
> Krist van Besien wrote:
>> On Mon, May 17, 2010 at 9:06 PM, listmail <listmail@triad.rr.com>
wrote:
>>
>>> after modifying /etc/grub.d/40_custom run `update-grub` which
>>> repopulates
>>> /boot/grub/grub.cfg
>>>
>>
>> I did just that, as I mentioned in my mail. May problem is not that
>> the entry is not added, it is, my problem is that the entry is ignored
>> for some reason.
>> I''ve tested this by copying another menuentry from grub.conf
in to
>> 40:_custom, running update-grub and this entry was displayed upon
>> boot.
>> So there is something with my menuentry syntax that causes grub to
>> ignore it. However I am not given any clues as to whay grub is
>> ignoring this entry, nor do I find any information on the web.
>>
>> So what am I missing here?
>>
>>
>>
>> Krist
>>
>>
>
>
> _______________________________________________
> 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