On Thu, Oct 27, 2016 at 11:02:12AM -0500, Ax0n wrote:
> To circle back: I can reproduce the VM lock-up 100% of the time by typing
> too quickly into the VM virtual serial console, such as my password and
> longer command strings that I know by muscle memory.
>
> I tried a few things such as
To circle back: I can reproduce the VM lock-up 100% of the time by typing
too quickly into the VM virtual serial console, such as my password and
longer command strings that I know by muscle memory.
I tried a few things such as slowly typing several kilobytes of text into
the console, one
On Wed, Oct 26, 2016 at 06:36:25PM -0500, Ax0n wrote:
> I'm running vmd with the options you specified, and using tee(1) to peel it
> off to a file while I can still watch what happens in the foreground. It
> hasn't happened again yet, but I haven't been messing with the VMs as much
> this week as
I'm running vmd with the options you specified, and using tee(1) to peel it
off to a file while I can still watch what happens in the foreground. It
hasn't happened again yet, but I haven't been messing with the VMs as much
this week as I was over the weekend.
One thing of interest: inside the VM
On Mon, Oct 24, 2016 at 11:07:32PM -0500, Ax0n wrote:
> Thanks for the update, ml.
>
> The VM Just did it again in the middle of backspacing over uname -a...
>
> $ uname -a
> OpenBSD vmmbsd.labs.h-i-r.net 6.0 GENERIC.MP#0 amd64
> $ un <-- frozen
>
> Spinning like mad.
>
Bizarre. If it were
Thanks for the update, ml.
The VM Just did it again in the middle of backspacing over uname -a...
$ uname -a
OpenBSD vmmbsd.labs.h-i-r.net 6.0 GENERIC.MP#0 amd64
$ un <-- frozen
Spinning like mad.
[axon@transient ~]$ vmctl status
ID PID VCPUSMAXMEMCURMEM TTY NAME
On Mon, Oct 24, 2016 at 07:36:48PM -0500, Ax0n wrote:
> I suppose I'll ask here since it seems on-topic for this thread. Let me
> know if I shouldn't do this in the future. I've been testing vmm for
> exactly a week on two different snapshots. I have two VMs: One running the
> same snapshot
I suppose I'll ask here since it seems on-topic for this thread. Let me
know if I shouldn't do this in the future. I've been testing vmm for
exactly a week on two different snapshots. I have two VMs: One running the
same snapshot (amd64, Oct 22) I'm running on the host vm, the other running
amd64
Hey @Peter, one more time thank so much for the heads up :)
For those that interest.
I'm running OpenBSD-Current under VMware-Workstation 12 ( just need to set
processor proprieties to virtualize intel VT-x/EPT or AMD-V/RVI )
And have fun to test VMD
:)
Thank you
2016-10-22 8:43
Hey Peter ,
Thank you for the advice, I'll get current
Cheers dude !
(:
2016-10-22 6:44 GMT-02:00 Peter Hessler :
> This isn't expected to work at all. That is why it was disabled.
> You'll need to upgrade the Hypervisor to -current, or to 6.1 when it is
> released.
>
>
This isn't expected to work at all. That is why it was disabled.
You'll need to upgrade the Hypervisor to -current, or to 6.1 when it is
released.
On 2016 Oct 22 (Sat) at 00:06:08 -0200 (-0200), R0me0 *** wrote:
:Hello misc.
:
:For testing purposes
:
:I compiled kernel with vmd support.
:
Hello misc.
For testing purposes
I compiled kernel with vmd support.
After start the vm -> vmctl start "myvm" -m 512M -i 1 -d disk.img -k /bsd.rd
I created a bridge and added vether0 and tap0
In the vm I have configured an ip 192.168.1.30
If I perform ping from OpenBSD Hypervisor -> ping
12 matches
Mail list logo