On 10/08/2012 03:13 PM, Stefan G. Weichinger wrote: > > Greetings, libvirt-users ... > > I ask for help with virtualizing an ancient machine with a linux kernel 2.2. > > I already succeeded doing that but I face random performance issues and > I somehow get lost in all the settings and options. > > I am using Virtual Machine Manager: > > * I can't chose something like Linux for the OS and 2.2 for the kernel. > > Does the combination "linux/2.4 kernel" work or should I choose "Other" > or "Generic" ? This is a question for virt-manager, which is a package built on top of libvirt, and maintained on the virt-tools-list@xxxxxxxxxx [cc'd, in case someone wants to add more details to this thread]. That said, my understanding is that the only use virt-manager makes of these designations is knowing in advance whether your guest is able to support virtio out of the box (newer Linux builds do, older ones don't), to know whether to expose the disk image to the guest as virtio (faster) or as scsi (slower, but portable to more guests). Choosing other/generic is always safe, if you later want to tweak things to see if virtio was supported after all. > > * Later there I get a choice of "Architektur" (or "architecture" ? > german here): for a 32bit-guest, should it be "i686" to reflect the > environment for the guest or "x86_64" to fully use the potential of the > host? For running a 32-bit guest, either mode works (you can ALWAYS run a 32-bit OS on 64-bit hardware); the difference is that 64-bit mode gets slightly more testing, but 32-bit mode is slightly more efficient as it does not have to emulate instructions for 64-bit operations that will not be used by your 32-bit guest. -- Eric Blake eblake@xxxxxxxxxx +1-919-301-3266 Libvirt virtualization library http://libvirt.org
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ libvirt-users mailing list libvirt-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvirt-users
