Custom Query (16363 matches)
Results (412 - 414 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #8125 | fixed | 4.0.2 Guru Mediation (PGM_PAGE_GET_STATE(pPage) == PGM_PAGE_STATE_ALLOCATED) => Fixed in 4.0.4 | ||
| Description |
XP SP3 Guest crashed while idle. Host is Sol Express. See attached log |
|||
| #8773 | fixed | 4.0.4 and 4.0.6 IO Subsystem errors => Fixed in SVN | ||
| Description |
There is a bug in IO subsystem of the 4.0.4 and 4.0.6 VBox, which is quite easy to reproduce. To reproduce it it is enough to copy the file into the guest OS (using, for example NFS as a medium, but You can try different media as well) and compute its checksum (using cksum utility). Such copy of the file generates quite different checksum, than original file. I have tested it on different Host/Guest OSes combination, so I think, that the bug is generic Here are examples : Host : Windows 7 64 bits, SP1 (guests : Oracle Linux 5.6, 64 bits, Solaris 10u9 64 bits) Host : Oracle Linux 5.6, 64 bits, (guests : Oracle Linux 5.6, 64 bits, Solaris 10u9 64 bits) Host : Solaris 10u9, 64 bits, (guests : Oracle Linux 5.6, 64 bits, Solaris 10u9 64 bits) The bug is able to reproduce on at least some larger files (around 1GB) Versions affected are (at least : 4.0.4 and 4.0.6) I have reproduced it with option "Used host IO cache" both - enabled, and disabled - results are the same. I am choosing "Solaris" as a host and guest, but - as I have written - the bug seems to be generic, as I have tested it on more Host/Guest combinations than this one. However - I haven't tested it on any 32-bit platform. |
|||
| #8483 | obsolete | 4.0.4 install errors - destroys host networking | ||
| Description |
At least in the case of an upgrade install, the latest 4.0.4 installer kicks this error when installing network drivers: Error Renaming Connection Cannot rename this connection. A connection with the name you specified already exists. Specify a different name. The install seems to finish, though Windows kicks the typical "this didn't install properly" dialogue. However, networking on the host is then broken, the network location is damaged beyond Windows ability to repair. In other words, your installer just bricked my machine until I apparently figure out how to repair the destruction of my network card/drivers/configuration. |
|||

