Displaying 4 results from an estimated 4 matches for "pt_msi_disable".
2013 Feb 26
4
passthroughed msix device
...PCI-MSI-edge
mpt2sas0-msix0
After change affinity to vcpu1, interrupt still happen on vcpu0. And
sometimes we got "/No irq handler for vector (irq -1)/" and panic.
qemu-dm.log shows error:
pt_msixctrl_reg_write: guest enabling MSI-X, disable MSI-INTx translation
pci_intx: intx=1
pt_msi_disable: Unmap msi with pirq 4f
pt_msix_update_one: Update msix entry 0 with pirq 4f gvec 59
pt_msixctrl_reg_write: guest enabling MSI-X, disable MSI-INTx translation
pci_intx: intx=1
pt_msi_disable: Unmap msi with pirq 4e
pt_msix_update_one: Update msix entry 0 with pirq 4e gvec 69
pci_msix_writel: Can...
2013 Feb 07
41
Patch series for IGD passthrough
This series contains all the fixes required to produce a working IGD
passthrough box. All the changes are previously seen in the dev list but
not yet accepted. Some of them are out-dated and need some reshape.
Detailed description can be found later in each patch.
. [PATCH 1/3] qemu-xen-trad/pt_msi_disable: do not clear all MSI flags
. [PATCH 2/3] qemu-xen-trad: Correctly expose PCH ISA bridge for IGD
. [PATCH 3/3] qemu-xen-trad: IGD passthrough: Expose vendor specific
Thanks,
Timothy
2012 Nov 13
6
Does xen-4.2.0 support VGA passthrough with the virtual machine created by xl command?
Hi, everyone!
I am working on xen-4.2.0 with spice remote connect. My host is Fedora 14
and guest is win7.
I have installed spice package and now I can connect to guest by spice
client.
For better graphics experience, I want to try the VGA passthrough.
With spice tool, I have to create a VM by xl command, and now I am
wondering if it supports VGA passghrouth?
If so, how should I test it ?
2012 Dec 03
21
Issue about domU missing interrupt
Hi developers,
I met some domU issues and the log suggests missing interrupt.
Details from here:
http://www.gossamer-threads.com/lists/xen/users/263938#263938
In summary, this is the suspicious log:
(XEN) vmsi.c:122:d32767 Unsupported delivery mode 3
I''ve checked the code in question and found that mode 3 is an ''reserved_1''
mode.
I want to trace down the source of this