[Bug 1845290] Re: ACPI issue with RHEL4 guest VM's
[Expired for qemu (Ubuntu) because there has been no activity for 60 days.] ** Changed in: qemu (Ubuntu) Status: Incomplete => Expired -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845290] Re: ACPI issue with RHEL4 guest VM's
Thank you for the link. I will try this in the next few days and post my results here. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845290] Re: ACPI issue with RHEL4 guest VM's
Yes, you can copy an old bios from a different system and specify the path you placed to it like [1]. It depends on how you want to resolve this special very outdated guest. As an alternative I might consider setting up a Xenial LXD container and granting it the few extra permissions it needs to run KVM. From there virsh/virt-manager or whatever you use can talk to the libvirt in the container and it can stay old as long as xenial is supported. [1]: https://libvirt.org/formatdomain.html#elementsOSBIOS -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845290] Re: ACPI issue with RHEL4 guest VM's
I came across this: https://fabianlee.org/2018/09/13/ubuntu-alternate- firmware-bios-for-kvm/ Can I use the qemu-provided bios in 16.04 and use it in 18.04 for these VMs with really old kernels? -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845290] Re: ACPI issue with RHEL4 guest VM's
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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845290] Re: ACPI issue with RHEL4 guest VM's
Hi Christian, I tried your suggestion... That definitely avoided the ACPI issue, however, the VM still won't completely shutdown when I run the poweroff command. virsh shutdown also doesn't do anything anymore, as far as the guest is concern. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845290] Re: ACPI issue with RHEL4 guest VM's
Hi Michael, You could give it a try without acpi [1][2], which often works fine and in many cases helps to avoid awkward acpi issues. TL;DR: qemu: add -no-acpi argument libvirt: drop acpi from features [1]: https://qemu.weilnetz.de/doc/qemu-doc.html#index-_002dno_002dacpi [2]: https://wiki.libvirt.org/page/QEMUSwitchToLibvirt#-no-acpi -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845290] Re: ACPI issue with RHEL4 guest VM's
The host where the problem doesn't happen runs Ubuntu 16.04 with kernel 4.15.0-58-generic and qemu-kvm 1:2.5+dfsg-5ubuntu10.41 My work desktop is running on Ubuntu 18.04 with kernel 5.0.0-25-generic and qemu-kvm 1:2.11+dfsg-1ubuntu7.17 The Oracle Bare Metal host is running Ubuntu 18.04 (minimal install) with kernel 4.15.0-1025-oracle and qemu-kvm 1:2.11+dfsg-1ubuntu7.18 The RHEL4 guest runs kernel 2.6.9-67.ELsmp I tested two additional VMs, this time they are on Ubuntu 8.04 with kernel 2.6.24-32. One exhibits a similar issue, but the other one doesn't. VMs running more recent Ubuntu releases and even Windows 7 guests do not exhibit this problem. So it is likely because of the old kernel version being incompatible with the newer ACPI tables qemu provides. :( Unfortunately, I cannot migrate the apps running in these VMs to a more recent RHEL release. :( Is there a way to provide these guests with old kernel the older SDT's? -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845290] Re: ACPI issue with RHEL4 guest VM's
** Package changed: kvm (Ubuntu) => qemu (Ubuntu) -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845290] Re: ACPI issue with RHEL4 guest VM's
On 25/09/2019 04:27, Michael Tinsay wrote: > Public bug reported: > > Background: > > I'm testing migration of our KVM guests from a server running on 16.04 > to a server running on 18.04. Could you, please, provide information regarding your kernel versions (host and guest) and the exact QEMU version you are using (package version) ? Does this happen in more recent kernels (being used with same RHEL 4 guest ?). > Issue: > > In all RHEL4-based guests tested, ACPI is not being loaded. dmesg log > contains the following: > > ACPI-0307: *** Error: ns_search_and_enter: Bad character in ACPI Name: > 2E5C1502 > ACPI-0292: *** Error: Looking up [0x2E5C1502] (NON-ASCII) in namespace, > AE_BAD_CHARACTER > ACPI-1134: *** Error: [NULL NAME], AE_BAD_CHARACTER > ACPI-0125: *** Error: acpi_load_tables: Could not load namespace: > AE_BAD_CHARACTER > ACPI-0134: *** Error: acpi_load_tables: Could not load tables: > AE_BAD_CHARACTER > ACPI: Unable to load the System Description Tables This likely happens because your guest kernel can't handle the ACPI tables being provided by QEMU. You can try dumping the ACPI tables and disassembling them by executing: $ sudo acpidump > acpi.dat $ acpixtract -a acpi.dat $ rm acpi.dat and then executing: $ for file in *.dat; do iasl -d $file; done this will generate several .dsl files you can attach to this case. But, it is very likely that it is your guest kernel that misbehaves with more recent ACPI tables definitions, and, instead of finding only ASCII chars where it expects, it also reads some binary data that it wasn't expecting (and complains about it being non UTF-8, for example). > The VMs will continue to boot up and run fine. But since ACPI is not > running properly, the VMs do not completely shutdown when powering off. > Issuing virsh shutdown on the host also doesn't work because > of this situation. > > I have tested this on 2 different machine: my work desktop and a bare > metal instance in Oracle Cloud. Both are running 18.04 with latest > updates. > > ** Affects: kvm (Ubuntu) > Importance: Undecided > Status: New ** Changed in: kvm (Ubuntu) Status: New => Incomplete ** Changed in: kvm (Ubuntu) Importance: Undecided => Low -- 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/kvm/+bug/1845290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
