Not sure whether this is useful, but here it goes:
typo: "chosen"
consistency: 'z' instead of 's' (seems to be used in the rest too)
cosmetics: space at end of line.
Index: m4.common
===
RCS file:
On Sat, Oct 15, 2016 at 05:11:49PM +0100, Edd Barrett wrote:
> Hi,
>
> Here's an intial stab at a FAQ entry for vmm.
>
> It covers two common setups:
> * a vmm guest with network access via the host's wired network
> * a vmm guest with network access via the host's wireless network
>
>
On Sat, Oct 15, 2016 at 09:55:05AM +0200, s...@openbsd.org wrote:
>
>
> On Fri, 14 Oct 2016, Mike Larkin wrote:
>
> > On Fri, Oct 14, 2016 at 04:49:31PM +0900, YASUOKA Masahiko wrote:
> > > Hi,
> > >
> > > I'm working on NEC Express5800/R110h-1 (dmesg is attached). On this
> > > machine, our
Hi,
Here's an intial stab at a FAQ entry for vmm.
It covers two common setups:
* a vmm guest with network access via the host's wired network
* a vmm guest with network access via the host's wireless network
Please critique. Once we have the details right, I can run it past tj.
Some other
Here's a different approach that doesn't involve the ugly branching
depending on id -u.
When Theo and I discussed the problem, we concluded that the order of
cleandir: and includes: is wrong during make build. Swapping them
results in a list of 28 root-owned files in /usr/obj/:
On Sat, Oct 15, 2016 at 09:25:43AM -0600, Aaron Bieber wrote:
> Hola,
>
> I have been running into some issues getting vmm to start up vms. It
> had been previously working (yes it's enabled in bios, I have even
> tried disabling and re-enabling a few times).
>
> I started seeing the 'failed to
Hola,
I have been running into some issues getting vmm to start up vms. It
had been previously working (yes it's enabled in bios, I have even
tried disabling and re-enabling a few times).
I started seeing the 'failed to enter VMM mode' about every other
reboot but now it happens all the time.
On Fri, 14 Oct 2016, Mike Larkin wrote:
> On Fri, Oct 14, 2016 at 04:49:31PM +0900, YASUOKA Masahiko wrote:
> > Hi,
> >
> > I'm working on NEC Express5800/R110h-1 (dmesg is attached). On this
> > machine, our kernel panics with following message.
> >
> > cpu0 at mainbus0panic: cpu at apic