All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Hartmann <andihartmann@01019freenet.de>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: Andreas Hartmann <andihartmann@01019freenet.de>,
	Joerg.Roedel@amd.com, Chris Sanders <sanders.chris@gmail.com>,
	kvm@vger.kernel.org
Subject: Re: AMD KVM Pci Passthrough reports device busy
Date: Wed, 06 Jun 2012 00:02:03 +0200	[thread overview]
Message-ID: <4FCE81DB.90802@01019freenet.de> (raw)
In-Reply-To: <1338930560.23475.232.camel@bling.home>

Alex Williamson wrote:
> On Tue, 2012-06-05 at 22:37 +0200, Andreas Hartmann wrote:
>> Alex Williamson wrote:
>>> On Tue, 2012-06-05 at 18:55 +0200, Andreas Hartmann wrote:
>>>> Alex Williamson wrote:
>>>> [...]
>>>>> Yep, I think the previous suggestion about reloading vfio_iommu_type1
>>>>> with allow_unsafe_interrupts=1 will solve it.
>>>>
>>>> Yes! Works now. Success!!!!!
>>>>
>>>> Works means: Device is seen in VM. I couldn't test it up to now, because
>>>> I don't have any driver in the VM for this device.
>>
>> Well, I've got another problem now with 3.4: I can't pass through my
>> PCIe device any more, which works fine without any problem with 3.1.10.
>> I'm getting the following error in 3.4:
>>
>> Failed to assign irq for "hostdev0": Input/output error
>> Perhaps you are assigning a device that shares an IRQ with another device?
>> qemu-kvm: -device pci-assign,host=04:00.0,id=hostdev0,configfd=19,bus=pci.0,addr=0x6: Device 'pci-assign' could not be initialized
>>
>> options kvm allow_unsafe_assigned_interrupts=1 is set.
>>
>> There are shared IRQ's - but that's the same in 3.1.10.
>>
>> This VM is started with libvirt (virsh) the old fashioned way with the
>> old qemu-kvm tool. Doesn't this work any more?
> 
> Does this help: https://lkml.org/lkml/2012/6/1/261

Yes - this fixed the problem!


Thanks,
Andreas

  reply	other threads:[~2012-06-05 22:04 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-04 21:11 AMD KVM Pci Passthrough reports device busy Chris Sanders
2012-06-05  3:44 ` Alex Williamson
2012-06-05 10:39   ` Andreas Hartmann
2012-06-05 14:27     ` Alex Williamson
2012-06-05 15:17       ` Andreas Hartmann
2012-06-05 15:48         ` Alex Williamson
2012-06-05 15:58         ` Andreas Hartmann
2012-06-05 16:19           ` Alex Williamson
2012-06-05 16:55             ` Andreas Hartmann
2012-06-05 18:43               ` Alex Williamson
2012-06-05 20:37                 ` Andreas Hartmann
2012-06-05 21:09                   ` Alex Williamson
2012-06-05 22:02                     ` Andreas Hartmann [this message]
2012-06-06  8:12               ` Andreas Hartmann
2012-06-06  8:46                 ` Andreas Hartmann
2012-06-06  9:35                   ` Andreas Hartmann
2012-06-06 16:39                 ` Alex Williamson
2012-06-06 19:17                   ` Andreas Hartmann
2012-06-06 10:11       ` Joerg Roedel
2012-06-25  5:55         ` Andreas Hartmann
2012-06-25 11:22           ` Joerg Roedel
2012-07-11 14:26         ` Andreas Hartmann
2012-07-11 16:58           ` Joerg Roedel
2012-07-11 19:32             ` Andreas Hartmann
2012-07-11 20:01               ` Alex Williamson
2012-06-06  1:32     ` sheng qiu
2012-06-06  3:07       ` Chris Sanders
2012-06-06  3:25         ` Alex Williamson
2012-06-06  3:31           ` Chris Sanders
2012-06-06  5:27             ` Alex Williamson

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=4FCE81DB.90802@01019freenet.de \
    --to=andihartmann@01019freenet.de \
    --cc=Joerg.Roedel@amd.com \
    --cc=alex.williamson@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=sanders.chris@gmail.com \
    /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.