From mboxrd@z Thu Jan 1 00:00:00 1970 From: James Bulpin Subject: Re: domU won't recognise my block devices Date: Thu, 01 Dec 2005 17:19:29 +0000 Message-ID: <438F30A1.8010000@xensource.com> References: <84EA05E2CA77634C82730353CBE3A843032189C3@SAUSEXMB1.amd.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <84EA05E2CA77634C82730353CBE3A843032189C3@SAUSEXMB1.amd.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Langsdorf, Mark" Cc: Ian Pratt , Xen-devel@lists.xensource.com, James Harper List-Id: xen-devel@lists.xenproject.org We're testing both 32 and 64 bit builds on a mixture of Xeon and Opteron. Many of my colleagues use Opteron machines as their personal test boxes as well. I've just fired off a test run explicitly on an Opteron-based Sun V20z to make sure all is well: it it has booted and started a guest just fine. Regards, James Langsdorf, Mark wrote: >>>No initrd. AoE is only used by dom0. Boot messages follow: >> >>It works for me... Are you sure you haven't borked your config? > > > Ian, are you testing on Opterons in 64-bit mode or some other > hardware? One of the common themes in these bug reports (see > also bugzilla #392) is 64-bit Opterons. 64-bit Intel Xeon > does not seem to be affected in the same way. > > -Mark Langsdorf > AMD, Inc. > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel