Software - Support => Other => Topic started by: GatesHater52 on February 06, 2015, 09:37:07 AM
Title: [SOLVED] Virutal machine error after recent Virutal Box update
Post by: GatesHater52 on February 06, 2015, 09:37:07 AM
This affects 2 different machines, one 32bit & one 64bit.
Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
SessionMachine
Interface:
ISession {12f4dcdb-12b2-4ec1-b7cd-ddd9f6c5bf4d}
[attachment deleted by admin]
Title: Re: Virutal machine error after recent Virutal Box Update
Post by: Jerry on February 06, 2015, 01:04:05 PM
How did you originally install VB?
Title: Re: Virutal machine error after recent Virutal Box Update
Post by: GatesHater52 on February 06, 2015, 01:09:48 PM
From the "Install additional Software " entry in the LL2.0 menu. thanks.
Title: Re: Virutal machine error after recent Virutal Box Update
Post by: Jerry on February 06, 2015, 01:18:25 PM
Are there any additional errors?
Title: Re: Virutal machine error after recent Virutal Box Update
Post by: ukbrian on February 06, 2015, 01:48:34 PM
In VB at open "File > Preferences" Click "Extensions" Is the installed extension green?
Title: Re: Virutal machine error after recent Virutal Box Update
Post by: GatesHater52 on February 06, 2015, 01:52:13 PM
No. When I start the machine, the window opens, immediately closes & the dialog box opens with the text I copied in my post. I did a quick search of LL, Ubuntu & Vbox forums, finding a couple of "close, but no cigar" posts, but noting affecting the current software versions.
Title: Re: Virutal machine error after recent Virutal Box Update
Post by: GatesHater52 on February 06, 2015, 01:54:23 PM
Two Green check marks. VNC & extension pack
Title: Re: Virutal machine error after recent Virutal Box Update
Post by: Jerry on February 06, 2015, 02:14:14 PM
What is the output of - cat /proc/cpuinfo
Title: Re: Virutal machine error after recent Virutal Box Update
Post by: GatesHater52 on February 06, 2015, 02:27:28 PM
greg@LabEmeritus:~$ cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 6 model : 6 model name : AMD Athlon(tm) XP 2000+ stepping : 2 cpu MHz : 1666.679 cache size : 256 KB physical id : 0 siblings : 1 core id : 0 cpu cores : 1 apicid : 0 initial apicid : 0 fdiv_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr sse syscall mmxext 3dnowext 3dnow bogomips : 3333.35 clflush size : 32 cache_alignment : 32 address sizes : 34 bits physical, 32 bits virtual power management: ts
Title: Re: Virutal machine error after recent Virutal Box Update
Post by: Jerry on February 06, 2015, 08:35:00 PM
Your cpu does not support virtualization so you will be unable to use VirtualBox.
Title: Re: Virutal machine error after recent Virutal Box Update
Post by: GatesHater52 on February 06, 2015, 08:48:05 PM
I have been running a windows 2000 installation which worked fine until vbox updated early this week. If the CPU did not support virualization, why did it work?
Title: Re: Virutal machine error after recent Virutal Box Update
Post by: Jerry on February 06, 2015, 08:50:57 PM
I am not sure, looking at your cpu flags I can't see a reference to virtualization.
Title: Re: Virutal machine error after recent Virutal Box Update
Post by: GatesHater52 on February 06, 2015, 08:57:03 PM
Failed to open a session for the virtual machine XP_64.
Unsupported version 11 of data unit 'vga' (instance #0, pass 0xffffffff) (VERR_SSM_UNSUPPORTED_DATA_UNIT_VERSION).
Result Code: NS_ERROR_FAILURE (0x80004005) Component: Console Interface: IConsole {8ab7c520-2442-4b66-8d74-4ff1e195d2b6}
This is the error on my 64 bit PC, after the same update.
Title: Re: Virutal machine error after recent Virutal Box Update
Post by: Jerry on February 06, 2015, 09:04:05 PM
Try this:
https://www.youtube.com/watch?v=rsUExNLSObk
Title: Re: Virutal machine error after recent Virutal Box Update
Post by: GatesHater52 on February 06, 2015, 09:46:59 PM
Thank you. Discarding the saved state worked, but the older pc I use at work to keep a ms access database. By chance, I backed up the .vdi the last day it worked so I may be able to migrate it to another PC. I don,t really have the luxury of time.
Title: Re: Virutal machine error after recent Virutal Box Update
Post by: Jerry on February 06, 2015, 10:01:55 PM
Don't thank me, thank Google :)
Title: Re: Virutal machine error after recent Virutal Box Update
Post by: GatesHater52 on February 07, 2015, 09:48:18 PM
It comes full circle.That's where I started!
Title: Re: Virutal machine error after recent Virutal Box Update
Post by: GatesHater52 on February 09, 2015, 08:14:23 AM
Happy day! Discarded saved state & I am back in business.