From: Andi Reinbrech <andi.reinbrech@darwinistic.com>
To: xen-devel@lists.xen.org
Subject: 4.2 kernel 3.5 USB PCI Passthrough
Date: Tue, 25 Sep 2012 09:09:57 +0200 [thread overview]
Message-ID: <506158C5.6000302@darwinistic.com> (raw)
Hi Xenners,
I have been using 4.2 for a very long time now, and recently (since
upgrading to rc2), I've had some strange issues cropping up:
None of my disk images boot with xl create; I have moved the important
ones to LVM disks, since phy: boots fine. I have hacked some of the xen
code to make this work (but forgot which hack got it working, it has to
do with the caching modes in the file open calls - I will double check
and get back to the list). My qemu disks are always reported as
0mb-sized volumes in the BIOS screen when this bug manifests itself.
Neither raw nor qcow2 images work.
When I upgraded to kernel 3.5, my USB PCI passthrough stopped working.
The secondary VGA passthrough still works fine, just the USB host
controller that is passed through gets claimed by xen, but the guest
cannot load drivers for the controller. I.e. the guest (Windoze 7) sees
it in device manager, but the device fails to activate.
Last night I upgraded to the latest 3.5.4 in the fc17 repo, and the USB
issue was still there. The weird thing though, is that it seems that my
raw images magically started booting. I still need to investigate this,
in more detail to make sure I'm not mixing up versions and get
conclusive results.
Apologies, this post is not too detailed and contains too many "maybes",
but I though there may be a simple answer that someone else had stumbled
across the same issues recently.
I will compile rc3 later on and run decent comparisons on both kernels,
as well as raw and LVM machines.
Kind regards,
Andi
next reply other threads:[~2012-09-25 7:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-25 7:09 Andi Reinbrech [this message]
2012-09-25 8:01 ` 4.2 kernel 3.5 USB PCI Passthrough Pasi Kärkkäinen
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=506158C5.6000302@darwinistic.com \
--to=andi.reinbrech@darwinistic.com \
--cc=xen-devel@lists.xen.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.