Code E_INVALIDARG (0x80070057) during clonehd

[Duanehebert]

Ok. At the command prompt this is what I have:

Code: Select all

D:\VirtualBox\VirtualMachines\Fedora_20>VBoxManage clonehd Fedora20.vdi Fedora20F.vdi --format VDI --variant Fixed
VBoxManage.exe: error: Failed to create the VirtualBox object!
VBoxManage.exe: error: Code E_NOINTERFACE (0x80004002) - No such interface supported (extended info not available)
VBoxManage.exe: error: Most likely, the VirtualBox COM server is not running or failed to start.

I now don't get E_INVALIDARG but I get E_NOINTERFACE.

I'm in the folder with the image that I want to clone.

As for the updated kernel, the error is a make error that fails with 4.3.12. We've be able to install the VBoxAdditions 4.3.16 while still using VBox 4.3.12 to get around this. This was done based on a thread here where I posted the exact errors. This seems to work though we still can't install the latest VirtualBox as we get this com server not running error when trying to load a guest. Like I said, this is why I'm trying to see what causes this. Or maybe the VirtualBox Com server not running message is a generic error message?

DKMS is installed.

[mpack]

Can you show that command without the unfortunate word wrap? If there's a space in the dest filename then you should wrap it "in quotes".

E_NOINTERFACE is a different kettle of fish entirely. That means that VirtualBox is not installed properly (or at all) for the current user.

[Duanehebert]

I reinstalled the extension pack. This is what I get now:

Code: Select all

D:\VirtualBox\VirtualMachines\Fedora_20>VBoxManage clonehd Fedora20.vdi Fedora20F.vdi --format VDI --variant Fixed
VBoxManage.exe: error: Failed to create the VirtualBox object!
VBoxManage.exe: error: Code E_NOINTERFACE (0x80004002) - No such interface supported (extended info not available)
VBoxManage.exe: error: Most likely, the VirtualBox COM server is not running or failed to start.

I'm running this from the folder where the vdi files are.
Is this message "the Virtual Box COM server is not running..." just a generic error message?

The problem with building the editions breaking is a make error with code that is no longer valid with the current kernel. I got around this by installing VBoxAddtions 4.3.16 with the existing VBox 4.3.12 as suggested here. We're not able to get the latest VirtualBox to run with what looks like problems with the beefed up security.

[mpack]

Extension pack? That isn't required for this.

E_NOINTERFACE means that it can't launch VBoxSVC to execute the command. It means that VirtualBox is not properly installed for the current user.

[Duanehebert]

Sorry about the word wrap. It's a copy/paste of the actual error in a cmd prompt. But there are no spaces in the path.

The Virtual Box installation is done as administrator. The current user is not administrator. Although, if I launch the command prompt as administrator, I get the same thing. I'll try to reinstall.

[mpack]

Installing for the user "Duane" using "Run as administrator" - is good.

Installing for user "Administrator" - not good, leads to error message given if user "Duane" tries to use the service.

"Run as administrator" should not be required to run "VBoxManage clonehd", at least not if the current user already has r/w access to the folders involved.

[Duanehebert]

Ok. I did install using "run as administrator" so this should work.

I think I will remove the installation and reinstall. I would like to try the latest version anyway. Thanks for your time.


After a complete uninstall/reboot/reinstall everything seems to work again with 4.3.12 and VBoxAddtions 4.3.16. It looks like there were some remnants of a failed attempt at upgrading to 4.3.18. Removing everything and doing a clean install worked.

EDIT: Well it seemed to work for a moment. After a system restart, I'm back to the E_INVALID arg error that I posted initially. I made a clone device manually by adding a static sized hard drive and then copying it with DD inside the machine. After rebooting with this one, my builds were maybe 2% faster so that was no help.

When I get the E_INVALIDARG error, is it possible to get some more detailed information as to which arg is invalid? I expect it's a permission issue but I don't see it.

[system]

Hello,

I confirm that setting the VBoxManage.exe binary in "XP SP3 Compatibility mode" is the right solution.
Tried reinstall and upgrade extension pack, running as administrator and changing VM name, I got the error with this command:

VBoxManage.exe startvm NAMEOFVM --type headless

[mpack]

I confirm that setting the VBoxManage.exe binary in "XP SP3 Compatibility mode" is the right solution.

That is not required.