similar to: Is: Xen 4.2 and using 'xl' to save/restore is buggy with PVHVM Linux guests (v3.10 and v3.11 and presumarily earlier as well). Works with Xen 4.3 and Xen 4.4. Was:Re: FAILURE 3.11.0-rc7upstream(x86_64) 3.11.0-rc7upstream(i386)\: 2013-08-26 (tst001)

Hello, While testing Fedora 16 Xen PVHVM guests I noticed the following problem: When starting F16 PVHVM guest I can see the vifX.0 and tapX.0 interfaces appear on dom0, but after the guest kernel (Linux 3.1.0) starts and loads PVHVM drivers the vif/tap interfaces disappear from dom0.. so the bridge in dom0 doesn''t have any vifs/taps connected to it anymore. Has anyone seen that

Hello. It is update of my previous message. I''ve checked that I can passthrough discrete graphic card, but when I try use in IGP (without discrete card in the slot) linux come to desktop without usage in inteldmr driver indeed. Dmesg show that I have some problem with ioremap. Is someone tried do pci/vga passthrough of integrated graphic or know way to solve that problem? Best regards.

Today is my day! This is with Xen 4.4 (pulled today) when I build a kernel in dom0 and have two guests launching at the same time. This is what I get: (XEN) Assertion ''l1e_get_pfn(MAPCACHE_L1ENT(hashent->idx)) == hashent->mfn'' failed at domain_page.c:203 and it blows up. Here is the full log: \ \/ /___ _ __ | || | | || | _ _ _ __ ___| |_ __ _| |__ | | ___

(copying xen-devel, full logs are at bugs.debian.org/748052, this is Debian Jessie, Xen 4.3.0 and Linux 3.13 Mike also reported that Debian Wheezy Xen 4.1.4 didn't work either, not clear which kernel that was with though, Wheezy's 3.2 or Jessie's 3.13) On Thu, 2014-05-15 at 10:11 -0700, Mike Egglestone wrote: > Here are some results with (now) the latest BIOS version 41. (was >

Hi, everyone! We google a lot, but can''t find how to config the pvscsi on our ubuntu13.04 PV on HVM.There are some links http://wiki.xen.org/wiki/Paravirtualized_SCSI http://wiki.xen.org/wiki/Xen_Configuration_File_Options And we use the config option above Configure PVSCSI devices vscsi = [ ''/dev/sdc, 0:0:0:0'' ] I pass sdc to the hvm, but in our pvhvm (ubuntu13.04)

Hey, It looks like one of the patches that went in Xen 4.1 blows up. This used to work over the weekend, so I can only surmise it is one the three patches. This is with a debug=y build (which has been working nicely for the last month or more). It looks like one of the patches that went in Xen 4.1 blows up. This used to work a day ago - that is c/s 23551 worked nicely. ----- Forwarded message

Package: xen-hypervisor-4.4-amd64 Version: 4.4.1-9+deb8u1 Severity: important I already posted this on the xen-devel-mailinglist but no one seems to have an answer. I'm posting it here because perhaps someone using Debian and Virtualization might have an idea about this? Since Debian 8 I observe that live migrating a PVM on XEN 4.4.1 (also 4.5.1) and Linux Kernel 4.1.0 (also 3.18) requires

Ian Campbell <ijc at hellion.org.uk> writes: #Please boot with loglvl=all on the hypervisor command line for this too. No problem Ian, Here are some results with (now) the latest BIOS version 41. (was version 35) This is a fresh new install of Debian "Testing" non production server. Just wanted to run some test domU's. Changing USB ports, no effect. I even tried a different

This issue I am encountering seems to only happen on multi-socket machines. It also does not help that the only multi-socket box I have is an Romley-EP (so two socket SandyBridge CPUs). The other SandyBridge boxes I''ve (one socket) are not showing this. Granted they are also a different model (42). The problem is that when I run ''perf top'' within an SMP PVHVM guest,

Hey I wanted to try my hand at doing some GPU passthrough so on my ASUS M5A97 which in the pass worked with an older BIOS (but said BIOS had issues after S3 suspend) - but with a BIOS the PCI passthrough does not work. That is due to:: (XEN) IVHD Error: Invalid IO-APIC 0xff (XEN) AMD-Vi: Error initialization

Package: xen-hypervisor-4.1-amd64 Version: 4.1.4-3+deb7u1 Severity: normal I tried GRUB_CMDLINE_XEN="dom0_mem=8192M": that delivers 6964868K total, then crashes when used=2837436K free=4127432K. By crash I mean the gnome screen was blown away, replaced by a black screen with white log lines. That seems to happen every time dom0 uses a large amount of memory. After setting

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

Hello, http://www.phoronix.com/scan.php?page=article&item=ubuntu_1110_xenkvm&num=1 Ubuntu 11.10 with Xen 4.1.1 and Linux 3.0. Xen seems to be doing very poorly on that benchmark. If someone has time to repeat that benchmark it would be good.. Comparing the results to those from Stefano from XenSummit 2011 NA there has be something wrong.. the results at XenSummit were pretty much the

Package: xen-hypervisor-4.1-amd64 Version: 4.1.4-3+deb7u1 Severity: normal Hello, I was running Xen for a few years and after a PSU failure I never got the system working stable again. I suspected damage to the board so I replaced everything in the system piece by piece but Xen enabled kernel always crashes even with only Dom0 running when moderate amount of IO happens on the box. kvm seems

Hello, More information and a patch for the bug. -- Pasi ----- Forwarded message from George Dunlap <George.Dunlap at eu.citrix.com> ----- From: George Dunlap <George.Dunlap at eu.citrix.com> To: Jan Beulich <JBeulich at novell.com> Cc: Sander Eikelenboom <linux at eikelenboom.it>, Jeremy Fitzhardinge <jeremy at goop.org>, Yunhong Jiang <yunhong.jiang at

@@ -491,16 +512,15 @@ int pirq_guest_bind(struct vcpu *v, int int rc = 0; cpumask_t cpumask = CPU_MASK_NONE; + WARN_ON(!spin_is_locked(&v->domain->evtchn_lock)); I find this WARN_ON() is triggered harmlessly when I assign device to HVM guest. The call trace is XEN_DOMCTL_bind_pt_irq -> pt_irq_create_bind_vtd() -> pirq_guest_bind(). Should we

Xen developers, After an upgrade of my Debian Jessie dom0 and domUs, my passthroughed NIC stopped working. This bug was probably introduced in Debian Jessie sometime between 2015-12-30 and 2016-01-08 as 2015-12-30 as 2015-12-30 was the last time I upgraded without any problems according to my dpkg.log. This bug has also been reported to Debian Bug (https://bugs.debian.org/810379), where I got

Source: xen Severity: normal Dear Maintainer, After an upgrade, my passthroughed NIC stopped working. I created a new jessie domU and tried to passthrough some PCI devices and found that both USB3 host controller and tg3 NIC generated these lines in domU dmesg: xen:events: Failed to obtain physical IRQ 31 xen:events: Failed to obtain physical IRQ 32 xen:events: Failed to obtain physical IRQ 33

Support PV on HVM MSIX remapping The technique is the same used with MSI: if the guest enables an MSIX passing 0 as vector number, then read the address and use it as pirq number for the following mapping request to Xen. Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com> diff --git a/hw/pt-msi.c b/hw/pt-msi.c index f0fb3e3..b01744e 100644 --- a/hw/pt-msi.c +++

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