[Resolved] Resuming Windows 10 guest (64 bit) fails with "power up progress issue detected"

This is for discussing general topics about how to use VirtualBox.
Post Reply
Aethalides
Posts: 2
Joined: 23. Mar 2019, 18:49
Primary OS: Linux other
VBox Version: PUEL
Guest OSses: Linux,pfSense,Windows

[Resolved] Resuming Windows 10 guest (64 bit) fails with "power up progress issue detected"

Post by Aethalides »

Hi

As explained in the title, whenever I try to resume my Windows 10 guest machine I get an error message as detailed in this ticket. After discarding saved state it always boots correctly.

Anybody have any ideas of pointers?

Thank you

---
Host: Arch Linux 64 bit
Guest: Windows 10, 64 Bit
Guest additions installed

Guest Machine settings:
Base memory: 8GB
Processors: 4
Boot order: optical, hard disk
Acceleration: VT-x/AMD-V, Nested Paging, PAE/NX, KVM Paravirtualization
Video Memory: 256MB
Graphics Controller: VBoxVGA
Storage controller: SAS
Audio host driver: pulseaudio
Controller: Intel HD Audio
Network adapter 1: Intel PRO/1000 MT Server (NAT)
USB Controller: xHCI

version numbers:
local/virtualbox 6.0.4-4
local/virtualbox-ext-oracle 6.0.4-1
local/virtualbox-ext-vnc 6.0.4-4
local/virtualbox-guest-iso 6.0.4-1
local/virtualbox-host-dkms 6.0.4-4

Code: Select all

00:00:23.172204 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={The virtual machine is being powered down}, preserve=false aResultDetail=0
00:00:23.172365 GUI: UIMachineView::storeGuestSizeHint: Storing guest-screen size-hint for screen 0 as 1920x942
00:00:23.180315 NAT: Zone(nm:mbuf_cluster, used:0)
00:00:23.180564 NAT: Zone(nm:mbuf_packet, used:0)
00:00:23.180572 NAT: Zone(nm:mbuf, used:0)
00:00:23.180576 NAT: Zone(nm:mbuf_jumbo_pagesize, used:0)
00:00:23.180803 NAT: Zone(nm:mbuf_jumbo_9k, used:0)
00:00:23.180930 NAT: Zone(nm:mbuf_jumbo_16k, used:0)
00:00:23.180998 NAT: Zone(nm:mbuf_ext_refcnt, used:0)
00:00:23.181014 E1000#0: Interrupt attempts: 0
00:00:23.181017 E1000#0: Interrupts raised : 0
00:00:23.181020 E1000#0: Interrupts lowered: 0
00:00:23.181023 E1000#0: ICR outside ISR   : 0
00:00:23.181025 E1000#0: IMS raised ints   : 0
00:00:23.181028 E1000#0: Interrupts skipped: 0
00:00:23.181031 E1000#0: Masked interrupts : 0
00:00:23.181034 E1000#0: Early interrupts  : 0
00:00:23.181037 E1000#0: Late interrupts   : 0
00:00:23.181039 E1000#0: Lost interrupts   : 0
00:00:23.181042 E1000#0: Interrupts by RX  : 0
00:00:23.181045 E1000#0: Interrupts by TX  : 0
00:00:23.181047 E1000#0: Interrupts by ICS : 0
00:00:23.181050 E1000#0: Interrupts by RDTR: 0
00:00:23.181052 E1000#0: Interrupts by RDMT: 0
00:00:23.181055 E1000#0: Interrupts by TXQE: 0
00:00:23.181058 E1000#0: TX int delay asked: 0
00:00:23.181074 E1000#0: TX delayed:         0
00:00:23.181078 E1000#0: TX delay expired:   0
00:00:23.181081 E1000#0: TX no report asked: 0
00:00:23.181083 E1000#0: TX abs timer expd : 0
00:00:23.181086 E1000#0: TX int timer expd : 0
00:00:23.181089 E1000#0: RX abs timer expd : 0
00:00:23.181092 E1000#0: RX int timer expd : 0
00:00:23.181095 E1000#0: TX CTX descriptors: 0
00:00:23.181097 E1000#0: TX DAT descriptors: 0
00:00:23.181100 E1000#0: TX LEG descriptors: 0
00:00:23.181103 E1000#0: Received frames   : 0
00:00:23.181106 E1000#0: Transmitted frames: 0
00:00:23.181109 E1000#0: TX frames up to 1514: 0
00:00:23.181112 E1000#0: TX frames up to 2962: 0
00:00:23.181114 E1000#0: TX frames up to 4410: 0
00:00:23.181117 E1000#0: TX frames up to 5858: 0
00:00:23.181120 E1000#0: TX frames up to 7306: 0
00:00:23.181123 E1000#0: TX frames up to 8754: 0
00:00:23.181126 E1000#0: TX frames up to 16384: 0
00:00:23.181129 E1000#0: TX frames up to 32768: 0
00:00:23.181132 E1000#0: Larger TX frames    : 0
00:00:23.181134 E1000#0: Max TX Delay        : 0
00:00:23.210384 GIM: KVM: Resetting MSRs
00:00:23.213474 Changing the VM state from 'DESTROYING' to 'TERMINATED'
00:00:23.214985 Console: Machine state changed to 'Saved'
00:00:23.803413 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Failed to load unit 'lsilogicsas' (VERR_SSM_LOADED_TOO_LITTLE)}, preserve=false aResultDetail=-1833
00:00:23.805916 Power up failed (vrc=VERR_SSM_LOADED_TOO_LITTLE, rc=NS_ERROR_FAILURE (0X80004005))
00:00:24.306558 GUI: UIMachineViewNormal::adjustGuestScreenSize: Adjust guest-screen size if necessary
00:00:24.306575 GUI: Aborting startup due to power up progress issue detected...
Last edited by socratis on 24. Mar 2019, 21:27, edited 1 time in total.
Reason: Marked as [Resolved].
socratis
Site Moderator
Posts: 27330
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: Resuming Windows 10 guest (64 bit) fails with "power up progress issue detected"

Post by socratis »

Aethalides wrote:After discarding saved state it always boots correctly.
Take a look at the Known Issues in the "Discuss the 6.0.0 release" post. I think you might have been hit by a couple of restore-saved-state tickets that are still open...
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.
Aethalides
Posts: 2
Joined: 23. Mar 2019, 18:49
Primary OS: Linux other
VBox Version: PUEL
Guest OSses: Linux,pfSense,Windows

Re: Resuming Windows 10 guest (64 bit) fails with "power up progress issue detected"

Post by Aethalides »

After reading the suggested thread and many others I can confirm that killing the SAS controller from the machine and replacing it with a SATA one fixes the behaviour I encountered.

I am now able to successfully save and resume my Windows 10 guest.
socratis
Site Moderator
Posts: 27330
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: Resuming Windows 10 guest (64 bit) fails with "power up progress issue detected"

Post by socratis »

So, it seems that you were bitten by https://www.virtualbox.org/ticket/18263 after all...
Glad you got it going, marking as [Resolved].
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.
Post Reply