QEMU 7.0 Released With Intel AMX Support, Many RISC-V Additions

[Anux]

and as for the Armv4 it's removing support from the backend, meaning qemu TCG will no longer work on Armv4 hosts, not that Armv4 will no longer work inside of qemu.

And whats the use of emulating another arch on an arm4 device anyways? It most likely doesn't have enogh ram and it certainly would be slow as hell.

[Quackdoc]

My setup is extra special (AMD decided to change something in their windows driver 4 years ago and since then I need to manually design the PCIe layout) I have no hopes of ever getting a GUI that supports this kind of fuckery. Took me a day testing, searching the net and reading man pages. ^_^ It's my hobby and I learned alot.

lol, I would certainly love too see what a gui that would support functionality like this would look like, it would be a mess to say the least LOL

[Quackdoc]

- QEMU 7.0 drops support for old PowerPC 401 / 403 / 601 / 602 CPUs.

- Dropping of Armv4 and Armv5 from the Tiny Code Generator (TCG).

Or what did you mean?

for the power PC stuff, all of the removed CPUs full functionality is kept from their later targets (IE. 604 cpu is fully compatible with 601) (same with 401 and 405 I believe might be wrong on this one though) so it's just bloat, literally nothing as lost.

and as for the Armv4 it's removing support from the backend, meaning qemu TCG will no longer work on Armv4 hosts, not that Armv4 will no longer work inside of qemu.

[milkylainen]

what was depreciated that would effect this?

- QEMU 7.0 drops support for old PowerPC 401 / 403 / 601 / 602 CPUs.

- Dropping of Armv4 and Armv5 from the Tiny Code Generator (TCG).

Or what did you mean?

[Anux]

if you wanted a good UI you would need a dedicated qemu UI.

My setup is extra special (AMD decided to change something in their windows driver 4 years ago and since then I need to manually design the PCIe layout) I have no hopes of ever getting a GUI that supports this kind of fuckery. Took me a day testing, searching the net and reading man pages. ^_^ It's my hobby and I learned alot.

[Quackdoc]

Can't say I'm a fan of all the deprecation.
Half the point of QEMU is to run things without physical hardware.
To be able to emulate a older ARM is useful if you're writing esoteric stuff.

Not everything is a modern desktop or a server system.
If the m68k can live in the form of virtualization, so should the older ARMs and PPCs.

what was depreciated that would effect this?

[milkylainen]

Can't say I'm a fan of all the deprecation.
Half the point of QEMU is to run things without physical hardware.
To be able to emulate a older ARM is useful if you're writing esoteric stuff.

Not everything is a modern desktop or a server system.
If the m68k can live in the form of virtualization, so should the older ARMs and PPCs.

[Quackdoc]

Hey, I tried to use virtmanager several times and allways had some options that didn't work with it or I couldn't even get the whole mess to run at all. At the end I allways rolled back to a shell script with a super long quemu-line in it, atleast thats controlable and gives working results. Not easy, pretty ugly but enough for my windows gaming needs.

one of the issues with qemu is there are so many bloody options, making a UI for it is quite the chore. also libvirt isn't a qemu control but a generic vm control platform. though virtmanager is more oriented to KVM (using qemu), it also supports LXC and XEN VMs.

if you wanted a good UI you would need a dedicated qemu UI. but like I said, that can be quite the chore. I once thought about tackling it, but that would have to be a paid job lol. making a simple GUI for options would be fairly easy, making it look okay and be usable however. well avoiding choice vomit might be a hassle

[Anux]

For many many years I have seen a lot people who struggle with QEMU command arguments. Most try a user-friendly interface like VirtManager, then they try to find out what commands are being generated. Some scratch in the logs of "/var/log/libvirt/qemu/", others try "ps aux | grep KVM" and even if users know about "virsh domxml-to-native" they struggle a lot. I sympathize with them. I've been there. It's not fun at all.

Hey, I tried to use virtmanager several times and allways had some options that didn't work with it or I couldn't even get the whole mess to run at all. At the end I allways rolled back to a shell script with a super long quemu-line in it, atleast thats controlable and gives working results. Not easy, pretty ugly but enough for my windows gaming needs.

[Quackdoc]

still no vulkan support sadly, but the new dbus interface is really nice, hope it leads to some better VDI setups.