** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1910696
Title:
Qemu fails to start with error " There is no option group 'spice'"
Fixed here:
https://gitlab.com/qemu-project/qemu/-/commit/632a8873500d27022c
** Changed in: qemu
Status: Expired => Fix Committed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1910696
Title:
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1910696
Title:
Qemu fails
The QEMU project is currently moving its bug tracking to another system.
For this we need to know which bugs are still valid and which could be
closed already. Thus we are setting the bug state to "Incomplete" now.
If the bug has already been fixed in the latest upstream version of QEMU,
then
** Tags removed: qemu
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1910696
Title:
Qemu fails to start with error " There is no option group 'spice'"
Status in QEMU:
New
Bug description:
Are there any downsides of compiling modules statically (like what
Debian folks do)?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1910696
Title:
Qemu fails to start with error " There is no
Due to this bug, I cannot start LXD virtual machines on Arch Linux
anymore.
$ lxc start debian10vm
Error: Failed to run: forklimits limit=memlock:unlimited:unlimited --
/usr/bin/qemu-system-x86_64 -S -name debian10vm -uuid
e265f257-85ca-445f-be5c-0170dca5955d -daemonize -cpu host -nographic
Additional information: This error occurs only if spice is compiled as
module (`--enable-modules`) and spice parameters are supplied from file
with `-readconfig /path/to/file` . If spice parameters are supplied from
the command line (`-spice param1=a,param2=b`) , an error does not occur.
Possible
