> 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 unt
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
In the man pages for VMX, it states under "bugs":
Currently only one core is supported.
Does anyone know why this is? The inclusion of this under "bugs" alongside the
tendency to crash the kernel makes me think that VMX was originally intended to
be able to leverage multiple cores and
