Re: can't get vmd to work on current

2016-09-08 Thread Alexander Hall
On September 8, 2016 11:34:48 AM GMT+02:00, "Mart Tõnso" wrote: >> True. If it was merely GENERIC[.MP] with vmm enabled, then fine. But >a >> kernel named "TIMMU" could deserve some explanation as to what's been >> done to it. > >That's why I included the config in the first email, but I see where

Re: can't get vmd to work on current

2016-09-08 Thread Mart Tõnso
> True. If it was merely GENERIC[.MP] with vmm enabled, then fine. But a > kernel named "TIMMU" could deserve some explanation as to what's been > done to it. That's why I included the config in the first email, but I see where the confusion arises. Since VMM is not enabled by default and changing

Re: can't get vmd to work on current

2016-09-07 Thread Alexander Hall
On Wed, Sep 07, 2016 at 07:07:01PM +0300, Mart Tõnso wrote: > >> OpenBSD 6.0-current (TIMMU) #4: Wed Sep 7 00:35:13 EEST 2016 > > > > Not going to help with custom kernels. Work on -current on real > > Only reason that I'm using a custom kernel is to enable vmm, so this > is a catch 22. True. If

Re: can't get vmd to work on current

2016-09-07 Thread Mart Tõnso
>> OpenBSD 6.0-current (TIMMU) #4: Wed Sep 7 00:35:13 EEST 2016 > > Not going to help with custom kernels. Work on -current on real Only reason that I'm using a custom kernel is to enable vmm, so this is a catch 22. > hardware with a standard kernel if you want to play with vmm please. Hm, yes,

Re: can't get vmd to work on current

2016-09-07 Thread David Coppa
Il 7 settembre 2016 20:43:47 CEST, "Mart Tõnso" ha scritto: >Hello, > >I'm trying to get vmd working, but am failing so far. > >What I've done: > >Custom kernel config to enable vmm: > >include "arch/amd64/conf/GENERIC" > >option MULTIPROCESSOR >#option MP_LOCKDEBUG > >cpu*at mainbus?

Re: can't get vmd to work on current

2016-09-07 Thread Mike Larkin
On Wed, Sep 07, 2016 at 09:55:17PM +0300, Mart T??nso wrote: > Pardon me, dmesg follows. This is inside a Virtualbox VM for "testing > purposes". vmm at mainbus0 not configured Whatever you're trying to do on your host, it's not passing through VT-x features. > > OpenBSD 6.0-current (TIMMU) #4:

Re: can't get vmd to work on current

2016-09-07 Thread Mart Tõnso
Pardon me, dmesg follows. This is inside a Virtualbox VM for "testing purposes". OpenBSD 6.0-current (TIMMU) #4: Wed Sep 7 00:35:13 EEST 2016 r...@bsd1.lan:/usr/src/sys/arch/amd64/compile/TIMMU real mem = 1056899072 (1007MB) avail mem = 1020399616 (973MB) mpath0 at root scsibus0 at mpath0: 25

Re: can't get vmd to work on current

2016-09-07 Thread Mike Larkin
On Wed, Sep 07, 2016 at 09:43:47PM +0300, Mart T??nso wrote: > Hello, > > I'm trying to get vmd working, but am failing so far. > > What I've done: > > Custom kernel config to enable vmm: > > include "arch/amd64/conf/GENERIC" > > option MULTIPROCESSOR > #option MP_LOCKDEBUG > > cpu*

can't get vmd to work on current

2016-09-07 Thread Mart Tõnso
Hello, I'm trying to get vmd working, but am failing so far. What I've done: Custom kernel config to enable vmm: include "arch/amd64/conf/GENERIC" option MULTIPROCESSOR #option MP_LOCKDEBUG cpu*at mainbus? # enable vmm vmm0 at mainbus0 # EOF /etc/vm.conf: # vm.conf sets="/va