On Fri, Oct 13, 2017 at 03:55:25AM +0700, Kamil Shakirov wrote:
> Hello Mike,
>
> Just wanted to update you that I can now successfully run Debian 9 x64 VM on
> recently released OpenBSD 6.2. All I did was fresh Debian install in Qemu,
> then configured serial console in grub settings.
>
> Tha
On Fri, Oct 13, 2017 at 03:55:25AM +0700, Kamil Shakirov wrote:
> Hello Mike,
>
> Just wanted to update you that I can now successfully run Debian 9 x64 VM on
> recently released OpenBSD 6.2. All I did was fresh Debian install in Qemu,
> then configured serial console in grub settings.
>
> Tha
Hello Mike,
Just wanted to update you that I can now successfully run Debian 9 x64 VM on
recently released OpenBSD 6.2. All I did was fresh Debian install in Qemu,
then configured serial console in grub settings.
Thank you for your work on vmm.
By the way, is it possible to allocate more than
On Fri, Sep 15, 2017 at 12:55:17AM +0700, Kamil Shakirov wrote:
> Hello Mike,
>
> I apologize for the late reply, I found this email in my spambox :(.
>
> After reporting this issue I had to move back to OpenBSD 6.1-stable where it
> works because I needed GNU/Linux VM for my development. I w
Hello Mike,
I apologize for the late reply, I found this email in my spambox :(.
After reporting this issue I had to move back to OpenBSD 6.1-stable where it
works because I needed GNU/Linux VM for my development. I will try again the
CURRENT next week and report back again.
Thanks!
> On
On Wed, Sep 13, 2017 at 11:56:22AM -0400, Dave Voutila wrote:
> Well this is embarrassing. Let's just say "console=ttyS0,115200" is
> not the same as "console=/dev/ttyS0,115200".
>
> Definitely user error. Sorry, Mike!
>
>
Heh, no problem. I've had a few of those myself.
On a related note, I d
Well this is embarrassing. Let's just say "console=ttyS0,115200" is
not the same as "console=/dev/ttyS0,115200".
Definitely user error. Sorry, Mike!
On Sun, Sep 10, 2017 at 10:22 AM, Dave Voutila wrote:
> Mike,
>
> Must be something specific to my machine as it's still not working for
> me. I t
Mike,
Must be something specific to my machine as it's still not working for
me. I tried an upgrade and then a completely fresh install of the
snapshot from yesterday. I still see the same behavior across
different Alpine flavors.
If I have some spare time this week I'll try to roll a custom Alpi
I'm away from that system for the next few days, but will be able to
try again this weekend.
I'll upgrade to the latest snapshot, grab the same exact Alpine iso,
and try using your vmctl parameters.
On Tue, Sep 5, 2017 at 12:46 AM, Mike Larkin wrote:
> On Tue, Sep 05, 2017 at 12:20:58AM -0700,
On Tue, Sep 05, 2017 at 12:20:58AM -0700, Mike Larkin wrote:
> On Sun, Sep 03, 2017 at 10:22:07PM -0700, Mike Larkin wrote:
> > On Sun, Sep 03, 2017 at 03:03:22PM -0400, Dave Voutila wrote:
> > > Decided to test using the "virt" Alpine build and it creates the error
> > > I alluded to but couldn't
On Sun, Sep 03, 2017 at 10:22:07PM -0700, Mike Larkin wrote:
> On Sun, Sep 03, 2017 at 03:03:22PM -0400, Dave Voutila wrote:
> > Decided to test using the "virt" Alpine build and it creates the error
> > I alluded to but couldn't remember. Login as root succeeds, but when
> > it tries to properly e
On Mon, Sep 04, 2017 at 05:53:15PM +0700, Kamil Shakirov wrote:
> Hello,
>
> I too have a problem with the recent VMM from OpenBSD-current. Few
> snapshots (weeks) ago I created a Linux VM installing Devuan amd64 using
> Qemu. Then configured this image to use serial port for booting and
> logi
Hello,
I too have a problem with the recent VMM from OpenBSD-current. Few
snapshots (weeks) ago I created a Linux VM installing Devuan amd64 using
Qemu. Then configured this image to use serial port for booting and
login. Then got it to run with vmctl(8) successfuly. Then configured sshd
and
On Sun, Sep 03, 2017 at 03:03:22PM -0400, Dave Voutila wrote:
> Decided to test using the "virt" Alpine build and it creates the error
> I alluded to but couldn't remember. Login as root succeeds, but when
> it tries to properly exec busybox's ash process it errors out with:
>
> -ash: can't access
Mike,
Thanks for the reply.
Unfortunately, this is during the initial Alpine iso boot _before_ a
new user is created. Hence root is the only user in existance during
login per their installation instructions (per
https://wiki.alpinelinux.org/wiki/Installation).
I dug a little further and found t
Decided to test using the "virt" Alpine build and it creates the error
I alluded to but couldn't remember. Login as root succeeds, but when
it tries to properly exec busybox's ash process it errors out with:
-ash: can't access tty; job control turned off
Still results in writing the prompt, but a
On Sun, Sep 03, 2017 at 12:41:31PM -0400, Dave Voutila wrote:
> Hi misc@,
>
> I'm using the latest AMD64 snapshot from 2017-09-02 and can no longer
> log into an Alpine Linux VM. (This was working with a previous
> snapshot from a few days ago.)
>
> Currently I'm using the "vanilla" image from
>
Hi misc@,
I'm using the latest AMD64 snapshot from 2017-09-02 and can no longer
log into an Alpine Linux VM. (This was working with a previous
snapshot from a few days ago.)
Currently I'm using the "vanilla" image from
https://www.alpinelinux.org/downloads/
I've removed any presence of /etc/vm.c
18 matches
Mail list logo
