Starting VBox from Windows 10 64 bit host

Discussions about using Solaris guests in VirtualBox.

Starting VBox from Windows 10 64 bit host

Postby matdave » 24. Dec 2015, 10:46

The guest, whatever version windows, linux or solaris will work for a few weeks then fail, i have to restart the PC change some ethernet adapter property usually I toggle ipv6 enabled and then virtualbox guest starts ok. This cycle repeats

The attached files shoiw the error screenshots, first error1 then eventually error2


the log file is :

VirtualBox VM 5.0.10 r104061 win.amd64 (Nov 10 2015 16:56:18) release log
00:00:05.796561 Log opened 2015-12-24T08:26:12.194491400Z
00:00:05.796562 Build Type: release
00:00:05.796566 OS Product: Windows 10
00:00:05.796567 OS Release: 10.0.10240
00:00:05.796568 OS Service Pack:
00:00:05.951360 DMI Product Name: OptiPlex 755
00:00:05.955681 DMI Product Version:
00:00:05.955692 Host RAM: 8061MB total, 6569MB available
00:00:05.955694 Executable: C:\Program Files\Oracle\VirtualBox\VirtualBox.exe
00:00:05.955695 Process ID: 4312
00:00:05.955695 Package type: WINDOWS_64BITS_GENERIC
00:00:06.048629 Installed Extension Packs:
00:00:06.048688 Oracle VM VirtualBox Extension Pack (Version: 5.0.10 r104061; VRDE Module: VBoxVRDP)
00:00:06.063007 Console: Machine state changed to 'Starting'
00:00:06.065691 GUI: UIMediumEnumerator: Medium-enumeration finished!
00:00:06.372775 SUP: Loaded VMMR0.r0 (C:\Program Files\Oracle\VirtualBox\VMMR0.r0) at 0xfffff800fe1d0000 - ModuleInit at fffff800fe1f1cc0 and ModuleTerm at fffff800fe1f21b0 using the native ring-0 loader
00:00:06.372818 SUP: VMMR0EntryEx located at fffff800fe1f4be0 and VMMR0EntryFast at fffff800fe1f28f0
00:00:06.372824 SUP: windbg> .reload /f C:\Program Files\Oracle\VirtualBox\VMMR0.r0=0xfffff800fe1d0000
00:00:06.380791 Guest OS type: 'Solaris_64'
00:00:06.393699 Installed Drivers:
00:00:06.415537 C:\WINDOWS\System32\drivers\VBoxNetAdp6.sys (Version: 5.0.10.4061)
00:00:06.431920 C:\WINDOWS\system32\DRIVERS\VBoxNetLwf.sys (Version: 5.0.10.4061)
00:00:06.456486 C:\WINDOWS\system32\DRIVERS\VBoxUSBMon.sys (Version: 5.0.10.4061)
00:00:06.492826 C:\WINDOWS\system32\DRIVERS\VBoxDrv.sys (Version: 5.0.10.4061)
00:00:06.497052 fHMForced=true - Lots of RAM
00:00:06.497081 fHMForced=true - 64-bit guest
00:00:06.557158 File system of 'F:\VIRTUAL BOX MACHINES\sol_zfs2\Snapshots' (snapshots) is ntfs
00:00:06.557179 File system of 'F:\VIRTUAL BOX MACHINES\sol_zfs2\sol_zfs2.vdi' is ntfs
00:00:06.579674 File system of 'F:\VIRTUAL BOX MACHINES\sol_zfs2\utility1.vdi' is ntfs
00:00:06.601505 File system of 'F:\VIRTUAL BOX MACHINES\sol_zfs2\d1.vdi' is ntfs
00:00:06.621849 File system of 'F:\VIRTUAL BOX MACHINES\sol_zfs2\d2.vdi' is ntfs
00:00:06.700233 File system of 'F:\VIRTUAL BOX MACHINES\sol_zfs2\d3.vdi' is ntfs
00:00:06.713206 File system of 'F:\VIRTUAL BOX MACHINES\sol_zfs2\d4.vdi' is ntfs
00:00:06.726078 File system of 'F:\VIRTUAL BOX MACHINES\sol_zfs2\d5.vdi' is ntfs
00:00:06.738976 File system of 'F:\VIRTUAL BOX MACHINES\sol_zfs2\d6.vdi' is ntfs
00:00:06.741353 File system of 'F:\VIRTUAL BOX MACHINES\sol-10-u11-ga-x86-dvd.iso' (DVD) is ntfs
00:03:40.335913 NetworkAttachmentType_Bridged: Failed to get NetCfg, hrc=EPT_S_NOT_REGISTERED 0x800106D9 (0x800106d9)
00:03:40.336077 AssertLogRel F:\tinderbox\win-5.0\src\VBox\Main\src-client\ConsoleImpl2.cpp(4897) int __cdecl Console::i_configNetwork(const char *,unsigned int,unsigned int,struct INetworkAdapter *,struct CFGMNODE *,struct CFGMNODE *,struct CFGMNODE *,bool,bool): !FAILED(hrc)

00:03:40.336085 hrc=EPT_S_NOT_REGISTERED 0x800106D9
00:03:40.337320 VMSetError: F:\tinderbox\win-5.0\src\VBox\VMM\VMMR3\VM.cpp(367) int __cdecl VMR3Create(unsigned int,const struct VMM2USERMETHODS *,void (__cdecl *)(struct UVM *,void *,int,const char *,unsigned int,const char *,const char *,char *),void *,int (__cdecl *)(struct UVM *,struct VM *,void *),void *,struct VM **,struct UVM **); rc=VERR_MAIN_CONFIG_CONSTRUCTOR_COM_ERROR
00:03:40.337326 VMSetError: The configuration constructor in main failed due to a COM error. Check the release log of the VM for further details.
00:03:40.337969 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={The configuration constructor in main failed due to a COM error. Check the release log of the VM for further details. (VERR_MAIN_CONFIG_CONSTRUCTOR_COM_ERROR)}, preserve=false aResultDetail=0
00:03:40.338408 Console: Machine state changed to 'PoweredOff'
00:03:40.396610 Power up failed (vrc=VERR_MAIN_CONFIG_CONSTRUCTOR_COM_ERROR, rc=E_FAIL (0X80004005))
00:03:40.618176 GUI: UIMachineViewNormal::resendSizeHint: Restoring guest size-hint for screen 0 to 1680x985
00:03:40.618259 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={7303a66d-433b-25a4-f9a8-fcadf87e0c2a} aComponent={DisplayWrap} aText={The console is not powered up}, preserve=false aResultDetail=0
Attachments
error2.jpg
error2.jpg (38.32 KiB) Viewed 2493 times
error1.jpg
error1.jpg (14.27 KiB) Viewed 2493 times
matdave
 
Posts: 4
Joined: 22. May 2012, 07:16

Re: Starting VBox from Windows 10 64 bit host

Postby mpack » 24. Dec 2015, 11:13

Please provide logs as zipped attachments, not pasted text.

I suspect you have not installed VirtualBox properly: "F:\VIRTUAL BOX MACHINES" is not the typical home folder for VMs.
mpack
Site Moderator
 
Posts: 25453
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: Starting VBox from Windows 10 64 bit host

Postby matdave » 24. Dec 2015, 12:46

Zipped logs and attached

I have run virtualbox on XP, Windows 7 and Linux and always placed Virtual Machines in a folder structured along with my development activities and never had this issue before, it is only since moving to Windows 10 as the host OS.

From looking at the log files it seems to be related to the network configuration, which ties in with it working after enableing/disabling the IPV6 properties for the network adapter
Attachments
logs.zip
(69.93 KiB) Downloaded 13 times
matdave
 
Posts: 4
Joined: 22. May 2012, 07:16

Re: Starting VBox from Windows 10 64 bit host

Postby mpack » 24. Dec 2015, 12:59

I don't need 50 copies of the log, unless you want to pay for my time to go through them all! Just one relevant log is enough.

Plus you posted in "Windows Guests" though your guest actually seems to be Solaris. Moving this topic to "Solaris guests".

I see nothing amiss in VBox.log - the VM runs for 5 minutes and is then shut down. Are you sure your problem is VM related at all?
mpack
Site Moderator
 
Posts: 25453
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: Starting VBox from Windows 10 64 bit host

Postby matdave » 24. Dec 2015, 14:27

Hi

It is never my intention to take up others valuable time, but I started this post thinking this was a forum where I might find people who have come across similar issues.

As I stated initially the problem appears every few weeks and is resolved by either disabling or enabling IPV6 on the ethernet adapter which makes me think of Windows 10/VirtualBox integration. It is also agnostic of the Guest OS (Windows, Linux or Solaris) - so you are correct in that it may have been better in a Windows 10 host sub-forum. Initially I sent the text from the log that shows the issue, it seems to reference two c++ files. I only included all the logs, as you suggested, in a zip thinking that may provide a better chance at seeing what the problem may be - VBox.log.3 and Vbox.log may be all that was required.

You say that the unusual location of virtual machines might cause an issue, if this was the case then I would expect the fault to appear each time.
matdave
 
Posts: 4
Joined: 22. May 2012, 07:16

Re: Starting VBox from Windows 10 64 bit host

Postby mpack » 24. Dec 2015, 14:39

matdave wrote:You say that the unusual location of virtual machines might cause an issue

That is not what I said. I remarked that your VM location was unusual, which could imply that you have not installed it properly, or perhaps you are using an unsupported fork such as "Portable VirtualBox". If you assure me that neither of those is the case then the matter ends there.

As to the log, I am not prepared to wade through a whole pile of the things. What I expected from you was a single log from a session which exhibited the problem you describe.
mpack
Site Moderator
 
Posts: 25453
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP


Return to Solaris Guests

Who is online

Users browsing this forum: No registered users and 2 guests