- Users - libvirt List Archives

Read-only iscsi disk? Or hot-plug?
by Paul van der Vlis 07 Sep '20

07 Sep '20

Hello, I have an iSCSI disk with a backup. I want to use that backup on another machine to test putting back data. What I use now is this: ---- <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='directsync' io='native'/> <source dev='/dev/disk/by-id/scsi-36e843b6afdddf65dc4e9d4dc2dab66de'/> <target dev='vdh' bus='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x0c' function='0x0'/> </disk> ---- Is it possible to do this read-only? What I also could do is to hot-unplug the disk at the production machine, and then hot-plug it at the test-machine. But the machines are Windows, and I don't know Windows well. With regards, Paul -- Paul van der Vlis Linux systeembeheer Groningen https://www.vandervlis.nl/

2 2

debian 10, vm cant connect to the host bridge
by Schuldei, Andreas 07 Sep '20

07 Sep '20

This is my system info: Debian Release: 10.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.4.60-1-pve (SMP w/16 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Libvirt version 5.0.0 qemu Version: 1:3.1+dfsg-8+deb10u7 I try to get the filtering bridge to work. This is the host, with the br0 that is connected to a trunked port ================================ ip a 1: lo: <LOOPBACK,UP,LOWER_UP> 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: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 34:48:ed:f0:a9:e8 brd ff:ff:ff:ff:ff:ff inet 10.12.0.13/24 brd 10.12.0.255 scope global eno1 valid_lft forever preferred_lft forever inet6 fe80::3648:edff:fef0:a9e8/64 scope link valid_lft forever preferred_lft forever 3: eno2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master br0 state UP group default qlen 1000 link/ether 34:48:ed:f0:a9:e9 brd ff:ff:ff:ff:ff:ff inet6 fe80::3648:edff:fef0:a9e9/64 scope link valid_lft forever preferred_lft forever 4: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether e6:67:7b:87:b5:ca brd ff:ff:ff:ff:ff:ff inet6 fe80::e467:7bff:fe87:b5ca/64 scope link valid_lft forever preferred_lft forever 5: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether 52:54:00:2b:e3:f7 brd ff:ff:ff:ff:ff:ff inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0 valid_lft forever preferred_lft forever 6: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast master virbr0 state DOWN group default qlen 1000 link/ether 52:54:00:2b:e3:f7 brd ff:ff:ff:ff:ff:ff 19: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master br0 state UNKNOWN group default qlen 1000 link/ether fe:54:00:fc:ea:e6 brd ff:ff:ff:ff:ff:ff inet6 fe80::fc54:ff:fefc:eae6/64 scope link valid_lft forever preferred_lft forever =================== bridge vlan show port vlan ids eno2 4 7 221 800 br0 None virbr0 1 PVID Egress Untagged virbr0-nic 1 PVID Egress Untagged vnet0 800 ================== however the mac does not show up when i do ================== brctl showmacs br0 ================== so vnet0 does not yet communicate with the bridge inside the vm: ============================= ip a 1: lo: <LOOPBACK,UP,LOWER_UP> 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: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 52:54:00:fc:ea:e6 brd ff:ff:ff:ff:ff:ff inet 195.37.235.121/26 brd 195.37.235.127 scope global enp1s0 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:fefc:eae6/64 scope link valid_lft forever preferred_lft forever =============================== and =========== ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. >From 195.37.235.121 icmp_seq=1 Destination Host Unreachable >From 195.37.235.121 icmp_seq=2 Destination Host Unreachable ============== The mac address of vnet0 and enp1s0 is the same. That means they are the same entity. yay! The XML describing the network part of the VM is here: ===================== <interface type='bridge'> <mac address='52:54:00:29:b6:e0'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> ======================= what could be the problem?

2 3

Error With Xeon 2678 in virt-manager
by John Bajer 06 Sep '20

06 Sep '20

Hello, I have to select Ivy Bridge since I have Xeon 2678 but I cannot find it on the drop-down menu in virt-manager. When I select copy host cpu configuration it changes it to EPYC as soon as I click the start button. I have Manjaro on my computer. How to solve this problem? Thanks! *John Washington Bajer* *El Ciclista de la Triste Figura*

1 0

printing the qemu final execution line from an xml
by daggs 04 Sep '20

04 Sep '20

Greetings, I have a qemu line which I want to convert ot libvirt xml but as domxml-from-native is deprecated, I want to try it the other way around. e.g. write an libvirt xml and dump the final qemu line without running it. is there a way to do so? Thanks, Dagg.

2 2

usb-hdmi-cec-adapter usb pass-through experiences
by daggs 03 Sep '20

03 Sep '20

Greetings, I need to get a device like this: https://www.pulse-eight.com/p/104/usb-hdmi-cec-adapter I have usb pass-through experiences with some usb devices such as dtv, wireless network, thumbsticks and wireless keyboards. I know there isn't much to be done in usb pass-through but I did had issues with the former two, now I'm using a wireless network without and issues. I wanted to know if someone has tried using this device as pass-through into a vm and can share his thoughts. Thanks, Dagg.

2 2

libvirt 6.7 meson.build error
by Chen Wenwei 03 Sep '20

03 Sep '20

Found pkg-config: /usr/local/bin/pkg-config (0.29.2) Did not find CMake 'cmake' Found CMake: NO Run-time dependency libapparmor found: NO (tried pkgconfig and cmake) Library attr found: YES Library audit found: YES Run-time dependency bash-completion found: YES 2.1 Run-time dependency blkid found: NO (tried pkgconfig and cmake) Library cap-ng found: YES Run-time dependency libcurl found: NO (tried pkgconfig and cmake) Run-time dependency dbus-1 found: NO (tried pkgconfig and cmake) Run-time dependency devmapper found: NO (tried pkgconfig and cmake) Library devmapper found: YES meson.build:1048:19: ERROR: Unknown variable "tmp". A full log can be found at /home/libvirt-6.7.0/build/meson-logs/meson-log.txt [root@localhost libvirt-6.7.0]#

2 1

bridge + SR-IOV guests with KVM
by Philipp Rosenberger 02 Sep '20

02 Sep '20

Hi, I managed to get SR-IOV with an Intel I350 NIC to work.For this I followed the documentation on this page: https://wiki.libvirt.org/page/Networking#Assignment_from_a_pool_of_SRIOV_VF… But as I have more VMs then VF on the NIC I also have a bridge wich serves the other guests. As I run Debian Buster as host I followed the documentation here: https://wiki.libvirt.org/page/Networking#Debian.2FUbuntu_Bridging If I use only the SRIOV everything works as expected. All guests can be reached for the network and the guests and host can reach each other. The same goes for a sole bridged environment. As I dived into the issue I found an answer form the intel community: https://community.intel.com/t5/Ethernet-Products/82599-VF-to-Linux-host-bri… It says I need to add the "VF mac addresses and eth0 mac address to bridge forwarding database". I have done this with the following command: bridge fdb add 52:54:00:3c:1c:e6 dev eth_lan0 The mac address is from my VM which is on the bridge. And the eth_lan0 interface is the physical interface of my bridge and also the PF of my I350 NIC. This seems to work. But doing this manually is annoying and a bit of a hassle when creating new VMs on the bridge. I there a way to let libvirt do this work? Best regards Philipp PS: This presentation shows it pretty well on page 33: https://events.static.linuxfound.org/sites/events/files/slides/LinuxConJapa…

2 1

Meson build
by Toolybird 01 Sep '20

01 Sep '20

Hi, Just a heads up on my experiences with the new build system. Arch Linux meson-0.55.1 Overall, it looks good, so well done! Just a couple of minor things I noted: 1. Arch uses a meson wrapper script (arch-meson) that sets: --buildtype plain This seems to trigger a bug in meson that results in copious bogus compiler warnings: cc1: warning: ‘-Wformat-y2k’ ignored without ‘-Wformat’ [-Wformat-y2k] cc1: warning: ‘-Wformat-extra-args’ ignored without ‘-Wformat’ [-Wformat-extra-args] cc1: warning: ‘-Wformat-zero-length’ ignored without ‘-Wformat’ [-Wformat-zero-length] cc1: warning: ‘-Wformat-contains-nul’ ignored without ‘-Wformat’ [-Wformat-contains-nul] cc1: warning: ‘-Wformat-security’ ignored without ‘-Wformat’ [-Wformat-security] which of course breaks -Werror builds. I can easily work around it by setting `-D git_werror=disabled' or even better still: CFLAGS+=" -Wall" arch-meson... Maybe this github issue is related?: https://github.com/mesonbuild/meson/issues/7399 2. Arch currently builds libvirt with support for ZFS. Seeing as ZFS is not in the distro proper, a simple Autoconf tweak is used: ZFS=/usr/bin/zfs ZPOOL=/usr/bin/zpool \ ./configure ... This is surprisingly hard to emulate with meson, in fact it appears impossible, unless I resort to dodgy hacks with sed etc. Cheers

6 10

I want to unsubscribe
by Bilal Arif 31 Aug '20

31 Aug '20

Block360 PVT Limited NSTP, Islamabad, Pakistan. Whatsapp/Mobile: +923457343638 Web: www.block360.io

2 1

Re: plug pre-created tap devices to libvirt guests
by Marcus 30 Aug '20

30 Aug '20

> On Tue, Jun 30, 2020 at 04:02:05PM +0100, Daniel P. Berrangé wrote: > > On Tue, Jun 30, 2020 at 12:59:03PM +0200, Miguel Duarte de Mora Barroso wrote: > > > On Mon, Apr 6, 2020 at 4:03 PM Laine Stump <lstump redhat com> wrote: > > > > > > > > On 4/6/20 9:54 AM, Daniel P. Berrangé wrote: > > > > > On Mon, Apr 06, 2020 at 03:47:01PM +0200, Miguel Duarte de Mora Barroso wrote: > > > > >> Hi all, > > > > >> > > > > >> I'm aware that it is possible to plug pre-created macvtap devices to > > > > >> libvirt guests - tracked in RFE [0]. > > > > >> > > > > >> My interpretation of the wording in [1] and [2] is that it is also > > > > >> possible to plug pre-created tap devices into libvirt guests - that > > > > >> would be a requirement to allow kubevirt to run with less capabilities > > > > >> in the pods that encapsulate the VMs. > > > > >> > > > > >> I took a look at the libvirt code ([3] & [4]), and, from my limited > > > > >> understanding, I got the impression that plugging existing interfaces > > > > >> via `managed='no' ` is only possible for macvtap interfaces. > > > > > > > > > > > > No, it works for standard tap devices as well. > > > > > > > > > > > > The reason the BZs and commit logs talk mostly about macvtap rather than > > > > tap is because 1) that's what kubevirt people had asked for and 2) it > > > > already *mostly* worked for tap devices, so most of the work was related > > > > to macvtap (my memory is already fuzzy, but I think there were a couple > > > > privileged operations we still tried to do for standard tap devices even > > > > if they were precreated (standard disclaimer: I often misremember, so > > > > this memory could be wrong! But definitely precreated tap devices do work). > > > > > > > > > > It's been a while since I've started this thread, but lately I've > > > understood better how tap devices work, and that new insight makes me > > > wonder about a couple of things. > > > > > > Our ultimate goal In kubevirt is to consume a pre-created tap device > > > by a kubernetes pod that doesn't have the NET_ADMIN capability. > > > > > > After looking at the current libvirt code, I don't think that is > > > currently supported, since we'll *always* enter the > > > `virNetDevTapCreate` function in [1] (I'm interested in the *tap* > > > scenario). > > > > > > The tap device is effectively created in that function - [2] - by > > > opening the clone device (/dev/net/tun), and calling `ioctl(fd, > > > TUNSETIFF,...)` in it. AFAIK, both of those operations *require* the > > > NET_ADMIN capability. If I'm correct, this means that the current > > > libvirt implementation makes our goals impossible to achieve. > > > > AFAIK, that is not correct - CAP_NET_ADMIN isn't required to open > > or create a tap device - only to add the tap device to a bridge. > > > > So if you create the tap device & attach it to a bridge ahead of > > time, libvirt should then be able to open it and give it to QEMU > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/dri… > > ((uid_valid(tun->owner) && !uid_eq(cred->euid, tun->owner)) || > (gid_valid(tun->group) && !in_egroup_p(tun->group))) && > !ns_capable(net->user_ns, CAP_NET_ADMIN); > > > This is called by the TUNSETIFF code. > > AFAICT, that means if you fchown(tapfd, uid, gid), to the uid+gid of > libvirtd, it should not require CAP_NET_ADMIN. > > Regards, > Daniel I have no idea if this message will get linked into the thread properly, but I came across this and wanted to comment on the mystery without having an actual email to reply to or headers. I recently ran into this issue as well, and found that even *with* NET_ADMIN at the container level, trying to launch Qemu directly results in: qemu-system-x86_64: -netdev tap,id=hostnet0,ifname=tap0: could not configure /dev/net/tun (tap0): Permission denied So as a note I'd say even Libvirt aside, Qemu is trying to do this as well: https://github.com/qemu/qemu/blob/0982a56a551556c704dc15752dabf57b4be1c640/… But it's unclear where the EPERM is coming from in the kernel at tun_set_iff(). Of note, if I give Qemu a non-existing tap name, it will create it, but if I give it an existing tap name, I get EPERM.

1 1

Distinguishing between host and guest initiated VM shutdown
by Milan Zamazal 27 Aug '20

27 Aug '20

Hi, we have a problem in oVirt that highly available VMs don't restart after host poweroff because Vdsm identifies the case as a user initiated shutdown (https://bugzilla.redhat.com/1800966) When poweroff is run on the host, libvirt-guests service takes an action. `virsh shutdown' is run on the VM, the guest OS is shut down cleanly and libvirt reports a shutdown event with VIR_DOMAIN_EVENT_SHUTDOWN_GUEST detail. Although it is a host initiated shutdown actually. Does libvirt provide any means to distinguish this case from a regular user shutdown? Thanks, Milan

3 4

support for live migration with PCI passthrough devices
by Henry lol 26 Aug '20

26 Aug '20

Hi guys, I'm wondering whether libvirt supports live migration for the VM with PCI passthrough devices. or it must be assumed before live migration that all passthrough devices be unplugged? If so, all unplugged devices should be manually hot-plugged to the VM after migration?? Thanks.

4 4

python-libvirt domain.destroy() doesn't appear to be working for me
by Jeremy Markle 24 Aug '20

24 Aug '20

I'm using the python-libvirt library and finding that I cannot get .destroy() or .shutdown() to work. https://github.com/simora/docker-libvirt-flask/blob/cba6041b47bdf4ccb3b9506… That is the line in my code. .create() works fine and using virsh in the docker container works fine to destroy the domain as well. This is based on ubuntu bionic in a docker container with the libvirt socket and such made available. .create() works, listing works and virsh works so permissions are not the issue. I'm confident I have failed to properly use the function or am missing the appropriate logging. Any assistance would be greatly appreciated.

3 5

couple of questions
by Vjaceslavs Klimovs 24 Aug '20

24 Aug '20

Hey folks, I've been experimenting with native NBD live migration w/ TLS and have a couple of questions. 1) It appears that in some cases modified default_tls_x509_cert_dir from qemu.conf is not respected, seems like virsh always expects a default location and does not check default_tls_x509_cert_dir: virsh # migrate vm1 qemu+tls://ratchet.lan/system --live --persistent --undefinesource --copy-storage-all --verbose --tls error: internal error: unable to execute QEMU command 'object-add': Unable to access credentials /etc/pki/qemu/ca-cert.pem: No such file or directory It's checking /etc/pki and not the location specified in default_tls_x509_cert_dir. Is this a bug or am I missing something? 2) QEMU has -object tls-cipher-suites, but there does not seem to be a way to specify TLS priority in libvirt's qemu conf. Solvable via compile time --tls-priority flag, but that's not very convenient. Is there a way to set TLS priority for QEMU TLS connections from libvirt configs? This would be equivalent to libvirtd.conf's tls_priority setting, but for QEMU, not for libvirt's own connections. 3) After setting up default_tls_x509_cert_dir and default_tls_x509_verify = 1 (and directories as required see 1), virsh initiated migrations with --tls flag succeed and captures show that it's using TLS. However, they equally succeed without the flag. Is there a way to ensure that only TLS communication is permitted between QEMUs? I tried nbd_tls, but that did not seem to have any effect. Thanks a lot for your help!

2 2

unable to migrate non shared storage in tunneled mode
by Vjaceslavs Klimovs 24 Aug '20

24 Aug '20

Hey all, With libvirt 6.5.0 and qemu 5.1.0 migration of non shared disks in tunneled mode does not work for me: virsh # migrate alpinelinux3.8 qemu+tls://ratchet.lan/system --live --persistent --undefinesource --copy-storage-all --tunneled --p2p error: internal error: qemu unexpectedly closed the monitor: Receiving block device images Error unknown block device 2020-08-15T21:21:48.995016Z qemu-system-x86_64: error while loading state section id 1(block) 2020-08-15T21:21:48.995193Z qemu-system-x86_64: load of migration failed: Invalid argument This is both with UEFI and BIOS guests. I understand that newer ways of migrating non shared disks is via NBD directly with QEMU, however I am certain that this used to work before libvirt 6.0. There is a series of commits to /src/qemu/qemu_migration.c on Dec 8, 2019, could they have something to do with this? Is migration of non shared disks supported and supposed to work in tunneled mode or is it not a supported configuration and native NBD directly with QEMU should be used in all cases? Thanks in advance! Full qemu log on receiving host: 2020-08-15 21:23:38.917+0000: starting up libvirt version: 6.5.0, qemu version: 5.1.0, kernel: 5.4.57-gentoo, hostname: ratchet.lan LC_ALL=C \ PATH=/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin:/opt/bin \ HOME=/var/lib/libvirt/qemu/domain-4-alpinelinux3.8 \ USER=root \ XDG_DATA_HOME=/var/lib/libvirt/qemu/domain-4-alpinelinux3.8/.local/share \ XDG_CACHE_HOME=/var/lib/libvirt/qemu/domain-4-alpinelinux3.8/.cache \ XDG_CONFIG_HOME=/var/lib/libvirt/qemu/domain-4-alpinelinux3.8/.config \ QEMU_AUDIO_DRV=none \ /usr/bin/qemu-system-x86_64 \ -name guest=alpinelinux3.8,debug-threads=on \ -S \ -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-4-alpinelinux3.8/master-key.aes \ -blockdev '{"driver":"file","filename":"/var/lib/libvirt/uefi/OVMF_CODE.fd","node-name":"libvirt-pflash0-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-pflash0-format","read-only":true,"driver":"raw","file":"libvirt-pflash0-storage"}' \ -blockdev '{"driver":"file","filename":"/var/lib/libvirt/qemu/nvram/alpinelinux3.8_VARS.fd","node-name":"libvirt-pflash1-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-pflash1-format","read-only":false,"driver":"raw","file":"libvirt-pflash1-storage"}' \ -machine pc-q35-5.1,accel=kvm,usb=off,dump-guest-core=off,pflash0=libvirt-pflash0-format,pflash1=libvirt-pflash1-format \ -cpu kvm64,ibpb=on,md-clear=on,spec-ctrl=on,ssbd=on,vme=on,x2apic=on,hypervisor=on \ -m 2048 \ -overcommit mem-lock=off \ -smp 2,sockets=2,cores=1,threads=1 \ -uuid 95286971-32fa-4138-be0e-519ec21af800 \ -no-user-config \ -nodefaults \ -chardev socket,id=charmonitor,fd=35,server,nowait \ -mon chardev=charmonitor,id=monitor,mode=control \ -rtc base=utc,driftfix=slew \ -global kvm-pit.lost_tick_policy=delay \ -no-hpet \ -no-shutdown \ -global ICH9-LPC.disable_s3=1 \ -global ICH9-LPC.disable_s4=1 \ -boot strict=on \ -device pcie-root-port,port=0x10,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x2 \ -device pcie-root-port,port=0x11,chassis=2,id=pci.2,bus=pcie.0,addr=0x2.0x1 \ -device pcie-root-port,port=0x12,chassis=3,id=pci.3,bus=pcie.0,addr=0x2.0x2 \ -device pcie-root-port,port=0x13,chassis=4,id=pci.4,bus=pcie.0,addr=0x2.0x3 \ -device qemu-xhci,p2=15,p3=15,id=usb,bus=pci.1,addr=0x0 \ -blockdev '{"driver":"host_device","filename":"/dev/vg0/test","aio":"native","node-name":"libvirt-2-storage","cache":{"direct":true,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-2-format","read-only":false,"cache":{"direct":true,"no-flush":false},"driver":"raw","file":"libvirt-2-storage"}' \ -device virtio-blk-pci,bus=pci.2,addr=0x0,drive=libvirt-2-format,id=virtio-disk0,bootindex=1,write-cache=on \ -device ide-cd,bus=ide.0,id=sata0-0-0 \ -chardev pty,id=charserial0 \ -device isa-serial,chardev=charserial0,id=serial0 \ -vnc 127.0.0.1:2 \ -device VGA,id=video0,vgamem_mb=16,bus=pcie.0,addr=0x1 \ -incoming defer \ -device virtio-balloon-pci,id=balloon0,bus=pci.3,addr=0x0 \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on char device redirected to /dev/pts/5 (label charserial0) Receiving block device images Error unknown block device 2020-08-15T21:23:39.278287Z qemu-system-x86_64: error while loading state section id 1(block) 2020-08-15T21:23:39.278422Z qemu-system-x86_64: load of migration failed: Invalid argument 2020-08-15 21:23:39.344+0000: shutting down, reason=failed

2 3

Conflicting parameters on qemu call
by Jan Walzer 21 Aug '20

21 Aug '20

Hi Lists, I currently have the issue of wanting to use emu-system-x86_64 on a ppc64le platform. It is imperative to pass the "-accel tcg,thread=multi” parameter to qemu when starting an instance, as without that, it will only use one thread and hence of limited/no use. The problem is, that libvirt itself, passes “-machine q35,accel=tcg” to qemu, which is a different parameter, that conflicts with the other one. Can we discuss, if I either have overlooked something, or is there a workaround, or is this a bug? I’m running: # uname -a Linux tiger-v4 5.7.0-1-powerpc64le #1 SMP Debian 5.7.6-1 (2020-06-24) ppc64le GNU/Linux # apt-cache policy libvirt-daemon libvirt-daemon: Installed: 6.5.0-1 Candidate: 6.5.0-1 Version table: *** 6.5.0-1 500 500 http://deb.debian.org/debian testing/main ppc64el Packages # apt-cache policy qemu-system-x86 qemu-system-x86: Installed: 1:5.0-14 Candidate: 1:5.0-14 Version table: *** 1:5.0-14 500 500 http://deb.debian.org/debian testing/main ppc64el Packages Do you need any more information? Feel free to only continue on the list that matters. Greetings, Jan

2 8

multiple vms with same PCI passthrough
by Daniel Black 18 Aug '20

18 Aug '20

In attempting to isolate vfio-pci problems between two different guest instances, the creation of a second guest (with existing guest shutdown) resulted in:. Aug 09 12:43:23 grit libvirtd[6716]: internal error: Device 0000:01:00.3 is already in use Aug 09 12:43:23 grit libvirtd[6716]: internal error: Device 0000:01:00.3 is already in use Aug 09 12:43:23 grit libvirtd[6716]: Failed to allocate PCI device list: internal error: Device 0000:01:00.3 is already in use Compiled against library: libvirt 6.1.0 Using library: libvirt 6.1.0 Using API: QEMU 6.1.0 Running hypervisor: QEMU 4.2.1 (fc32 default install) The upstream code seems also to test definitions rather than active uses of the PCI device. My potentially naive patch to correct this (but not the failing test cases) would be: diff --git a/src/util/virpci.c b/src/util/virpci.c index 47c671daa0..a00c5e6f44 100644 --- a/src/util/virpci.c +++ b/src/util/virpci.c @@ -1597,7 +1597,7 @@ int virPCIDeviceListAdd(virPCIDeviceListPtr list, virPCIDevicePtr dev) { - if (virPCIDeviceListFind(list, dev)) { + if (virPCIDeviceBusContainsActiveDevices(dev, list)) { virReportError(VIR_ERR_INTERNAL_ERROR, _("Device %s is already in use"), dev->name); return -1; Is this too simplistic or undesirable a feature request/implementation? I'd be more than grateful if someone carries this through as I'm unsure when I may get time for this.

2 5

KVM guest VM IP address
by Kaushal Shriyan 18 Aug '20

18 Aug '20

Hi, I am trying to find out the IP address of the KVM guest virtual machine. #virsh dumpxml newsoftlinedrupalpoc | grep "mac address" | awk -F\' '{ print $2}' 52:54:00:2c:7e:ff [root@baseserver1 ~]# arp -an | grep 52:54:00:2c:7e:ff [root@baseserver1 ~]# virsh domifaddr newsoftlinedrupalpoc Name MAC address Protocol Address ------------------------------------------------------------------------------- [root@baseserver1 ~]# It is not showing anything. I manually configure the IP using /etc/sysconfig/network-scripts/ifcfg-eth0 ONBOOT=yes IPADDR=192.168.0.189 PREFIX=24 GATEWAY=192.168.0.10 DNS1=8.8.8.8 DNS2=8.8.4.4 CentOS Linux release 7.6.1810 (Core) virt-install --version 1.5.0 virsh version Compiled against library: libvirt 4.5.0 Using library: libvirt 4.5.0 Using API: QEMU 4.5.0 Running hypervisor: QEMU 1.5.3 Am I missing something? Thanks in advance and I look forward to hearing from you. Best Regards,

2 1

ipv6 NAT; accept_ra errors and about network choice
by Ian Wienand 18 Aug '20

18 Aug '20

Hello, Firstly THANK YOU for the IPv6 NAT support merged in 6.5. It has been almost impossible to get IPv6 into a VM on a laptop that switches between wifi and wired (dock) connections, because you can not add a wifi interface to a bridge. I know NAT is against the IPv6 end-to-end xen but it makes this "just work" for the vast majority of people like me who need to ssh/curl/talk to ipv6 only hosts! So I installed 6.6.0 from the virt-preview repos on Fedora 32 to eagerly test it out. My network config looks like <network> <name>network</name> <uuid> ... </uuid> <forward mode='nat'> <nat ipv6='yes'/> </forward> <bridge name='virbr0' stp='on' delay='0'/> <mac address=' ... '/> <domain name='network'/> <ip address='192.168.100.1' netmask='255.255.255.0'> <dhcp> <range start='192.168.100.128' end='192.168.100.254'/> </dhcp> </ip> <ip family='ipv6' address='fc00:dead:beef:55::' prefix='64'> </ip> </network> The first problem I hit was trying to start that network: error: internal error: Check the host setup: enabling IPv6 forwarding with RA routes without accept_ra set to 2 is likely to cause routes loss. Interfaces to look at: wlp4s0 wlp4s0 is my wifi card that is configured by NetworkManager in a completely unremarkable fashion. By default it gets an ipv6 via SLAAC from my router. This feels a bit like the unresolved bug [1] which says that systemd-networkd is handling the RA's in userspace for ... reasons [2]. It's unclear to me if NetworkManager is doing similar. I feel like this must be a red-herring. My wired interface has the same setting of 0 $ cat /proc/sys/net/ipv6/conf/enp0s31f6/accept_ra 0 and is similarly just a very standard auto-configured NetworkManager interface. When I "net-start" the network whilst on wifi libvirt doesn't seem to care about that interface (I presume it only looks at the active one?). When I dock and turn off wifi, ipv6 connectivity continues to work through enp0s31f6, so I don't think the accept_ra really matters in this case. I feel like this message is incorrect, and being as I've done nothing special to my underlying interfaces probably going to be wrong for a lot of people trying this? Does anyone know the details of this message and see why it would be required in this situation? The other thing that I'd like to expand the documentation on, if I can get some clarity, is the choice of network. It seems like it has to be a /64, and it seems like the best choice is within fc00::/7, or at least that is what has been assigned for private networks like this [3]? The only problem with this is that I think glibc filters this range so nothing prefers IPv6. Is this the range expected to be used for ipv6 NAT? If so, would a patch to drop some documentation breadcrumbs about setting gai.conf or something be useful? Or are there better choices for the network? Thanks! -i [1] https://bugzilla.redhat.com/show_bug.cgi?id=1639087 [2] https://github.com/systemd/systemd/commit/3b015d40c19d9338b66bf916d84dec601… [3] https://tools.ietf.org/html/rfc4193

3 4

Post-firewall hook to insert custom rules?
by Gunnar Niels 18 Aug '20

18 Aug '20

Hello, I have a set of iptables rules that I need to insert *after* libvirt has set up all of its firewall rules. Is there a hook that I can tap into in order to run something like a custom script to make sure this happens? Any ideas? -GN

2 2

Way to skip check for 'libvirt-qemu' group and user while installing guest
by john doe 17 Aug '20

17 Aug '20

Hi, Debian Buster here, I'm trying to install a guest on a sshfs mount, Libvirt is checking for the user and group 'libvirt-qemu'. Is there a way to avoid that check or has anyone a way to use a mount used by sshfs with Libvirt? The SSH server has no group with the UID/GID of 'libvirt-qemu'. -- John Doe

1 1

Constant error logging
by Digimer 17 Aug '20

17 Aug '20

Hi all, I've got a (pacemaker + drbd) cluster running VMs. When the VM is running on another node, the local storage is Secondary, meaning that it can't be read or otherwise touched. As such, virsh thinks there is no storage and constantly prints errors like: ==== Aug 14 19:25:24 mk-a02n01.digimer.ca libvirtd[1655]: 2020-08-14 23:25:24.812+0000: 1679: error : qemuOpenFileAs:3119 : Failed to open file '/dev/drbd/by-res/srv01-sql/0': No such file or directory Aug 14 19:25:24 mk-a02n01.digimer.ca libvirtd[1655]: 2020-08-14 23:25:24.812+0000: 1679: error : qemuOpenFileAs:3119 : Failed to open file '/dev/drbd/by-res/srv01-sql/1': No such file or directory Aug 14 19:25:24 mk-a02n01.digimer.ca libvirtd[1655]: 2020-08-14 23:25:24.812+0000: 1679: error : qemuOpenFileAs:3119 : Failed to open file '/dev/drbd/by-res/srv07-el6/0': Wrong medium type === To the system logs (journald), about once every second or two. Is there any way to tell libvirtd not to complain about this? Thanks -- Digimer Papers and Projects: https://alteeve.com/w/ "I am, somehow, less interested in the weight and convolutions of Einstein’s brain than in the near certainty that people of equal talent have lived and died in cotton fields and sweatshops." - Stephen Jay Gould

2 1

Problem with xen config
by Christoph 14 Aug '20

14 Aug '20

Hi all, I 've such a config on xen (4.14): name = "marax.chao5.int" uuid = "e0de3cb7-3937-417d-8d63-b0993b377b6a" maxmem = 16384 memory = 16384 kernel = '/usr/lib64/xen/boot/hvmloader' vcpus = 16 rtc_timeoffset = 0 localtime = 1 on_poweroff = "destroy" on_reboot = "restart" on_crash = "restart" vif = [ "mac=00:16:3e:05:01:10,bridge=xenbr5,script=vif-bridge,model=e1000" ] parallel = "none" serial = "none" type = "hvm" loader = "/usr/lib64/xen/boot/hvmloader" disk = [ "phy:/dev/mapper/marax_c,hda,rw", "phy:/dev/vg_lilith/lv_marax_d,hdb,rw" ] max_grant_frames = "128" pci = [ "01:00.0", "01:00.1", "01:00.2", "01:00.3", "00:1f.3", "05:00.0" ] pci_permissive = 1 keymap = "de" vnclisten="0.0.0.0" pci_power_mgmt=1 xen_platform_pci=1 pci_msitranslate=1 viridian=1 hpet=1 acpi=1 apic=1 pae=1 I want to convert it to a xml format for use it with libvirt/virsh but I get an error: "error: An error occurred, but the cause is unknown" If I comment out the line with pci = [ "01:00.0", "01:00.1", "01:00.2", "01:00.3", "00:1f.3", "05:00.0" ] then it works but I dont see the settings like xen_platform_pci=1 pci_msitranslate=1 pci_permissive = 1 max_grant_frames = "128 and the pci passthrough devices are not there... Does libvirt doesnt support such a config? -- ------ Greetz

3 9

pass-though Intel gpu int o a vm
by daggs 12 Aug '20

12 Aug '20

Greetings, I have a server that run a vm with several nic pcie cards as pass-though. the board has an intel gpu and the hdmi output is not used. I thought of booting up another vm and pass the gpu into it. I found several discussions on the subject stating that it isn't possible but all of them are several years old. I wonder if that has changed? is there a way to pt the vga to a vm? Thanks, Dagg.

3 5

Question for smbios
by David 10 Aug '20

10 Aug '20

I am reposting this because it's been 2 or 3 weeks. Hello, Hopefully this is the right place to send a question like this... I'm attempting to automate creation of VMs using virt-install and a cloud-init disk image. To get this to work, I need to specify the location of the cloud-init configs by passing smbios key/value pairs. Normally, -smbios is provided to qemu to do this. With virt-install, the Internet says I should use --sysinfo. However, --sysinfo (as well as --qemu-comandline) is reported as an invalid command flag, and it is not present when I look at man virt-install and virt-install --help. I am hoping someone on the list knows why this isn't working or can explain how I might provide the arguments to qemu. The host is Debian 9. It is up-to-date as far as package versions are concerned, as much as Debian 9 can be. I can't find any indication about why the arguments would have been taken away. Thanks!

3 3