Page 1 of 2
Virtual Box 4.2 crash
Posted: 2. May 2013, 22:06
by Skay
Just installed Virtual Box 4.2 on a windows 7 64 bit professional computer. I am trying to run Ubuntu and the when I start the VM it crashes. I have attached the log file. It is a new install on a brand new machine.
Any thoughts on what might be causing this?
Re: Virtual Box 4.2 crash
Posted: 2. May 2013, 22:18
by Perryg
Was the guest shut down (not in saved state)?
Is the abort icon active in the main manager?
Re: Virtual Box 4.2 crash
Posted: 2. May 2013, 22:38
by Skay
The VM machine crashes on startup. Basically we created a new Uduntu VM configure it, start it and it crashes almost immediately.
(Computer has a Intel 3470 processor with 8GB of memory, so I don't think there should be an resource issue)
Re: Virtual Box 4.2 crash
Posted: 2. May 2013, 22:57
by Perryg
VirtualBox VM
4.2.10 r84104 win.amd64 (Mar 15 2013 19:08:54) release log
00:00:00.578279 Oracle VM VirtualBox Extension Pack (Version:
4.2.12 r84980; VRDE Module: VBoxVRDP)
Let's start with this. You have a mismatch with the Extpack and the version of VBox. Either upgrade to version 4.2.12 or download the 4.2.10 Extpack
http://download.virtualbox.org/virtualbox/
Re: Virtual Box 4.2 crash
Posted: 2. May 2013, 23:17
by Skay
I upgraded to Virtualbox version 4.2.12 and ensure Extension pack is 4.2.12 as well. Still crashing immedately
Here are the newly generated logs.
Re: Virtual Box 4.2 crash
Posted: 2. May 2013, 23:26
by Perryg
Code: Select all
00:00:00.542165 Changing the VM state from 'CREATING' to 'CREATED'.
00:00:00.542363 Changing the VM state from 'CREATED' to 'POWERING_ON'.
00:00:00.542481 Changing the VM state from 'POWERING_ON' to 'RUNNING'.
00:00:00.543551 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:00:00.543553 !!
00:00:00.543553 !! Guru Meditation -4014 (VERR_VMX_INVALID_GUEST_STATE)
00:00:00.543581 !!
00:00:00.543610 !!
Did you install the XP guest or did you get it from someone? Plus the first topic said Ubuntu guest not Windows. It would help if we don't jump around until the cause is located.
Is the guest 32 or 64 bit?
Also
From the hosts terminal/command window type
VBoxManage showvminfo <VM Name> --details and post here. Replace <VM Name> with the actual name of the VM. Use " " if the name has a space in it.
Note if the host is Windows you need to be in the directory that has VBoxManage.exe for the command to work.
Re: Virtual Box 4.2 crash
Posted: 2. May 2013, 23:37
by Skay
I apologize for including the Windows VM log files.
The host system is 64-bit and the Guest VM is a 32-bit
Here are the Ubuntu VM log files. This time it started reading the Ubuntu live CD to begin the installation but crashes about 5 seconds later nonetheless.
The host system is Windows so that particular command line syntax is not taking: "VBoxManage is not recognized as an internal command"
Re: Virtual Box 4.2 crash
Posted: 2. May 2013, 23:45
by Perryg
So this log is from where you started and were running the live CD?
If you read the last line I say that for this to work you must be in the folder/directory that actually has VBoxManage for the command to work.
Re: Virtual Box 4.2 crash
Posted: 2. May 2013, 23:48
by Skay
C:\Program Files\Oracle\VirtualBox>VBoxManage showvminfo ubuntu --details
VBoxManage.exe: error: Could not find a registered machine named 'ubuntu'
VBoxManage.exe: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), compo
nent VirtualBox, interface IVirtualBox, callee IUnknown
VBoxManage.exe: error: Context: "FindMachine(Bstr(VMNameOrUuid).raw(), machine.a
sOutParam())" at line 2495 of file VBoxManageInfo.cpp
Re: Virtual Box 4.2 crash
Posted: 2. May 2013, 23:52
by noteirak
Re: Virtual Box 4.2 crash
Posted: 2. May 2013, 23:55
by Skay
C:\Program Files\Oracle\VirtualBox>VBoxManage.exe list vms
"Ubuntu" {db25e4d3-5b08-4b0b-ba74-4cd30b2e0c70}
"Mac ML" {61e695cf-7fac-4a96-8ff9-2b3f387d78f8}
"ubuntuone" {cc8237c1-998a-4808-a535-f0bdac550181}
"WinXP" {22edef00-9e58-4a31-9ae4-070237a171e9}
Re: Virtual Box 4.2 crash
Posted: 3. May 2013, 00:26
by noteirak
Try this then (note that the case must be respected!)
Code: Select all
VBoxManage showvminfo Ubuntu --details
Re: Virtual Box 4.2 crash
Posted: 3. May 2013, 02:04
by Skay
Code: Select all
Name: Ubuntu
Groups: /
Guest OS: Ubuntu
UUID: db25e4d3-5b08-4b0b-ba74-4cd30b2e0c70
Config file: C:\Users\cardenasce\VirtualBox VMs\Ubuntu\Ubuntu.vbox
Snapshot folder: C:\Users\cardenasce\VirtualBox VMs\Ubuntu\Snapshots
Log folder: C:\Users\cardenasce\VirtualBox VMs\Ubuntu\Logs
Hardware UUID: db25e4d3-5b08-4b0b-ba74-4cd30b2e0c70
Memory size: 712MB
Page Fusion: off
VRAM size: 64MB
CPU exec cap: 100%
HPET: off
Chipset: piix3
Firmware: BIOS
Number of CPUs: 1
Synthetic Cpu: off
CPUID overrides: None
Boot menu mode: message and menu
Boot Device (1): DVD
Boot Device (2): HardDisk
Boot Device (3): Not Assigned
Boot Device (4): Not Assigned
ACPI: on
IOAPIC: off
PAE: on
Time offset: 0ms
RTC: UTC
Hardw. virt.ext: on
Hardw. virt.ext exclusive: off
Nested Paging: on
Large Pages: on
VT-x VPID: on
State: powered off (since 2013-05-02T21:28:36.000000000)
Monitor count: 1
3D Acceleration: on
2D Video Acceleration: off
Teleporter Enabled: off
Teleporter Port: 0
Teleporter Address:
Teleporter Password:
Tracing Enabled: off
Allow Tracing to Access VM: off
Tracing Configuration:
Autostart Enabled: off
Autostart Delay: 0
Storage Controller Name (0): IDE
Storage Controller Type (0): PIIX4
Storage Controller Instance Number (0): 0
Storage Controller Max Port Count (0): 2
Storage Controller Port Count (0): 2
Storage Controller Bootable (0): on
Storage Controller Name (1): SATA
Storage Controller Type (1): IntelAhci
Storage Controller Instance Number (1): 0
Storage Controller Max Port Count (1): 30
Storage Controller Port Count (1): 1
Storage Controller Bootable (1): on
IDE (1, 0): E: (UUID: 00445644-0000-0000-0000-00000000453a) (temp eject)
SATA (0, 0): C:\Users\cardenasce\VirtualBox VMs\Ubuntu\Ubuntu.vdi (UUID: 7614817
7-9fad-4030-b6c4-a267d82ea12c)
NIC 1: MAC: 0800279695CC, Attachment: NAT, Cable connected: on, Trace:
off (file: none), Type: 82540EM, Reported speed: 0 Mbps, Boot priority: 0, Prom
isc Policy: deny, Bandwidth group: none
NIC 1 Settings: MTU: 0, Socket (send: 64, receive: 64), TCP Window (send:64, re
ceive: 64)
NIC 2: disabled
NIC 3: disabled
NIC 4: disabled
NIC 5: disabled
NIC 6: disabled
NIC 7: disabled
NIC 8: disabled
Pointing Device: USB Tablet
Keyboard Device: PS/2 Keyboard
UART 1: disabled
UART 2: disabled
LPT 1: disabled
LPT 2: disabled
Audio: disabled
Clipboard Mode: disabled
Drag'n'drop Mode: disabled
VRDE: disabled
USB: enabled
EHCI: disabled
USB Device Filters:
<none>
Available remote USB devices:
<none>
Currently Attached USB Devices:
<none>
Bandwidth groups: <none>
Shared folders: <none>
VRDE Connection: not active
Clients so far: 0
Guest:
Configured memory balloon size: 0 MB
Re: Virtual Box 4.2 crash
Posted: 3. May 2013, 02:16
by Perryg
There is something missing to the story here. You said You had just installed VirtualBox and can not get the guest to work. But you actually have 4 guests listed as being registered. One of them you can not use legally.
All indications are that these guests were actually created on a different system, or your install is different than what the logs and now the settings suggest. If you want to get to the bottom of this you are going to need to explain exactly what you had/have and don't leave anything out. Otherwise I don't think you will be able to solve this (I know I won't)
Re: Virtual Box 4.2 crash
Posted: 3. May 2013, 02:33
by Skay
This is a "new" build machine I've just recently put together. MSI motherboard, Intel i5-3470 processor, etc. I initially started from scratch, meaning I just installed VirtualBox, downloaded a copy of Ubuntu 32-bit, burned to a CD and created a new virtual machine. This is the Ubuntu VM.
I cannot seem to get past the point of VirtualBox crashing immediately after launching the VM.
The other 3 VM's you see were from a different computer and I just added them this afternoon. Thought I'd add these additional VM's, known to work from a different machine, and try to boot the guest OS but the same issue occurs. Each of these VM's crash immediately after starting.