Marc, are you using spice and audio, and have no qemu-user-gui package
installed?
If yes, please try the same qemu usage but with qemu-user-gui package
installed, --
it might be #977301 and the prob is due to qemu segfaulting due to unexpectedly
missing audio backend.
Thanks,
/mjt
Control: tag -1 + unreproducible
25.12.2020 18:20, Marc Haber wrote:
On Sat, Dec 19, 2020 at 06:09:33PM +0300, Michael Tokarev wrote:
Note also this is just a warning, qemu is definitely not giving up, it
just says this way to open a device WILL not work in some future, but it
does work now.
On Sat, Dec 19, 2020 at 06:09:33PM +0300, Michael Tokarev wrote:
> Note also this is just a warning, qemu is definitely not giving up, it
> just says this way to open a device WILL not work in some future, but it
> does work now. And indeed it continues to work fine. So it looks like
> you missed
On Sat, Dec 19, 2020 at 06:00:23PM +0300, Michael Tokarev wrote:
> Marc, what do you want we to do?
The optimum would be saying what to do if this message is printed.
Surely there is a new way to open a block device. If that one is not yet
supported by libvirt, libvirt (upstream?) should work on
Control: tag -1 + moreinfo
19.12.2020 18:00, Michael Tokarev wrote:
19.12.2020 17:55, Marc Haber wrote:
This VM won't start any more with qemu 5.2, saying "Opening a block
device as a file using the file drive is deprecated". It unfortunately
Note also this is just a
19.12.2020 17:55, Marc Haber пишет:
Package: qemu-system-x86
Version: 1:5.2+dfsg-2
Severity: important
I have my VM images on individually encrypted LVs so that I can
individually lock and unlock VMs. This is what my block device looks
like:
[1/5386]mh@drop:~ $ ls -al /dev/mapper/centos
Package: qemu-system-x86
Version: 1:5.2+dfsg-2
Severity: important
I have my VM images on individually encrypted LVs so that I can
individually lock and unlock VMs. This is what my block device looks
like:
[1/5386]mh@drop:~ $ ls -al /dev/mapper/centos
lrwxrwxrwx 1 root root 8 Dez 19 15:47
7 matches
Mail list logo