* Alex Williamson (alex.william...@hp.com) wrote:
> On Tue, 2009-04-07 at 07:54 -0700, Chris Wright wrote:
> > * Sheng Yang (sh...@linux.intel.com) wrote:
> > > On Tuesday 07 April 2009 08:02:10 Chris Wright wrote:
> > > > * Alex Williamson (alex.william...@hp.com) wrote:
> > > > > I'm wondering if
On Tue, 2009-04-07 at 07:54 -0700, Chris Wright wrote:
> * Sheng Yang (sh...@linux.intel.com) wrote:
> > On Tuesday 07 April 2009 08:02:10 Chris Wright wrote:
> > > * Alex Williamson (alex.william...@hp.com) wrote:
> > > > I'm wondering if we need a spot for device specific fixups for PCI
> > > > p
* Sheng Yang (sh...@linux.intel.com) wrote:
> On Tuesday 07 April 2009 08:02:10 Chris Wright wrote:
> > * Alex Williamson (alex.william...@hp.com) wrote:
> > > I'm wondering if we need a spot for device specific fixups for PCI
> > > pass-through. In the example below, I want to expose a single por
On Tuesday 07 April 2009 08:02:10 Chris Wright wrote:
> * Alex Williamson (alex.william...@hp.com) wrote:
> > I'm wondering if we need a spot for device specific fixups for PCI
> > pass-through. In the example below, I want to expose a single port of
> > an Intel 82571EB quad port copper NIC to a
* Alex Williamson (alex.william...@hp.com) wrote:
>
> I'm wondering if we need a spot for device specific fixups for PCI
> pass-through. In the example below, I want to expose a single port of
> an Intel 82571EB quad port copper NIC to a guest. It works great until
> I shutdown the guest, at whi
I'm wondering if we need a spot for device specific fixups for PCI
pass-through. In the example below, I want to expose a single port of
an Intel 82571EB quad port copper NIC to a guest. It works great until
I shutdown the guest, at which point the guest e1000e driver knows by
the device ID that
