Guest Not Booting

[madurham]

I have a Linux VM that isn't booting.
I run have a batch file that I use to launch the VM and apply restrictions on the settings etc. This batch file runs fine and the VM window opens with the Ubuntu icon. Then while still black the window closes again without presenting any error messages.
I am deploying this through SCCM to two classrooms of ~25 machines each and it's working fine in the other room. I assumed it has something to do with the hardware in the room (Dell 740/760, 4GB RAM, 240GB SSD) but I have a Windows guest that is deployed with the same process and works fine.
I've tried copying the files from a working PC, uninstalling and reinstalling VBox but I keep getting the same issue. I'm wondering what I'm missing or what else I can try.

VirtualBox version 4.3.30
Extensions installed
Attached the log files from one of the PCs

[loukingjr]

With the VM fully shut down, right click it in GUI. Select "Show Log" and save "VBox.log" to a zip file. Attach the zip here.

[Perryg]

VirtualBox VM 4.3.30 r101610 win.amd64 (Jul 10 2015 12:21:05) release log
00:00:01.214300 Oracle VM VirtualBox Extension Pack (Version: 4.3.32 r103443; VRDE Module: VBoxVRDP)

The Extension Pack *must match the running version of VirtualBox. Fix this first and if that does not solve your issue the post the new log file ( as an attachment ) after shutting down the guest.

Code: Select all

00:00:01.896871     Host path 'N:\', map name 'N_DRIVE', writable, automount=true, create_symlinks=false, missing=true
00:00:01.896896 ERROR [COM]: aRC=E_INVALIDARG (0x80070057) aIID={8ab7c520-2442-4b66-8d74-4ff1e195d2b6} aComponent={Console} aText={Shared folder path 'N:\' does not exist on the host}, preserve=false
00:00:01.897036 Console: VM runtime error: fatal=false, errorID=BrokenSharedFolder message="The shared folder 'N_DRIVE' could not be set up: Shared folder path 'N:\' does not exist on the host.
00:00:01.897038 The shared folder setup will not be complete. It is recommended to power down the virtual machine and fix the shared folder settings while the machine is not running"

Also you need to fix the above.

[madurham]

With the VM fully shut down, right click it in GUI. Select "Show Log" and save "VBox.log" to a zip file. Attach the zip here.

Is there something wrong with the one I attached to my original post?

[loukingjr]

Hmmm, for some reason when I downloaded the attachment the unzipped it the vbox.logs weren't actually logs. The start up log was. Is why I asked for a new log.

Looks like I have to fix something.

[madurham]

VirtualBox VM 4.3.30 r101610 win.amd64 (Jul 10 2015 12:21:05) release log
00:00:01.214300 Oracle VM VirtualBox Extension Pack (Version: 4.3.32 r103443; VRDE Module: VBoxVRDP)

The Extension Pack *must match the running version of VirtualBox. Fix this first and if that does not solve your issue the post the new log file ( as an attachment ) after shutting down the guest.

Code: Select all

00:00:01.896871     Host path 'N:\', map name 'N_DRIVE', writable, automount=true, create_symlinks=false, missing=true
00:00:01.896896 ERROR [COM]: aRC=E_INVALIDARG (0x80070057) aIID={8ab7c520-2442-4b66-8d74-4ff1e195d2b6} aComponent={Console} aText={Shared folder path 'N:\' does not exist on the host}, preserve=false
00:00:01.897036 Console: VM runtime error: fatal=false, errorID=BrokenSharedFolder message="The shared folder 'N_DRIVE' could not be set up: Shared folder path 'N:\' does not exist on the host.
00:00:01.897038 The shared folder setup will not be complete. It is recommended to power down the virtual machine and fix the shared folder settings while the machine is not running"

Also you need to fix the above.

Ah, I didn't realise I'd installed the wrong extensions, doh! I'll sort that out now.
The drive mapping issue has never prevented the guest from booting before.

[madurham]

Hmmm, for some reason when I downloaded the attachment the unzipped it the vbox.logs weren't actually logs. The start up log was. Is why I asked for a new log.

Looks like I have to fix something.

I just had a look. They are just files with a .log.1 extension. If you remove the number and the '.' it should open fine.

[loukingjr]

Yes, I know. I just don't remember having the issue before.

[madurham]

I've corrected the extension version and mapped a drive for the host. Still no luck.
Attached .zip of new logs.

[madurham]

This time I also got the attached error on my batch file.
I've encountered it before but it didn't prevent the guest from booting.

[Perryg]

The log file is clean now and does not show an actual issue. I would investigate your script.

If it were me I would reboot the actual guest and try to get it working normally before you try to use a custom script. That way you can at least remove one thing from the equation to try to track down the underlying issue/s.

[scottgus1]

The error in the batch file says the guest you're trying to register has the same identifier code (the UUID) as another guest. Did you make a copy of an existing guest by the usual Windows folders methods and try to register the new copy? If so, that would cause the shown error. To make a copy of a guest that Virtualbox can use you have to clone the guest within Virtualbox.

Alternately, if someone deleted the guest from the machine without unregistering it, or you copied the guest back from a backup to reset it but the old guest was still registered, trying to re-register the guest will cause the error.

[madurham]

The error in the batch file says the guest you're trying to register has the same identifier code (the UUID) as another guest. Did you make a copy of an existing guest by the usual Windows folders methods and try to register the new copy? If so, that would cause the shown error. To make a copy of a guest that Virtualbox can use you have to clone the guest within Virtualbox.

Alternately, if someone deleted the guest from the machine without unregistering it, or you copied the guest back from a backup to reset it but the old guest was still registered, trying to re-register the guest will cause the error.

The error didn't happen the first time I ran the script yesterday so would it be just because it's already registered and it'll be safe to remove the registervm line from the script after the first time?

[madurham]

The log file is clean now and does not show an actual issue. I would investigate your script.

If it were me I would reboot the actual guest and try to get it working normally before you try to use a custom script. That way you can at least remove one thing from the equation to try to track down the underlying issue/s.

I'll try that today.

[madurham]

Running the VM without a script has the same problem.