KVM Issuse

Discussion in 'Linux Admins, Storage and Virtualization' started by GCM, Nov 11, 2015.

  1. GCM

    GCM Active Member

    Joined:
    Aug 24, 2015
    Messages:
    137
    Likes Received:
    43
    So,

    Having an issue with KVM on Ubuntu 14.04 that is driving me insane.

    This is a new box, so I will go through what I did:

    - Set up bonded NIC's. Failover, 1 active at a time
    - Set up a bridge on top of that bond.

    - Installed KVM on Ubuntu
    - Installed virt-manager on Ubuntu

    - Installed a VM without issue, but it wouldn't see the bridged interface, only virtual NAT.

    - Shut down the VM to try and diagnose. VM now refuses to start due a connection error.

    - Virt-manager and Virsh both refuse to create an VM's due to connection reset.

    Here is my network config:

    Code:
    # The loopback network interface
    auto lo
    iface lo inet loopback
    # EM1 Configuration
    auto em1
    iface em1 inet manual
    bond-master bond0
    bond-primary em1
    
    # EM2 Configuration
    auto em2
    iface em2 inet manual
    bond-master bond0
    
    # Bond EM1 & EM2
    auto bond0
    iface bond0 inet manual
    bond-mode active-backup
    bond-miimon 100
    bond-slaves none
    
    # Bridge for Bond0
    auto br0
    iface br0 inet static
    bridge_ports bond0
    address 192.168.3.130
    netmask 255.255.252.0
    gateway 192.168.1.1
    dns-nameservers 8.8.8.8
    bridge-fd 9
    bridge-hello 2
    bridge-maxage 12
    bridge-stp off
    
    Anyone have similar issues? I've sat here for hours trying to find a fix to get any VM's created, but I'm hitting a brick wall.
     
    #1
  2. RTM

    RTM Active Member

    Joined:
    Jan 26, 2014
    Messages:
    427
    Likes Received:
    142
    If you use virt-manager you probably won't see the bridge, instead you can select "specify shared device name" on the NIC of your VM then you can enter br0 under "bridge".
     
    #2
  3. GCM

    GCM Active Member

    Joined:
    Aug 24, 2015
    Messages:
    137
    Likes Received:
    43
    Tried that, but it's still no go.

    I can't even create new VM's atm, or start because they'll just error out:

    @BUSNYVM01:/etc/libvirt/qemu# virsh -d 0 start BUSDJ01
    start: domain(optdata): BUSDJ01
    start: found option <domain>: BUSDJ01
    start: <domain> trying as domain NAME
    error: Failed to start domain BUSDJ01
    error: Connection is closed
     
    #3

Share This Page