AVIZ Networks
HomeRelease
  • Open Networking Enterprise Suite (ONES)
    • ONES Application
      • ONES Telemetry Collector(s) and Visibility
      • ONES Time Scale Metric Calculation
      • ONES Rule Engine
      • ONES Orchestration
      • ONE DL
      • ONES AVIZ Support
      • ONES Security
      • ONES Multisite
    • Licensing
  • What's new?
  • Getting Started
    • Supported Switch Platforms and NOS
    • Scalability
    • Subscription
    • ONES Installation
      • Installation Pre-requisites
      • Download ONES Package
      • Installing ONES Application
      • Upgrade ONES Application
      • ONE-DL cloud Deployment
      • Installing ONES Agents 3.1.0
        • ONES Telemetry Agent Installation
        • ONES Server Agent Installation
        • ONES Orchestration Agent Installation
        • Agent Less Telemetry
          • Cumulus(NVUE API)
          • Arista EOS (eAPI)
          • CISCO NXOS (GRPC)
      • Adding New Controller
      • Installing ONES Multisite
    • VM Deployment
      • VMware ONES Deployment
      • KVM ONES Deployment
      • Upgrade VM
  • ONES Web GUI Administration
    • Login Page
    • Adding Devices
    • AI Asistance
    • Monitor
    • Inventory
      • Devices
      • Configurations
        • YAML Based Configuration
          • VXLAN-Symmetric
            • VXLAN-Symmetric-SAG-no-mclag-vrf
            • VXLAN-Symmetric-SAG-mclag-vrf
            • VXLAN-Symmetric-SVI-no-mclag-vrf
            • VXLAN-Symmetric-SVI-mclag-vrf
            • VXLAN-Symmetric-SAG-vrf-RoCE
          • VXLAN-SVI
            • VXLAN-SVI-no-mclag-IPv6-eBGP-IPv6-SVI
            • VXLAN-SVI-no-mclag-iBGP-IPv4-Underlay
            • VXLAN-SVI-no-mclag-eBGP-IPv6-SAG
            • VXLAN-SVI-no-mclag-eBGP-IPv4-Underlay
            • VXLAN-svi-no-mclag-eBGP-BGPU-Underlay
          • VXLAN-SAG
            • VXLAN-SAG-no-mclag-iBGP-no-host
            • VXLAN-SAG-no-mclag-iBGP-BGPU-Underlay
            • VXLAN-SAG-no-mclag-iBGP-BGPU-Underlay-HostPO
            • VXLAN-SAG-no-mclag-ebgp-no-host
          • VXLAN-MGLAG
            • VXLAN-MCLAG-ibgp-sag
            • VXLAN-MCLAG-ebgp-svi.yaml
            • VXLAN-MCLAG-ipv6-ibgp-sag
            • VXLAN-MCLAG-ebgp-BGPU-IPv6SAG
            • VXLAN-MCLAG-ibgp-BGPU-IPv6svi
            • VXLAN-MCLAG-ipv4-ibgp-svi
            • VXLAN-MCLAG-ipv6-ebgp-sag
          • VXLAN-Asymmetric
            • VXLAN-Asymmetric-SAG-no-mclag
            • VXLAN-Asymmetric-SAG-mclag
            • VXLAN-Asymmetric-SVI-no-mclag
            • VXLAN-Asymmetric-SVI-mclag
          • MH-VXLAN
            • MH-VXLAN-ibgp-sag
            • MH-VXLAN-ipv6-ibgp-sag
            • MH-VXLAN-Asymmetric-SAG
            • MH-VXLAN-ebgp-BGPU-IPv6SAG
            • MH-VXLAN-ipv6-ebgp-sag
            • MH-VXLAN-Symmetric-2-SAG-vrf
          • MCLAG
            • MCLAG-IPv4-SVI-AccessHosts
            • MCLAG-ibgp-BGPU-Underlay-IPv4SVI-AccessHosts
            • MCLAG-ibgp-IPv6-Underlay-IPv6SVI-AccessHosts
            • MCLAG-IPv4-Underlay-IPv6SVI-AccessHosts
            • MCLAG-IPv6-Underlay-IPv6SVI-AccessHosts
          • L3-MCLAG
            • L3-MCLAG
            • L3-MCLAG-bgpU-combinedLink
            • L3-MCLAG-bgp-combinedLink
          • L2-LS
            • L2LS-EC-L2
            • L2LS-EC-L3-ipv4
            • L2LS-EC-L3-ipv6
          • iBGP
            • i-BGP-IPv6-CLOS-IPv6-host
            • i-BGP-IPv6-CLOS-IPv4-svi
            • i-BGP-IPv4-CLOS-L2PO-host
            • i-BGP-IPv4-CLOS-L2-host
            • i-BGP-IPv4-CLOS-IPv6-svi
            • i-BGP-IPv4-CLOS-IPv4-PO-host
            • i-BGP-BGP-U-CLOS-IPv4-svi
            • i-BGP-BGP-U-CLOS-IPv4-host
          • e-BGP
            • e-BGP-IPv6-CLOS-IPv6-host
            • e-BGP-IPv6-CLOS-IPv4-svi
            • e-BGP-IPv4-CLOS-L2-host
            • e-BGP-IPv4-CLOS-IPv6-svi
            • e-BGP-BGP-U-CLOS-IPv6-svi
            • e-BGP-BGP-U-CLOS-IPv6-host
          • BGP-PO
            • BGP-PO-SLFOW-LeafOnly-EC
            • BGP-PO-SLFOW-LeafOnly-EC-incr1
            • BGP-PO-MCLAG-SLFOW-LeafOnly-EC
          • LeafOnly-EC
          • IPCLOS-1-IPv4-SVI-AccessHosts
          • DHCP-IPCLOS-IPv4-SVI-AccessHosts
          • VXLAN-Symmetric-SAG-vrf-RoCE
        • GUI Based Configuration
        • NetOps Based Configuration
    • Rule Engine
      • Rules Type
        • Add Rules: Entity
        • Add Rules: Entity by Properties
      • Alerts
    • Analytics
    • Settings
    • Integrations
      • Slack Channel Integration
      • Zendesk Support Integration
      • Service Now Integration
      • Cloud Services
        • Splunk
        • Amazon S3
    • Accounts
  • Support
    • How to contact Aviz Networks Support?
    • Backup and Recovery
Powered by GitBook

Copyright © Aviz Networks, Inc.

On this page
  • QCOW Deployment
  • Download Qcow2 Package
  • Create the VM using GUI App virt-manager
  • Create the VM using QEMU (XML configuration)
  • Connect to Machine
  • Credentials to access ONES QCOW2 VM

Was this helpful?

  1. Getting Started
  2. VM Deployment

KVM ONES Deployment

PreviousVMware ONES DeploymentNextUpgrade VM

Last updated 2 months ago

Was this helpful?

QCOW Deployment

Download Qcow2 Package

  • Work with Aviz Sales/Support contact to create an account on Aviz Networks Support Portal

  • Login to with your account credentials

  • Click on the Downloads section, under ONES, click to download ONES Release 3.1.0

  • Untar the file

    • tar -I pbzip2 -xf ONES-3.1.0_Full.tar.bz2
      aviz_ones/
      aviz_ones/aviz_ones.qcow2  
      aviz_ones/aviz_ones.xml  
      aviz_ones/aviz_ones.xml.back
  • Navigate to aviz_ones

  • Copy ONES Release 3.1.0 package (qcow2) to KVM Hypervisor Server

Create the VM using GUI App virt-manager

If your host server has Ubuntu Desktop and virt-manager installed you can use it to deploy the VM. Make sure you can start the Virtual Machine Manager and that it connects successfully to the local hypervisor.

Creating a VM with virt-manager is very straightforward, Use the following steps to deploy the ONES-Application

  • File -> New Virtual Machine -> Import existing disk image -> Forward

Now the ONES Application is ready to use

Create the VM using QEMU (XML configuration)

  • Edit an existing XML configuration file from the following template using vi

vi aviz_ones.xml
<domain type="kvm">
  <name>aviz_ones_3.1.0</name>
  <memory unit="KiB">25777216</memory>
  <currentMemory unit="KiB">25777216</currentMemory>
  <vcpu placement="static">16</vcpu>
  <resource>
    <partition>/machine</partition>
  </resource>
  <os>
    <type arch="x86_64" machine="pc-i440fx-1.5">hvm</type>
    <boot dev="hd" />
  </os>
  <features>
    <acpi />
    <apic />
  </features>
  <clock offset="utc" />
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <devices>
    <emulator>/usr/bin/qemu-system-x86_64</emulator>
    <disk type="file" device="disk">
      <driver name="qemu" type="qcow2" cache="writeback" />
      <source file="/home/aviz/aviz_ones/aviz_ones.qcow2" />
      <target bus="virtio" dev="vda" />
    </disk>
    <serial type="pty">
      <source path="/dev/pts/3" />
      <target port="0" />
    </serial>
    
    <interface type="network">
	<model type="e1000" />
        <source network="br0" />
        <address type="pci" domain="0x0000" bus="0x00" slot="0x00" function="0x0" />
    </interface>
   <controller type="usb" index="0" />
    <memballoon model="virtio">
      <alias name="balloon0" />
      <address type="pci" domain="0x0000" bus="0x00" slot="0x04" function="0x0" />
    </memballoon>
  </devices>
</domain>
User Inputs in XML File
Line #2   The Name of the VM
Line #3   The amount of System Memory for the VM
Line #4   The amount of System Memory for the VM
Line #5   The number of vCPU Core for the VM
Line #25  The Path to the qcow2 VM image file
Line #35  The name of the Linux bridge on the host machine
  • Start the VM

virsh create <VM XML configuration file>

#sonic@sonic-39:~$ virsh create aviz_ones.xml 
#Domain ONES_VM01 created from aviz_ones.xml
#sonic@sonic-39:~$ 

If you see a permission error run the virsh command with sudo may fix the issue

  • Check the VM status

sonic@sonic-39:~$ virsh list
 Id    Name                           State
----------------------------------------------------
 8     aviz_ones_3.1.0                running
sonic@sonic-39:~$ 

Connect to Machine

sonic@sonic-39:~$ virsh console 8 
Connected to domain 'aviz_ones_3.1.0'
Escape character is ^] (Ctrl + ])

ONES login: 

Credentials to access ONES QCOW2 VM

Username: aviz
Password: Aviz@123

https://support.aviznetworks.com