public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 116611] New: scsi-block passthrough breaks with external pci-express SATA controller
Date: Mon, 18 Apr 2016 05:26:59 +0000	[thread overview]
Message-ID: <bug-116611-28872@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=116611

            Bug ID: 116611
           Summary: scsi-block passthrough breaks with external
                    pci-express SATA controller
           Product: Virtualization
           Version: unspecified
    Kernel Version: 4.4
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: kvm
          Assignee: virtualization_kvm@kernel-bugs.osdl.org
          Reporter: mutedbytes@gmail.com
        Regression: No

My hardware provides 6 SATA ports directly from Intel Z97 chipset, and 2
additional SATA ports from a Marvell 88SE9172 attached to the Z97 PCI-e bus. A
physical block device attached directly to the chipset ports can successfully
be passed through using virtio-scsi-pci controller and scsi-block device to
Windows 8/8.1/10 guest using qemu 2.5. However, attaching the same physical
drive to the Marvell controller results in missing drives or weird/corrupted
behavior in the guest when attempting to perform the same passthrough (for
example, no hard drives are found during guest installation procedure after
loading virtio drivers). This seems to have broken somewhere in 4.2 or later,
as it works fine as expected in 4.1. The broken behavior appears in 4.4 and
4.5, though I have not been able to test 4.2 and 4.3.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

                 reply	other threads:[~2016-04-18  5:27 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bug-116611-28872@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=kvm@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox