Custom Query (16363 matches)
Results (121 - 123 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #14892 | fixed | ERROR_MAX_THRDS_REACHED / unable to shutdown | ||
| Description |
the ERROR_MAX_THRDS_REACHED was displayed when attempting to open the main vbox app (where I can see and control all VM that I have. I then also got an error: Failed to stop the virtual machine Freebsd10A. Invalid machine state Paused when checking if the guest entered the ACPI mode). Callee RC: E_FAIL (0x80004005) When I tried to "close" the machine (after shutting down the OS inside) More details: Host Windows Vista Guest Freebsd / several network interfaces The guest has been running for a long time (over a week, maybe 2 or 3). The host was up all the time too, neither host nor guest where suspended at any time. I first noted that the guest could no longer connect to the public internet. Yet the guest still had network to the host (I was connected via ssh, and the ssh session was as old as the guests uptime) I then attempted to start the vbox control center (see above) and got the ERROR_MAX_THRDS_REACHED. Clicking ok, got me to start the control center. Then I shutdown (via ssh) the freebsd inside the VM, after that I went to the VM window (in which I can see the fbsd console), and attempted to close / power off the machine. I get the above error. I was not able to resume it. Attempting several times I eventually got "the instruction 0x598878e0 referenced memory at 0x00000010 the memory could not be read" |
|||
| #11614 | fixed | Virtualbox crashes Os X host | ||
| Description |
I run a vm with Windows 7 guest on a Os X host, VM running maximized (not fullscreen) on separate monitor. Sometimes (almost once a day) when moving between vm and host (for instance checking mail or browser on host) computer will crash hard (entire computer). Cannot guarantee that this is a virtualbox problem, but virtualbox is the last thread in panic dump from os x. Problem has existed entire 4.2 version (also present in 4.2.10). |
|||
| #8408 | fixed | VHD corruption when taking snapshots => Fixed in SVN | ||
| Description |
My config Virtualbox 4.0.4 Windows 7 x64 Gold Ultimate (fully patched, excluding SP1) Dell XPS 1640 Summary Taking a snapshot when the disks are of VHD format can corrupt the data on the disk. Affects:
Try the following vboxmanage createhd --filename "C:\Virtual Machines"\bugtest.vhd --size 1024 --format vhd New VM (in the GUI)
Reconfigure VM:
Start VM Insert "Ubuntu desktop 10.04 x86 desktop" Boot ubuntu CD and switch to root console (ctrl-alt-f1; sudo -i) Use parted to create a single primary partition & format with fat32. mount /dev/sda1 /mnt echo root > /mnt/root.txt shutdown (use the GUI if you're booting that particular ISO) take new snapshot "root" power on, boot, console, sudo, mount cat /mnt/root.txt (successful) echo child1 > /mnt/child1.txt shutdown (use the GUI if you're booting that particular ISO) <here, you might want to boot + mount again just to make sure the file did get "written"...don't know why I had trouble with this> take new snapshot "child1" power on, boot, console, sudo, mount cat /mnt/child1.txt (file is missing) You can get the file back by rolling back to "child1", deleting "child1", and powering on. Comments Restoring my (now corrupt) hard disks from backup. I know VHD is not that common a format, but still...very obvious corruption of data. Back to VirtualBox 3 a second time. Other Thoughts While we're at it, can we fix the format of the differencing VHDs so they mount correctly in Windows 7? Currently, only base disk VHDs created by VirtualBox will mount correctly via disk management. I like the ability to natively mount in Windows, which is why I've used VHD in the past. (Who knows, might be a Microsoft format limitation rather than VirtualBox.) Hope this helps! Aaron Curley |
|||

