XP Guest keeps aborting

[Palpaz]

I have the latest version of VB (Version 5.1.26 r117224 (Qt5.6.2)) in a MacBook pro Host (running 10.9.5 OSX).

I have windows XP and Windows 7 guests that I have used for years (around 7 years) without any problem.

Since the last update of Virtual Box, my XP guest keeps aborting for no apparent reason... whenever I want to use it, the desktop is no longer there and I go check the VB app, and it shows "Aborted", usually happens when my Mac goes to sleep. This only happens with XP... win7 works fine.

I haven't installed anything new in windows XP, and it has happened even after new start with no applications running (on XP).

This is what the XP Log looks like:

Code: Select all

00:37:23.404556 Pausing VM execution, reason 'host suspend'
00:37:23.791318 Changing the VM state from 'RUNNING' to 'SUSPENDING'
00:37:28.327990 PDMR3Suspend: 4 297 111 547 ns run time
00:37:28.328037 Changing the VM state from 'SUSPENDING' to 'SUSPENDED'
00:37:28.328100 Console: Machine state changed to 'Paused'
00:37:28.511045 DarwinDisableGlobalHotKeys: Unexpected enmMode=3

there is nothing else after that.... and it shows Aborted... so if I run it again, it just starts normally (loose everything I had open - not saved)

The Win 7 log looks like this: (same sleep of my computer)

Code: Select all

11:09:15.753031 Pausing VM execution, reason 'host suspend'
11:09:15.775882 Changing the VM state from 'RUNNING' to 'SUSPENDING'
11:09:16.188929 AIOMgr: Endpoint for file '/Users/Palace/VirtualBox VMs/Windoze7/Snapshots/{31be60ca-481c-49a3-a536-18e33a709844}.vdi' (flags 000c0781) created successfully
11:09:16.325952 PDMR3Suspend: 550 023 386 ns run time
11:09:16.325982 Changing the VM state from 'SUSPENDING' to 'SUSPENDED'
11:09:16.326026 Console: Machine state changed to 'Paused'
11:09:16.328584 DarwinDisableGlobalHotKeys: Unexpected enmMode=3
11:10:42.156871 NAT: DNS servers changed, triggering reconnect
11:10:46.935410 Resuming VM execution, reason 'host resume'
11:10:46.935487 Changing the VM state from 'SUSPENDED' to 'RESUMING'
11:10:47.253136 AIOMgr: Endpoint for file '/Users/Palace/VirtualBox VMs/Windoze7/Snapshots/{31be60ca-481c-49a3-a536-18e33a709844}.vdi' (flags 000c0723) created successfully
11:10:47.773247 NAT: Link down
11:10:47.773289 Changing the VM state from 'RESUMING' to 'RUNNING'
11:10:47.773311 Console: Machine state changed to 'Running'
11:10:47.987643 GUI: UIMachineLogicFullscreen::sltMachineStateChanged:Machine-state changed from 'paused' to 'running': Adjust machine-window 

so win 7 resumes, but win XP aborts...

Any help will be appreciated.

Thank you.

[mpack]

You have an execution cap of 80% set. This is a valid feature, but I must admit that I'm suspicious of it, because I rarely see it used. Why did you use it?

There seems to be a lot of strange USB activity, e.g. a whole screenful of "USB Suspended | USB Operational". What USB device do you have connected? Perhaps this is related to my first point.

The above sequence ends with the entire VM being suspended, and then the log is truncated - did you grab the log while the VM was still running?

[Palpaz]

I think I moved to 80% because when Windows Freeze I didn't want my Mac to freeze (or that's what I thought Execution Cap does..) What it really does? What % should I put it?

I grabbed the log when it said ABORTED... then if I click Start, it starts windows again, from scratch. It doesn't even complain that I turned off without properly turning off or that there was a problem and if I want to start in safe mode.. nothing... just starts again.

I noticed the USB activity... the USB Suspend /USB Operational... but since this is my first time looking at logs, I didn't know if it was something normal to keep it alive or something. All that activity happens, while I'm doing nothing... and If I connect something it shows when I do, with no problem (and the device works fine - I'm connecting usb-serial ports)

like this:
00:01:46.324266 EHCI: USB Operational
00:01:47.107057 EHCI: USB Suspended
00:02:06.457301 EHCI: USB Operational
00:02:07.025754 EHCI: USB Suspended
00:02:20.886098 VUSB: Attached '00007fa52be172c0[proxy 03eb:2104]' to port 2
00:02:21.186984 VUSB: Attached '00007fa52b854c80[proxy 067b:2303]' to port 3
00:02:21.296496 VUSB: Attached '00007fa5296702c0[proxy 067b:2303]' to port 4
00:02:24.991847 EHCI: USB Operational
00:02:25.892104 EHCI: USB Suspended
00:02:35.136686 EHCI: USB Operational
00:02:36.107384 EHCI: USB Suspended

[mpack]

I would put the CPU cap back to 100%. You have only given the guest one of your hosts two cores, so there's no way the guest can starve the host of CPU entirely.

If practical, I'd like you to use the XP guest for a while with USB support disabled in the USB settings (and of course the USB device not attached). The goal is to verify that the odd USB behaviour is relevant.

Can you tell me what the USB serial device is? I'm wondering if the device itself is... dodgy, in driver terms. I.e. going to a power down state with far too short a timeout. This would certainly kill throughput, but of course nothing should cause a VM abort without even a guru meditation error.

[socratis]

According to the Linux-USB website:

• 03eb:2104 is from 'Atmel', an 'AVR ISP mkII', which hints to an Audio Video Recorder?
• 067b:2303 is from 'Bridge Information', no more information given.

The device from Atmel returns a lot of results about buggy behavior, so mpack's comment about a dodgy device may be right on the money...

[mpack]

03eb:2104 is from 'Atmel', an 'AVR ISP mkII', which hints to an Audio Video Recorder?

Not audio, that's an "in system programmer (ISP)", i.e. a debug dongle, similar to a JTAG dongle, designed for AVR, which is a type of embedded microcontroller. Perhaps you've heard of the Arduino, which uses AVR.

I have a couple of AVRISPmkIIs myself. Most likely this will not turn out to be the genuine Atmel device (which is long retired and replaced by more expensive alternatives), this will be a Chinese clone relying on out of date drivers... and yes, this is the sort of thing I had in mind.

[socratis]

Perhaps you've heard of the Arduino, which uses AVR.

Ah, so that's what that thing is! Thanks Don!

[Palpaz]

Thank you for your help.

Yes it's a programmer for Atmel, but I don't have it always connected, and still have same problem, and the log looks the same when I don't have anything connected as in "Suspended / operational" activity...

I confirmed that every time my Mac sleeps, it causes the "Aborted" status on Windows XP. Even if I'm running win7 and XP at the same time, after sleep the XP one is aborted and win7 is running back normally.

I tried this:

After a clean restart of my mac, and without running Win7.

First, I Started again the WindowsXP VM (only change was execution cap to 100%) and did a PAUSE from the VB menu, and then release the pause and it worked... didi it twice with no problem, and then a normal shutdown from windows. Thats in one of the Logs I'm attaching.

Second, I disabled USB (uncheck "Enable USB controller" from PORTS/USB), and started (after another clean restart of my mac) then I forced a sleep on my Mac, and it aborted again. That's on the other Log attached.

[michaln]

You have some external audio device, don't you. See viewtopic.php?f=8&t=84166 and viewtopic.php?f=8&t=84190

Either use a current test build (probably preferable), downgrade, or disable audio for your VM.

[mpack]

Well, that certainly makes things clearer.

00:01:58.805697 Pausing VM execution, reason 'host suspend'
00:01:58.805820 Changing the VM state from 'RUNNING' to 'SUSPENDING'
00:01:58.935634 PDMR3Suspend: 129 762 235 ns run time
00:01:58.935937 Changing the VM state from 'SUSPENDING' to 'SUSPENDED'
00:01:58.935979 Console: Machine state changed to 'Paused'

So, it got all the way to a paused state and then presumably the VM aborted, but I can't say why since I'm not a Mac user. I'd guess that if the Mac was closing the VirtualBox app then that would explain it. Did you get an OS X update recently? Does OS X have an option to leave app xxx running when the OS is suspended?

[frank]

For us it would be very helpful if you could try the most recent 5.1 Mac OS X test build and confirm that it fixes your problem. In general you can treat the 5.1.x test builds as very stable.

[michaln]

A crash log from OS X would shed some light on the issue.

What I can say with certainty is that VirtualBox 5.1.26 r117224 on OS X crashes if an audio device is changed at VM runtime. Sleep/resume may trigger intermittent changes.

[Palpaz]

Well, that certainly makes things clearer.

00:01:58.805697 Pausing VM execution, reason 'host suspend'
00:01:58.805820 Changing the VM state from 'RUNNING' to 'SUSPENDING'
00:01:58.935634 PDMR3Suspend: 129 762 235 ns run time
00:01:58.935937 Changing the VM state from 'SUSPENDING' to 'SUSPENDED'
00:01:58.935979 Console: Machine state changed to 'Paused'

Yes, that's the last thing I see on the logs when it goes to aborted. I'm not sure about the option to leave app running, but I know that if I have both: Win7 and WinXP machines running and my Mac sleeps, Win7 "wakes up" but XP crashes... why would OS X selecting XP to crash.

[Palpaz]

You have some external audio device, don't you.

Either use a current test build (probably preferable), downgrade, or disable audio for your VM.

I did a downgrade to Version 5.1.22 r115126 (Qt5.6.2), (that's the last one I was using before the upgrade to 5.1.26 and had it already on my Downloads folder) and ran the VM without changing anything on Settings, and put my Mac to sleep. When it woke up, it shows Paused momentarily and then Running!! it worked!

Here is the Log.

I'm not aware of having any external audio devices btw...

Ok. for now, I won't upgrade... if you need more tests from me to fix the problem, let me know.

Thank you.

[mpack]

It would be very helpful if you gave something back to the project by trying the test build as Frank requested. Reverting to some random older version doesn't really move us forward.