Re: Enabling VIMAGE by default for FreeBSD 11?
On 10/17/14, 1:43 PM, vijju.singh wrote: We've seen issues with vnet delete causing stale pointers in mbufs referencing the per-vnet loopback interface (deleted with the vnet). you can also see this sort of problem with removable devices. e.g. USB network interfaces, so it's not unique to vnet. Sent via the Samsung GALAXY S®4, an AT&T 4G LTE smartphone Original message From: Dag-Erling Smørgrav Date:10/16/2014 10:39 AM (GMT-08:00) To: "Bjoern A. Zeeb" Cc: freebsd-...@freebsd.org,freebsd-virtualization@freebsd.org,freebsd-arch Subject: Re: Enabling VIMAGE by default for FreeBSD 11? "Bjoern A. Zeeb" writes: Dag-Erling Smørgrav writes: There are other serious issues with our current pf (checksum corruption) which I think can only be resolved by importing a newer version. Sorry, but you lost context. I was talking about security implications in VIMAGE context, not about random bugs. I realize that, but you're talking about patching our current pf, and I think that's a waste of time; we should import a newer version instead (which I assume already has those patches). DES ___ 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?
We've seen issues with vnet delete causing stale pointers in mbufs referencing the per-vnet loopback interface (deleted with the vnet). Sent via the Samsung GALAXY S®4, an AT&T 4G LTE smartphone Original message From: Dag-Erling Smørgrav Date:10/16/2014 10:39 AM (GMT-08:00) To: "Bjoern A. Zeeb" Cc: freebsd-...@freebsd.org,freebsd-virtualization@freebsd.org,freebsd-arch Subject: Re: Enabling VIMAGE by default for FreeBSD 11? "Bjoern A. Zeeb" writes: > Dag-Erling Smørgrav writes: > > There are other serious issues with our current pf (checksum > > corruption) which I think can only be resolved by importing a newer > > version. > Sorry, but you lost context. I was talking about security > implications in VIMAGE context, not about random bugs. I realize that, but you're talking about patching our current pf, and I think that's a waste of time; we should import a newer version instead (which I assume already has those patches). DES -- Dag-Erling Smørgrav - d...@des.no ___ 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: Enabling VIMAGE by default for FreeBSD 11?
On Sat, Oct 11, 2014 at 11:15 PM, Adrian Chadd wrote: > ... is it enabled by default on pcbsd? > Kris has answered the question about pcbsd and VIMAGE. As an additional datapoint, I would like to point out that VIMAGE has been enabled in FreeNAS for some time: https://github.com/freenas/freenas/blob/master/build/nanobsd-cfg/FREENAS.amd64 -- 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: convert .vmdk files
On 10/16/14 09:51, Pete Wright wrote: > > > On 10/15/14 23:09, Benjamin Connelly wrote: >>> qemu-img convert -f vmdk -O raw foo.vmdk foo.img >> >> Thank you! >> I've been struggling to get a 9.1 system running on bhyve (do to lack of >> virtio drivers in -RELEASE ISO's) and this enabled me to install 9.1 on >> VirtualBox, add the virtio kernel modules from ports, tweak configs, and >> qemu-img convert the .vdi file to a raw .img for bhyve! >> > > > oh that's great - glad i could help :) > > I realized after sending my last message that the wiki.freebsd.org/bhyve > page is immutable under my account and i am unable to add content to it > (i'm not in the ContributorsGroup on the wiki) so if someone wouldn't > mind adding me to that group or point me in the right direction to do so > that'd be great! > I have been granted contributor access to the wiki and have updated the FAQ section. Thanks everyone for helping me sort that out. Cheers, -pete -- Pete Wright p...@nomadlogic.org twitter => @nomadlogicLA ___ 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: HEADS UP: Merging projects/bhyve_svm to HEAD
I’ve applied Neel’s patch against r273182 and am currently abusively testing it on a mix of HP DL385s w/ dual Opteron 6378SE, & Single socket AMD G34s ( some with Opteron 6200s, some with 6300s ), about 15 boxes in total - so far so good. Seriously awesome work Gentlemen. cheers, -bp > On Oct 15, 2014, at 8:30 PM, Matthew Grooms wrote: > > Fantastic news! Greatly appreciated. > > -Matthew > > On Oct 15, 2014 10:00 PM, Anish Gupta wrote: >> >> Hi all, >> >> The projects/bhyve_svm branch is ready to be merged to HEAD. >> >> This branch contains patches to bhyve to enable it to work on AMD >> processors with SVM/AMD-V hardware extensions[1]. Pretty much any AMD >> processor since 2010 will have the features required by bhyve. >> >> bhyve on AMD supports (almost) all the features available with Intel >> [2]. All guest OSes supported on Intel are supported on AMD. All the >> bhyve-related utilities function similarly on both Intel and AMD >> platforms [3]. >> >> The patch against HEAD revision 273066 is available for review and testing: >> https://people.freebsd.org/~neel/bhyve/bhyve_svm.diff [Neel’s web directory] >> >> [1]: http://en.wikipedia.org/wiki/X86_virtualization >> [2]: bhyve doesn't support PCI passthru on AMD at this time >> [3]: bhyvectl has grown some processor-specific options >> >> Thanks and regards, >> Peter, Neel & Anish[akgu...@gmail.com] >> ___ >> 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" > ___ > 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" ___ 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[2]: Enabling VIMAGE by default for FreeBSD 11?
--- Original message --- From: "Dag-Erling Smørgrav" Date: 16 October 2014, 20:39:22 > "Bjoern A. Zeeb" writes: > > Dag-Erling Smørgrav writes: > > > There are other serious issues with our current pf (checksum > > > corruption) which I think can only be resolved by importing a newer > > > version. > > Sorry, but you lost context. I was talking about security > > implications in VIMAGE context, not about random bugs. > > I realize that, but you're talking about patching our current pf, and I > think that's a waste of time; we should import a newer version instead > (which I assume already has those patches). > Forget about importing new version of PF from OS, which doesn't has virtualized inet stack. Cheers, w ___ 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?
"Bjoern A. Zeeb" writes: > Dag-Erling Smørgrav writes: > > There are other serious issues with our current pf (checksum > > corruption) which I think can only be resolved by importing a newer > > version. > Sorry, but you lost context. I was talking about security > implications in VIMAGE context, not about random bugs. I realize that, but you're talking about patching our current pf, and I think that's a waste of time; we should import a newer version instead (which I assume already has those patches). DES -- Dag-Erling Smørgrav - d...@des.no ___ 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 10:58 AM, Craig Rodrigues wrote: > Hi, > > What action items are left to enable VIMAGE by default for FreeBSD 11? > > Not everyone uses bhyve, so VIMAGE is quite useful when using jails. > > Based on the discussion in this thread, I started writing down a list of action items before enabling VIMAGE by default: https://wiki.freebsd.org/VIMAGE/TODO Does that look reasonable? -- 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: convert .vmdk files
On 10/15/14 23:09, Benjamin Connelly wrote: >> qemu-img convert -f vmdk -O raw foo.vmdk foo.img > > Thank you! > I've been struggling to get a 9.1 system running on bhyve (do to lack of > virtio drivers in -RELEASE ISO's) and this enabled me to install 9.1 on > VirtualBox, add the virtio kernel modules from ports, tweak configs, and > qemu-img convert the .vdi file to a raw .img for bhyve! > oh that's great - glad i could help :) I realized after sending my last message that the wiki.freebsd.org/bhyve page is immutable under my account and i am unable to add content to it (i'm not in the ContributorsGroup on the wiki) so if someone wouldn't mind adding me to that group or point me in the right direction to do so that'd be great! cheers, -pete -- Pete Wright p...@nomadlogic.org twitter => @nomadlogicLA ___ 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 16 Oct 2014, at 08:52 , Dag-Erling Smørgrav wrote: > "Bjoern A. Zeeb" writes: >> Also if people are seriously thinking about virtualising pf we need to >> import the openbsd/apple pf fix from a few years ago because otherwise >> people in virtualised stacks with a /dev/pf can do ugly things. I >> think it’s been this one: >> http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-3830 > > There are other serious issues with our current pf (checksum corruption) > which I think can only be resolved by importing a newer version. Sorry, but you lost context. I was talking about security implications in VIMAGE context, not about random bugs. — 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?
"Bjoern A. Zeeb" writes: > Also if people are seriously thinking about virtualising pf we need to > import the openbsd/apple pf fix from a few years ago because otherwise > people in virtualised stacks with a /dev/pf can do ugly things. I > think it’s been this one: > http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-3830 There are other serious issues with our current pf (checksum corruption) which I think can only be resolved by importing a newer version. DES -- Dag-Erling Smørgrav - d...@des.no ___ 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"
