similar to: NIC PCI-Passthrough problems (PV domU driver crashes)

Hi, I'm on a Dell VEP 1405 running Debian 9.11 and I'm running a few tests with various interfaces given in PCI passthrough to a qemu/KVM Virtual Machine also running Debian 9.11. I noticed that only one of the four I350 network controllers can be used in PCI passthrough. The available interfaces are: *# dpdk-devbind.py --status Network devices using kernel driver

Hello, I''m using Gentoo Linux amd64 with the 2.6.34-xen-r4 kernel from portage. I''ve been successfully using Xen 4.0 for almost a year, but now it seems that with the dawn of Xen 4.1, the package maintainers have forces unstable users to upgrade from 4.0 to 4.1 Looking forward to try the new xl interface, I installed it, but there seem to be a few problems with xen-4.1 First

Hello, I''m using Gentoo Linux amd64 with the 2.6.34-xen-r4 kernel from portage. I''ve been successfully using Xen 4.0 for almost a year, but now it seems that with the dawn of Xen 4.1, the package maintainers have forces unstable users to upgrade from 4.0 to 4.1 Looking forward to try the new xl interface, I installed it, but there seem to be a few problems with xen-4.1 First

On 01/30/2017 04:17 PM, Adi Pircalabu wrote: > On 28/01/17 05:21, Kevin Stange wrote: >> On 01/27/2017 06:08 AM, Karel Hendrych wrote: >>> Have you tried to eliminate all power management features all over? >> >> I've been trying to find and disable all power management features but >> having relatively little luck with that solving the problems. Stabbing

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-5.4 Severity: important When using the the intel igb driver from the 3.2.0-0.bpo.4-amd64 kernel and debian squeeze hypervisor with a Intel 82576 quad port nic the first nic fails to get an IRQ mapping: relevant lines from dmesg ----8<---- [ 24.264857] Intel(R) Gigabit Ethernet Network Driver - version 3.2.10-k [ 24.264929] Copyright (c)

I''m using Xen 4.01 and jeremy''s pvops kernel, the kernel version is 2.6.32.18. At first I want to test the performance of pci passthrough when it comes to the network card 82571EB I''m using the Jeremy''s kernel 2.6.32.18 as DomU kernel too. And I found if the interface is not connected, I mean the network card receives no packet, ( the network card

I''m using Xen 4.01 and jeremy''s pvops kernel, the kernel version is 2.6.32.18. At first I want to test the performance of pci passthrough when it comes to the network card 82571EB I''m using the Jeremy''s kernel 2.6.32.18 as DomU kernel too. And I found if the interface is not connected, I mean the network card receives no packet, ( the network card

I have three different types of CentOS 6 Xen 4.4 based hypervisors (by hardware) that are experiencing stability issues which I haven't been able to track down. All three types seem to be having issues with NIC and/or PCIe. In most cases, the issues are unrecoverable and require a hard boot to resolve. All have Intel NICs. Often the systems will remain stable for days or weeks, then

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

On Wed, Jan 27, 2016 at 7:30 PM, Konrad Rzeszutek Wilk < konrad.wilk at oracle.com> wrote: > On Sat, Jan 23, 2016 at 05:12:04PM +0100, Tommi Airikka wrote: > > 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

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

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

Hi! we have two Intel Quad Nic 82576, PCI ID 8086:10E8 and use the igb driver 1.3.19.3 on Debian 5.0.1. I used the pciback.hide XEN kernel parameter and made on of the NIC''s interfaces available in a DomU. Now, when I am starting the VM, the system crashes (log attached) I also tried to boot with the irqpoll option - the Interrupt Disabled message still appears when I try to start the

Package: xen-hypervisor-4.4-amd64 Version: 4.4.1-9 On a fresh installation of Debian Jessie, when I try to start a domU, it try to access to a dom0 LVM Volume Group : [...] (I put all the boot at the end) Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... Begin: Assembling all MD

Just out of annoyance more than curiosity, but ever since I started using Xen 4.2-unstable rev-25467, every time I try to run "sudo xl create <domu_config_file>", or "sudo xl reboot", or "sudo xl destroy", it always gives me this message: "*xend is running, which prevents xl from working correctly. If you still want to force the execution of xl please

I''ve migrated my Dom0 host to Xen 4.2.0 + xl toolstack. With ''xm'' toolstack, configs in /etc/xen/auto are autostarted, assuming xend/xendomains services are started. IIUC, when using xl toolstack, those services are not to be started; and, afaict, the installation process for 4.2 has them disabled by default. Now, the configs in /etc/xen/auto are simply ignored. I

On Mon, Oct 17, 2011 at 05:36:27PM +0200, Dario Faggioli wrote: > Hi everyone, > > I''m trying to setup PCI-passthrough for a network card on a testbox. > With HVM, everything seems to work, while if I try with a pv-guest the > domain crashes! > > Here''s the thing: > -- > # xl pci-list-assignable-devices > 0000:07:00.0 > 0000:07:00.1 > >

# HG changeset patch # User Olaf Hering <olaf@aepfle.de> # Date 1338572607 -7200 # Node ID 3da83ff08d6b6431c104a431d6617ccb5977643b # Parent fde8ad0252ee6ddb8d71dda869db3b20b3d9ca62 xl.cfg: document the cpuid= option Signed-off-by: Olaf Hering <olaf@aepfle.de> diff -r fde8ad0252ee -r 3da83ff08d6b docs/man/xl.cfg.pod.5 --- a/docs/man/xl.cfg.pod.5 +++ b/docs/man/xl.cfg.pod.5 @@ -969,9

Hi, I have a system based on a Supermicro X8DTH-i motherboard and a Xeon E5506 CPU. It was previously running Debian lenny with xen-hypervisor-3.2-1-amd64 (3.2.1-2) / linux-image-2.6.26-2-xen-amd64 (2.6.26-29) without incident. I upgraded it to Debian squeeze, with xen-hypervisor-4.0-amd64 (4.0.1-4) / linux-image-2.6.32-5-xen-amd64 (2.6.32-45) and now it does not complete a boot of the dom0

Hey, I just started noticing it today - with qemu-xen (tip is commit b97307ecaad98360f41ea36cd9674ef810c4f8cf xen_disk: mark ioreq as mapped before unmapping in error case) when I try to pass in a PCI device at bootup it blows up with: char device redirected to /dev/pts/2 (label serial0) qemu: hardware error: xen: failed to populate ram at 40050000 CPU #0: EAX=00000000 EBX=00000000