Are there any opensource/free Unix like RTOS that can run a virtual machine like QNX Neutrino RTOS (http://www.qnx.com/products/evaluation/eval-target.html) ?

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 homelab setup like this (diagram is also available here ): One thing to note here is, my Proxmox host just has 1 NIC for ethernet cable. It has WiFi too but I decided not to use it because it won't play nicely with what I wanted to do (that's my understanding after reading dozens of articles/forums about it). So I plugged an ethernet cable from a WiFi repeater. This Proxmox host is located in different place in my home - that's why I didn't plug the ethernet directly to the home router. From my laptop, I can wirelessly SSH into the Proxmox host (192.168.1.5) just fine. I can also wirelessly access Proxmox's web UI at https://192.168.1.5:8006 just fine. What I want to do here is network segmentation between my home network and the VMs network. I know there are free router software out there like pfSense, OpenWrt and etc. But I want to take this the opportunity to build it from scratch so I can better understand how things are working together. I'm planning to run some VMs in this Proxmox host. They all should run within the VMs network I'm creating here. Some VMs may run on dynamic IP/DHCP mode and some may run on static IP mode. 99% of them will be Linux VMs. I'm good without IPv6 support in this VMs network for now. Also, using VLANs is not an option because my router doesn't support VLANs. With that said, I followed this guide to create a virtual router in Ubuntu VM. The only thing I did differently from that guide is I created a bridge (br0) and assign it a static IP (192.168.2.1/24) so it can be a router / virtual switch for my VMs network. I didn't follow the *Port Forwarding from the Internet to the LAN* and *So, about that testing...* steps because I don't need them. In other words, I followed all the steps until and including *Allowing traffic out to the Internet* step. What I see currently: - [OK] VMs can ping each other - [OK] VMs can ping internet - [Not OK] VM 1 and VM 2 can ping devices in home network e.g. laptop and router - [OK] Laptop can ping Router VM - [Not OK] Laptop can't ping VM 1 or VM 2* \* I already added a static route in my laptop by following this guide . I also tried adding a static route in the home router/gateway. FWIW, below are my configs... ip a from Proxmox host: 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 2: eno1: mtu 1500 qdisc pfifo_fast master vmbr0 state UP group default qlen 1000 link/ether fc:4d:d4:f3:fe:d3 brd ff:ff:ff:ff:ff:ff altname enp0s25 3: wlp2s0: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 28:c2:dd:a5:46:53 brd ff:ff:ff:ff:ff:ff 4: vmbr0: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether fc:4d:d4:f3:fe:d3 brd ff:ff:ff:ff:ff:ff inet 192.168.1.5/24 scope global vmbr0 valid_lft forever preferred_lft forever inet6 fe80::fe4d:d4ff:fef3:fed3/64 scope link valid_lft forever preferred_lft forever 5: vmbr1: mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether 8e:7e:21:7e:f9:e1 brd ff:ff:ff:ff:ff:ff inet6 fe80::8c7e:21ff:fe7e:f9e1/64 scope link valid_lft forever preferred_lft forever 11: tap104i0: mtu 1500 qdisc pfifo_fast master vmbr0 state UNKNOWN group default qlen 1000 link/ether b6:5c:75:be:38:d5 brd ff:ff:ff:ff:ff:ff 12: vmbr2: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 3e:6b:04:2c:d9:e0 brd ff:ff:ff:ff:ff:ff inet6 fe80::3c6b:4ff:fe2c:d9e0/64 scope link valid_lft forever preferred_lft forever 13: tap104i1: mtu 1500 qdisc pfifo_fast master vmbr2 state UNKNOWN group default qlen 1000 link/ether 46:d9:8f:dd:ab:77 brd ff:ff:ff:ff:ff:ff 23: tap102i0: mtu 1500 qdisc pfifo_fast master vmbr2 state UNKNOWN group default qlen 1000 link/ether 46:9c:a4:fd:81:27 brd ff:ff:ff:ff:ff:ff 24: tap103i0: mtu 1500 qdisc pfifo_fast master vmbr2 state UNKNOWN group default qlen 1000 link/ether 12:90:ee:36:27:7a brd ff:ff:ff:ff:ff:ff Content of /etc/network/interfaces in Proxmox host: auto lo iface lo inet loopback iface eno1 inet manual auto vmbr0 iface vmbr0 inet static address 192.168.1.5/24 gateway 192.168.1.1 bridge-ports eno1 bridge-stp off bridge-fd 0 iface wlp2s0 inet manual auto vmbr1 iface vmbr1 inet manual bridge-ports none bridge-stp off bridge-fd 0 auto vmbr2 iface vmbr2 inet manual bridge-ports none bridge-stp off bridge-fd 0 post-up echo 1 > /proc/sys/net/ipv4/ip_forward post-up iptables -t nat -A POSTROUTING -s '192.168.2.0/24' -o vmbr0 -j MASQUERADE post-down iptables -t nat -D POSTROUTING -s '192.168.2.0/24' -o vmbr0 -j MASQUERADE Notes: - vmbr1 was from my previous experiment and not relevant/related here; none of my VMs are using vmbr1 network - The post-up and post-down lines were copied from this guide - part of my trial and error effort ip a from Router VM: 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 2: ens18: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 2a:06:12:a9:18:98 brd ff:ff:ff:ff:ff:ff altname enp0s18 inet 192.168.1.175/24 metric 100 brd 192.168.1.255 scope global dynamic ens18 valid_lft 4270sec preferred_lft 4270sec inet6 fe80::2806:12ff:fea9:1898/64 scope link valid_lft forever preferred_lft forever 3: ens19: mtu 1500 qdisc fq_codel master br0 state UP group default qlen 1000 link/ether ca:bc:10:17:e0:2f brd ff:ff:ff:ff:ff:ff altname enp0s19 inet6 fe80::c8bc:10ff:fe17:e02f/64 scope link valid_lft forever preferred_lft forever 4: br0: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether da:56:23:09:09:72 brd ff:ff:ff:ff:ff:ff inet 192.168.2.1/24 brd 192.168.2.255 scope global br0 valid_lft forever preferred_lft forever inet6 fe80::d856:23ff:fe09:972/64 scope link valid_lft forever preferred_lft forever Content of /etc/network/interfaces in Router VM: auto lo iface lo inet loopback auto ens18 iface ens18 inet dhcp #auto ens19 #iface ens19 inet static # address 192.168.99.1 # netmask 255.255.255.0 IP forward config in Router VM: $ cat /etc/sysctl.conf | grep net.ipv4.ip_forward net.ipv4.ip_forward=1 Content of /etc/network/if-pre-up.d/iptables in Router VM: #!/bin/sh /sbin/iptables-restore < /etc/network/iptables Content of /etc/network/iptables in Router VM: *nat :PREROUTING ACCEPT [0:0] :INPUT ACCEPT [0:0] :OUTPUT ACCEPT [0:0] :POSTROUTING ACCEPT [0:0] # ens18 is WAN interface # br0 is LAN interface -A POSTROUTING -o ens18 -j MASQUERADE COMMIT *filter :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [0:0] # Service rules # basic global accept rules - ICMP, loopback, traceroute, established all accepted -A INPUT -s 127.0.0.0/8 -d 127.0.0.0/8 -i lo -j ACCEPT -A INPUT -p icmp -j ACCEPT -A INPUT -m state --state ESTABLISHED -j ACCEPT # enable traceroute rejections to get sent out -A INPUT -p udp -m udp --dport 33434:33523 -j REJECT --reject-with icmp-port-unreachable # DNS - accept from LAN -A INPUT -i br0 -p tcp --dport 53 -j ACCEPT -A INPUT -i br0 -p udp --dport 53 -j ACCEPT # DHCP client requests - accept from LAN -A INPUT -i br0 -p udp --dport 67:68 -j ACCEPT # SSH - accept from WAN -A INPUT -i ens18 -p tcp --dport 22 -j ACCEPT # drop all other inbound traffic -A INPUT -j DROP # Forwarding rules # forward packets along established/related connections -A FORWARD -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT # forward ICMP -A FORWARD -p icmp -j ACCEPT -A FORWARD -p icmp -s 0.0.0.0/0 -d 192.168.2.0/24 -j ACCEPT # forward from LAN (br0) to WAN (ens18) -A FORWARD -i br0 -o ens18 -j ACCEPT # drop all other forwarded traffic -A FORWARD -j DROP COMMIT Result of sudo iptables -S command in Router VM: -P INPUT ACCEPT -P FORWARD ACCEPT -P OUTPUT ACCEPT -A INPUT -s 127.0.0.0/8 -d 127.0.0.0/8 -i lo -j ACCEPT -A INPUT -p icmp -j ACCEPT -A INPUT -m state --state ESTABLISHED -j ACCEPT -A INPUT -p udp -m udp --dport 33434:33523 -j REJECT --reject-with icmp-port-unreachable -A INPUT -i br0 -p tcp -m tcp --dport 53 -j ACCEPT -A INPUT -i br0 -p udp -m udp --dport 53 -j ACCEPT -A INPUT -i br0 -p udp -m udp --dport 67:68 -j ACCEPT -A INPUT -i ens18 -p tcp -m tcp --dport 22 -j ACCEPT -A INPUT -j DROP -A FORWARD -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT -A FORWARD -p icmp -j ACCEPT -A FORWARD -d 192.168.2.0/24 -p icmp -j ACCEPT -A FORWARD -i br0 -o ens18 -j ACCEPT -A FORWARD -j DROP DHCP config in /etc/dhcp/dhcpd.conf in Router VM: subnet 192.168.2.0 netmask 255.255.255.0 { range 192.168.2.100 192.168.2.199; option routers 192.168.2.1; option domain-name-servers 192.168.2.1; option broadcast-address 192.168.2.255; host ubuntu-desktop { hardware ethernet 5A:5B:74:01:69:34; fixed-address 192.168.2.2; } } Note: ubuntu-desktop is VM 1 Questions: 1. How can I block VM 1 and VM 2 from accessing devices in my home network? TCP/UDP/ICMP and everything. 2. How can I access the VM 1 and VM 2 when I'm using laptop or desktop e.g. sending ping/ICMP request (ping 192.168.2.2/ping 192.168.2.101), access Nginx process running on port 80 (curl 192.168.2.2/curl 192.168.2.101) and SSH server process running on port 22 (ssh user@192.168.2.2/ssh user@192.168.2.101) on both VMs? I did some research about this and I got into DNAT/SNAT/Masquerade topic but I'm not sure if that's what I need. If yes, what the rules should look like? I'm new to this iptables topic. I tried rules below but I still can't ping to the VM 1 and VM 2 from my laptop. iptables -I FORWARD -s 192.168.1.0/24 -d 192.168.2.0/24 -j ACCEPT iptables -I FORWARD -s 192.168.2.0/24 -d 192.168.1.0/24 -m conntrack --ctstate ESTABLISHED -j ACCEPT iptables -t nat -I POSTROUTING -s 192.168.1.0/24 -d 192.168.2.0/24 -j SNAT --to 192.168.2.1

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?

# Prerequisites Alpine Linux Edge

~ $ podman --version
podman version 5.5.2
~ $ distrobox --version
distrobox: 1.8.1.2
~ $ mount|grep ^cgroup|awk '{print $1}'|uniq
cgroup2

I followed the steps in Alpine Wiki for setting up distrobox and podman for rootless usage. # What is happening The block bellow is the primary issue I'm running into.

~ $ distrobox create --name debox --image debian:latest
Creating 'debox' using image debian:latest	[ OK ]
Distrobox 'debox' successfully created.
To enter, run:

distrobox enter debox

~ $ distrobox enter debox
Error: unable to start container "409500222cb9ecfb488522e1d0a13046e68408fcb62a9dcfb52ae88bda0816c0": runc: runc create failed: unable to start container process: unable to apply cgroup configuration: rootless needs no limits + no cgrouppath when no permission is granted for cgroups: mkdir /sys/fs/cgroup/409500222cb9ecfb488522e1d0a13046e68408fcb62a9dcfb52ae88bda0816c0: permission denied: OCI permission denied

I've attempted to create the folder distrobox tries to create and give my user complete permissions to use it to no avail. The same error occurs. Launching this container with just podman will output the same error. Meanwhile, starting similar container with podman seamingly works.

~ $ distrobox rm debox
# output omitted
~ $ podman create --name debox -i debian:latest
62f2044c8bb7e86b4a78bd48e7f0c66c1071924a3bc65c0d49519ca399753d9c
~ $ podman start debox
debox

As indicated by podman stats the container is up and running:

ID            NAME        CPU %       MEM USAGE / LIMIT  MEM %       NET IO      BLOCK IO           PIDS        CPU TIME         AVG CPU %
62f2044c8bb7  debox       23.49%      0B / 7.182GB       0.00%       0B / 796B   2.876GB / 1.516GB  0           1h22m26.154492s  6227.30%

It starts with showing impossibly high CPU percentage hence, the high average CPU use. Probably, irrelevant to issue. After attaching to container there is no prompt. Detaching to exit via ctrl+p, ctrl+q is impossible. Attempting to stop container will force podman to resort to SIGKILL. Container will not appear in podman ps afterwords (it did before) but, still can be launched but, the same as above will repeat:

~ $ podman stop debox
WARN StopSignal SIGTERM failed to stop container debox in 10 seconds, resorting to SIGKILL 
debox
~ $ podman ps
CONTAINER ID  IMAGE       COMMAND     CREATED     STATUS      PORTS       NAMES
~ $ podman start debox
debox

# What I want Just distrobox enter debox and use container as intended.

I'm running **Proxmox VE 8.4.1**, and I’m experiencing a strange behavior with a **Debian 12 (Bookworm)** VM: the qemu-guest-agent is clearly active and responding, but when I try to shut down the VM via qm shutdown , it never completes. The VM remains stuck in the state:

running (shutdown)

Also, the qm agent ping command returns **no output at all**. --- ### ✅ Working behavior: - Guest has qemu-guest-agent installed and running - Device /dev/virtio-ports/org.qemu.guest_agent.0 exists inside the VM - Agent is enabled via agent: 1 in qm config - Commands like the following return valid JSON:

qm guest cmd  get-osinfo  
qm guest cmd  get-time  
qm guest cmd  get-users  
qm guest cmd  network-get-interfaces

--- ### ❌ Failing behavior: - qm agent ping → **no output, no error** Example:

root@host:~# qm agent 100 ping
root@host:~#

- qm shutdown → executes, but VM remains stuck in "running (shutdown)" state - Restarted host and guest multiple times, same result --- ### 🔧 Setup: **Guest VM (Debian 12):**

# cat /etc/os-release
Debian GNU/Linux 12 (bookworm)

# qemu-ga --version
QEMU Guest Agent 7.2.17 (but tried also with 10.0.0+ds-2~bpo12+2 installed via bookworm-backports and nothing changes)

# ls -l /dev/virtio-ports/
crw------- 1 root root ... org.qemu.guest_agent.0

**Host (Proxmox):**

# pveversion
pve-manager/8.4.1/2a5fa54a8503f96d (running kernel: 6.8.12-11-pve)

# apt show pve-qemu-kvm
Version: 9.2.0-6

--- ### 📜 Logs (from journalctl -xe on the host):

Jul 14 16:20:42 hostname pvedaemon: start VM 100: UPID:hostname:00000000:00000000:00000000:qmstart:100:root@pam:
Jul 14 16:20:42 hostname pvedaemon:  starting task UPID:hostname:00000000:00000000:00000000:qmstart:100:root@pam:
Jul 14 16:20:43 hostname pvedaemon: VM 100 started with PID 516522.
Jul 14 16:20:43 hostname pvedaemon:  end task UPID:hostname:00000000:00000000:00000000:qmstart:100:root@pam: OK
Jul 14 16:20:44 hostname pvedaemon:  starting task UPID:hostname:00000000:00000000:00000000:vncproxy:100:root@pam:
Jul 14 16:20:44 hostname pvedaemon: starting vnc proxy UPID:hostname:00000000:00000000:00000000:vncproxy:100:root@pam:
Jul 14 16:21:08 hostname pvedaemon:  starting task UPID:hostname:00000000:00000000:00000000:qmshutdown:100:root@pam:
Jul 14 16:21:08 hostname pvedaemon: shutdown VM 100: UPID:hostname:00000000:00000000:00000000:qmshutdown:100:root@pam:
Jul 14 16:21:32 hostname pvedaemon:  end task UPID:hostname:00000000:00000000:00000000:vncproxy:100:root@pam: OK
Jul 14 16:21:36 hostname pvedaemon: VM 100 qmp command failed - VM 100 qmp command 'guest-ping' failed - got timeout
Jul 14 16:21:55 hostname pvedaemon: VM 100 qmp command failed - VM 100 qmp command 'guest-ping' failed - got timeout
Jul 14 16:22:14 hostname pvedaemon: VM 100 qmp command failed - VM 100 qmp command 'guest-ping' failed - unable to connect to VM 100 qga socket - timeout after 31 retries

--- ### 🤔 My theory: Since all other guest cmd commands work fine, it seems that **Proxmox is expecting a response from guest-ping**, and when it doesn’t receive it (or receives an empty response), it **fails to confirm the VM shut down properly** — which leads to the stuck "running (shutdown)" state. --- ## ❓ Question: What could be causing guest-ping (used internally by qm agent ping and qm shutdown) to fail or timeout, even when other guest cmd commands succeed? - Is there something about how qemu-ga communicates that might explain why guest-ping isn't acknowledged? - Could this be a bug or mismatch between Proxmox 8.4 and the QEMU Guest Agent in debian, tried bot native 7.2.17 and backports v10? - Is there a proper workaround to allow clean qm shutdown detection without guest-ping? Any insights from people using similar versions (QEMU 9+, guest-agent 10+, Proxmox 8) would be very appreciated. Thanks! --- Some images: Dump of serial after adding the serial port to the vm before the shutdown and after pressing the shutdown button in GUI interface. root@proxmox:~# qm terminal 100 starting serial terminal on interface serial0 (press Ctrl+O to exit) [ 26.693132] reboot: Power down nothing happens on serial after this

I'm making my first steps in FreeBSD, so please excuse any possible "linuxism". My goal is to run FreeBSD 10.2 inside virtual machine with QEMU/KVM and allow USB3 network card passthrough from the host to make it the only available WAN interface. To start QEMU/KVM I run the following: kvm -m 4096 \ -snapshot \ -hda /path/to/the/image \ -device nec-usb-xhci,id=xhci,addr=0x5 \ -device usb-host,bus=xhci.0,vendorid=0x0b95,productid=0x1790 \ -net none This is running fine, if I'm trying to start Ubuntu 16.04. The interface is up, shows up in lsusb and the address is assigned by DHCP. I'm also able to run the very same FreeBSD image with VirtualBox: the card is recognised (as it's supported by FreeBSD) and I see: pciconf -lv #skipped xhci0@pci0:0:12:0: class=0x0c0330 card=0x00000000 chip=0x1e318086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = '7 Series/C210 Series Chipset Family USB xHCI Host Controller' class = serial bus subclass = USB When running QEMU monitor, info usb returns (no surprise) the same entry for the network card, both for Ubuntu and FreeBSD. The only way of adding XHCI controller in QEMU I found is to specify nec-usb-xhci, so far this is the only difference between VirtualBox and QEMU I see. Is there a way to make this USB3 passthrough to FreeBSD possible with QEMU?

I have created a bootable usb and created a virtual box raw disk with the following command- sudo VBoxManage internalcommands createrawvmdk -filename popliveusb.vmdk -rawdisk /dev/sdd1 But when I was adding raw disk to my virtual machine's storage, I was getting VERR_ACCESS_DENIED error. Then I followed this solution. I changed the owner using this command sudo chown eh54n:eh54n popliveusb.vmdk. Then added my user to disk group using this command sudo usermod -a -G disk $USER. But now I am getting **VERR_FILE_NOT_FOUND** error. This is the full error-

Failed to open the disk image file /home/eh54n/popliveusb.vmdk.

Could not find file for the medium '/home/eh54n/popliveusb.vmdk' (VERR_FILE_NOT_FOUND).

Result Code: VBOX_E_FILE_ERROR (0x80BB0004)
Component: MediumWrap
Interface: IMedium {ad47ad09-787b-44ab-b343-a082a3f2dfb1}
Callee: IVirtualBox {d0a0163f-e254-4e5b-a1f2-011cf991c38d}
Callee RC: VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)

When I run the VirtualBox using sudo, I don't have my VMs. How can I add the vmdk raw disk to my VM?

Are there any better alternative to chroot environment? I'm thinking about running nginx on a jailed environment. BTW, I'm on OpenVZ VPS, so modifying the Kernel is a no-no. (I think that prevents me from installing SELinux, AppArmor, etc.)

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'm working on an networking lab tool leveraging QEMU-based VM virtualization and docker technology to run VMs and containers respectively on a Linux host. The underlying lab connectivity is implemented by using linux bridges. I have a linux Ubuntu guest running inside a QEMU VM that features a virtio-net paravirualized interface with TAP backend. Such TAP interface is connected to a linux bridge's port on the host. root@eve-ng62-28:~# brctl show vnet0_3 bridge name bridge id STP enabled interfaces vnet0_3 8000.d63b1f37e4ba no vnet0_9_2 vunl0_3_3 vunl0_7_0 vunl0_9_2 root@eve-ng62-28:~# root@eve-ng62-28:~# ethtool -i vunl0_7_0 driver: tun version: 1.6 firmware-version: expansion-rom-version: bus-info: tap supports-statistics: no supports-test: no supports-eeprom-access: no supports-register-dump: no supports-priv-flags: no root@eve-ng62-28:~# I'm using Linux ftrace via trace-cmd frontend to dig into some details, see also https://unix.stackexchange.com/questions/797717/tcp-checksum-offloading-on-virtio-net-paravirtualized-interfaces root@eve-ng62-28:~# trace-cmd start -e net:netif_receive_skb_entry -f "name == 'vunl0_7_0'" root@eve-ng62-28:~# root@eve-ng62-28:~# trace-cmd show # tracer: nop # # entries-in-buffer/entries-written: 1/1 #P:48 # # _-----=> irqs-off/BH-disabled # / _----=> need-resched # | / _---=> hardirq/softirq # || / _--=> preempt-depth # ||| / _-=> migrate-disable # |||| / delay # TASK-PID CPU# ||||| TIMESTAMP FUNCTION # | | | ||||| | | qemu-system-x86-600348 b.... 66505.777999: netif_receive_skb_entry: dev=vunl0_7_0 napi_id=0x0 queue_mapping=1 skbaddr=0000000006a1cc35 vlan_tagged=0 vlan_proto=0x0000 vlan_tci=0x0000 protocol=0x0800 ip_summed=3 hash=0x00000000 l4_hash=0 len=60 data_len=0 truesize=768 mac_header_valid=1 mac_header=-14 nr_frags=0 gso_size=0 gso_type=0x0 As you can see, linux guest sends outgoing TCP packets to the virtio-net network interface setting CHECKSUM_PARTIAL(3) tag in the ip_summed field within sk_buff struct. My question is related to the TASK-PID field shown by trace-cmd show. 600348 is the PID of the qemu-system-x86_64 process's instance associated to the VM. As required I edit this to provide the question: is the TASK-PID shown the PID or TID of the process/thread that is the context the TAP driver runs into ?

After install the program and execute vmPlayer request the kernel headers to recompile it (I guess), after that vmP install the virtual network device, at this point show an error. and the vmware-15092.log file is: 2015-03-27T22:51:28.154-06:00| vthread-4| I120: Preprocessed UTS_RELEASE, got value "3.19.1-201.fc21.x86_64". 2015-03-27T22:51:28.154-06:00| vthread-4| I120: The header path "/lib/modules/3.19.1-201.fc21.x86_64/build/include" for the kernel "3.19.1-201.fc21.x86_64" is valid. Whoohoo! 2015-03-27T22:51:28.158-06:00| vthread-4| I120: The GCC version matches the kernel GCC minor version like a glove. 2015-03-27T22:51:28.158-06:00| vthread-4| I120: Validating path "/lib/modules/3.19.1-201.fc21.x86_64/build/include" for kernel release "3.19.1-201.fc21.x86_64". 2015-03-27T22:51:28.158-06:00| vthread-4| I120: Failed to find /lib/modules/3.19.1-201.fc21.x86_64/build/include/linux/version.h 2015-03-27T22:51:28.158-06:00| vthread-4| I120: /lib/modules/3.19.1-201.fc21.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead. 2015-03-27T22:51:28.158-06:00| vthread-4| I120: using /usr/bin/gcc for preprocess check 2015-03-27T22:51:28.164-06:00| vthread-4| I120: Preprocessed UTS_RELEASE, got value "3.19.1-201.fc21.x86_64". 2015-03-27T22:51:28.164-06:00| vthread-4| I120: The header path "/lib/modules/3.19.1-201.fc21.x86_64/build/include" for the kernel "3.19.1-201.fc21.x86_64" is valid. Whoohoo! 2015-03-27T22:51:28.164-06:00| vthread-4| I120: Using temp dir "/tmp". 2015-03-27T22:51:28.165-06:00| vthread-4| I120: Obtaining info using the running kernel. 2015-03-27T22:51:28.165-06:00| vthread-4| I120: Setting header path for 3.19.1-201.fc21.x86_64 to "/lib/modules/3.19.1-201.fc21.x86_64/build/include". 2015-03-27T22:51:28.165-06:00| vthread-4| I120: Validating path "/lib/modules/3.19.1-201.fc21.x86_64/build/include" for kernel release "3.19.1-201.fc21.x86_64". 2015-03-27T22:51:28.165-06:00| vthread-4| I120: Failed to find /lib/modules/3.19.1-201.fc21.x86_64/build/include/linux/version.h 2015-03-27T22:51:28.165-06:00| vthread-4| I120: /lib/modules/3.19.1-201.fc21.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead. 2015-03-27T22:51:28.165-06:00| vthread-4| I120: using /usr/bin/gcc for preprocess check 2015-03-27T22:51:28.171-06:00| vthread-4| I120: Preprocessed UTS_RELEASE, got value "3.19.1-201.fc21.x86_64". 2015-03-27T22:51:28.171-06:00| vthread-4| I120: The header path "/lib/modules/3.19.1-201.fc21.x86_64/build/include" for the kernel "3.19.1-201.fc21.x86_64" is valid. Whoohoo! 2015-03-27T22:51:28.288-06:00| vthread-4| I120: found symbol version file /lib/modules/3.19.1-201.fc21.x86_64/build/Module.symvers 2015-03-27T22:51:28.288-06:00| vthread-4| I120: Reading symbol versions from /lib/modules/3.19.1-201.fc21.x86_64/build/Module.symvers. 2015-03-27T22:51:28.302-06:00| vthread-4| I120: Read 15286 symbol versions 2015-03-27T22:51:28.302-06:00| vthread-4| I120: Invoking modinfo on "vmnet". 2015-03-27T22:51:28.304-06:00| vthread-4| I120: "/sbin/modinfo" exited with status 256. 2015-03-27T22:51:28.381-06:00| vthread-4| I120: Setting destination path for vmnet to "/lib/modules/3.19.1-201.fc21.x86_64/misc/vmnet.ko". 2015-03-27T22:51:28.381-06:00| vthread-4| I120: Extracting the vmnet source from "/usr/lib/vmware/modules/source/vmnet.tar". 2015-03-27T22:51:28.385-06:00| vthread-4| I120: Successfully extracted the vmnet source. 2015-03-27T22:51:28.385-06:00| vthread-4| I120: Building module with command "/usr/bin/make -j4 -C /tmp/modconfig-3fL25O/vmnet-only auto-build HEADER_DIR=/lib/modules/3.19.1-201.fc21.x86_64/build/include CC=/usr/bin/gcc IS_GCC_3=no" 2015-03-27T22:51:29.709-06:00| vthread-4| W110: Failed to build vmnet. Failed to execute the build command. Now I don't know what to do, any idea?

My question may be weird. I want to know if there is some virtual machine that lets me install Windows 7 under Linux and lets Windows use, as a virtual device, the same device that is really installed in my physical PC. I need to do that, because of a lot of Adobe software that I need for work and I can't switch to other software (even if I'd like to). Maybe what I need could be something even simpler, like letting the virtual machine see the graphics card I have to get the full compatibility with the Adobe software and the OpenGL and DirectX drivers. Actually I use VirtualBox to run Windows, and Fedora is my main OS. The hardware that I need to share is as follows: ⠀CPU - Intel Core i7 990x (even only a subset of all the cores) ⠀GPU - Nvidia Quadro 2000

I want to test and debug linux kernel internals within the bluetooth stack, i.e. /net/bluetooth. I have a (rather minimal) kernel, manually built, with debug symbols, and a busybox at the moment, running in qemu. Now I want to investigate specific bluetooth functions from the kernel. I thought, a virtual device would be easiest but it seems harder than expected. I found there is btvirt from bluez for dealing with virtual bluetooth devices. I have tried manually building bluez statically. Doesn't work, btvirt is still (at least partly) dynamically linked (and hence doesn't work in my vm):

# in bluez repo
autoreconf -vfi
./configure --enable-static --enable-debug --enable-test --enable-testing --enable-deprecated --enable-experimental --enable-logger CFLAGS=-static LDFLAGS=-static
make
ldd emulator/btvirt  # output below
	linux-vdso.so.1 (0x00007f7225f23000)
	libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f7225cf5000)
	/lib64/ld-linux-x86-64.so.2 (0x00007f7225f25000)

Also, I tried clang instead of gcc, without success. musl-gcc yielded some error about readline when trying to ./configure I have not followed further yet. What options do I have/which route would be the easiest? 1. Should I abandon my minimal kernel and use a full debian/ubuntu instead? I need debugging symbols and might want to pin to specific versions, so I guess, I would have to manually build the debian/ubuntu kernel (i.e. in accordance with some minimum build flags these distros need/expect), right? 2. How much work is it/should I try to expand my custom small setup with libc, linker etc? 3. Am I on the right track at all? I assume(d) that kernel bluetooth developers might use virtual devices. (Am I correct on that one? If people have experience here, I'd be curious.) Or is this rather hopeless and should I try to pass-through a USB bluetooth device instead? Thanks in advance, I'll be happy to provide further info if needed.

I want to get virtual machine in a TTY (VT*) in fullscreen like GDM3 can take a TTY (VT*) for the graphic part of linux I want DISPLAY (heard as the output of a graphic server, here the VMs) to be redirected in a TTY (VT*), and not in a window like usually It will make like the computer run multiple OS at the same time but in fact it's a Linux Kernel who virtualize the differents OS that we can see on the different TTY (VT*) You know, the TTY (VT*) in CTRL + ALT + Fi ---------- Okay ---------- Not okay

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 have a Ubuntu VM on VirtualBox running in headless mode. Host is a Windows 10 machine. I want to be able to render Ubuntu's applications on Windows using XServer. Currently, I tried this: - Installed X410 XServer on Windows. - ssh into Virtual Machine with a -X option so that X forwarding is enabled. - If I run a graphical application from command line now, it complains that cannot connect XServer. My DISPLAY env variable is localhost:10.0. Below is error I get on launching the graphical application: connect /tmp/.X11-unix/X0: No such file or directory Unable to init server: Could not connect: Connection refused Failed to parse arguments: Cannot open display:

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.