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.
Hi Wei,
I can not reproduce this bug on the latest RHEL.7.2 version on both AMD and INTEL hosts.
1. qemu-kvm:
qemu-kvm-1.5.3-102.el7.x86_64
kernel-3.10.0-315.el7.x86_64
2. qemu-kvm-rhev:
qemu-kvm-rhev-2.3.0-22.el7.x86_64
kernel-3.10.0-315.el7.x86_64
Steps are same as comment 0.
Thanks.
(In reply to CongLi from comment #6)
> Hi Wei,
>
> I can not reproduce this bug on the latest RHEL.7.2 version on both AMD and
> INTEL hosts.
>
> 1. qemu-kvm:
> qemu-kvm-1.5.3-102.el7.x86_64
> kernel-3.10.0-315.el7.x86_64
>
> 2. qemu-kvm-rhev:
> qemu-kvm-rhev-2.3.0-22.el7.x86_64
> kernel-3.10.0-315.el7.x86_64
>
> Steps are same as comment 0.
>
>
> Thanks.
Thanks. With the results, I think we can close this BZ for now.
Created attachment 864416 [details] session log Description of problem: iometer: 'Get port error in SynchReceive' in win7 guest Version-Release number of selected component (if applicable): kernel-3.10.0-88.el7.x86_64 qemu-kvm-1.5.3-47.el7.x86_64 How reproducible: sometimes Steps to Reproduce: 1. Boot a win7.x86_64 guest with additional disk -drive id=drive_image1,if=none,cache=none,snapshot=off,aio=native,file=/home/staf-kvm-devel/autotest-devel/client/tests/virt/shared/data/images/win7-64-virtio.qcow2 \ -device virtio-blk-pci,id=image1,drive=drive_image1,bootindex=0,bus=pci.0,addr=04 \ -drive id=drive_disk1,if=none,cache=none,snapshot=off,aio=native,file=/home/staf-kvm-devel/autotest-devel/client/tests/virt/shared/data/images/storage.qcow2 \ -device virtio-blk-pci,id=disk1,drive=drive_disk1,bootindex=1,bus=pci.0,addr=05 \ -device virtio-net-pci,mac=9a:2c:2d:2e:2f:30,id=idRLH8yG,netdev=idWzgGeX,bus=pci.0,addr=06 \ 2. Format the additional disk 2.1 echo list disk > cmd && echo exit >> cmd && diskpart /s cmd 2.2 echo select disk 1 > cmd && echo create partition primary >> cmd && echo select partition 1 >> cmd && echo assign letter=I >> cmd && echo exit >> cmd && diskpart /s cmd 2.3 format I: /FS:NTFS /V:local /Q /y 3. Install and register Iometer 3.1 cmd /c xcopy /y D:\Iometer\* C:\Iometer\ 3.2 cmd /c regedit /s C:\Iometer\iometer.reg 4. Run Iometer.exe with icf cmd /c Iometer.exe /c iometer-performance.icf /r C:\autotest_iometer_result.csv Actual results: 2014-02-18 09:09:20: C:\Iometer> 2014-02-18 09:26:02: Successful PortTCP::Connect 2014-02-18 09:26:02: - port name: 10.66.108.64 2014-02-18 09:26:02: Get port error in SynchReceive. 2014-02-18 09:26:02: Get port error in SynchReceive. 2014-02-18 09:26:03: 2014-02-18 09:26:03: C:\Iometer> Expected results: there is no error when do iometer and iometer can finish successfully Additional info: 1. Qemu CML: /home/staf-kvm-devel/autotest-devel/client/tests/virt/qemu/qemu \ -S \ -name 'virt-tests-vm1' \ -sandbox off \ -M pc \ -nodefaults \ -vga std \ -chardev socket,id=qmp_id_qmpmonitor1,path=/tmp/monitor-qmpmonitor1-20140218-090815-NKr7WQmD,server,nowait \ -mon chardev=qmp_id_qmpmonitor1,mode=control \ -chardev socket,id=serial_id_serial0,path=/tmp/serial-serial0-20140218-090815-NKr7WQmD,server,nowait \ -device isa-serial,chardev=serial_id_serial0 \ -chardev socket,id=seabioslog_id_20140218-090815-NKr7WQmD,path=/tmp/seabios-20140218-090815-NKr7WQmD,server,nowait \ -device isa-debugcon,chardev=seabioslog_id_20140218-090815-NKr7WQmD,iobase=0x402 \ -device ich9-usb-uhci1,id=usb1,bus=pci.0,addr=03 \ -drive id=drive_image1,if=none,cache=none,snapshot=off,aio=native,file=/home/staf-kvm-devel/autotest-devel/client/tests/virt/shared/data/images/win7-64-virtio.qcow2 \ -device virtio-blk-pci,id=image1,drive=drive_image1,bootindex=0,bus=pci.0,addr=04 \ -drive id=drive_disk1,if=none,cache=none,snapshot=off,aio=native,file=/home/staf-kvm-devel/autotest-devel/client/tests/virt/shared/data/images/storage.qcow2 \ -device virtio-blk-pci,id=disk1,drive=drive_disk1,bootindex=1,bus=pci.0,addr=05 \ -device virtio-net-pci,mac=9a:2c:2d:2e:2f:30,id=idRLH8yG,netdev=idWzgGeX,bus=pci.0,addr=06 \ -netdev tap,id=idWzgGeX,vhost=on,vhostfd=23,fd=22 \ -m 4096 \ -smp 4,maxcpus=4,cores=2,threads=1,sockets=2 \ -cpu 'Opteron_G4',+kvm_pv_unhalt,hv_relaxed,hv_spinlocks=0x1fff,hv_vapic \ -drive id=drive_cd1,if=none,snapshot=off,aio=native,media=cdrom,file=/home/staf-kvm-devel/autotest-devel/client/tests/virt/shared/data/isos/windows/winutils.iso \ -device ide-cd,id=cd1,drive=drive_cd1,bootindex=2,bus=ide.0,unit=0 \ -device usb-tablet,id=usb-tablet1,bus=usb1.0,port=1 \ -vnc :0 \ -rtc base=localtime,clock=host,driftfix=slew \ -boot order=cdn,once=c,menu=off \ -enable-kvm 2. cpuinfo: processor : 23 vendor_id : AuthenticAMD cpu family : 21 model : 1 model name : AMD Opteron(TM) Processor 6234 stepping : 2 microcode : 0x6000626 cpu MHz : 2400.140 cache size : 2048 KB physical id : 1 siblings : 12 core id : 5 cpu cores : 6 apicid : 75 initial apicid : 43 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid amd_dcm aperfmperf pni pclmulqdq monitor ssse3 cx16 sse4_1 sse4_2 popcnt aes xsave avx lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 nodeid_msr topoext perfctr_core perfctr_nb arat cpb hw_pstate npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold bogomips : 4799.75 TLB size : 1536 4K pages clflush size : 64 cache_alignment : 64 address sizes : 48 bits physical, 48 bits virtual power management: ts ttp tm 100mhzsteps hwpstate cpb