Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Created attachment 821446[details]
logs of guest dmesg, lspci dump on host
Description of problem:
I started a rhel6.5 guest with BCM57810 VFs assigned. After booted up, suspended guest to memory. Network connectivity was lost when resumed back.
Version-Release number of selected component (if applicable):
2.6.32-430.el6.x86_64
qemu-kvm-0.12.1.2-2.415.el6.x86_64
How reproducible:
1/1
Steps to Reproduce:
1.
2.
3.
Actual results:
[bnx2x_vfpf_init:389(eth8)]INIT VF failed: 2. Breaking...
pm_op(): pci_pm_resume+0x0/0xc0 returns -11
PM: Device 0000:00:08.0 failed to resume: error -11
[bnx2x_vfpf_init:389(eth7)]INIT VF failed: 2. Breaking...
pm_op(): pci_pm_resume+0x0/0xc0 returns -11
PM: Device 0000:00:09.0 failed to resume: error -11
Restarting tasks ... done.
Expected results:
Additional info:
CLI:
/usr/libexec/qemu-kvm -M rhel6.5.0 -cpu host -enable-kvm -m 4096 -realtime mlock=off -smp 4,sockets=2,cores=2,threads=1 -nodefaults -monitor stdio -boot menu=on -rtc base=utc,clock=host,driftfix=slew -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0 -drive file=/home/rhel6.5.qcow2,if=none,id=drive-virtio-disk0,format=qcow2,cache=none,werror=stop,rerror=stop,aio=native -device virtio-blk-pci,scsi=off,bus=pci.0,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,id=hostnet0,vhost=on -device virtio-net-pci,netdev=hostnet0,id=net0,mac=46:1a:4a:42:48:25,bus=pci.0 -k en-us -vga cirrus -device intel-hda,id=sound0,bus=pci.0 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device virtio-balloon-pci,id=balloon0,bus=pci.0 -vnc :1 -device pci-assign,host=23:01.7,id=vf -device pci-assign,host=23:01.0,id=pf -serial unix:/opt/serial,server,nowait -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0
Comment 2RHEL Program Management
2013-11-11 09:36:07 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
S3/S4 support is tech-preview in RHEL6 and it'll be promoted to fully supported
at some point, but only in RHEL7.
Therefore we're closing all S3/S4 related bugs in RHEL6. New bugs will be
considered only if they're regressions or break some important use-case or
certification.
RHEL7 is being more extensively tested and effort from QE is underway in
certifying that this particular bug is not present there.
Please reopen with a justification if you believe this bug should not be
closed. We'll consider them on a case-by-case basis following a best effort
approach.
Thank you.
Created attachment 821446 [details] logs of guest dmesg, lspci dump on host Description of problem: I started a rhel6.5 guest with BCM57810 VFs assigned. After booted up, suspended guest to memory. Network connectivity was lost when resumed back. Version-Release number of selected component (if applicable): 2.6.32-430.el6.x86_64 qemu-kvm-0.12.1.2-2.415.el6.x86_64 How reproducible: 1/1 Steps to Reproduce: 1. 2. 3. Actual results: [bnx2x_vfpf_init:389(eth8)]INIT VF failed: 2. Breaking... pm_op(): pci_pm_resume+0x0/0xc0 returns -11 PM: Device 0000:00:08.0 failed to resume: error -11 [bnx2x_vfpf_init:389(eth7)]INIT VF failed: 2. Breaking... pm_op(): pci_pm_resume+0x0/0xc0 returns -11 PM: Device 0000:00:09.0 failed to resume: error -11 Restarting tasks ... done. Expected results: Additional info: CLI: /usr/libexec/qemu-kvm -M rhel6.5.0 -cpu host -enable-kvm -m 4096 -realtime mlock=off -smp 4,sockets=2,cores=2,threads=1 -nodefaults -monitor stdio -boot menu=on -rtc base=utc,clock=host,driftfix=slew -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0 -drive file=/home/rhel6.5.qcow2,if=none,id=drive-virtio-disk0,format=qcow2,cache=none,werror=stop,rerror=stop,aio=native -device virtio-blk-pci,scsi=off,bus=pci.0,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,id=hostnet0,vhost=on -device virtio-net-pci,netdev=hostnet0,id=net0,mac=46:1a:4a:42:48:25,bus=pci.0 -k en-us -vga cirrus -device intel-hda,id=sound0,bus=pci.0 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device virtio-balloon-pci,id=balloon0,bus=pci.0 -vnc :1 -device pci-assign,host=23:01.7,id=vf -device pci-assign,host=23:01.0,id=pf -serial unix:/opt/serial,server,nowait -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0