• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login
Netgate Discussion Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login

Interfaces not showing in Dataplane KVM

Scheduled Pinned Locked Moved Problems Installing or Upgrading TNSR Software
24 Posts 3 Posters 5.1k Views
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • R
    Ralms 0 @Derelict
    last edited by Mar 17, 2021, 9:40 PM

    @derelict To split my replies, here is the installation wizard phase:

    VM:

    The network devices were added to the VM with Firewall off:
    26da06ef-a5f5-4aac-ad1e-37d02c7e3e8a-image.png

    VM starting point:
    07dc97f8-2053-4a56-9916-55c37b53f636-image.png

    Installation Wizard base:


    07bcfbe5-4de4-4ca2-8ee9-8d53d9377faf-image.png

    Wizard starting point:
    14af1e27-a6b2-48f2-a98e-fe7570b72dca-image.png

    Changed timezone to Lisbon:
    599c78fd-ad5a-48cd-8f44-66b55b8e8b9a-image.png

    Setting storage:
    35e19180-4312-428c-afa0-a0c1330c23ef-image.png

    4ee83bef-4523-40af-8631-ab983d62abfd-image.png

    Installation Wizard Network:

    Starting point:
    c5f29d89-a1a3-488a-82a6-2efabd22b415-image.png

    Set hostname to tnsr:
    d4060168-2d77-4c9a-a699-85f49ded90f5-image.png

    Configure ens20:
    9ddad681-2cdf-456c-9aaa-65a9e14a0736-image.png

    Set IPv4 to dhcp and IPv6 to ignore:
    9a47ef83-1057-4bdb-a3c1-d9af6695f37b-image.png

    Tick option 7 and 8 for Connect automatically after reboot and Apply Configuration in installer
    d41d64df-63a6-4730-a793-bdbf2c3d559a-image.png

    Go back to wizard home and not touch the other 2 interfaces:
    d9c8c635-fefc-43ed-b729-424e0b2edecb-image.png

    Installation Wizard finish:

    Confirm the Software Selection:
    4b87a6c5-7fe5-475c-8e10-a89220d4bd91-image.png

    Processing:
    588b3ef2-4834-478d-b256-1557a2714277-image.png

    All set:
    89f88c79-2f2e-43a2-91e3-5ac79fb80b49-image.png

    Being installation:
    2dd2dbf9-4a90-4b69-84b4-955d2ba1672a-image.png

    1 Reply Last reply Reply Quote 0
    • R
      Ralms 0 @Derelict
      last edited by Mar 17, 2021, 10:06 PM

      @derelict

      Installation Complete:


      50e81cd8-65e8-4704-b8bd-879ac07e9565-image.png

      Automatic Reboot.
      First Login:
      abb4c459-b478-4602-8845-cbac27609e27-image.png

      Interfaces and Network Manager:
      e5d63fe1-74d9-418e-bc4d-a162615c36d3-image.png

      So it shows as "Not running", so I might have enabled it by accident when I set the NM_CONTROLLED.

      show interface returns nothing.
      f795753a-03c0-4b4a-8241-2dd338e1f429-image.png

      Set Interfaces Down as mention in the docs:
      a0154aa2-7664-4197-a159-0d4442fd9289-image.png

      Default config from ENS18:
      2aae3bcc-73e9-4a5d-961a-edcd31858813-image.png

      Set NM_CONTROLLED to no:
      f30f0848-b1a4-4af4-a8b7-b539f422b953-image.png

      Without Reboot, still nothing:
      e9fb211b-3862-472f-b562-6d27edb0ed46-image.png

      Rebooted the system.

      Interfaces still now showing up.
      53e6a786-b5e5-410a-9997-b7cb717463d4-image.png

      Set network name:
      4f6cb942-d8ba-4320-84fb-98b334620e9f-image.png

      So yeah, I have no idea what is going on, what I'm doing wrong.

      This is a Proxmox 6.3-6 running on an HP DL360p Gen8.

      L 1 Reply Last reply Mar 19, 2021, 10:57 PM Reply Quote 0
      • L
        lastactionhero @Ralms 0
        last edited by Mar 19, 2021, 10:57 PM

        @ralms-0
        @Derelict

        I am also struggling with this. This is my first time attempting to install, registered earlier this week. I am not using Proxmox, but KVM libvirt natively. I installed latest version from ISO, serial setup, with 8 virtio network bridge interfaces. I am not looking to pass anything through or use SR-IOV, as eventually I'd like this to migrate between my hosts. Upon completed installation, only my configured host interface is active. I tried both static and/or dhcp, this always works.

        tnsr# show version
        
        Version: tnsr-v21.03-2
        Build timestamp: Thu Mar  4 10:29:54 2021 CST
        

        I dropped to host shell, NetworkManager service is not running.

        systemctl start NetworkManager
        systemctl enable NetworkManager

        This get's NetworkManager going again. I am not sure why it wasn't running and enabled. I am then able to issue "nmcli device status" to get results of all my interfaces. I then apply "NM_CONTROLLED=no" to respective ifcfg-enp1s0, etc interfaces so they are unmanaged. Reboot for good measure.

        And thats where I'm at... It's still not working after reboot.

        tnsr(config)# dataplane dpdk dev 
          0000:01:00.0          Ethernet controller: Red Hat, Inc. Virtio network device (rev 01)                                                                                                                                                      
          0000:02:00.0          Ethernet controller: Red Hat, Inc. Virtio network device (rev 01)                                                                                                                                                      
          0000:03:00.0          Ethernet controller: Red Hat, Inc. Virtio network device (rev 01)                                                                                                                                                      
          0000:04:00.0          Ethernet controller: Red Hat, Inc. Virtio network device (rev 01)                                                                                                                                                      
          0000:05:00.0          Ethernet controller: Red Hat, Inc. Virtio network device (rev 01)                                                                                                                                                      
          0000:06:00.0          Ethernet controller: Red Hat, Inc. Virtio network device (rev 01)                                                                                                                                                      
          0000:07:00.0          Ethernet controller: Red Hat, Inc. Virtio network device (rev 01)                                                                                                                                                      
          0000:08:00.0          Ethernet controller: Red Hat, Inc. Virtio network device (rev 01)                                                                                                                                                      
          default      
        

        Trying to configure name's for interfaces.

        tnsr(config)# dataplane dpdk dev 0000:01:00.0 network name WAN1
        Changes to dataplane startup settings require a dataplane restart to take effect.
        tnsr(config)# dataplane dpdk dev 0000:02:00.0 network name WAN2
        Changes to dataplane startup settings require a dataplane restart to take effect.
        tnsr(config)# service dataplane restart
        

        Show interface results in nothing.

        I've read through release notes known issues and I am not sure if this is not a supported configuration or not and known. My KVM hosts, running Ubuntu 20.10, netplan interfaces are configured as bridges with VLAN's, on bonded 10Gbit interfaces.

        1 Reply Last reply Reply Quote 0
        • L
          lastactionhero
          last edited by Mar 19, 2021, 11:56 PM

          Some more troubleshooting

          [root@esg01 admin]# sudo dmesg | grep virtio_net
          [    4.078543] virtio_net virtio1 enp2s0: renamed from eth1
          [    4.084586] virtio_net virtio2 enp3s0: renamed from eth2
          [    4.091946] virtio_net virtio3 enp4s0: renamed from eth3
          [    4.101909] virtio_net virtio4 enp5s0: renamed from eth4
          [    4.136131] virtio_net virtio0 enp1s0: renamed from eth0
          [    4.146091] virtio_net virtio5 enp6s0: renamed from eth5
          [    4.171685] virtio_net virtio7 enp8s0: renamed from eth7
          [    4.203872] virtio_net virtio6 enp7s0: renamed from eth6
          
          [root@esg01 admin]# sudo tnsrctl status
          vpp.service: activating
          clixon-backend.service: activating
          clixon-restconf.service: activating
          tnsr-boot.service: active
          tnsr-dataplane-netns.service: active
          frr-dataplane.service: inactive
          strongswan-dataplane.service: inactive
          nginx-dataplane.service: inactive
          ntpd-dataplane.service: inactive
          unbound-dataplane.service: inactive
          sshd-dataplane.service: inactive
          snmp-subagent-dataplane.service: inactive
          snmpd-dataplane.service: inactive
          nginx.service: inactive
          ntpd.service: inactive
          snmp-subagent.service: inactive
          snmpd.service: inactive
          DHCPv4 server: inactive
          
          [root@esg01 admin]# sudo systemctl status vpp
          ● vpp.service - Vector Packet Processing Process
             Loaded: loaded (/usr/lib/systemd/system/vpp.service; enabled; vendor preset: enabled)
            Drop-In: /usr/lib/systemd/system/vpp.service.d
                     └─intentional-restart.conf, nm-wait-online.conf, on-failure.conf, requires-dataplane.conf
             Active: activating (auto-restart) (Result: exit-code) since Fri 2021-03-19 16:24:36 PDT; 4s ago
            Process: 2591 ExecStopPost=/bin/cp /etc/tnsr/tnsr-running.xml /etc/tnsr.xml (code=exited, status=0/SUCCESS)
            Process: 2590 ExecStopPost=/bin/echo TNSR startup mode switch : using running DB (code=exited, status=0/SUCCESS)
            Process: 2588 ExecStopPost=/bin/echo VPP stopped, modifying TNSR startup mode (code=exited, status=0/SUCCESS)
            Process: 2586 ExecStart=/usr/bin/vpp -c /etc/vpp/startup.conf (code=exited, status=1/FAILURE)
            Process: 2584 ExecStartPre=/sbin/modprobe uio_pci_generic (code=exited, status=0/SUCCESS)
            Process: 2582 ExecStartPre=/bin/rm -f /dev/shm/db /dev/shm/global_vm /dev/shm/vpe-api (code=exited, status=0/SUCCESS)
           Main PID: 2586 (code=exited, status=1/FAILURE)
              Tasks: 0 (limit: 49476)
             Memory: 0B
             CGroup: /system.slice/vpp.service
          [root@esg01 admin]# sudo systemctl status clixon-backend         
          ● clixon-backend.service - Clixon backend
             Loaded: loaded (/usr/lib/systemd/system/clixon-backend.service; enabled; vendor preset: enabled)
             Active: activating (start-post) since Fri 2021-03-19 16:24:21 PDT; 46s ago
            Process: 2404 ExecStartPost=/usr/bin/echo TNSR startup mode switch : using none (code=exited, status=0/SUCCESS)
            Process: 2403 ExecStartPost=/usr/bin/cp -f /etc/tnsr/tnsr-none.xml /etc/tnsr.xml (code=exited, status=0/SUCCESS)
            Process: 2402 ExecStartPost=/usr/bin/echo clixon_backend started successfully, modifying TNSR startup mode (code=exited, status=0/SUCCESS)
            Process: 2341 ExecStart=/usr/sbin/clixon_backend (code=exited, status=0/SUCCESS)
              Tasks: 1 (limit: 49476)
             Memory: 23.8M
             CGroup: /system.slice/clixon-backend.service
                     └─2401 /usr/sbin/clixon_backend
          
          Mar 19 16:24:21 esg01 clixon_backend[2341]: os_priv_change: changing uid from 0 to 0
          Mar 19 16:24:21 esg01 clixon_backend[2341]: Mar 19 16:24:21: os_priv_change: changing uid from 0 to 0
          Mar 19 16:24:21 esg01 clixon_backend[2341]: Startup successful, no backup needed
          Mar 19 16:24:21 esg01 clixon_backend[2341]: Mar 19 16:24:21: Startup successful, no backup needed
          Mar 19 16:24:21 esg01 clixon_backend[2401]: clixon_backend: 2401 Started
          Mar 19 16:24:21 esg01 systemd[1]: clixon-backend.service: Can't convert PID files /var/tnsr/tnsr.pidfile O_PATH file descriptor to proper file descriptor: Permission denied
          Mar 19 16:24:21 esg01 echo[2402]: clixon_backend started successfully, modifying TNSR startup mode
          Mar 19 16:24:21 esg01 echo[2404]: TNSR startup mode switch : using none
          Mar 19 16:24:21 esg01 systemd[1]: clixon-backend.service: Can't convert PID files /var/tnsr/tnsr.pidfile O_PATH file descriptor to proper file descriptor: Permission denied
          Mar 19 16:24:21 esg01 systemd[1]: clixon-backend.service: Can't convert PID files /var/tnsr/tnsr.pidfile O_PATH file descriptor to proper file descriptor: Permission denied
          [root@esg01 admin]# sudo systemctl status clixon-restconf
          ● clixon-restconf.service - Clixon restconf
             Loaded: loaded (/usr/lib/systemd/system/clixon-restconf.service; enabled; vendor preset: enabled)
             Active: activating (auto-restart) (Result: exit-code) since Fri 2021-03-19 16:25:19 PDT; 2s ago
            Process: 2711 ExecStart=/www-data/clixon_restconf (code=exited, status=203/EXEC)
           Main PID: 2711 (code=exited, status=203/EXEC)
          
          D 1 Reply Last reply Mar 20, 2021, 2:20 AM Reply Quote 0
          • D
            Derelict LAYER 8 Netgate @lastactionhero
            last edited by Mar 20, 2021, 2:20 AM

            @lastactionhero Does the host see the interfaces when running something like

            sudo ip link

            in the host namespace?

            If so, then you must get the host to relinquish the interfaces before you can add them to the dataplane.

            I do not know off-hand the particular recipe for doing so in your case. All I know is I have zero problems installing tnsr in proxmox-wrapped KVM virtual machines using virtio NICs. If I ever do find myself in that predicament I just add ONBOOT and NM_CONTROLLED set to no and reboot.

            tnsr-b1 tnsr# host shell ip link
            1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
                link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
            4: ens20: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
                link/ether 2a:d4:de:20:c8:db brd ff:ff:ff:ff:ff:ff
            
            tnsr-b1 tnsr(config)# dataplane dpdk dev 
              0000:00:12.0          Ethernet controller: Red Hat, Inc. Virtio network device                                                    
              0000:00:13.0          Ethernet controller: Red Hat, Inc. Virtio network device                                                    
              0000:00:14.0          Ethernet controller: Red Hat, Inc. Virtio network device                                                    
              0000:00:15.0          Ethernet controller: Red Hat, Inc. Virtio network device                                                    
              default              
            
            tnsr-b1 tnsr# show config run json
            snip
            
                  "dpdk": {
                    "dev": [
                      {
                        "id": "0000:00:12.0",
                        "name": "outside"
                      },
                      {
                        "id": "0000:00:13.0",
                        "name": "inside"
                      },
                      {
                        "id": "0000:00:15.0",
                        "name": "opt1"
                      }
                    ]
                  },
                                                                                            
            tnsr-b1 tnsr# show interface ip
            Interface: inside
                IPv4 MTU: 0 bytes
                IPv4 Route Table: ipv4-VRF:0
                IPv4 addresses:
                    172.29.101.1/29
            
            Interface: loop0
                IPv4 MTU: 0 bytes
                IPv4 Route Table: ipv4-VRF:0
            
            Interface: opt1
                IPv4 MTU: 0 bytes
                IPv4 Route Table: ipv4-VRF:0
                IPv4 addresses:
                    172.29.105.1/24
            
            Interface: outside
                IPv4 MTU: 0 bytes
                IPv4 Route Table: ipv4-VRF:0
                IPv4 addresses:
                    172.25.228.57/24
            
            

            I wish I could be more help right now but that's really all I have.

            Chattanooga, Tennessee, USA
            A comprehensive network diagram is worth 10,000 words and 15 conference calls.
            DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
            Do Not Chat For Help! NO_WAN_EGRESS(TM)

            1 Reply Last reply Reply Quote 0
            • L
              lastactionhero
              last edited by Mar 20, 2021, 5:31 AM

              Some more troubleshooting. This looks to be permissions related issue.

              @Derelict When you install, are you enabling root account with a password? Or are you creating a user account, making it a member of administrator (root)? I'm doing the later, making an admin user account, member of administrators (root). The root account remains disabled.

              I was able to get this working, but only for troubleshooting more of the issue, not resolving it. I think I would need support at this point to chime in, fix a bug here, which I'm not going to pay for at this time. I really want this to just work because I've heard good things regarding performance and I really want this. I'd like to switch from my current VyOS which just works.

              My steps above with NetworkManager work to sort out the interfaces making them unmanaged. As the journalctl -xe logs indicated, vpp.service is the issue, it's not starting. I can manually start this if I drop to host shell and execute vpp with the config.

              [admin@esg01 ~]$ sudo /usr/bin/vpp -c /etc/vpp/startup.conf
              [sudo] password for admin: 
              /usr/bin/vpp[7433]: perfmon: skipping source 'intel-uncore' - intel_uncore_init: no uncore units found
              /usr/bin/vpp[7433]: tls_init_ca_chain:609: Could not initialize TLS CA certificates
              /usr/bin/vpp[7433]: tls_mbedtls_init:644: failed to initialize TLS CA chain
              /usr/bin/vpp[7433]: tls_init_ca_chain:710: Could not initialize TLS CA certificates
              /usr/bin/vpp[7433]: tls_openssl_init:784: failed to initialize TLS CA chain
              

              Once this is running, I am then able to see my interfaces in tnsr CLI, dataplane dpdk dev. Everything jives up at this point as you mention in your replies as it should. No more errors in the CLI either.

              esg01 tnsr# show interface 
              Interface: Guest
                  Admin status: down
                  Link down, link-speed 10 Gbps, unknown duplex
                  Link MTU: 1500 bytes
                  MAC address: 52:54:00:7b:f7:69
                  IPv4 MTU: 0 bytes
                  IPv4 Route Table: ipv4-VRF:0
                  IPv6 MTU: 0 bytes
                  IPv6 Route Table: ipv6-VRF:0
                  VLAN tag rewrite: disable
                  Rx-queues
                      queue-id 0 : cpu-id 1
                  counters:
                    received: 0 bytes, 0 packets, 0 errors
                    transmitted: 0 bytes, 0 packets, 0 errors
                    protocols: 0 IPv4, 0 IPv6
                    0 drops, 0 punts, 0 rx miss, 0 rx no buffer
              
              Interface: Management
                  Admin status: down
                  Link down, link-speed 10 Gbps, unknown duplex
                  Link MTU: 1500 bytes
                  MAC address: 52:54:00:d4:64:23
                  IPv4 MTU: 0 bytes
                  IPv4 Route Table: ipv4-VRF:0
                  IPv6 MTU: 0 bytes
                  IPv6 Route Table: ipv6-VRF:0
                  VLAN tag rewrite: disable
                  Rx-queues
                      queue-id 0 : cpu-id 1
                  counters:
                    received: 0 bytes, 0 packets, 0 errors
                    transmitted: 0 bytes, 0 packets, 1 errors
                    protocols: 0 IPv4, 0 IPv6
                    0 drops, 0 punts, 0 rx miss, 0 rx no buffer
              
              Interface: WAN1
                  Admin status: down
                  Link down, link-speed 10 Gbps, unknown duplex
                  Link MTU: 1500 bytes
                  MAC address: 52:54:00:a5:5c:04
                  IPv4 MTU: 0 bytes
                  IPv4 Route Table: ipv4-VRF:0
                  IPv6 MTU: 0 bytes
                  IPv6 Route Table: ipv6-VRF:0
                  VLAN tag rewrite: disable
                  Rx-queues
                      queue-id 0 : cpu-id 1
                  counters:
                    received: 0 bytes, 0 packets, 0 errors
                    transmitted: 0 bytes, 0 packets, 0 errors
                    protocols: 0 IPv4, 0 IPv6
                    0 drops, 0 punts, 0 rx miss, 0 rx no buffer
              
              Interface: WAN2
                  Admin status: down
                  Link down, link-speed 10 Gbps, unknown duplex
                  Link MTU: 1500 bytes
                  MAC address: 52:54:00:f1:5a:97
                  IPv4 MTU: 0 bytes
                  IPv4 Route Table: ipv4-VRF:0
                  IPv6 MTU: 0 bytes
                  IPv6 Route Table: ipv6-VRF:0
                  VLAN tag rewrite: disable
                  Rx-queues
                      queue-id 0 : cpu-id 1
                  counters:
                    received: 0 bytes, 0 packets, 0 errors
                    transmitted: 0 bytes, 0 packets, 0 errors
                    protocols: 0 IPv4, 0 IPv6
                    0 drops, 0 punts, 0 rx miss, 0 rx no buffer
              
              Interface: WiFi
                  Admin status: down
                  Link down, link-speed 10 Gbps, unknown duplex
                  Link MTU: 1500 bytes
                  MAC address: 52:54:00:22:9e:9b
                  IPv4 MTU: 0 bytes
                  IPv4 Route Table: ipv4-VRF:0
                  IPv6 MTU: 0 bytes
                  IPv6 Route Table: ipv6-VRF:0
                  VLAN tag rewrite: disable
                  Rx-queues
                      queue-id 0 : cpu-id 1
                  counters:
                    received: 0 bytes, 0 packets, 0 errors
                    transmitted: 0 bytes, 0 packets, 0 errors
                    protocols: 0 IPv4, 0 IPv6
                    0 drops, 0 punts, 0 rx miss, 0 rx no buffer
              
              Interface: Workstation
                  Admin status: down
                  Link down, link-speed 10 Gbps, unknown duplex
                  Link MTU: 1500 bytes
                  MAC address: 52:54:00:45:31:92
                  IPv4 MTU: 0 bytes
                  IPv4 Route Table: ipv4-VRF:0
                  IPv6 MTU: 0 bytes
                  IPv6 Route Table: ipv6-VRF:0
                  VLAN tag rewrite: disable
                  Rx-queues
                      queue-id 0 : cpu-id 1
                  counters:
                    received: 0 bytes, 0 packets, 0 errors
                    transmitted: 0 bytes, 0 packets, 0 errors
                    protocols: 0 IPv4, 0 IPv6
                    0 drops, 0 punts, 0 rx miss, 0 rx no buffer
              
              esg01 tnsr# 
              

              I will reinstall again tomorrow trying with root account enabled. I don't know what else to do beyond this.

              D 1 Reply Last reply Mar 20, 2021, 8:31 PM Reply Quote 0
              • D
                Derelict LAYER 8 Netgate @lastactionhero
                last edited by Mar 20, 2021, 8:31 PM

                @lastactionhero I usually make an additional admin-level account but I never enable root. I generally log in using the tnsr user.

                Chattanooga, Tennessee, USA
                A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                Do Not Chat For Help! NO_WAN_EGRESS(TM)

                1 Reply Last reply Reply Quote 0
                • L
                  lastactionhero
                  last edited by Mar 21, 2021, 1:44 AM

                  Installing using virt-manager works. I have no issues performing a install and interfaces are present for use right away. No errors.

                  Installing via my kvm host, using virt-install seems to be where the issue is. Reviewing the domain XML's for any difference, I cannot find any difference. Very strange. If I find what's missing I'll update the post, but it works fine as a VM and virtio installing using virt-manager.

                  1 Reply Last reply Reply Quote 0
                  • R
                    Ralms 0
                    last edited by Mar 23, 2021, 9:15 PM

                    So, destiny decided that I should have received a support ticket with Netgate about this. (I was very surprised about it)

                    The support experience was very impressive and the engineer identified the issue really fast.

                    Proxmox uses QEMU, which integrates KVM.
                    It happens that the default CPU Type, "kvm64", doesn't have all the instruction extensions required, such as SSE 4.2, as mentioned here:
                    https://docs.netgate.com/tnsr/en/latest/platforms/kvm/#creating-a-vm

                    I've changed the VM to use CPU Type "Nehalem" and it worked out of the box, with the steps I've shared before.

                    Hope it helps others in the future :)

                    Thanks.

                    1 Reply Last reply Reply Quote 0
                    • L
                      lastactionhero
                      last edited by Mar 23, 2021, 10:14 PM

                      I too was able to resolve my issue. I apologize for hijacking this thread thinking it was similar underlying issue.

                      The difference between working and not working was when using virt-install, I need to use --cdrom for specifying the install ISO. Using --location ends up not working. While the installation completes, network interfaces do not. Virt-manager worked because it was using cdrom and not location.

                      Works:

                      sudo virt-install --cdrom tnsr.iso
                      

                      Does not work:

                      sudo virt-install --location tnsr.iso
                      
                      1 Reply Last reply Reply Quote 0
                      24 out of 24
                      • First post
                        24/24
                        Last post
                      Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
                        This community forum collects and processes your personal information.
                        consent.not_received