VirtualBox

Changes between Initial Version and Version 2 of Ticket #16045


Ignore:
Timestamp:
Oct 7, 2016 5:31:25 PM (8 years ago)
Author:
Valery Ushakov
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #16045

    • Property Host type other → Linux

  • Ticket #16045 – Description

    initial v2  
    11Hi everyone,
    2 Thanks for VirtualBox, it's a great product.
     2Thanks for !VirtualBox, it's a great product.
    33
    4 I use VirtualBox as my hypervisor for virtual OpenStack deployments.
     4I use !VirtualBox as my hypervisor for virtual OpenStack deployments.
    55I have been using it since the early 5.0 times to deploy multi-nodes OpenStack deployments. These deployments typically include 4 to 12 nodes as VBox machines, using multiple e1000 interfaces (4 per vbox machine, 3 of them being host-only network interfaces).
    66
    … …  
    99- Large RHEL6.x hypervisor (128Gb or 192Gb RAM). These typically are kept up-to-date with the RedHat kernels.
    1010- One large undercloud VBox VM (16Gb, pagefusion off, nestedpaging on, vtxvpid on, largepages on, paravirt KVM). It has 4 NICs:
    11  -- nic0: hostonly to vboxnet0
    12  -- nic1: hostonly to vboxnet1
    13  -- nic2: hostonly to vboxnet2
    14  -- nic3: Bridged to external network (Main Hypervisor interface)
     11 - nic0: hostonly to `vboxnet0`
     12 - nic1: hostonly to `vboxnet1`
     13 - nic2: hostonly to `vboxnet2`
     14 - nic3: Bridged to external network (Main Hypervisor interface)
    1515
    1616- 8 to 16 overcloud VBox VM's with the same settings as the above but using a slightly different NIC configuration:
    17  -- nic0: hostonly to vboxnet0
    18  -- nic1: hostonly to vboxnet1
    19  -- nic2: hostonly to vboxnet1 (to make a BOND with nic1)
    20  -- nic3: hostonly to vboxnet2
     17 - nic0: hostonly to `vboxnet0`
     18 - nic1: hostonly to `vboxnet1`
     19 - nic2: hostonly to `vboxnet1` (to make a BOND with nic1)
     20 - nic3: hostonly to `vboxnet2`
    2121
    22 On nic1/nic2 (connected to vboxnet1), I use a mixture of 802.1Q Tagged VLAN's (this is specific to OpenStack).
     22On nic1/nic2 (connected to `vboxnet1`), I use a mixture of 802.1Q Tagged VLAN's (this is specific to OpenStack).
    2323
    2424As I am testing some OpenStack corner cases, I am deleting/re-creating this setup on a very frequent basis (sometimes 4 times per day).
    2525
    2626Description of problem:
    27 On latest RHEL6.8 kernels (2.6.32-642.6.1), the vboxnet[0-2] network stop 'working' after just a few minutes when deploying the nodes.
     27On latest RHEL6.8 kernels (2.6.32-642.6.1), the `vboxnet[0-2]` network stop 'working' after just a few minutes when deploying the nodes.
    2828No traffic can be seen by tcpdump'ing the adapters on either the Hypervisor or the nodes.
    2929On the hypervisor (RHEL6.8 host), I attempt to capture network traffic like this:
     30{{{
    3031# tcpdump -nevi vboxnet1
     32}}}
    3133or
     34{{{
    3235# tcpdump -nevi vboxnet2
    33 
     36}}}
    3437On the undercloud node, I attempt to capture traffic like this:
     38{{{
    3539# tcpdump -nevi eth1 (connected to vboxnet1)
     40}}}
    3641or
     42{{{
    3743# tcpdump -nevi eth2 (connected to vboxnet2)
    38 
     44}}}
    3945At the begining of a deployment (PXE'ing the overcloud nodes), things start working properly but stop after just a few minutes.
    4046
    4147Things were working properly with:
    42 VBox 5.0.26 + Kernel 2.6.32-642.3.1.el6.x86_64
    43 VBox 5.0.26 + Kernel 2.6.32-642.4.2.el6.x86_64
    44 VBox 5.1.6 + Kernel 2.6.32-642.4.2.el6.x86_64
     48- VBox 5.0.26 + Kernel 2.6.32-642.3.1.el6.x86_64
     49- VBox 5.0.26 + Kernel 2.6.32-642.4.2.el6.x86_64
     50- VBox 5.1.6 + Kernel 2.6.32-642.4.2.el6.x86_64
    4551
    46 I am also taking great care in making sure that the vbox kernel modules are freshly compiled on the running kernel by cleaning out the /lib/modules and forcing a rebuild (using DKMS on VBox 5.0 and using vboxconfig on VBox 5.1)
     52I am also taking great care in making sure that the vbox kernel modules are freshly compiled on the running kernel by cleaning out the /lib/modules and forcing a rebuild (using DKMS on VBox 5.0 and using `vboxconfig` on VBox 5.1)
    4753
    4854Things stop working after just a few minutes with:
    49 VBox 5.1.6 + Kernel 2.6.32-642.6.1.el6.x86_64 (the latest RHEL6.8 kernel).
     55- VBox 5.1.6 + Kernel 2.6.32-642.6.1.el6.x86_64 (the latest RHEL6.8 kernel).
    5056
    5157I am currently trying to isolate the issue and see if I can provide more data.
     58
    5259Is there a way to put an hostonly network in debug mode?
     60
    5361Thanks,

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy Automated Access Etiquette