Red Hat Bugzilla – Bug 816452
【virtio-win][balloon]Uninstall balloon driver from Device Manager leads to BSOD after changing balloon value in monitor
Last modified: 2013-02-28 07:59:55 EST
Description of problem:
Uninstalling balloon driver from device manager leads to BSOD after doing a series actions of reducing balloon values.
Version-Release number of selected component (if applicable):
Tried the bz for three times,all can reproduce the issue
Steps to Reproduce:
1.Boot up guest
/usr/libexec/qemu-kvm -m 4G -smp 2 -cpu cpu64-rhel6,+x2apic,family=0xf -usb -device usb-tablet -drive file=win2k8-64-run.raw,format=raw,if=none,id=drive-virtio0,cache=none,werror=stop,rerror=stop -device ide-drive,drive=drive-virtio0,id=virtio-blk-pci0,bootindex=1 -netdev tap,sndbuf=0,id=hostnet0,script=/etc/qemu-ifup,downscript=no -device e1000,netdev=hostnet0 -uuid 7a82fd37-b740-4105-8757-43b8aadce8b9 -monitor stdio -drive file=disk1.raw,if=none,id=drive-virtio1,cache=none,werror=stop,rerror=stop -device virtio-blk-pci,drive=drive-virtio1,id=virtio-blk-pci1 -drive file=disk2.raw,if=none,id=drive-virtio2,cache=none,werror=stop,rerror=stop -device virtio-blk-pci,drive=drive-virtio2,id=virtio-blk-pci2 -spice port=5952,disable-ticketing -vga qxl -device virtio-balloon-pci,id=balloon1
Reducing balloon value from monitor
(qemu) balloon 100
(qemu) balloon 2000
(qemu) balloon 1800
(qemu) balloon 1600
(qemu) balloon 1700
(qemu) balloon 1500
(qemu) info balloon
3.Go to Device Manager and uninstall the balloon driver
The guest should works well
Got three dumps and will upload them to the bug.
Similar issue can be found on window 2k3 32 bits,so please also have a look and I will put the related dump to the same location - comments 1 .Any issues feel free let me know,thanks
Dor, Vadim and I decided to postpone this bug to 6.4
It also occurs while upgrading balloon driver from 6.2 to 6.3 during memory balloon on 6.2.z host
will upload related dump files to the bug.
Created attachment 587992 [details]
Created attachment 587993 [details]
Reproduce the issue on windows 7 32 ,windows 2008 R2 and windows 2008 64.
Move back to original bug title due to the issue was orginal found in RHEL6.3 hosts.
When QE verify this issue , need to check driver update test as well .
please check with the most recent driver available at
Reproduced it on virtio-win-prewhql-0.1-27,
Steps,please refer to comments 0
Verified on virtio-win-prewhql-0.1-29
Steps,please refer to comment 0 and testing also included driver's upgrading
Base on above the bug is fixed on virtio-win-prewhql-0.1-29
According to comment #13 ,move status to VERIFIED.