Custom Query (16363 matches)
Results (2128 - 2130 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #2509 | obsolete | Microchip mpasm.exe assembly puts VB into an infinite loop | ||
| Description |
If you run mpasm.exe 4.11 from Microchip (basically a text mode MSDOS program) VirtualBox goes into an infinite loop. The MS Windows XP SP 3 session does not respond at all. the VirtualBox session in the Linux host space run all out. It will not respond to a kill, but kill -9 works. The MS Windows session and the Virtual Box application are completely unresponsive. |
|||
| #2554 | fixed | host port forwarding stops working | ||
| Description |
I have several Linux virtual machines running NAT'ed on a Linux host (all Ubuntu 8.04). Each has a port from the host mapped to port 80 in the guest, and a port from the host mapped to port 22. vbguest1: 2201 -> 22, 1081 -> 80 vbguest2: 2202 -> 22, 1082 -> 80 vbguest3: 2203 -> 22, 1083 -> 80 vbguest4: 2204 -> 22, 1084 -> 80 vbguest5: 2205 -> 22, 1085 -> 80 I also run openvpn in each slice connecting each to a private openvpn network. All guests are clients to a another physical machine that runs as an OpenVPN server elsewhere. After 10 days of uptime one could no longer reach the web server or ssh server in vbguest1 via the host forwarded ports. However, both the web server and the ssh server were reachable from the openvpn network. They also both worked correctly inside the slice. Looking at the log files I could find nothing unusual anywhere. I telnet'ed to host:1080 and the TCP/IP session would be negotiated, however no data would flow to or from the web server application in the guest. The other slices were all working correctly. vbguest2 runs the same application suite as vbguest1. And the applications in vbguest2 were correctly accessible via the host forwarded ports. |
|||
| #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. |
|||

