Lost networking and shared clipboard

[BPickle]

Okay, I think I've figured a little more out. In WinXP I've checked the event log, which says:

Timeout (30000 milliseconds) waiting for the VirtualBox Guest Additions Service service to connect.

The VirtualBox Guest Additions Service service failed to start due to the following error:

The service did not respond to the start or control request in a timely fashion.

It shows up in TaskManager, but I can't manually end it, as stated before. So it appears to be there, but just unresponsive.

I found a 3-year-old post that said to edit the registry to produce a log:

HKLM\SYSTEM\CurrentControlSet\Services\VBoxService\ImagePath = "system32\VBoxService.exe -vvvv --logfile c:\VBoxService.log" (REG_EXPAND_SZ)

My log from that doesn't say much. It gives a package type of WINDOWS_32BITS_GENERIC, OS version of 5.1.2600, OS service pack 3. That's about it.

So it appears that WinXP is having trouble communicating with VBoxService.exe.

[BPickle]

I've uninstalled GA 5 and reinstalled GA 4.3.10, and the service still fails to connect according to the Event Viewer. So assuming that before the update to 4.3.34, I had 4.3.10, 4.3.10 should work within my WinXP guest.

After the event log service starts up, the VB GA error messages are the first to appear. So I don't see any hint of anything else interfering with the VBoxService service starting up.

[BPickle]

I installed VM 5.0.0 for Trusty with extensions and GA, both 5.0.0, and attached is another log.

Earlier today I tried 4.3.10.

Something must be keeping GA from doing its thing inside the guest, that's my guess at this point. It was working fine, and now it isn't, and I certainly didn't change anything within WinXP.

[BPickle]

When I installed 5.0.0 yesterday, I used gdebi, since a recent post on another thread suggested that. No go.

Today I noticed that there were a couple extra files in /etc/init.d pertaining to virtualbox, so I uninstalled 5.0.0, moved all six of the vbox-related files, and installed 5.0.10. No go. I then applied the latest updates to Ubuntu, rebooted everything, and checked in the WinXP guest for shared folders. Nothing. I then used explorer to navigate to the \\Vboxsvr item under VirtualBox Shared Folders. When I click on that item, it seems to just hang.

Disabling the network via the bottom of the guest window and then enabling it again causes the guest to try to get an IP, but it can't do that successfully. That suggests that VirtualBox is communicating with the guest to a point.

The guest window used to fill the screen, but it doesn't anymore. The available screen resolutions in the display properties of the guest don't match the maximum size available, like I think they use to.

As far as I know, I have no firewall running on the guest that could be interfering with something.

Typing sc stop vboxservice from a command prompt in the guest gives the error message that that service has not been started. Trying to start the service in this manner yields the same error message found in the event log, and results in two vboxservice processes running in taskmanager.

On the host side, vboxmanage debugvm WinXP osdetect tells me that I'm running WinNT. Is that what it should say, rather than WinXP?

[Perryg]

I am sorry that no one from the Windows side has picked up your topic. I might make a suggestion to see what might be happening.

Install a new guest Windows if you prefer or Linux. Any will do to see if the issue is guest related or something else.

After your reply I will move this topic to a Windows guest forum and maybe that will get more attention.

[BPickle]

Thanks, Perryg.

I tried creating a VM for some tiny variation of Linux. It is able to download stuff from the internet if the network connection is enabled, so I think that means networking is working. I can't get GA installed properly because the installer can't find the headers, so I can't check out things like the shared clipboard. But if networking is working, that's more than my WinXP guest can do.

[Perryg]

Yes more than likely the features would actually work if you installed the headers and then install the guest additions.

I will move this to Windows guests now and hopefully someone that deals with Windows will read this and help.

[BPickle]

I used system restore in the WinXP guest to go back before this problem surfaced, and I then reinstalled GA 5.0.10.

I still don't have networking, shared clipboard, or shared folders. The WinXP event log is still saying that VBoxService and VBoxTray are failing to start, and these two processes still cannot be crashed using TaskManager.

I'm at the point now where I have to get this VM operational soon. Tomorrow will make one week since it went down. Tips would be appreciated.

[BPickle]

I found the VBoxSvc.log and it does give an error message:

Code: Select all

VirtualBox XPCOM Server 4.3.34_Ubuntu r104062 linux.amd64 (Nov 23 2015 18:06:43) release log
00:00:00.000335 main     Log opened 2015-12-04T16:35:32.571250000Z
00:00:00.000337 main     Build Type: release
00:00:00.000340 main     OS Product: Linux
00:00:00.000341 main     OS Release: 3.16.0-53-generic
00:00:00.000342 main     OS Version: #72~14.04.1-Ubuntu SMP Fri Nov 6 18:17:23 UTC 2015
00:00:00.000366 main     DMI Product Name: MS-7693
00:00:00.000374 main     DMI Product Version: 4.0
00:00:00.000444 main     Host RAM: 7773MB total, 4974MB available
00:00:00.000447 main     Executable: /usr/lib/virtualbox/VBoxSVC
00:00:00.000447 main     Process ID: 22899
00:00:00.000448 main     Package type: LINUX_64BITS_GENERIC (OSE)
00:00:00.105680 nspr-2   Home directory: '/home/bpickle/.VirtualBox'
00:00:00.106105 nspr-2   Loading settings file "/home/bpickle/.VirtualBox/VirtualBox.xml" with version "1.12-linux"
00:00:00.109911 nspr-2   Failed to retrive disk info: getDiskName(/dev/mapper/ubuntu--vg-root) --> ubuntu--vg-root
00:00:00.110886 nspr-2   HostDnsMonitor: old information
00:00:00.110903 nspr-2     no server entries
00:00:00.110917 nspr-2     no search string entries
00:00:00.110928 nspr-2     no domain set
00:00:00.110938 nspr-2   HostDnsMonitor: new information
00:00:00.110948 nspr-2     server 1: 127.0.1.1
00:00:00.110961 nspr-2     search string 1: home
00:00:00.110972 nspr-2     domain: home
00:00:00.110988 nspr-2   HostDnsMonitorProxy::notify
00:00:00.112972 nspr-2   VDInit finished
00:00:00.120325 nspr-2   Loading settings file "/home/bpickle/VirtualBox VMs/WinXP/WinXP.vbox" with version "1.13-linux"
00:00:00.122201 nspr-2   Loading settings file "/home/bpickle/VirtualBox VMs/TinyLinux/TinyLinux.vbox" with version "1.14-linux"
00:00:00.261144 nspr-3   WARNING [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={93269330-48ca-4096-b4a2-1189df336267} aComponent={Host} aText={VirtualBox is not currently allowed to access USB devices.  You can change this by adding your user to the 'vboxusers' group.  Please see the user manual for a more detailed explanation}, preserve=true 
00:00:00.396866 nspr-2   WARNING [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={93269330-48ca-4096-b4a2-1189df336267} aComponent={Host} aText={VirtualBox is not currently allowed to access USB devices.  You can change this by adding your user to the 'vboxusers' group.  Please see the user manual for a more detailed explanation}, preserve=true 
00:00:00.397966 nspr-2   WARNING [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={93269330-48ca-4096-b4a2-1189df336267} aComponent={Host} aText={VirtualBox is not currently allowed to access USB devices.  You can change this by adding your user to the 'vboxusers' group.  Please see the user manual for a more detailed explanation}, preserve=true 
00:04:37.147693 nspr-2   WARNING [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={93269330-48ca-4096-b4a2-1189df336267} aComponent={Host} aText={VirtualBox is not currently allowed to access USB devices.  You can change this by adding your user to the 'vboxusers' group.  Please see the user manual for a more detailed explanation}, preserve=true 
00:04:37.149337 nspr-2   WARNING [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={93269330-48ca-4096-b4a2-1189df336267} aComponent={Host} aText={VirtualBox is not currently allowed to access USB devices.  You can change this by adding your user to the 'vboxusers' group.  Please see the user manual for a more detailed explanation}, preserve=true 
00:04:37.384222 nspr-2   WARNING [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={93269330-48ca-4096-b4a2-1189df336267} aComponent={Host} aText={VirtualBox is not currently allowed to access USB devices.  You can change this by adding your user to the 'vboxusers' group.  Please see the user manual for a more detailed explanation}, preserve=true 
00:04:37.385350 nspr-3   WARNING [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={93269330-48ca-4096-b4a2-1189df336267} aComponent={Host} aText={VirtualBox is not currently allowed to access USB devices.  You can change this by adding your user to the 'vboxusers' group.  Please see the user manual for a more detailed explanation}, preserve=true 
00:04:37.389921 nspr-3   WARNING [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={93269330-48ca-4096-b4a2-1189df336267} aComponent={Host} aText={VirtualBox is not currently allowed to access USB devices.  You can change this by adding your user to the 'vboxusers' group.  Please see the user manual for a more detailed explanation}, preserve=true 
00:04:37.400057 nspr-3   WARNING [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={93269330-48ca-4096-b4a2-1189df336267} aComponent={Host} aText={VirtualBox is not currently allowed to access USB devices.  You can change this by adding your user to the 'vboxusers' group.  Please see the user manual for a more detailed explanation}, preserve=true 
00:04:37.401601 nspr-3   Load [/usr/lib/virtualbox/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/linux.amd64/VBoxHostWebcam.so] rc VINF_SUCCESS
00:04:37.417442 nspr-2   ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={480cf695-2d8d-4256-9c7c-cce4184fa048} aComponent={SessionMachine} aText={Saved screenshot data is not available (VERR_NOT_SUPPORTED)}, preserve=false
00:04:37.418832 nspr-3   WARNING [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={93269330-48ca-4096-b4a2-1189df336267} aComponent={Host} aText={VirtualBox is not currently allowed to access USB devices.  You can change this by adding your user to the 'vboxusers' group.  Please see the user manual for a more detailed explanation}, preserve=true 
00:04:37.432639 nspr-3   WARNING [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={93269330-48ca-4096-b4a2-1189df336267} aComponent={Host} aText={VirtualBox is not currently allowed to access USB devices.  You can change this by adding your user to the 'vboxusers' group.  Please see the user manual for a more detailed explanation}, preserve=true 
00:04:37.538596 nspr-3   WARNING [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={93269330-48ca-4096-b4a2-1189df336267} aComponent={Host} aText={VirtualBox is not currently allowed to access USB devices.  You can change this by adding your user to the 'vboxusers' group.  Please see the user manual for a more detailed explanation}, preserve=true 
00:04:37.539059 nspr-3   WARNING [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={93269330-48ca-4096-b4a2-1189df336267} aComponent={Host} aText={VirtualBox is not currently allowed to access USB devices.  You can change this by adding your user to the 'vboxusers' group.  Please see the user manual for a more detailed explanation}, preserve=true 
00:04:37.539768 nspr-3   WARNING [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={93269330-48ca-4096-b4a2-1189df336267} aComponent={Host} aText={VirtualBox is not currently allowed to access USB devices.  You can change this by adding your user to the 'vboxusers' group.  Please see the user manual for a more detailed explanation}, preserve=true 
00:04:38.259559 nspr-2   WARNING [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={93269330-48ca-4096-b4a2-1189df336267} aComponent={Host} aText={VirtualBox is not currently allowed to access USB devices.  You can change this by adding your user to the 'vboxusers' group.  Please see the user manual for a more detailed explanation}, preserve=true 
00:04:38.260908 nspr-3   WARNING [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={93269330-48ca-4096-b4a2-1189df336267} aComponent={Host} aText={VirtualBox is not currently allowed to access USB devices.  You can change this by adding your user to the 'vboxusers' group.  Please see the user manual for a more detailed explanation}, preserve=true 
00:07:40.006364 nspr-3   WARNING [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={93269330-48ca-4096-b4a2-1189df336267} aComponent={Host} aText={VirtualBox is not currently allowed to access USB devices.  You can change this by adding your user to the 'vboxusers' group.  Please see the user manual for a more detailed explanation}, preserve=true 
00:07:40.007427 nspr-2   WARNING [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={93269330-48ca-4096-b4a2-1189df336267} aComponent={Host} aText={VirtualBox is not currently allowed to access USB devices.  You can change this by adding your user to the 'vboxusers' group.  Please see the user manual for a more detailed explanation}, preserve=true 
00:07:43.905538 nspr-4   WARNING [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={93269330-48ca-4096-b4a2-1189df336267} aComponent={Host} aText={VirtualBox is not currently allowed to access USB devices.  You can change this by adding your user to the 'vboxusers' group.  Please see the user manual for a more detailed explanation}, preserve=true 
00:07:43.907065 nspr-4   WARNING [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={93269330-48ca-4096-b4a2-1189df336267} aComponent={Host} aText={VirtualBox is not currently allowed to access USB devices.  You can change this by adding your user to the 'vboxusers' group.  Please see the user manual for a more detailed explanation}, preserve=true

As yet another attempt to come up with some sort of resolution, I switched back from the official version to the Ubuntu fork. I can switch back and see if I still get the above error message. But I wouldn't mind hearing whether anyone thinks the above not retrieving disk info message and the not allowed to access USB devices might have anything to do with my problem. I have verified that my username is in the vboxuser group. and so I don't know why I'm even getting that error message.

[BPickle]

The disk image I'm using now was copied to a raid system, and that copy on the raid system has an event log with an item dated Nov. 21, 2015. So it was unaffected by the recent update. I've therefore started a VM using this older VDI file. While there were no errors in the log file before regarding the loading of VBoxService, there are now. The shared clipboard doesn't work. There is no shared folder. The only improvement I see is that the VM screen fills the entire available area, not just a slightly smaller area.

I think this rules out the possibility that WinXP registry issues are causing this, unless the registry had the same issues prior to any of these problems surfacing.

[BPickle]

I assume that a kernel upgrade since the above posts caused VirtualBox to not be able to start up any virtual machines. I therefore uninstalled VirtualBox 4.3.34, and installed 5.0.12, a newer version than I have yet tried. Now I can start VMs just fine, but I still have all the same problems:

• No shared clipboard.
• No share folder.
• No networking.
• Can't use task manager to close down VBoxTray and VBoxService.

I think I'm still unable to print to a USB printer as well.

My last post was on December 6, and there have been no posts or suggestions since. Am I posting my problem in the wrong place? Is support for VirtualBox ending? It seems like 40+ days is a long time to wait until getting some sort of assistance.

[Perryg]

Is support for VirtualBox ending? It seems like 40+ days is a long time to wait until getting some sort of assistance.

Actually this is the end user forum. Users trying to help users. Support is only available via a support contract with Oracle. I will try to help but you must keep in mind I do not do Windows.

1) We only assist if you are using the official version of VirtualBox from virtualbox.org.
2) When changing between a repo fork and the official version you must first remove the repo fork and reboot the host.
3) After the first steps are followed you need to provide some diagnostic information such as a new log file, and it would help to see the guests configuration ( see command below ).

• From the hosts terminal/command window type VBoxManage showvminfo <VM Name> --details and post here. Replace <VM Name> with the actual name of the VM. Use " " if the name has a space in it.
  
  Note if the host is Windows you need to be in the directory that has VBoxManage.exe for the command to work.

[BPickle]

Thanks for your reply. Here is the info that was printed out:

Code: Select all

Name:            WinXP
Groups:          /
Guest OS:        Windows XP (32-bit)
UUID:            14d346fb-6808-44c2-b6d4-296259a51883
Config file:     /home/bpickle/VirtualBox VMs/WinXP/WinXP.vbox
Snapshot folder: /home/bpickle/VirtualBox VMs/WinXP/Snapshots
Log folder:      /home/bpickle/VirtualBox VMs/WinXP/Logs
Hardware UUID:   14d346fb-6808-44c2-b6d4-296259a51883
Memory size:     2048MB
Page Fusion:     off
VRAM size:       32MB
CPU exec cap:    100%
HPET:            off
Chipset:         ich9
Firmware:        BIOS
Number of CPUs:  1
PAE:             on
Long Mode:       on
CPUID Portability Level: 0
CPUID overrides: None
Boot menu mode:  message and menu
Boot Device (1): Floppy
Boot Device (2): DVD
Boot Device (3): HardDisk
Boot Device (4): Not Assigned
ACPI:            on
IOAPIC:          on
Time offset:     0ms
RTC:             local time
Hardw. virt.ext: off
Nested Paging:   on
Large Pages:     off
VT-x VPID:       on
VT-x unr. exec.: on
Paravirt. Provider: Legacy
State:           running (since 2016-01-17T15:15:10.023000000)
Monitor count:   1
3D Acceleration: on
2D Video Acceleration: off
Teleporter Enabled: off
Teleporter Port: 0
Teleporter Address: 
Teleporter Password: 
Tracing Enabled: off
Allow Tracing to Access VM: off
Tracing Configuration: 
Autostart Enabled: off
Autostart Delay: 0
Default Frontend: 
Storage Controller Name (0):            IDE
Storage Controller Type (0):            PIIX3
Storage Controller Instance Number (0): 0
Storage Controller Max Port Count (0):  2
Storage Controller Port Count (0):      2
Storage Controller Bootable (0):        on
IDE (0, 0): /home/bpickle/VirtualBox VMs/WinXP/WinXP.vdi (UUID: e7f5e183-14e4-4865-8bef-52aec1940339)
IDE (1, 0): /home/bpickle/Downloads/VBoxGuestAdditions_5.0.12.iso (UUID: bd678e4d-cca0-4391-bd45-8aae9866ba7e)
NIC 1:           MAC: 080027E3D320, Attachment: NAT, Cable connected: on, Trace: off (file: none), Type: Am79C973, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: allow-a
ll, Bandwidth group: none
NIC 1 Settings:  MTU: 0, Socket (send: 64, receive: 64), TCP Window (send:64, receive: 64)
NIC 2:           disabled
NIC 3:           disabled
NIC 4:           disabled
NIC 5:           disabled
NIC 6:           disabled
NIC 7:           disabled
NIC 8:           disabled
NIC 9:           disabled
NIC 10:           disabled
NIC 11:           disabled
NIC 12:           disabled
NIC 13:           disabled
NIC 14:           disabled
NIC 15:           disabled
NIC 16:           disabled
NIC 17:           disabled
NIC 18:           disabled
NIC 19:           disabled
NIC 20:           disabled
NIC 21:           disabled
NIC 22:           disabled
NIC 23:           disabled
NIC 24:           disabled
NIC 25:           disabled
NIC 26:           disabled
NIC 27:           disabled
NIC 28:           disabled
NIC 29:           disabled
NIC 30:           disabled
NIC 31:           disabled
NIC 32:           disabled
NIC 33:           disabled
NIC 34:           disabled
NIC 35:           disabled
NIC 36:           disabled
Pointing Device: PS/2 Mouse
Keyboard Device: PS/2 Keyboard
UART 1:          disabled
UART 2:          disabled
LPT 1:           disabled
LPT 2:           disabled
Audio:           enabled (Driver: PulseAudio, Controller: SB16, Codec: SB16)
Clipboard Mode:  Bidirectional
Drag and drop Mode: Bidirectional
Session name:    GUI/Qt
Video mode:      1280x960x32 at 0,0 enabled
VRDE:            disabled
USB:             enabled
EHCI:            disabled
XHCI:            disabled
USB Device Filters:

<none>

Available remote USB devices:

<none>

Currently Attached USB Devices:

UUID:               aef68e07-8ba2-4c9d-ae95-7df4dc0495f7
VendorId:           0x0aec (0AEC)
ProductId:          0x5010 (5010)
Revision:           1.0 (0100)
Manufacturer:       SOYO    
Product:            USB Storage Device
SerialNumber:       0AEC501000001A002
Address:            sysfs:/sys/devices/pci0000:00/0000:00:16.0/usb7/7-1//device:/dev/vboxusb/007/002

UUID:               78b929f9-f169-48c3-a6b0-cff5ec3fdd21
VendorId:           0x04f9 (04F9)
ProductId:          0x01a6 (01A6)
Revision:           1.0 (0100)
Manufacturer:       Brother Industries, Ltd
Product:            MFC-8860DN Port(FaxModem)
SerialNumber:       000L7J558637
Address:            sysfs:/sys/devices/pci0000:00/0000:00:13.2/usb2/2-1//device:/dev/vboxusb/002/017

Bandwidth groups:  <none>

Shared folders:  

Name: 'Share_Folder', Host path: '/home/bpickle/VirtualBox VMs/WinXP/Share Folder' (machine mapping), writable
Name: 'ShareFolder', Host path: '/home/bpickle/VirtualBox VMs/WinXP/ShareFolder' (machine mapping), writable

VRDE Connection:    not active
Clients so far:     0

Video capturing:    not active
Capture screens:    0
Capture file:       /home/bpickle/VirtualBox VMs/WinXP/WinXP.webm
Capture dimensions: 1024x768
Capture rate:       512 kbps
Capture FPS:        25

Guest:

Configured memory balloon size:      0 MB
OS type:                             WindowsXP
Additions run level:                 1
Additions version:                   5.0.12 r104815


Guest Facilities:

Facility "VirtualBox Base Driver": active/running (last update: 2016/01/17 15:20:40 UTC)
Facility "VirtualBox Desktop Integration": initializing (last update: 2016/01/17 15:23:21 UTC)
Facility "Seamless Mode": not active (last update: 2016/01/17 15:15:09 UTC)
Facility "Graphics Mode": not active (last update: 2016/01/17 15:20:40 UTC)

See any problems?

The host is Ubuntu 14.04.

When switching from 4.3.34 to 5.0.12, I have no idea at this point whether I was already using an official version or was instead using a distro version. I did reboot the guest WinXP between uninstalling and installing the Guest Additions, since that's the only way to get the old VBoxTray and VBoxService to quit running, but whether I needed to reboot the host, or what I'm supposed to do now that I've already installed 5.0.12 without rebooting, I don't know.

Originally this thread was posted elsewhere, I think under Linux hosts. Perryg determined that it didn't look like there was anything wrong with the host side, and so he moved the thread to Windows guests.

[Perryg]

And the new log file?

It is really important that you remove a repo version before you install the official version so if you don't remember that could actually be the reason for your issue.

First remove the already installed version and reboot the host, then install and test again. If it still fails I will need to see the new log file.

[BPickle]

Hi Perryg. Sorry. I didn't notice it was you who had posted. I really appreciate you trying to help. I've wondered if it's a lost cause. I really need to get this up and running ASAP. Using a loopback to access files in the VDI, that might work well enough, but it's going to be a real pain.

I rebooted the host after uninstalling 5.0.12. I then reinstalled the same. I detect no improvement whatsoever.

Someone out there ought to be able to tell us why VBoxTray and VBoxService can't be crashed in TaskManager, or why WinXP can't communicate with them after they're running.