Custom Query (16363 matches)
Results (1579 - 1581 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1614 | fixed | Missing Run Level shortcuts with generic Linux .RUN install => Fixed in 1.6.2 | ||
| Description |
I have installed VB three times, using the generic Linux .RUN installer. I noticed that the VirtualBox kernel driver and networking are not initialized in run level 2, which is the default run level in Debian. I'm using "testing" and "unstable", so the pre-packaged Debian binaries for "stable" are not usable for me. Symbolic links S20vboxdrv -> ../init.d/vboxdrv S20vboxnet -> ../init.d/vboxnet are installed in /etc/rc3.d/ and /etc/rc5.d/ but not /etc/rc2.d/ which is the Debian default run level. Please consider putting the symbolic links into Run Levels 2 through 5. People who know enough to alter their run level will know to delete these symbolic links if they do not want those drivers to be active. Sadly, it took me a while to figure out why VirtualBox would give me an error when I first started my machine, but work once I "rebuilt" the driver. The initial installation and subsequent driver "rebuilds" all occurred in Run Level 2, which I must assume your installer does not check before creating the symbolic links. |
|||
| #1615 | fixed | insufficient guest time synchronisation (in 1.5.6 was OK) | ||
| Description |
Hello VirtualBox programmers, 1.6.0 time synchronisation of the guest system is insufficient. In version 1.5.6 it worked absolutely sufficient. Background: we (industry OEM, paying for VirtualBox licences) are using a data acquisition program as VirtualBox guest (host=Win XP(e), guest = Win XPe). Using VirtualBox 1.5.6 time synchronisation is fine, the acquired trend data do not show any interruption. After updating to VirtualBox 1.6.0 (for test purposes) we get an unusable time delay of the guest machine. The time delay of the guest is resynchronised after some minutes, but the data trend lines aquired every second get an interruption when automatic resync is done. We need a guest time differing less than one second of the host time! This is a killer criterion for our future using of VirtualBox! martl |
|||
| #1616 | worksforme | Cannot connect to services on the host on Mac OS X | ||
| Description |
I have told VirtualBox to use 192.168.0.0/8 as the NAT network, because 10.0.2.0/8 does not work at all, as it conflicts with Mac OS X's Internet Sharing network. However, if I try to ssh into the host (which I assume should be reachable via the gateway IP 192.168.0.2 or the DNS server IP 192.168.0.3), it times out. The host firewall is set to allow everything. In particular, NetworkManager picks up a DNS server address of 192.168.0.3, but that doesn't work at all - it just times out. So I have to manually configure the DNS servers. I cannot work around the issue by using a bridged network, as that is not supported by VirtualBox on Mac OS X. So this problem makes it very inconvenient to share files between host and guest. |
|||

