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

Re: [Xen-devel] cannot boot domU


  • To: Stephan Böni <boeni@xxxxxx>
  • From: Nicholas Lee <emptysands@xxxxxxxxx>
  • Date: Mon, 17 Oct 2005 09:50:22 +1300
  • Cc: stoeni <stoeni@xxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Sun, 16 Oct 2005 20:47:41 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=oQzvvWBprG8m8fqC69/De1bYep95pNvxDfAVgpAqtSorv04XUtKc60tFOwQmd8C+FovJDbijMTpmVhq1Ebd37pHPG7LxiVuPVkQRynAVl0bHlFoaX8JYLQoomNDs53qEQX5ZkeJc7Qt1LE9ZayhwuVQf8g8zBBJJYJHlMdF2RgE=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Two things.

Make sure hotplug is install in dom0.

Make sure the disk block device name in domU, sda1 in your case, does
not conflict with a device block in active use in dom0.  ie. change it
to something like sdb1 or sba10.

There are a few threads about this last week.

--
Nicholas Lee
http://stateless.geek.nz
gpg 8072 4F86 EDCD 4FC1 18EF  5BDD 07B0 9597 6D58 D70C

_______________________________________________
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®.