Bug 1523463

Created attachment 1364619 [details]
try to figer out bashrecord

Hi,
Recently I was setting up a compute node for openstack,following is my enviroment:

Server:Centos7x64 with fully updated,and epkernal updated to 
Linux compute2 4.14.3-1.el7.elrepo.x86_64 #1 SMP Thu Nov 30 09:35:20 EST 2017 x8
6_64 x86_64 x86_64 GNU/Linux

qemu:qemu-img version 2.9.0(qemu-kvm-ev-2.9.0-16.el7_4.8.1)
Copyright (c) 2003-2017 Fabrice Bellard and the QEMU Project developers

openstack:openstack pike with rdo source,with selfservice network(linuxbridge) and cinder.

and then I created a windows2012r2 image (follow step of https://docs.openstack.org/image-guide/windows-image.html instead one step different virt-install --os-distro windows --os-version 2012,my virt-install cannot identify os distro and os version params so I delete these two params)
for openstack with virtio-win-0.1.141.iso(stable),there are three drivers I use,which is 
1.virtio-Netkvm                                  when I'm install windows
2.virtio-Disk & SCSI                             when I'm install windows
3.virtio-Ballon                                  when windows setup over,I loginto it and found there was a yello error PCI device,try to setup it with virtio ISO and it tell me successful installed ballon driver,so it should be a ballon device.
Description of problem:
after installed virtio-ballon driver,I upload the image to openstack and created a instance,running and then I click start-menu--shutdown I got a explorer.exe reported 
0x192200668 invoked 0x192200668memoryaddress,the memory cannnot be writen.
Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.create a win2012 r2 image with ballon,virtio network and virtio 
2.upload to openstack
3.make a instance and when it's running,shutdown or reboot

Actual results:
windows 2012 r2 with ballon drive cannot normally shutdown,first explorer.exe report a memory cannot be writen ,then continue then hangs on in the last picture of windows(on shutting down）

Expected results:
shutdown and release memory and other virtual device normally

Additional info:
please check attachment,thanks!