Skip to contentSkip to conversation

is shutdown/halt supposed to work?

DISCUSSION Ingo Molnar 2 participants 4 messages Mar 10, 2007 – Mar 11, 2007 3 messages not in the archive KVM

lore
Share & tools
lore
#0 lore raw

here's a really stupid question that i remember having seen discussed here before but for which i didnt find the answer in the archives: if i do a shutdown/halt in a KVM (Linux/Fedora) guest then is qemu supposed to exit back to the command line? Currently qemu just keeps looping when i do that, i have to kill it explicitly to make the guest stop.

Ingo

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

A message that is not in the archive (sent off-list or not yet received): [email protected]

#2 lore raw
Quoted 7 lines · Ingo Molnar

here's a really stupid question that i remember having seen discussed here before but for which i didnt find the answer in the archives: if i do a shutdown/halt in a KVM (Linux/Fedora) guest then is qemu supposed to exit back to the command line? Currently qemu just keeps looping when i do that, i have to kill it explicitly to make the guest stop.

I've actually never tried an orderly shutdown - I'm too impatient :). As it works well in qemu (0.8.2), I expect the problem is with our non-functioning acpi (the kernel complains acpi is broken when it starts up).

Signature · 8 lines
error compiling committee.c: too many arguments to function


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

A message that is not in the archive (sent off-list or not yet received): 45F3C9E9.1000804-atKUWr5tajBWk0Htik3J/[email protected]

#4 lore raw
Quoted 4 lines · Avi Kivity

I've actually never tried an orderly shutdown - I'm too impatient :). As it works well in qemu (0.8.2), I expect the problem is with our non-functioning acpi (the kernel complains acpi is broken when it starts up).

do you mean this message:

Using APIC driver default
ACPI: RSDP 000FA6A0, 0014 (r0 BOCHS )

 ACPI: RSDT 225F0000, 002C (r0 BOCHS  BXPCRSDT        1 BXPC        1)
 ACPI: FACP 225F002C, 0074 (r0 BOCHS  BXPCFACP        1 BXPC        1)
 ACPI: DSDT 225F0100, 0832 (r1   BXPC   BXDSDT        1 INTL 20060912)

ACPI: FACS 225F00C0, 0040
ACPI: APIC 225F0938, 0040 (r0 BOCHS BXPCAPIC 1 BXPC 1)
ACPI: no DMI BIOS year, acpi=force is required to enable ACPI
ACPI: Disabling ACPI support

? I guess we could fill in the DMI BIOS year. I'll try acpi=force.

Ingo

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

A message that is not in the archive (sent off-list or not yet received): [email protected]

#6 lore raw
Quoted 16 lines · Ingo Molnar
Quoted 5 lines · Avi Kivity

I've actually never tried an orderly shutdown - I'm too impatient :). As it works well in qemu (0.8.2), I expect the problem is with our non-functioning acpi (the kernel complains acpi is broken when it starts up).

do you mean this message:

Using APIC driver default
ACPI: RSDP 000FA6A0, 0014 (r0 BOCHS )

 ACPI: RSDT 225F0000, 002C (r0 BOCHS  BXPCRSDT        1 BXPC        1)
 ACPI: FACP 225F002C, 0074 (r0 BOCHS  BXPCFACP        1 BXPC        1)
 ACPI: DSDT 225F0100, 0832 (r1   BXPC   BXDSDT        1 INTL 20060912)
Quoted 8 lines

ACPI: FACS 225F00C0, 0040
ACPI: APIC 225F0938, 0040 (r0 BOCHS BXPCAPIC 1 BXPC 1)
ACPI: no DMI BIOS year, acpi=force is required to enable ACPI
ACPI: Disabling ACPI support

? I guess we could fill in the DMI BIOS year. I'll try acpi=force.

I'm more worried about

Quoted 5 lines

ACPI: Core revision 20060707
ACPI Error (hwacpi-0179): Hardware did not change modes [20060707] ACPI Error (evxfevnt-0084): Could not transition to ACPI mode [20060707] ACPI Warning (utxface-0154): AcpiEnable failed [20060707]
ACPI: Unable to enable ACPI

which I get on my FC6 guest. The Windows issues also point to general acpi brokenness.

Signature · 8 lines
error compiling committee.c: too many arguments to function


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV