Bug 870587
| Summary: | KVM: Kaspersky 2013 installer dies in XP guest | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Todd <ToddAndMargo> | ||||||
| Component: | qemu-kvm | Assignee: | Andrea Arcangeli <aarcange> | ||||||
| Status: | CLOSED WORKSFORME | QA Contact: | Virtualization Bugs <virt-bugs> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 6.2 | CC: | acathrow, areis, bsarathy, chayang, dyasny, juzhang, michen, mkenneth, qiguo, qzhang, rhod, virt-maint | ||||||
| Target Milestone: | rc | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2012-11-17 17:01:08 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
Todd
2012-10-27 03:40:02 UTC
Created attachment 634115 [details]
xp guest xml file
hi Todd, I have tried reproduce the bug what you hit, but till now, it not happen, # rpm -qa \*qemu\* qemu-kvm-0.12.1.2-2.295.el6_3.2.x86_64 qemu-kvm-debuginfo-0.12.1.2-2.295.el6_3.2.x86_64 qemu-img-0.12.1.2-2.295.el6_3.2.x86_64 qemu-guest-agent-0.12.1.2-2.295.el6_3.2.x86_64 gpxe-roms-qemu-0.9.7-6.9.el6.noarch qemu-kvm-tools-0.12.1.2-2.295.el6_3.2.x86_64 # rpm -qa \*spice\* spice-vdagent-0.8.1-3.el6.x86_64 spice-client-0.8.2-15.el6.x86_64 spice-glib-0.11-11.el6.x86_64 spice-gtk-0.11-11.el6.x86_64 spice-protocol-0.10.1-5.el6.noarch spice-server-debuginfo-0.12.0-1.el6.x86_64 spice-gtk-python-0.11-11.el6.x86_64 spice-client-debuginfo-0.8.2-15.el6.x86_64 spice-server-0.10.1-10.el6.x86_64 steps to reproduce 1.according to the xml file, boot and install a windows xp SP3 guest with virt-manager, cli like this #/usr/libexec/qemu-kvm -name 295-6-3-2-c2 -S -M rhel6.3.0 -cpu Nehalem,-popcnt,-sse4.2 -enable-kvm -m 4096 -smp 4,sockets=2,cores=2,threads=2 -uuid 273065fa-0220-803d-24b4-332b1ccecfbe -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/295-6-3-2-c2.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime,driftfix=slew -no-shutdown -boot order=c,menu=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/var/lib/libvirt/images/295-6-3-2-c2.img,if=none,id=drive-ide0-0-0,format=qcow2,cache=none,aio=threads -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -netdev tap,fd=22,id=hostnet0,vhost=on,vhostfd=24 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:bf:84:54,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -device usb-tablet,id=input0 -spice port=5901,addr=127.0.0.1,disable-ticketing -k en-us -vga qxl -global qxl-vga.vram_size=67108864 -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 2.install virtio devices drivers inside guest(also test without installing them) 3.install kis12.0.0.374en_gb.exe(url:http://products.kaspersky-labs.com/english/homeuser/kis2012/kis12.0.0.374en_gb.exe) inside guest(also test without installing it ) 4.try to install kis13.0.1.4190en.exe(url:http://usa.kaspersky.com/files/?file=kis&lang=en&ver=2013&pn=Downloads+%7C+Product+Updates+%7C+Kaspersky+Internet+Security) Actual Results kis13.0.1.4190en.exe installer runs happily and finished without errors, during the tests i changed the vcpu type to Penryn/Sandbridge/Nehalem/core2duo,and resized the memory, but no errors either. If my steps are wrong or missing anything, please correct me. Thanks Created attachment 637010 [details]
The one of the xml files I used for testing
Retry to reproduce this bug: Setup: 1.According to the xml supported by Todd, virsh edit the vm.xml i used. 2.Install the drivers with virtio-win-1.5.4 for balloon, virtio-serial, qxl. 3.Install and verify vdservice started. 4.Clone 3 vms with the virt-manager. Then try to reproduce the bug in following scenarios: Steps: Scenario 1:install kis2013 directly. 1.Run the installer kis13...... 2.Installer progress:extract package files 100%. 3.Installer progress:rearch "Welcome to kaspersky Internet Security 2013" wizard,then click "install" button. 4.Installer progress: rearch "The application is being installed...", start installing application. 5.Install successfully. Actual result: not hit the bug. Scenario 2:install kis2012 then install kis2013 without kis2012 uninstalled. 1.Run the installer kis2012. 2.After it installed, reboot vm. 3.Run the installer kis13...... 4.Installer progress:extract package files 100%. 5.Installer progress:rearch "Welcome to kaspersky Internet Security 2013" wizard,then click "install" button. 6.Installer progress: rearch "The application is being installed...", start installing application. 7.Install successfully, reboot the vm. Actual result: not hit the bug. Scenario 3:install kis2012 then install kis2013 with kis2012 uninstalled. 1.Run the installer kis2012. 2.After it installed, reboot vm. 3.Uninstall kis2012, reboot vm. 4.Run the installer kis13...... 5.Installer progress:extract package files 100%. 6.Installer progress:rearch "Welcome to kaspersky Internet Security 2013" wizard,then click "install" button. 7.Installer progress: rearch "The application is being installed...", start installing application. 8.Install successfully. Actual result: not hit the bug. Hi Todd If my steps are wrong or missing anything, please correct me. And I attached a xml i used. Thanks! Qian Guo Hi Qian, I am not ignoring you. Thing have been crazy around here. It may be a week or two before I can followup. I appreciate your patience. -T Hi Todd, Thank you for taking the time to enter a bug report with us. We appreciate the feedback and look to use reports such as this to guide our efforts at improving our products. That being said, this bug tracking system is not a mechanism for requesting support, and we are not able to guarantee the timeliness or suitability of a resolution. If this issue is critical or in any way time sensitive, please raise a ticket through your regular Red Hat support channels to make certain it receives the proper attention and prioritization to assure a timely resolution. For information on how to contact the Red Hat production support team, please visit: https://www.redhat.com/support/process/production/#howto Thanks, Ronen. |