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
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
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
On Mon, Dec 5, 2016 at 5:55 PM, richard wrote:
> 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
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
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
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