Andreas Nilsson wrote: > On Sun, Sep 2, 2012 at 6:56 PM, Roman Bogorodskiy <no...@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.
Yes, reading from /dev is not very convenient, but appears that sysctl is not supported. I didn't read the code though, but I don't see anything looking like that in sysctl -a. Probably the most handy way of doing that is via 'vmmctl' or a tool like that. Anyways, I started spotting one more problem: I start a VM like that: sudo /usr/sbin/bhyveload -m 256 -M 0 -h /var/run/bhyve/test1/vm1 test1 sudo /usr/bin/cpuset -l 0-3 /usr/sbin/bhyve -m 256 -M 0 -s 1,virtio-net,tap0 test1 The last commands give me: Failed to emulate instruction at 0xffffffff80594f3a What could be wrong with that? Roman Bogorodskiy
pgpfM2RxGRdE6.pgp
Description: PGP signature