FS#50408 - [qemu] i386 system moved to qemu-arch-extras with 2.6.0-2
Attached to Project:
Arch Linux
Opened by Ng Oon-Ee (ngoonee) - Tuesday, 16 August 2016, 03:35 GMT
Last edited by David Runge (dvzrv) - Friday, 22 April 2022, 06:34 GMT
Opened by Ng Oon-Ee (ngoonee) - Tuesday, 16 August 2016, 03:35 GMT
Last edited by David Runge (dvzrv) - Friday, 22 April 2022, 06:34 GMT
|
Details
Description:
A bit of a surprise that qemu-system-i386 is no longer packaged with [qemu] and has been moved to [qemu-arch-extras]. Opinion - i386 is one of the primary use-cases and should be supported with the main package, as its obviously more 'core' than arm/mips and the other architectures. Additional info: * package version(s) qemu-2.6.0-2 |
This task depends upon
Closed by David Runge (dvzrv)
Friday, 22 April 2022, 06:34 GMT
Reason for closing: Won't fix
Additional comments about closing: All system emulators are provided in separate split packages with qemu >= 7.0.0.
The meta package qemu-emulators-full can be used to install all of them.
Friday, 22 April 2022, 06:34 GMT
Reason for closing: Won't fix
Additional comments about closing: All system emulators are provided in separate split packages with qemu >= 7.0.0.
The meta package qemu-emulators-full can be used to install all of them.
I'm checking too and will report thereafter.
- uptime 3', idle
95-110 / 95-110 / 115-120 MiB
- and with an identical browser+session + 3' wait:
215-245 / 225-260 / 255-265 MiB
So basically this guest shows 8-18% more RAM usage between v2.6.0 i386 and v2.6.1 x86_64 (and 2-13% more between v2.6.1 and 2.6.1 x86_64), including the variations between consecutives launches with the same qemu binary. I run this so I know whether I need to install extra/qemu-arch-extra or not.
When I did the split, I keep the both official arches to make easy to emulate one another from i686 and x86_64.
Using "-cpu pentium2" did the trick for my current need. Do qemu-system-i386 can use this trick to emulate 64bits system?
If we can substitute x86_64 emulator for all cases, why upstream still provides 2 binaries?