BHyVe: vm_setup_memory(highmem): Cannot allocate memory

[Andreas Nilsson]

On Sun, Sep 2, 2012 at 6:56 PM, Roman Bogorodskiy <novel at freebsd.org> wrote:

>   Roman Bogorodskiy wrote:
>
> >   Peter Grehan wrote:
> >
> > > Hi Roman,
> > >
> > > > Yeah, but I'd like to leave more memory for the host system, so I
> > > > specified 6GB. I have 8GB at all, so 2GB left for VMs.
> > > > Should it cause any problems?
> > >
> > >   No, that should be fine.
> > >
> > > > BTW, I encountered a problem with the tap0 device. I create a tap
> device
> > > > and assign an address to it, using 'ifconfig tap0 192.168.1.1 up'.
> > > >
> > > > I boot a VM and everything goes fine. When I do 'reboot' in the
> guest,
> > > > it reboots, but tap0 on the host goes down and its address is
> dropped.
> > > > Is that an expected behaviour?
> > >
> > >   Yes - we probably need to fix the tap device to not do that :(
> >
> > Yeah, it would be great to get this fixed.
> >
> > And one question: is there a way to get a list of all running VMs on the
> > host? Doesn't seem like vmmctl being able to do that.
>
> Oh, I've started reading the code and figured out that I can just do
> `ls /dev/vmm`!
>
> Roman Bogorodskiy
>

IMHO: Please don't introduce "reading stuff in /dev" as a standard way to
get info ( at least not for end user). sysctl is so much nicer to work with.

Regards
Andreas