I'm receiving an error when try to start a VM. The log file show this status
00:00:05.979451 Console: Machine state changed to 'PoweredOff'
00:00:06.551645 GUI: Passing request to close Runtime UI from machine-logic to UI session.
00:00:06.918674 GUI: UIMachineViewNormal::resendSizeHint: Restoring guest size-hint for screen 0 to 1299x669
00:00:06.918895 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={4680b2de-8690-11e9-b83d-5719e53cf1de} aComponent={DisplayWrap} aText={The console is not powered up}, preserve=false aResultDetail=0
00:00:06.919491 GUI: Aborting startup due to invalid machine state detected: 1
Any suggestion?
Thx in advance
[Solved] Virtual machine does not start
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Virtual machine does not start
The whole log is usually necessary to start diagnosing a problem.
Please zip the log file, and post the zip file, using the forum's Upload Attachment tab.
Please zip the log file, and post the zip file, using the forum's Upload Attachment tab.
Re: Virtual machine does not start
Here is the log file. Thx again
- Attachments
-
- wxplog.zip
- log file
- (47.79 KiB) Downloaded 10 times
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Virtual machine does not start
You are very close to exhausting available RAM on this host. Too close.
OTOH, your graphics RAM allocation is pathetically small. Don't you get a incorrect settings warning for this? I would increase to 64MB.
I see other errors in the log.
It's a pity you only gave XP one core when you installed it, since your host can afford two. Getting XP to recognize multiple cores after installation is not trivial.
XP really doesn't need 4GB RAM. 512MB was a good spec back in the day. Certainly 1024MB or 2048MB would be luxury.00:00:03.668689 Host RAM: 7806MB (7.6GB) total, 4200MB (4.1GB) available
...
00:00:03.998791 RamSize <integer> = 0x0000000100000000 (4 294 967 296, 4 096 MB, 4.0 GB)
00:00:03.999610 VRamSize <integer> = 0x0000000001000000 (16 777 216, 16 MB)
OTOH, your graphics RAM allocation is pathetically small. Don't you get a incorrect settings warning for this? I would increase to 64MB.
I see other errors in the log.
And finally the big one.00:00:04.375264 Console: VM runtime error: fatal=false, errorID=BrokenSharedFolder message="The shared folder 'ms-w' could not be set up: Shared folder path '/media/jluishg/ms-w' does not exist on the host.
I believe this means that you have another hypervisor enabled on your host, fighting for control of VT-x. On a Linux host I guess that would be KVM.00:00:04.451100 Console: Machine state changed to 'GuruMeditation'
00:00:04.453310 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:00:04.453313 !!
00:00:04.453314 !! VCPU0: Guru Meditation -79 (VERR_INVALID_STATE)
00:00:04.453324 !!
It's a pity you only gave XP one core when you installed it, since your host can afford two. Getting XP to recognize multiple cores after installation is not trivial.
Re: Virtual machine does not start
Hi, first of all thanks for your comments. I changed the RAM settings and solve the main problem. I found that "Multipass" was running a virtual machine. I stopped and VBox works fine. Thanks again.
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Virtual machine does not start
Thanks for reporting back.