New profile: tqemu #6255
New profile: tqemu #6255
Conversation
There was a problem hiding this comment.
Why is the profile for a qemu wrapper in some cases more restrictive than the
profile for qemu itself (qemu-system-x86_64.profile)?
Suggestions:
- Move the contents of
qemu-system-x86_64.profileintoqemu-common.profile
and make the former (andqemu-launcher.profile) redirect to the latter - Make
tqemu.profileredirect toqemu-common.profile - Harden
qemu-common.profile(preferably in another PR as it may cause
breakage for qemu itself)
AFAIK tqemu is the only such wrapper that doesn't rely on libvirt. It's more limited in its functionality, but that also makes it very straightforward to sandbox. I'll need more time to refactor/double-check the qemu wrappers as you suggested. Thanks! |
That's good to know, but qemu itself does not use libvirt (it's essentially the My point was that in general it doesn't make much sense for a wrapper (tqemu)
On second though, for simplicity, I'd just copy and paste most of |
Done! |
Description: QEMU frontend without libvirt. https://github.com/thanoulis/tqemu
Add a common profile to deduplicate entries and make qemu-related profiles redirect to it. Relates to netblue30#6255.
Add a common profile to deduplicate entries and make qemu-related profiles redirect to it. Relates to netblue30#6255.
Add a common profile to deduplicate entries and make qemu-related profiles redirect to it. Relates to #6255.
tqemu
Description: QEMU frontend without libvirt.
https://github.com/thanoulis/tqemu