This is an archived copy of the Xen.org mailing list, which we have
preserved to ensure that existing links to archives are not broken.
The live archive, which contains the latest emails, can be found at
http://lists.xen.org/
Checkout /etc/default/grub. I am pretty sure Lucid hides the grub
menu by default now. Not sure if you can hit a key to make it
appear so you may have to use the desktop cd and use a chroot to fix
things.
You could also use partprobe on dom0 to make embedded lvm partitions visible if that's what you're using.
Just don't try run update-grub while chrooted. Better to hack /boot/grub/grub.cfg directly then re-run update-grub after you get it booted.
-Bruce
On 9/16/2010 4:08 PM, Priya wrote:
Hey guys!
Thanks for
the continued support and advice. It seems like my job
is not done yet.. :(
I finished
the installation using Thiago's documentation and the
configuration file from Boris.
While building the kernel, I kept the
default setting for all the questions that came up at the
prompt.
When I set up the xend and the xendaemon
services using, I still get the earlier warning:
update-rc.d
xend defaults 20 21
the output was:
update-rc.d: warning: xend start runlevel arguments
(2 3 4 5) do not match LSB
Default-Start values (3 4 5)
update-rc.d: warning: xend stop runlevel arguments
(0 1 6) do not match LSB
Default-Stop values (0 1 2 6)
And after rebooting the
machine, I don't even get the grub2 choices
for boot. All I get is a Kernel Panic message
saying:
kernel panic - not syncing
: VFS: unable to mount root FS on
unknown-block
Obviously, this is a
problem with the grub file that I
created, but shouldn't I at least get
the option to boot up the Ubuntu 10.04
that was initially working?
Now, can anyone please
tell me how to correctly assign "root"
to the correct hard disk partition
("hda.?") while creating your custom
grub file in the /etc/grub2.d/
directory?
Now that
I don't get the options from grub about which OS
operating system I want to boot up from, is there
a way to change the grub file to point to the
correct hd partition? State of complete collapse
at this time............
funny, how so many of us are having trouble with
this documentation, ive got a kernel and all
built, but i fear same as you somethings not right
with the grub config
I am using your configuration file
to install xen4.0.1 from scratch.
Thanks! Could you please also send
me the grub entry (or the file that
you made for the xen boot in the
/etc/grub.d/ directory). I just want
to confirm that it is the same as
the original tutorial.
Also, did you change anything else
from the steps given below (from the
original mail by Thiago) while
installing your version:
3- Download, compile and install
Linux from the Jemery's tree:
make prep-kernels
wget http://livexen01.worldweb.com.br/linux-config-2.6.23.18-xen-4.0.1-1-tcmc-10.08-1
-O
build-linux-2.6-pvops_x86_64/.config
cd build-linux-2.6-pvops_x86_64
make menuconfig # Change whatever
you want, if you now what you're
doing...
make
chmod g-s /usr/src/ -R
make deb-pkg
dpkg -i
../linux-image-2.6.32.18-tcmc-10.08-1-xen_2.6.32.18-tcmc-10.08-1-xen-*.deb
depmod 2.6.32.18-tcmc-10.08-1-xen
update-initramfs -c -k
2.6.32.18-tcmc-10.08-1-xen
4- Enable Xen at boot:
update-rc.d xend defaults 20 21
update-rc.d xendomains defaults 21
20
5- Configure the Grub2:
vim /etc/grub.d/40_custom
---- cut here ----
#!/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.
xenfs is
not mounted.
Here is the
output for the
mount command:
-------------
/dev/sda1 on /
type ext4
(rw,errors=remount-ro)
proc on /proc
type proc
(rw,noexec,nosuid,nodev)
none on
/proc/sys/fs/binfmt_misc
type
binfmt_misc
(rw,noexec,nosuid,nodev)
none on /sys
type sysfs
(rw,noexec,nosuid,nodev)
none on
/sys/kernel/debug
type debugfs
(rw)
none on
/sys/kernel/security
type
securityfs
(rw)
none on /dev
type tmpfs
(rw,mode=0755)
none on
/dev/pts type
devpts
(rw,noexec,nosuid,gid=5,mode=0620)
none on
/dev/shm type
tmpfs
(rw,nosuid,nodev)
none on
/var/run type
tmpfs
(rw,nosuid,mode=0755)
none on
/var/lock type
tmpfs
(rw,noexec,nosuid,nodev)
none on
/lib/init/rw
type tmpfs
(rw,nosuid,mode=0755)
/dev/sdb1 on
/media/08AF-8FE8
type vfat
(rw,nosuid,nodev,uhelper=udisks,uid=1000,gid=1000,shortname=mixed,dmask=0077,utf8=1,flush)
------------------------------
I did a
modprobe on
xenfs but I
cannot mount
it yet. Could
you please
give me the
correct
command line
arguments for
doing so. Here
are my
outputs:
------------------------
root@XenOpen:~#
modprobe xenfs
root@XenOpen:~#
mount xenfs
mount: can't
find xenfs in
/etc/fstab or
/etc/mtab
-----------------------------------------------------------
Thanks a lot
for your
advice. Really
appreciate it!
@Borris:
There is
no "xen"
directory in
/dev....Here
is what I
have:
> And
then when I
reboot the
machine, xend
does not
start. On
issuing
> the
command
/etc/init.d/xend
start, or
status, there
is no terminal
> output.
> When I
type in "xend
start"
directly, I
get the
following
error
> message:
> sudo
xend start
>>
>> the
output is:
>>
>> ERROR
Internal
error: Could
not obtain
handle on
privileged
command
> interface
Do you
have xenfs
mounted?
see if the
following line
comes up in
the list if
you type
mount:
# mount
...
xenfs on
/proc/xen type
xenfs (rw)
...
If not, then
you can try
mounting it
manually. If
xenfs is
compiled as
a module, you
may have to
modprobe it
first. If it
is not enabled
in
your
kernel, then
you have to
rebuild your
dom0 kernel,
and enable it.
On my (Ubuntu
Server 10.04.1
based) system,
this gets
mounted
automatically
by either udev
or xend itself
(it is not in
fstab).
In my
experience on
this system,
xend fails
ususually due
to one of the
following
reasons:
1) Failure to
mount xenfs
(because it is
not
configured, or
the module
is
not loaded).
2)
Inconsistent
installation
of xentools
(in wrong
python
directory or
mixed with
older
version).
Home