I am trying to create some VM using the virt-manager and no matter what I do I am getting this error: Unable to complete install: 'internal error: guest failed to start: Failure in libvirt_lxc startup: Failed to create /var/lib/libvirt/images/vol.qcow2/.oldroot: Not a directory ' Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 65, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/createvm.py", line 2001, in _do_async_install installer.start_install(guest, meter=meter) File "/usr/share/virt-manager/virtinst/install/installer.py", line 701, in start_install domain = self._create_guest( File "/usr/share/virt-manager/virtinst/install/installer.py", line 649, in _create_guest domain = self.conn.createXML(install_xml or final_xml, 0) File "/usr/lib/python3.9/site-packages/libvirt.py", line 4035, in createXML if ret is None:raise libvirtError('virDomainCreateXML() failed', conn=self) libvirt.libvirtError: internal error: guest failed to start: Failure in libvirt_lxc startup: Failed to create /var/lib/libvirt/images/vol.qcow2/.oldroot: Not a directory I have tried to set in /etc/libvirt/qemu.conf the user and group to match my user and group, installed libvirt-glusterfs and it doesn’t work. I am using: libvirtd (libvirt) 7.0.0 and virt-manager v.3.2.0. For the record, I am running Manjaro Linux i3wm and my kernel is 5.11

I use libvirt-manager to manager my VMs. I create a new VM, and a default virtual network, which uses NAT. **virsh net-edit default** gives me: default ec2b5979-dd0c-43db-ab16-99f2e48ef0dd I have configured my Linux guest to use this network, and the device is set to **rtl8139**. After I started the VM, it can see the device, but it cannot get network address. **brctl show** gives me: bridge name bridge id STP enabled interfaces virbr0 8000.5254000eb14f yes virbr0-nic **ip link show** gives me: 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: wlan0: mtu 1500 qdisc pfifo_fast state UP mode DORMANT group default qlen 1000 link/ether c8:ff:28:78:44:01 brd ff:ff:ff:ff:ff:ff 3: virbr0: mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000 link/ether 52:54:00:0e:b1:4f brd ff:ff:ff:ff:ff:ff 4: virbr0-nic: mtu 1500 qdisc pfifo_fast master virbr0 state DOWN mode DEFAULT group default qlen 1000 link/ether 52:54:00:0e:b1:4f brd ff:ff:ff:ff:ff:ff One odd thing I found is that in "Connection Details"/"Network Interfaces" page, the virbr0 is shown as **inactive**, and I cannot activate it. Trying to activate it gives me: > libvirtError: this function is not supported by the connection driver: virInterfaceCreate

Does anyone know how to get full screen mode working using QEMU on MacOS (Ventura or Monterey)? I tried entering full screen on my 5120 x 2880 resolution display, however Gnome Display Manager doesn't advertise a setting larger then 1620x... I'm wondering if this is something that needs to be set manually in X-Windows.

I am using MX Linux and I have a problem enabling 3d acceleration in virt-manager. I enabled 3d acceleration by checking the OpenGL box in the Display Spice section and then selecting Virtio in the Video section, but after that, if I try to start the virtual machine, I get this error:

Error starting domain: internal error: process exited while connecting to monitor
    
Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 72, in cb_wrapper
    callback(asyncjob, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 108, in tmpcb
    callback(*args, **kwargs)
  File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", line 57, in newfn
    ret = fn(self, *args, **kwargs)
          ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/share/virt-manager/virtManager/object/domain.py", line 1402, in startup
    self._backend.create()
  File "/usr/lib/python3/dist-packages/libvirt.py", line 1373, in create
    raise libvirtError('virDomainCreate() failed')
libvirt.libvirtError: internal error: process exited while connecting to monitor

I found that if I change user and group from libvirt-qemu to root in /etc/libvirt/qemu.conf, I don't get this error when starting virtual machine, but I see only a black screen when the machine starts.

I'm trying to automate installation of a debian machine with a preseed configuration file and despite a few hiccups here and there it seems to work. I am confused though why adding --inject-initrd makes the installer throw these errors:

conf
mount: mounting /dev/vda on /media failed: Invalid argument
umount: can't unmount /media: Invalid argument
mount: mounting /dev/fd0 on /media failed: No such file or directory
umount: can't unmount /media: Invalid argument

Installation then continues fine, but I can't understand why these errors come up. They don't show up when there is no --inject-initrd option any ideas would be appreciated, I've tried adding --debug option, but it didn't reveal anything full command:

virt-install --name  --vcpus=8 --memory=20000 --disk size=400 --network network= --location=/tmp/debian-12.11.0-amd64-netinst.iso --os-variant=debian11 --graphics none --initrd-inject ./preseed.cfg --extra-args "console=ttyS0" --debug

I was using Ubuntu until I recently changed to Arch (Manjaro). However, when re-installing Virt-Manager again, I wanted to start the old virtual machines. The configuration hasn't changed but I encounter errors: The machine can't get stated any more and I receive the following error message: Error launching details: Host does not support domain type kvm with machine 'pc-i440fx-focal' for virtualization type 'hvm' with architecture 'x86_64' Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/vmwindow.py", line 40, in get_instance cls._instances[key] = vmmVMWindow(vm) File "/usr/share/virt-manager/virtManager/vmwindow.py", line 83, in __init__ self._details = vmmDetails(self.vm, self.builder, self.topwin, File "/usr/share/virt-manager/virtManager/details/details.py", line 389, in __init__ self._init_details() File "/usr/share/virt-manager/virtManager/details/details.py", line 807, in _init_details vmmAddHardware.build_video_combo(self.vm, video_dev) File "/usr/share/virt-manager/virtManager/addhardware.py", line 816, in build_video_combo default = DeviceVideo.default_model(vm.xmlobj) File "/usr/share/virt-manager/virtinst/devices/video.py", line 47, in default_model if (guest.lookup_domcaps().supports_video_virtio() and File "/usr/share/virt-manager/virtinst/guest.py", line 656, in lookup_domcaps if not self._domcaps or not _compare(self._domcaps): File "/usr/share/virt-manager/virtinst/guest.py", line 646, in _compare if self.os.machine and not _compare_machine(domcaps): File "/usr/share/virt-manager/virtinst/guest.py", line 633, in _compare_machine capsinfo = self.lookup_capsinfo() File "/usr/share/virt-manager/virtinst/guest.py", line 674, in lookup_capsinfo self._capsinfo = self.conn.caps.guest_lookup( File "/usr/share/virt-manager/virtinst/capabilities.py", line 319, in guest_lookup raise ValueError(msg) ValueError: Host does not support domain type kvm with machine 'pc-i440fx-focal' for virtualization type 'hvm' with architecture 'x86_64' I did not make any changes to the BIOS settings or anything. So virtualization in general should still work fine. Any ideas?

I've just launched "virt-manager" on my Ubuntu 21.04 and with my big surprise I've seen the error "**kvm is not available. It could means that the kvm package is not installed and so on**" ; this is not true. I've installed kvm and it is working great,as u can see the image below : give a look at what the terminal is telling : "**/dev/kvm exists ; kvm acceleration can be used**". What Am I supposed to believe ? What's missing ? # apt install qemu-kvm libvirt-clients libvirt-daemon-system Reading package lists... Done Building dependency tree... Done Reading state information... Done Note, selecting 'qemu-system-x86' instead of 'qemu-kvm' qemu-system-x86 is already the newest version (1:5.2+dfsg-9ubuntu3.1). libvirt-clients is already the newest version (7.0.0-2ubuntu2). libvirt-daemon-system is already the newest version (7.0.0-2ubuntu2). 0 upgraded, 0 newly installed, 0 to remove and 11 not upgraded. # virt-host-validate QEMU: Checking for hardware virtualization : PASS QEMU: Checking if device /dev/kvm exists : PASS QEMU: Checking if device /dev/kvm is accessible : PASS QEMU: Checking if device /dev/vhost-net exists : PASS QEMU: Checking if device /dev/net/tun exists : PASS QEMU: Checking for cgroup 'cpu' controller support : PASS QEMU: Checking for cgroup 'cpuacct' controller support : PASS QEMU: Checking for cgroup 'cpuset' controller support : PASS QEMU: Checking for cgroup 'memory' controller support : PASS QEMU: Checking for cgroup 'devices' controller support : PASS QEMU: Checking for cgroup 'blkio' controller support : PASS QEMU: Checking for device assignment IOMMU support : PASS QEMU: Checking if IOMMU is enabled by kernel : PASS QEMU: Checking for secure guest support : WARN (Unknown if this platform has Secure Guest support) LXC: Checking for Linux >= 2.6.26 : PASS LXC: Checking for namespace ipc : PASS LXC: Checking for namespace mnt : PASS LXC: Checking for namespace pid : PASS LXC: Checking for namespace uts : PASS LXC: Checking for namespace net : PASS LXC: Checking for namespace user : PASS LXC: Checking for cgroup 'cpu' controller support : PASS LXC: Checking for cgroup 'cpuacct' controller support : PASS LXC: Checking for cgroup 'cpuset' controller support : PASS LXC: Checking for cgroup 'memory' controller support : PASS LXC: Checking for cgroup 'devices' controller support : PASS LXC: Checking for cgroup 'freezer' controller support : PASS LXC: Checking for cgroup 'blkio' controller support : PASS LXC: Checking if device /sys/fs/fuse/connections exists : PASS Again : ● libvirtd.service - Virtualization daemon Loaded: loaded (/lib/systemd/system/libvirtd.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2021-07-28 13:18:31 CEST; 41min ago TriggeredBy: ● libvirtd-admin.socket ● libvirtd-ro.socket ● libvirtd.socket Docs: man:libvirtd(8) https://libvirt.org Main PID: 2091 (libvirtd) Tasks: 21 (limit: 32768) Memory: 49.3M CGroup: /system.slice/libvirtd.service ├─2091 /usr/sbin/libvirtd ├─2405 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper └─2406 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper Jul 28 12:45:30 Z390-AORUS-PRO libvirtd: internal error: Failed to start QEMU binary /usr/local/bin/qemu-system-x86_64 for probing: libvirt: error : cannot execute binary /usr/local/bin/qemu-system-x86_64: Permission denied Jul 28 12:45:30 Z390-AORUS-PRO libvirtd: Failed to probe capabilities for /usr/local/bin/qemu-system-x86_64: internal error: Failed to start QEMU binary /usr/local/bin/qemu-system-x86_64 for probing: libvirt: error : cannot execute binary /usr/local/bin/qemu-system-x86_64: Permission denied Jul 28 13:58:54 Z390-AORUS-PRO libvirtd: internal error: libxenlight state driver is not active Jul 28 13:58:54 Z390-AORUS-PRO libvirtd: End of file while reading data: Input/output error Jul 28 13:58:54 Z390-AORUS-PRO libvirtd: invalid argument: could not find capabilities for arch=x86_64 domaintype=qemu Jul 28 13:58:54 Z390-AORUS-PRO libvirtd: internal error: Cannot find suitable emulator for x86_64 Jul 28 13:58:54 Z390-AORUS-PRO libvirtd: internal error: Failed to start QEMU binary /usr/local/bin/qemu-system-x86_64 for probing: libvirt: error : cannot execute binary /usr/local/bin/qemu-system-x86_64: Permission denied Jul 28 13:58:54 Z390-AORUS-PRO libvirtd: Failed to probe capabilities for /usr/local/bin/qemu-system-x86_64: internal error: Failed to start QEMU binary /usr/local/bin/qemu-system-x86_64 for probing: libvirt: error : cannot execute binary /usr/local/bin/qemu-system-x86_64: Permission denied Jul 28 13:59:06 Z390-AORUS-PRO libvirtd: internal error: Failed to start QEMU binary /usr/local/bin/qemu-system-x86_64 for probing: libvirt: error : cannot execute binary /usr/local/bin/qemu-system-x86_64: Permission denied Jul 28 13:59:06 Z390-AORUS-PRO libvirtd: Failed to probe capabilities for /usr/local/bin/qemu-system-x86_64: internal error: Failed to start QEMU binary /usr/local/bin/qemu-system-x86_64 for probing: libvirt: error : cannot execute binary /usr/local/bin/qemu-system-x86_64: Permission denied

I've just got brand new Lenovo P1 gen7 with 16" with decent 3840x2400 resolution. Fedora 42 handles it pretty well: it let me set up scaling to whatever suits me, and that's all. However KVM guest does not seem to read the screen size properly. Vm's icons and texts are extremely tiny. It's just annoyng to set it up internally for every VM I'm runnig and change it every time I start it on other display. Is it possible to make qemu/KVM/libvirt somehow report the accual size of the window/screen in DPI or mm, so VM could decide if it should run on 1:1 or in scaling mode in more-less automatic manner?

I am experiencing a consistent issue with Linux VMs accessed via virt-manager. These VMs, running various versions of Fedora Linux with the Mate desktop environment, crash when the QXL video driver is used and the system is under heavy load for more than an hour (e.g., during make && make install operations). Symptoms --- All the following symptoms must be present; otherwise, it might be a different issue: * The desktop session abruptly ends, causing all running processes to terminate, and the login screen is displayed again. * The kernel log (dmesg) shows the following errors at the end:

qxl 0000:00:01.0: object_init failed for (266240, 0x00000001)
[drm:qxl_gem_object_create [qxl]] *ERROR* Failed to allocate GEM object (262164, 1, 4096, -12)
[drm:qxl_alloc_ioctl [qxl]] *ERROR* qxl_alloc_ioctl: failed to create gem ret=-12

Workaround --- Switching the VM’s video driver from QXL to Virtio prevents the crashes. However, this change introduces new issues: * Automatic screen resolution adjustment to the window size no longer works. * Display performance significantly degrades, especially when scrolling through a full terminal window, where you can visibly see each line being redrawn. Additional Information --- I have read similar bug reports, with some mentioning that the issue might be resolved with kernel 6.10. Unfortunately, this is not the case for me. I have encountered the same problem in an older VM with Fedora 34 and kernel 5.16, as well as in newer VMs with Fedora 38 and 40 running kernel 6.10. This sounds similar, but the error is different: https://access.redhat.com/solutions/7004385 One of the affected vms runs Fedora 40 with kernel 6.10.6-200.fc40.x86_64, it has spice-vdagent-0.22.1-6 installed. This vm currently has 32 GB of RAM allocated.

My host is debian 12 and I used virt-manager for the virtualization. My guest is Kali Linux. I'm using an Ethernet connection and I need to use a bridge network to connect to an internal machine in my network. So on my host, I edited my /etc/network/interfaces as follows:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

auto enp0s31f6
iface enp0s31f6 inet manual

auto br0
iface br0 inet dhcp
bridge_ports enp0s31f6
bridge_hw

My source for this is: https://www.reddit.com/r/debian/comments/115f64u/debian_12_bookworm_network_bridging_for_kvm_vm/ You can see the VM configuration below: Maybe my host firewall blocks something so I installed firewalls and I added the following rules:

firewall-cmd --permanent --direct --passthrough ipv4 -I FORWARD -i br0 -j ACCEPT
firewall-cmd --permanent --direct --passthrough ipv4 -I FORWARD -o br0 -j ACCEPT
systemctl restart firewalld

source: https://forums.opensuse.org/t/firewall-blocks-internet-on-bridge-in-kvm-virtual-machine/138737/6 Unfortunately, it changed nothing.

As far as I can see, VirtualBox 7.x only supports the following formats: * .vdi * .vhd * .vmdk * .hdd * .qcow/.qcow1 * .qed The virt-manager 4.1 again only seems to support the following formats: * .raw * .qcow2 Is it possible to use e.g. the .qed, .qcow/.qcow1 and the .vmdk format also with virt-manager? **Remark:** It is known that some formats can be converted p.e. by qemu into others. However, we are not asking for conversion options. We are asking for formats that can be used under VirtualBox _as well as_ the virt-Manager.

I have Virtual Machine Manager installed on my Raspberry Pi 4B (8GB) running Bullseye. I also installed RedHat, but I don’t have Gnome, and I’m wondering if it’s possible to run a GUI in Virtual Machine Manager on the Pi 4B (8GB). When I try to start Firefox, I get this error: Error: no DISPLAY environment variable specified

I have been happily using KVM and virt-manager on Arch Linux for about a year now. This morning, one of my VMs broke (that is another story which I don't think is related), and I decided that it would just be easiest to delete it and virt-install again. However, after deleting this VM via the virt-manager interface, I was no longer able to start virt-manager:

$ virt-install
Traceback (most recent call last):
  File "/usr/share/virt-manager/virt-install", line 15, in 
    import virtinst
  File "/usr/share/virt-manager/virtinst/__init__.py", line 49, in 
    from virtinst.domain import *  # pylint: disable=wildcard-import
  File "/usr/share/virt-manager/virtinst/domain/__init__.py", line 5, in 
    from .blkiotune import DomainBlkiotune
  File "/usr/share/virt-manager/virtinst/domain/blkiotune.py", line 8, in 
    from ..xmlbuilder import XMLBuilder, XMLChildProperty, XMLProperty
  File "/usr/share/virt-manager/virtinst/xmlbuilder.py", line 16, in 
    from .xmlapi import XMLAPI
  File "/usr/share/virt-manager/virtinst/xmlapi.py", line 7, in 
    import libxml2
  File "", line 991, in _find_and_load
  File "", line 975, in _find_and_load_unlocked
  File "", line 671, in _load_unlocked
  File "", line 779, in exec_module
  File "", line 911, in get_code
  File "", line 580, in _compile_bytecode
EOFError: marshal data too short

It seems that libxml2 is broken in some way:

Python 3.8.3 (default, May 17 2020, 18:15:42) 
[GCC 10.1.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import libxml2
Traceback (most recent call last):
  File "", line 1, in 
  File "", line 991, in _find_and_load
  File "", line 975, in _find_and_load_unlocked
  File "", line 671, in _load_unlocked
  File "", line 779, in exec_module
  File "", line 911, in get_code
  File "", line 580, in _compile_bytecode
EOFError: marshal data too short

I have tried updating my system as well as removing and reinstalling the obvious packages, libvirt, virt-manager, libxml2 and libvirt-python, and that has not helped, nor has the somewhat dangerous pacman -Syyu. Any ideas about what might be broken here? I am using the LTS kernel, 5.4. Python version is 3.8. Virt-manager is 2.2.1 Also, if I just start python, I can load all the modules mentioned in the above error without any issue. I'm close to just doing a clean reinstall, but that is a terrible bother, and I'd like to avoid it if I can just fix some dependencies in Arch edit: As suggested in the comment, I tried running strace and here is the output (perhaps if I look at it long enough I will have some insight about which file might be corrupted). File corruption does seem likely as I ran out of disk space on root.

~]$ strace python -c 'import libxml2'
#output was too big to paste in here, so I cut out everything but the last part, which is what seemed most likely to be relevant
###..........many lines deleted....####
###..........many lines deleted....####
###..........many lines deleted....####
getcwd("/home/boss", 1024)              = 11
stat("/home/boss", {st_mode=S_IFDIR|0750, st_size=3488, ...}) = 0
stat("/home/boss", {st_mode=S_IFDIR|0750, st_size=3488, ...}) = 0
stat("/home/boss", {st_mode=S_IFDIR|0750, st_size=3488, ...}) = 0
openat(AT_FDCWD, "/home/boss", O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = 3
fstat(3, {st_mode=S_IFDIR|0750, st_size=3488, ...}) = 0
getdents64(3, /* 41 entries */, 32768)  = 1416
getdents64(3, /* 0 entries */, 32768)   = 0
close(3)                                = 0
stat("/usr/lib/python3.8", {st_mode=S_IFDIR|0755, st_size=8192, ...}) = 0
stat("/usr/lib/python3.8/lib-dynload", {st_mode=S_IFDIR|0755, st_size=8192, ...}) = 0
stat("/home/boss/.local/lib/python3.8/site-packages", {st_mode=S_IFDIR|0700, st_size=3488, ...}) = 0
stat("/usr/lib/python3.8/site-packages", {st_mode=S_IFDIR|0755, st_size=8192, ...}) = 0
stat("/usr/lib/python3.8/site-packages/libxml2.py", {st_mode=S_IFREG|0644, st_size=345896, ...}) = 0
stat("/usr/lib/python3.8/site-packages/libxml2.py", {st_mode=S_IFREG|0644, st_size=345896, ...}) = 0
openat(AT_FDCWD, "/usr/lib/python3.8/site-packages/__pycache__/libxml2.cpython-38.pyc", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=139264, ...}) = 0
ioctl(3, TCGETS, 0x7fffbe383200)        = -1 ENOTTY (Inappropriate ioctl for device)
lseek(3, 0, SEEK_CUR)                   = 0
lseek(3, 0, SEEK_CUR)                   = 0
fstat(3, {st_mode=S_IFREG|0644, st_size=139264, ...}) = 0
mmap(NULL, 143360, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f2172e15000
read(3, "U\r\r\n\0\0\0\0\203\224\246^(G\5\0\343\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 139265) = 139264
read(3, "", 1)                          = 0
close(3)                                = 0
mmap(NULL, 262144, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f2172dd5000
write(2, "Traceback (most recent call last"..., 35Traceback (most recent call last):
) = 35
write(2, "  File \"\", line 1, in ", line 1, in 
) = 39
openat(AT_FDCWD, "", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/lib/python38.zip/", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/lib/python3.8/", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/lib/python3.8/lib-dynload/", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/home/boss/.local/lib/python3.8/site-packages/", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/lib/python3.8/site-packages/", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
write(2, "  File \"", line 991, in _find_and_load
) = 68
openat(AT_FDCWD, "", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/lib/python38.zip/", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/lib/python3.8/", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/lib/python3.8/lib-dynload/", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/home/boss/.local/lib/python3.8/site-packages/", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/lib/python3.8/site-packages/", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
write(2, "  File \"", line 975, in _find_and_load_unlocked
) = 77
openat(AT_FDCWD, "", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/lib/python38.zip/", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/lib/python3.8/", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/lib/python3.8/lib-dynload/", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/home/boss/.local/lib/python3.8/site-packages/", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/lib/python3.8/site-packages/", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
write(2, "  File \"", line 671, in _load_unlocked
) = 68
openat(AT_FDCWD, "", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/lib/python38.zip/", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/lib/python3.8/", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/lib/python3.8/lib-dynload/", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/home/boss/.local/lib/python3.8/site-packages/", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/lib/python3.8/site-packages/", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
write(2, "  File \"", line 779, in exec_module
) = 74
openat(AT_FDCWD, "", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/lib/python38.zip/", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/lib/python3.8/", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/lib/python3.8/lib-dynload/", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/home/boss/.local/lib/python3.8/site-packages/", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/lib/python3.8/site-packages/", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
write(2, "  File \"", line 911, in get_code
) = 71
openat(AT_FDCWD, "", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/lib/python38.zip/", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/lib/python3.8/", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/lib/python3.8/lib-dynload/", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/home/boss/.local/lib/python3.8/site-packages/", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/lib/python3.8/site-packages/", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
write(2, "  File \"", line 580, in _compile_bytecode
) = 80
openat(AT_FDCWD, "", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/lib/python38.zip/", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/lib/python3.8/", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/lib/python3.8/lib-dynload/", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/home/boss/.local/lib/python3.8/site-packages/", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/lib/python3.8/site-packages/", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
write(2, "EOFError: marshal data too short"..., 33EOFError: marshal data too short
) = 33
rt_sigaction(SIGINT, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=SA_RESTORER, sa_restorer=0x7f21734763e0}, {sa_handler=0x7f21736ca3a2, sa_mask=[], sa_flags=SA_RESTORER, sa_restorer=0x7f21734763e0}, 8) = 0
munmap(0x7f2172dd5000, 262144)          = 0
munmap(0x7f2172e15000, 143360)          = 0
sigaltstack(NULL, {ss_sp=0x5610230bc580, ss_flags=0, ss_size=16384}) = 0
sigaltstack({ss_sp=NULL, ss_flags=SS_DISABLE, ss_size=0}, NULL) = 0
exit_group(1)                           = ?
+++ exited with 1 +++

edit: This thread seems promising, but I have no idea where I would check to see if __init__.py is missing.

I managed to get my NVidia GPU (RTX 3070) working with 3D acceleration in virt-manager. I had to make a user QEMU/KVM session as there's some bug not causing it to not work in the system/root session. I also needed to make a separate EGL-Headless device with the following XML: (As a side note, having rendernode to /dev/nvidia0 just crashes the VM after the initial text pops up in case that is somehow relevant) Regardless, the main issue I am having now is that the display still seems absurdly choppy and the screen tearing is abysmal. I'm not sure what the problem is but after looking around for a while I found 2 potentially related links with similar issues? Is this simply an unfortunate issue for NVidia GPUs?: [https://gitlab.com/libvirt/libvirt/-/issues/311](https://gitlab.com/libvirt/libvirt/-/issues/311) [https://github.com/NixOS/nixpkgs/issues/164436](https://github.com/NixOS/nixpkgs/issues/164436) The weird thing is that I saw a very recent tutorial to set up 3D acceleration for NVidia GPUs on virt-manager but the absurd screen-tearing and lagginess doesn't seem to be happening to the guy in the video: [https://www.youtube.com/watch?v=2ljLqVDaMGo&t](https://www.youtube.com/watch?v=2ljLqVDaMGo&t) Basically looking for some explanation/confirmation of the issue (and maybe even a fix if possible)

I have a /dev/ttyUSB0 on my Debian for a serial RS232 device. What I try to do is to pass it into a WindowsXP (virtmanager, KVM, qemu) as a serial interface (e.g. COM2). I don`t get it done. The only thing I can do is to pass it as as USB-device. That works but then WinXP asks for a driver - what I do not have. So how to get my USB-serial as an non-USB serial into the virtual machine?

I'm having trouble understanding why my host and guest machines don't have internet connections. I'm using NAT in virt-manager. When I am not connected to Wi-Fi

user@user ~> ip route
169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown

When I am connected to Wi-Fi

user@user ~> ip route
default via 192.168.100.1 dev wlo1 proto dhcp src 192.168.100.46 metric 600 
169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 
192.168.100.0/24 dev wlo1 proto kernel scope link src 192.168.100.46 metric 600 
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown

When the guest machine is running

user@user ~> ip route
0.0.0.0 dev vnet0 scope link 
default dev vnet0 scope link 
default via 192.168.100.1 dev wlo1 proto dhcp src 192.168.100.46 metric 600 
169.254.0.0/16 dev vnet0 proto kernel scope link src 169.254.28.155 
169.254.0.0/16 dev virbr0 scope link metric 1000 
192.168.100.0/24 dev wlo1 proto kernel scope link src 192.168.100.46 metric 600 
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1

The output of the command traceroute 8.8.8.8 when the guest machine is running:

1 user (169.254.84.131) ...

While when the guest machine is not running:

1 _gateway (192.168.100.1) ...
2 ...
...
11 ...

I don't know a lot about networking. Any help is much appreciated! Edit: I also forgot to mention that when the guest machine is not running, the internet connection of the host machine is working.

My host is Arch Linux and I'm using virt-manager to run VMs. I noticed it had access to my microphone when Cortana started listening to me after a Windows guest install. I've looked through all the settings in the virtual hardware details section but I can't find anything relating to microphones. There is a "Sound" device added automatically, and when I delete it the VM looses access to the microphone, but it also cannot output any sound. I'm looking for a way to cut off microphone access while still allowing audio to come out.

virt-manager uses BIOS as the default option for firmware. There is an option to change this to UEFI just before installation, after the volume is set up. However, after installation, the dropdown menu for changing the firmware disappears. The installed system boots only with UEFI and not BIOS. The installation was a cumbersome procedure and I would like to avoid doing it all over again if possible. Is there a way to convert the firmware to UEFI while keeping the contents of the system (disk) intact?

I am attempting to passthrough a WiFi dongle (USR5423 802.11bg Wireless Adapter [ZyDAS ZD1211B]) to a VM running Debian 12 running under QEMU/KVM. I need the device passed through to the VM for a project i am working on. I have installed the zd1211rw firmware, and it seems that the system knows that it is a wlan adapter since it is visible as a network interface, it doesn't come up but it's there: 4: wlx0014c142c70c: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 26:c2:97:8f:76:ec brd ff:ff:ff:ff:ff:ff permaddr 00:14:c1:42:c7:0c Moreover, if i check dmesg, I see there are some serious errors with loading the firmware.

[  250.122984] usb 1-3: USB control request for firmware upload failed. Error number -110
[  250.123003] usb 1-3: Could not upload firmware code uph. Error number -110
[  250.123033] zd1211rw 1-3:1.0: couldn't load firmware. Error number -110

From various searches across the internet, I think the error -110 is related to USB timing out. For this, I added GRUB_CMDLINE_LINUX_DEFAULT="usb-storage.quirks=0baf:0121:u" to the grub config inside /etc/default/grub, but it didn't help much. Any tips?

I cloned a GPT formatted disk that contains a dual boot (Windows + Linux Debian) that works perfectly well on its real machine. I try to create a VM with Qemu that uses the cloned disk, to make it boot on the Debian partition but the best I could do is to boot Windows. Here is the command I used:

-sh
virt-install \
    --name "vm-test_dual_boot" \
    --boot loader=/usr/share/OVMF/OVMF_CODE.fd \
    --vcpus 2 --memory 8192 --osinfo debian11 \
    --network bridge=br0 \
    --graphics=vnc \
    --disk path=/home/user/vm/clone.qcow2 \
    --import -v

I can not do the same thing as the real UEFI machine which associates a HD(1,GPT,unique_identifier) ​​filesystem with the \EFI\debian\shimx64.efi file. Could you help me boot Debian? --- Thanks to @telcoM I changed the command in :

-sh
boot_config=\
"loader=/usr/share/OVMF/OVMF_CODE_4M.fd,"\
"loader.readonly=yes,"\
"loader.type=pflash,"\
"nvram.template=/usr/share/OVMF/OVMF_VARS_4M.ms.fd,"\
"nvram=/home/user/vm/clone_nvram.fd" ;

virt-install \
    --name "vm-test_dual_boot" \
    --boot $boot_config \
    --vcpus 2 --memory 8192 --osinfo win10 \
    --network bridge=br0 \
    --graphics=vnc \
    --disk path=/home/user/vm/clone.qcow2 \
    --import -v

Notes: - from the directory /usr/share/OVMF loader must match the nvram.template then OVMF_CODE_4M.fd to OVMF_VARS_4M.ms.fd, so in my case this triggered this error : "Guest has not initialized the display ( yet )". - the user defined in /etc/libvirt/qemu.conf (default : libvirt-qemu), must have read and execute right acccess to the nvram file else this trigger a permission error. - in my case --osinfo win10 is mandatory as the default vHD EFI boot is Windows (before I tried debian11 which ended on BSOD ). - for the --network part it is assumed that we have a br0 bridge device (see here for temporary bridge with Network Manager or here with iproute and here for permanent one with ifup). Once created, configure VM EFI to boot the right partition (see @telcoM detailed answer to achieve it temporarily or permanently).