- User Since
- Jun 17 2016, 8:17 PM (337 w, 2 d)
Jul 27 2022
Jul 2 2022
May 5 2022
What is needed to help this review along?
Mar 23 2022
FYI from 13.0R:
What is the status of this work? This feature remains desirable.
Feb 16 2022
This applies cleanly to 13.0R and corrects the issue. Tested with dd(1) and fio using /dev/ada0 backed by a malloc md device.
May 4 2021
Great work James all who have provided review!
Feb 17 2021
Feb 14 2021
In testing this against 13.0-BETA1, stderr redirection does not appear to work:
Feb 12 2021
Trying to clear Phabricator messages/
When testing with fully-booted Windows Server 2019 and FreeBSD 13 guests, 10 second and 30 second waits work. (Destroy wait isn't reached)
Two people have confirmed that Windows often needs two ACPI nudges. It may be wise to take this approach.
Ignore the Dom0 reported in xl list! LOL!
royger@, Do you have any thoughts on how to elegantly check if a VM is running during start, to skip it? Will xl create generally do the right thing if a VM is already running?
I'm guessing load_rc_config $name isn't needed?
Here's a thought on VM tear-down:
Feb 9 2021
royger@: I am finding that Windows sometimes needs two shutdown attempts. Should this be left to the user to verify that the shutdown was successful, or should we consider some logic to wait, destroy, etc?
(Not sure how to submit unsubmitted comments...)
Regarding "status": This relies entirely on xl(1) for status, and it just provides the facts. There is no daemon involved short of xencommons and the Xen kernel itself. I had to use xencomains_cmd because without it, the rc framework would look to see if xl was running (xl top in my case for debugging), and it would say "Hey, is this already running?" when you started domains. NetBSD opts for a "list" rather than status, and Linux does things I need to decrypt.
Removing DOCS mention, adding xencommons REQUIREment
Feedback from royger@: REQUIRE: XENCOMMONS (All caps?)
Let's see what royger@ says on those points. Thank you!
Correcting PREFIX and adding USE_RC_SUBR
Looking at other examples in files, is this correct?
Moved to external utility in 2019
Fixed by bz@ in 2019 and re-fixed in 2021
Jan 21 2021
Thank you Kyle and Ed!
Aug 25 2020
Great work! Will 'config.dump' or another flag do a dry-run dump of the bhyve command to be executed? This would be very helpful. Apologies if I am overlooking it.
Mar 12 2019
Mar 1 2019
This is partially obsoleted by https://reviews.freebsd.org/D19418
Thank you bz@!
Feb 4 2019
I did a quick MAXCPU increase test on 12.0R based on comments by cpersiva@ but the results were neither positive nor directly related to these patches.
To use these patches, first increase VM_MAXCPU from 16 in:
I have applied these related VM_MAXCPU patches to 12.0R and rebuilt the related components.
Sep 8 2018
I have split out the build option survey components and WITHOUT_DYNAMICROOT.
Ed, this builds and installs for me wth both pristine sources that include only these, and my sources with my other build option changes updated to this for dhcpclient/ping.
Sep 7 2018
That looks good to me. Please advise if you want me to test it.
I have updated the diff to remove the build option survey components and have submitted a separate diff to rgrimes for his review and review by his mentors. This is based on 12.0-ALPHA4.
Sep 6 2018
From another 12.0-ALPHA4 build:
Adding the 'svnlite diff -x -U99999' full diff. Not yet broken it up.
I believe at least some of these should be addressed by fixing whatever failed rather than by excluding parts from the build; do you have a list of the errors you encountered with the various combinations? i.e., I would be interested in seeing how ping and dhclient fail under DYNAMICROOT.
For any future uploads please include full context (e.g. from git diff -U9999 or equivalent).
Sep 5 2018
Aug 18 2018
Yes, it appears syslogd can be be built with a mix of WITHOUT_INET and WITHOUT_INET_SUPPORT, plus the WITHOUT_INET6 and WITHOUT_INET6_SUPPORT
Aug 16 2018
Nov 3 2017
Were the tips removed by this added to adduser(8) or the Handbook?
In my testing, this appears to be based on FreeBSD 10.1, which is well supported by AHCI emulation. Supporting back to 5.0 or earlier would make this much more useful.
Consider changing it to mention of using a "memstick" .img installer in Shell mode. I find them quite useful for rescue work and the install media can even be used to boot the new installation in bhyve(8).
Aug 17 2017
Have you found any time?
Aug 14 2017
Several people would like to see this through. Please add a copyright and license to the work.
May 23 2017
mat, is this something you can commit?
Ed's comments are all accurate. This document conflates many things and suggest we take a moment to address them at BSDCan or in advance. I for one think the nuts and bolts of SVN be separated out, ideally in a way that produces a document that can double as an in-base man page for snvlite(1).
Mar 23 2017
Yes, this is a forklift upgrade of a ransom note of a document. Please specify the sequence of changes you would like to see.
Mar 12 2017
Those Actions don't quite sound like what I want..
Those Actions are not intuitive
Sep 12 2016
Sep 7 2016
That's correct. And I prefer that the problem is fixed in beadm from ports.
Sep 6 2016
Some of the issues that this addresses, as pointed out:
Aug 1 2016
The original sysbench author promised an updated release but may have abandoned the project. Percona has forked it for their purposes. Other suggestions in this situation?
Jul 21 2016
Support for FreeBSD 6 and older, even if for historical/academic purposes, is a topic that keeps coming up. Legacy systems come in all shapes and sizes and I can think of at least one point-of-sale vendor that spans generations of FreeBSD and other Unix systems.
Jul 17 2016
I can't help but notice that there is a /usr/share/firmware directory.
Jul 11 2016
May I suggest removing "-edk2" from the port name? Few users know what this means and it is easily forgotten.