Bug 1301104
| Summary: | [RFE] Automate configuration of host's boot parameters to support VFIO passthrough | |||
|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Michal Skrivanek <michal.skrivanek> | |
| Component: | RFEs | Assignee: | Martin Polednik <mpoledni> | |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Nisim Simsolo <nsimsolo> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | high | |||
| Version: | 3.6.0 | CC: | bugs, danken, fdeutsch, jniederm, mavital, melewis, mgoldboi, michal.skrivanek, nsimsolo, tjelinek, ycui | |
| Target Milestone: | ovirt-4.0.0-beta | Keywords: | FutureFeature | |
| Target Release: | 4.0.0 | Flags: | rule-engine:
ovirt-4.0.0+
rule-engine: exception+ nsimsolo: testing_plan_complete+ mgoldboi: planning_ack+ tjelinek: devel_ack+ mavital: testing_ack+ |
|
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Enhancement | ||
| Doc Text: |
Previously, any modification to the kernel command line had to be executed and maintained by administrators. This process was more complex in the Red Hat Enterprise Virtualization Hypervisor as the file system had to be manually remounted as writable to make the required changes.
Now, a new UI selection has been added when adding or editing a host that allows for kernel line modifications directly from the web administration portal. These changes are then maintained by Red Hat Virtualization. Supported modifications are supported as checkboxes but more complex modifications are also allowed as free text entry.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1375893 (view as bug list) | Environment: | ||
| Last Closed: | 2016-08-01 12:28:41 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1234283, 1235331, 1270581, 1301082, 1341268, 1372178, 1375893 | |||
|
Description
Michal Skrivanek
2016-01-22 15:33:41 UTC
For reference vintage node is using grub2 - but the grub2 configuration file is not under /boot. In addition vintage Node is _only_ caring about grub.conf - and not about the additional files /etc/sysconfig/grub and others. If it's only about 4.0, then Node Next will be used, which will work as CentOS/RHEL does. Just for reference: There is already a tool to add customer kernel arguments to the bootloader config: grubby. https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/System_Administrators_Guide/sec-Making_Persistent_Changes_to_a_GRUB_2_Menu_Using_the_grubby_Tool.html grubby is currently the most likely candidate to be used on Node Next as well for bootloader configuration. It supports grub, grub2 and syslinux and other bootloaders. grubby should be a good solution for 4.0, we won't have to deal with grub directly Let me note that oVirt Node Next is now using grubby (as recommended) to modify the grub.cfg file. Don't you also need to boot the host (I wonder if kexec would suffice?) Yes, it needs to be rebooted. But if we make it a part of redeploy it's ok, we can do a full "normal" reboot. Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA. changes are in, just waiting on host-deploy respin and spec update Verified: rhevm-4.0.2.2-0.1.el7ev qemu-kvm-rhev-2.3.0-31.el7_2.20.x86_64 libvirt-client-1.2.17-13.el7_2.5.x86_64 vdsm-4.18.9-1.el7ev.x86_64 Test plan attached to external trackers. Hm, it seems documentation was not really updated with the new feature. Let me open a new doc bug for that as we need to update screenshots of Cluster dialog and add a bit more details about supportability of each kernel option |