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


[Xen-users] Xvd Problem

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Xvd Problem
From: Jayson Vantuyl <jvantuyl@xxxxxxxxxxxxxx>
Date: Fri, 9 Feb 2007 13:30:17 -0600
Delivery-date: Fri, 09 Feb 2007 11:31:25 -0800
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
We recently added a disk to our Coraid SAN.  We've used tons of devices off of this SAN with Xen before, but this time we experienced some weird behavior.

I configured a DomU to have the device directly offered as a disk (i.e.  'phy/dev/etherd/e1.1,sdb1,rw').  When I tried to boot it, an xvd process showed up as usual.  However, it consumed 100% processor usage and the domain never started.  I also couldn't kill it without rebooting the machine.

The only thing about this device (that I can tell) is that it has a high device minor:

brw-rw---- 1 root disk 152, 272 Feb  4 01:25 /dev/etherd/e1.1

Does the Xen vbd have problems with these newer device nodes?

Jayson Vantuyl
Systems Architect

Xen-users mailing list
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] Xvd Problem, Jayson Vantuyl <=