On Wed, 01/25 18:37, Narcis Garcia wrote: > El 25/01/17 a les 12:53, Fam Zheng ha escrit: > > On Wed, 01/25 12:43, Narcis Garcia wrote: > >> El 25/01/17 a les 09:49, Alberto Garcia ha escrit: > >>> On Mon, Jan 23, 2017 at 01:00:26AM +0100, Joe wrote: > >>> > >>>> I'm trying Qemu (2.8.0) on Slackware GNU Linux 14.2 (64-bit) host. > >>>> I've a Windows XP (guest) raw image which was working with Qemu > >>>> times ago (I used it on an older Slackware version as host system). > >>> > >>> The default hardware emulated by QEMU changes in each new version. > >>> > >>> If it worked with an earlier version and now you find that the guest > >>> is detecting new hardware, try forcing the emulation of a machine from > >>> an older version of QEMU. > >>> > >>> For example: > >>> > >>> qemu-system-i386 -M pc-i440fx-1.6 -m 2G ... > >>> > >>> Type 'qemu-system-i386 -M ?' for a complete list. > >>> > >>> Berto > >>> > >> > >> Is there some documentation about default hardware for each QEMU version? > >> For similar reason, I'm interested in to use equivalent specification by > >> parameters, to "freeze" a lot of guests' hardware environments. > >> > >> > > > > In this case you may want to use virt-manager/libvirt to manage your VMs, > > which > > will take care of stablizing QEMU parameters across version changes and even > > more importantly migration (in case you use it). > > > > Fam > > > > 3 reasons: I prefer to control what is Qemu emulating, I already have > guest OSes configured for a Qemu defaults, and I use my own virtual > manager (not the libvirt one). > I suppose libvirt developers had the same question to solve. >
libvirt uses -nodefaults to build the emulated devices explicitly. Fam
