Post by Deepak ChawlaAlso, is there a way to mount the plan9 internal partitions (9fat, fossil
etc) on Linux?
if you just want to rescue your plan9.ini, then boot the cd in that image
and edit it directly. you can toss in new kernels that way, too.
if you get one kernel limping along in one vm and set up a nat for your
vms, you can pxe boot test kernels. it makes life quite a bit nicer.
i know that this works for vmware fusion. should probablly work for
workstation, too.
Post by Deepak ChawlaI tried *nomp=0, but still only saw one CPU. I removed the line altogether,
now the kernel panics (see attachment). Any way to override the kernel
params in plan9.ini?
it appears that the lapic clock is reasonable, but what is not reasonable is the
cpu clock is 1/10th the frequency printed on the cpu0 line.
i think this may be because the emulation is confusing the 8253
timing. if this is true, then the solution is to change this line
archmp.c:79: if(cpuserver && m->havetsc)
to remove the cpu server bit. i removed this test from 9atom kernels,
since i didn't understand how the distinction could be helpful, and
it seemed like the seed of a very long debugging session starting with
the puzzle "why does the cpu kernel work on this hardware, but the
terminal not?"
- erik