From: Tim Small <tim@buttersideup.com>
To: David Shaw <dshaw@jabberwocky.com>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: Hyper-V and IDE disks > 128GB
Date: Wed, 03 Nov 2010 11:15:03 +0000 [thread overview]
Message-ID: <4CD14437.6070402@buttersideup.com> (raw)
In-Reply-To: <12CD8E2D-64F0-46D6-8ACB-C411D7BECEE7@jabberwocky.com>
On 02/11/10 18:52, David Shaw wrote:
> Can someone suggest a direction to go in next?
>
I think I've seen this problem reported before, with the same diagnosis
that Alan gave. i.e. it's a HyperV bug, albeit one which doesn't affect
Windows operating systems.
As I believe Microsoft and Redhat have some sort of co-support agreement
with respect to each other's virtualisation platforms, you may want to
report it on Redhat's bugzilla (after verifying that the fault is also
present in the RHEL6 beta). I'd guess they'll either implement a
workaround or have some relatively straightforward mechanism to report
the fault to Microsoft - courtesy of their co-support agreement...
Cheers,
Tim.
prev parent reply other threads:[~2010-11-03 11:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-02 18:52 Hyper-V and IDE disks > 128GB David Shaw
2010-11-02 19:27 ` Alan Cox
2010-12-01 15:53 ` David Shaw
2010-11-03 11:15 ` Tim Small [this message]
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=4CD14437.6070402@buttersideup.com \
--to=tim@buttersideup.com \
--cc=dshaw@jabberwocky.com \
--cc=linux-ide@vger.kernel.org \
/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.