Custom Query (16363 matches)
Results (556 - 558 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #927 | fixed | Fails to bring host networking down on startup error | ||
| Description |
I had been using a "host pipe" serial port, which I create using an external command (socat) before booting the VM. Unfortunately, the command exits and the socket file is deleted when I shut down a VM. If the socket file is missing when the VM is booted, this results in the following error: Serial device 0 cannot attach to char driver
.
VBox status code: -102 (VERR_FILE_NOT_FOUND).
Result Code: 0x80004005
Component: Console
Interface: IConsole {1dea5c4b-0753-4193-b909-22330f64ec45}
And the VM fails to start. I disabled the serial port and then tried to start the VM again, but then got the following rather cryptic error: Unknown error creating VM (VERR_HOSTIF_INIT_FAILED).
VBox status code: -3100 (VERR_HOSTIF_INIT_FAILED).
Result Code: 0x80004005
Component: Console
Interface: IConsole {1dea5c4b-0753-4193-b909-22330f64ec45}
Only after a lot of frustration did I discover that this was caused by the fact that my "host interface" network adapter had not been brought down after the first attempt to start the VM. Manually running the script I use to bring the vbox0 interface down solved the problem, but that was only after I had already deleted the VM and its snapshots and created a new one :-( Please:
The first error message could also be improved by explicitly mentioning which file could not be found. |
|||
| #929 | fixed | Upgrading Win XP guest additions doesn't upgrade VBoxMRXNP.dll | ||
| Description |
I used to have VBox 1.4, and then upgraded to 1.5.2. I started my Win XP guest, and asked it to install the guest additions again. Seemed to go fine, but shared folders didn't work. It turns out that the VBoxMRXNP.dll file wasn't upgraded. I attach an install log from installing the new guest additions. |
|||
| #930 | fixed | Crashed unexpectedly at restart | ||
| Description |
I created and used for a couple of times a test VM with just Firefox 3 Beta 1 installed on top of a patched Windows XP SP2. Today I created and added a second (virtual) hard disk and also changed the default NAT to be a host network interface and moved the NAT as the second interface. Now each time that I start the VM it crashed after a few seconds during boot, and even if I switch back to previous settings or create a new machine with the same main (virtual) disk it does the same... Thanks |
|||

