XP Guest Additions issue

[Richard]

I am running 5 Ubuntu boxes 4 are Hardy and 1 is gutsy all with XP SP2 Guests.

When I install or updated to virtualbox 1.6.2 I had to install guest additions several times to get network shares working.

For example: I had my Documents folder shared in 1.5.6 on a gutsy box and a net use script that mounted upon login. As soon as I upgraded to 1.6.2 and installed guest additions the net use script wouldn't work. I knew this problem existed from my other boxes and installed them again, no worky, again, no worky, and finally the 4TH TIME my net use script mounted it automatically.

Thank you for your product.

[pentagonik]

Fix for network problems

[pentagonik]

I've attached a "sf_fix.reg" file to this defect. Please save this file on your guests hard drive, double click on it and say "Yes" if it asks to write to the registry.

After a reboot, the net use script should working again. This issue will be fixed in the next release of VBox.

[Richard]

This fix didn't work for speed wise. I have to share the folder and then change my scripts to net use x: \10.0.2.2\SharedFolder

Otherwise to open a simple word document sometimes takes a whole minute.

I am also getting a BSOD on some print shares... I'll attach a screenshot. My aunt is telling me she is getting a black screen with small dots on it (she sent me a screen)

[Richard]

video issues randomly happens.

[Richard]

log right after a crash trying to go from full screen back to windowed mode

[Richard]

2nd log

[Richard]

So to summarize issues with guest additions:

Network issues with sharing (extremely slow with \vboxserver share) so fix is to share in host and mount with \10.0.2.2\sharename

Video issues black screens at random (screenshot attached)

Bluescreens with some printer shares

Will restart gdm sometimes when switching from or to full screen mode.

[Klaus Espenlaub]

A test with Additions r33126 was reported to show a BSOD.

[Jamie Jackson]

I'm getting something very similar, and it *might* be related.

Ubuntu 8.10 host VirtualBox 1.6.2 from Sun site Windows XP SP2 guest

Steps to reproduce: Start VirtualBox & start "xp1" VM In "xp1" vm, Start >> Run "\xboxsvr\anothershare"; click ok I get the same sort of vm screen as the attached screenshot.

Other operations trigger the issue, too, but this is a pretty reliable one. Other triggers are mainly ones that access or try to access network shares (not just \vboxsvr\* shares).

I don't know what happens to the VM. I don't know if it's a graphics only problem, or what, but sending ctrl-alt-del doesn't do anything to it. I don't seem to, or don't know how, to recover the session aside from rebooting the vm. However, I suppose the vm is unresponsive anyway, even under the graphic weirdness.

I'd assume that this is sort of equivalent to a BSOD, though I haven't seen a proper BSOD, just the black screen with rainbow streaks (same as attached png).

Additions r33126 didn't work for me either (thanks, though, klaus).

Not sure where to go from here, nor how to troubleshoot.

[Jamie Jackson]

Forgot to mention that this problem is not particular to 1.6.2. The reason I tried 1.6.2 is I was having the same problem (recently) in 1.6.0 (also the sun package).

Sorry about the lack of <br> above, but I guess it's still legible.

[Richard]

Also on another note the guest resolution auto-resize function has never worked right since 1.5.4. I had issues with additions 1.6.3 and 1.6.0 and just reinstalled 1.5.4 and instantly realized better handling of guest window resizing.

[pentagonik]

Please try again with 1.6.4. If you still get errors, please report back here.

[Richard]

Still having network issues. The video issues will take a while to fully test. can not mount \vboxsvr\Documents on one box and on the others it is still slower to access files than using \10.0.2.2\Documents.

[Richard]

1.6.4 just switched from full screen and it kills my icon layout back to 640x480 woo

[Jamie Jackson]

So far, so good with 1.6.4: No more black, streaky freezes.

[Richard]

Ok huge issues still now instead of nice black screens and reboots on print. I'm also getting achingly slow usage from \vboxsvr\share and going to \10.0.2.2\share reboots without fail! I'm attaching a screenshot for your viewing pleasure.....

[Richard]

Virtualbox doing it's thing

[Frank Mehnert]

When did this BSOD happen, during boot or reboot?

[Richard]

it causes a reboot. It happens when I use my network to access a share on the host sometimes when using \vboxsvr\share and everytime when using \10.0.2.2\share. The funny thing is that 1.6.0 if I remember correctly was the opposite. I tried a different network adapter FAIL.

[Greg Knapp]

Just adding I also experienced a BSOD in Windows Vista when it first booted when restoring the Window from a minimized state. This has only happened once - I've been running Virtual box for approximately two weeks.

My host OS is Ubuntu 8.04 running VirtualBox 1.6.4 and Windows Vista SP1 with guest additions installed. I didn't have any applications open in Vista at the time as it had just booted. I had just upgraded to IE8 beta 2 though.

Would it help to attach my VB log file?

[Frank Mehnert]

All: Did 1.6.6 fix the problem for you?

[Richard]

No and 2.0 didn't either. I have attached a screenshot again. I am going to upgrade to 2.02 today but I don't think it's been fixed in that either.

[Richard]

woo

[Richard]

When is this going to be fixed? I have 2.0.2 and it has happened to me twice within the last week? What's the deal? It's been doing this since 1.6.0. Is this on the roadmap to be fixed? Is there work being done to fix it?

[sunlover]

Disable the WebClient? service in the guest. See ​http://forums.virtualbox.org/viewtopic.php?t=2155&start=0&postdays=0&postorder=asc&highlight=mrxdav especially the last comment.

[Frank Mehnert]

Did that help?

[Richard]

Lol no

[sunlover]

Similar issues have been fixed some time ago. Please use VirtualBox 3.0.12 or 3.1 beta ( ​http://forums.virtualbox.org/viewtopic.php?f=15&t=24827 ). Make sure to install corresponding guest additions.

[Technologov]

No response, please close.

-Technologov

[Frank Mehnert]

Well, let's wait for at least 4 weeks for a response.