QEMU VM has no IPCoreboot + QEMU Tutorial Request (Google has failed)Confusion about interfaces, iptables, connections, local connectionHow do I fix Debian that refuses to connect to the internet in VirtualBox?Making /dev/net/tun available to qemu?Qemu curses interface dimensionsNetworking with Graylog in Qemu?Script to create macvlan bridge on the host doesn't work unless it's run twiceConnect to running qemu instance with qemu monitorStatic IPv4 in QEMURunning QEMU inside VM

Are cabin dividers used to "hide" the flex of the airplane?

New order #4: World

Symmetry in quantum mechanics

Extreme, but not acceptable situation and I can't start the work tomorrow morning

LWC and complex parameters

Why do we use polarized capacitors?

Pristine Bit Checking

How would photo IDs work for shapeshifters?

What does 'script /dev/null' do?

Does a dangling wire really electrocute me if I'm standing in water?

What is it called when one voice type sings a 'solo'?

What are the advantages and disadvantages of running one shots compared to campaigns?

Does bootstrapped regression allow for inference?

A poker game description that does not feel gimmicky

Is there a name of the flying bionic bird?

Why is the design of haulage companies so “special”?

Patience, young "Padovan"

Can a planet have a different gravitational pull depending on its location in orbit around its sun?

Are objects structures and/or vice versa?

Calculate Levenshtein distance between two strings in Python

Domain expired, GoDaddy holds it and is asking more money

Is every set a filtered colimit of finite sets?

How can I fix this gap between bookcases I made?

Lied on resume at previous job



QEMU VM has no IP


Coreboot + QEMU Tutorial Request (Google has failed)Confusion about interfaces, iptables, connections, local connectionHow do I fix Debian that refuses to connect to the internet in VirtualBox?Making /dev/net/tun available to qemu?Qemu curses interface dimensionsNetworking with Graylog in Qemu?Script to create macvlan bridge on the host doesn't work unless it's run twiceConnect to running qemu instance with qemu monitorStatic IPv4 in QEMURunning QEMU inside VM






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








0















I tried to run a VM on QEMU, but the VM is up without an IP address associated with eth0. I configured the bridge and tap interface on the host, and I can see that:



brctl show bro
bridge name bridge id STP enabled interfaces
bro 8000.bedc8d16e7d8 no eno1
tap0


The interfaces look good:



ip addr show bro
3: bro: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether be:dc:8d:16:e7:d8 brd ff:ff:ff:ff:ff:ff
inet 192.168.100.112/24 brd 192.168.100.255 scope global dynamic bro
valid_lft 540129sec preferred_lft 540129sec
inet6 fe80::bcdc:8dff:fe16:e7d8/64 scope link
valid_lft forever preferred_lft forever

ip addr show eno1
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master bro state UP group default qlen 1000
link/ether 98:90:96:9d:d9:83 brd ff:ff:ff:ff:ff:ff

ip addr show tap0
8: tap0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel master bro state DOWN group default qlen 1000
link/ether d2:74:5b:04:81:f8 brd ff:ff:ff:ff:ff:ff
inet 192.168.100.222/24 brd 192.168.100.255 scope global tap0
valid_lft forever preferred_lft forever


Here is the command I use to run the VM:



sudo qemu-system-aarch64 -m 1024 -cpu cortex-a57 -M virt -nographic -pflash flash0.img -pflash flash1.img -drive if=none,file=CentOS-7-aarch64-Minimal-1810.iso,id=hd0 -device virtio-blk-device,drive=hd0 -netdev type=tap,id=net0 -device virtio-net-device,netdev=net0,mac=bc:dc:8d:16:e7:d8, -hda centos7-arm.img


At the guest there is no IP, even though DHCP is no:



[root@localhost ~]# ip link show eth0
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
link/ether bc:dc:8d:16:e7:d8 brd ff:ff:ff:ff:ff:ff


After I tried to config from CentOS nmtui, service network restart failed. Found in log:



localhost.localdomain network[4058]: Bringing up interface eth0: Error: Connection activation failed: IP configuration could not be reserved (no available address, timeout, etc.)


Do you have any idea what could be going wrong?










share|improve this question






























    0















    I tried to run a VM on QEMU, but the VM is up without an IP address associated with eth0. I configured the bridge and tap interface on the host, and I can see that:



    brctl show bro
    bridge name bridge id STP enabled interfaces
    bro 8000.bedc8d16e7d8 no eno1
    tap0


    The interfaces look good:



    ip addr show bro
    3: bro: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether be:dc:8d:16:e7:d8 brd ff:ff:ff:ff:ff:ff
    inet 192.168.100.112/24 brd 192.168.100.255 scope global dynamic bro
    valid_lft 540129sec preferred_lft 540129sec
    inet6 fe80::bcdc:8dff:fe16:e7d8/64 scope link
    valid_lft forever preferred_lft forever

    ip addr show eno1
    2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master bro state UP group default qlen 1000
    link/ether 98:90:96:9d:d9:83 brd ff:ff:ff:ff:ff:ff

    ip addr show tap0
    8: tap0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel master bro state DOWN group default qlen 1000
    link/ether d2:74:5b:04:81:f8 brd ff:ff:ff:ff:ff:ff
    inet 192.168.100.222/24 brd 192.168.100.255 scope global tap0
    valid_lft forever preferred_lft forever


    Here is the command I use to run the VM:



    sudo qemu-system-aarch64 -m 1024 -cpu cortex-a57 -M virt -nographic -pflash flash0.img -pflash flash1.img -drive if=none,file=CentOS-7-aarch64-Minimal-1810.iso,id=hd0 -device virtio-blk-device,drive=hd0 -netdev type=tap,id=net0 -device virtio-net-device,netdev=net0,mac=bc:dc:8d:16:e7:d8, -hda centos7-arm.img


    At the guest there is no IP, even though DHCP is no:



    [root@localhost ~]# ip link show eth0
    2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
    link/ether bc:dc:8d:16:e7:d8 brd ff:ff:ff:ff:ff:ff


    After I tried to config from CentOS nmtui, service network restart failed. Found in log:



    localhost.localdomain network[4058]: Bringing up interface eth0: Error: Connection activation failed: IP configuration could not be reserved (no available address, timeout, etc.)


    Do you have any idea what could be going wrong?










    share|improve this question


























      0












      0








      0








      I tried to run a VM on QEMU, but the VM is up without an IP address associated with eth0. I configured the bridge and tap interface on the host, and I can see that:



      brctl show bro
      bridge name bridge id STP enabled interfaces
      bro 8000.bedc8d16e7d8 no eno1
      tap0


      The interfaces look good:



      ip addr show bro
      3: bro: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
      link/ether be:dc:8d:16:e7:d8 brd ff:ff:ff:ff:ff:ff
      inet 192.168.100.112/24 brd 192.168.100.255 scope global dynamic bro
      valid_lft 540129sec preferred_lft 540129sec
      inet6 fe80::bcdc:8dff:fe16:e7d8/64 scope link
      valid_lft forever preferred_lft forever

      ip addr show eno1
      2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master bro state UP group default qlen 1000
      link/ether 98:90:96:9d:d9:83 brd ff:ff:ff:ff:ff:ff

      ip addr show tap0
      8: tap0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel master bro state DOWN group default qlen 1000
      link/ether d2:74:5b:04:81:f8 brd ff:ff:ff:ff:ff:ff
      inet 192.168.100.222/24 brd 192.168.100.255 scope global tap0
      valid_lft forever preferred_lft forever


      Here is the command I use to run the VM:



      sudo qemu-system-aarch64 -m 1024 -cpu cortex-a57 -M virt -nographic -pflash flash0.img -pflash flash1.img -drive if=none,file=CentOS-7-aarch64-Minimal-1810.iso,id=hd0 -device virtio-blk-device,drive=hd0 -netdev type=tap,id=net0 -device virtio-net-device,netdev=net0,mac=bc:dc:8d:16:e7:d8, -hda centos7-arm.img


      At the guest there is no IP, even though DHCP is no:



      [root@localhost ~]# ip link show eth0
      2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
      link/ether bc:dc:8d:16:e7:d8 brd ff:ff:ff:ff:ff:ff


      After I tried to config from CentOS nmtui, service network restart failed. Found in log:



      localhost.localdomain network[4058]: Bringing up interface eth0: Error: Connection activation failed: IP configuration could not be reserved (no available address, timeout, etc.)


      Do you have any idea what could be going wrong?










      share|improve this question
















      I tried to run a VM on QEMU, but the VM is up without an IP address associated with eth0. I configured the bridge and tap interface on the host, and I can see that:



      brctl show bro
      bridge name bridge id STP enabled interfaces
      bro 8000.bedc8d16e7d8 no eno1
      tap0


      The interfaces look good:



      ip addr show bro
      3: bro: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
      link/ether be:dc:8d:16:e7:d8 brd ff:ff:ff:ff:ff:ff
      inet 192.168.100.112/24 brd 192.168.100.255 scope global dynamic bro
      valid_lft 540129sec preferred_lft 540129sec
      inet6 fe80::bcdc:8dff:fe16:e7d8/64 scope link
      valid_lft forever preferred_lft forever

      ip addr show eno1
      2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master bro state UP group default qlen 1000
      link/ether 98:90:96:9d:d9:83 brd ff:ff:ff:ff:ff:ff

      ip addr show tap0
      8: tap0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel master bro state DOWN group default qlen 1000
      link/ether d2:74:5b:04:81:f8 brd ff:ff:ff:ff:ff:ff
      inet 192.168.100.222/24 brd 192.168.100.255 scope global tap0
      valid_lft forever preferred_lft forever


      Here is the command I use to run the VM:



      sudo qemu-system-aarch64 -m 1024 -cpu cortex-a57 -M virt -nographic -pflash flash0.img -pflash flash1.img -drive if=none,file=CentOS-7-aarch64-Minimal-1810.iso,id=hd0 -device virtio-blk-device,drive=hd0 -netdev type=tap,id=net0 -device virtio-net-device,netdev=net0,mac=bc:dc:8d:16:e7:d8, -hda centos7-arm.img


      At the guest there is no IP, even though DHCP is no:



      [root@localhost ~]# ip link show eth0
      2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
      link/ether bc:dc:8d:16:e7:d8 brd ff:ff:ff:ff:ff:ff


      After I tried to config from CentOS nmtui, service network restart failed. Found in log:



      localhost.localdomain network[4058]: Bringing up interface eth0: Error: Connection activation failed: IP configuration could not be reserved (no available address, timeout, etc.)


      Do you have any idea what could be going wrong?







      network-interface qemu






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Mar 28 at 14:47









      fra-san

      2,0271620




      2,0271620










      asked Mar 28 at 13:10









      RD7RD7

      1




      1




















          1 Answer
          1






          active

          oldest

          votes


















          0














          It's been a while since I ran kvm guests directly from the command line (I prefer libvirt, or more recently Proxmox).



          However, looking at the interface definitions at the host, and comparing it to my working configuration, the most obvious difference is that your tap0 interface has IP address 192.168.100.222/24 whereas mine has no IP address. (The guest defines an IP address, obtained from DHCP. The host interface should not have one.)



          # brctl show br0
          bridge name bridge id STP enabled interfaces
          br0 8000.009c029758d6 no eth0
          vnet5

          # ip addr show vnet5
          12: vnet5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master br0 state UNKNOWN group default qlen 1000
          link/ether fe:54:00:3c:75:33 brd ff:ff:ff:ff:ff:ff
          inet6 fe80::fc54:ff:fe3c:7533/64 scope link
          valid_lft forever preferred_lft forever


          # ssh vmguest ip addr show eth0
          2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
          link/ether 52:54:00:3c:75:33 brd ff:ff:ff:ff:ff:ff
          inet 192.168.1.15/24 brd 192.168.1.255 scope global eth0
          valid_lft forever preferred_lft forever
          inet6 fe80::5054:ff:fe3c:7533/64 scope link
          valid_lft forever preferred_lft forever


          Did you set that IP address on tap0 yourself, or was it a side-effect of your kvm command?






          share|improve this answer

























            Your Answer








            StackExchange.ready(function()
            var channelOptions =
            tags: "".split(" "),
            id: "106"
            ;
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function()
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled)
            StackExchange.using("snippets", function()
            createEditor();
            );

            else
            createEditor();

            );

            function createEditor()
            StackExchange.prepareEditor(
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: false,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            imageUploader:
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            ,
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            );



            );













            draft saved

            draft discarded


















            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f509216%2fqemu-vm-has-no-ip%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            It's been a while since I ran kvm guests directly from the command line (I prefer libvirt, or more recently Proxmox).



            However, looking at the interface definitions at the host, and comparing it to my working configuration, the most obvious difference is that your tap0 interface has IP address 192.168.100.222/24 whereas mine has no IP address. (The guest defines an IP address, obtained from DHCP. The host interface should not have one.)



            # brctl show br0
            bridge name bridge id STP enabled interfaces
            br0 8000.009c029758d6 no eth0
            vnet5

            # ip addr show vnet5
            12: vnet5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master br0 state UNKNOWN group default qlen 1000
            link/ether fe:54:00:3c:75:33 brd ff:ff:ff:ff:ff:ff
            inet6 fe80::fc54:ff:fe3c:7533/64 scope link
            valid_lft forever preferred_lft forever


            # ssh vmguest ip addr show eth0
            2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
            link/ether 52:54:00:3c:75:33 brd ff:ff:ff:ff:ff:ff
            inet 192.168.1.15/24 brd 192.168.1.255 scope global eth0
            valid_lft forever preferred_lft forever
            inet6 fe80::5054:ff:fe3c:7533/64 scope link
            valid_lft forever preferred_lft forever


            Did you set that IP address on tap0 yourself, or was it a side-effect of your kvm command?






            share|improve this answer





























              0














              It's been a while since I ran kvm guests directly from the command line (I prefer libvirt, or more recently Proxmox).



              However, looking at the interface definitions at the host, and comparing it to my working configuration, the most obvious difference is that your tap0 interface has IP address 192.168.100.222/24 whereas mine has no IP address. (The guest defines an IP address, obtained from DHCP. The host interface should not have one.)



              # brctl show br0
              bridge name bridge id STP enabled interfaces
              br0 8000.009c029758d6 no eth0
              vnet5

              # ip addr show vnet5
              12: vnet5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master br0 state UNKNOWN group default qlen 1000
              link/ether fe:54:00:3c:75:33 brd ff:ff:ff:ff:ff:ff
              inet6 fe80::fc54:ff:fe3c:7533/64 scope link
              valid_lft forever preferred_lft forever


              # ssh vmguest ip addr show eth0
              2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
              link/ether 52:54:00:3c:75:33 brd ff:ff:ff:ff:ff:ff
              inet 192.168.1.15/24 brd 192.168.1.255 scope global eth0
              valid_lft forever preferred_lft forever
              inet6 fe80::5054:ff:fe3c:7533/64 scope link
              valid_lft forever preferred_lft forever


              Did you set that IP address on tap0 yourself, or was it a side-effect of your kvm command?






              share|improve this answer



























                0












                0








                0







                It's been a while since I ran kvm guests directly from the command line (I prefer libvirt, or more recently Proxmox).



                However, looking at the interface definitions at the host, and comparing it to my working configuration, the most obvious difference is that your tap0 interface has IP address 192.168.100.222/24 whereas mine has no IP address. (The guest defines an IP address, obtained from DHCP. The host interface should not have one.)



                # brctl show br0
                bridge name bridge id STP enabled interfaces
                br0 8000.009c029758d6 no eth0
                vnet5

                # ip addr show vnet5
                12: vnet5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master br0 state UNKNOWN group default qlen 1000
                link/ether fe:54:00:3c:75:33 brd ff:ff:ff:ff:ff:ff
                inet6 fe80::fc54:ff:fe3c:7533/64 scope link
                valid_lft forever preferred_lft forever


                # ssh vmguest ip addr show eth0
                2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
                link/ether 52:54:00:3c:75:33 brd ff:ff:ff:ff:ff:ff
                inet 192.168.1.15/24 brd 192.168.1.255 scope global eth0
                valid_lft forever preferred_lft forever
                inet6 fe80::5054:ff:fe3c:7533/64 scope link
                valid_lft forever preferred_lft forever


                Did you set that IP address on tap0 yourself, or was it a side-effect of your kvm command?






                share|improve this answer















                It's been a while since I ran kvm guests directly from the command line (I prefer libvirt, or more recently Proxmox).



                However, looking at the interface definitions at the host, and comparing it to my working configuration, the most obvious difference is that your tap0 interface has IP address 192.168.100.222/24 whereas mine has no IP address. (The guest defines an IP address, obtained from DHCP. The host interface should not have one.)



                # brctl show br0
                bridge name bridge id STP enabled interfaces
                br0 8000.009c029758d6 no eth0
                vnet5

                # ip addr show vnet5
                12: vnet5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master br0 state UNKNOWN group default qlen 1000
                link/ether fe:54:00:3c:75:33 brd ff:ff:ff:ff:ff:ff
                inet6 fe80::fc54:ff:fe3c:7533/64 scope link
                valid_lft forever preferred_lft forever


                # ssh vmguest ip addr show eth0
                2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
                link/ether 52:54:00:3c:75:33 brd ff:ff:ff:ff:ff:ff
                inet 192.168.1.15/24 brd 192.168.1.255 scope global eth0
                valid_lft forever preferred_lft forever
                inet6 fe80::5054:ff:fe3c:7533/64 scope link
                valid_lft forever preferred_lft forever


                Did you set that IP address on tap0 yourself, or was it a side-effect of your kvm command?







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Mar 28 at 15:48

























                answered Mar 28 at 13:28









                roaimaroaima

                46k758124




                46k758124



























                    draft saved

                    draft discarded
















































                    Thanks for contributing an answer to Unix & Linux Stack Exchange!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid


                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.

                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f509216%2fqemu-vm-has-no-ip%23new-answer', 'question_page');

                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    -network-interface, qemu

                    Popular posts from this blog

                    Frič See also Navigation menuinternal link

                    Identify plant with long narrow paired leaves and reddish stems Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) Announcing the arrival of Valued Associate #679: Cesar Manara Unicorn Meta Zoo #1: Why another podcast?What is this plant with long sharp leaves? Is it a weed?What is this 3ft high, stalky plant, with mid sized narrow leaves?What is this young shrub with opposite ovate, crenate leaves and reddish stems?What is this plant with large broad serrated leaves?Identify this upright branching weed with long leaves and reddish stemsPlease help me identify this bulbous plant with long, broad leaves and white flowersWhat is this small annual with narrow gray/green leaves and rust colored daisy-type flowers?What is this chilli plant?Does anyone know what type of chilli plant this is?Help identify this plant

                    fontconfig warning: “/etc/fonts/fonts.conf”, line 100: unknown “element blank” The 2019 Stack Overflow Developer Survey Results Are In“tar: unrecognized option --warning” during 'apt-get install'How to fix Fontconfig errorHow do I figure out which font file is chosen for a system generic font alias?Why are some apt-get-installed fonts being ignored by fc-list, xfontsel, etc?Reload settings in /etc/fonts/conf.dTaking 30 seconds longer to boot after upgrade from jessie to stretchHow to match multiple font names with a single <match> element?Adding a custom font to fontconfigRemoving fonts from fontconfig <match> resultsBroken fonts after upgrading Firefox ESR to latest Firefox