Custom Query (16363 matches)
Results (2338 - 2340 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #2393 | duplicate | Timer stalls in mode 2 | ||
| Description |
When the emulated timer runs in mode 2, it counts down from its initial value to 1, but does not then reload the initial value. Instead, it stays at 1. This behaviour prevents AROS (http://www.aros.org) from booting under VBox. This is the code used by AROS to initialise the timer:
And this is the code used to read the timer's value:
This works on real machines and on several other emulators. I don't know if it's much different from what other OSs do. |
|||
| #2394 | obsolete | 64-bit Opensolaris guest boot errors on 64-bit OpenSolaris host running NIS | ||
| Description |
I have three host installations of 64-bit OpenSolaris 2008.05 running VB 2.0.2 (amd64). On most I have no problems installing 64-bit guests, including OpenSolaris 2008.05 as a guest. However, if the OpenSolaris 64-bit HOST is running as an NIS client, then the OpenSolaris 64-bit GUEST, including LiveCD, boots extremely slowly and with the following errors, no matter if the guest machine has been configured with or without these options: network card (none), audio card (none), serial (none). Guest Errors (repeated): Method "/usr/sbin/avahi-daemon-bridge-dsd -D" failed with exit status 255. Method "/lib/svc/method/inetd-updatde start" failed due to signal KILL. gdm-binary....WARNING: Failed to start X server several times in a short time period... The errors are not present if VT is disabled and therefore 32-bit OpenSolaris is used. ACPI has been enabled in all tests, and mixtures of the other two settings have also been tested. The two computers used to test NIS were a Dell Precision 380 with 8GB memory and Pentium D 3GHz, the next was a Thinkpad Z61p with a core2Duo and 2GB memory that had been working with OpenSolaris as a host AND guest. I made the Thinkpad an NIS client, and then this problem materialized both with the installed version and with a LiveCD guest, just as described above. A third system that has never seen NIS runs OpenSolaris as a 64-bit host and guest perfectly (It is a Shuttle SX38P2 Pro). OpenSolaris runs NIS as a client fine and I don't think it is an OpenSolaris issue since this happens with a raw LiveCD boot with no networking in the guest whatsoever. It is this mix of OpenSolaris 64-bit GUEST on an OpenSolaris 64-bit HOST running NIS that makes the GUEST fail to boot properly. Although I've not been able to track down the settings that most influence this problem, I have found that having in your HOST's /etc/nsswitch.conf the "bad" entries below seems also to help manifest the VB problem, but the "good" entries do not. In both situations, NIS must actually be running and working for this to have an impact. Recall that this is in spite of the fact that your guest can be configured without a network card and the problems still occur. BAD: hosts: files nis dns GOOD: hosts: files dns nis BAD: aliases: files nis GOOD: aliases: nis files Sorry to be so verbose, but it can be difficult to describe the specifics of how & when this manifests, but it has only happened in the situations described. |
|||
| #2395 | fixed | VirtualBox failing when a virtual machine is started at boot -> fixed in 2.0.4 | ||
| Description |
Hi, I have a strange problem: I have a recent (2.0.2 PUEL) version of VirtualBox installed on a very up-to-date ubuntu 8.4 Hardy host. I have a specialized Linux version (IPCop 1.4.21) as guest; this is based on a 2.4.36 kernel. This virtual machine acts as firewall for the host and for the rest of my home network. It works (I'm using it to write this!). The strangeness begins if and when I start this virtual machine with USER=$VBOXUSER LOGNAME=$VBOXUSER start-stop-daemon --start --quiet --background --make-pidfile --pidfile $PIDFILE --name VBoxHeadless --chuid $VBOXUSER --startas /usr/bin/VBoxHeadless -- -s IPCop -a $VRDPADDR -p $VRDPPORT from within one of the startup scripts (I do attach the complete script along with the /etc/network/interfaces file I use to setup the bridges). If I do this the firewall machine starts ok and works (I can ssh into the machine and the whole firewall does work), but VirtualBox does not work ok anymore. Symptoms are:
I saw another, apparently similar bug that concerned the SDL libraries, but I do not think it is relevant here. I also tried to move the start of the Virtual Machine to the very end of the boot sequence (S95vbox-ipcop in /etc/rc2.d), but nothing changed. The behavior is very repetitive.
What did I do wrong? |
|||

