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

[Xen-users] domU issues


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Fred Blaise <chapeaurouge@xxxxxxxxx>
  • Date: Mon, 31 Oct 2005 15:35:13 +0100
  • Delivery-date: Mon, 31 Oct 2005 14:32:23 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=VpGnJeTLIogF49JwnGqfg8k1Pj3jh/2mE01CaS4rGpUeIgSnwtk6KPdDAajGfZhpk80LRQnmYtkHH1Xdjl12V75bLYJMoTngw+9xWdJl+lhr2nSuSPtjqB11gQVXxu+JUqk484fkVs60+MCMOu79hq71AAxml8Fnx4blMcsM3G4=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hi all

I have had issues with my dom0 due to an IDE problem. After putting CONFIG_BLK_DEV_PDC202XX_NEW=y, it was solved.

I am now encountering the same exact error with my domU. I tried to enable privileged mode in the U kernel, but no luck. my domU actually started once... go figure.

I have just check out the new hg code, and now I have a kernel panic, with domU in privileged mode. The 'Attempted to kill init' thing.

How can I make my domU aware of the CONFIG_BLK_DEV_PDC202XX_NEW=y present in the dom0, so that it can read my disks? Shouldn't it work right away anyway?

Thanks.

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

 


Rackspace

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