Description of problem:
The qemu monitor system_powerdown command no longer has any effect in qemu 2.1 in Fedora 21.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
* Download images
$ mkdir test
$ cd test
$ wget http://files.cockpit-project.org/testdata/images/cockpit-fedora-20-x86_64-root.xz
$ wget http://files.cockpit-project.org/testdata/images/cockpit-fedora-20-x86_64-initrd.xz
$ wget wget http://files.cockpit-project.org/testdata/images/cockpit-fedora-20-x86_64-kernel.xz
$ xz -d *.xz
* Run the system
$ /usr/bin/qemu-system-x86_64 -machine accel=kvm -m 1024 -drive if=virtio,file=$PWD/cockpit-fedora-20-x86_64-root,index=0,serial=ROOT,snapshot=on -kernel $PWD/cockpit-fedora-20-x86_64-kernel -initrd $PWD/cockpit-fedora-20-x86_64-initrd -append "root=/dev/vda console=ttyS0 quiet enforcing=0" -nographic -monitor unix:path=$PWD/cockpit.mon,server,nowait
* Wait for the VM to boot
* In another terminal, run the system_powerdown command in the qemu monitor:
$ cd test
$ nc -U cockpit.mon
QEMU 2.1.0 monitor - type 'help' for more information
No effect on the running VM.
The VM shuld proceed to shutdown (as if an ACPI power button had been pressed). This happened in qemu 1.6.x. The exit code should be zero.
The above test case works well on Fedora 20 with identical images, with qemu-1.6.2-7 and similar.
*** Bug 1139357 has been marked as a duplicate of this bug. ***
I reproduced the issue with 2.1.0 packages in f21, but the issue seems fixed with 2.1.1 stable which I'm building now.
qemu-2.1.1-1.fc21 has been submitted as an update for Fedora 21.
* should fix your issue,
* was pushed to the Fedora 21 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing qemu-2.1.1-1.fc21'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
This fixes the issue with the cockpit integration tests.
qemu-2.1.1-1.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.