virt-aa-helper: uncommon devices break starting a guest: input evdev, nvdimm, rng
Bug #1757085 reported by
Christian Ehrhardt
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libvirt (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
Adding the following two to the devices section of a guest makes it fail to start.
<memory model='nvdimm'>
<source>
<path>
</source>
<target>
<size unit='KiB'
<node>0</node>
</target>
</memory>
<input type='passthrough' bus='virtio'>
<source evdev='
</input>
This is due to virt-aa-helper not adding their paths to the apparmor profile.
(Note that hot-add is covered via domain label callbacks that I currently implement - see bug 1755153).
summary: |
- virt-aa-helper: input evdev and nvdimm path in guest xml are not - accessible + virt-aa-helper: uncommon devices break starting a guest: input evdev, + nvdimm, rng |
Changed in libvirt (Ubuntu): | |
status: | New → In Progress |
importance: | Undecided → High |
To post a comment you must log in.
I was working on adding RNG support as well, but they actually are usually working.
/dev/random / urandom is in the apparmor base profile, more special paths are super-uncommon and therefore valid to be added by an admin.
For the EDG backend config is usually via UDP/IP so no path support needed either for the normal case.