[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] Re: Strange Block Device Issue


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: Alexander Wigen <alex@xxxxxxxxx>
  • Date: Thu, 19 Apr 2007 04:05:54 +0000 (UTC)
  • Delivery-date: Thu, 19 Apr 2007 05:58:59 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Jayson Vantuyl <jvantuyl <at> engineyard.com> writes:

> 
> 
> Has anyone seen anything remotely like this before? First, I'm running the 
initial Xen-3.0.4 release, although I experienced it with 3.0.3 as well.
> 
> The problem occurs when I create a new DomU with the following setup:
> 
> kernel = '/boot/vmlinuz-2.6.16.33-xenU-domU'
> memory = 384
> name = 'some_name'
> vif = [ 'bridge=xenbr0' ]
> disk = [
> Â Â Â Â 'phy:/dev/working/lvm/device,sda1,w',
> Â Â Â Â 'phy:/dev/working/lvm/device2,sda2,w',
> ÂÂ ÂÂ Â'phy:/dev/etherd/e2.5,sdc,w',
> ÂÂ ÂÂ Â'phy:/dev/etherd/e2.6,sdd,w',
> Â Â ÂÂ ]
> root = '/dev/sda1 ro'
> vcpus = 1

Hi Jayson,

I just ran into the same issue with vblade running on a different host and 
using it as:
disk = ['phy:/dev/etherd/e2.0,hda1,w']

100% cpu usage in dom0 for xvd. I'm using Xen 3.0.2


Cheers

Alexander Wigen


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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.