From: James Bulpin <james@xensource.com>
To: "Langsdorf, Mark" <mark.langsdorf@amd.com>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>,
Xen-devel@lists.xensource.com,
James Harper <james.harper@bendigoit.com.au>
Subject: Re: domU won't recognise my block devices
Date: Thu, 01 Dec 2005 17:19:29 +0000 [thread overview]
Message-ID: <438F30A1.8010000@xensource.com> (raw)
In-Reply-To: <84EA05E2CA77634C82730353CBE3A843032189C3@SAUSEXMB1.amd.com>
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
next prev parent reply other threads:[~2005-12-01 17:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-01 16:18 domU won't recognise my block devices Langsdorf, Mark
2005-12-01 17:19 ` James Bulpin [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-12-01 4:19 James Harper
2005-12-01 3:50 James Harper
2005-12-01 8:47 ` Steven Hand
2005-12-01 2:39 James Harper
2005-12-01 2:20 Ian Pratt
2005-12-01 2:06 James Harper
2005-12-01 2:02 James Harper
2005-12-01 1:34 Ian Pratt
2005-12-01 1:31 James Harper
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=438F30A1.8010000@xensource.com \
--to=james@xensource.com \
--cc=Xen-devel@lists.xensource.com \
--cc=james.harper@bendigoit.com.au \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=mark.langsdorf@amd.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.