similar to: KVM VM crash under I/O load (e1000 and virtio)

Hmmm...any chance that you can ellaborate on what updates will be included with 5.1. Not sure if it will be of practical interest anymore (I have 4 new network cards...non-Intel..on the way) since I have spent far more time on this problem than I should have. But, from a curiousity perspective, I am curious. If I could resolve this problem and use the Intel cards, that would be ideal.

I have a machine running Centos 5, x86_64. It has an Intel NIC: # lspci 15:00.0 Ethernet controller: Intel Corporation 82572EI Gigabit Ethernet Controller (Fiber) (rev 06) The machine has two dualcore cpus. If I look at /proc/interrupts I get: CPU0 CPU1 CPU2 CPU3 0: 144873228 220741831 173615012 220733357 IO-APIC-edge timer 4: 269120 1203485

I get the following results when I try to load the 2.6.11.4 kernel with an Intel e1000 driver (the one that comes in the kernel source): 1) If I build it into the kernel, nothing shows up at all. 2) If I build it as a loadable module, I get errors on eth0 and eth1 that the MAC address is different than expected, and it ignores the controller. What's up with this? Thanks. mhr

[This email is either empty or too large to be displayed at this time]

I recently noticed that after starting xend ethtool no longer work for my e1000 card. In my 2.X box which is a P4, ethtool is working after xend start. Same version of e1000 on both boxes. The unstable box is a Tyan 2462 SMP, FC4 dom0 The 2.X box is Dell P330 UP, Centos 4.1 domO Until xend start ethtool is fine, in both setups I am using the e1000 as eth0. Regards, Ted

Anyone running 7.1 and using E1000 hardware that has the time, I would appreciate any testing you can do. This has an important fix for SuperMicro servers but any regression test of the code would be helpful. Backup the contents of /usr/src/sys/dev/e1000 and then overwrite with this tarball. Send feedback to me, Jack

Package: xen-hypervisor-3.2-1-amd64 Version: 3.2.1-2 Severity: normal Hi, Is the e1000 network card within domU no longer available? With model=e1000 a Xen domain refuses to start while with etch this was possible. There are some Windows guests on which I can not install gplpv, so with lenny they will just get 100mbit ethernet emulated. Cheers, Andreas -- System Information: Debian Release:

There appears to be an issue with installation over an HP switch. Upon bootup, the network driver resets twice which somehow never allows the client to ask and therefore receive it's MAC address. This follows the RH bug : https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=110036 Installation via a directly attached cable to the head node works fine. I have emailed the Beowulf list in

Hi, try to use virtio instead... Atte. Daniel Romero P. On Thu, May 10, 2018 at 3:53 PM, Ihar Hrachyshka <ihrachys@redhat.com> wrote: > Hi, > > In kubevirt, we discovered [1] that whenever e1000 is used for vNIC, > link on the interface becomes ready several seconds after 'ifup' is > executed, which for some buggy images like cirros may slow down boot > process

On 05/10/2018 02:53 PM, Ihar Hrachyshka wrote: > Hi, > > In kubevirt, we discovered [1] that whenever e1000 is used for vNIC, > link on the interface becomes ready several seconds after 'ifup' is > executed What is your definition of "becomes ready"? Are you looking at the output of "ip link show" in the guest? Or are you watching "brctl

On Thu, May 10, 2018 at 11:53:23AM -0700, Ihar Hrachyshka wrote: > Hi, > > In kubevirt, we discovered [1] that whenever e1000 is used for vNIC, > link on the interface becomes ready several seconds after 'ifup' is > executed, which for some buggy images like cirros may slow down boot > process for up to 1 minute [2]. If we switch from e1000 to virtio, the > link is

Hello! We tried to move Windows 2003 VM with e1000 driver from Centos 7 which runs qemu-kvm-0.12.1.2-2.491.el6_8.7.x86_64 to Centos 7 with qemu-kvm-ev-2.6.0-28.el7_3.6.1.x86_64 and we got problems- tcp sessions, namely smb connections, randomly drops. We didn't test previous qemu-rhev with this VM, so we don't know how it works in them. Could you tell me is this known problem? Any

30.03.2017 10:52, Dmitry Melekhov ?????: > Hello! > > We tried to move Windows 2003 VM with e1000 driver from Centos 7 which > runs qemu-kvm-0.12.1.2-2.491.el6_8.7.x86_64 > to Centos 7 with qemu-kvm-ev-2.6.0-28.el7_3.6.1.x86_64 and we got > problems- > tcp sessions, namely smb connections, randomly drops. > > We didn't test previous qemu-rhev with this VM, so we

On Fri, Jan 17, 2020 at 3:16 PM david <david at daku.org> wrote: > > Folks > > I know that support for the network adaptors supported by the 'e1000' > driver have been removed from the base distribution. However, I have > exactly that controller (Broadcom Gigabit Ethernet PCI, not > PCIe). Is there a way for me to add support for that on Centos > 8.1?

At 03:27 PM 1/17/2020, Akemi Yagi wrote: >On Fri, Jan 17, 2020 at 3:16 PM david <david at daku.org> wrote: > > > > Folks > > > > I know that support for the network adaptors supported by the 'e1000' > > driver have been removed from the base distribution. However, I have > > exactly that controller (Broadcom Gigabit Ethernet PCI, not > >

16.01.2013 18:50, Xen.org security team пишет: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Xen Security Advisory CVE-2012-6075 / XSA-41 > qemu (e1000 device driver): Buffer overflow when processing large packets > > SUMMARY AND SOURCES OF INFORMATION > ================================== > > An issue in qemu has been disclosed which we believe affects

Hi, I've been experiencing occassional network time-outs with the Intel Gigabit nic's (e1000) in Poweredge systems. I'm not sure if it's a hard or software problem but it occurs on different systems with Centos 4.2 and 4.3 and was wondering if there' s a workaround available like compiling an updated e1000 module or something. kind regards, Geert -------------- next part

Hello, I install Centos'es from PXE, with vmlinuz and initrd provided by images/pxeboot from the first CD of centos 3.4. The server is a PowerEdge 1850 with two integrated e1000 nic interfaces. So kernel is booting, then it comes to the screen which ask for one nic to do a dhcp query. I choose eth0, dhcp server reply well and then i get an ip address, dns'es, etc. And nothing else

Folks I know that support for the network adaptors supported by the 'e1000' driver have been removed from the base distribution. However, I have exactly that controller (Broadcom Gigabit Ethernet PCI, not PCIe). Is there a way for me to add support for that on Centos 8.1? Perhaps a driver in an RPM package? Thanks David

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