Custom Query (16363 matches)
Results (2140 - 2142 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #9141 | obsolete | Audio cuts out after many hours of playback | ||
| Description |
I'm trying out running some broadcast automation software inside a VirtualBox Windows XP VM, on a Linux host (Ubuntu 10.04). Naturally this means a long-running audio playback task, which works nearly perfectly, but: After about 10-12 hours of playback, sound abruptly cuts out. When it does so, the playback software on the VM roughly doubles the rate at which it is "outputting" sound. I imagine this is because some component downstream is emptying the soundcard buffer faster than it would ordinarily, perhaps because it has experienced some failure and is emptying the buffer fast to keep the guest from freezing? To get sound working properly again I only need to restart the playback application, not the VM or host OS. The backend device is ALSA, sent through dmix. The VBox log file contains nothing particularly interesting except for a pair of PIT reconfigure messages when I stop and restart the playback app. ALSA sound capture is intentionally redirected to null. I haven't tried Pulse output as Pulse isn't installed on the box in question. OSS output selects the wrong sample rate (plays 44.1khz guest output at 48khz, leading to a slight chipmunk effect) so I haven't used it for any significant amount of time. So obviously this isn't a very useful bug report yet. How do I get more detailed information about what's going on in the audio backend? |
|||
| #2435 | invalid | VRDPAUTH external on ubuntu hardy host -> Fixed in 2.1.2 | ||
| Description |
VirtualBox 2.0.2. I am unable to get the standard external vrdp authentication working on Ubuntu 8.04. In the VB logs I get: 00:00:44.533 VRDP: Logon: kelisport06 (192.168.1.10) build 2600. User: [sam] Domain: [] Screen: 0 00:00:44.534 VRDPAUTH: User: [sam]. Domain: []. Authentication type: [External] 00:00:44.535 VRDPAUTH: ConsoleVRDPServer::Authenticate: loading external authentication library'VRDPAuth' 00:00:44.535 VRDPAUTH: Could not resolve import 'VRDPAuth2'. Error code: VERR_SYMBOL_NOT_FOUND 00:00:44.535 VRDPAUTH: Using entry point 'VRDPAuth'. 00:00:44.584 VRDPAUTH: external authentication module returned 'access denied' 00:00:44.584 VRDPAUTH: Access denied. I exported: export VRDP_AUTH_DEBUG_FILENAME=/tmp/vbox_auth.log And tried again, /tmp/vbox_auth.log gave me: u[sam], d[], p[8] vrdpauth_pam_init: dlopen libpam.so failed vrdpauth_pam_init failed 4 This looks like VRDPAuth.so is linking to a non existent lib, indeed on hardy /lib/libpam.so does NOT exist, only /lib/libpam.so.0, I then did : $ sudo ln -s /lib/libpam.so.0 /lib/libpam.so And tried again, this time /tmp/vbox_auth.log gave me: u[sam], d[], p[8] init ok Using PAM service: login start ok conv: num 1 u[sam] p[8] conv: 0 returning password [8] auth ok pam_acct_mgmt failed 9. Authentication service cannot retrieve authentication info vrdpauth_pam_close completed This is where I get stuck. it seems that VRDPAuth.so is NOT compatible with PAM on ubuntu 8.08 What is happening? |
|||
| #3559 | fixed | vboxdrv & vboxnet services under debian based systems : incorrect S an K runlevel sequence numbers => Fixed in SVN | ||
| Description |
The vboxdrv & vboxnet service scripts contain the following line: # chkconfig: 35 30 60 Which suggests that the intent is to start these services at sequence 30 and stop them at 60. First, it would seem more logical to follow basic formula K = 100 - S i.e. 30-70 or 40-60. Is there a special reason for not stopping the vbox services in the same sequence as they are started? More importantly, under debian systems the chkconfig directive has no effect, chkconfig is a fedora/redhat directive. The start ans stop sequence numbers should be explicitly passed to update-rc.d command. This is no longer the case as with version 2.1.4 the start and stop sequence numbers are both 20 - the default for update-rc.d. This causes serious problems on systems that run vbox guests as services as they must be stoped before any attempt to stop vboxdrv & vboxnet. On a Ubuntu 8.10 stopping vboxdrv & vboxnet with a guest running seems to result in a kernel crash, changing the sequence numbers to 20 80 solved the problem. |
|||

