Re: vmctl send

On Fri, Oct 25, 2024 at 09:12:04AM +0200, Holger Glaess wrote: > hi > > > if id do an > > vmctl -v send vpngw  | ssh bellab vmctl receive vpngw > > > i got an > > bellab vmd[18629]: denied request 19 from uid 107 > > on the receiving system. > > the _

vmctl send

hi if id do an vmctl -v send vpngw  | ssh bellab vmctl receive vpngw i got an bellab vmd[18629]: denied request 19 from uid 107 on the receiving system. the _vmd user is changed that he have an shell and an home dir where the vm image are stored. the vm.conf part on both machines are

Re: vmctl start: vm command failed: Operation already in progress (no one VM run in the same time)

> Martin martin...@protonmail.com writes: > > > Try to start VM from previously (<6.9) working command as below: > > $ doas /usr/sbin/vmctl start -m 8G -c -n vmlan -d /path/to/vm.qcow2 vm > > Now I have trouble with it on 6.9amd64 with 1-5 patches installed. > > $ doa

vmctl start: vm command failed: Operation already in progress (no one VM run in the same time)

Hi list, Try to start VM from previously (<6.9) working command as below: $ doas /usr/sbin/vmctl start -m 8G -c -n vmlan -d /path/to/vm.qcow2 vm Now I have trouble with it on 6.9amd64 with 1-5 patches installed. $ doas rcctl status vmd vmd(ok) command above returns: vmctl start: vm comm

Re: vmctl start: vm command failed: Operation already in progress (no one VM run in the same time)

Martin writes: > Try to start VM from previously (<6.9) working command as below: > > $ doas /usr/sbin/vmctl start -m 8G -c -n vmlan -d /path/to/vm.qcow2 vm > > Now I have trouble with it on 6.9amd64 with 1-5 patches installed. > > $ doas rcctl status vmd > vmd(ok

VMM: crashing BIOS "hangs" vmctl start -c / cu

Hi, just a head's up / for the archives. Do more important things first :) While testing my packer-vmm port "across the board", I just noticed that bsd.rd older 5.7 will just hang in 'vmctl start -c' for.. forever? Dec 9 12:24:12 ssfnhv011 vmd[48696]: myvm: starte

Re: vmctl / vmd

On Sun, Aug 12, 2018 at 4:53 AM Stuart Henderson wrote: > > On 2018-08-11, Mike Larkin wrote: > > On Fri, Aug 10, 2018 at 04:14:28PM -0400, sven falempin wrote: > >> Dear readers, > >> > >> I just installed / syspatch a fresh 6.3 and i was not able to get the > >> network working > >> inside the

Re: vmctl / vmd

On 2018-08-11, Mike Larkin wrote: > On Fri, Aug 10, 2018 at 04:14:28PM -0400, sven falempin wrote: >> Dear readers, >> >> I just installed / syspatch a fresh 6.3 and i was not able to get the >> network working >> inside the alpine-virt-3.8.0-x86_64.iso kernel . >> >> I tried -L ( witch create a

Re: vmctl / vmd

On Fri, Aug 10, 2018 at 04:14:28PM -0400, sven falempin wrote: > Dear readers, > > I just installed / syspatch a fresh 6.3 and i was not able to get the > network working > inside the alpine-virt-3.8.0-x86_64.iso kernel . > > I tried -L ( witch create a TAP with 100.64.id network :S ), and -n > a

vmctl / vmd

Dear readers, I just installed / syspatch a fresh 6.3 and i was not able to get the network working inside the alpine-virt-3.8.0-x86_64.iso kernel . I tried -L ( witch create a TAP with 100.64.id network :S ), and -n and -i with manual bridge setup. I see packets going through and arp replies b

Re: vmctl and 6.3/testing

On Tue, Mar 27, 2018 at 03:56:53PM -0400, sven falempin wrote: > Readers, > > I was able to setup a 6.3 openbsd inside a vmd (neat) > but i had to use '-b /bsd.rd' because '-d install63.fs' > always crashed inside the guest kernel at 'mount'. > > Now testing snapshots inside snapshots. > > Feels

vmctl and 6.3/testing

Readers, I was able to setup a 6.3 openbsd inside a vmd (neat) but i had to use '-b /bsd.rd' because '-d install63.fs' always crashed inside the guest kernel at 'mount'. Now testing snapshots inside snapshots. Feels good man. -- -- --

Another vmd sanity check recommendation / WAS: "vmctl stop" causing disk image corruption with OpenBSD 6.2-stable VM

g' Subject: Re: "vmctl stop" causing disk image corruption with OpenBSD 6.2-stable VM ... > May I suggest a vmd sanity check to avoid a VM disk image being loaded by > more than one VM simultaneously? Providing a patch is outside my skill set, > unfortunately. > >

Re: vmctl

On Sun, Feb 25, 2018 at 09:12:24PM -0300, Friedrich Locke wrote: > Is openbsd vm a container ? > > Thanks for explanation. > > > Livre > de vírus. www.avast.com >

vmctl

Is openbsd vm a container ? Thanks for explanation. Livre de vírus. www.avast.com

Re: vmctl status shows vm as stopped although running

debian within vmd and this works quite well right now. Now I noticed, that vmctl status shows the vm as STOPPED, although it is running. I can connect to the console without problems. Is this status showing some "other" status? Thanks. Robert An OS can spent a large amount of time &quo

Re: vmctl status shows vm as stopped although running

esting running debian within vmd and > > > this works quite well right now. > > > > > > Now I noticed, that vmctl status shows the vm as STOPPED, although it is > > > running. > > > > > > I can connect to the console without pro

Re: vmctl status shows vm as stopped although running

On Mon, Feb 19, 2018 at 11:12:52AM -0800, Mike Larkin wrote: > On Mon, Feb 19, 2018 at 02:40:47PM +0100, Robert Paschedag wrote: > > Hi misc, > > > > I am running STABLE and just started testing running debian within vmd and > > this works quite well right now. > &g

Re: vmctl status shows vm as stopped although running

On Mon, Feb 19, 2018 at 02:40:47PM +0100, Robert Paschedag wrote: > Hi misc, > > I am running STABLE and just started testing running debian within vmd and > this works quite well right now. > > Now I noticed, that vmctl status shows the vm as STOPPED, although it is >

Re: vmctl status shows vm as stopped although running

On 02/19/18 15:23, Carlos Cardenas wrote: On Mon, Feb 19, 2018 at 02:40:47PM +0100, Robert Paschedag wrote: Hi misc, I am running STABLE and just started testing running debian within vmd and this works quite well right now. Now I noticed, that vmctl status shows the vm as STOPPED, although

Re: vmctl status shows vm as stopped although running

On Mon, Feb 19, 2018 at 02:40:47PM +0100, Robert Paschedag wrote: > Hi misc, > > I am running STABLE and just started testing running debian within vmd and > this works quite well right now. > > Now I noticed, that vmctl status shows the vm as STOPPED, although it is >

vmctl status shows vm as stopped although running

Hi misc, I am running STABLE and just started testing running debian within vmd and this works quite well right now. Now I noticed, that vmctl status shows the vm as STOPPED, although it is running. I can connect to the console without problems. Is this status showing some "other&qu

Re: vmctl status - output order

On 2018-02-17, Jiri B wrote: > I can't read C but how do you sort vmctl status output? > > host1# vmctl status >ID PID VCPUS MAXMEM CURMEM TTYOWNER NAME > 6 99046 12.0G698M ttyp4jirib build1 > 1 93692 12.0G91

vmctl status - output order

I can't read C but how do you sort vmctl status output? host1# vmctl status ID PID VCPUS MAXMEM CURMEM TTYOWNER NAME 6 99046 12.0G698M ttyp4jirib build1 1 93692 12.0G917M ttyp7jirib jirib1 7 - 1

Re: "vmctl stop" causing disk image corruption with OpenBSD 6.2-stable VM

> unfortunately. > > > Yours truly, > > > Breen > Not a bad idea, I'll toss it on the to-do list. thanks.. -ml > > > From: Mike Larkin > Sent: February 1, 2018 10:21 PM > To: openbsd2012 > Cc: misc@openbsd.org

Re: "vmctl stop" causing disk image corruption with OpenBSD 6.2-stable VM

Subject: Re: "vmctl stop" causing disk image corruption with OpenBSD 6.2-stable VM On Fri, Feb 02, 2018 at 05:36:16AM +, openbsd2012 wrote: > I've been testing out vmd with a single OpenBSD VM for about a week. > > > Running "vmctl stop 1" from the vmd

Re: "vmctl stop" causing disk image corruption with OpenBSD 6.2-stable VM

On Fri, Feb 02, 2018 at 05:36:16AM +, openbsd2012 wrote: > I've been testing out vmd with a single OpenBSD VM for about a week. > > > Running "vmctl stop 1" from the vmd host often causes the VM on reboot to > output "WARNING: / was not properly unmou

"vmctl stop" causing disk image corruption with OpenBSD 6.2-stable VM

I've been testing out vmd with a single OpenBSD VM for about a week. Running "vmctl stop 1" from the vmd host often causes the VM on reboot to output "WARNING: / was not properly unmounted", or in some cases the VM will loop infinitely at the boot prompt. I can avoid

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

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 > >> On 07/22/17 20:54

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

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 following messages

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

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 the

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

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 dm

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

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 to

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

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

tart vmd 2. Run vmd manually. Per the vmd(8) man page, you may add -v one or more times for additional information. # vmd -v > On 07/22/17 20:03, Josh Grosse wrote: > > On Sat, Jul 22, 2017 at 07:30:19PM +0300, G wrote: > >> Hello. > >> Im following vmct

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

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

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

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 f

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

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? Thanks in advance for your help. ps. Im running openbsd 6.1 stable