On 1/10/19 8:15 PM, David C. Rankin wrote:
On 01/10/2019 12:33 AM, Bruce Ferrell wrote:
I only have a couple windows VMs, Win7 and 2008r2. Host OS is Scientific Linux
6.10 on a Dell R710.
I saw some slowness after the update and changed the virtualization method to
KVM from Hyper-V (don't ask me how that got set) and that cleared it up.
Thanks, I'll give that a look. I didn't change anything there (haven't in 2+
years). Looking with VBoxManage, I have
VT-x VPID: enabled
VT-x unr. exec.: enabled
Paravirt. Provider: Default
Effective Paravirt. Prov.: HyperV
State: powered off (since 2019-01-10T09:12:25.000000000)
Which is what the manual says it should be under
10.4. Paravirtualization Providers
https://www.virtualbox.org/manual/ch10.html
I have tried with/without 2D acceleration enabled and 48/32M or dedicated
video. It makes no difference. Both Command Prompt (cmd.exe) and PowerShell
terminals are effected. (the listing still crawls) I've been through the event
log with even view and it is clean. No issues out of the ordinary.
This is a distinct and pronounced slowdown with 6.0.0. Ironically, all I use
windows 7 vbox install for is helping people with programming questions on
StackOverflow (I use Linux exclusively, but sometimes they have a MinGW or VS
question that I need windows for) So my use of Win7 is primarily limited to
using cmd.exe and building short C/C++ programs.
That's why this isn't one of those things where is "umm, I think is a little
slower...", this is one of those things "where it is immediately noticeable
and damn near unusable..."
I have another Win7 guest where the host is still 5.2.22 and it is fine.
Any other ideas? I'm pretty well stumped. I don't have the option of dropping
back to 5.2.22 on this server as it is Archlinux and running Linux 4.20.
Could this be related to any of the Spectre mitigations that effect vbox on
Linux 4.20? (I'm grasping here...)
I'll keep looking at it. I don't even have enough info to open a bug-report
other than what I've included in the e-mail. No errors thrown on host or
guest, so it's just basically something that 6.0.0 did.
David,
You and I live in similar worlds. I do enterprise product support to pay the bills. The number of times I've been told "it's broke!!!... " with hair on fire and hands waving (not
that I think this is you... I've seen too much of your work here).... So, yeah, but what... Exactly is slow? Is the performance issue CPU? I/O (disk)? Interrupts? Let's find out.
Here's is what I would do:
On both good and bad
- Fire up task manager/perfmon
run the process/app the makes the issue show
Take a look at all of the metrics to see what is spiking. If the VM is slow,
SOMETHING is gonna show a spike... I hope ;)
That may give a pointer to an area of virtualbox to look in at least.
I might even get radical and grab the open source version of sysdig and profile
the VM process, but that MAY be a bit extreme... strace on it/them maybe?
_______________________________________________
VBox-users-community mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/vbox-users-community
_______________________________________________
Unsubscribe:
mailto:[email protected]?subject=unsubscribe
