Custom Query (16363 matches)
Results (1705 - 1707 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #3076 | fixed | VirtualBox 2.1.0 silently fails guest file opens when VBox process runs out of file descriptors | ||
| Description |
Performing some large Visual Studio builds on Windows 2003 using a project located in a shared folder was failing with random windows errors about being unable to open specific files. The files named existed and could be opened at a later time with no problems. On a hunch, I increased the ulimit of file descriptors from 256 to 1024 and restarted the virtual machine. After then I was able to use VStudio without errors. (I was also able to reproduce the error by attempting a Windows command line copy of the project with "xcopy /s <shared-project-location> <local-project-location>") It would be helpful if when VirtualBox encounters EMFILE errors to log a notice (rate limited if need be) to the log file for the machine to give a hint as to the problem. |
|||
| #4486 | fixed | VirtualBox 3.0.2 hard hangs Solaris 10u6 kernel when running HW assisted VMs -> fixed in SVN/3.0.6 | ||
| Description |
After installing the 3.0.2 update (and rebooting to make sure driver structures were consistent), attempting to run previously built and running (under 2.x) virtual machines (Windows 2008, Linux Ubuntu 8.10, Centos) will eventually hard hang the Solaris 10 host kernel it is running upon. Environment: S10u6 patched to 138889-08 on AMD Opteron 2376, 4Gb memory. VirtualBox 3.0.2 r49928 for SunOS. Started Win2k8 and Ubuntu guests headless (with HW virtualization enabled). System hard hangs after about 3 hours runtime. Could not break console to MDB (system was booted w/debugger enabled). System does not character echo nor respond to network (ping). No disk activity observed. Same hang happened almost immediately after starting 3 guest VMs concurrently. All VMs had HVM enabled with one CPU allocated to each guest (IO Apic enabled). This configuration had been running solidly under VB 2.2.2 for months uptime. No entries were noted in either the VM logfile(s) nor syslog. Guests could be resumed after host is rebooted. Currently reverting to 2.4.x. |
|||
| #2279 | invalid | VirtualBox 2.0.2 64-bit guest OS not working | ||
| Description |
Supposedly with virtualbox 2.0 support for 64-bit guest OS was added, however every Linux 64-bit distro I try won't get past the CPU test. Here's the error message I get from my last test of Ubuntu desktop: "This kernel requires an x86-64 CPU, but only detected an i1586 CPU." others 64-bit OS I've tried with similar error messages include. RHEL 3,4,5 64-bit OS, and the original RHEL WS 3 that came with my SUN W2100z, which also doesn't work with virtualbox. I've had load directly on this system RHEL WS 3 and RHEL 4 as native OS ok. I've read a lot which talked about VT-x/AMD-V support within your BIOS. But at this point everything loads just find natively, just not in virualbox, which leads me to think it's still not working in virtualbox. Any ideas what needs to be down to get it to work? Thanks |
|||

