Hide Forgot
Created attachment 491452 [details] screenshot Description of problem: The following message display and the guest stay on this stage for a long time after guest-rhel5 resume from S4. pls refer to screenshot. pnp: Failed to activate device 00:02. pnp: Failed to activate device 00:03. pnp: Failed to activate device 00:05. pnp: Failed to activate device 00:06. Version-Release number of selected component (if applicable): guest kernel: 2.6.18-255.el5 host kernel: 2.6.32-128.el6.x86_64 qemu-kvm-0.12.1.2-2.153.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1. boot guest with ide+rtl8139 by the following cmd-line 2. do s4 -- echo disk > /sys/power/state 3. start the guest again with the same cmd-line Actual results: The error message display and the guest stay on this stage for a long time, then it boot up. But it's network has problem, cannot 'ping' the other host. pnp: Failed to activate device 00:02. pnp: Failed to activate device 00:03. pnp: Failed to activate device 00:05. pnp: Failed to activate device 00:06. Expected results: no error message Additional info: cmd-line: /usr/libexec/qemu-kvm -drive file=/home/kvm_autotest_root/images/RHEL-Server-5.6-64-virtio.raw,index=0,if=none,id=drive-ide0-0-0,media=disk,cache=none,format=raw,aio=native -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -device rtl8139,netdev=idYE7II3,mac=9a:d4:58:7d:03:b4,id=ndev00idYE7II3,bus=pci.0,addr=0x3 -netdev tap,id=idYE7II3,ifname=t0-034719-x0nn,script=/etc/qemu-ifup-switch,downscript=no -m 512 -smp 2,cores=1,threads=1,sockets=1 -cpu cpu64-rhel6,+sse2,+x2apic -vnc :1 -rtc base=localtime,clock=host,driftfix=none -M rhel6.1.0 -boot order=cdn,once=c,menu=off -usbdevice tablet -enable-kvm -monitor stdio The guest's dmesg information after resume from s4 saved in attachment. Attached the serial information.
Created attachment 491453 [details] guest's dmesg
Created attachment 491455 [details] serial-vm-log
Since RHEL 6.2 External Beta has begun, and this bug remains unresolved, it has been rejected as it is not proposed as exception or blocker. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.
This issue is extremely old. If there is still a customer affected on the latest version of RHEL6, please reopen and provide specifics.