Custom Query (16363 matches)
Results (2482 - 2484 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #15365 | obsolete | USB problem after upgrading to 5.0.18 | ||
| Description |
Hello, I have been in the community and request assistance since I could not find a solution in web. Here is the issue: I am running ubunty 14.04 LTS as the host system. Up to version 4.3.12 I have not had any issues with USB everything worked fine. Earlier I tried 4.3.16 and did not work. Now I have upgraded to 5.0.18. In summary 4.3.12 was the last version which works fine for me. Of course I could go back to 4.3.12 however I decided to to contact you for a deep dive and hopefully for support since I believe that I am not the only person in the world having this issue but maybe the first one to seriously willing to tackle it. I am added to vboxusers and have installed the right extpack. Everything seems to be fine according to the community moderator. But it is not. When I start vbox and try to add a USB filter device I got the greyed out <no device available> even though it is visible in Ubuntu. As stated the last working release for me was 4.3.12. Let me know what kind of information you need in order to investigate. Thanks |
|||
| #15363 | fixed | CentOS 7.2 VirtualBox repo metadata is broken | ||
| Description |
# yum search virtualbox Loaded plugins: fastestmirror base | 3.6 kB 00:00:00 epel/x86_64/metalink | 23 kB 00:00:00 extras | 3.4 kB 00:00:00 updates | 3.4 kB 00:00:00 virtualbox/7/x86_64/signature | 198 B 00:00:00 virtualbox/7/x86_64/signature | 951 B 00:00:00 !!! virtualbox/7/x86_64/primary FAILED http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/primary.xml.gz: [Errno -1] Metadata file does not match checksum Trying other mirror. ... failure: repodata/primary.xml.gz from virtualbox: [Errno 256] No more mirrors to try. http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/primary.xml.gz: [Errno -1] Metadata file does not match checksum |
|||
| #15362 | obsolete | Failed to start VM (Hardening) - VirtualBox 5.0.18 | ||
| Description |
Hello, I'm not able to start any virtual machine using VirtualBox 5.0.18. I'm able to launch the VM's when using 4.3.12, which from my understanding, excludes hardening code. Attached is the hardening log and error message screenshot. I've seen other tickets that are similar and the solution seems to be to try a later build, but none of the other builds I've tried except 4.3.12 work for me. My host system is Windows 7 x64. McAfee suite (scrubbed of possibly sensitive information): McAfee Host Intrusion Prevention
Version number: 8.0
Build date: Sunday, December 15, 2013
Build Number: 8.0.0.2919
License Type: Licensed
Language: Automatic
Security Content Version: 8.0.0.6894
Security Content Created On: Wednesday, March 02, 2016
Patch: 4
McAfee Agent
Version number: 4.8.0.1938
Managed
Last security update check: 4/27/2016 12:01:24 PM
Last agent-to-server communication: 4/27/2016 12:10:37 PM
Agent to Server Communication Interval (every): 45 minutes
Policy Enforcement Interval (every): 35 minutes
McAfee ePO Deep Command Discovery Plugin
Version number: 2.3.0.376
Language: Multiple
McAfee Drive Encryption Agent
Version number: 7.1.3.547
Language: Multiple
McAfee File and Removable Media Protection
Version number: 4.3.1.138
Language: Multiple
McAfee Drive Encryption
Version number: 7.1.3.547
AccessData Enterprise Agent
Version number: 6.0.0
McAfee VirusScan Enterprise + AntiSpyware Enterprise
Version number: 8.8.0 (8.8.0.1445)
Build date: 8/21/2015
Scan engine version (32-bit): 5800.7501
Scan engine version (64-bit): 5800.7501
DAT version: 8146.0000
DAT Created on: 4/25/2016
Buffer Overflow and Access Protection DAT version: 700
Installed Patches: 6
Installed Modules:
Copyright © 1995-2015 McAfee, Inc.
All Rights Reserved.
www.mcafee.com
Please let me know if any other information is required. Thank you! |
|||

