After upgrading to VBox 5.2.18 all my VMS hang/freeze

Discussions related to using VirtualBox on Windows hosts.
Post Reply
chrisBL
Posts: 3
Joined: 17. Aug 2018, 17:46

After upgrading to VBox 5.2.18 all my VMS hang/freeze

Post by chrisBL »

Hello,

after Upgrading (ON A FRESH INSTALLED PC!!!) Virtualbox to Version 5.2.18 all my VMs running extremly slow/freezing

Windows 7: Boot is running slow, hangs and freezing inside Windows 7; Bevor: running smoothly

Windows 2000: Boot is runnnig extremly slow and VM stuck in boot screen; Bevore: running smootly
Attachments
VirtualBox_win2k_17_08_2018_17_53_05.png
VirtualBox_win2k_17_08_2018_17_53_05.png (2.65 KiB) Viewed 1415 times
VirtualBox_win2k_17_08_2018_17_53_02.png
VirtualBox_win2k_17_08_2018_17_53_02.png (1.94 KiB) Viewed 1415 times
Logs.zip
(128.69 KiB) Downloaded 11 times
chrisBL
Posts: 3
Joined: 17. Aug 2018, 17:46

Re: After upgrading to VBox 5.2.18 all my VMS hang/freeze

Post by chrisBL »

I temporary solved the Problem!

I have reinstalled Windows 10 on my Host!

But it cant be normally reinstallting OS on the host everytime a newer Virtualbox Version is out!

So please patient and take a look on this strange issue!

Best regards
socratis
Site Moderator
Posts: 27329
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: After upgrading to VBox 5.2.18 all my VMS hang/freeze

Post by socratis »

00:00:06.210905 ICH9 <integer> = 0x0000000000000001 (1)
Can you please tell me why you felt the need to use an unsupported (for your guest) chipset? Why did you change the template suggested defaults? Please switch it back to the default PIIX3. And no, "it used to work" is not a good reason enough. "It's unsupported" is a much stronger argument. Just hover over the chipset and read the tooltip...

I didn't see any evidence that the Guest Additions (GAs) were installed. You should install them, you'll get a much better experience.
chrisBL wrote:But it cant be normally reinstallting OS on the host everytime a newer Virtualbox Version is out!
The opposite is true; when you do a major upgrade (e.g. from Win10 1703 to 1709 or 1803), then you need to re-install VirtualBox. Re-installing Windows to fix a VirtualBox issue? That to me tells me that something was wrong with your Win10 host to begin with...
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.
chrisBL
Posts: 3
Joined: 17. Aug 2018, 17:46

Re: After upgrading to VBox 5.2.18 all my VMS hang/freeze

Post by chrisBL »

socratis wrote:
00:00:06.210905 ICH9 <integer> = 0x0000000000000001 (1)
Can you please tell me why you felt the need to use an unsupported (for your guest) chipset? Why did you change the template suggested defaults? Please switch it back to the default PIIX3. And no, "it used to work" is not a good reason
Now i haven't change anything yet and everything runs fine, without chaning back from ICH9.
I have changed back to PIIX3 without any success.
Trying to install with a new template and new virtual HD ended in stucking bootscreen.
Post Reply