I have a host with 4 ethernet ports. I want to assign eno1 to VM1, eno2 to VM2 and so on... eno1, eno2 , eno3 and eno4 each have static IPs. I want VM01 to have the static IP of eno2. For that purpose I setup a bridge and added eno2 to the bridge. upto this point it looks ok. After that I installed VM using cockpit. during install I let the config as default to enp1s0 (with DHCP for IPv4). After install on boot up the interface did not get IP address. I am expecting eno2 IP which shows up on bridge after eno2 was added to bridge, should show up for this interface. **on VM client** **nmcli connection status** **From KVM host: I believe the vnet0 came from VM install. relevant output below:** # ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 3: eno2: mtu 1500 qdisc mq master br2 state UP group default qlen 1000 link/ether 20:67:7c:d6:07:a5 brd ff:ff:ff:ff:ff:ff 19: br2: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 20:67:7c:d6:07:a5 brd ff:ff:ff:ff:ff:ff inet 123.112.147.147/26 brd 135.193.167.191 scope global noprefixroute br2 valid_lft forever preferred_lft forever 22: vnet0: mtu 1500 qdisc fq_codel master br2 state UNKNOWN group default qlen 1000 link/ether fe:54:00:e6:ef:b1 brd ff:ff:ff:ff:ff:ff inet6 fe80::fc54:ff:fee6:efb1/64 scope link valid_lft forever preferred_lft forever # bridge link show 3: eno2: mtu 1500 master br2 state forwarding priority 32 cost 100 22: vnet0: mtu 1500 master br2 state forwarding priority 32 cost 100 here is the xml portion from VM:

I have an issue creating VMs on CentOS using Boxes with the following error:

Virtualization extensions are unavailable on your system. Check your BIOS settings to enable them.

Also, when I try to use Virtual Machine Manager it says that

ins not available

, while I did install it and it's running with all needed libs. I wanted to access BIOS but there is a password on it (the laptop I have was a present and I don't know the password). I did try to flash the BIOS by upgrading it. I created a BIOS recovery USB drive, but it turns out that BIOS will not start the update wizard since there might be some issue with CMOS. The procedure for resetting CMOS on this HP is not working at all (it's ignored and the laptop just boots up regularly). Is there any way I can reset the BIOS password from the terminal? I lost a few hours Googling but I couldn't find any solution. It seems that my only chance is to do it from the terminal or some tool (if it exists). Edit: Laptop: HP Folio 9470m (I followed instructions for BIOS flash from HP support doc.) CPU on laptop is supporting virtualization: [root@DESKTOP-GHPREJB ivan]# lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 2 Core(s) per socket: 2 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 58 Model name: Intel(R) Core(TM) i5-3427U CPU @ 1.80GHz Stepping: 9 CPU MHz: 941.480 CPU max MHz: 2800.0000 CPU min MHz: 800.0000 BogoMIPS: 4589.71 Virtualization: VT-x Also: [root@DESKTOP-GHPREJB ivan]# egrep -q 'vmx|svm' /proc/cpuinfo && echo yes || echo no yes Edit 2: For future search results, this can help as this is the official reply I got from HP support on BIOS password reset request: >HP is committed to the security and privacy of its customers. HP has changed the policy regarding the BIOS Password Reset Service and will no longer provide this option to our customers. This change allows HP to protect customer’s data, BIOS configuration, and device settings, ensuring best in class security for HP products. Allowing access into the BIOS provides the potential opportunity for a rogue user to remove current security settings and change other device settings that could make the PC’s data vulnerable. For this reason, we are no longer able to reset the BIOS password for any reason. • The BIOS password feature on the HP PC was created for the users to provide an option to secure their PC at a hardware level, and it is the responsibility of the user to manage their password. If the BIOS password is forgotten, HP no longer provides a service to reset or remove the BIOS password. • If a unit has a BIOS password and is being sent in for repair, customer should remove the BIOS admin password and Power on password before the service is initiated. • If the unit has the password and the customer is unwilling/unable to provide the password, HP may not be able to complete the repair work. Then the option is that customer can replace the board at his/her own cost as this is not covered under warranty.

I've just configured the passthrough on my ubuntu / I9 9900k / nvidia geforce RTX 2080 ti machine. Now I'm converting the VMware virtual machine VMDK files (created from the conversion of a physical installation of Windows 10) into one big qcow2 file with the following command : mario@ziomario-Z390-AORUS-PRO:/media/ziomario/DATI/DiscoC/DESKTOP-N9UN2H3# qemu-img convert -f vmdk DESKTOP-N9UN2H3*.vmdk -O qcow2 /media/ziomario/WIN/DiscoC/DESKTOP-N9UN2H3/QCOW2/DESKTOP-N9UN2H3.qcow2 The physical installation of Windows 10 has a size of 300 GB. The VMDK files produced by the conversion did with vCenter Converter have a size of 558 GB. I don't know what could be the final size of the converted qcow2 file. What I know is that I tried to save it in a disk of 1 TB and it became full. I would like to know if there is a way to convert more than one VMDK file into a qcow2 or img file (these are the formats accepted by qemu/kvm virt-manager) that will have almost the same size of the original ones. thanks.

i have a headless box running bbqlinux that i'm trying to use as an android-studio development box. when i go to launch an .avd in the emulator, i receive this error: Cannot launch AVD in emulator Output: emulator: ERROR: x86 emulation currently requires hardware acceleration! Please ensure KVM is properly installed and usable. CPU acceleration status: This user doesn't have permissions to use KVM (/dev/kvm). this was freaking me out and i spent a good amount of time trying to sure that everything was enabled, installed correctly, permissions set, etc... then: i plugged a screen in and logged directly into the box and bam! it works fine. so my problem is maybe the vncserver? i'm using tigervnc that i set up according to this page: https://wiki.archlinux.org/index.php/Vncserver just in case it helps, my xstartup file is unset SESSION_MANAGER unset DBUS_SESSION_BUS_ADDRESS [ -x /etc/vnc/xstartup ] && exec /etc/vnc/xstartup [ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources vncconfig -iconic & startxfce4 & other than that, i've not changed the default environment hardly at all except to add lighttable, ssh, & vnc. so my question is really - should i not be doing it this way? is there a better workflow or vnc server program for what i'm trying to do? - is there a command switch or option that i missed that maybe enables the hardware acceleration over vnc? thanks!

*System: Ubuntu MATE 24.04.2* I tried to start a virtual machine under VirtualBox and received the following error: > VirtualBox can't enable the AMD-V extension. Please disable the KVM kernel extension, recompile your kernel and reboot (VERR_SVM_IN_USE). I made no changes to my system (that I am aware) to cause this. Yesterday all was fine, today the problem. Fortunately, a quick search revealed the following article with the solution: Quick Fix VirtualBox can’t enable the AMD-V extension I am assuming that KVM was enabled in a background system update. Questions: 1) How and why were the KVM modules enabled? 2) Can I safely, as per the article, permanently blacklist the kvm and kvm_amd modules?

Every time I start/stop a KVM, the libvirtd 3.0.0-4 throws the following error in syslog: libvirtd: 2018-08-07 21:00:19.699+0000: 3145: \ error : qemuMonitorIO:710 : internal error: \ End of file from qemu m onitor virtlogd: 2018-08-07 21:00:19.901+0000: 2753: \ error : virNetSocketReadWire:1801 : \ End of file while reading data: Input/output error Does anyone experience the same problem?

One of my KVM servers (2 Xeon E5-2680 v2, 1 AMD Vega 10 GPU, Ubuntu 20.04.1 LTS) became unresponsive last night. Of the 5 VMs running on the server, only one could be reached. The server itself refused SSH connections, and I could not even get a screen over HDMI. I did not see any other solution than to reset it. Having done that, I would like to better understand what was actually going on. The following journals are available on the system: # journalctl --list-boots -8 57c5ae37af1649379e82b349abb14f9d Sun 2020-05-24 20:25:57 CEST—Sun 2020-05-24 20:44:30 CEST -7 c617acfdd3854669bd114d1d033cd5a7 Sun 2020-05-24 20:45:01 CEST—Mon 2020-05-25 19:21:48 CEST -6 745df76c9d784907862118c7804a19ab Mon 2020-05-25 19:22:26 CEST—Mon 2020-05-25 19:42:17 CEST -5 9781df6fa3494c4588d0cf4a99678e84 Mon 2020-05-25 19:42:59 CEST—Thu 2020-06-04 04:53:20 CEST -4 db93d994719a4ee1ad8eb74932220898 Thu 2020-06-04 18:45:10 CEST—Thu 2020-06-04 19:16:38 CEST -3 c6007ce834bd4933805138523549677e Thu 2020-06-04 19:17:20 CEST—Thu 2020-08-20 18:35:54 CEST -2 c24b967697ce41a2ac6c1707936dc450 Thu 2020-08-20 18:36:23 CEST—Mon 2020-08-31 17:21:52 CEST -1 b1efda1e7a3b42d4ae9a20f0c3b06fcf Mon 2020-09-07 09:49:24 CEST—Mon 2020-09-07 09:59:49 CEST 0 f5de0a1534a7478e87847031156976d0 Mon 2020-09-07 10:00:19 CEST—Mon 2020-09-07 10:08:33 CEST As you may already see from the list, the last 7 days are missing, I don't actually have access to a journal leading up to the system error. Running journalctl --verify shows the following output. 1f23cc0: Invalid object File corruption detected at /var/log/journal/f9decb319623482392299509c566049a/system@0005a744de309d9e-3dfdf0e20f2b37de.journal~:1f23cc0 (of 33554432 bytes, 97%). FAIL: /var/log/journal/f9decb319623482392299509c566049a/system@0005a744de309d9e-3dfdf0e20f2b37de.journal~ (Bad message) PASS: /var/log/journal/f9decb319623482392299509c566049a/system@24f780e4155245c0a176021b285d8b61-0000000000000001-0005a744de2ec87d.journal PASS: /var/log/journal/f9decb319623482392299509c566049a/user-1000@6da18e6709a04eb8809cb4af946ec557-00000000000008e3-0005a66900b2a7be.journal PASS: /var/log/journal/f9decb319623482392299509c566049a/system@24f780e4155245c0a176021b285d8b61-0000000000010c89-0005a8cfc4df2d27.journal PASS: /var/log/journal/f9decb319623482392299509c566049a/user-1000@6da18e6709a04eb8809cb4af946ec557-0000000000010c88-0005a8cfc4dec165.journal PASS: /var/log/journal/f9decb319623482392299509c566049a/system@24f780e4155245c0a176021b285d8b61-000000000001b654-0005ab341293df34.journal PASS: /var/log/journal/f9decb319623482392299509c566049a/user-1000@6da18e6709a04eb8809cb4af946ec557-000000000001bf95-0005ab56000dcbe1.journal PASS: /var/log/journal/f9decb319623482392299509c566049a/system@0005aeb4750f8660-d0ac81b12520109c.journal~ PASS: /var/log/journal/f9decb319623482392299509c566049a/system@cf2a7210a86040e6aa7736d9b0a88e8b-0000000000000001-0005aeb4750dab5e.journal PASS: /var/log/journal/f9decb319623482392299509c566049a/system.journal PASS: /var/log/journal/f9decb319623482392299509c566049a/user-1000@6da18e6709a04eb8809cb4af946ec557-00000000000269b9-0005ad9c6a92da4a.journal PASS: /var/log/journal/f9decb319623482392299509c566049a/user-1000.journal Reading through some of the obvious web search results, it seems that it is currently not possible to repair a corrupted journal, it's just gone. Frankly, I find it a bit strange when the systemd lead writes that he does not see a need for corrupt journalctl entries to be fixed but maybe it's just me. I'm really not sure what else to do. In my /var/log, I also have files called syslog but they also stop on August 31 and continue today. The same is true for kern. I looked through some other log files such as Xorg and dmesg. Honestly, I'm not even sure what to look for but nothing seems to jump at me. Xorg.log shows only one error that seems unlikely to be the culprit for my problems: [230912.637] (II) xfree86: Adding drm device (/dev/dri/card0) [230912.637] (EE) /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied There seem to be no error or fail messages in dmesg. I mean, everything works currently but this error seems to repeat itself every few weeks. Which other steps can I take to get a better understanding of this issue?

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

I have Fedora 35 installed as a VM, with Qemu/KVM as the hypervisor and virt-manager as the graphical front-end, running under Manjaro KDE. Following numerous guides & answers I have managed to get clipboard sharing to work between the host and client using the spice display server and spice-vdagent on the client. However this only seems to work when the client logins to the X11 session. I have found [a Reddit post](https://www.reddit.com/r/swaywm/comments/pg0rqi/clipboard_sharing_using_spicevdagent_not_working/) which claims spice-vdagent only supports the X11 clipboard, which is uncorroborated but so far agrees with my testing. Here's the systemd journals when I login to X11/Wayland on the VM respectively:

> journalctl -b -u spice-vdagentd*
## timestamps & hostname removed

## X11
spice-vdagentd: opening vdagent virtio channel
spice-vdagentd: Set max clipboard: 104857600
spice-vdagentd: Set max clipboard: 104857600

## Wayland
spice-vdagentd: Error getting owner UID for pid 1063: No such process
spice-vdagentd: UID mismatch: UID=1000 PID=1063 suid=4294967295

So my question is: is it true that spice-vdagent does not yet support Wayland clipboard? If false, what could be going wrong? If true, are there currently any good workarounds (except for the obvious "don't use Wayland")?

I need your advice. Brief to my question: I got two Linux/Ubuntu 18.04 LTS machines. First one is the host (SSHD) and has a VM machine installed on it (virtual machine's ethernet is configured as NAT: Qemu/KVM - virtualization). Simple SSH connection between host and VM on it in NAT regime works perfectly:

ssh user@ip.address > pass

First machine is connected to router via LAN and second machine is a ssh-client connected to a router via Wifi. machine1(host machine, LAN) > Router mtu 1500 inet 192.168.122.x netmask 255.255.255.0 broadcast 192.168.122.255 ``` P.S. I would prefer not to switch NAT to bridge regime. If you need more data, I will gladly provide you with some more details.

I have a VM which has an attached raided device with fstab entry: /dev/md127 /mnt/blah ext4 nofail 0 2 The raided disks are corrupted and during startup the unit entered emergency/maintence mode, which means only the local host user could exit this mode and start it up normally. During normal startup the following occurred in syslog: systemd-fsck: /dev/md127 contains a file system with errors, check forced. systemd-fsck: /dev/md127: Inodes that were part of a corrupted orphan linked list found. systemd-fsck: /dev/md127: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. systemd-fsck: #011(i.e., without -a or -p options) systemd-fsck: fsck failed with exit status 4. systemd-fsck: Running request emergency.target/start/replace systemd: systemd-fsck@dev-md127.service: Main process exited, code=exited, status=1/FAILURE systemd: systemd-fsck@dev-md127.service: Failed with result 'exit-code'. systemd: Failed to start File System Check on /dev/md127. systemd: Dependency failed for /mnt/blah. systemd: Dependency failed for Provisioner client daemon. My guess is that the OS goes to emergency/maintenance mode because of the corrupt raided disks: systemctl --state=failed UNIT LOAD ACTIVE SUB DESCRIPTION ● systemd-fsck@dev-md127.service loaded failed failed File System Check on /dev/md127 What i want is for the VM to startup regardless of whether the raided drives are corrupt/unmountable, so it shouldn't go to emergency/maintenance mode. I followed these posts to attempt at disabling emergency/maintenance mode: - https://unix.stackexchange.com/questions/416640/how-to-disable-systemd-agressive-emergency-shell-behaviour - https://unix.stackexchange.com/questions/326493/how-to-determine-exactly-why-systemd-enters-emergency-mode/393711#393711 - https://unix.stackexchange.com/questions/422319/emergency-mode-and-local-disk I had to first create the directory local-fs.target.d in /etc/systemd/system/, which felt wrong. I then created a nofail.conf in /etc/systemd/system/local-fs.target.d/nofail.conf containing: [Unit] OnFailure= After loading that drop file, I was able to confirm that the drop file was found by local-fs.target: sudo systemctl status local-fs.target ● local-fs.target - Local File Systems Loaded: loaded (/lib/systemd/system/local-fs.target; static; vendor preset: enabled) Drop-In: /etc/systemd/system/local-fs.target.d └─nofail.conf Active: active since Tue 2019-01-08 12:36:41 UTC; 3h 55min ago Docs: man:systemd.special(7) BUT, after rebooting, the VM still ended up in emergency/maintenance mode. Have i missed something? Does the nofail.conf solution not work with raided disks? ---------- EDIT: I was able to get a print out of the logs when the system booted to emergency mode (sorry it's a screenshot since i don't have access to the host and had to ask the owner for it): Here's the output from systemctl for systemd-fsck@dev-md127:

sudo systemctl status --no-pager --full systemd-fsck@dev-md127
 ● systemd-fsck@dev-md127.service - File System Check on /dev/md127
    Loaded: loaded (/lib/systemd/system/systemd-fsck@.service; static; vendor preset: enabled)
    Active: failed (Result: exit-code) since Thu 2019-01-10 12:05:44 UTC; 2h 57min ago
      Docs: man:systemd-fsck@.service(8)
   Process: 1025 ExecStart=/lib/systemd/systemd-fsck /dev/md127 (code=exited, status=1/FAILURE)
  Main PID: 1025 (code=exited, status=1/FAILURE)

 systemd: Starting File System Check on /dev/md127...
 systemd-fsck: /dev/md127 contains a file system with errors, check forced.
 systemd-fsck: /dev/md127: Inodes that were part of a corrupted orphan linked list found.
 systemd-fsck: /dev/md127: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
 systemd-fsck:         (i.e., without -a or -p options)
 systemd-fsck: fsck failed with exit status 4.
 systemd-fsck: Running request emergency.target/start/replace
 systemd: systemd-fsck@dev-md127.service: Main process exited, code=exited, status=1/FAILURE
 systemd: systemd-fsck@dev-md127.service: Failed with result 'exit-code'.
 systemd: Failed to start File System Check on /dev/md127.

As i pointed out earlier, i have nofail set in /etc/fstab. Now the questions are: 1. What is the dependency in the failed dependency in the screenshot? 2. If fsck fails on /dev/md127, why does it enter emergency mode and how do i disable that? EDIT 2: A couple of other things i can add are: 1. the vm is a kvm vm 2. it's a software raid Kind regards, Ankur

Problem: I have a new SATA drive I wish to sysprep with a Windows installation. I only have Windows virtualised on my PC. My Solution: Attach (passthrough) the entire drive to the Windows VM and sysprep as normal. This is my VGA/Passthrough script: #!/bin/bash #1st PART configfile=/etc/vfio-pci.cfg vfiobind() { dev="$1" vendor=$(cat /sys/bus/pci/devices/$dev/vendor) device=$(cat /sys/bus/pci/devices/$dev/device) if [ -e /sys/bus/pci/devices/$dev/driver ]; then echo $dev > /sys/bus/pci/devices/$dev/driver/unbind fi echo $vendor $device > /sys/bus/pci/drivers/vfio-pci/new_id } modprobe vfio-pci cat $configfile | while read line;do echo $line | grep ^# >/dev/null 2>&1 && continue vfiobind $line done #2nd PART xrandr --output DVI-D-0 --off /usr/bin/synergys --config /home/%username%/.synergy.conf export QEMU_ALSA_DAC_BUFFER_SIZE=512 QEMU_ALSA_DAC_PERIOD_SIZE=170 QEMU_AUDIO_DRV=alsa sudo qemu-system-x86_64 \ -enable-kvm \ -M q35 \ -m 8192 \ -cpu host,kvm=off,migratable=off,+invtsc,enforce \ -smp 4,sockets=1,cores=4,threads=1 \ -bios /usr/share/seabios/bios.bin -vga none \ -device ioh3420,bus=pcie.0,addr=1c.0,multifunction=on,port=1,chassis=1,id=root.1 \ -device vfio-pci,host=06:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on \ -device vfio-pci,host=06:00.1,bus=root.1,addr=00.1 \ -soundhw all \ -drive if=none,file=/media/VM/windows1.img,id=disk,format=raw -device ide-hd,bus=ide.0,drive=disk \ -net tap,vlan=0 \ -boot menu=on sudo killall synergys xrandr --output DVI-D-0 --auto xrandr --output DVI-D-0 --right-of HDMI-0 exit 0 Question 1): I want to make /dev/sdc available to the VM. What -option format will achieve this. (To reiterate the new disk, sdc, has **no** content, partition or formatting at this point.) Question 2): Am I making life stupidly difficult for myself and is there is much simpler solution. Question 3) I do know that this can be achieved by using .xml script that virt-manager uses, but as you see I am not using virt-manager to launch the VM (because of the VGA Pasthrough), would it be possible to convert/import this startup script into the virt-manager .xml format and then add something like: ...to the `` section? Many thanks just for reading to end if you managed it.

How or where were these pools created? Where are configuration files? $ virsh pool-list --all Name State Autostart ------------------------------------------- default active yes Downloads active yes $ virsh pool-info Downloads Name: Downloads UUID: fdbe7407-67c4-405d-8e46-9c2695a8b353 State: running Persistent: yes Autostart: yes Capacity: 219.88 GiB Allocation: 34.87 GiB Available: 185.01 GiB $ virsh pool-info default Name: default UUID: cb72b02e-b436-4ec9-9460-d297744c4c69 State: running Persistent: yes Autostart: yes Capacity: 219.88 GiB Allocation: 34.95 GiB Available: 184.93 GiB I believe that the pools were created by the virt-manager GUI. Is there free space on default? I think that the Downloads pool is probably superfluous.

I am running a VM on a Linux host using qemu+kvm and libvirt, the guest system is CentOS 7. I wish to share a folder between the two such that host:/some/dir becomes accessible as guest:/some/other/dir. I wish to minimise effort and cannot re-compile the kernel on either side. I experimented with plan9 but cannot get it to run (the p9 dkms module won't compile on the CentOS 7 guest). There must be a better way? Performance is secondary as it does not work at all right now.

In Virtual Box there is a network type "Internal Network", which is where two or more VMs can communicate with each other only. No network connection to the host or other machines. This is the kind of network I need. Using libvirt I was able to set up an "Isolated Network". According to the libvirt docs "In this mode, guests connected to the virtual switch can communicate with each other, and with the host". This doesn't quite work for me as I need network isolation from the host. Does anyone know how to accomplish this using libvirt? I tried following along with this link and creating a virtual private bridge but couldn't get it to work. https://www.linux-kvm.org/page/Networking

I have been trying to configure port mirror on Virtual bridge created using open vswitch. I have created the following ports on Bridge demo_bridge using: sudo ovs-vsctl add-port demo_bridge victim0 Bridge demo_bridge Port "demo_bridge" Interface demo_bridge type: internal Port "victim0" Interface victim0 type: internal Port "attacker0" Interface attacker0 type: internal Port "wireshark0" Interface wireshark0 type: internal ovs_version: "2.5.2" I am conducting a simple experiment where VM1 (attached to attacker0) is going to attack VM2 (attached to victim0), and I need to mirror all traffic from attacker0 vport to wireshark0 (VM3 capturing network traffic). However, whenever I enable mirroring, I can no longer ping from VM1 (Attacker VM) to VM3 (Wireshark VM); furthermore I cannot see any mirrored traffic on VM3 either. These are the two set of commands I have used to create mirror port, and none of them work: sudo ovs-vsctl \ -- set Bridge demo_bridge mirrors=@m1 \ -- --id=@attacker0 get Port attacker0 \ -- --id=@wireshark0 get Port wireshark0 \ -- --id=@m1 create Mirror name=port_mirror1 select-dst-port=@attacker0 select-src-port=@attacker0 output-port=@wireshark0 //From YOUTUBE Video sudo ovs-vsctl \ -- --id=@p get port victim0 \ -- --id=@m create mirror name=mirror0 \ -- add bridge demo_bridge mirrors @m \ -- set mirror mirror0 output_port=@p //Activate the mirror sudo ovs-vsctl \ -- --id=@p get port ens3 \ -- set mirror mirror0 select_dst_port=@p \ -- set mirror mirror0 select_src_port=@p These commands do create the mirror port, but they also break the network connection between the attacker VM1 and victim VM2. When the mirror is removed, I can ping to all VM just fine. The local interface on each VM (ens3) has a static IP addresses connected to the Bridge demobridge. /etc/network/interfaces auto ens3 iface ens3 inet static address 172.168.0.3 network 172.168.0.0/27 netmask 255.255.255.0

I have setup KVM on Ubuntu 17.10 (host) and have Windows 10 running as guest OS on it. Attached to the computer is a USB printer. I would like to be able to print from the guest OS. Printer works fine when printing from host, but I cannot print from guest OS. So far, the guest OS has been able to successfully connect to the outside world and can even access other computers on the Windows network. I have looked around SE but only found answers to VirtualBox or Linux guest.

I am trying to run a program that uses QEMU on an Ubuntu VM in VirtualBox hosted on a Windows 10 computer with an AMD CPU. When I try to run the program it gives me this error: Could not access KVM kernel module: No such file or directory qemu-system-x86_64: failed to initialize kvm: No such file or directory I've tried a lot of solutions posted online. This one appeared the most promising. However, when I run sudo modprobe kvm_amd it gives me this error: modprobe: ERROR: could not insert 'kvm_amd': Operation not supported Tried to fix that with no luck. I ran virt-host-validate and got: QEMU: Checking for hardware virtualization : FAIL (Only emulated CPUs are available, performance will be significantly limited) 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 : WARN (Enable 'devices' in kernel Kconfig file or mount/enable cgroup controller in your system) QEMU: Checking for cgroup 'blkio' controller support : PASS QEMU: Checking for device assignment IOMMU support : WARN (Unknown if this platform has IOMMU support) QEMU: Checking for secure guest support : WARN (Unknown if this platform has Secure Guest support) Other solutions have suggested messing around with VirtualBox settings, this is what I got from trying those: This hasn't helped fix it. Other solutions mention going to the BIOS to fix it, but since this is a VM there doesn't seem to be a way to do that in VirtualBox.

I'm having this weird behavior when i start a VM on Arch Linux under wayland with Virtio, 3D acceleration enabled, Spice server and openGL enabled. Am I missing some kind of driver? When I start the VM with OpenGL disabled and it works ok. - OS: Arch Linux - Wayland - Memory: 62.2 GiB - Architecture: x86_64 - GPU: Intel(R) Arc(tm) Graphics (MTL) || Intel open-source Mesa driver || Mesa 25.1.2-arch1.1

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