Custom Query (16363 matches)
Results (97 - 99 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1393 | obsolete | Protocol error trying to rename directory on share (Windows host, Linux guest) | ||
| Description |
~$ sudo mount -t vboxsf -o uid=1000,gid=1000,exec workspaces /ws ~$ cd /ws /ws$ mkdir a /ws$ ls -ld a drwxrwxrwx 1 blaukopf blaukopf 0 2008-04-07 19:16 a /ws$ mv a b mv: cannot move `a' to `b': Protocol error Host is Windows XP, guest is Ubuntu Linux. I am able to read, write and create files and directories on the share. File renaming works, directory renaming does not. |
|||
| #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. |
|||
| #1403 | obsolete | vbox doesn't grab USB devices after insertion with open criteria | ||
| Description |
If a filter is set up for a particular USB device then vbox will grab it and it will show up in the guest's lsusb output. This behavior is consistent no matter when the USB device is plugged in (before or after the VM boots) If the filter is open so it's supposed to match everything vbox will grab the USB device only if it was plugged in before virtual machine starts. If the USB device is plugged in after the virtual machine is running lsusb shows nothing unless a users selects the device in the Device menu. Make the behavior the same everywhere. If you have an open filter to match everything vbox should grab all USB devices when they're plugged in and pass them to the guests. |
|||

