Custom Query (16363 matches)
Results (577 - 579 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #4931 | worksforme | VirtualBox segfault | ||
| Description |
(unformatted content removed) |
|||
| #1400 | obsolete | Windows 98 SE guest aborts on first reboot after install, log shows unknown command 0x2e | ||
| Description |
I am trying to get Windows 98 Second Edition working as a guest OS with VirtualBox-OSE 1.5.6 under Debian-lenny (but VirtualBox upgraded from -unstable to see if this bug was already fixed). The log has the following: Log created: 2008-04-07T07:46:28.988455000Z Executable: /usr/lib/virtualbox/VirtualBox Arg[0]: /usr/lib/virtualbox/VirtualBox Arg[1]: -comment Arg[2]: Windows 98 Second Edition Arg[3]: -startvm Arg[4]: 45d9dd7a-60cc-42f6-46b8-b59c797edd7a unknown command: 0x2e unknown command: 0x2e unknown command: 0x2e I know 98SE isn't officially supported but some people have reported success so I was hoping that I would be able to get it working. If possible I'd like to help fix it, but it depends on what exactly the unknown command is: if it's an opcode then fixing it is probably outside my expertise; it it is an interrupt I might be able to help, and if a CD-ROM thing, I could probably spelunk the qemu code which does not exhibit this particular bug. Even if I can't fix it myself, or someone can get to it before me, I would be happy to help with the debugging by providing more detailed logs, if there are commands for producing such. |
|||
| #14941 | duplicate | General Failure "Do not use this!!!" on latest 5.0.10 r104061 for Debian 8 | ||
| Description |
Just upgraded from 4.3 to 5.0.10 on my Debian Jessie Box. Went to launch a VM and got this: General failure - DON'T USE THIS!!!. (VERR_GENERAL_FAILURE).
Result Code: NS_ERROR_FAILURE (0x80004005) Uninstalled VB (and all traces of it including ~/.config/VirtualBox) and even chucked existing VMs on the hard drive. Re-installed fresh (including a new download w/verified SHA256 sums), copied VM from backup, and still getting the error!! Looking at VBox.log, at the end there seems to be a reference to a path that does not exist on my system. Perhaps this is the problem? --C64 |
|||

