On Tue, 26 Mar 2024 14:29:58 +0100 Philippe Mathieu-Daudé <philmd@xxxxxxxxxx> wrote: > Hi Igor, > > On 26/3/24 14:08, Thomas Huth wrote: > > > > s/iaspc/isapc/ in the subject > > > > On 26/03/2024 13.51, Igor Mammedov wrote: > >> ISAPC machine was introduced 25 years ago and it's a lot of time since > >> such machine was around with real ISA only PC hardware practically > >> defunct. > >> Also it's slowly bit-rots (for example: I was able to boot RHEL6 on > >> RHEL9 host > >> in only TCG mode, while in KVM mode it hung in the middle of boot) > > I'm quite opposed to this patch. QEMU models various very-old / > defunct hardware. I'm pretty sure Bernhard and myself are OK to > keep maintaining it, besides we are working in separating it from > the i440fx+piix machine. Also, this machine is particularly > interesting for my single-binary experiments. it would not be fair to ask you or Bernard to deal with every case where ISAPC related code gets in a way, nor it's fair to ask other contributors to ensure that their patches don't break semi-working ISAPC or refactor code that relates to it. [ for example I'd like to refactor smbios parts in the image ACPI table builder, but the I'd have to do it for legacy part as well without means to verify that. Sure it can be done but at cost of extra time spent to rewrite something that would never be used and to find test env to verify touched code. ] However I look at it, isapc is burden at this point and it gets into a way of evolving. [downstream hat] while both of you do a wonderful job of separating some parts of the mess we have, it's a lot of churn which is not ideal when it comes to backporting patches. [emotional hat] Nowadays with modern containers tooling it's very easy to spawn old qemu environment to play with removed machines/features. quick few minutes example that lets me run isapc on old ubuntu without need to read how to build containers in 100 different ways: toolbox create --distro ubuntu --release 22.04 toolbox enter ubuntu-toolbox-22.04 toolbox enter ubuntu-toolbox-22.04 [user@toolbox ~]$ sudo apt update [user@toolbox ~]$ sudo apt install qemu-system-x86 [user@toolbox ~]$ qemu-system-i386 -M isapc -vnc :0 my_toy.qcow2 PS: I haven't had high hopes of this getting accepted, but I had to try. Though recent trend was that upstream QEMU were deprecating/dropping old machines/devices (even ones that kernel folks were using for testing) and it hasn't caused the end of universe (old qemu(s) sill exists and can be used for those cases). > Where I agree is we should stop reporting "KVM on ISA/PC machine" > as supported. > > Regards, > > Phil. > > >> Rather than spending time on fixing 'the oldest' no longer tested > >> machine type, > >> deprecate it so we can clean up QEMU code from legacy fixups and > >> hopefully > >> make it easier to follow. > >> > >> Folks who have to use ancient guest that requires ISAPC can still > >> use older QEMU to play with it. > >> > >> Signed-off-by: Igor Mammedov <imammedo@xxxxxxxxxx> > >> --- > >> docs/about/deprecated.rst | 7 +++++++ > >> hw/i386/pc_piix.c | 1 + > >> 2 files changed, 8 insertions(+) > >> > >> diff --git a/docs/about/deprecated.rst b/docs/about/deprecated.rst > >> index 7b548519b5..5708296991 100644 > >> --- a/docs/about/deprecated.rst > >> +++ b/docs/about/deprecated.rst > >> @@ -226,6 +226,13 @@ These old machine types are quite neglected > >> nowadays and thus might have > >> various pitfalls with regards to live migration. Use a newer machine > >> type > >> instead. > >> +``isapc`` (since 9.0) > >> +''''''''''''''''''''''''''''''''''''''''''''''''''''' > >> + > >> +These old machine type are quite neglected nowadays and thus might have > > > > "This old machine type is ..." ? > > > >> +various pitfalls with regards to live migration. Use a newer machine > >> type > >> +instead. > > > > I doubt that isapc could ever be used reliably for live migration, since > > it's an unversioned machine type, so I think it would be better to not > > mention live migration here. > > > > Thomas > > > > > _______________________________________________ Devel mailing list -- devel@xxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxx
