vSLX - issue powering on virtual chassis.

[JanZorz]

Hi,

I installed vSLX 2.3.0 on Ubuntu 16.04 system and I’m using slxos 20.1.1 as OS. I followed the installation instructions in slx-20.1.1-vslx-guide.pdf and installed the whole thing into a KVM VM with CPU=host setting and nested virtualization turned on (AMD proc, so I have “svm” flag present in /proc/cpuinfo). 

I’m able to create a template with example in the manual and I’m able to create a chassis, but when I turn it on (or start), things go wrong quite quickly and the whole process freezes. With “start” command in vsh I dont even get to any prompt, it just says that machine was powered on successfuly.

/var/log/libvirt/qemu/PB_1_av1.log says this:

2021-03-11 14:53:45.251+0000: starting up libvirt version: 1.3.1, package: 1ubuntu10.30 (Guilherme G. Piccoli <gpiccoli@canonical.com> Wed, 26 Feb 2020 13:23:18 -0300), qemu version: 2.10.0, hostname: netscan-r-vslx.6clabs.com
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin QEMU_AUDIO_DRV=none /usr/bin/kvm -name PB_1_av1 -S -machine pc-q35-2.6,accel=kvm,usb=off -m 8192 -realtime mlock=off -smp 4,sockets=4,cores=1,threads=1 -uuid 90d0087c-503b-429c-9a93-d15ab2f36d05 -nographic -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-PB_1_av1/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -boot strict=on -device i82801b11-bridge,id=pci.1,bus=pcie.0,addr=0xc -device pci-bridge,chassis_nr=2,id=pci.2,bus=pcie.0,addr=0xe -device nec-usb-xhci,id=usb,bus=pcie.0,addr=0x5 -drive file=/VM/templates/snapsh/av1/PB4000.img,format=qcow2,if=none,id=drive-virtio-disk0 -device virtio-blk-pci,scsi=off,bus=pci.2,addr=0x2,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=26,id=hostnet0,vhost=on,vhostfd=28 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:e6:52:1d,bus=pcie.0,addr=0x3 -netdev tap,ifname=Tav1000,script=/VM/qemu-link,id=hostnet1,vhost=on,vhostfd=29 -device virtio-net-pci,netdev=hostnet1,id=net1,mac=00:11:22:aa:bb:00,bus=pcie.0,addr=0x7 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -device virtio-balloon-pci,id=balloon0,bus=pcie.0,addr=0x8 -device 'cpci,bus=pci.1,addr=1,lib=libpbsysfpga.so,args=chip_version{0x16052462}model_id{4000}hw_rev{2}chassis_id{av1}eeprom_parent_dir{/VM/templates/snapsh}' -device 'cpci,bus=pci.2,addr=1,lib=libpcid-linux-64.so,args=devname{88375}' -msg timestamp=on
Domain id=3 is tainted: high-privileges
Domain id=3 is tainted: custom-argv
Domain id=3 is tainted: shell-scripts
2021-03-11T14:53:45.669639Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/2 (label charserial0)
ioctl(TUNSETIFF): Device or resource busy
avalanche_intr_set_vector

and /var/log/syslog says this:

Mar 11 10:07:58 netscan-r-vslx kernel: [ 2228.396562] device vnet0 entered promiscuous mode
Mar 11 10:07:58 netscan-r-vslx kernel: [ 2228.420882] br0: port 2(vnet0) entered forwarding state
Mar 11 10:07:58 netscan-r-vslx kernel: [ 2228.420900] br0: port 2(vnet0) entered forwarding state
Mar 11 10:07:46 netscan-r-vslx virtlogd[2501]: End of file while reading data: Input/output error
Mar 11 10:07:58 netscan-r-vslx libvirtd[1719]: Domain id=4 name='PB_1_av1' uuid=90d0087c-503b-429c-9a93-d15ab2f36d05 is tainted: high-privileges
Mar 11 10:07:58 netscan-r-vslx libvirtd[1719]: Domain id=4 name='PB_1_av1' uuid=90d0087c-503b-429c-9a93-d15ab2f36d05 is tainted: custom-argv
Mar 11 10:07:58 netscan-r-vslx libvirtd[1719]: Domain id=4 name='PB_1_av1' uuid=90d0087c-503b-429c-9a93-d15ab2f36d05 is tainted: shell-scripts
Mar 11 10:07:58 netscan-r-vslx systemd-udevd[4530]: Could not generate persistent MAC address for Tav1000: No such file or directory
Mar 11 10:07:59 netscan-r-vslx kernel: [ 2229.927120] device Tav1000 entered promiscuous mode
Mar 11 10:08:00 netscan-r-vslx virtlogd[2501]: End of file while reading data: Input/output error

Any idea, anyone?

I have a feeling that things go wrong when creating tuntap interface, but I’m not sure. 

Thank you very much for all your help!

Jan Zorz, 6connect labs 

[SamPirok · Accepted solution]

Hi, thank you for your patience while I looked in to this for you. I tried to run this past our Data Center techs but I’m told vSLX is only supported by our service engineers (SEs) at the moment. I’d recommend reaching out to your SE for help with this. If you’re unsure who to reach out to for your SE, you can always go here and we will find you a local contact to speak with: https://www.extremenetworks.com/contact-sales/

[JanZorz]

as additional info - when I power-on the chassis and qemu process is running, this interfaces are created:

12: brav1: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
    link/ether 0a:cc:c7:22:44:75 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::8cc:c7ff:fe22:4475/64 scope link
       valid_lft forever preferred_lft forever
19: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master br0 state UNKNOWN group default qlen 1000
    link/ether fe:54:00:e6:52:1d brd ff:ff:ff:ff:ff:ff
    inet6 fe80::fc54:ff:fee6:521d/64 scope link
       valid_lft forever preferred_lft forever
20: Tav1000: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 9206 qdisc pfifo_fast state UNKNOWN group default qlen 1000
    link/ether 66:27:5f:64:ad:1a brd ff:ff:ff:ff:ff:ff
    inet6 fe80::6427:5fff:fe64:ad1a/64 scope link
       valid_lft forever preferred_lft forever
 

They are in puzzling state: UNKNOWN.