On Mon, Feb 28, 2011 at 3:31 PM, Chris Wright wrote:
>
> * James Neave (robo...@gmail.com) wrote:
> > HOLY CRAP IT WORKS 8@
>
>
> Hey, great! ;)
>
> > ...almost...
> >
> > OK, "clear_emulator_capabilities=0" solved the IRQ problem (which was,
> > as it turns out, the rawio problem)
> > My VM c
On Mon, Feb 28, 2011 at 8:25 PM, James Neave wrote:
> On Mon, Feb 28, 2011 at 3:31 PM, Chris Wright wrote:
>> * James Neave (robo...@gmail.com) wrote:
>>> HOLY CRAP IT WORKS 8@
>>
>>
>> Hey, great! ;)
>>
>>> ...almost...
>>>
>>> OK, "clear_emulator_capabilities=0" solved the IRQ problem (whic
On Mon, Feb 28, 2011 at 3:31 PM, Chris Wright wrote:
> * James Neave (robo...@gmail.com) wrote:
>> HOLY CRAP IT WORKS 8@
>
>
> Hey, great! ;)
>
>> ...almost...
>>
>> OK, "clear_emulator_capabilities=0" solved the IRQ problem (which was,
>> as it turns out, the rawio problem)
>> My VM came up,
* James Neave (robo...@gmail.com) wrote:
> HOLY CRAP IT WORKS 8@
Hey, great! ;)
> ...almost...
>
> OK, "clear_emulator_capabilities=0" solved the IRQ problem (which was,
> as it turns out, the rawio problem)
> My VM came up, both the tuners were there and after the firmware
> install I was
On Fri, Feb 25, 2011 at 11:31 PM, Chris Wright wrote:
> * James Neave (robo...@gmail.com) wrote:
>> On Fri, Feb 25, 2011 at 11:02 PM, James Neave wrote:
>> > On Fri, Feb 25, 2011 at 10:47 PM, James Neave wrote:
>> >> On Fri, Feb 25, 2011 at 12:06 AM, Chris Wright
>> >> wrote:
>> >>> * James Ne
* James Neave (robo...@gmail.com) wrote:
> On Fri, Feb 25, 2011 at 11:02 PM, James Neave wrote:
> > On Fri, Feb 25, 2011 at 10:47 PM, James Neave wrote:
> >> On Fri, Feb 25, 2011 at 12:06 AM, Chris Wright wrote:
> >>> * James Neave (robo...@gmail.com) wrote:
> OK, here's my latest dmesg wit
* James Neave (robo...@gmail.com) wrote:
> On Fri, Feb 25, 2011 at 12:06 AM, Chris Wright wrote:
> > * James Neave (robo...@gmail.com) wrote:
> >> OK, here's my latest dmesg with amd_iommu_dump and debug with no quiet
> >> http://pastebin.com/JxEwvqRA
> >
> > Yeah, that's what I expected:
> >
> >
On Fri, Feb 25, 2011 at 11:02 PM, James Neave wrote:
> On Fri, Feb 25, 2011 at 10:47 PM, James Neave wrote:
>> On Fri, Feb 25, 2011 at 12:06 AM, Chris Wright wrote:
>>> * James Neave (robo...@gmail.com) wrote:
OK, here's my latest dmesg with amd_iommu_dump and debug with no quiet
http:
On Fri, Feb 25, 2011 at 10:47 PM, James Neave wrote:
> On Fri, Feb 25, 2011 at 12:06 AM, Chris Wright wrote:
>> * James Neave (robo...@gmail.com) wrote:
>>> OK, here's my latest dmesg with amd_iommu_dump and debug with no quiet
>>> http://pastebin.com/JxEwvqRA
>>
>> Yeah, that's what I expected:
On Fri, Feb 25, 2011 at 12:06 AM, Chris Wright wrote:
> * James Neave (robo...@gmail.com) wrote:
>> OK, here's my latest dmesg with amd_iommu_dump and debug with no quiet
>> http://pastebin.com/JxEwvqRA
>
> Yeah, that's what I expected:
>
> [ 0.724403] AMD-Vi: DEV_ALIAS_RANGE
* James Neave (robo...@gmail.com) wrote:
> Just out of interest, what kind of mileage would I expect out of
> buying a shiny new PCIe tuner?
Hard to say. One advantage would be if it's using MSI or MSI-X
interrupts.
> Can I pass through PCIe?
Often, yes (still some caveats w.r.t. extended confi
* James Neave (robo...@gmail.com) wrote:
> OK, here's my latest dmesg with amd_iommu_dump and debug with no quiet
> http://pastebin.com/JxEwvqRA
Yeah, that's what I expected:
[0.724403] AMD-Vi: DEV_ALIAS_RANGE devid: 08:00.0 flags:
00 devid_to: 00:14.4
[0.724439] AMD-Vi
* James Neave (robo...@gmail.com) wrote:
> libvirtError: this function is not supported by the connection driver:
> Unable to reset PCI device :00:14.4: no FLR, PM reset or bus reset
> available
Right, libvirt is more restrictive than qemu-kvm (forgot you were using
libvirt here).
> There is
On Wed, Feb 23, 2011 at 8:09 PM, James Neave wrote:
> On Wed, Feb 23, 2011 at 7:44 PM, James Neave wrote:
>> On Wed, Feb 23, 2011 at 12:11 AM, Chris Wright wrote:
>>> * James Neave (robo...@gmail.com) wrote:
On Tue, Feb 22, 2011 at 1:51 AM, Chris Wright wrote:
> * James Neave (robo...
On Wed, Feb 23, 2011 at 7:44 PM, James Neave wrote:
> On Wed, Feb 23, 2011 at 12:11 AM, Chris Wright wrote:
>> * James Neave (robo...@gmail.com) wrote:
>>> On Tue, Feb 22, 2011 at 1:51 AM, Chris Wright wrote:
>>> > * James Neave (robo...@gmail.com) wrote:
>>> >> Does anybody know the debug kerne
On Wed, Feb 23, 2011 at 12:11 AM, Chris Wright wrote:
> * James Neave (robo...@gmail.com) wrote:
>> On Tue, Feb 22, 2011 at 1:51 AM, Chris Wright wrote:
>> > * James Neave (robo...@gmail.com) wrote:
>> >> Does anybody know the debug kernel switches for iommu?
>> >
>> > Two helpful kernel commandl
* James Neave (robo...@gmail.com) wrote:
> On Tue, Feb 22, 2011 at 1:51 AM, Chris Wright wrote:
> > * James Neave (robo...@gmail.com) wrote:
> >> Does anybody know the debug kernel switches for iommu?
> >
> > Two helpful kernel commandline options are:
> >
> > amd_iommu_dump debug (and drop "quiet
2011/2/22 Roedel, Joerg :
> On Tue, Feb 22, 2011 at 04:18:20AM -0500, James Neave wrote:
>> On Tue, Feb 22, 2011 at 1:51 AM, Chris Wright wrote:
>> I added "capability sys_rawio" to the libvirtd apparmor profile,
>> restarted apparmor and libvirt-bin and it just complained about the
>> apparmor pr
On Tue, Feb 22, 2011 at 04:18:20AM -0500, James Neave wrote:
> On Tue, Feb 22, 2011 at 1:51 AM, Chris Wright wrote:
> I added "capability sys_rawio" to the libvirtd apparmor profile,
> restarted apparmor and libvirt-bin and it just complained about the
> apparmor profile.
> The only other thing I
On Tue, Feb 22, 2011 at 1:51 AM, Chris Wright wrote:
> * James Neave (robo...@gmail.com) wrote:
>> Finally, here is the very latest dmesg:
>> http://pastebin.com/9HE61K62
>
> OK, this is an AMD IOMMU box.
>
> [0.00] ACPI: IVRS cfcf9830 000E0 (v01 AMD RD890S
> 00202031 AMD 00
* James Neave (robo...@gmail.com) wrote:
> Finally, here is the very latest dmesg:
> http://pastebin.com/9HE61K62
OK, this is an AMD IOMMU box.
[0.00] ACPI: IVRS cfcf9830 000E0 (v01 AMD RD890S 00202031
AMD )
It's discovered and enalbed properly:
[0.698992] AMD
On Mon, Feb 21, 2011 at 11:28 PM, Chris Wright wrote:
> * Alex Williamson (alex.william...@redhat.com) wrote:
>> I don't know why you're getting -EBUSY for this device, but maybe we can
>> start from a clean slate and see if it helps. Here's what I would
>> suggest:
>
> I bet this is an AMD IOMMU
* Alex Williamson (alex.william...@redhat.com) wrote:
> I don't know why you're getting -EBUSY for this device, but maybe we can
> start from a clean slate and see if it helps. Here's what I would
> suggest:
I bet this is an AMD IOMMU box. Can we get full dmesg?
--
To unsubscribe from this list:
On Mon, Feb 21, 2011 at 10:55 PM, James Neave wrote:
> On Mon, Feb 21, 2011 at 10:49 PM, James Neave wrote:
>> On Mon, Feb 21, 2011 at 10:25 PM, James Neave wrote:
>>> On Mon, Feb 21, 2011 at 9:01 PM, Alex Williamson
>>> wrote:
On Mon, 2011-02-21 at 20:31 +, James Neave wrote:
> On
On Mon, Feb 21, 2011 at 10:49 PM, James Neave wrote:
> On Mon, Feb 21, 2011 at 10:25 PM, James Neave wrote:
>> On Mon, Feb 21, 2011 at 9:01 PM, Alex Williamson
>> wrote:
>>> On Mon, 2011-02-21 at 20:31 +, James Neave wrote:
On Mon, Feb 14, 2011 at 5:48 PM, Alex Williamson
wrote:
>
On Mon, Feb 21, 2011 at 10:25 PM, James Neave wrote:
> On Mon, Feb 21, 2011 at 9:01 PM, Alex Williamson
> wrote:
>> On Mon, 2011-02-21 at 20:31 +, James Neave wrote:
>>> On Mon, Feb 14, 2011 at 5:48 PM, Alex Williamson
>>> wrote:
>>> > On Sat, 2011-02-12 at 16:04 +, James Neave wrote:
>>
On Mon, Feb 21, 2011 at 9:01 PM, Alex Williamson
wrote:
> On Mon, 2011-02-21 at 20:31 +, James Neave wrote:
>> On Mon, Feb 14, 2011 at 5:48 PM, Alex Williamson
>> wrote:
>> > On Sat, 2011-02-12 at 16:04 +, James Neave wrote:
>> >> On Tue, Feb 8, 2011 at 10:17 AM, James Neave wrote:
>> >>
On Mon, 2011-02-21 at 20:31 +, James Neave wrote:
> On Mon, Feb 14, 2011 at 5:48 PM, Alex Williamson
> wrote:
> > On Sat, 2011-02-12 at 16:04 +, James Neave wrote:
> >> On Tue, Feb 8, 2011 at 10:17 AM, James Neave wrote:
> >> > On Tue, Feb 8, 2011 at 9:59 AM, Kenni Lund wrote:
> >> >> 20
On Mon, Feb 14, 2011 at 5:48 PM, Alex Williamson
wrote:
> On Sat, 2011-02-12 at 16:04 +, James Neave wrote:
>> On Tue, Feb 8, 2011 at 10:17 AM, James Neave wrote:
>> > On Tue, Feb 8, 2011 at 9:59 AM, Kenni Lund wrote:
>> >> 2011/2/7 Daniel P. Berrange :
>> >>> On Sat, Feb 05, 2011 at 04:34:0
On Sat, 2011-02-12 at 16:04 +, James Neave wrote:
> On Tue, Feb 8, 2011 at 10:17 AM, James Neave wrote:
> > On Tue, Feb 8, 2011 at 9:59 AM, Kenni Lund wrote:
> >> 2011/2/7 Daniel P. Berrange :
> >>> On Sat, Feb 05, 2011 at 04:34:01PM +, James Neave wrote:
> Hi,
>
> I'm tryi
On Tue, Feb 8, 2011 at 10:17 AM, James Neave wrote:
> On Tue, Feb 8, 2011 at 9:59 AM, Kenni Lund wrote:
>> 2011/2/7 Daniel P. Berrange :
>>> On Sat, Feb 05, 2011 at 04:34:01PM +, James Neave wrote:
Hi,
I'm trying to pass a NOVA-T-500 TV Tuner card through to a gust VM.
I'm
On Tue, Feb 8, 2011 at 9:59 AM, Kenni Lund wrote:
> 2011/2/7 Daniel P. Berrange :
>> On Sat, Feb 05, 2011 at 04:34:01PM +, James Neave wrote:
>>> Hi,
>>>
>>> I'm trying to pass a NOVA-T-500 TV Tuner card through to a gust VM.
>>> I'm getting the error "The driver 'pci-stub' is occupying your d
2011/2/7 Daniel P. Berrange :
> On Sat, Feb 05, 2011 at 04:34:01PM +, James Neave wrote:
>> Hi,
>>
>> I'm trying to pass a NOVA-T-500 TV Tuner card through to a gust VM.
>> I'm getting the error "The driver 'pci-stub' is occupying your device
>> :08:06.2"
>
> This is a rather misleading err
On Mon, Feb 7, 2011 at 1:26 PM, Daniel P. Berrange wrote:
> On Sat, Feb 05, 2011 at 04:34:01PM +, James Neave wrote:
>> Hi,
>>
>> I'm trying to pass a NOVA-T-500 TV Tuner card through to a gust VM.
>> I'm getting the error "The driver 'pci-stub' is occupying your device
>> :08:06.2"
>
> Th
On Sat, Feb 05, 2011 at 04:34:01PM +, James Neave wrote:
> Hi,
>
> I'm trying to pass a NOVA-T-500 TV Tuner card through to a gust VM.
> I'm getting the error "The driver 'pci-stub' is occupying your device
> :08:06.2"
This is a rather misleading error message. It is *expected* that
pci-s
35 matches
Mail list logo
