On Thu, Nov 26, 2015 at 06:31:34PM +0100, Norman Golisz wrote:
> On Thu Nov 26 2015 15:11, Karel Gardas wrote:
> > Not sure, but on misc you can search for "vmm uvm_fault in vmware
> > player/workstation when Intel VT/AMD-v not enabled" thread from which
> > it looks like vmm requires extended-page
On Thu Nov 26 2015 15:11, Karel Gardas wrote:
> Not sure, but on misc you can search for "vmm uvm_fault in vmware
> player/workstation when Intel VT/AMD-v not enabled" thread from which
> it looks like vmm requires extended-page tables virtualization
> feature.
Looks like this could indeed be rela
Not sure, but on misc you can search for "vmm uvm_fault in vmware
player/workstation when Intel VT/AMD-v not enabled" thread from which
it looks like vmm requires extended-page tables virtualization
feature. Certainly this is not presented on my T500 so I would guess
it's neither on your T400. Plea
On Wed Nov 25 2015 22:00, Gregor Best wrote:
> on amd64 with a snapshot from today, I'm getting (transcribed):
>
> kernel: page fault trap, code=0
> ddb{1}> trace
> vm_writepage() at vm_writepage+0x158
> VOP_IOCTL() at VOP_IOCTL+0x44
> vn_ioctl() at vn_ioctl+0x77
>
Hi Mike,
on amd64 with a snapshot from today, I'm getting (transcribed):
kernel: page fault trap, code=0
ddb{1}> trace
vm_writepage() at vm_writepage+0x158
VOP_IOCTL() at VOP_IOCTL+0x44
vn_ioctl() at vn_ioctl+0x77
sys_ioctl() at sys_ioctl+0x196
An early rough cut of the vmm subsystem is now in the tree. This includes both
the kernel parts and userland parts.
There are still lots of things that need to be fixed and improved. For this
reason, it is still disabled by default.
But there is enough there for people to start playing with runni
