Re: kern.hz – Windows aequivalent, high CPU usage on bhyve copmared to ESXi

t;freebsd-virtualization-unsubscr...@freebsd.org" What does your bhyve command line invocation look like? -- Allan Jude ___ 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: Overcommitting CPUs with BHyve?

and line flag, -p, to let you pin a vCPU to a physical CPU. This might avoid some of the issues with the threads hopping around all the time. If you were anyone else, I'd also ask if you ensured your vfs.zfs.arc_max was low enough to actually leave some ram for the VM to use. -- Allan Jude signature.asc Description: OpenPGP digital signature

Re: Checking bhyve supported features (sysctls)

ething else. > >I looked at the code for bhyvectl, bhyveload and >byhve. They do not actually try to decide if vmm >is supported or not, they simply process the error >from a vm_create() or vm_open() call and exit >with an error code if they can not handle it >(some of the cod

Re: Query regarding tutorials (Please have a quick read of me!)

mmunity benefit more of an example of 2012 (which is much >> lighter)? >> >> Or perhaps something entirely different, any replies would be more than >> welcome :) > > because of the internal container boundaries of windows 10 and server 2016, i > won't run anything older. so if you're doing a windows server on bhyve video, > i would want it to be 2016. > -- Allan Jude signature.asc Description: OpenPGP digital signature

Re: Query regarding tutorials (Please have a quick read of me!)

On 2018-08-26 01:54, Paul Vixie wrote: > On Sunday, August 26, 2018 2:46:42 AM UTC Allan Jude wrote: >> On 2018-08-25 13:45, Paul Vixie wrote: >>> ... i remain >>> mystified by the behaviour of grub-bhyve, which usually fails (no >>> meaningful error message

Re: bhyve performance problem with SQL server

ps://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to > "freebsd-virtualization-unsubscr...@freebsd.org" What is the 'volblocksize' of your zvol? What block size are you using for the bhyve virtual device? is it virtio-blk or ahci? Can you tell if the problem is related to disk IO? -- Allan Jude signature.asc Description: OpenPGP digital signature

Re: zvol vs sparse-zvol vs file

w block storage. There isn't really any difference between a zvol and a thin-provisioned zvol, unless you run out of space (if you over-provision). -- Allan Jude signature.asc Description: OpenPGP digital signature

Re: Custom Qcow2 Images

e > that is around 500MB. > > Thanks in advance! > -pete > I would expect the answer is `poudriere image` with a src.conf with many WITHOUT_* knobs to disable things you don't need to get the image down in size. There is likely a list of such knobs you could borrow from nanobsd.

Re: Centos 8, Centos Stream and XFS

On 2019-09-29 09:54, The Doctor via freebsd-virtualization wrote: > Are we able to solve those 3 problems? > If you boot using UEFI or UEFI-CSM you don't need bhyve-grub to support the newer filesystem stuff, as it will use CentOS's verion of grub installed inside the image.

Re: bhyve: TRIM support in AHCI controller

ve updated my patch to add TRIM support to the bhyve block interface here: https://reviews.freebsd.org/D21707 I am working on an update to the virtio driver, to make FreeBSD guests able to TRIM if the hypervisor supports it as well: https://reviews.freebsd.org/D21708 -- Allan Jude signature.asc Description: OpenPGP digital signature

Re: bhyve, Windows guest and trim support

mands, and you will see the space become free in your zvol. There is a separate patch to teach the FreeBSD virtio-blk driver to send TRIM commands, it is still in review (needs testing on hypervisors other than bhyve): https://reviews.freebsd.org/D21708 -- Allan Jude signature.asc Description: OpenPGP digital signature

Re: zfs compression of a volume

e the compression setting. If you want to recompress the entire volume: 1) stop the bhyve 2) snapshot the volume 3) create a new volume, with compression enabled 4) zfs send -e oldvolume@snapshot | zfs recv -F newvolume 5) start the bhyve using the new volume 6) (optional) destroy t

Re: After 12.1->12.2 upgrade FreeBSD bhyve guest does not start anymore

t;     eg. ufs:/dev/da0s1a >>     zfs:tank >>     cd9660:/dev/cd0 ro >>   (which is equivalent to: mount -t cd9660 -o ro /dev/cd0 /) >> >>   ?   List valid disk boot devices >>   .   Yield 1 second (for background tasks) >>       Abort manual input >> >> mountroot> > > Then, if I just type "ufs:/dev/vtbd0a" it will start correctly. > > > Can anyone explain why this happens and how to avoid it? > > >  bye & Thanks > av. > ___ > 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" Do you happen to have a ZFS partition? I think some changes to some of the bootstrap (pre-loader) code that is shared with bhyve-load, means it always prefers ZFS over UFS (normally for booting a real machine, you use a different bootstrap for UFS than for ZFS, but bhyve-load is a special case. -- Allan Jude ___ 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"

<    1   2