> Kernels from -current built after the merge hang like this with Intel VT-x
> active:
> ...
> cpu0 at mainbus0: (uniprocessor)
> cpu0: Intel Celeron (Mendocino) (686-class), 2660.28 MHz, id 0x665
> cpu0: "Intel(R) Xeon(R) CPU               5150  @ 2.66GHz"
> <hang>
> 
> A working boot of the same kernel (with Intel VT-x disabled) looks like
> this:
> ...
> mainbus0 (root)
> cpu0 at mainbus0: (uniprocessor)
> cpu0: Intel Celeron (Mendocino) (686-class), 2662.25 MHz, id 0x665
> cpu0: features f80b9b9<FPU,PSE,TSC,MSR,MCE,CX8,SEP,MTRR>
> cpu0: features f80b9b9<PGE,CMOV,MMX>
> cpu0: features f80b9b9<FXSR,SSE,SSE2,SS>
> cpu0: features2 1<SSE3>
> cpu0: "Intel(R) Xeon(R) CPU            5150  @ 2.66GHz"
> cpu0: I-cache 32 KB 64B/line 8-way, D-cache 32 KB 64B/line 8-way
> cpu0: L2 cache 4 MB 64B/line 16-way
> cpu0: ITLB 128 4 KB entries 4-way
> cpu0: 64 page colors
> pci0 at mainbus0 bus 0: configuration mode 1
> ...
> 
> Disabling largepages seems to fix this issue and allow it to boot and run
> properly.
> I've tried the different OS options under Parallels but they seem to just
> change what CPU is identified and have no effect on the hang.  I don't know
> if there is an easy way to recognize Parallels' virtual CPU, but we need
> that or a way to disable largepages.
> 
> This is on a Mac Pro with Parallels 2.5.  Can anyone else reproduce this?
> 
> -Andrew

do you know if other os (or older netbsd) can run with largepages
under parallels with vt-x enabled?

YAMAMOTO Takashi