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-devel

Re: [Xen-devel] Re: pv_ops dom0 USB fixed

To: "Jeremy Fitzhardinge" <jeremy@xxxxxxxx>
Subject: Re: [Xen-devel] Re: pv_ops dom0 USB fixed
From: "Todd Deshane" <deshantm@xxxxxxxxx>
Date: Thu, 11 Dec 2008 16:16:41 -0500
Cc: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Aviv Grafi <aviv@xxxxxxxxxxxx>
Delivery-date: Thu, 11 Dec 2008 13:17:23 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:reply-to :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=kxKRFZHU22Njh6Q3xAAdpuEqs/Uluq+nbDg9TMjWcvE=; b=MwKbdXtN2Q/AyfexdFba3JbMi476mxMcsfLK36yUqbTYAr7j6pgu7fP3pwIxvu8Vr7 wGSIsN1K2Fj0BGm9JFvP8mF0Jz/YoHUHe9hkyIMpqpR4FV9tXspQhFSS/+O9CQ2idoIj 17U3WtWjRwp9xWEzwJ1X3WAkv/LyMXD9G96zE=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:to:subject:cc:in-reply-to :mime-version:content-type:content-transfer-encoding :content-disposition:references; b=ZyQ0ZYPkZymVQrOTlbx29Ipaqq+V6a0pFLYb5/2ip69bTIcoEIqLo9ZM7ZkBXbwWGX ktcFrJTaatx3uIA05sRe1rsXMq+hZbMDiKkk/NryXn6uLHNMhPIMzqO9a7dtGfQWMsBM yJUIknepvzqw+lLmJJe93MFdI62LbLnl1A7fk=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <49417DA5.7000400@xxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4940210C.1060401@xxxxxxxx> <1e16a9ed0812101448i52a39946o528c74effa2690ab@xxxxxxxxxxxxxx> <4940C98D.6070004@xxxxxxxx> <1e16a9ed0812110850odff8f56h836b7187ad0c64b0@xxxxxxxxxxxxxx> <49415945.3030508@xxxxxxxx> <1e16a9ed0812111147h3416cbb5uc11a8b9f5f0d0e80@xxxxxxxxxxxxxx> <1e16a9ed0812111203l73a0bf5ek5f1264c4097718ef@xxxxxxxxxxxxxx> <4941778F.4090709@xxxxxxxx> <1e16a9ed0812111229s3e9e3e9eia8c909516daf10a2@xxxxxxxxxxxxxx> <49417DA5.7000400@xxxxxxxx>
Reply-to: deshantm@xxxxxxxxx
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Thu, Dec 11, 2008 at 3:52 PM, Jeremy Fitzhardinge <jeremy@xxxxxxxx> wrote:
> Todd Deshane wrote:
>>>>
>>>> In the BIOS it has two SATA operation modes.
>>>> Normal and Legacy.
>>>>
>>>> If it is set to legacy, the Xen kernel stops dead at
>>>> the initramfs prompt.
>>>>
>>>> Xen boot of Normal and Legacy mode attached.
>>>>
>>>> I will now try to copy my xen config over to the
>>>> VT-d (755) box.
>>>>
>>>
>>> Hm, I would have expected to see some reference to "ahci" in there.  Does
>>> your initscript look for the root device via a hardcoded device, or by
>>> using
>>> label/uuid?
>>>
>>>
>>
>> Which init script are you referring to?
>>
>
> Sorry, I meant your initrd.
>

Oh, it is a hard-coded device for the Xen kernel boot.

Cheers,
Todd

-- 
Todd Deshane
http://todddeshane.net
http://runningxen.com

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

<Prev in Thread] Current Thread [Next in Thread>