Author Topic: try to get vdi to work (Resolved) :)  (Read 1845 times)

Offline GOTHBITES

  • Hero Member
  • *****
  • Posts: 749
  • Oh I get it now. Windows 8 is a Bigger Sham
try to get vdi to work (Resolved) :)
« on: September 16, 2012, 01:57:52 AM »
Hello
 I was having issues so i started over but when i try to use my last vb here is what i get

Quote
A differencing image of snapshot {1bc90034-045f-463d-954e-0f3ae9e88300} could not be found. Could not find an open hard disk with UUID {ce87f151-585f-4c42-907f-41c200fa52ad}.  
the details gave this

Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
SnapshotMachine
Interface:
IMachine {5eaa9319-62fc-4b0a-843c-0cb1940f8a91}
Callee:
IVirtualBox {c28be65f-1a8f-43b4-81f1-eb60cb516e66}

Now was intersting because last I had a similar issues and all I did was edit but this time i must have did something wrong. it became unaccesible so started from scratch

kde 4 latest vb 4.1.20 kde  4.8
« Last Edit: September 27, 2012, 10:44:02 AM by GOTHBITES »
UPDATED!! ASUS U52F Notebook i5 CPU,  4Gb ram, 640Gb Hard drive Dual-Boot Win 7Pro/KDE 4 3.2.18-pclos2.bfs

ASUS U50F notebook i3 4Gb Ram. 500 GB hard drive dual-boot Win 7/ KDE 3.2.18-pclos2.pae.bfs    Of course thats just my opinion I could wrong

Offline menotu

  • PCLinuxOS Tester
  • Super Villain
  • *******
  • Posts: 15296
  • ┌∩┐(◕_◕)┌∩┐
Re: try to get vdi to work
« Reply #1 on: September 16, 2012, 07:33:34 AM »
Were "snapshots" created whilst using that VM? as it may be looking for a VDI snapshot associated with the "main" VDI hard disk.
PCLinuxOS 32bit KDE 4.10.1; kernel-3.4.11-pclos1.bfs & 64bit 3.2.18bfs; NVidia GeForce 8400GS 1GB 310.19 driver

Sony Vaio SVE1513A4ESI Laptop, Intel Core i5, 2.6GHz, 6GB RAM, 750GB, 15.6" Intel HD Graphics 4000

Offline GOTHBITES

  • Hero Member
  • *****
  • Posts: 749
  • Oh I get it now. Windows 8 is a Bigger Sham
Re: try to get vdi to work
« Reply #2 on: September 16, 2012, 03:53:28 PM »
Were "snapshots" created whilst using that VM? as it may be looking for a VDI snapshot associated with the "main" VDI hard disk.

yes I did and i copied all the folders just now im try to get past this
UPDATED!! ASUS U52F Notebook i5 CPU,  4Gb ram, 640Gb Hard drive Dual-Boot Win 7Pro/KDE 4 3.2.18-pclos2.bfs

ASUS U50F notebook i3 4Gb Ram. 500 GB hard drive dual-boot Win 7/ KDE 3.2.18-pclos2.pae.bfs    Of course thats just my opinion I could wrong

Offline GermanTux

  • Hero Member
  • *****
  • Posts: 693
Re: try to get vdi to work
« Reply #3 on: September 18, 2012, 07:16:15 PM »
Were "snapshots" created whilst using that VM? as it may be looking for a VDI snapshot associated with the "main" VDI hard disk.

yes I did and i copied all the folders just now im try to get past this

Delete the virtual machine, but do not delete the vdi file.  Then re-create the virtual machine, and point it to that file. 

The other option is to delete the xml header file that contains the settings.  Itt's under ~.virtualbox/<machine name>. 

Offline GOTHBITES

  • Hero Member
  • *****
  • Posts: 749
  • Oh I get it now. Windows 8 is a Bigger Sham
Re: try to get vdi to work
« Reply #4 on: September 18, 2012, 09:59:19 PM »
Were "snapshots" created whilst using that VM? as it may be looking for a VDI snapshot associated with the "main" VDI hard disk.

yes I did and i copied all the folders just now im try to get past this

Delete the virtual machine, but do not delete the vdi file.  Then re-create the virtual machine, and point it to that file. 

The other option is to delete the xml header file that contains the settings.  Itt's under ~.virtualbox/<machine name>. 

Thank you
I was about to give up and start from scratch
UPDATED!! ASUS U52F Notebook i5 CPU,  4Gb ram, 640Gb Hard drive Dual-Boot Win 7Pro/KDE 4 3.2.18-pclos2.bfs

ASUS U50F notebook i3 4Gb Ram. 500 GB hard drive dual-boot Win 7/ KDE 3.2.18-pclos2.pae.bfs    Of course thats just my opinion I could wrong

Offline Xenaflux

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 3834
Re: try to get vdi to work
« Reply #5 on: September 18, 2012, 10:46:53 PM »
Quote
Thank you
I was about to give up and start from scratch

Have been there a few times.
Now I export to name.ova
No more problems .
The great thing in this world is not so much where we stand,
as in what direction we are moving.
                                                    (Oliver Wendell Holmes )

Offline GOTHBITES

  • Hero Member
  • *****
  • Posts: 749
  • Oh I get it now. Windows 8 is a Bigger Sham
Re: try to get vdi to work
« Reply #6 on: September 20, 2012, 01:30:53 PM »
Were "snapshots" created whilst using that VM? as it may be looking for a VDI snapshot associated with the "main" VDI hard disk.

yes I did and i copied all the folders just now im try to get past this

Delete the virtual machine, but do not delete the vdi file.  Then re-create the virtual machine, and point it to that file. 

The other option is to delete the xml header file that contains the settings.  Itt's under ~.virtualbox/<machine name>. 

Firs my apologies fro the delayed responses

I first tried to use the xml but got the error about mismatched uuid, then when I tried to virtual manager it couldn't find it literally i moved the vdi to the virtual box folder nothing
 I wonder if i could manually edit the Xmil to included the vdi   
UPDATED!! ASUS U52F Notebook i5 CPU,  4Gb ram, 640Gb Hard drive Dual-Boot Win 7Pro/KDE 4 3.2.18-pclos2.bfs

ASUS U50F notebook i3 4Gb Ram. 500 GB hard drive dual-boot Win 7/ KDE 3.2.18-pclos2.pae.bfs    Of course thats just my opinion I could wrong

Offline GermanTux

  • Hero Member
  • *****
  • Posts: 693
Re: try to get vdi to work
« Reply #7 on: September 27, 2012, 12:50:23 AM »
Firs my apologies fro the delayed responses

I first tried to use the xml but got the error about mismatched uuid, then when I tried to virtual manager it couldn't find it literally i moved the vdi to the virtual box folder nothing
 I wonder if i could manually edit the Xmil to included the vdi   

Yikes - this sounds like your VDI file is corrupt.  You may be stuck. 

Throwing this out there - what file system are you using for partition where Virtualbox data is stored? 

Offline JALU

  • Sr. Member
  • ****
  • Posts: 455
  • Just Another Linux User
Re: try to get vdi to work
« Reply #8 on: September 27, 2012, 02:07:04 AM »
Rule #1 (IMHO) - never use the snapshot rubbish.  If you need to backup your virtual machine, make a copy of the .vdi file

GOTHBITES,

My suggestion>
   Hide your main .vdi file somewhere safe
   open Virtual Box Manager and remove all the defined machines
   goto ~/.VirtualBox/ and clear all files/subfolders
   move your main .vdi to ~/.VirtualBox/
   in Virtual Box Manager create a new machine using existing virtual hard drive (point to your .vdi)

Cages
« Last Edit: September 27, 2012, 02:09:10 AM by darkages II »
THEN and THAN usage..
Use than to make a comparison. Use then when referring to time.

Offline GOTHBITES

  • Hero Member
  • *****
  • Posts: 749
  • Oh I get it now. Windows 8 is a Bigger Sham
Re: try to get vdi to work
« Reply #9 on: September 27, 2012, 10:43:20 AM »

Yikes - this sounds like your VDI file is corrupt.  You may be stuck. 

Throwing this out there - what file system are you using for partition where Virtualbox data is stored? 

If you mean ext3 or ext 4 the standard
Rule #1 (IMHO) - never use the snapshot rubbish.  If you need to backup your virtual machine, make a copy of the .vdi file

GOTHBITES,

My suggestion>
   Hide your main .vdi file somewhere safe
   open Virtual Box Manager and remove all the defined machines
   goto ~/.VirtualBox/ and clear all files/subfolders
   move your main .vdi to ~/.VirtualBox/
   in Virtual Box Manager create a new machine using existing virtual hard drive (point to your .vdi)

Cages


The Virtual manager still could not see the see the vdi  file I just removed the folder and made a new one added the vdi file and still nothing.
However Thanks for your suggestion It was a Huge Bloody help  :). Now I know where all the folders I need to keep are at.  lmao I was going nuts trying to figure this out 

I am going to consider this  HUGE resolved  again thank you GermanTux darkages II  Xenaflux
UPDATED!! ASUS U52F Notebook i5 CPU,  4Gb ram, 640Gb Hard drive Dual-Boot Win 7Pro/KDE 4 3.2.18-pclos2.bfs

ASUS U50F notebook i3 4Gb Ram. 500 GB hard drive dual-boot Win 7/ KDE 3.2.18-pclos2.pae.bfs    Of course thats just my opinion I could wrong