public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Wayne Feick <waf@brunz.org>
To: Amit Shah <amit.shah@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: Does KVM PCI Device Assignment allow guests to access firewire?
Date: Wed, 28 Jan 2009 09:05:36 -0800	[thread overview]
Message-ID: <1233162336.4895.13.camel@localhost.localdomain> (raw)
In-Reply-To: <20090128151555.GD1759@amit-x200.pnq.redhat.com>

On Wed, 2009-01-28 at 20:45 +0530, Amit Shah wrote:
> Hello Wayne,
> 
> On (Tue) Jan 27 2009 [21:15:22], Wayne Feick wrote:
> > I recently saw the following:
> > 
> >    https://fedoraproject.org/wiki/Features/KVM_PCI_Device_Assignment
> > 
> > This looks like it might allow guests to access a firewire device. Can
> > anyone confirm or deny whether that will be the case? 
> 
> Is the firewire port on a PCI card? If yes, it *might* work. We've only
> tested network device assignment so far; if you have a system with VT-d,
> you can give it a try yourself.
> 
> Amit.

Thanks for the response, Amit. Yes, firewire tends to sit on the PCI
bus. Looking at the reported flags for my notebook CPU (Core 2 T7200) I
don't see vt-d so I guess it won't work on this system.

I've only started playing with non-VMware virtualization recently, and
I'm fast learning that not all Intel CPUs are equal when it comes to
virtualization support.

Wayne.



  reply	other threads:[~2009-01-28 17:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-28  5:15 Does KVM PCI Device Assignment allow guests to access firewire? Wayne Feick
2009-01-28 15:15 ` Amit Shah
2009-01-28 17:05   ` Wayne Feick [this message]
2009-01-28 18:52     ` Nikola Ciprich
2009-01-28 18:58       ` Glauber Costa
2009-01-29  3:49     ` David S. Ahern
2009-01-28 23:11   ` Michael Tokarev

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=1233162336.4895.13.camel@localhost.localdomain \
    --to=waf@brunz.org \
    --cc=amit.shah@redhat.com \
    --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