Glad this resolved the awkward acpi issue. The shutdown problem in guest comes down to something RHEL4 specific, I'm rather sure it didn't realize/know it is without ACPI now. Probably uninstall or reinstall things related to acpid and apm - not sure what that would be on RHEL4 thou. But is was a common issue in the past search engines will give you plenty of suggestions for that - you need to find what works for you.
For the "virsh shutdown" you'll probably need to set "mode" now - from man page: By default the hypervisor will try to pick a suitable shutdown method. To specify an alternative method, the --mode parameter can specify a comma separated list which includes "acpi", "agent", "initctl", "signal" and "paravirt". The order in which drivers will try each mode is undefined, and not related to the order specified to virsh. For strict control over ordering, use a single mode at a time and repeat the command. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845290 Title: ACPI issue with RHEL4 guest VM's To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1845290/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
