WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Kernel panic - not syncing: VFS: unable to mount root ...... Re: [Xen-us

To: "CLIFFORD ILKAY" <clifford_ilkay@xxxxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Kernel panic - not syncing: VFS: unable to mount root ...... Re: [Xen-users] xen on a remote computer, installing virtual machines without cds
From: "Sueveges Gyoergy" <georg@xxxxxxxxxxxx>
Date: Sat, 08 Oct 2005 22:53:13 +0200
Delivery-date: Sat, 08 Oct 2005 20:54:14 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <200510012237.29919.clifford_ilkay@xxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Organization: etixpert Gmbh
References: <opsxt285clp7qfxi@xxxxxxxxxxx> <200510012237.29919.clifford_ilkay@xxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Opera M2/7.54u1 (Linux, build 892)
Hi

Thnx for everybody`s help on subject of installing xen on remote computer. I decided to make a home installation first of all as a reproduction of remote system (with suse 9.3 with lilo, fs: resiserfs), and only when everything works fine I will try to install it remotely.

I could already migrate to grub from lilo (Yast could do this), and install the xen rpm-s from yast ( since I`m not a linux expert :) Unfortunetely the yast doesn´t make any entry into the menu.lst of grub. So I had to insert the title xen manually. And it doesn`t work. When booting Igot kernel panic:

 kernel panic - no syncing: VFS: Unable to mount root fs unknown block(0,0)

But I followed the instructions in the xen doc, so I now have the following entries in menu.lst:

timeout 8
hiddenmenu
default 0

title Xen 2.0 / XenLinux 2.6
    kernel (hd0,6)/boot/xen.gz dom0_mem=131072 noreboot
module (hd0,6)/boot/vmlinuz-xen root=/dev/hda7 selinux=0 resume=/dev/hda6 showopts console=tty0

title SUSE_LINUX_9.3
kernel (hd0,6)/boot/vmlinuz root=/dev/hda7 vga=0x31a selinux=0 splash=silent linux26 resume=/dev/hda6 showopts
    initrd (hd0,6)/boot/initrd
....

I also tried only with the parameters written in the xen doc (no selinux, resume, showopts). When I insert initrd-xen (module (hd0,6)/boot/initrd-xen) too, then it says, that kernel should be loaded first.

Maybe it doesn´t recognize the reiserfs file system? What could be done? I saw in the archive that someone had similar problem with DevFS, but I don`t think that it is also a solution for me. Since I`m not a linux expert, Maybe may the problem is a very basic problem?
Which way should I go? Thnx for your help in advance :)

Best Regards
 George






On Sat, 1 Oct 2005 22:37:29 -0400, CLIFFORD ILKAY <clifford_ilkay@xxxxxxxxxxx> wrote:

On September 28, 2005 18:25, Sueveges Gyoergy wrote:
Hi All,

  I have just downloaded xen. We rent a computer with suse 9.3
(1000km from here, access with ssh2). I'd like to install 2 virtual
machines (both with suse), of course without CD or floppy (due to
distance). So I have no X and no CD. In this case what can be the
best way to install xen, and the virtual machines?

Thnx
  George

ps: As I see in the documentation, xen can be configured only with
grub. I have lilo, so xen with lilo is not possible?

What you are trying to do is fraught with dangers. It is not
impossible but one minor mistake and you will have no remote access.
I have done a remote server installation with no remote hands but it
was not easy. I had a means of power cycling the server and
specifying PXE boot on the next boot. I could then attempt to fix the
problem on the previous boot from the hard disk though it was not
always obvious what the problem was. If the problem was before
syslogd started, there would be no indication of it in the logs. It
took some trial and error to get it working but I eventually got it
working.

Make sure to include kernel modules for your hardware and filesystems.
I built my dom0 and domU kernels as monolithic kernels and disabled
support for module loading.

Some (many?) colocation facilities assign static IPs via dhcp. I got
bitten by this once when this possibility did not occur to me until I
had the provider reimage the drive of the server with their custom
Red Hat distro. Once I realized that their installation was getting
its IP via dhcp, I made the necessary change to my installation of
Mandrake and I was off to the races. In your case, you already have a
working installation so you should be able to use that as a point of
reference.

Once you have the kernel booted, be very careful with iptables rules.
You can easily lock yourself out. Until you get this sorted out, you
might want to specify one IP address that you have access to, not
necessarily the one that you are using for the remote configuration
and testing, for which everything is allowed.



--
Using Opera's revolutionary e-mail client: http://www.opera.com/m2/

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

<Prev in Thread] Current Thread [Next in Thread>