Comments by "" (@serge5046) on "How to install u0026 use QEMU+KVM and virt-manager" video.

  1.  @techofe-anopensourcebasedd5822  You can use the Windows PPD file for that printer which should be inside the Windows drivers. You need to install the package tofrodos on MX and then use the program fromdos to convert the DOS file to the UNIX format so that CUPS can use it
    2
  2.  @Doriandotslash  Not as easily as you think. For bridge networking, you often need bridge-utils and ebtables and you have to check in the host's terminal that the correct vibrN interfaces are there (replace N with 1 or 2 depending on the case)
    2
  3.  @Doriandotslash  Try to install Slackware or Gentoo in a VM and see if the network is doing fine (doing updates and installing packages in the VM). Now by bridge networking I meant between the host and the VM not between VM's. Your case is working because you chose the default networking for the two machines which is always 192.168.122.0/24 and your two VM's are in the same default network as you can see it from this article: https://wiki.libvirt.org/page/VirtualNetworking I am talking about a bridge networking between the host and the VM ! I didn't see it the first time but in your screenshot the machine is pinging to itself !!!
    2
  4.  @kabochaVA  For nftables with libvirtd: https://github.com/kopperi/libvirt-networking-nft-script For SELinux:https://www.systutorials.com/docs/linux/man/8-virsh_selinux/ https://libvirt.org/drvqemu.html#securityselinux Or you might try Cockpit as virt-manager is deprecated and might be removed in the future: https://ostechnix.com/manage-kvm-virtual-machines-using-cockpit-web-console/
    1
  5.  @techofe-anopensourcebasedd5822  Could you give me the exact series model of your MFP Toshiba printer?
    1
  6. On which distribution? Try to install ebtables, restart libvirtd daemon or install libvirt-daemon-system on Debian. Or check the permissions: https://www.dark-hamster.com/server/virtualization/failed-connect-socket-varrunlibvirtlibvirt-sockno-file-directory/
    1
  7.  @Doriandotslash  I see why: you probably have a version of qemu >= 5 and of virt-manager >= 2.2
    1