VDI location using TC errors

[scottgus1]

After the "basic procedure" paragraph you saw in "How to Move a VM" is this paragraph:

Of course, if the copy is on the same host as the original VM then VirtualBox will object to your attempt to register the same UUID twice. You must remove the original VM from the manager before the copy can be added (*).

You'll have to remove the old guest from the GUI before registering the guest on the TC volume.

[HiAll]

After the "basic procedure" paragraph you saw in "How to Move a VM" is this paragraph:

Of course, if the copy is on the same host as the original VM then VirtualBox will object to your attempt to register the same UUID twice. You must remove the original VM from the manager before the copy can be added (*).

You'll have to remove the old guest from the GUI before registering the guest on the TC volume.

I took the drastic step of reformating my HD and got all the way to creating the VM. Removed the old guest from the GUI. Moved the .vbov to TC volume. CLicked on it to gerister and it worked. Stopped it. Clicked on .vbox and it started it. Stop it. Then started it again only to get the same UUID error. But this time I noticed the pathway changed to 'Z:\\in 7.vdi'" and not "Z:\\win7.vdi" thus two different UUID registered:

Failed to open the hard disk file Z:\Win 7.vdi.

Cannot register the hard disk 'Z:\Win 7.vdi' {cba7d8c6-6fb6-4b47-b25f-44d0246a366e} because a hard disk 'Z:\\in 7.vdi' with UUID {cba7d8c6-6fb6-4b47-b25f-44d0246a366e} already exists.

Result Code: E_INVALIDARG (0x80070057)
Component: VirtualBox
Interface: IVirtualBox {fafa4e17-1ee2-4905-a10e-fe7c18bf5554}
Callee RC: VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)


What to do? I really need this up for work or Im going to get fired. Please advise. Anyone? PLS?

[Perryg]

I have been trying to follow this but to tell you the truth it is really confusing.

Why are you moving the .vbox file for in the first place?

1) install the guest on the TC drive to begin with or
2) move the entire folder after you remove it from the main manager (without deleting) and add it again using the add feature.

[loukingjr]

I just looked at this myself and I believe Perry is correct. And I bet the original .vdi was never unregistered before it was moved.

[HiAll]

I have been trying to follow this but to tell you the truth it is really confusing.

Why are you moving the .vbox file for in the first place?

1) install the guest on the TC drive to begin with or
2) move the entire folder after you remove it from the main manager (without deleting) and add it again using the add feature.

Thanks for your quick reply. Whenever I create a new vm I make sure the installation directory is in the tc hidden volume. I don't know why but the install folder name keeps changing thus the pathway is blocked as it doesn't recognize the folder. I then release remove the old vid and ISO and add it back again in the storage and it works. I also eight clicked and make a desktop short cut as suggested in here but he vm wouldn't boot up.

I read the older version of vb doesn't do this but I can't seem to find the post. Would uninstalling and reinstall an older version of vb help in this case? Also, I noticed there is a virtualbox.xml file with evidence of a tc volume install on my local HD. None of the tutorial I read mentions this or how to mitigate the risk. What to do??

Would any senior member here be interested in Remote Desktop in to finish the install correctly for 25usd of btc for 5 minutes of your expert time? I'm open to escrow to senior members only. I really REALLY need this set up for work.

The end result I'm looking for is a stable vm win7 installed which I could load from my tc volume with no problems again and again. Someone please help this low tech loser, lol. I'm not joking. I'm soon frustrated now seeing everyone else installing vb no problemo.

[Perryg]

Look its not that hard. You create the guest in the TC volume and it should be just fine. I don't use the desktop icon myself at all maybe that is the issue. Mixing the TC and normal can be what is causing the issue I guess but if the path changes it has to be the host that is messing with the path. In fact the two paths you show are one in local and the other is a network location. Is that what you are trying to do a network based guest?

[loukingjr]

First I question the wisdom of using a discontinued application such as TrueCrypt in a business environment. At the time development was discontinued (5/14), it had a number of security flaws.

But, is it possible that one can't run a VirtualBox vm from a hidden volume?

[HiAll]

So I boot and try to start the vm but still uuid errors and .vdi. So I manually go to GUI machine to release and remove ISO and vdi since it's now highlighted yellow and won't let me boot up. Then go to storage and re-add the vdi and ISO. Shortly afterwards it starts up but it's super slow. Almost 5 minutes to boot. to has 3gb of memory which is half of my ram. I also noticed when I installed windows I picked a win7 32bit and set the vb to install as such but somehow win 7 ultimate got installed since the install page didn't show any 64 or 32 bit selection. Could this be causing the slowness on the vm? Moreover the third time I run the vm it's a little faster.

[HiAll]

First I question the wisdom of using a discontinued application such as TrueCrypt in a business environment. At the time development was discontinued (5/14), it had a number of security flaws.

But, is it possible that one can't run a VirtualBox vm from a hidden volume?

There was a 30,000usd audit of tc recently and it passed. I rather use tc then bit locker which comes with windows. Hell I don't even like windows! Rather use Linux but don't have the time to learn as I had Ubuntu 12.4 before and for the life of me I couldn't get a simple client to install using all these sudo apt comes I don't understand. All my work os are windows. This is why I use windows for now.

[Perryg]

This is the reason for you slow guest.

Code: Select all

00:00:03.677860 HMR3Init: Falling back to raw-mode: AMD-V is disabled in the BIOS (or by the host OS).

It is also why you can not install a 64 bit guest.

You still have not answered my question and I will not reply again until you do.

[HiAll]

Look its not that hard. You create the guest in the TC volume and it should be just fine. I don't use the desktop icon myself at all maybe that is the issue. Mixing the TC and normal can be what is causing the issue I guess but if the path changes it has to be the host that is messing with the path. In fact the two paths you show are one in local and the other is a network location. Is that what you are trying to do a network based guest?

No network based guest. Just need a nice encrypted setup. A little paranoia is good especially after the snowmen incident. Also, what is this mixing the TC and normal mean? Moreover, are you saying the host has to be messing with the path, meaning me? All I did was follow a tutorial which showed the .vbox being moved to the TC. Turned off the vb and turned the vb on again by clicking on the vbox to show the vb working inside the TC hidden volume.

[HiAll]

This is the reason for you slow guest.

Code: Select all

00:00:03.677860 HMR3Init: Falling back to raw-mode: AMD-V is disabled in the BIOS (or by the host OS).

It is also why you can not install a 64 bit guest.

You still have not answered my question and I will not reply again until you do.

I noticed that too but I'm using a win7 32 bit ISO? Also, after another click on the vbox and changing out the ISO and vdi it starts up. Also my BIOS is enabled so I don't know why it's doing that? Weird indeed. Could I just have a bad version? It seems like there are more problems once a new vb update occurs.

[Perryg]

The error means exactly what it says. Either the VT-x/AMD-v is not turned on in the machine bios or your host has something else that is taking hold of it so VirtualBox can not use it.
Whether the host is 32-bit or 64-bit makes no difference in that regard. This will not stop you from using a 32-bit guest but it will be really slow since it is using software acceleration instead of hardware.

You keep saying that you move the .vbox file but the instructions state specifically that you *must* move the entire guest folder, not just the single .vbox file.

If you look at your screen shot you will see what I was getting at.
Z:\Win 7.vdi is a drive location
Z:\\in 7.vdi is similiar to a network location

or you typed it wrong.

Also when moving guests around it is best that you remove all virtual CD/DVD media from the virtual drive before the move to keep from having issues like " can not find ..."

[mpack]

If you look at your screen shot you will see what I was getting at.
Z:\Win 7.vdi is a drive location
Z:\\in 7.vdi is similiar to a network location

Actually, I have suspected for some time that there is a bug in VBox's handling of Windows root folder paths, of which this looks like it might be an example (supposed bug: Vbox doesn't like empty folder names, i.e. root folders. In forcing a non-empty name it adds a redundant slash). However I have not been able to pin it down.

Of course the problem would not arise if the move instructions were accurately followed.