Custom Query (16363 matches)
Results (2440 - 2442 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #11898 | obsolete | Problem install extension 4.2.14 | ||
| Description |
hi, i have Windows 7 32bit . i installed virtual box 4.2.14 . After i tried to install Oracle_VM_VirtualBox_Extension_Pack-4.2.14-86644.vbox-extpack , but i received that error: Installazione dell'Extension Pack C:/Users/Sebastiano_Cala'/Desktop/Oracle_VM_VirtualBox_Extension_Pack-4.2.14-86644.vbox-extpack non riuscita. The installer failed with exit code 2: VBoxExtPackHelperApp.exe: error: Missing --sha-256 option rcExit=2. Codice 'uscita: E_FAIL (0x80004005) Componente: ExtPackManager Interfaccia: IExtPackManager {3295e6ce-b051-47b2-9514-2c588bfe7554} Please , help me to resolve that error. |
|||
| #16055 | fixed | TLS issues in Ubuntu guest after Windows 10 anniversary update | ||
| Description |
I run Ubuntu 14.04 LTS in VirtualBox 5.1.6 on Windows 10. Hyper-V is disabled. Everything has worked great until the host system was upgraded with KB3181403 (Windows 10 anniversary update). I already tried the same VM on W8.1 and W7. It works without any issues. But the problem can be reproduced on other machines with W10 + KB3181403. When accessing content via an HTTPS conncetion on W10 with KB3181403 I get the following error in my terminal now: CODE: SELECT ALL EXPAND VIEW unable to access '...': gnutls_handshake() failed: A TLS packet with unexpected length was received. It doesn't happens with curl. I have noticed the behavior with my own service application and with apt-get update. Last one fails now for all packages with an HTTPS source. |
|||
| #9532 | fixed | all incoming Ethernet multicast dropped => Fixed in SVN | ||
| Description |
Running a Solaris 10 guest in 4.1.2 on Solaris 11 (build 172). I have the network configured in bridged mode with the Intel Pro/1000 MT Desktop adapter (I have tried all other adapters and all exhibit this same problem). It appears that Virtualbox is dropping all incoming multicast packets. The host VNIC used by Virtualbox sends them up, but they're being dropped somewhere between the VNIC and the guest adapter (snoop in the guest doesn't show them). This is easily demonstrated by pinging 224.0.0.1 and observing that all nodes in the IPv4 subnet receive the multicast ICMP echo except for the Virtualbox guest. As a side-effect of this, IPv6 in the guest doesn't work _at all_. IPv6 depends on multicast to do neighbor discovery, router discovery, and stateless address autoconfiguration. None of this works in the guest as a result of this bug. |
|||

