Re: vmctl: connect: /var/run/vmd.sock: No such file or directory

2017-07-23 Thread G
I changed BIOS settings and it worked :-) On 07/23/17 15:54, Alexander Hall wrote: > > > On July 22, 2017 8:42:48 PM GMT+02:00, G wrote: >> thanks! it worked! > > > It could be of public interest exactly *what* worked. Hardware change? BIOS > settings? > > /Alexander >

Re: vmctl: connect: /var/run/vmd.sock: No such file or directory

2017-07-23 Thread Alexander Hall
On July 22, 2017 8:42:48 PM GMT+02:00, G wrote: >thanks! it worked! It could be of public interest exactly *what* worked. Hardware change? BIOS settings? /Alexander >On 07/22/17 20:54, Josh Grosse wrote: >> On Sat, Jul 22, 2017 at 08:38:56PM +0300, G wrote: >>> I get the

Re: vmctl: connect: /var/run/vmd.sock: No such file or directory

2017-07-22 Thread G
thanks! it worked! On 07/22/17 20:54, Josh Grosse wrote: > On Sat, Jul 22, 2017 at 08:38:56PM +0300, G wrote: >> I get the following messages >> >> # vmd -vd >> vmd: /dev/vmm: Operation not supported by device > > The vmm(4) driver requires hardware virtualization features, and if you > have

Re: vmctl: connect: /var/run/vmd.sock: No such file or directory

2017-07-22 Thread Josh Grosse
On Sat, Jul 22, 2017 at 08:38:56PM +0300, G wrote: > I get the following messages > > # vmd -vd > vmd: /dev/vmm: Operation not supported by device The vmm(4) driver requires hardware virtualization features, and if you have the right hardware, may require you to enable them in your BIOS. Your

Re: vmctl: connect: /var/run/vmd.sock: No such file or directory

2017-07-22 Thread G
I get the following messages # vmd -vd vmd: /dev/vmm: Operation not supported by device On 07/22/17 20:24, Josh Grosse wrote: > On Sat, Jul 22, 2017 at 01:21:33PM -0400, I wrote: > >> # vmd -v > > I'd like to correct this. Add -d to prevent running in the background, > and log output

Re: vmctl: connect: /var/run/vmd.sock: No such file or directory

2017-07-22 Thread Josh Grosse
On Sat, Jul 22, 2017 at 01:21:33PM -0400, I wrote: > # vmd -v I'd like to correct this. Add -d to prevent running in the background, and log output to stderr. # vmd -dv

Re: vmctl: connect: /var/run/vmd.sock: No such file or directory

2017-07-22 Thread Josh Grosse
On Sat, Jul 22, 2017 at 08:13:03PM +0300, G wrote: > I already enable vmd. I though enable vmd was enough > I haven't run rcctl start vmd but when I tried it I get > # rcctl start vmd > vmd(failed) Pick an option: 1. Re-run rcctl with debugging output: # rcctl -d start vmd 2. Run

Re: vmctl: connect: /var/run/vmd.sock: No such file or directory

2017-07-22 Thread G
I already enable vmd. I though enable vmd was enough I haven't run rcctl start vmd but when I tried it I get # rcctl start vmd vmd(failed) On 07/22/17 20:03, Josh Grosse wrote: > On Sat, Jul 22, 2017 at 07:30:19PM +0300, G wrote: >> Hello. >> Im following vmctl manual and i get. >> >> # vmctl

Re: vmctl: connect: /var/run/vmd.sock: No such file or directory

2017-07-22 Thread Josh Grosse
On Sat, Jul 22, 2017 at 07:30:19PM +0300, G wrote: > Hello. > Im following vmctl manual and i get. > > # vmctl create disk.img -s 4.5G > vmctl: imagefile created > # vmctl start "myvm" -m 1G -i 1 -b /bsd -d disk.img > vmctl: connect: /var/run/vmd.sock: No such file or directory > > Any ideas?