Re: Windows Desktop OS only show one CPU on bhyve even though 2-4 are assigned
It's a little bit annoying is that this setting is "systemwide" I agree. but I believe there was talk to make this per-vm, though I don't know how that is coming along... Not quickly. I added a bugzilla note to track this: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215077 later, Peter. ___ 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: Windows Desktop OS only show one CPU on bhyve even though 2-4 are assigned
The short answer is that Windows Desktop OS only supports a single CPU socket, optionally with many cores. The default in bhyve is to expose each virtual CPU as a separate socket. There are a set of sysctls that let you control this, so you can instead expose the 4 cpus as cores of a single socket, and it will then work with Windows 8.1/10, but I don't recall what they are off the top of my head, but they are in the archive which you can browse here: https://lists.freebsd.org/pipermail/freebsd-virtualization/ The post in question is http://docs.FreeBSD.org/cgi/mid.cgi?b26b6124-7ac6-0408-3016-f5678ad144d0 later, Peter. ___ 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"
Automatic provisioning via bhyve
Hello, I was wondering if anyone has experimented or worked on with a way, given the ISO, automatically create any number of bhyve guests with preset installer options, an option to run them and a way to destroy all the virtual machines as well as their images/zvols. Best regards, Domagoj Stolfa. ___ 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: Windows Desktop OS only show one CPU on bhyve even though 2-4 are assigned
On Mon, Dec 5, 2016 at 5:55 PM, richardwrote: > On 12/05/16 17:41, Allan Jude wrote: >> >> On 2016-12-05 05:22, Michael Braig wrote: >>> >>> Dear All, >>> >>> I have now setup Window Desktop OS based on 8.1 and 10, but also Windows >>> Server 2012 R2. >>> >>> The latter correctly shows the amount of assigned CPUs. The Desktop OSs >>> always only show one, but also have high CPU load with especially the >>> Windows network service. >>> >>> Did anybody experience this as well, anybody who can advise me on how >>> Windows will recognize the additional CPUs? >>> >>> I am using an HP ML110 G7 with Xeon CPUs. >>> >>> Regards >>> Michael >>> ___ >>> 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" >>> >> This question has been answered before, in the last 2-3 months, if you >> search the archive. >> >> The short answer is that Windows Desktop OS only supports a single CPU >> socket, optionally with many cores. The default in bhyve is to expose >> each virtual CPU as a separate socket. There are a set of sysctls that >> let you control this, so you can instead expose the 4 cpus as cores of a >> single socket, and it will then work with Windows 8.1/10, but I don't >> recall what they are off the top of my head, but they are in the archive >> which you can browse here: >> >> https://lists.freebsd.org/pipermail/freebsd-virtualization/ >> > i've put > > hw.vmm.topology.cores_per_package=4 > > in /boot/loader.conf > > richard > > And did that fix your issue? It's a little bit annoying is that this setting is "systemwide" but I believe there was talk to make this per-vm, though I don't know how that is coming along... > > ___ > 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" ___ 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: Windows Desktop OS only show one CPU on bhyve even though 2-4 are assigned
On 12/05/16 17:41, Allan Jude wrote: On 2016-12-05 05:22, Michael Braig wrote: Dear All, I have now setup Window Desktop OS based on 8.1 and 10, but also Windows Server 2012 R2. The latter correctly shows the amount of assigned CPUs. The Desktop OSs always only show one, but also have high CPU load with especially the Windows network service. Did anybody experience this as well, anybody who can advise me on how Windows will recognize the additional CPUs? I am using an HP ML110 G7 with Xeon CPUs. Regards Michael ___ 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" This question has been answered before, in the last 2-3 months, if you search the archive. The short answer is that Windows Desktop OS only supports a single CPU socket, optionally with many cores. The default in bhyve is to expose each virtual CPU as a separate socket. There are a set of sysctls that let you control this, so you can instead expose the 4 cpus as cores of a single socket, and it will then work with Windows 8.1/10, but I don't recall what they are off the top of my head, but they are in the archive which you can browse here: https://lists.freebsd.org/pipermail/freebsd-virtualization/ i've put hw.vmm.topology.cores_per_package=4 in /boot/loader.conf richard ___ 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: Windows Desktop OS only show one CPU on bhyve even though 2-4 are assigned
On 2016-12-05 05:22, Michael Braig wrote: > Dear All, > > I have now setup Window Desktop OS based on 8.1 and 10, but also Windows > Server 2012 R2. > > The latter correctly shows the amount of assigned CPUs. The Desktop OSs > always only show one, but also have high CPU load with especially the > Windows network service. > > Did anybody experience this as well, anybody who can advise me on how > Windows will recognize the additional CPUs? > > I am using an HP ML110 G7 with Xeon CPUs. > > Regards > Michael > ___ > 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" > This question has been answered before, in the last 2-3 months, if you search the archive. The short answer is that Windows Desktop OS only supports a single CPU socket, optionally with many cores. The default in bhyve is to expose each virtual CPU as a separate socket. There are a set of sysctls that let you control this, so you can instead expose the 4 cpus as cores of a single socket, and it will then work with Windows 8.1/10, but I don't recall what they are off the top of my head, but they are in the archive which you can browse here: https://lists.freebsd.org/pipermail/freebsd-virtualization/ -- 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"
Windows Desktop OS only show one CPU on bhyve even though 2-4 are assigned
Dear All, I have now setup Window Desktop OS based on 8.1 and 10, but also Windows Server 2012 R2. The latter correctly shows the amount of assigned CPUs. The Desktop OSs always only show one, but also have high CPU load with especially the Windows network service. Did anybody experience this as well, anybody who can advise me on how Windows will recognize the additional CPUs? I am using an HP ML110 G7 with Xeon CPUs. Regards Michael ___ 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"