Custom Query (16363 matches)
Results (202 - 204 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #7010 | duplicate | VM crashes while exiting from full screen mode | ||
| Description |
Host: Ubuntu 10.04 64 VirtualBox 3.2.4 2D,3D acceleration enabled VM crashes while exiting from full screen mode (host key + F) VirtualBox main window show VM status: Aborted |
|||
| #17647 | duplicate | Host-Only adapter failled to install | ||
| Description |
Hello, [How to reproduce it] From fresh installation, installation was ok,I had no problem to use host-only network and the host-only adapter was present. The problem began when I removed using VirtualBox GUI my host-only adapter, I was then not able to re-create it using either the GUI and the command line. [Similar issues] As you can imagine I've walk through the VirtualBox forum and Bug tracker before posting and I found a similar issue : + https://www.virtualbox.org/ticket/17354 + https://forums.virtualbox.org/viewtopic.php?f=6&t=86179 Here the antivirus was involded and disable it resolved the issue. In my case I've completely uninstall my corporate antivirus + deactivate Windows Defender without success. [Troubleshooting] + Repair VirtualBox + Uninstall VirtualBox + Remove %userprofile%\.virtualbox + Remove drivers in %windir%\System32\drivers + Remove registry keys about VirtualBox + Install 5.2 VirtualBox + Run Installer as Admin right + Run a Ccleaner registry cleaning With a result always the same, failed to create host-only adapter. [logs] VirtualBox Gui logs are showing : Failed to create a host network interface. Querying NetCfgInstanceId failed (0x00000002). Code d'erreur : E_FAIL (0x80004005) Composant : HostNetworkInterfaceWrap Interface : IHostNetworkInterface {455f8c45-44a0-a470-ba20-27890b96dba9} C:\Windows\INF\setupapi.dev.log
!!! idb: Failed to open driver package object 'vboxnetadp6.inf_amd64_37fe176ed22ac0b0'. Error = 0x00000005 <<< Section end 2018/03/27 18:20:45.540 <<< [Exit status: FAILURE(0x00000005)] [other] It's just a supposition but I'm wondering if the issue is trigered also as I respond [NO] once to the UAC pop-up message asking to install host-only driver (after choosing to create host-only adapter from the GUI). Thanks in advance for all your help, this issue is a blocker for me. |
|||
| #17686 | invalid | A virtual machine with networking bridged to a vlan host interface, cannot communicate | ||
| Description |
Hi! I have a vlan interface named vlan100: 2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 74:46:a0:90:c3:7d brd ff:ff:ff:ff:ff:ff
3: vlan100@eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 74:46:a0:90:c3:7d brd ff:ff:ff:ff:ff:ff
inet 172.17.100.222/24 brd 172.17.100.255 scope global noprefixroute vlan100
valid_lft forever preferred_lft forever
inet6 fe80::45a2:1264:44:3154/64 scope link noprefixroute
valid_lft forever preferred_lft forever
And I want a virtual machine bridged to this interface: <Network>
<Adapter slot="0" enabled="true" MACAddress="0800276C0E92" type="82540EM">
<DisabledModes>
<InternalNetwork name="intnet"/>
<NATNetwork name="NatNetwork"/>
</DisabledModes>
<BridgedInterface name="vlan100"/>
</Adapter>
</Network>
In this case the virtual machine cannot communicate, because of packets going to virtual machine appears tagged. You can see it tagged in attached screenshot of tcpdump in virtual machine. |
|||

