On 20/10/2016 06:21, A223 A223 wrote:
Okay, I've enabled intremap=no_x2apic_optout on the host kernel and
didn't see much of a change in performance.
I feel I should mention that the qemu process on the host consumes
about 8-30% CPU (as shown in top) when the guest (Windows 10) task
manager
Okay, I've enabled intremap=no_x2apic_optout on the host kernel and
didn't see much of a change in performance.
I feel I should mention that the qemu process on the host consumes
about 8-30% CPU (as shown in top) when the guest (Windows 10) task
manager shows <1.0% cpu utilization. More often than
On Wednesday, October 19, 2016, A223 A223 > wrote:
> On Mon, Oct 17, 2016 at 10:24 PM, Alex Williamson
> wrote:
> > I picked up a card based on the same Fresco FL1100 (rev 10) chip, I
> > don't
On Mon, Oct 17, 2016 at 10:24 PM, Alex Williamson
wrote:
> I picked up a card based on the same Fresco FL1100 (rev 10) chip, I
> don't think it needs the no-bus-reset quirk above, resets seem to work
> fine for me. In fact the card works as expected with the previous
On Fri, 14 Oct 2016 10:56:44 -0600
Alex Williamson wrote:
> On Fri, 14 Oct 2016 10:47:42 -0600
> Alex Williamson wrote:
>
> > On Mon, 10 Oct 2016 20:05:02 -0700
> > A223 A223 wrote:
> >
> > > I just tried testing
On Fri, 14 Oct 2016 10:47:42 -0600
Alex Williamson wrote:
> On Mon, 10 Oct 2016 20:05:02 -0700
> A223 A223 wrote:
>
> > I just tried testing the patch.
> >
> > Initially, it seemed to work fine (log messages below).
> > However, I am getting
On Mon, 10 Oct 2016 20:05:02 -0700
A223 A223 wrote:
> I just tried testing the patch.
>
> Initially, it seemed to work fine (log messages below).
> However, I am getting hard lockup of the host machine shortly after
> the vfio_region_setup related log lines print out to the
I just tried testing the patch.
Initially, it seemed to work fine (log messages below).
However, I am getting hard lockup of the host machine shortly after
the vfio_region_setup related log lines print out to the screen. I
would say that rougly 3 of the 9 VM startups resulted in a hard lock
like
On Thu, Oct 6, 2016 at 9:29 PM, Alex Williamson
wrote:
> On Thu, 6 Oct 2016 21:07:06 -0700
> A223 A223 wrote:
>
>> On Thu, Oct 6, 2016 at 8:30 PM, A223 A223 wrote:
>> > On Thu, Oct 6, 2016 at 9:46 AM, Alex Williamson
>> >
On Thu, 6 Oct 2016 21:07:06 -0700
A223 A223 wrote:
> On Thu, Oct 6, 2016 at 8:30 PM, A223 A223 wrote:
> > On Thu, Oct 6, 2016 at 9:46 AM, Alex Williamson
> > wrote:
> >> On Wed, 5 Oct 2016 20:30:34 -0700
> >> A223 A223
On Wed, 5 Oct 2016 20:30:34 -0700
A223 A223 wrote:
> On Wed, Oct 5, 2016 at 9:33 AM, Alex Williamson
> wrote:
> > On Wed, 5 Oct 2016 02:13:21 -0700
> > A223 A223 wrote:
> >> How can I go about tracking down the root cause of
On Wed, Oct 5, 2016 at 8:30 PM, A223 A223 wrote:
> On Wed, Oct 5, 2016 at 9:33 AM, Alex Williamson
> wrote:
>> On Wed, 5 Oct 2016 02:13:21 -0700
>> A223 A223 wrote:
>>> How can I go about tracking down the root cause of this
On Wed, Oct 5, 2016 at 9:33 AM, Alex Williamson
wrote:
> On Wed, 5 Oct 2016 02:13:21 -0700
> A223 A223 wrote:
>> How can I go about tracking down the root cause of this error?
>
> This often means that the device resources are in use by another,
>
Hello,
When attempting PCI passthrough of a USB controller using the
following parameter to qemu:
-device vfio-pci,host=05:00.0,bus=root.1,addr=00.5
I receive the following error:
qemu-system-x86_64: -device
vfio-pci,host=05:00.0,bus=root.1,addr=00.5: Failed to mmap
:05:00.0 BAR 2.
14 matches
Mail list logo