Bug 1583328
| Summary: | NPE while running VM with passthrough network vnic type | ||
|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Tomas Jelinek <tjelinek> |
| Component: | BLL.Virt | Assignee: | Andrej Krejcir <akrejcir> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Nisim Simsolo <nsimsolo> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | future | CC: | akrejcir, bugs, lsvaty, michal.skrivanek, rbarry, rdlugyhe, sgoodman |
| Target Milestone: | ovirt-4.4.0 | Flags: | pm-rhel:
ovirt-4.4+
|
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ovirt-engine 4.4.0-27 22b6f82 | Doc Type: | Bug Fix |
| Doc Text: |
Previously, a custom scheduler policy was used without the `HostDevice` filter. Consequently, the virtual machine was scheduled on an unsupported host, causing a null pointer exception.
With this update, some filter policy units are now mandatory, including `HostDevice`. These filter policy units are always active, cannot be disabled, and they are no longer visible in the UI or API.
These filters are mandatory:
- Compatibility-Version
- CPU-Level
- CpuPinning
- HostDevice
- PinToHost
- VM leases ready
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-04-16 10:29:24 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: | |||
|
Description
Tomas Jelinek
2018-05-28 17:55:47 UTC
Reducing the severity since it happens only when using a custom scheduler and that does not include the HostDevice filter and asking for NIC passthrough - which is not a common scenario. Martin, I wonder if that's a virt bug. I understand the intent to provide flexible scheduling policies for users but making the HostDevice filter optional leads to this awkward scenario - unlike Memory filter for instance that can be dropped and we'll still be able to generate the VM configuration, in this case, we won't be able to produce a valid libvirt XML. Adding a validation right after the call to the scheduler is exactly like making the HostDevice filter mandatory, right? Re-targeting to 4.3.1 since it is missing a patch, an acked blocker flag, or both Andrej, can you answer the question? I suppose it's indeed like that and HostDevice should be mandatory. What needs to be done to make it so? Andrej, ping? Making the HostDevice filter mandatory is better than adding a validation after scheduling. The VM could be scheduled to a different host, where the passthrough works. We can create a set of mandatory policy units that would be always used. As a side effect, the mandatory filters would not show in the webadmin. This bug is targeted to 4.4.2 and in modified state. can we re-target to 4.4.0 and move to QA? Closing low/medium severity bugs, based on QE capacity, if you would like to still verify this issue please reopen. |