I have a Wheezy guest I can't shutdown cleanly from libvirt (i.e. without logging into VM
and shutting down VM from within VM) because the guest is failing to get ACPI events.

The guest didn't have issues before jessie (i.e. while on Wheezy) and does have acpid and I've
even tried adding acpi-support to no avail.  acpi is enabled as a feature in the XML.

The strange thing is a Windows 8.1 guest is not having issues with this (it was created around
the same time as the wheezy guest, while host was on wheezy).

The command line generated by libvirt is:

LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin QEMU_AUDIO_DRV=none /usr/bin/kvm -name <name> -S -machine pc-1.1,accel=kvm,usb=off -m 256 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid <uuid> -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/<name>.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -boot order=cd,menu=on,strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x4 -drive if=none,id=drive-ide0-1-0,readonly=on,format=raw -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -drive file=<image>,if=none,id=drive-virtio-disk0,format=raw -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0 -netdev tap,fd=25,id=hostnet0 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=<mac>,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-seria
 l,chardev=charserial0,id=serial0 -device usb-tablet,id=input0 -vnc 127.0.0.1:1 -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6

Neither libvirt  nor the guest produce any logs as result of issuing the shutdown command from virt-manageer or virsh.

Check https://wiki.debian.org/libvirt/Debugging to get more logs. I
don't have any issues shuting down wheezy guests..
Cheers,
 -- Guido

I'll try to get some time to do some debugging.  The strange thing is
that a freshly installed wheezy guest has no problem, so it's really
only this one guest that is having issues, for no apparent reason.

What's really weird part is that I'm not aware of having made any
changes to that guest that should be remotely relevant.

Regards,

Daniel
 r
ia

Can you diff the two configurations please (working and non-workin
wheezy guest)? Otherwise I'm inclined to close this.
Cheers,
 -- Guido