similar to: intel quad gigabit nic and pci passthrough

On 01/25/2014 06:54 PM, Ivan Kabaivanov wrote: > Hi all > > I have a very weird case of pci passthrough. > > I have a machine with 7 network interfaces, all of them intel. Four of them are on one quad giga ethernet device. If I manually unbind the devices and allow qemu to use them, with intel IOMMU working, everything works like a charm. Here's how I do it manually: >

Hi, All the reviews for the AMD 890fx chipset reported that it supports IOMMU v1.2. But I cannot find any mention of that on AMD site. Does 890fx support IOMMU? Do 890fx motherboards with IOMMU exist? Does Xen support 890fx? Regards, Leonardo _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

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

Hi , I would like to assign a Network Interface card to Physical Slot X in the virtual machine, I have gone through the XML file definition[Now i have some idea on how to position the Network Interface in Logical PCI Slot.] I am NOT interested in using a PCI Pass-through from the Host. currently running Fedora 19 with libvirt 1.2.0 I would like to create an network interface card on

On Tue, Apr 11, 2017 at 08:09:01AM -0400, Pete Orrall wrote: > > And *why* random NIC names? Quick, you've got servers from 5 > > manufacturers, of different ages... what's the NIC going to be called? Do > > names like enp5s0 offer any convenience to *anyone* not a hardware > > engineer? > > As someone else had stated, it's not related to SystemD but >

Hello All, I have one CentOS 6 KVM virtualization server that I built around a year ago (best I can tell it was in October 2012) at which time I would have been installing 6.3 [0]. That particular install used the Consistent Network Device Naming [1] conventions (PCIe NICs are p1p1, p1p2). I started to build out a new KVM virt server (kickstarting a 6.4 install now as compared to 6.3 back then)

Hey dag, [...] I don't know if you saw it, we just created HDT's mailing list, if you want to join us, would be nice ;o) At least, I put the list on CC. > * The Chassis View has as Asset Tag something like > " Sa" > when highlighting I see it says " Safe" Fixed this morning by this commits :

I would really appreciate some pointers on what I am doing wrong here. I have a need to run multiple virtual guests which have each their own GPU and some USB controllers passed-through. I am able to run one of the guests like this (assuming vfio stuff has happened elsewhere), but I would prefer to use virsh: kvm -M q35 -m 8192 -cpu host,kvm=off \ -smp 4,sockets=1,cores=4,threads=1 \ -bios

Reposting from virt-tools mailing list: Hi! I'm facing a problem that could be triggered by some lacking of support from libvirt on Open vSwitch (or could be my mistake). I have interests in researching on virtual networks and SDN. To keep things simple, I've decided to use libvirt/virt-tools to manage VM's since my focus is on the network, instead of using a full feature system

On 7/28/2016 3:41 PM, Fawzy Ibrahim wrote: > LSI SATA MEGARAID 95Q9 afaik, the megaraid cards are mostly all SAS, which support SATA drives, except very old ones were SCSI. Ok, I do see they had a series of MegaRAID SATA 150-xx and 300-xx cards, these were 64 bit PCI or PCI-X cards. 95Q9 does not appear to be a valid card number, 9240, 9260, 9280 are some pci-express SAS MegaRaid

Quoting Laine Stump (laine@laine.org): > On 08/12/2015 02:34 PM, Alex Holst wrote: > > I would really appreciate some pointers on what I am doing wrong here. > > > > I have a need to run multiple virtual guests which have each their own GPU and > > some USB controllers passed-through. I am able to run one of the guests like > > this (assuming vfio stuff has

Hello, I´m trying to map one network interface of a Dual-Port e1000 Server Adapter to a DomU (firewall). In Dom0 the adaper is seen with lspci as: 06:00.0 Ethernet controller: Intel Corporation 631xESB/632xESB DPT LAN Controller Copper (rev 01) 06:00.1 Ethernet controller: Intel Corporation 631xESB/632xESB DPT LAN Controller Copper (rev 01) My goal is to map only 06:00.1 to DomU so I used this

Hi all, I were upgrading my system recently. But I met some difficult problems, the biggest one is described in http://permalink.gmane.org/gmane.comp.emulators.xen.user/66971, unfortunately I got no answer yet. My original environment is xen3.4.2(64bit) + dom0 kernel 2.6.18-xen, and 4 domus with kernel 2.6.18-xen, after first upgrade stage, I have Xen4.1.0(64bit)+dom0 kernel 2.6.32.39, and 4 domu

Hi all, I were upgrading my system recently. But I met some difficult problems, the biggest one is described in http://permalink.gmane.org/gmane.comp.emulators.xen.user/66971, unfortunately I got no answer yet. My original environment is xen3.4.2(64bit) + dom0 kernel 2.6.18-xen, and 4 domus with kernel 2.6.18-xen, after first upgrade stage, I have Xen4.1.0(64bit)+dom0 kernel 2.6.32.39, and 4 domu

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

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

Hello, I''m getting many "Error getting mfn" on a xen4.1.3 with dom0 3.4.11 x86_32. I thought it could be related to xen/mmu: Release just the MFN list, not MFN list and part of pagetables. http://git.kernel.org/?p=linux/kernel/git/konrad/xen.git;a=commit;h=785f62314984ea3af9dd830b020289ba2509ae69 (XEN) Freed 212kB init memory. (XEN) mm.c:908:d0 Error getting mfn 2009b (pfn

On Sun, Mar 9, 2014 at 10:51 AM, Marcin Slusarz <marcin.slusarz at gmail.com> wrote: > [ 326.168487] ====================================================== > [ 326.168491] [ INFO: possible circular locking dependency detected ] > [ 326.168496] 3.13.6 #1270 Not tainted > [ 326.168500] ------------------------------------------------------- > [ 326.168504] ldconfig/22297 is

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