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

[Xen-users] Can not start Guest, receiving errors

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Can not start Guest, receiving errors
From: "Octavian Teodorescu" <octav@xxxxxxxxxxxxxxxx>
Date: Tue, 29 May 2007 14:14:36 +0300 (EEST)
Delivery-date: Tue, 29 May 2007 04:11:44 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: SquirrelMail/1.4.8-4.el4.centos
Hi guys,

I have a CentOS installed on my system (P4- core2duo, sata hard drive). At
installation I have also installed the Virtualization package which
installed xen, and made the boot record for xen.

I realized that I don't have kernel-xen0 and kernel-xenU as I had in
Fedora (fedora was another unlucky experience with xen). My grub.conf:
=================
default=0
timeout=5
splashimage=(hd0,0)/boot/grub/splash.xpm.gz
hiddenmenu
title CentOS (2.6.18-8.1.4.el5xen)
root (hd0,0)
kernel /boot/xen.gz-2.6.18-8.1.4.el5
module /boot/vmlinuz-2.6.18-8.1.4.el5xen ro root=LABEL=/ rhgb quiet
module /boot/initrd-2.6.18-8.1.4.el5xen.img
title CentOS (2.6.18-8.el5xen)
root (hd0,0)
kernel /boot/xen.gz-2.6.18-8.el5
module /boot/vmlinuz-2.6.18-8.el5xen ro root=LABEL=/ rhgb quiet
module /boot/initrd-2.6.18-8.el5xen.img
===========
The dom0 boots ok, and I didn't had any problems with it. Xend is started.

I am tring to create a virtual machine (initially I wanted to install
FreeBSD, but I've read just before posting that can not be
paravirtualized, so I'll use another version of linux or the same).
I have the following config file called linux:
------------------
#kernel = "/boot/vmlinuz-2.6.10-xenU"
kernel = "/boot/vmlinuz-2.6.18-8.1.4.el5xen"

# The domain build function. Default is 'linux'.
builder='linux-test'

memory = 512

name = "bsd"

# List of which CPUS this domain is allowed to use, default Xen picks
#cpus = "" # leave to Xen to pick
#cpus = "0" # all vcpus run on CPU0
#cpus = "0-3,5,^1" # run on cpus 0,2,3,5
vcpus = 1

vif = [ '', 'bridge=xenbr1' ]

device_model = '/usr/lib64/xen/bin/qemu-dm'

disk = [ 'phy:/dev/VGvhosts/root,hda1,w',
'phy:/dev/VGvhosts/swap,hda2,w',
'phy:/dev/VGvhosts/tmp,hda3,w' ]
# 'phy:/dev/VGvhosts/var,hda4,w' ]

dhcp="dhcp"

# Set root device.
root = "/dev/hda1"


cdrom = "/home/admn/iso/6.2-RELEASE-i386-disc1.iso"
boot = "dc"

[root@octavpc1 xen]# mcedit linux

[root@octavpc1 xen]# cat linux
#kernel = "/boot/vmlinuz-2.6.10-xenU"
kernel = "/boot/vmlinuz-2.6.18-8.1.4.el5xen"

# The domain build function. Default is 'linux'.
builder='linux'

memory = 512

name = "linux-test"

# List of which CPUS this domain is allowed to use, default Xen picks
#cpus = "" # leave to Xen to pick
#cpus = "0" # all vcpus run on CPU0
#cpus = "0-3,5,^1" # run on cpus 0,2,3,5
vcpus = 1

vif = [ '', 'bridge=xenbr1' ]

device_model = '/usr/lib64/xen/bin/qemu-dm'

disk = [ 'phy:/dev/VGvhosts/root,hda1,w',
'phy:/dev/VGvhosts/swap,hda2,w',
'phy:/dev/VGvhosts/tmp,hda3,w' ]
# 'phy:/dev/VGvhosts/var,hda4,w' ]

dhcp="dhcp"

# Set root device.
root = "/dev/hda1"


cdrom = "/home/admn/iso/6.2-RELEASE-i386-disc1.iso"
boot = "dc"
----------------------


When I do a xm create -c linux, I see the vm booting (at least that's what
I think it's doing) and I receive an error. Here are the last line of what
I see on my screen:
----------------
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
XENBUS: Device with no driver: device/vbd/769
XENBUS: Device with no driver: device/vbd/770
XENBUS: Device with no driver: device/vbd/771
XENBUS: Device with no driver: device/vif/0
XENBUS: Device with no driver: device/vif/1
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
VFS: Cannot open root device "hda1" or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(0,0)


If I try to mount the logical volumes, I get:
--------------------
Using config file "./linux".
Error: destroyDevice() takes exactly 3 arguments (2 given)
----------------------
I tried to change from hda to sda, I have also tried sda3 for all of them
since my disk looks like this:
sda1 - / -30GB
sda2 - swap -3,5GB
sda3 - lvm - 209GB
On the lvm I have the following partitions formated as ext3: root, var,
tmp and .... swap.

I know I have the image of a bsd cd know (I'll make an image of a linux
and use that instead), but it should at least boot! Right?

So I tried a lot of Google and couldn't find an answer to my problem. This
is my first time with xen. Can U please help me?

Thanks in advance.


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

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