I think this has been fixed by this commit here:
https://git.qemu.org/?p=qemu.git;a=commitdiff;h=d139e9a6cf01b8c31f59
... so closing this ticket now.
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thanks for reporting this bug.
That certainly could be confusing. However, practically speaking, since
qemu was compiled without that support, it becomes more difficult for
qemu to tell the difference between a unsupported but otherwise-valid
type, and an invalid type.
Perhaps upstream would
Thanks for reporting this bug.
That certainly could be confusing. However, practically speaking, since
qemu was compiled without that support, it becomes more difficult for
qemu to tell the difference between a unsupported but otherwise-valid
type, and an invalid type.
Perhaps upstream would
** Also affects: qemu-kvm (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/838974
Title:
Confusing error report for missing vde
** Also affects: qemu-kvm (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/838974
Title:
Confusing error report for missing vde support
To manage
