VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (2203 - 2205 of 16363)

Ticket Resolution Summary Owner Reporter
#10670 obsolete XP guest hangs on reboot esp. after MS Updates scottgus1bug
Description

I have had XP guests sometimes hang when doing a Windows-Update-invoked reboot. Both XP and 7 hosts, different versions of Virtualbox.

The guests get to just before the VM window would shrink to 640x480. They stop responding, no disk or network activity, just XP's peacefully-running light blue (not BSOD blue) background. If I pause/unpause or save-state/restart the VM window turns black and gets a grid of lines filling half the window. The VM does nothing else and I have to reset it. Then it boots up normally.

Two XP guests sometimes exhibit this behavior for now. I used to have this problem in a third guest, but it hasn't shown itself for a long while, despite still getting the same Windows updates as the two present offenders.

I have searched and found references to audio being the culprit (one guest has audio, one used to but does not now). Also, "absolute pointer" has been fingered, but I never use that setting and neither guest has ever had it turned on.

The attached zipped logs refer to these VMs:

XP guest: "XPnet"; XP host, audio on, no absolute pointer, VB version 3.1.2 (this one runs all the time with no scheduled reboots, I think all the logs in the zip are from Windows-Update-induced hanged reboots)

XP guest: "Email Tester" Windows 7 host, audio used to be on but now disabled in VM settings, no absolute pointer, VB version 4.0.16 (this one is shut down by a host-induced Vboxmanage command every night; only the most recent log was a Windows-update-induced hanged reboot, the earlier logs should be normal shutdowns. I've also had this VM running on version 3.2.12 on a different Windows 7 host, with the same behavior)

The third guest "Antispam" (same host as "Email Tester") that used to have this problem also was XP, audio on, no absolute pointer. Audio is still on. It just had a Windows Update same time as the other two, but did not hang during reboot. The attached log is this VM's last Windows-Update-successful-reboot log for reference.

Guest Additions are current in each VM. I have not seen if other causes for in-guest-invoked reboots cause hanging, and I haven't had the hang happen when I tell the guest to reboot from the guest's Start menu or a "Shutdown -r". It seems that Windows Update is the only rebooter that causes this to happen that I've noticed so far. And I've not experienced Windows Update having a problem rebooting the physical XP PCs I have at home.

#10671 obsolete Unable to set the necessary display resolution in the guest Rafcio
Description

I'm unable to set the second display to the external monitor native resolution. The host is RHEL 6.2 on Thinkpad T420 and the guest is Windows XP. There is Lenovo external monitor attached to the laptop with the native resolution of 1680x1050. I installed the guest additions in the client and tried to set the second display to the external monitor native resolution to no avail. Linux correctly recognizes the external monitor resolution, so I'm sure the problem is in the VBox code. I messed around trying different things, but basically I have either 1600x900 (the laptop's internal display native resolution) as the maximum resolution for the second display, or a whole bunch of bigger resolutions (some ridiculous 4000 by something), but no typical and popular resolutions to pick from (like 1680x1050). If the bigger resolutions are displayed (right now they are not), then the next resolutions after 1600x900 is 1600x1200. Because I messed around with things (i.e. reinstalled the guest additions) and I'm not sure what made the bigger resolutions disappear from the display settings in XP, but I'm sure that 1680x1050 wasn't available and either 1920x1080 or 1920x1200 (or both). I'd expect that those popular resolutions were always available, instead those ridiculous big resolutions were available even though they were much bigger than the monitor's native resolution. I added the "custom" 1680x1050 resolution using the vboxmanage command (that was one of the first things I tried), but it doesn't seem to have any effect. The command "vboxmanage getextradata global CustomVideoMode1" returns "Value: 1680x1050x32", so the value seems to be properly set, but still no 1680x1050 resolution in the guest to choose from. In the process of troubleshooting this issue I believe I ran into another bug. In the documentation I read about sending the video resolution hint to the client, but it has to be sent to the specific client (cannot be done globally). The client has been created using the GUI interface and except that external monitor resolution everything seems to be OK, but somehow the client is not in the list. When I try to send the hint with the command "vboxmanage controlvm RRSWWSXPVM setvideomodehint 1680 1050 32" I get an error message (VBoxManage: error: Could not find a registered machine named 'RRSWWSXPVM'... (truncated)" and the command "vboxmanage list vms --long" returns nothing. How could that be? The VM is basically working fine execpt the resolution issue.

#10674 obsolete Shared folder not accessible - sometimes EDoe
Description

In my (Win XP SP3) guest the host's (Win XP SP3) shared folder - accessed as volume D:\ - is sometimes "not accessible", but sometimes it is.

After the error message the folder tree in Windows Explorer (guest) often disappears, then pressing F5 might bring it up again, maybe after a couple of trials. Copying files to the (not-read-only) volume also works only sometimes.

Variations of access rights, set from either host or guest, do not affect this phenomenon.

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.

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