VirtualBox

Opened 7 years ago

Last modified 2 years ago

#17215 reopened defect

Guest additions command line updating fails (Linux host, Windows guest) — at Version 4

Reported by: roland651 Owned by:
Component: VM control Version: VirtualBox 5.2.0
Keywords: Cc:
Guest type: Windows Host type: Linux

Description (last modified by janitor)

I have a Linux host (Ubuntu 16.04, 64 bits) and a Windows guest (Windows 7 professional, 64 bits). I try to update the guest additions using the command line.

So I issue the command (from the Linux host, with the VM guest powered on):

VBoxManage guestcontrol "win7"  updateadditions --source /usr/share/virtualbox/VBoxGuestAdditions.iso --verbose

The command fails and I get the following output:

Updating Guest Additions ...
Using source: /usr/share/virtualbox/VBoxGuestAdditions.iso
VBoxManage: error: Could not open guest session: VERR_TIMEOUT
VBoxManage: error: Details: code VBOX_E_IPRT_ERROR (0x80bb0005), component GuestWrap, interface IGuest, callee nsISupports
VBoxManage: error: Context: "UpdateGuestAdditions(Bstr(strSource).raw(), ComSafeArrayAsInParam(aArgs), ComSafeArrayAsInParam(aUpdateFlags), pProgress.asOutParam())" at line 3667 of file VBoxManageGuestCtrl.cpp

I tried with Virtualbox 5.1.30 and 5.2.0 and I get the same result.

Manually updating the guest additions (withon the guest) works as expected.

And I was also able to start a program within the guest, using commands like:

VBoxManage guestcontrol "win7" --username my_account run --exe "C:\Windows\System32\notepad.exe"

So, I think this issue is clearly a bug...

Change History (4)

comment:1 by Socratis, 7 years ago

I tried it on an OSX host with similar results.

comment:2 by Miro Penchev, 6 years ago

This bug is still here, same on me - Host: OpenSuse Leap 15.0, VirtualBox 5.2.14, Guests: Win7/10

comment:3 by Socratis, 6 years ago

I tried it, just like the previous time, with:

  • Host: OSX 10.11.6
  • VirtualBox: 5.2.16
  • Guest: Windows XP SP3 with Guest Additions 5.1.26

What I noticed this time though is that on the guest the VirtualBox Guest Additions Service crashed. I did not pay attention last time. That would definitely explain the TIMEOUT because of lost communication with the service.

A matter of the Guest Additions (existing in the VM) then, and not the VBoxManage command? Can't tell for sure...

comment:4 by janitor, 6 years ago

Description: modified (diff)
Note: See TracTickets for help on using tickets.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy Automated Access Etiquette