blob: 30cb050c082daaaa709aa88b958c129af21d9d2d (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
|
virtual: 0.930
graphic: 0.910
i386: 0.890
architecture: 0.875
x86: 0.863
performance: 0.848
ppc: 0.844
socket: 0.843
device: 0.832
register: 0.829
user-level: 0.827
PID: 0.822
boot: 0.819
mistranslation: 0.817
TCG: 0.816
semantic: 0.809
network: 0.808
debug: 0.806
VMM: 0.805
files: 0.794
kernel: 0.791
permissions: 0.772
hypervisor: 0.768
vnc: 0.761
arm: 0.726
KVM: 0.724
risc-v: 0.723
assembly: 0.619
peripherals: 0.619
system_powerdown NOT working in qemu-kvm with KVM enabled for FreeBSD guests
system_powerdown stops working in qemu-kvm for FreeBSD guests if KVM is enabled.
How to reproduce:
1. qemu -cdrom ~/.VirtualBox/libvirt/FreeBSD-8.1-RELEASE-i386-bootonly.iso
2. Enter system_powerdown in the qemu console
3. Nothing happens.
Adding --no-kvm option makes system_powerdown work:
1. qemu --no-kvm -cdrom ~/.VirtualBox/libvirt/FreeBSD-8.1-RELEASE-i386-bootonly.iso
2. system_powerdown
3. FreeBSD installer shows the shutdown dialog as expected
Tested on FreeBSD 6.4, 7.2, and 8.0 with qemu-kvm 0.12.5 and older versions.
The subject should be: system_powerdown is NOT working - can someone correct this please?
I have the same issue with FreeBSD 8.1-RELEASE (i386 and x86_64) on qemu-kvm 0.12.5 (Fedora 13)
system_powerdown works properly for Linux and Windows 2008 guests, but not for FreeBSD The ACPI power button event is not received by the FreeBSD guest.
I found this (unconfirmed) status report:
http://www.spinics.net/lists/kvm/msg40064.html
So it seems to be a regression...
This is fixed upstream (in seabios actually) by commit 6d5a2172f2b76900572107868ec080400c4f615d -- see http://git.linuxtogo.org/?p=kevin/seabios.git;a=commit;h=6d5a2172f2b76900572107868ec080400c4f615d . I added this patch to Debian releases of qemu-kvm, both for squeeze and experimental.
The updated bios.bin works fine for me, thanks.
Marking this now as "Fix released" according to comment #3
|