Re: Enabling VIMAGE by default for FreeBSD 11?
... is it enabled by default on pcbsd? -a ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: Enabling VIMAGE by default for FreeBSD 11?
On Sat, Oct 11, 2014 at 11:15 PM, Adrian Chadd adr...@freebsd.org wrote: ... is it enabled by default on pcbsd? -a It was enabled in PCBSD here: https://github.com/trueos/trueos/commit/3108bbe003bc38339fbd4a26542b184b2ccb271a -- Craig ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: Enabling VIMAGE by default for FreeBSD 11?
Should also add here that for those using PF as a firewall that VIMAGE enabled kernels don't play to well together Unless you like looking at cores all day. -- Jason Hellenthal Mobile: +1 (616) 953-0176 jhellent...@dataix.net JJH48-ARIN On Oct 12, 2014, at 01:15, Adrian Chadd adr...@freebsd.org wrote: ... is it enabled by default on pcbsd? -a ___ freebsd-...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: Enabling VIMAGE by default for FreeBSD 11?
It was for a while in 9.2, but we removed it from 10.0 and later due to stability issues we kept getting reports about. Haven't tried it since then, dont know if those issues are fixed. On Oct 12, 2014, 2:15 AM, at 2:15 AM, Adrian Chadd adr...@freebsd.org wrote: ... is it enabled by default on pcbsd? -a ___ freebsd-a...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-arch To unsubscribe, send any mail to freebsd-arch-unsubscr...@freebsd.org ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: libvirt improvements for bhyve
Craig Rodrigues wrote: On Sat, Oct 11, 2014 at 11:05 AM, Roman Bogorodskiy no...@freebsd.org wrote: Frankly speaking, it's a hard topic for me and currently I don't have a complete idea how to design that. The thing I'm worried about is that as far as I understand that exit codes are sort of temporary solution and will be dropped in the future. Also, it seems the behaviour is changing already, e.g. IIRC on -CURRENT the bhyve proccess doesn't exit on reboots (unlike in 10-R). My goal is to support 10-R and I'm not sure how to probe if exit codes are available or not (and how to probe if e.g. if new exit code will be added in some future version). Any reason why you are stuck on 10-R? Unlike other parts of FreeBSD, bhyve is not mature, and is evolving over time. Serious users of bhyve are following CURRENT or 10-STABLE. 10-STABLE has the same error status codes as CURRENT, and 10.1-R is coming out in a few weeks. libvirt for bhyve is even less mature than bhyve itself, so tracking bhyve beyond the release should be OK, but it's up to you. Well, it's not an ultimate goal to support 10-R, but while it's not very painful, I think it's a nice thing to do. Also, it doesn't mean that I'm not adding features available only in -STABLE, I just want user to have a possibility to have a meaningful error messages if certain feature is not support. Also, I forgot to mention one more important issue with the exit code approach. Libvirt doesn't serve as a parent process for the bhyve processes. The reason for that is to allow libvirt restart without having to interrupt the VMs (that's useful for upgrades or e.g. libvirtd crash). I'm not sure how I could track exit codes in such case. IMHO, the good way to solve this problem is to introduce some sort of control socket on the bhyve side that could be used to query VM status and push events about its change. I've been wanting to implement a PoC for that for quite some time, but, unfortunately, haven't got to it yet. In its current form, my experience has been that bhyve and libvirt are unusable for serious work, based on the issues which I've described before for starting/stopping VM's. bhyve + custom scripting is the only way to go. I tried to use libvirt + bhyve for jenkins.freebsd.org, but found it unusable, even though Jenkins has libvirt support for starting VM's on demand. I backed away from libvirt, and ended up writing my own scripts. I am trying to convince some people to go with libvirt + bhyve for a simulation/testing system, but am having a hard time because of all the rough edges, and Linux + KVM + libvirt looks a lot more mature and easier to use. It's too bad, because I think if you can incorporate a few minor enhancements to libvirt for bhyve, it can definitely be a replacement for Linux + KVM + libvirt Neel, Peter, can you comment on the status exit codes from bhyve? Are those temporary, or will you keep them? There is no other way for external scripts to detect reset/poweroff. It looks like the confusion over this issue is blocking Roman from moving forward with libvirt. Thanks. -- Craig Roman Bogorodskiy pgpF0qdEbZyie.pgp Description: PGP signature
Re: no routing from new bhyve install
Answered my own question - the machine froze and rebooted. Now bhyve works as expected. Looks like it's as fast as bare metal, which is unexpected. -- John ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: Enabling VIMAGE by default for FreeBSD 11?
On 12 Oct 2014, at 16:25 , Yamagi Burmeister li...@yamagi.org wrote: Hello, it's been a while since I tested VIMAGE, but at the last time somewhere in 10-CURRENT some UMA memory leaks were left when destroying vnets. They weren't showstoppers for most workloads, but pretty anoying... Have those been fixed? No, an old perforce branch of mine had all but the last TCP ones fixed. The code is still there. — Bjoern A. Zeeb Come on. Learn, goddamn it., WarGames, 1983 ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: Enabling VIMAGE by default for FreeBSD 11?
On Sun, Oct 12, 2014 at 5:33 AM, Allan Jude allanj...@freebsd.org wrote: On 2014-10-12 07:28, Jason Hellenthal wrote: Should also add here that for those using PF as a firewall that VIMAGE enabled kernels don't play to well together Unless you like looking at cores all day. There have been patches to address this. I know Martin m...@freebsd.org had something, I was talking to him about it at AsiaBSDCon this spring. pf patches for vnet have been committed to this branch: https://svnweb.freebsd.org/base/projects/pf/head/ Some of the patches have been merged to HEAD such as this: https://svnweb.freebsd.org/base?view=revisionrevision=264689 -- Craig ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: Enabling VIMAGE by default for FreeBSD 11?
On 10/12/14, 1:55 PM, wishmaster wrote: --- Original message --- From: Alexander V. Chernikov melif...@ipfw.ru Date: 11 October 2014, 23:20:39 On 11 Oct 2014, at 21:58, Craig Rodrigues rodr...@freebsd.org wrote: Hi, What action items are left to enable VIMAGE by default for FreeBSD 11? Are there any tests results showing performance implications on different network-related workloads? the last time we teste things vnet made things faster. if you spread 100 sessions over N vnets and had 100 sessions on one system, then there are 1/N as many locking collisions as each vnet is its own locking domain. Julian ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
