Anyone else updated to v5.1 and finding Win10 guest aborts?

[gulbrain]

Hi,

I"d been using 5.0 for a few weeks and created the guest under that, installing a fresh Windows 10 and some bits 'n' pieces.

The host has been having problems (complete hangs) which I'm trying to diagnose, but since upgrading VirtualBox to 5.1, the guest aborts as soon as I move the mouse pointer onto its console.

Did I miss something?
Maybe it's because it was aborted due to system issues whilst running under 5.0 and now is troubled with something having got out of sync.?
I tried starting it and then doing a clean shutdown before mousing over it. It shutdown nicely, but the problem remains when i restart it.

I have some clones from a clean shutdown in v5.0 before the latest guest sw install, but haven't tried them, yet.

I appreciate that's all vague ... but if I'm wondering if I'm alone with the problem or fallen foul of a rookie trap.

I have the Extension Pack installed and that upgraded automatically when I started 5.1.

Suggestions welcome.

Virtual Box version: v 5.1.0 r108711
Host OS: Pointlinux - 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt25-2+deb8u3

Thanks,
Tim

[socratis]

In order to better understand the problem you need to submit some more information. Please read the following: Minimum information needed for assistance. For the VM log file ("VBox.log.zip"), here's what you do:

1. Start the VM. Not from a saved or suspended state. Clean start.
2. Take the steps required to generate/observe the error.
3. Shut down the VM (if it hasn't aborted by itself). Not suspended, not paused. Shut down. If you can't shut it down by normal means, close the VM window and select "Power off".
4. Right-click on the VM in the VirtualBox Manager.
5. Select "Show Log..."
6. Save it (just the first log, VBox.log), ZIP it and attach it in your response (see the "Upload attachment" at the bottom of the form).

On top of that if you could repeat the procedure without actually crashing the host, it would be helpful to compare the two.

[WFV]

My Windows 7 Pro 64 bit guest aborted on first start after upgrading to 5.1 but hasn't since - but I haven't tried the mouse in the window during startup (never have a reason to, but believe I accidentally clicked the mouse in the window while it was starting that first time). As mentioned already, for troubleshooting get the log socratis pointed out.

[gulbrain]

Thank you for your input.
Let me clarify: the guest aborts when I move the mouse onto the console. Even if that's after it's started and I'm about to try to login.

Attached: two vm logs - one crash, one clean startup/shutdown.

I tried one of the clones moments ago, and it does the same thing - so it's fix or re-install Windows 10 time ;-(.

Thanks,
Tim

[socratis]

Thanks for submitting both logs. I thought it would make my life easier, but it didn't. I couldn't find no differences whatsoever. Differences that were recorded in the logs that is. I have no clue whatsoever. I've got some minor questions:
• "as soon as I move the mouse pointer onto its console" : What do you mean "console"?
• "Maybe it's because it was aborted due to system issues" : Can you elaborate on this?

[WFV]

@ gulbrain: Maybe dumb question, how is your mouse integration set up? Just wondering if the update changed the integration settings for W10 guests.
I'm having a different issue with recent upgrade to 5.1 - can't get Linux Guest audio to work, the two Windows Guests (Win7pro64 & WinXPhome) audio are working. Not asking in this for help in this forum, just mentioning that maybe there is problem(s) with 5.1 guest-modules. I'm not showing any audio errors in the VBox logs - apparently both VBox and the Linux guests think its working (it's not like they can hear it,,,)

[socratis]

just mentioning that maybe there is problem(s) with 5.1 guest-modules

Your audio problem has absolutely nothing to do with the guest additions. In fact your problem has absolutely nothing to do with this thread.

[gulbrain]

• "as soon as I move the mouse pointer onto its console" : What do you mean "console"?
The window that appears when I start the machine. The window into which I click to enter my login details to use the machine. It basically means that I can't use the machine in any way.

• "Maybe it's because it was aborted due to system issues" : Can you elaborate on this?
The host has been having issues where periodically it hangs completely and utterly. The only way forward it to reset it and login again. This presumably terminates the guest unexpectedly. With the guest in that state, I upgraded VirtualBox - and wondered if that might be related to the problem. I have since, however, observed this same behaviour (instant abort when I go to use it) when I started a clone that I had taken from a clean shutdown and I believe this rules out this concern.

* how is your mouse integration set up?
In the guest's settings I had "USB Tablet". I tried "PS/2 Mouse", but it made no difference. Is that what you meant?

Wondering if there was a fundamental issue, I downloaded a Debian netinst iso and started a new machine with that. I was able to click through the first parts of the GUI installer.

In the absence of other ideas, I may just have to re-install. Sometimes I do get the recovery window and I'll give that a go first. It likely won't make it worse !

Thanks,
Tim

[WFV]

easy does it socratis, I was referring to possible problem with VBox sharing hardware resources and the similarity of not showing up in the logs - minga. failure to share host resources can result in aborted boots regardless of the particular component, mouse, speaker anything that has to travel across the mother board... however, nonetheless two distinct issues as pointed out - audio not belonging to this thread is resolved and no need to create another thread.

[socratis]

I was referring to possible problem with VBox sharing hardware resources and the similarity of not showing up in the logs

There was never such an issue on this thread.

failure to share host resources can result in aborted boots regardless of the particular component, mouse, speaker anything that has to travel across the mother board...

I'm sorry but that doesn't make too much sense. Too broad a statement and I'm afraid that again it doesn't apply to this thread.

easy does it socratis

That was easy on my book. "Minga" on the other hand, isn't. It's borderline OK. Really borderline. I've watched plenty of Italian movies to know even how it's pronounced properly...

[gulbrain]

Update: Just upgraded to vbox 5.1.2. No change in behaviour noticed.

[gulbrain]

In the absence of further ideas, I really hope the re-install works.
I'm a short while off *needing* the machine, so ...

[bmn]

I was having the same issues trying to install a Windows 7 64 bits guest on a Mac OS 10.10.5 host using an upgraded VirtualBox 5.0.x to 5.1.2

My solution was selecting:

• Chipset: ICH9
• HiDPI Support: [Checked] Use Unscaled HiDPI Output

I don't know which one made the trick but it worked. I hope it helps to others.

[TimPeregoy]

I am having a similar experience with Ubuntu 14.04 as the host, and Win10 guests. Two guests are Win7 upgrades, and one is a native Win10 installation. In my case, the problem seemed to be related to network access; I would browse the Windows network and the VM would quit.

I am trying the ICH9 chipset approach suggested above to see if this has an effect.

[gulbrain]

OK, so it's been a while and a few things have upgraded, fixed, etc outside of vbox.

The behaviour has changed slightly in that it reboots, rather than aborts. That is, until Windows thinks it crashed and asks about recovery mode.

Code: Select all

OS: 4.6.0-0.bpo.1-amd64 #1 SMP Debian 4.6.4-1~bpo8+1 (2016-08-11)
VirtualBox: 5.1.6 r110634 (Qt5.6.1)

There is also some information in a log file which may or may not provide a clue.

Code: Select all

...
00:01:00.485227 ********************* End of statistics **********************
00:01:00.503796 NAT: Zone(nm:mbuf_cluster, used:0)
00:01:00.504425 NAT: Zone(nm:mbuf_packet, used:0)
00:01:00.504431 NAT: Zone(nm:mbuf, used:1)
00:01:00.504438 NAT: Zone(nm:mbuf_jumbo_pagesize, used:0)
00:01:00.505052 NAT: Zone(nm:mbuf_jumbo_9k, used:0)
00:01:00.505389 NAT: Zone(nm:mbuf_jumbo_16k, used:0)
00:01:00.505556 NAT: Zone(nm:mbuf_ext_refcnt, used:0)
00:01:00.539255 GIM: HyperV: Resetting MMIO2 regions and MSRs
00:01:00.550254 Changing the VM state from 'DESTROYING' to 'TERMINATED'
00:01:00.559817 Console: Machine state changed to 'PoweredOff'
00:01:01.024928 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={The object is not ready}, preserve=false aResultDetail=0

Still not tried re-installing Windows : just waiting for the time and priority.

Thanks for reading.