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] problem starting domains

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] problem starting domains
From: Luke <secureboot@xxxxxxxxx>
Date: Tue, 24 Jan 2006 09:38:39 -0500
Delivery-date: Tue, 24 Jan 2006 14:46:48 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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
I'm trying to start a number of lvm-backend domUs on a Dell Poweredge 2850 (i've got nousb on the grub command line, and no usb in the kernel).

Some domUs are created and started successfully.

However, quite a few of my domUs don't start properly. I get the correct Started Domain messages... but then the domain doesn't "go anywhere", meaning it uses .3 cpu time, then never any more.

I create the domUs by dd if=/dev/xen/base_image of=/dev/xen/ new_image, after creating a new_image using lvcreate of the same size as the base image. I've verified that these images actually exist.

Looking through the log from xend.log below, i see an error about / dev/hda1 (the root device given to the domU on the command line, which you can also see in the logs) not existing. Why would that be?

I'm running the xen-3.0 testing...

The physical machine has 2 Xeon dual-core processors with hyperthreading (which is enabled). Should I disable hyperthreading in the kernel? Would that make a difference? I saw a post earlier about that...

Error log attached, with ip addresses replaced.

Attachment: xen.log
Description: Binary data


Thanks for the help.


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>