QEMU 5.0 recognition issue

Question

QEMU 5.0 recognition issue

nphuracm opened this issue 4 years ago · comments

I'm on Debian Buster armhf. When I finish compiling the latest QEMU release - QEMU 5.0.0, installed it and tried to load it into AQEMU, something weird happens. Here's a screenshot:

My QEMU release was being recognized as QEMU 2.0. Then I tried to manually locate the binary files(in my home directory), but then AQEMU popped out a lot of warnings saying that it can't read info from file or stuff. After that my QEMU was recognized as an "obsolete" QEMU release.
(I looked at the about page and it says that AQEMU contains support for QEMU 2.0 and up! Then why QEMU 5.0.0 couldn't be configured?)
(Extra info: When I tried to rename QEMU in AQEMU, AQEMU crashed. Also, the QEMU release's version defined in AQEMU cannot be changed anyway.)

Tobi · Answer 1 · Sun Jul 26 2020 23:38:37 GMT+0800 (China Standard Time)

@pankdora
Eventually support for old versions like QEMU2.0 will probably have to be dropped.

Currently either it detects your qemu installation or it doesn't. And if it does, it'll recognize it as QEMU 2.0 no matter which version you have. There's really no distinction of QEMU versions for now.

I'm thinking about making QEMU 5.0 or 4.0 the new minimum requirement, if I make a new AQEMU release.

Did you get it to work?

nphuracm · Answer 2 · Tue Jul 28 2020 13:56:46 GMT+0800 (China Standard Time)

Uh, yes, it does work for basic features, but I couldn't use some features shown in AQEMU and I think maybe they are obsoleted. For example, I tried to map a USB drive to a VM and QEMU says that it doesn't recognize the -device option "usb-host".

Tobi · Answer 3 · Wed Jul 29 2020 00:13:11 GMT+0800 (China Standard Time)

Thanks for the report. I'd like people to always post the full error message and detailed steps of how they got there. Not saying it isn't enough how you did make the report, but it'd make my life even simpler, if you provided a step by step guide about the error, or even screenshots. I'm not using AQEMU all the time, you know, and therefore I sometimes need a little reminder how things are done there. Also as a reference for future developers, detailed step by steps are always best. Definitely not complaining about you, I think the report is helpful, just saying it would be nicer for me as a developer if all error reports were in great detail, so I can easily reproduce them.