Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA
PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=2 PME-
Kernel driver in use: vfio-pci
Thanks,
kind regards,
Andreas Hartmann
--
To unsubscribe from this list: send the line unsubscribe kvm
Alex Williamson wrote:
On Wed, 2013-06-26 at 17:14 +0200, Andreas Hartmann wrote:
Bjorn Helgaas wrote:
[fix Joerg's email address]
On Tue, Jun 25, 2013 at 10:15 PM, Bjorn Helgaas bhelg...@google.com wrote:
On Wed, Jul 11, 2012 at 11:18 PM, Alex Williamson
alex.william...@redhat.com wrote
-root.php?group=gmane.linux.kernel.pciarticle=16422
I think, Joerg wrote clearly that there is no problem any more to apply
this patch. I run it since a long time meanwhile without any problem.
Please, why aren't these patches applied?
Thanks,
kind regards,
Andreas Hartmann
--
To unsubscribe from
,
Andreas Hartmann
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Alex Williamson wrote:
On Thu, 2012-10-04 at 17:13 +0200, Andreas Hartmann wrote:
Hello Alex,
I just tested vfio as part of linux 3.6 and detected, that it
doesn't work because of the following missing patch:
http://news.gmane.org/find-root.php?group=gmane.linux.kernel.pciarticle=16422
-g323cf9f.tar.gz). I didn't
encounter any problem so far.
If you like, I could compile a more actual version, too (if there have
been any changes).
To see more about my use case:
http://permalink.gmane.org/gmane.linux.drivers.rt2x00.user/1051
You may add a Tested-by Andreas Hartmann andihartm
Alex Williamson schrieb:
On Mon, 2012-08-13 at 17:48 +0200, Andreas Hartmann wrote:
Alex Williamson wrote:
On Mon, 2012-08-13 at 08:27 -0500, Anthony Liguori wrote:
Alex Williamson alex.william...@redhat.com writes:
VFIO kernel support was just merged into Linux, so I'd like to
formally
Alex Williamson wrote:
On Mon, 2012-08-13 at 18:36 +0200, Andreas Hartmann wrote:
[...]
If I'm using your qemu instead of qemu from kvm-0.15 (opensuse package),
this error comes up when passing through a PCIe device, which works
absolutely fine with kvm 0.15. I would have expected, that your
Hello,
I managed to run this PCI (not PCIe(!)) device
06:07.0 Network controller [0280]: Ralink corp. RT2800 802.11n PCI [1814:0601]
Subsystem: Linksys Device [1737:0067]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Avi Kivity wrote:
On 07/25/2012 10:53 PM, Alex Williamson wrote:
On Wed, 2012-07-25 at 22:30 +0300, Avi Kivity wrote:
On 07/25/2012 08:03 PM, Alex Williamson wrote:
This adds PCI based device assignment to Qemu using the Linux VFIO
userspace driver interface. After setting up VFIO device
Avi Kivity schrieb:
On 07/26/2012 12:28 PM, Andreas Hartmann wrote:
Avi Kivity wrote:
On 07/25/2012 10:53 PM, Alex Williamson wrote:
On Wed, 2012-07-25 at 22:30 +0300, Avi Kivity wrote:
On 07/25/2012 08:03 PM, Alex Williamson wrote:
This adds PCI based device assignment to Qemu using
Alex Williamson wrote:
[I removed qemu-devel because I'm not registered there]
On Thu, 2012-07-26 at 19:40 +0300, Avi Kivity wrote:
On 07/26/2012 07:33 PM, Alex Williamson wrote:
In the common case, on x86 (but I'm repeating myself), the iommu group
includes just one device, yes? Could we
that they support a
subset of ACS.
Signed-off-by: Alex Williamson alex.william...@redhat.com
Tested-by: Andreas Hartmann andihartm...@01019freenet.de
Cc: Joerg Roedel joerg.roe...@amd.com
---
Two things about this patch make me a little nervous. The
first is that I'd really like to have
Hello Joerg,
Joerg Roedel wrote:
On Tue, Jun 05, 2012 at 08:27:05AM -0600, Alex Williamson wrote:
Joerg, the question is whether the multifunction device above allows
peer-to-peer between functions that could bypass the iommu. If not, we
can make it the first entry in device specific acs
Hello Joerg,
Joerg Roedel wrote:
Hi Andreas,
On Wed, Jul 11, 2012 at 04:26:30PM +0200, Andreas Hartmann wrote:
May I please ask, if you meanwhile could get any information about
potential peer-to-peer communication between the functions of the
following multifunction device:
Good news
Hello Joerg,
Joerg Roedel wrote:
On Tue, Jun 05, 2012 at 08:27:05AM -0600, Alex Williamson wrote:
Joerg, the question is whether the multifunction device above allows
peer-to-peer between functions that could bypass the iommu. If not, we
can make it the first entry in device specific acs
Alex Williamson wrote:
On Sat, 2012-06-09 at 18:25 +0200, Andreas Hartmann wrote:
Alex Williamson wrote:
On Sat, 2012-06-09 at 11:28 +0200, Andreas Hartmann wrote:
[...]
What's the risk of this patch? Machine crash? Data loss for an active
file in an application? Complete filesystem damage
Andreas Hartmann wrote:
Alex Williamson wrote:
On Sat, 2012-06-09 at 18:25 +0200, Andreas Hartmann wrote:
Alex Williamson wrote:
On Sat, 2012-06-09 at 11:28 +0200, Andreas Hartmann wrote:
[...]
What's the risk of this patch? Machine crash? Data loss for an active
file in an application
Alex Williamson wrote:
On Fri, 2012-06-08 at 18:16 +0200, Andreas Hartmann wrote:
[...]
Besides the problem with AMD IOMMU, which requires to unbind a whole
group of devices in some cases (PCI passthrough - not PCIe), it's really
cool! And it's usable now!
If you're feeling adventurous
On Fri, 08 Jun 2012 11:35:07 -0600
Alex Williamson alex.william...@redhat.com wrote:
On Fri, 2012-06-08 at 18:58 +0200, Andreas Hartmann wrote:
Hello Alex,
You can probably say, what this message on host side means:
kernel: [ 3902.124109] vfio_dma_do_map: RLIMIT_MEMLOCK (65536
Andreas Hartmann wrote:
On Fri, 08 Jun 2012 11:35:07 -0600
Alex Williamson alex.william...@redhat.com wrote:
[...]
I'm definitely curious if there's anything cumulative about the locked
memory problem above. Thanks,
Ok, I managed to get it reproducible. I'll describe step by step, how
Alex Williamson wrote:
On Sat, 2012-06-09 at 15:42 +0200, Andreas Hartmann wrote:
On Fri, 08 Jun 2012 11:35:07 -0600
Alex Williamson alex.william...@redhat.com wrote:
On Fri, 2012-06-08 at 18:58 +0200, Andreas Hartmann wrote:
Hello Alex,
You can probably say, what this message on host side
Alex Williamson wrote:
On Sat, 2012-06-09 at 11:28 +0200, Andreas Hartmann wrote:
[...]
What's the risk of this patch? Machine crash? Data loss for an active
file in an application? Complete filesystem damage? The latter would be
worse.
What we're trying to prevent by testing whether
Andreas Hartmann wrote:
Alex Williamson wrote:
[...]
I just pushed a vfio-3.4 branch to my tree at
git://github.com/awilliam/linux-vfio.git. Please let me know what you
find with this.
Works fine :-) vfio and fglrx and PCIe passthrough.
I rebuild the vfio patch on base of your vfio-3.4
Hi Dominic,
Dominic Eschweiler wrote:
Am Freitag, den 08.06.2012, 08:16 -0600 schrieb Alex Williamson:
Yes, thanks Jan. This is exactly what VFIO does. VFIO provides
secure config space access, resource access, DMA mapping services, and
full interrupt support to userspace.
I know about
Hello Alex,
You can probably say, what this message on host side means:
kernel: [ 3902.124109] vfio_dma_do_map: RLIMIT_MEMLOCK (65536) exceeded
The WLAN card in the VM doesn't work any more. It came up after a few
times of restarting the VM (with unbinding / rebinding - procedures).
I'll see
Andreas Hartmann wrote:
Hello Alex,
You can probably say, what this message on host side means:
kernel: [ 3902.124109] vfio_dma_do_map: RLIMIT_MEMLOCK (65536) exceeded
The WLAN card in the VM doesn't work any more. It came up after a few
times of restarting the VM (with unbinding
Alex Williamson wrote:
On Fri, 2012-06-08 at 19:39 +0200, Andreas Hartmann wrote:
[...]
- What size should be used for ulimit -l?
It should be about the size of memory assigned to the guest.
Ok, I'm using 256MB, this means, I should try to set ulimit -l to 256MB.
Nevertheless, I'm wondering
Alex Williamson wrote:
On Fri, 2012-06-08 at 19:39 +0200, Andreas Hartmann wrote:
Andreas Hartmann wrote:
Hello Alex,
You can probably say, what this message on host side means:
kernel: [ 3902.124109] vfio_dma_do_map: RLIMIT_MEMLOCK (65536) exceeded
The WLAN card in the VM doesn't work
Alex Williamson wrote:
Passes pci_intx_mask_supported but continues to send interrupts as
discovered through VFIO-based device assignment.
http://www.spinics.net/lists/kvm/msg73738.html
Signed-off-by: Alex Williamson alex.william...@redhat.com
Tested-by: Andreas Hartmann andihartm
Hello Alex,
what about a module parameter to achieve this behaviour manually by
the user without recompiling? I fear, there are much more candidates
out there needing this feature.
Kind regards and thank you,
Andreas
Alex Williamson wrote:
Passes pci_intx_mask_supported but continues to send
Alex Williamson wrote:
On Thu, 2012-06-07 at 08:18 +0200, Andreas Hartmann wrote:
Hello Alex,
what about a module parameter to achieve this behaviour manually by
the user without recompiling? I fear, there are much more candidates
out there needing this feature.
Yeah, that's probably
Alex Williamson wrote:
On Thu, 2012-06-07 at 23:01 +0200, Andreas Hartmann wrote:
Alex Williamson wrote:
On Thu, 2012-06-07 at 08:18 +0200, Andreas Hartmann wrote:
Hello Alex,
what about a module parameter to achieve this behaviour manually by
the user without recompiling? I fear
Alex Williamson wrote:
On Thu, 2012-06-07 at 23:42 +0200, Andreas Hartmann wrote:
Alex Williamson wrote:
On Thu, 2012-06-07 at 23:01 +0200, Andreas Hartmann wrote:
[...]
May I have please another question?
Unfortunately I can't cleanly unmount filesystems during shutdown with
your
kernel
On Tue, 05 Jun 2012 18:55:42 +0200
Andreas Hartmann andihartm...@01019freenet.de 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
On Wed, 6 Jun 2012 10:12:27 +0200
Andreas Hartmann andihartm...@01019freenet.de wrote:
On Tue, 05 Jun 2012 18:55:42 +0200
Andreas Hartmann andihartm...@01019freenet.de wrote:
Alex Williamson wrote:
[...]
Yep, I think the previous suggestion about reloading vfio_iommu_type1
Andreas Hartmann wrote:
On Wed, 6 Jun 2012 10:12:27 +0200
Andreas Hartmann andihartm...@01019freenet.de wrote:
On Tue, 05 Jun 2012 18:55:42 +0200
Andreas Hartmann andihartm...@01019freenet.de wrote:
Alex Williamson wrote:
[...]
Yep, I think the previous suggestion about reloading
On Wed, 06 Jun 2012 10:39:30 -0600
Alex Williamson alex.william...@redhat.com wrote:
On Wed, 2012-06-06 at 10:12 +0200, Andreas Hartmann wrote:
On Tue, 05 Jun 2012 18:55:42 +0200
Andreas Hartmann andihartm...@01019freenet.de wrote:
Alex Williamson wrote:
[...]
Yep, I think
Hello Alex,
thanks for your efforts!
Maybe, you already know that I'm suffering the same problem :-( with a
GA-990XA-UD3 (990X chipset).
On Mon, 04 Jun 2012 21:44:05 -0600
Alex Williamson alex.william...@redhat.com wrote:
[...]
I have a setup with an AMD 990FX system and a spare PVR-350 card
Andreas Hartmann wrote:
[...]
I tried to run qemu-system-x86_64 but got this error on startup:
qemu-system-x86_64: -device
vfio-pci,host=06:07.0,id=hostdev0,bus=pci.0,addr=0x5: vfio: failed to set
iommu for container: Operation not permitted
qemu-system-x86_64: -device
vfio-pci,host
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
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
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
Hello,
please, could somebody explain the difference in behaviour between
setting the boot option iommu=pt and not setting it?
I can see the following differences:
w/ iommu=pt:
[0.832946] AMD-Vi: Enabling IOMMU at :00:00.2 cap 0x40
[0.883983] AMD-Vi: Initialized for Passthrough
Hello!
I do have a question regarding the following VM (running on a linux
3.1.10 host with kvm 1.0). In the VM runs openSUSE 12.1 / 64bit.
The defined vnc interface is not used!
How much memory should this VM maximally use on the host (- memory
usage of the kvm-qemu process), as long as the
Hello kvm-list!
I sent the following text to Don with some additional detailed log
files. If somebody else need them too, I can provide them with pn.
Kind regards,
Andreas Hartmann
Andreas Hartmann schrieb:
Hello Don,
thank you for your reply!
I just want to describe in short the two
Hello Don!
Am Tue, 13 Dec 2011 01:21:41 +0100
schrieb Andreas Hartmann andihartm...@01019freenet.de:
Am Mon, 12 Dec 2011 13:36:36 -0500
schrieb Don Dutile ddut...@redhat.com:
On 12/12/2011 06:15 AM, Andreas Hartmann wrote:
Hello!
I've got a few questions to a problem, which
- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Thank you for your advice,
kind regards,
Andreas Hartmann
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord
Hello Don!
Am Tue, 13 Dec 2011 01:21:41 +0100
schrieb Andreas Hartmann andihartm...@01019freenet.de:
[...]
Ok. If I remove the intel card and put in instead a 32 bit PCIe card
like TP-Link TG-3468, I could assign each of these two cards to
different VMs.
Is this correct?
No - it isn't
Am Mon, 12 Dec 2011 13:36:36 -0500
schrieb Don Dutile ddut...@redhat.com:
On 12/12/2011 06:15 AM, Andreas Hartmann wrote:
Hello!
I've got a few questions to a problem, which already was analyzed here
sometime ago:
http://markmail.org/message/dspovwvzp3wtdrf6#query:+page:1
. Is there any way to get the devices into different VMs? (I can't put them to
another PCI slot as there are just 2 PCI slots on the board.)
2. Is there any fix to prevent the host crash - maybe in a newer version of kvm
or kernel?
Thank you very much for your help,
kind regards,
Andreas Hartmann
51 matches
Mail list logo
