Bug 836145
Summary: | Whitelist or blacklist guests that can enter suspend states | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Amit Shah <amit.shah> |
Component: | libvirt | Assignee: | Michal Privoznik <mprivozn> |
Status: | CLOSED DUPLICATE | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.3 | CC: | acathrow, ajia, amit.shah, dallan, dyasny, dyuan, eblake, mzhan, rwu, whuang |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-09-10 07:06:24 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Amit Shah
2012-06-28 08:39:19 UTC
Libvirt is too low-level to know which guest OS is installed in a VM; you may need to clone this bug to higher-level components like virt-install to create guests correctly in the first place based on attributes learned from libosinfo about what the guest should be able to support. That said, libvirt _does_ need to provide a way to determine which bios to use, as part of the domain XML, so that the upper-level software sets this ability correctly based on whether the guest being installed supports S3/S4. However, this capability is _already_ present since 0.9.12: commit ddf2dfa1f79af0405df5ca10583764a497c7a0db Author: Daniel P. Berrange <berrange> Date: Tue Apr 10 15:02:13 2012 +0100 Wire up <loader> to set the QEMU BIOS path * src/qemu/qemu_command.c: Wire up -bios with <loader> * tests/qemuxml2argvdata/qemuxml2argv-bios.args, tests/qemuxml2argvdata/qemuxml2argv-bios.xml: Expand existing BIOS test case to cover <loader> But our docs are out of date, in not mentioning how to properly use the <loader> subelement in order to influence which bios is chosen: http://libvirt.org/formatdomain.html#elementsOSBIOS so this bug is definitely worth leaving open until that is resolved. Indeed the support has to come from higher layers. Note that there's another possibility to selecting a bios: qemu will gain a command line parameter to notify bios whether to advertise s3/s4 support or not. libvirt needs to insert this command line argument depending on whether the guest supports suspend functionality. I'll clone a bug separately for libvirt from the qemu bug for this new function. After discussion with Amit I am closing this as dup. *** This bug has been marked as a duplicate of bug 836462 *** |