Custom Query (16363 matches)
Results (2524 - 2526 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #2582 | fixed | VirtualBox crash while Reactos 0.3.7 booting | ||
| Description |
ReactOS simply crash while Reactos 0.3.7 bootig. Host: Ubuntu 8.10 VirtualBox 2.0.4 |
|||
| #2583 | obsolete | Shared Folder still in configuration file and checked even if it is not any more used | ||
| Description |
I used a shared folder '/data/export/local/admin' for a Solaris 10 guest. Then I removed it from the list of shared folders. When I now try to boot the guest I got the following error
Shared folder path '/data/export/local/admin' is not absolute.
Result Code:
NS_ERROR_INVALID_ARG (0x80070057)
Component:
SharedFolder
Interface:
ISharedFolder {8b0c5f70-9139-4f97-a421-64d5e9c335d5}
Meanwhile I had the folder moved to a different partition and added a symbolic link to it. This error is strange because of two reasons. First of all, I would have not expected any dependency of this folder by the guest, since I had removed it from the configuration. Secondly, I would feel that a symbolic link should be OK here as well as long as it points to an existing target, which it does.
When removing the link and creating the directory hierarchy the guest boots well. The "Shared Folders" menu does not have an entry for '/data/export/local/admin'. Still the .xml file for the guest has the following entry
...
<SharedFolders>
<SharedFolder name="admin" hostPath="/data/export/local/admin" writable="true"/>
</SharedFolders>
...
I suspect that the .xml configuration does not get clean up properly and the checking code does not take into account that the virtual machines does not have this shared folder dependency. Please find the complete .xml file. |
|||
| #2584 | obsolete | vboxfs EPROTO error during file read | ||
| Description |
I recently attemped to use vboxsf/vboxfs to make an Ubuntu 8.04 host filesystem available in an Ubuntu 8.04 guest instance. All worked fine initially. A relatively simple application in the guest reads and writes files into a folder in the shared directory. Every once in a while the read() system call returns EPROTO. However, simply repeating the open/read/close works. It was failing about 1% of the time. I mounted the filesystem via NFS rather than vboxfs and the operations work 100% 24 hours per day for days on end. The operations also work days on end if the files are read/written to the filesystem inside the guest. I was unable to find anything in the log files at the time of the failed read calls. |
|||

