similar to: Intel Quad NIC made visible in guest -> system crash

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, I got a problem when prepared to pass-thru 82576 ethernet card with SR-IOV support. The 82576 card is build-in on the board. When loading igb driver for the card, dmesg show some errors like: pci 0000:05:00.0: BAR 10: can''t allocate mem resource [0xfbf00000-0xfbefffff] . igb 0000:05:00.0: not enough MMIO resources for SR-IOV igb 0000:05:00.0: Failed to initialize

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)

Hi, I am working of Intel 82576 device to test the SRIOV functionality. I want to assign VFs to a VMs(domU) and verify the control and data path. I installed Xen-unstable with 2.6.30-rc3(dom0). But the SRIOV functionality isn''t working, because MSI is not supported. Please let me know, what version of Xen and dom0 supports above functionality? Is there any tool available to manage SRIOV

hi everybody a windows kvm guest would not start, process gets killed with: Out of memory: Kill process 21984 (qemu-kvm) score 44 or sacrifice child I really don't know where/what I might be missing, config seems fine, everything looks ok - I only am not sure, do I need to first stub a SR-IOV device like regular passthrough? I'm trying sr-iov, having one NIC left to the host and the

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 > >

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 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

Hello, I have experienced a dom0 crash where the system became unreachable via the network and the console was unresponsive. I would appreciate help interpretting the logs and any configuration change suggestions. It is a stock Debian Lenny dom0 running xen 3.2.1 with kernel 2.6.26-2-xen-amd64 and an AMD Athlon IIx4 with 4 GB of RAM. It is running 4 VMs. One VM has two PCI NICs being

Hi all, I've got a Centos 5.1 kickstart that I must continue to use. How can I update the kick start image so that it recognizes Intel gigabit 82576 nic? BTW, I compiled the driver I need and have this igb.ko file. How do I incorporate that into my initrd.img file that I see on the kickstart CD that is probably my kickstart boot OS. Thank you very much in advance. aurf -

Hello everyone, I'm having problem with SR-IOV transparent VLAN. My host is Fedora 22 and my guest is: pfSense 2.3. The NIC is Intel 82576. I'm using pfSense Packet Capture to check the packet and find that inbound packet still have the vlan tag. The outbound packet seem fine because the router can receive DHCP discover packet from the guest and then send DHCP offer and ARP request

Hi, I have been receiving messages on a new DomU''s kern.log. I''ve done a lot of googling, but haven''t came up with anything very useful, at least not in a Xen context. I was wondering if anyone had any suggestions about what could be wrong. From everything I have read, there should be a stack trace included, but I am not seeing one. Thanks in advance, Ian. on

Hello - It's been sooooo long since I've tried hacking the kickstart media to include an updated driver but I guess that time has come again for me at least, getting an updated "igb" driver into the CentOS 5.2 installation for a HP DL165G5p(I'm not ready yet for CentOS 5.3). Anyways, I had a pretty basic question, I added a bunch of entries into the pci.ids file that were

Hi Guys I''m trying to measure the traffic of domUs using vnstat without luck. My configuration: Debian 6.0.3 xen 4.0.1 vnstat 1.11 I''m using bonding with two network cards. auto bond0 iface bond0 inet manual slaves eth0 eth1 bond-mode active-backup bond-miimon 100 bond-updelay 200 bond-downdelay 200 bond-primary eth0 auto br0 iface br0 inet static

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

Hi, experts I found the tun0 is 10Mb/s and I installed vnstat to monitor the tinc vpn traffic statistic, but due to 10Mb/s, the vnstat couldn’t update it’s database due to low speed rate, so anyway to change the tun from10Mb/s to higher? [root at box1 ~]# vnstat -u Info: Traffic rate for "myvpn" higher than set maximum 10 Mbit (248->341, r735 t38), syncing. [root at box1 ~]#

Hi, The default settings for celtclient are:- Sampling rate 48000 Frame size 256 Packet size 43 According to my calculations this should give a bitrate of 64kbit/sec + a little extra for the 32bit time stamp and 4 null byte pseudo header. Using vnstat I was very surprised to see that it was reporting a bitrate usage of around 16kbyte/sec which is 128kbit/sec, double what I was expecting. I

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