Custom Query (16363 matches)
Results (2470 - 2472 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #10670 | obsolete | XP guest hangs on reboot esp. after MS Updates | ||
| 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. |
|||
| #12911 | wontfix | Enhancement request: new network mode - Sandbox -> doable without support in VirtualBox | ||
| Description |
(This request was posted on the user forum here: https://forums.virtualbox.org/viewtopic.php?f=9&t=51729 PerryG suggested I post in Bugtracker, too.) I propose a new network mode, along with Bridged, NAT, Internal, etc., which sandboxes a guest so it can get internet access through the virtual NIC but no other network access on the host LAN. As of version 4.2.16, a guest on NAT network settings, in addition to getting internet access, can also access other host network resources in other IP address ranges besides the range NAT provides. My test guest had a 10.0.2.15 IP address, and I could ping and open shared folders on my 192.168.0.### physical LAN the host is connected to. I understand this is expected behavior for NAT. However, I've read of some folks on the forum wishing to use guests as sandboxes, keeping internet access only on a guest or for testing or isolating viruses. Since the guest can access the host's LAN at least by IP address, these users aren't as secure as they think they are. Some other users and I (https://forums.virtualbox.org/viewtopic.php?f=9&t=61005&p=284332) wish to have internet access to a guest with remote-in capabilities, which guests won't have any access to host LAN services. There are no built-in Virtualbox network settings that allow internet-access-only network connections for a guest. Such a setup is apparently possible by routing the guest through a pfsense guest with various filters in place (https://forums.virtualbox.org/viewtopic.php?f=6&t=52103). Adding another guest would add more complexity to a situation that would be very easy if all one had to do was choose a different network setup in Virtualbox. Since Virtualbox already offers such unique arrangements as linked clones, storage bandwidth control, and memory ballooning, far beyond just virtual hardware, sandboxing a guest would enhance Virtualbox even more. One could still network such sandboxed guests together in their own mini-LAN with another network card set to internal network. |
|||
| #13025 | fixed | help file may be wrong on disk Bandwidth control command | ||
| Description |
Need a little help with the disk bandwidth control command for my "Win7CVXeams" guest (running 4.2.16). Section 5.8 of the help file shows the following commands to limit disk bandwidth on a guest: VBoxManage bandwidthctl "VM name" add Limit --type disk --limit 20M VBoxManage storageattach "VM name" --controller "SATA" --port 0 --device 0 --type hdd --medium disk1.vdi --bandwidthgroup Limit I entered the first line, with my guest's information inserted, like this: VBoxManage bandwidthctl Win7CVXeams add CVXeams --type disk --limit 10 "VBoxManage bandwidthctl Win7CVXeams list" returns this: Name: 'CVXeams', Type: Disk, Limit: 10 Mbytes/sec So the first command seems to have worked. The second command was entered like this: VBoxManage storageattach Win7CVXeams --controller "SATA" --port 0 --device 0 --type hdd --medium G:\Win7CVXeams\Win7CVXeams.vdi --bandwidthgroup CVXeams VBoxManage returns a list of options for the storageattach command and the error: "Unknown option: --controller" (Vboxmanage doesn't seem to know what the help file knows...) So I delete the "--controller" and replace it with "--storagectl", making my command this: VBoxManage storageattach Win7CVXeams --storagectl "SATA" --port 0 --device 0 --type hdd --medium G:\Win7CVXeams\Win7CVXeams.vdi --bandwidthgroup CVXeams and the command completes. Something I'm missing? Or does the help file need an update? |
|||

