RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1378140 - e1000 emulated device isn't working with IR remap enabled
Summary: e1000 emulated device isn't working with IR remap enabled
Keywords:
Status: CLOSED DUPLICATE of bug 1369641
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qemu-kvm-rhev
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Virtualization Maintenance
QA Contact: weliao
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-21 15:04 UTC by Igor Mammedov
Modified: 2016-09-22 07:42 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-22 07:42:48 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Igor Mammedov 2016-09-21 15:04:34 UTC 
Description of problem:

When guest is booted it prints following messages some time after boot:

[   18.287349] WARNING: at net/sched/sch_generic.c:297 dev_watchdog+0x276/0x280()
[   18.287866] NETDEV WATCHDOG: enp0s2 (e1000): transmit queue 0 timed out
[   18.288333] Modules linked in: ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 ipt_REJECT nf_reject_ipv4 xt_conntrack ebtable_nat ebtable_broute bridge stp llc ebtable_filter ebtables ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_security ip6table_raw ip6table_filter ip6_tables iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_security iptable_raw iptable_filter iTCO_wdt iTCO_vendor_support ppdev sg parport_pc parport lpc_ich pcspkr i2c_i801 ip_tables ext4 mbcache jbd2 sd_mod crc_t10dif crct10dif_generic sr_mod crct10dif_common cdrom bochs_drm ahci libahci drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops ttm libata serio_raw drm e1000 i2c_core
[   18.293560] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.10.0-506.el7.x86_64 #1
[   18.294058] Hardware name: Red Hat KVM, BIOS 1.9.1-4.el7 04/01/2014
[   18.294488]  ffff880079a03d88 4f221f4c06a3d02a ffff880079a03d40 ffffffff81685a8c
[   18.295045]  ffff880079a03d78 ffffffff810857a0 0000000000000000 ffff8800768aa000
[   18.295600]  ffff880036c1fe80 0000000000000001 0000000000000000 ffff880079a03de0
[   18.296153] Call Trace:
[   18.296335]  <IRQ>  [<ffffffff81685a8c>] dump_stack+0x19/0x1b
[   18.296807]  [<ffffffff810857a0>] warn_slowpath_common+0x70/0xb0
[   18.297228]  [<ffffffff8108583c>] warn_slowpath_fmt+0x5c/0x80
[   18.297645]  [<ffffffff81595d06>] dev_watchdog+0x276/0x280
[   18.298031]  [<ffffffff81595a90>] ? dev_graft_qdisc+0x80/0x80
[   18.298456]  [<ffffffff810958f6>] call_timer_fn+0x36/0x110
[   18.298845]  [<ffffffff81595a90>] ? dev_graft_qdisc+0x80/0x80
[   18.299248]  [<ffffffff810985e7>] run_timer_softirq+0x237/0x340
[   18.299694]  [<ffffffff8108f07f>] __do_softirq+0xef/0x280
[   18.300072]  [<ffffffff81697b1c>] call_softirq+0x1c/0x30
[   18.300442]  [<ffffffff8102d365>] do_softirq+0x65/0xa0
[   18.300806]  [<ffffffff8108f415>] irq_exit+0x115/0x120
[   18.301165]  [<ffffffff81698795>] smp_apic_timer_interrupt+0x45/0x60
[   18.301608]  [<ffffffff81696cdd>] apic_timer_interrupt+0x6d/0x80
[   18.302021]  <EOI>  [<ffffffff81060eb6>] ? native_safe_halt+0x6/0x10
[   18.302487]  [<ffffffff8103482f>] default_idle+0x1f/0xc0
[   18.302890]  [<ffffffff81035176>] arch_cpu_idle+0x26/0x30
[   18.303268]  [<ffffffff810e7ba5>] cpu_startup_entry+0x245/0x290
[   18.303711]  [<ffffffff81673ed7>] rest_init+0x77/0x80
[   18.304081]  [<ffffffff81b0a05a>] start_kernel+0x42c/0x44d
[   18.304460]  [<ffffffff81b09a37>] ? repair_env_string+0x5c/0x5c
[   18.304873]  [<ffffffff81b09120>] ? early_idt_handlers+0x120/0x120
[   18.305299]  [<ffffffff81b095ee>] x86_64_start_reservations+0x2a/0x2c
[   18.305783]  [<ffffffff81b09742>] x86_64_start_kernel+0x152/0x175
[   18.306206] ---[ end trace d2d1b10673f13e29 ]---
[   18.306549] e1000 0000:00:02.0 enp0s2: Reset adapter

here is also output of 'ip addr' command:

[...]
2: enp0s2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000
    link/ether 52:54:00:12:34:56 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::5054:ff:fe12:3456/64 scope link 
       valid_lft forever preferred_lft forever


Version-Release number of selected component (if applicable):
qemu-kvm-rhev-2.6.0-26
host and guest kernel 3.10.0-506


How reproducible:
100%

Steps to Reproduce:
1.
 /usr/libexec/qemu-kvm --enable-kvm -m 2G rhel73.img -M q35 -smp 1,maxcpus=240   -device intel-iommu,intremap=on -machine kernel_irqchip=split
2. wait till guest boots and prints message or just check that NIC isn't working manually

Actual results:
network isn't operational

Expected results:
network is operational

Additional info:

the same issue with current upstream QEMU master
Comment 2 Chao Yang 2016-09-22 02:52:54 UTC 
Hi Igor, 

Would you please try https://bugzilla.redhat.com/show_bug.cgi?id=1369641#c2 ? Thanks!
Comment 3 Igor Mammedov 2016-09-22 07:42:48 UTC 

*** This bug has been marked as a duplicate of bug 1369641 ***
Note You need to log in before you can comment on or make changes to this bug.