Re: iocage no longer supported?
On Tue, 12 Apr 2016 11:44:14 -0400 Larry Bairdwrote: > I was beginning to look into a replacement for ezjail, mainly because > ezjail doesn't use jail.conf. After vistiting lots of sites and doing > some reading, I had about decided upon iocage. I am now convered > about this decision. When I visit https://github.com/iocage/iocage is > now says "**No longer supported. iocage is being rewritten in a > differnt language." Does anybody have any details? > https://github.com/iocage/iocage/commit/3f394561a3dde55cd3ac7911be313c5df5865183 -- Michael Gmelin ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
[Bug 198344] [virtio] virtio-balloon does not work
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198344 --- Comment #7 from Brad Davis--- It looks like this should be fixed in this MFC: https://svnweb.freebsd.org/base/stable/10/sys/dev/virtio/balloon/virtio_balloon.c?view=log Can someone test 10.3 and let us know? -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
iocage no longer supported?
I was beginning to look into a replacement for ezjail, mainly because ezjail doesn't use jail.conf. After vistiting lots of sites and doing some reading, I had about decided upon iocage. I am now convered about this decision. When I visit https://github.com/iocage/iocage is now says "**No longer supported. iocage is being rewritten in a differnt language." Does anybody have any details? Thanks, Larry -- Larry Baird Global Technology Associates, Inc. 1992-2012| http://www.gta.com Celebrating Twenty Years of Software Innovation | Orlando, FL Email: l...@gta.com | TEL 407-380-0220 ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
[Bug 208238] [Hyper-V] TSC frequency is not correctly detected: "calcru: runtime went backwards"
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208238 --- Comment #3 from Dexuan Cui--- The further patches on 11-CURRENT should fix the bug safely now: https://github.com/freebsd/freebsd/commit/297e2d2f528a41d9a9614e9b34049801f6935b31 https://github.com/freebsd/freebsd/commit/28d2243294e521bd34a063a402382b21ad03b262 https://github.com/freebsd/freebsd/commit/dbf747e96c50495258170a73aa5a6ab288b8b958 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
[Bug 208238] [Hyper-V] TSC frequency is not correctly detected: "calcru: runtime went backwards"
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208238 --- Comment #2 from Dexuan Cui--- The tsc-calibration fix was temporarily taken back last Friday because we found an interesting thing: with some kind of config, Xen can pretend to be Hyper-V by mimicking the hypervisor CPUID signature (this is usually to make Windows VM run better on Xen), but Xen doesn’t support Hyper-V timecounter, so the fix causes an unexpected panic when FreeBSD VM runs on Xen in this case. We're making another patch to better detect if the underlying hypervisor supports Hyper-V timecounter or not: https://lists.freebsd.org/pipermail/freebsd-current/2016-April/060519.html -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: -current host, 10.1 client loops
In message <570c74cf.1080...@freebsd.org>, Peter Grehan writes: > I'll try with a bit more CPU oversubscription and see if I can hit >this. Thanks for the info - this should help track it down. For what its worth, I think the port being compiled was: /usr/ports/www/p5-Mozilla-CAnss Another possibly relevant datapoint: The actively being written to filesystem is UFS+SU+TRIM but no journal and I think fsck sees more and worse corruption than it should if writes happened in the order Kirk intended. Specifically it should never get fsck_ffs into the "please run fsck again" jungle. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"