Custom Query (16363 matches)
Results (364 - 366 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #595 | fixed | Windows Vista host crashes | ||
| Description |
Under certain conditions, Windows Vista host kernel crashes, dumps, and after a blue screen, reboots ! Host: Windows Vista Ultimate, 32-bit, AMD Athlon XP, Aero Glass enabled, VirtualBox 1.5.0. Guests: Windows XP and Mandrake Linux 9.2. This is something that not always occur. (unreproduceble) -Technologov. 31.08.2007. |
|||
| #596 | fixed | Kernel bug while VM shuts down - SuSE Linux 10.0 AMD64 (Alsa) | ||
| Description |
Hello, I have a problem with VirtualBox running on the SuSE Linux 10.0 AMD64 host system. I am running the Windows XP as a guest OS. There are following messages loged in the syslog while the vboxdrv is loading:
When I shut down the VM there are following messages in the syslog:
I am using the VirtualBox_1.4.0_Linux_amd64.run. The same problem occured with the new VirtualBox_1.5.0_Linux_amd64.run. As a consequence of the problem reported by the above syslog messages I am not able to shut down the host Linux. It freezes while the "swapoff -a" command is executed. The VM and the guest WinXP runs OK. The only problem occurs when the WM shuts down. The same problem occurs even when I start VM with "empty" disk (without installed guest OS). I have fully patched SuSE Linux Eterprise Desktop 10.0 running on the "AMD Athlon 64 Processor 3000+" with 512MB RAM. Zdenek Cermak |
|||
| #597 | fixed | Cannot take a snapshot when there is a Writethrough hard disk attached | ||
| Description |
Trying to take a snapshot of a VM that has a disk in writethrough mode (even if you have other regular disks) causes the GUI to show an error: Cannot take a snapshot when there is a Writethrough hard disk attached ('/path/to/disk.vdi').
Result Code:
0x80004005
Component:
Machine
Interface:
IMachine {31f7169f-14da-4c55-8cb6-a3665186e35e}
Callee:
IConsole {1dea5c4b-0753-4193-b909-22330f64ec45}
This makes it hard to have a "system disk" that you want to snapshot and a "data disk" where you persist documents, settings and other stuff. The workaround today is to manually remove the disk from the VM using the settings window, take the snapshot, then re-add the disk. (And you must remember everytime you restore it). In VMWare, using the "persistent disk" that is the writethrough equivalent, the behaviour is to take the snapshot of regular disks and ignore the persistent ones. So, VBoxManage could have a similar behaviour, and maybe show a simple message like this when taking/restoring snapshots: The following disks are beign ignored because they are in writethrough mode: /path/to/disk1.vdi /path/to/disk2.vdi |
|||

