Too many CPUs warning

[loukingjr]

Explanation?

It's a Warning. That doesn't mean you can't do it.

[giacomo]

Why is there a WARNING for a situation that is not an issue?

[science_man]

Why is there a WARNING for a situation that is not an issue?

That's what I'm saying.

[loukingjr]

I didn't say it wasn't an issue. For most hosts and most guests it's not ideal to run all cores on a guest.

It's like a railroad crossing. "Warning! Railroad Crossing". Doesn't mean you have to sit there for the rest of your life.

[science_man]

I didn't say it wasn't an issue. For most hosts and most guests it's not ideal to run all cores on a guest.

It's like a railroad crossing. "Warning! Railroad Crossing". Doesn't mean you have to sit there for the rest of your life.

But the warning isn't "you're using more of your processors than is advisable", it's "you're using more processors than I think you have".

In the case when I have 8 processors and 4 cores, shouldn't I be allowed to allocate 7 to the guest and still be observing best practices for respecting the host?

[giacomo]

This warning comes up for any setting of 5-8. It only goes away when I set the number of CPUs to 4. I can only safely use half the number of cores?

Moreover, the warning is not consistent. Last week before I upgraded my CPU, I ran the same Ubuntu guest on the same host on an i5-4440 (2 physical core x 2 threads per core) I could use 1-4 cores without any such warning. So why does the warning only occur for certain processors and not others? Seems like a bug to me.

[loukingjr]

What I can say is, if a guest runs well for you with all cores assigned to a guest, go for it.

And although it's been explained multiple times, cores are not threads.

[science_man]

What I can say is, if a guest runs well for you with all cores assigned to a guest, go for it.

And although it's been explained multiple times, cores are not threads.

I think we all know the difference between threads and cores at this point. I'm going to submit a bug report.

[loukingjr]

okay.

[science_man]

Here ya go:
https://www.virtualbox.org/ticket/14944
Enjoy

[loukingjr]

without any logs they probably won't look at it.

[science_man]

There are no logs that would be relevant, are there?

[loukingjr]

My point was, you gave no screen shots, no vbox.log. Developers are not likely going to come to the forum to read your post.

[science_man]

My point was, you gave no screen shots, no vbox.log. Developers are not likely going to come to the forum to read your post.

You are probably right, but screen shots wouldn't tell anything that my description didn't, and I doubt vbox.log would say anything relevant.

Maybe I'll patch it myself if I have the time and just submit that.

[loukingjr]

Just trying to help. I take it you didn't read the info on the Bugtracker page.

Look forward to your "fix".