cs2015 wrote:It really is a problem with the new version of VB.
No it is not. The question is why it is a problem with your installation. My guess is that something that you have installed on the guest conflicts somehow with the updated GAs. I couldn't even begin to speculate. A theme? A window manager? A ... something else?
Yes it is.
Nothing has changed on the Guest installation - it is the same version of Win XP Pro I have been using for the past two years at least. No new software has been installed. As I said, it works perfectly with 5.0.28 but not 5.1.12. I have repeated the change of VB versions to confirm this.
The same issue occurs running VB 5.1.12 but with the old (5.0.28) GA too.
I bet that if you install a new WinXP guest you won't see the problem. But it maybe just me and the thousands of others that are using WinXP VMs without any issue.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
What is the graphics mode being used in the guest (display size and bits/pixel), and what is the graphics mode being used on the host?
I have not yet updated my installation to 5.1.12 (it's a big download for me on my home ADSL), but 5.1.10 with 5.1.10 GAs in an XP guest works quite adequately for me (no 3D). Dragging the VM window around of course does nothing to the CPU, while dragging a guest window around makes the explorer task consume between 5% and 17% of CPU. Win10 host.
socratis wrote:I bet that if you install a new WinXP guest you won't see the problem. But it maybe just me and the thousands of others that are using WinXP VMs without any issue.
By your own admission, you are using an obsolete version of MacOS.
But anyway, I took your advice and did a clean install of Win XP in a new Guest - same settings as before.
Guess what - exactly the same symptoms - dragging or resizing a window within the Guest (XP) desktop is like wading through treacle.
Just me Eh ??
(It even has the same choppy sound which wasn't present on 5.0.28)
Last edited by cs2015 on 2. Jan 2017, 16:14, edited 1 time in total.
mpack wrote:What is the graphics mode being used in the guest (display size and bits/pixel), and what is the graphics mode being used on the host?
I have not yet updated my installation to 5.1.12 (it's a big download for me on my home ADSL), but 5.1.10 with 5.1.10 GAs in an XP guest works quite adequately for me (no 3D). Dragging the VM window around of course does nothing to the CPU, while dragging a guest window around makes the explorer task consume between 5% and 17% of CPU. Win10 host.
See post 26 onwards.
Whether 2D or 3D is enabled makes no difference.
Note: I'm using a MacOS Sierra host.
Hmm... 10.12 then? The thing I was pointing to was that there was nothing substantial changing in the GAs in 5.1.12. The interaction may be bad with 10.12. I don't have a data point to contribute, but I believe there are a couple that do: loukingjr, rpmurray and I believe ChipMcK...
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
socratis wrote:Hmm... 10.12 then? The thing I was pointing to was that there was nothing substantial changing in the GAs in 5.1.12. The interaction may be bad with 10.12. I don't have a data point to contribute, but I believe there are a couple that do: loukingjr, rpmurray and I believe ChipMcK...
Note that when I was changing back and forth between 5.0.28 and 5.1.12, I briefly used GA 5.1.10 in conjunction with VB 5.1.12. That didn't solve the problem (but still worked). Only going back to 5.0.28 (VB and GA) worked properly with Sierra.
Eh? What does that mean? This topic has had 23 posts so far, including this one. I see previous discussion of guest mode hints as mentioned in the log, but that was not my question.
mpack wrote:5.0.x to 5.1.x covers quite a lengthy timespan. It would be very helpful if you could pin it down to an exact version.
5.0.30 is the newest version of 5.0.X, so I tried 5.1.0 which is the next version released.
That refused to let me install Guest Additions - launching the GA installer just launched VB then did nothing.
So I then tried 5.1.2 and that did install OK (including the GAs).
That exhibited exactly the same slow 'treacle' graphics issue as 5.1.12, so it seems likely that 5.1.0 will too.
cs2015 wrote:launching the GA installer just launched VB then did nothing.
I'm sorry but I can't figure out this sentence. You launched the GA installer which launched VirtualBox? You can't launch VirtualBox from the same place you launch the GA, nor can the GA installer cause the VirtualBox to launch. Was there a typo?
And BTW, the releases aren't exactly numbered, i.e. 5.1.0 didn't come after 5.0.30. The releases are happening in parallel, so the GAs could be broken somewhere in between releases:
2016-07-12 5.1.0
2016-07-18 5.0.26
2016-07-21 5.1.2
2016-08-16 5.1.4
2016-09-12 5.1.6
2016-10-28 5.1.8, 5.0.28
2016-11-21 5.1.10
2016-11-23 5.0.30
2016-12-20 5.1.12
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
socratis wrote:I'm sorry but I can't figure out this sentence. You launched the GA installer which launched VirtualBox? You can't launch VirtualBox from the same place you launch the GA, nor can the GA installer cause the VirtualBox to launch. Was there a typo?
Sorry yes, I meant Extension Pack, not Guest Additions.
socratis wrote:
And BTW, the releases aren't exactly numbered, i.e. 5.1.0 didn't come after 5.0.30. The releases are happening in parallel, so the GAs could be broken somewhere in between releases:
OK.
What I observed is that that both 5.1.2 and 5.1.12 gave exactly the same problem, but all the versions of 5.0.X I installed were OK, so I think there must be a change right from the start of the 5.1.X series.