similar to: [PATCH] qemu-xen: support PV on HVM MSIX remapping

Hi maintainer, Reprodue an bug on xen-unstable, it''s an irq affinity issue for passthroughed msix device to uek1 pvhvm(2.6.32 stable). I passthrough two mptsas devices(0000:0d:0.0, 0000:1f:0.0) to a pvhvm, irq affinity can''t be changed. Step to reproduce is as below: 1. xl -f pci-assignable-add 0000:0d:0.0; xl -f pci-assignable-add 0000:1f:0.0 2.xm cr -c vm.cfg

Hi All, When tried to pass through 2 mpt2sas HBA to hvm guest, hvmloader paused with below: MPT BIOS Fault 09h encountered at adapter PCI(00h,04h,00h) Press any key to continue... Checked related codes and mostly like it caused by rombios did not loaded MPT BIOS properly, and lead MPT BIOS failed to bootup. config-file of the guest as below: ---------------------------------- # cat vm.cfg

Accelerated msix entry is initialized to zero when msixtbl_pt_register is called. This doesn''t match the value from qemu side, although pirq may already be mapped and binded in qemu side. Kernel will get wrong value when reading msix info. Signed-off-by: Zhenzhong Duan <zhenzhong.duan@oracle.com> Tested-by: Yuval Shaia <yuval.shaia@oracle.com> --- tools/libxc/xc_domain.c

Several of these messages we coded using line continuation within a string literal. This is generally not recommended and also lead to odd sequences of many blanks in the middle of the messages. The message indicating a discarded write due to MSI-X already being enabled doesn''t need to be issued when a write doesn''t actually modify the current value. Adjust the surrounding logic

so... I've been tinkering with KVM again. my desktop is windows, the linux server is remote, so I have a ssh X tunnel running, and XMing running locally, and launch virt-manager. opens fine, shows the VM I created some time ago. I select that VM (which is running centos 6), and 'open', a window opens for a few seconds, then blam, virt-manager exits before I can click on

I'm using virt-manager 0.8.6 client side on Ubuntu 11.04. I can't get vnc over ssh to work to a kvm guest running on a Ubuntu 10.04 host. kvmhost:~> virsh vncdisplay testing :0 kvmhost:~> telnet 127.0.0.1 5900 Trying 127.0.0.1... Connected to 127.0.0.1. Escape character is '^]'. RFB 003.008 Client virt-manager debug: 2011-06-24 11:28:56,055 (console:923): Starting connect

Try giving the VM a Spice display, instead of VNC, see if that helps. Also, on Windows try Mobaxterm SSH client, it comes with X server built-in, perhaps it behaves less crappy. HTH Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro ----- Original Message ----- > From: "John R Pierce" <pierce at hogranch.com> > To: "CentOS mailing

Hi developer, i got a problem and need your help!(my english not very good) My KVM host in IDC, and there are some restrict in there lead to me connect to KVM host by port 22 or 16509 impossible. In generally If i want login my KVM host i must login in to a "stepping stones" first, then login to that KVM host.( Now assume that the KVM host ip is 1.1.1.1 and the "stepping

hi, I want to pass through "01:00.0",declared as pci=['01:00.0'] in cfg file. but found error log "pt_iomul_init: Error: pt_iomul_init can't open file /dev/xen/pci_iomul: No such file or directory: 0x1:0x0.0x0". in qemu-dm-example.hvm.log In fact, /dev/xen/pci_iomul does not exist. So where /dev/xen/pci_iomul implemented ? I have searched xen and linux code,

Add SR-IOV support for HVM guest. Signed-off-by: Yu Zhao <yu.zhao@intel.com> diff --git a/hw/pass-through.c b/hw/pass-through.c index 77ab759..da1a86b 100644 --- a/hw/pass-through.c +++ b/hw/pass-through.c @@ -47,6 +47,10 @@ struct dpci_infos { /* prototype */ static uint32_t pt_common_reg_init(struct pt_dev *ptdev, struct pt_reg_info_tbl *reg, uint32_t real_offset); +static

GK20A does not have dedicated RAM, thus having a RAM device for it does not make sense. Move the contiguous physical memory allocation to instmem. Signed-off-by: Alexandre Courbot <acourbot at nvidia.com> --- drm/nouveau/include/nvkm/subdev/instmem.h | 1 + drm/nouveau/nvkm/engine/device/gk104.c | 2 +- drm/nouveau/nvkm/subdev/fb/ramgk20a.c | 86 +-----------

This patch set adds basic supports for amd next generation iommu (IOMMUv2) hardware. IOMMUv2 supports various new features advertised by iommu extended feature register. It introduces guest level IO translation and supports state-of-the-art ATS/ATC devices with demand paging capability. Please refer to AMD IOMMU Architectural Specification [1] for more details. Thanks, Wei [1]

First, the Asterisk settings: ----- sip.conf ----- [general] port=5060 ; UDP Port to bind to (SIP standard port is 5060) bindaddr=0.0.0.0 ; IP address to bind to (0.0.0.0 binds to all) context=default ; Default context for incoming calls disallow=all ; First disallow all codecs; Set order allow=ulaw ; also known as g.711 PCMU; allow codecs in

Don't add an option for platforms to disable MSI-X in all devices. Paul Brook will find and fix all platforms that have broken MSI-X emulation. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- This patch on top of my msix series v6 is a bit tongue in cheek: it shows what can be done and Paul seems to think it's a good idea. So even though I don't necessarily agree,

Don't add an option for platforms to disable MSI-X in all devices. Paul Brook will find and fix all platforms that have broken MSI-X emulation. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- This patch on top of my msix series v6 is a bit tongue in cheek: it shows what can be done and Paul seems to think it's a good idea. So even though I don't necessarily agree,

On Fri, Dec 26, 2014 at 10:53:42AM +0800, Jason Wang wrote: > Hi all: > > This series try to share MSIX irq for each tx/rx queue pair. This is > done through: > > - introducing virtio pci channel which are group of virtqueues that > sharing a single MSIX irq (Patch 1) > - expose channel setting to virtio core api (Patch 2) > - try to use channel setting in virtio-net

On Sun, Jan 04, 2015 at 04:38:17PM +0800, Jason Wang wrote: > > On 12/28/2014 03:52 PM, Michael S. Tsirkin wrote: > > On Fri, Dec 26, 2014 at 10:53:42AM +0800, Jason Wang wrote: > >> Hi all: > >> > >> This series try to share MSIX irq for each tx/rx queue pair. This is > >> done through: > >> > >> - introducing virtio pci channel

Jason Wang <jasowang at redhat.com> writes: > Hi all: > > This series try to share MSIX irq for each tx/rx queue pair. This is > done through: > > - introducing virtio pci channel which are group of virtqueues that > sharing a single MSIX irq (Patch 1) > - expose channel setting to virtio core api (Patch 2) > - try to use channel setting in virtio-net (Patch 3)

On Fri, Dec 26, 2014 at 10:53:42AM +0800, Jason Wang wrote: > Hi all: > > This series try to share MSIX irq for each tx/rx queue pair. This is > done through: > > - introducing virtio pci channel which are group of virtqueues that > sharing a single MSIX irq (Patch 1) > - expose channel setting to virtio core api (Patch 2) > - try to use channel setting in virtio-net

On Sun, Jan 04, 2015 at 04:38:17PM +0800, Jason Wang wrote: > > On 12/28/2014 03:52 PM, Michael S. Tsirkin wrote: > > On Fri, Dec 26, 2014 at 10:53:42AM +0800, Jason Wang wrote: > >> Hi all: > >> > >> This series try to share MSIX irq for each tx/rx queue pair. This is > >> done through: > >> > >> - introducing virtio pci channel