for the kernel part, a devvmx vm *IS* a core basically and the physical memory that core sees is passed as a segment to the device.
so having multiple cpu support should be fine without having even to change the kernel part, you just have multiple vmx instances share a memory segment. however, to be practical, you'd need to add emulation code for the apic interrupt controller as well provide acpi or mp tables... reason is a core is started with a inter processor interrupt thru the apic. the kernel discoveres the apics thru eigther MP tables or ACPI tables. and the processor comes up in real-mode, which might have some limitations in what hardware will emulate for us so a interpreter might be needed. (tho i'm not fully sure on this) (note, right now vmx has no BIOS and it implements each OS bootloader itself so it starts executing the kernel in 32 bit mode directly). i dont see vmx causing kernel crashes for me. however, i think the author meant to express is lack of confidence in the air-tightiness of vmx giving the zillions of architectual registers you have to setup to contain a guest. it is easy to forget to set some bit and everything works until someone manages to exploit that. patches welcome. -- cinap ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Tc08115552282a0a2-M6ac623797c50743cf9de92ad Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
