virtualbox.org

I'm running Virtualbox 5.1.28 on macOS Sierra 10.12.6 and now Windows 10 VM won't start. I've included the log. I'm able to start Windows 10 VM on Debug Mode, but nothing else. Is there some way to fix this? The VM used to work just fine.

00:00:01.184772 Host RAM: 16384MB (16.0GB) total, 2215MB (2.1GB) available
00:00:01.292999 RamSize <integer> = 0x0000000180000000 (6 442 450 944, 6 144 MB, 6 GB)

You are assigning memory to your guest, that you do not have available. Either close some applications on the host, buy more RAM for the host, or reduce the amount of RAM assigned to the guest.

May I suggest a couple of applications, so that you know what's available on your system at any given time? What I do, is to have several monitor tools running at all times. Your preference may vary, but you can use either of them (I use all of them concurrently):

X Resource Graph.
Memory Monitor.
Built-in Activity monitor.

OK. I had multiple issues then. Now I made sure I have enough memory and it still gets stuck on splash screen. I have never had any memory issues before and I think this problem started after my macbook pro ran out of the battery and shutdown. Here is a new log.

I should have mentioned it in my first reply. Do you mind replacing the logs that you have with a ZIPPED version? It helps save a (virtual) tree or two...

Thanks.

A wild, probably inaccurate guess here - could it be the Win10 KB4041676 (1703) bug? I've read a few articles where M$ acknowledges the update bug but claim Home users don't have any trouble during the update process. If you have a backup, I would try to find a way of reverting to a 'good state' then try to update the OS at a later date.

Thee are some entries in the log that I can't say I've seen before:

Code: Select all

00:00:20.388753 VMMDev: Guest Log:  >>**** Start Dump VidPn Path ****>>
00:00:20.388806 VMMDev: Guest Log: VidPnSourceId(0),  VidPnTargetId(0)
00:00:20.388835 VMMDev: Guest Log: Source NOT Pinned
00:00:20.388916 VMMDev: Guest Log: Target NOT Pinned
00:00:20.389761 VMMDev: Guest Log:   --Transformation: Scaling(D3DKMDT_VPPS_UNPINNED), ScalingSupport(1), Rotation(D3DKMDT_VPPR_UNPINNED), RotationSupport(17)--Importance(D3DKMDT_VPPI_PRIMARY), TargetColorBasis(D3DKMDT_CB_UNINITIALIZED), Content(D3DKMDT_VPPC_NOTSPECIFIED), VFA_TL_O(0X0), VFA_BR_O(0X0), CCDynamicRanges: FirstChannel(0), SecondChannel(0), ThirdChannel(0), FourthChannel(0)| CProtection: Type(D3DKMDT_VPPMT_NOPROTECTION), TODO| GammaRamp: Type(D3DDDI_GAMMARAMP_DEFAULT), DataSize(0), TODO: dump the rest
00:00:20.389788 VMMDev: Guest Log:  <<**** Stop Dump VidPn Path ****<<
00:00:20.389807 VMMDev: Guest Log:   >>>+++SourceMode Set for Source(0)+++
00:00:20.389901 VMMDev: Guest Log:   <<<+++End Of SourceMode Set for Source(0)+++
00:00:20.389973 VMMDev: Guest Log:   >>>---TargetMode Set for Target(0)---
00:00:20.390011 VMMDev: Guest Log:   <<<---End Of TargetMode Set for Target(0)---
00:00:20.390013 VMMDev: Guest Log: ------
00:00:20.390024 VMMDev: Guest Log: MonModeSet: --------
00:00:20.390310 VMMDev: Guest Log:  Tgt[0]
00:00:20.391863 VMMDev: Guest Log: MonitorMode: ID: 1025, VSI: VStd(D3DKMDT_VSS_OTHER), totSize(640X480), activeSize(640X480), VSynch(-2/-2=1), PixelRate(-2), ScanLineOrdering(D3DDDI_VSSLO_PROGRESSIVE), ColorBasis: D3DKMDT_CB_SRGB, Ranges: FirstChannel(8), SecondChannel(8), ThirdChannel(8), FourthChannel(0), MonCapOr: D3DKMDT_MCO_DRIVER, Preference(D3DKMDT_MP_NOTPREFERRED)
00:00:20.394292 VMMDev: Guest Log: MonitorMode: ID: 1026, VSI: VStd(D3DKMDT_VSS_OTHER), totSize(800X600), activeSize(800X600), VSynch(-2/-2=1), PixelRate(-2), ScanLineOrdering(D3DDDI_VSSLO_PROGRESSIVE), ColorBasis: D3DKMDT_CB_SRGB, Ranges: FirstChannel(8), SecondChannel(8), ThirdChannel(8), FourthChannel(0), MonCapOr: D3DKMDT_MCO_DRIVER, Preference(D3DKMDT_MP_NOTPREFERRED)
00:00:20.396255 VMMDev: Guest Log: MonitorMode: ID: 1027, VSI: VStd(D3DKMDT_VSS_OTHER), totSize(1024X768), activeSize(1024X768), VSynch(-2/-2=1), PixelRate(-2), ScanLineOrdering(D3DDDI_VSSLO_PROGRESSIVE), ColorBasis: D3DKMDT_CB_SRGB, Ranges: FirstChannel(8), SecondChannel(8), ThirdChannel(8), FourthChannel(0), MonCapOr: D3DKMDT_MCO_DRIVER, Preference(D3DKMDT_MP_NOTPREFERRED)
00:00:20.397691 VMMDev: Guest Log: MonitorMode: ID: 1028, VSI: VStd(D3DKMDT_VSS_OTHER), totSize(1152X864), activeSize(1152X864), VSynch(-2/-2=1), PixelRate(-2), ScanLineOrdering(D3DDDI_VSSLO_PROGRESSIVE), ColorBasis: D3DKMDT_CB_SRGB, Ranges: FirstChannel(8), SecondChannel(8), ThirdChannel(8), FourthChannel(0), MonCapOr: D3DKMDT_MCO_DRIVER, Preference(D3DKMDT_MP_NOTPREFERRED)
00:00:20.399444 VMMDev: Guest Log: MonitorMode: ID: 1029, VSI: VStd(D3DKMDT_VSS_OTHER), totSize(1280X960), activeSize(1280X960), VSynch(-2/-2=1), PixelRate(-2), ScanLineOrdering(D3DDDI_VSSLO_PROGRESSIVE), ColorBasis: D3DKMDT_CB_SRGB, Ranges: FirstChannel(8), SecondChannel(8), ThirdChannel(8), FourthChannel(0), MonCapOr: D3DKMDT_MCO_DRIVER, Preference(D3DKMDT_MP_NOTPREFERRED)
00:00:20.399470 VMMDev: Guest Log: ------
00:00:20.399791 VMMDev: Guest Log: VBoxMP::VBoxVidPnCofuncModality: WARNING! :vboxVidPnApplyInfoForPathTarget failed Status(0xc01e030b
00:00:20.400443 VMMDev: Guest Log: Modality Info: PivotType(D3DKMDT_EPT_NOPIVOT), SourceId(0xffffffff), TargetId(0xffffffff),
00:00:20.400498 VMMDev: Guest Log: VBoxMP::DxgkDdiEnumVidPnCofuncModality: WARNING! :VBoxVidPnCofuncModality failed Status(0xc01e030b)
00:00:20.401890 VMMDev: Guest Log: VBoxMP::vboxVidPnTargetModeSetFromArray: WARNING! :pfnAddMode failed, Status 0xc01e030b
00:00:20.402400 VMMDev: Guest Log: TargetMode: ID: 1, VSI: VStd(D3DKMDT_VSS_OTHER), totSize(254X77), activeSize(254X77), VSynch(-2/-2=1), PixelRate(-2), ScanLineOrdering(D3DDDI_VSSLO_PROGRESSIVE), Preference(D3DKMDT_MP_NOTPREFERRED)
00:00:20.403169 VMMDev: Guest Log: VBoxMP::vboxVidPnApplyInfoForPathTarget: WARNING! :vboxVidPnTargetModeSetFromArray failed Status(0xc01e030b)
00:00:20.403186 VMMDev: Guest Log: VidPn: ---------

These keep repeating for some time. I honestly can't tell what's going on. Can you describe your setup? Can you simplify your setup as to go to a normal, windowed mode? Can you enable 2D and 3D acceleration? And finally, don't grab the log while the VM is running. If it's stuck, close the window and then grab the log.

Here is a new log after I've closed the window. I can enable HiDPI Output and 2D Video Acceleration although I haven't used them. If I try to enable 3D Acceleration there is a warning of invalid setting that my host machine doesn't support it.

Here are my computer specs:
MacBook Pro (15-inch, 2016)
Processor 2,6 GHz Intel Core i7
Memory 16 GB 2133 MHz LPDDR3
Graphics Radeon Pro 450 2048 MB
Intel HD Graphics 530 1536 MB

daily wrote:If I try to enable 3D Acceleration there is a warning of invalid setting that my host machine doesn't support it.

That's got to be a first! I've never seen a Mac not supporting 3D acceleration! And the error messages that I referred to in my last post? I tracked them down and they seem to originate from the WDDM module of the Guest Additions (GAs), again a problem in the graphics area.

Can you please download a small program called gfxCardStatus? This will tell you if you have the integrated or the discrete graphics card enabled and which process is forcing the discrete card. You can also manually choose to use the discrete GPU. So, try with that, force the Radeon to be used, start VirtualBox and see if you can enable 3D acceleration.

And if you can, please re-install the GAs in your Win10 guest. And finally, right-click on the VM, select Show in Finder. ZIP that .vbox file and upload that as well.

PS. Once you're done with the GAs installation, it's a good idea to eject the GAs CD from the guest's CD drive.

virtualbox.org

Windows 10 VM Stuck on boot screen.

Windows 10 VM Stuck on boot screen.

Re: Windows 10 VM Stuck on boot screen.

Re: Windows 10 VM Stuck on boot screen.

Re: Windows 10 VM Stuck on boot screen.

Re: Windows 10 VM Stuck on boot screen.

Re: Windows 10 VM Stuck on boot screen.

Re: Windows 10 VM Stuck on boot screen.

Re: Windows 10 VM Stuck on boot screen.