similar to: unable to add pci network to existing vm

On 12/10/18 1:24 PM, daggs wrote: > Greetings, > > I'm trying to add a virtual nic to an existing and active vm and I'm getting this error: > error: internal error: No more available PCI slots > > the cmd I'm trying to run is: virsh -c qemu:///system attach-interface --domain router --type bridge --source virbr0 --model virtio --config --live > > the lspci

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

Hello all, I'm currently experiencing an issue with an NFS server I've built (a Dell R710 with a Dell PERC H800/LSI 2108 and four external disk trays). It's a backup target for Solaris 10, CentOS 5.5 and CentOS 6.2 servers that mount it's data volume via NFS. It has two 10gig NICs set up in a layer2+3 bond for one network, and two more 10gig NICs set up in the same way in another

http://www.intel.com/content/www/us/en/chipsets/5520-and-5500-chipset-ioh-specification-update.html Stepping B-3 has two errata (#47 and #53) related to Interrupt remapping, to which the workaround is for the BIOS to completely disable interrupt remapping. These errata are fixed in stepping C-2. Unfortunately this chipset is very common and many BIOSes are not disabling remapping. We can

How does one do this? For example: # lspci | grep USB 00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 02) 00:1a.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 02) 00:1a.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 02) 00:1a.7 USB Controller: Intel Corporation 82801I (ICH9

Greetings, I''m attempting to do gfx_passthru with the primary graphics adapter (03:00.0), passing it to a guest. I can unbind it from the host but when I fire up the guest OS my monitor loses signal from the graphics card and that''s that. The GFX card is dual DVI, I''ve tried both slots. Host is Linux 2.6.32.14-1.2.105.xendom0.fc12.x86_64, Guest is Windows 7. PC is an

# lspci -nn 00:00.0 Host bridge [0600]: Intel Corporation 5520 I/O Hub to ESI Port [8086:3406] (rev 22) 00:01.0 PCI bridge [0604]: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 1 [8086:3408] (rev 22) 00:03.0 PCI bridge [0604]: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 3 [8086:340a] (rev 22) 00:05.0 PCI bridge [0604]: Intel Corporation 5520/X58 I/O Hub PCI

On 7/30/2016 6:56 AM, Fawzy Ibrhim wrote: > # lspci -nn > 00:00.0 Host bridge [0600]: Intel Corporation 5520 I/O Hub to ESI Port [8086:3406] (rev 22) > 00:01.0 PCI bridge [0604]: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 1 [8086:3408] (rev 22) > 00:03.0 PCI bridge [0604]: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 3 [8086:340a] (rev 22) >

All, just having spotted the backport of Linux commit 03bbcb2e I notice a certain discrepancy with the Xen commit having the same purpose as well as with the actual specification updates: The Linux solution keys off of device IDs 3403 and 3406, as listed in the specification update, but this way fails to cover the X58 chipset, which has - under different numbers (62 and 69) - the same errata

John R Pierce wrote: > On 7/26/2016 10:20 AM, Fawzy Ibrhim wrote: >> I want to install Centos 7 latest build on NEC Server 5800/120b-2. >> >> The installation wizard fails to detect the storage connected to LSI >> SATA MegaRaid PCI. > > which megaraid card? they've made quite a lot. lspci will list the > card type... > > linux will only see storage

1: IOMMU: properly check whether interrupt remapping is enabled 2: AMD IOMMU: only disable when certain IVRS consistency checks fail 3: VT-d: deal with 5500/5520/X58 errata Patch 1 and 2 are version 2 of a previously submitted, then withdrawn patch following up after XSA-36. Patch 3 is version 3 of a patch previously sent by Malcolm and Andrew. Signed-off-by: Jan Beulich

Hello, I have been working sometime now on getting a HVM accepting a PCI card from the host. As was said in the VT-D wiki I bought an ASUS P5E VM DO motherboard (rel 0803) which has the VT-D option in the bios. I want to pass a Hauppauge PVR 500 card to a virtual machine running LinuxMCE. After first trying XEN 3.2.1 which did not enable the "VT-D virtualisation" bit in xm dmesg, i

Is there a way to enable iommu I have hp 380 g6 and I get this (XEN) [VT-D]Disabling IOMMU due to Intel 5500/5520/X58 Chipset errata #47, #53 (XEN) I/O virtualisation disabled _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users

we have just upgraded to xen4.0+kernel2.6.31.13. however, we fonud that disk offline in high disk IO(xen4.0+kernel2.6.31.13). but whitout xen4.0, we only start with kernel2.6.31.13, the disk offline didn''t happen. I think it is a bug. test case: 57 physical machine we start 5 vm(cpu:2, memory:1024) in a physical machine.at the same time we do decompression in dom0. tar xzvf *.tar.gz tar

Hi all, (My first time in seeking assistance via the CentOS mailing list ... Not sure if I should be submitting this as a possible kernel bug). I've successfully installed Cent OS 5.1 (kernel: 2.6.18-53.1.13.el5) on an Optiplex 755 (EM64T). However I'm not able to get a NVIDIA Gigabyte 8600GT (PCI-e) card to work with the system despite successfully installing the latest NVIDIA drivers

Sorry to duplicate my issues onto the list - I thought I had looked through this thread before and seen a different error, but apparently Adam and I are running into much the same thing. I'm seeing exactly the same "Failed to assign device to IOMMU" along with the "Device not owned by PCI Back End or pci-stub" in these scenarios. I have not gone back to previous versions,

Hello, I''m hoping someone may be able to push us in the right direction. I''m trying to get one of our products to work with the current branch of Xen (4.0/4.0.0) but I''m hitting a problem. We are currently using Xen 3.3.2 on a Sun Blade 600 chassis (with x6270 blades) this works great. But when we upgrade to Xen 4.0/4.0.1 we get the following message when

Hi Phil Here it is: [root at totorbex ~]# lspci -nn .00:00.0 Host bridge [0600]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series SoC Transaction Register [8086:2280] (rev 21) 00:02.0 VGA compatible controller [0300]: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 21) 00:10.0 SD Host controller

Hello all, this is my first post to the mailing list, so I hope this is the right way to ask a question. I''ve installed xen on my laptop (Asus N51Vf, specs here: http://www.asus.com/product.aspx?P_ID=0Tc42s23bOdbbvY5), as I''m currently at university and don''t have my proper desktop hardware to play with. The laptop supports IOMMU/Vt-d and has one PCI-e Geforce GT130M

Hello, In real life I use xen 3.3.1 successfully on servers Fujitsu-Siemens RX100. Now I to see how working xen-3.4-rc3 on the same server, but unfortunately is a problem with loading a module to handle the disk (mptsas) . I use debian lenny 5.0.1 and kernel version 2.6.26-2-xen-686. Someone managed to compile 3.4 xen kernel with this version? xen:~# lspci 00:00.0 Host bridge: Intel