virtualbox.org

Hi. On 11/27 my WinXP (Home) VM on Ubuntu 14.04 refused to successfully boot up. I think a recent update caused the problem, which didn't appear until I tried to enable a USB port to print to, which caused a crash, which then gave me an opportunity to see that it wouldn't reboot.

At some point I discovered that disabling USB 2.0 allowed it to boot, but then I had no networking and no shared clipboard.

Since then I've installed the extensions and guest additions for 4.3.34. Now I've uninstalled that and have installed 5.0.10 from Oracle. As far as I can tell, the extensions and guest additions now installed match, both being 5.0.10. Still I have no networking or shared clipboard, whereas I did before.

It was set to NAT before, and I have also tried Bridged Network. I added a DHCP server, though 'VBoxManage list dhcpservers' now lists two. I've tried pinging from within the VBox the IPs for these two dhcp servers, and all I get is 'Destination host unreachable.'

Since I neither have networking nor a shared clipboard, even though the settings tell me it's bi-directional, I'm thinking some driver or file still isn't right, but all the VBox files in the Windows/system32 directory and the Program Files directory appear to have about the same date and time. And mouse capturing is working correctly, since I can go from the VM to the Host and back again just fine.

One other oddity is that, while working on all of this, I could not use TaskManager in WinXP to crash VBoxTray and VBoxService.

Any suggestions on what I should try next?

Post the guests log file ( as an attachment ). Right click on the guest in the Main Manager then click show log. Save and post as an attachment. Compress if it is too large to post.

Thanks, Perryg.

Attached is the log.

I forgot to say that the share folder no longer appears in the WinXP guest. I saw some error message linked to the WinXP systray about a network drive. And WinXP is wanting to re-activate because of supposed hardware changes.

Code: Select all

00:00:00.993448 File system of '/home/bpickle/OutPutFile.vdi' is ext4
00:00:01.042744 crCtlSubmit failed (rc=VERR_NOT_SUPPORTED)
00:00:01.593339   Name              <string>  = "WinXP" (cb=6)

It seems you have created an issue for yourself. The guest would have created a file named WinXP.vdi and you have something totally different. I would look into the reason for the name difference and make sure that the file actually is the right one. The error listed above is an indication that something is not supported and that is never a good sign if this was a working guest.

As for the re-activation that is something that you will also need to address since Windows is saying that the hardware has changed.

The file is the right one, and is the one that I have been using since setting this up in July. It contains the contents of my hard drive in my WinXP desktop that was functioning fine until the motherboard died.

I can certainly try changing the name of the file and get back to you.

After altering the name of the virtual hard disk, I tried disabling the network connection and re-enabling it, and that didn't re-establish networking.

But note the lines in the log that you omitted. The one about VERR_NOT_SUPPORTED comes right after the ones about the clipboard, and thus that error message concerns the clipboard rather than the name of the virtual hard disk. So what about the clipboard would be triggering that error message? I think that's the question.

I'm guessing that Guest Additions gets loaded much later in the log. If that is the case, does this error message mean that WinXP itself is not a supported version? Is that why it suddenly stopped functioning?

Have you actually tried rebooting the guest instead of using the saved state?

I have many times, but not after only changing the file name of the virtual hard disk. It's working. It's the shared folder, networking, and shared clipboard that aren't working. Thus far I've never had trouble with the virtual hard disk, regardless of the name.

I rebooted the VM, and still have no functionality, though those first error messages are reduced. Here's the first lines now:

Code: Select all

VirtualBox VM 5.0.10 r104061 linux.amd64 (Nov 10 2015 17:52:21) release log
00:00:00.691485 Log opened 2015-11-29T21:55:12.875319000Z
00:00:00.691487 Build Type: release
00:00:00.691490 OS Product: Linux
00:00:00.691491 OS Release: 3.16.0-53-generic
00:00:00.691492 OS Version: #72~14.04.1-Ubuntu SMP Fri Nov 6 18:17:23 UTC 2015
00:00:00.691511 DMI Product Name: MS-7693
00:00:00.691519 DMI Product Version: 4.0
00:00:00.691586 Host RAM: 7773MB total, 5729MB available
00:00:00.691589 Executable: /usr/lib/virtualbox/VirtualBox
00:00:00.691590 Process ID: 5146
00:00:00.691590 Package type: LINUX_64BITS_UBUNTU_14_04
00:00:00.724198 Installed Extension Packs:
00:00:00.724217   Oracle VM VirtualBox Extension Pack (Version: 5.0.10 r104061; VRDE Module: VBoxVRDP)
00:00:00.725383 Console: Machine state changed to 'Starting'
00:00:00.729011 GUI: UIMediumEnumerator: Medium-enumeration finished!
00:00:00.729787 Using XKB for keycode to scan code conversion
00:00:00.731549 SUP: Loaded VMMR0.r0 (/usr/lib/virtualbox/VMMR0.r0) at 0xffffffffc101a020 - ModuleInit at ffffffffc1039400 and ModuleTerm at ffffffffc10398d0
00:00:00.731570 SUP: VMMR0EntryEx located at ffffffffc103cde0 and VMMR0EntryFast at ffffffffc103c610
00:00:00.734663 Guest OS type: 'WindowsXP'
00:00:00.741110 crCtlSubmit failed (rc=VERR_NOT_SUPPORTED)
00:00:00.756642 File system of '/home/bpickle/VirtualBox VMs/WinXP/Snapshots' (snapshots) is ext4
00:00:00.756662 File system of '/home/bpickle/VirtualBox VMs/WinXP/WinXP.vdi' is ext4
00:00:00.789562 Shared clipboard service loaded
00:00:00.789578 Shared clipboard mode: Bidirectional
00:00:00.790554 Drag and drop service loaded
00:00:00.790560 Drag and drop mode: Bidirectional

Shut the guest down and then post a new log file ( as an attachment )

Here is the log after shutting down.

Is VERR_NOT_SUPPORTED referring to a problem with VMMR0.r0?

Actually the new log is showing that the guest should be functioning properly. I do see the one error but I am not even sure that is an issue. More than likely a red hearing at this point.
The clipboard, and the shared network show as working in the log so I would focus my attention to the guest at this point. One of the actual Windows folks will need to help you with that though so I will hold off for now.

Note: I would think if you had a ring0 issue you would be seeing a guest that does not actually boot or something in the log file about it.

In other words, at this point it looks like it's a Guest Additions issue, or some problem with how WinXP is interfacing with the Guest Additions?

Apparently I can't print to a USB printer either. So here is the complete list of known issues at present:

No networking. Guest appears to not be able to hear the DHCP.
No shared clipboard, in either direction.
No shared folder. I get this message in WinXP: "Could not reconnect all network drives.
Can't print to a USB printer.

I was wondering if there was some sort of residual stuff from a different version of Guest Additions in the registry or somewhere that might be messing things up, and thus have installed and uninstalled (by running the uninstall file) 4.3.10 and 4.3.34, but nothing has worked so far.

If the share folder worked, then I could print to a PDF, pass the PDF off to the host via the share folder, and print it off via the host. But without the share folder working, and without networking that could allow me to email it to myself, I don't have an easy workaround.

virtualbox.org

Lost networking and shared clipboard

Lost networking and shared clipboard

Re: Lost networking and shared clipboard

Re: Lost networking and shared clipboard

Re: Lost networking and shared clipboard

Re: Lost networking and shared clipboard

Re: Lost networking and shared clipboard

Re: Lost networking and shared clipboard

Re: Lost networking and shared clipboard

Re: Lost networking and shared clipboard

Re: Lost networking and shared clipboard

Re: Lost networking and shared clipboard

Re: Lost networking and shared clipboard

Re: Lost networking and shared clipboard

Re: Lost networking and shared clipboard

Re: Lost networking and shared clipboard