- Users - libvirt List Archives

about pcie-hot-plug on aarch64
by Jaze Lee 11 Oct '21

11 Oct '21

Hello, We run Openstack Stein on arm. It runs nova-compute(use libvirt as virt driver) on arm host. We found when built with disks (use ceph rbd) on arm hosts, the vm can not attach all disk correctly. For example, built with six disks, the vm may attach three disks. No obvious error can be fond in nova-compute, libvirt. We compare aarch64 and x86, find when detach disk, the dmesg of the vm's os is different. May be the pciehg parameter is different? Did anyone met the problem? Or some suggestions? x86: Nothing at all aarch64: Sep 29 15:28:55 * kernel: pciehp 0000:00:01.5:pcie004: Slot(0-5): Attention button pressed Sep 29 15:28:55 * kernel: pciehp 0000:00:01.5:pcie004: Slot(0-5): Powering off due to button press Sep 29 15:29:00 * kernel: pciehp 0000:00:01.5:pcie004: Slot(0-5): Attention button pressed Sep 29 15:29:00 * kernel: pciehp 0000:00:01.5:pcie004: Slot(0-5): Button cancel Sep 29 15:29:00 * kernel: pciehp 0000:00:01.5:pcie004: Slot(0-5): Action canceled due to button press Sep 29 15:29:07 * kernel: pciehp 0000:00:01.5:pcie004: Slot(0-5): Attention button pressed Sep 29 15:29:07 * kernel: pciehp 0000:00:01.5:pcie004: Slot(0-5): Powering off due to button press Sep 29 15:29:13 * kernel: pciehp 0000:00:01.5:pcie004: Slot(0-5): Link Up Sep 29 15:29:16 * kernel: pciehp 0000:00:01.5:pcie004: Failed to check link status Sep 29 15:29:18 * kernel: pciehp 0000:00:01.6:pcie004: Slot(0-6): Attention button pressed Sep 29 15:29:18 * kernel: pciehp 0000:00:01.6:pcie004: Slot(0-6): Powering off due to button press Sep 29 15:29:23 * kernel: pciehp 0000:00:01.6:pcie004: Slot(0-6): Attention button pressed Sep 29 15:29:23 * kernel: pciehp 0000:00:01.6:pcie004: Slot(0-6): Button cancel Sep 29 15:29:23 * kernel: pciehp 0000:00:01.6:pcie004: Slot(0-6): Action canceled due to button press Sep 29 15:29:30 * kernel: pciehp 0000:00:01.6:pcie004: Slot(0-6): Attention button pressed Sep 29 15:29:30 * kernel: pciehp 0000:00:01.6:pcie004: Slot(0-6): Powering off due to button press Sep 29 15:29:36 * kernel: pciehp 0000:00:01.6:pcie004: Slot(0-6): Link Up Sep 29 15:29:39 * kernel: pciehp 0000:00:01.6:pcie004: Failed to check link status Sep 29 15:29:39 * kernel: pciehp 0000:00:01.7:pcie004: Slot(0-7): Attention button pressed Sep 29 15:29:39 * kernel: pciehp 0000:00:01.7:pcie004: Slot(0-7): Powering off due to button press Sep 29 15:29:45 * kernel: pciehp 0000:00:01.7:pcie004: Slot(0-7): Attention button pressed Sep 29 15:29:45 * kernel: pciehp 0000:00:01.7:pcie004: Slot(0-7): Button cancel Sep 29 15:29:45 * kernel: pciehp 0000:00:01.7:pcie004: Slot(0-7): Action canceled due to button press Sep 29 15:29:52 * kernel: pciehp 0000:00:01.7:pcie004: Slot(0-7): Attention button pressed Sep 29 15:29:52 * kernel: pciehp 0000:00:01.7:pcie004: Slot(0-7): Powering off due to button press Sep 29 15:29:58 * kernel: pciehp 0000:00:01.7:pcie004: Slot(0-7): Link Up Sep 29 15:30:01 * kernel: pciehp 0000:00:02.0:pcie004: Slot(0-8): Attention button pressed Sep 29 15:30:01 * kernel: pciehp 0000:00:02.0:pcie004: Slot(0-8): Powering off due to button press

3 3

re: nwfilter direction not being used when protocol all
by Jason Pyeron 11 Oct '21

11 Oct '21

> -----Original Message----- > From: Jason Pyeron > Sent: Monday, October 11, 2021 8:49 AM > To: Kyle Marek; Michael Watson Jr > Cc: libvirt-users > > Watson / Kyle: > > (note I coped the list) > > While I read https://libvirt.org/formatnwfilter.html#nwfelemsRulesProtoMisc , it is not > clear that it is intended to add the iptables action without regard to the rule’s > direction. > > Take the following rule scenarios: > > <rule action='accept' direction='in' priority='500' statematch='false'> > <tcp dstportstart='22'/> > </rule> > <rule action='drop' direction='in' priority='1000'> > <all/> > </rule> > > # iptables-save | grep vnet5 | tee in > :FI-vnet5 - [0:0] > :FO-vnet5 - [0:0] > :HI-vnet5 - [0:0] > -A FI-vnet5 -p tcp -m tcp --sport 22 -j RETURN > -A FI-vnet5 -j DROP > -A FO-vnet5 -p tcp -m tcp --dport 22 -j ACCEPT > -A FO-vnet5 -j DROP > -A HI-vnet5 -p tcp -m tcp --sport 22 -j RETURN > -A HI-vnet5 -j DROP > -A libvirt-host-in -m physdev --physdev-in vnet5 -g HI-vnet5 > -A libvirt-in -m physdev --physdev-in vnet5 -g FI-vnet5 > -A libvirt-in-post -m physdev --physdev-in vnet5 -j ACCEPT > -A libvirt-out -m physdev --physdev-out vnet5 --physdev-is-bridged -g FO-vnet5 > > <rule action='accept' direction='in' priority='500' statematch='false'> > <tcp dstportstart='22'/> > </rule> > <rule action='drop' direction='out' priority='1000'> > <all/> > </rule> > > # iptables-save | grep vnet5 | tee out > :FI-vnet5 - [0:0] > :FO-vnet5 - [0:0] > :HI-vnet5 - [0:0] > -A FI-vnet5 -p tcp -m tcp --sport 22 -j RETURN > -A FI-vnet5 -j DROP > -A FO-vnet5 -p tcp -m tcp --dport 22 -j ACCEPT > -A FO-vnet5 -j DROP > -A HI-vnet5 -p tcp -m tcp --sport 22 -j RETURN > -A HI-vnet5 -j DROP > -A libvirt-host-in -m physdev --physdev-in vnet5 -g HI-vnet5 > -A libvirt-in -m physdev --physdev-in vnet5 -g FI-vnet5 > -A libvirt-in-post -m physdev --physdev-in vnet5 -j ACCEPT > -A libvirt-out -m physdev --physdev-out vnet5 --physdev-is-bridged -g FO-vnet5 > > <rule action='accept' direction='in' priority='500' statematch='false'> > <tcp dstportstart='22'/> > </rule> > <rule action='drop' direction='inout' priority='1000'> > <all/> > </rule> > > # iptables-save | grep vnet5 | tee inout > :FI-vnet5 - [0:0] > :FO-vnet5 - [0:0] > :HI-vnet5 - [0:0] > -A FI-vnet5 -p tcp -m tcp --sport 22 -j RETURN > -A FI-vnet5 -j DROP > -A FO-vnet5 -p tcp -m tcp --dport 22 -j ACCEPT > -A FO-vnet5 -j DROP > -A HI-vnet5 -p tcp -m tcp --sport 22 -j RETURN > -A HI-vnet5 -j DROP > -A libvirt-host-in -m physdev --physdev-in vnet5 -g HI-vnet5 > -A libvirt-in -m physdev --physdev-in vnet5 -g FI-vnet5 > -A libvirt-in-post -m physdev --physdev-in vnet5 -j ACCEPT > -A libvirt-out -m physdev --physdev-out vnet5 --physdev-is-bridged -g FO-vnet5 > > We note that the > > -A HI-vnet5 -j DROP > -A FI-vnet5 -j DROP > -A FO-vnet5 -j DROP > > Is present without regards to the state of the direction attribute on the “default” drop > rule. > > If the direction is “in” then the “-A FI-vnet5 -j DROP” should not exists. > > What does the source code say? I worry that either the docs are imprecise and this is > desired, or there is a bug and I can end up like After looking at libvirt-4.5.0/src/nwfilter/nwfilter_ebiptables_driver.c's _iptablesCreateRuleInstance and iptablesCreateRuleInstanceStateCtrl, I saw the if statements like the below. 1598 if (directionIn && !inout) { 1599 if ((rule->flags & IPTABLES_STATE_FLAGS)) 1600 create = false; 1601 } 1629 if (!directionIn) { 1630 if ((rule->flags & IPTABLES_STATE_FLAGS)) 1631 create = false; 1632 } Is the only way to respect the direction is to have <all state='something...'/> ? If that is the case the docs, really need an update to note this. For others, my deny inbound, allow outbound was accomplished by: <rule action='accept' direction='in' priority='999'> <all state='ESTABLISHED,RELATED'/> </rule> <rule action='drop' direction='in' priority='1000'> <all state='NONE'/> </rule> -Jason

1 0

nwfilter direction not being used when protocol all
by Jason Pyeron 11 Oct '21

11 Oct '21

Watson / Kyle: (note I coped the list) While I read https://libvirt.org/formatnwfilter.html#nwfelemsRulesProtoMisc , it is not clear that it is intended to add the iptables action without regard to the rule’s direction. Take the following rule scenarios: <rule action='accept' direction='in' priority='500' statematch='false'> <tcp dstportstart='22'/> </rule> <rule action='drop' direction='in' priority='1000'> <all/> </rule> # iptables-save | grep vnet5 | tee in :FI-vnet5 - [0:0] :FO-vnet5 - [0:0] :HI-vnet5 - [0:0] -A FI-vnet5 -p tcp -m tcp --sport 22 -j RETURN -A FI-vnet5 -j DROP -A FO-vnet5 -p tcp -m tcp --dport 22 -j ACCEPT -A FO-vnet5 -j DROP -A HI-vnet5 -p tcp -m tcp --sport 22 -j RETURN -A HI-vnet5 -j DROP -A libvirt-host-in -m physdev --physdev-in vnet5 -g HI-vnet5 -A libvirt-in -m physdev --physdev-in vnet5 -g FI-vnet5 -A libvirt-in-post -m physdev --physdev-in vnet5 -j ACCEPT -A libvirt-out -m physdev --physdev-out vnet5 --physdev-is-bridged -g FO-vnet5 <rule action='accept' direction='in' priority='500' statematch='false'> <tcp dstportstart='22'/> </rule> <rule action='drop' direction='out' priority='1000'> <all/> </rule> # iptables-save | grep vnet5 | tee out :FI-vnet5 - [0:0] :FO-vnet5 - [0:0] :HI-vnet5 - [0:0] -A FI-vnet5 -p tcp -m tcp --sport 22 -j RETURN -A FI-vnet5 -j DROP -A FO-vnet5 -p tcp -m tcp --dport 22 -j ACCEPT -A FO-vnet5 -j DROP -A HI-vnet5 -p tcp -m tcp --sport 22 -j RETURN -A HI-vnet5 -j DROP -A libvirt-host-in -m physdev --physdev-in vnet5 -g HI-vnet5 -A libvirt-in -m physdev --physdev-in vnet5 -g FI-vnet5 -A libvirt-in-post -m physdev --physdev-in vnet5 -j ACCEPT -A libvirt-out -m physdev --physdev-out vnet5 --physdev-is-bridged -g FO-vnet5 <rule action='accept' direction='in' priority='500' statematch='false'> <tcp dstportstart='22'/> </rule> <rule action='drop' direction='inout' priority='1000'> <all/> </rule> # iptables-save | grep vnet5 | tee inout :FI-vnet5 - [0:0] :FO-vnet5 - [0:0] :HI-vnet5 - [0:0] -A FI-vnet5 -p tcp -m tcp --sport 22 -j RETURN -A FI-vnet5 -j DROP -A FO-vnet5 -p tcp -m tcp --dport 22 -j ACCEPT -A FO-vnet5 -j DROP -A HI-vnet5 -p tcp -m tcp --sport 22 -j RETURN -A HI-vnet5 -j DROP -A libvirt-host-in -m physdev --physdev-in vnet5 -g HI-vnet5 -A libvirt-in -m physdev --physdev-in vnet5 -g FI-vnet5 -A libvirt-in-post -m physdev --physdev-in vnet5 -j ACCEPT -A libvirt-out -m physdev --physdev-out vnet5 --physdev-is-bridged -g FO-vnet5 We note that the -A HI-vnet5 -j DROP -A FI-vnet5 -j DROP -A FO-vnet5 -j DROP Is present without regards to the state of the direction attribute on the “default” drop rule. If the direction is “in” then the “-A FI-vnet5 -j DROP” should not exists. What does the source code say? I worry that either the docs are imprecise and this is desired, or there is a bug and I can end up like https://superuser.com/questions/1660080/in-libvirt-network-filters-nwfilter… As this is going to be a generic rule, applied many times – I would prefer not to have mac based source allow rules. -Jason

1 0

how to get enabled features
by Jiatong Shen 11 Oct '21

11 Oct '21

Hello community, I am trying to learn how to use dtrace and systemtap for libvirt, as the documentation says it seems to enable `--with-dtrace` when compiling. I am installing libvirt using apt install and is it possible to determine if dtrace is built by running some libvirt commands? Thank you. -- Best Regards, Jiatong Shen

2 1

Need more doc for libvirt-console-proxy
by Guy Godfroy 05 Oct '21

05 Oct '21

Hello, I'm making a web app for my company that will enable different teams to manage their own VMs. I wish to make possible to interact with each VM console, so I plan to use some xterm.js with websockets. So I discovered libvirt-console-proxy [1] when I looked for something to put a libvirt console into a websocket. That seems like the right tool for the job. The only doc I found is this article from 2017 [2]. After trying to understand from this article and from --help, I still have many questions. I am really bad at reading code so I can't even get answers from the sources. My main concern is: How a client is supposed to talk to the proxy? It is said that a security token must be provided. How? HTTP header? Which header? Am I missing something in websocket protocol? I think an example client implementation would help a lot. Also, I tried to use virtconsoleresolveradm to set up metadata on my domains like explained in the article [1] : ./virtconsoleresolveradm enable milou Enabled access to domain 'milou' But that doesn't seem to do anything (except defining the metadata namespace in the XML): virsh metadata milou http://libvirt.org/schemas/console-proxy/1.0 <consoles/> I precise that I have already this in my XML: <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </serial> <console type='pty'> <target type='serial' port='0'/> </console> Should I remove that? Should I edit that? Thanks for your help. Guy Godfroy [1] https://gitlab.com/libvirt/libvirt-console-proxy [2] https://www.berrange.com/posts/2017/01/26/announce-new-libvirt-console-prox…

1 1

how/where to configure access to libvirt-sock-ro
by Marc 04 Oct '21

04 Oct '21

I wanted to create a monitoring user that can do some reporting like this: runuser -u xxxxx -- prometheus-libvirt-exporter -libvirt.uri /var/run/libvirt/libvirt-sock-ro But I am getting the failed to connect: authentication required

2 1

how/where to configure access to libvirt-sock-ro
by Marc 03 Oct '21

03 Oct '21

I wanted to create a monitoring user that can do some reporting like this: runuser -u xxxxx -- prometheus-libvirt-exporter -libvirt.uri /var/run/libvirt/libvirt-sock-ro But I am getting the failed to connect: authentication required

1 0

Are secrets hidden from admins too - ?
by lejeczek 29 Sep '21

29 Sep '21

Hi guys. On a remote & "shared" systems - are private secrets completely 100% safe? Can root get to those? (naturally excluding hacking of unknown bugs & exploits and theories such as "no computer system is ultimately safe") And if answer is yes then - do you have any best practices for storing & managing of those secrets? many thanks, L.

3 6

How to move emulated SWTPM data to a new VM
by Sam Varshavchik 24 Sep '21

24 Sep '21

I have an existing VM with an emulated TPM module. I'm trying to create a replacement VM, pointing to the same disk image that the existing VM uses, and also migrate the existing TPM module to it. Would just copying everything in /var/lib/libvirt/swtpm/<UUID> work? I did some practice runs, and it seems that virt-manager immediately starts the new VM as soon as it creates one, so I need to quickly turn it off, go look up its new UUID, and copy over the TPM files?

2 2

security driver mismatch blocks live migration..
by Jiatong Shen 20 Sep '21

20 Sep '21

Hello community, I am seeing following error during performing a live migration libvirtError: unsupported configuration: Unable to find security driver for model apparmor The root cause is the destination libvirtd runs inside a container and apparmor profile is not enabled. Right now I am researching how to enable apparmor profile for a k8s pod. But Is it possible to do a live migrate an instance and disable security driver at the same time? Thank you. -- Best Regards, Jiatong Shen

2 1

internal error: Network is already in use by interface virbr0
by Michael Ströder 17 Sep '21

17 Sep '21

HI! I'm using libvirt 7.7.0 on openSUSE Tumbleweed. Until recently everything just worked. But now my virtual NAT network is not usable anymore. Starting a VM I get this error: # virsh start ae-dir-suse-p1 error: Failed to start domain 'ae-dir-suse-p1' error: Requested operation is not valid: network 'vnet1' is not active Manually starting the network does not work either: # virsh net-start vnet1 error: Failed to start network vnet1 error: internal error: Network is already in use by interface virbr0 In syslog I find: libvirtd: 6325: error : networkCheckRouteCollision:296 : internal error: Network is already in use by interface virbr0 What does that mean? Where to look for a config error? Ciao, Michael.

3 5

Compiling libvirt on ubuntu
by Or Ozeri 13 Sep '21

13 Sep '21

Hi, I'm trying to compile libvirt on ubuntu machine. I installed meson 0.59.1 using pip. Then installed a few more packages that were required by meson build: sudo apt-get install libxml2-utils xsltproc libpciaccess-dev ninja-build Finally, I followed the simple instructions over here: https://libvirt.org/compiling.html xz -dc libvirt-7.7.0.tar.xz | tar xvf - cd libvirt-7.7.0 meson build ninja -C build The last command fails with: FAILED: src/libvirt-admin.so.0.7007.0 cc -o src/libvirt-admin.so.0.7007.0 src/libvirt_probes.o src/libvirt-admin.so.0.7007.0.p/meson-generated_.._admin_admin_protocol.c.o src/libvirt-admin.so.0.7007.0.p/admin_libvirt-admin.c.o src/libvirt-admin.so.0.7007.0.p/datatypes.c.o -Wl,--as-needed -Wl,--no-undefined -shared -fPIC -Wl,--start-group -Wl,-soname,libvirt-admin.so.0 '-Wl,-rpath,$ORIGIN/:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX' -Wl,-rpath-link,/home/oro/ozeri/libvirt-7.7.0/build/src src/libvirt.so.0.7007.0 -Wl,--version-script=/home/oro/ozeri/libvirt-7.7.0/build/src/admin/libvirt_admin.syms -Wl,-z,nodelete /usr/lib/x86_64-linux-gnu/libcap-ng.so /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libdevmapper.so /usr/lib/x86_64-linux-gnu/libgnutls.so -Wl,-z,relro -Wl,-z,now -Wl,--no-copy-dt-needed-entries /usr/lib/x86_64-linux-gnu/libglib-2.0.so /usr/lib/x86_64-linux-gnu/libgobject-2.0.so /usr/lib/x86_64-linux-gnu/libgio-2.0.so /usr/lib/x86_64-linux-gnu/libxml2.so /usr/lib/x86_64-linux-gnu/libyajl.so -Wl,--end-group /usr/bin/ld: src/libvirt-admin.so.0.7007.0.p/admin_libvirt-admin.c.o: in function `callFull': /home/oro/ozeri/libvirt-7.7.0/build/../src/admin/admin_remote.c:99: undefined reference to `virNetClientProgramCall' /usr/bin/ld: src/libvirt-admin.so.0.7007.0.p/admin_libvirt-admin.c.o: in function `remoteAdminConnectClose': /home/oro/ozeri/libvirt-7.7.0/build/../src/admin/admin_remote.c:197: undefined reference to `virNetClientSetCloseCallback' /usr/bin/ld: /home/oro/ozeri/libvirt-7.7.0/build/../src/admin/admin_remote.c:199: undefined reference to `virNetClientClose' /usr/bin/ld: src/libvirt-admin.so.0.7007.0.p/admin_libvirt-admin.c.o: in function `remoteAdminPrivNew': /home/oro/ozeri/libvirt-7.7.0/build/../src/admin/admin_remote.c:225: undefined reference to `virNetClientNewUNIX' /usr/bin/ld: /home/oro/ozeri/libvirt-7.7.0/build/../src/admin/admin_remote.c:228: undefined reference to `virNetClientProgramNew' /usr/bin/ld: /home/oro/ozeri/libvirt-7.7.0/build/../src/admin/admin_remote.c:233: undefined reference to `virNetClientAddProgram' /usr/bin/ld: src/libvirt-admin.so.0.7007.0.p/admin_libvirt-admin.c.o: in function `remoteAdminConnectOpen': /home/oro/ozeri/libvirt-7.7.0/build/../src/admin/admin_remote.c:159: undefined reference to `virNetClientRegisterAsyncIO' /usr/bin/ld: /home/oro/ozeri/libvirt-7.7.0/build/../src/admin/admin_remote.c:166: undefined reference to `virNetClientSetCloseCallback' /usr/bin/ld: src/libvirt-admin.so.0.7007.0.p/admin_libvirt-admin.c.o: in function `virAdmConnectIsAlive': /home/oro/ozeri/libvirt-7.7.0/build/../src/admin/libvirt-admin.c:397: undefined reference to `virNetClientIsOpen' collect2: error: ld returned 1 exit status [2/11] Linking target tests/virsystemdtest FAILED: tests/virsystemdtest cc -o tests/virsystemdtest src/libvirt_probes.o tests/virsystemdtest.p/virsystemdtest.c.o -Wl,--as-needed -Wl,--no-undefined -Wl,-export-dynamic -pie -Wl,--whole-archive -Wl,--start-group tests/libtest_utils.a -Wl,--no-whole-archive '-Wl,-rpath,$ORIGIN/../src' -Wl,-rpath-link,/home/oro/ozeri/libvirt-7.7.0/build/src src/libvirt.so.0.7007.0 -Wl,--no-copy-dt-needed-entries -Wl,-export-dynamic -ldl /usr/lib/x86_64-linux-gnu/libglib-2.0.so /usr/lib/x86_64-linux-gnu/libgobject-2.0.so /usr/lib/x86_64-linux-gnu/libgio-2.0.so /usr/lib/x86_64-linux-gnu/libgnutls.so /lib/x86_64-linux-gnu/libnl-3.so /usr/lib/x86_64-linux-gnu/libnl-route-3.so /usr/lib/x86_64-linux-gnu/libxml2.so /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libselinux.so /usr/lib/x86_64-linux-gnu/libyajl.so -Wl,--end-group -Wl,-export-dynamic /usr/bin/ld: tests/virsystemdtest.p/virsystemdtest.c.o: in function `testActivationCreateFDs': /home/oro/ozeri/libvirt-7.7.0/build/../tests/virsystemdtest.c:506: undefined reference to `virNetSocketNewListenUNIX' /usr/bin/ld: /home/oro/ozeri/libvirt-7.7.0/build/../tests/virsystemdtest.c:513: undefined reference to `virNetSocketNewListenTCP' /usr/bin/ld: tests/virsystemdtest.p/virsystemdtest.c.o: in function `testActivation': /home/oro/ozeri/libvirt-7.7.0/build/../tests/virsystemdtest.c:548: undefined reference to `virNetSocketGetPath' /usr/bin/ld: /home/oro/ozeri/libvirt-7.7.0/build/../tests/virsystemdtest.c:570: undefined reference to `virNetSocketGetPort' collect2: error: ld returned 1 exit status ninja: build stopped: subcommand failed. I verified that these functions do exist inside libvirt.so.0.7007.0, but for some reason the linker fails. What am I doing wrong here? Thanks, Or

3 2

virsh domifaddr domain does not show static IP
by Kaushal Shriyan 12 Sep '21

12 Sep '21

Hi, I have assigned static IP for all the below KVM Guest VM's. Is there a way to find out the IP of the below VM's from virsh utility or any other utility? virsh domifaddr testdobssbahrainms does not show the static IP. # virsh list --all Id Name State ----------------------------------------- 1 testdobssbahrainms running 2 testdosstomcatpibms running 3 testdobsstomcatkineticms running 4 testdobsstomcatmsbms running 5 testdobsstomcatfdms running 6 testdobsstomcathsbcnetms running 7 testdobsstomcatdbbms running 8 testdobssapigeedev running # # virt-install --version 2.2.1 # cat /etc/redhat-release CentOS Stream release 8 #virsh domifaddr testdobssbahrainms #Name MAC address Protocol Address ------------------------------------------------------------------------------- Please guide. Thanks in advance. Best Regards, Kaushal

3 4

startupPolicy issue when changing CD
by Vojtech Juranek 10 Sep '21

10 Sep '21

Hi, when adding support for CD disk on block based storage into oVirt, I spotted following issue. When starting VM without CD, we add startupPolicy='optional' attribute into <source> element. Whole XML looks like this: <disk type='file' device='cdrom'> <driver name='qemu' error_policy='report'/> <source startupPolicy='optional'/> <target dev='sdc' bus='sata'/> <readonly/> <alias name='ua-d7003457-63c3-4c98-80f0-08ab5042c65e'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> To change/insert CD we use libvirt.updateDeviceFlags() with XML which looks like this (for block based disk): <?xml version='1.0' encoding='utf-8'?> <disk device="cdrom" type="block"> <source dev="/rhev/data-center/mnt/blockSD/cdac2a0c-b110-456d-a988-7d588626c871/images/638247d7-b4b1-4d98-87fa-c90235fcf4b1/145e7cd2-f92d-4eec-a8fb-6835b4b652e1" /> <target bus="sata" dev="sdc" /> </disk> However, updateDeviceFlags() fails with libvirt.libvirtError: XML error: 'startupPolicy' is only valid for 'file' type volume What is the reason for this error? We don't use `startupPolicy` attribute for block based disks, as shown on example above. Thanks in advance. Vojta

2 3

snapshot creation broken recently?
by Štěpán Němec 09 Sep '21

09 Sep '21

Hello, until very recently I had been happily creating snapshots of running VMs (created using virt-install) simply with virsh --connect qemu:///system snapshot-create-as <domain-name> <snapshot-name> Now when I try to do that I get the following error: Error creating snapshot: operation failed: Failed to take snapshot: pre-save failed: qxl Same thing trying to create a snapshot from virt-manager (which also used to work). Here's the full backtrace (as displayed in virt-manager): Error: Error while writing VM state: Unknown error -1 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/details/snapshots.py", line 237, in _do_create_snapshot self.vm.create_snapshot(xml) File "/usr/share/virt-manager/virtManager/object/domain.py", line 1124, in create_snapshot self._backend.snapshotCreateXML(xml, flags) File "/usr/lib/python3.9/site-packages/libvirt.py", line 3059, in snapshotCreateXML raise libvirtError('virDomainSnapshotCreateXML() failed') libvirt.libvirtError: operation failed: Failed to take snapshot: pre-save failed: qxl Error: Error while writing VM state: Unknown error -1 I am on Arch Linux (x86_64), using the distro packages. Checking my pacman logs, might update of qemu-headless from 6.0.0 to 6.1.0 have something to do with that? (Since then, libvirt has also been updated from 7.6.0 to 7.7.0, but I see no change WRT the problem described.) I would appreciate any advice on how to further investigate and/or work around the problem. (I checked https://gitlab.com/libvirt/libvirt/-/issues and didn't find anything that seemed related.) Thanks, Štěpán

2 2

one qustion about the snapshot of the libvirt, thanks.
by Guozhonghua 06 Sep '21

06 Sep '21

Hello, When we test snapshot features and review the code of libvirt, there is one question, not an issue. /* do the memory snapshot if necessary */ if (memory) { /* check if migration is possible */ if (!qemuMigrationSrcIsAllowed(driver, vm, false, 0)) goto cleanup; While making one snapshot with memory on one vm, but it is not allowed while the vm which has some src devices, such as pci devs, with which the vm is not allowed to be migrated. I want to known the reason, why should it check this conditions? Thank You!

2 2

vm vcpu uses isolated cores
by Jiatong Shen 02 Sep '21

02 Sep '21

Hello, I am trying to understand why qemu vm CPU threads uses isolated cpus. I have a host which isolates some cpus using isolcpu like isolcpus=1,2,3,4,5,7,8,9,10,11. unfortunately, vcpupin does not mask out these cpus (vcpupin is still something like ffffffff). When I log in to the system, seems qemu cpu thread only runs on these isolcpus. I do not quite understand this behavior, because I think by using isolcpu, kernel schedule will exclude these cpus and thus vcpu thread shouldn't use these cores unless taskset explicitly got called.. So my question is how does cpu thread got scheduled on isolated cpus? Thank you. -- Best Regards, Jiatong Shen

3 2

We need excellent and well-written documentation for setting up open source NAS software
by Turritopsis Dohrnii Teo En Ming 31 Aug '21

31 Aug '21

Subject: We need excellent and well-written documentation for setting up open source NAS software Good day from Singapore, Our company, which is a Systems Integrator (SI) in Singapore, is evaluating more than 30 different open source Network Attached Storage (NAS) software. We need excellent and well-written documentation for your open source NAS software. Please provide us with links on how to setup your open source NAS software. We are looking forward to your replies. Thank you very much for your kind assistance. Mr. Turritopsis Dohrnii Teo En Ming, 43 years old as of 31 August 2021, is a TARGETED INDIVIDUAL living in Singapore. He is an IT Consultant with a System Integrator (SI)/computer firm in Singapore. He is an IT enthusiast. -----BEGIN EMAIL SIGNATURE----- The Gospel for all Targeted Individuals (TIs): [The New York Times] Microwave Weapons Are Prime Suspect in Ills of U.S. Embassy Workers Link: https://www.nytimes.com/2018/09/01/science/sonic-attack-cuba-microwave.html ******************************************************************************************** Singaporean Targeted Individual Mr. Turritopsis Dohrnii Teo En Ming's Academic Qualifications as at 14 Feb 2019 and refugee seeking attempts at the United Nations Refugee Agency Bangkok (21 Mar 2017), in Taiwan (5 Aug 2019) and Australia (25 Dec 2019 to 9 Jan 2020): [1] https://tdtemcerts.wordpress.com/ [2] https://tdtemcerts.blogspot.sg/ [3] https://www.scribd.com/user/270125049/Teo-En-Ming -----END EMAIL SIGNATURE-----

1 0

issues with vm after upgrade
by daggs 30 Aug '21

30 Aug '21

Greetings, a few weeks ago I've upgraded my system, this resulted with qemu and libvirt being upgraded to 6.0.0 and ~7.5.0 respectfully. I have two vms running on my system, router and streamer. the router vm works great, the streamer vm doesn't. after the streamer vm start, the monitor screen gets black and thats it. no relevant error are found in the log, see: http://dpaste.com/ERWDEJQPC the xml ca be found at https://dpaste.com/FQDN6NTN2 in contrast the following oneliner works: qemu-system-x86_64 \ -machine pc-q35-5.0,accel=kvm,usb=off,smm=on,dump-guest-core=off \ -cpu host,migratable=on \ -m 15360 \ -smp 4,sockets=1,dies=1,cores=2,threads=2 \ -drive file=/home/streamer/streamer.img.qcow2.new,if=virtio,format=qcow2 \ -device vfio-pci,host=0000:00:02.0,romfile=/home/streamer/gpu-8086:5912-uefi.rom,multifunction=on \ -device vfio-pci,host=0000:00:1f.3,multifunction=on \ -usb \ -device usb-host,vendorid=0x046d,productid=0xc52e \ -device usb-host,vendorid=0x2548,productid=0x1002 \ -display none \ -netdev tap,id=hostnet0,ifname=virtsw-streamer,script=no,downscript=no \ -device e1000e,netdev=hostnet0,id=net0,mac=52:54:00:5a:4c:8c \ -blockdev '{"driver":"file","filename":"/usr/share/edk2-ovmf/OVMF_CODE.secboot.fd","node-name":"libvirt-pflash0-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"driver":"file","filename":"/var/lib/libvirt/qemu/nvram/streamer-vm-q35_VARS.fd","node-name":"libvirt-pflash1-storage","auto-read-only":true,"discard":"unmap"}' another issue encountered caused by this param: "-audiodev id=audio1,driver=none" which is auto added to the qemu line. if I add the line to the above oneliner, the guest doesn't detects the pt sound card. without it it does and it works. help on solving both issues will be appreciated. Thanks, Dagg

5 30

Question The order of the output of virsh guestinfo --filesystem
by liuyd.fnst＠fujitsu.com 24 Aug '21

24 Aug '21

Hi all. I'm curious about the output order of virsh guestinfo --filesystem. Is the output random? E.g Guest info ``` [root@localhost ~]# lsblk -Jp -o KNAME,FSTYPE,TYPE,MOUNTPOINT,PKNAME,SERIAL { "blockdevices": [ {"kname": "/dev/sr0", "fstype": null, "type": "rom", "mountpoint": null, "pkname": null, "serial": "drive-scsi0-0-0-0"}, {"kname": "/dev/vda", "fstype": null, "type": "disk", "mountpoint": null, "pkname": null, "serial": null}, {"kname": "/dev/vda1", "fstype": "vfat", "type": "part", "mountpoint": "/boot/efi", "pkname": "/dev/vda", "serial": null}, {"kname": "/dev/vda2", "fstype": "xfs", "type": "part", "mountpoint": "/boot", "pkname": "/dev/vda", "serial": null}, {"kname": "/dev/vda3", "fstype": "LVM2_member", "type": "part", "mountpoint": null, "pkname": "/dev/vda", "serial": null}, {"kname": "/dev/vdb", "fstype": null, "type": "disk", "mountpoint": null, "pkname": null, "serial": null}, {"kname": "/dev/vdb1", "fstype": "xfs", "type": "part", "mountpoint": "/mnt/test1", "pkname": "/dev/vdb", "serial": null}, {"kname": "/dev/vdb2", "fstype": "xfs", "type": "part", "mountpoint": "/mnt/test2", "pkname": "/dev/vdb", "serial": null}, {"kname": "/dev/vdb3", "fstype": "xfs", "type": "part", "mountpoint": "/mnt/test3", "pkname": "/dev/vdb", "serial": null}, {"kname": "/dev/dm-0", "fstype": "xfs", "type": "lvm", "mountpoint": "/", "pkname": "/dev/vda3", "serial": null}, {"kname": "/dev/dm-1", "fstype": "swap", "type": "lvm", "mountpoint": "[SWAP]", "pkname": "/dev/vda3", "serial": null} ] } ``` virsh guestinfo output. It is not sorted by name or total-bytes/used-bytes ``` [root@hpe-apollo80-01-n00 ~]# virsh guestinfo fj-kvm-vm --filesystem fs.count : 6 fs.0.name : dm-0 fs.0.mountpoint : / fs.0.fstype : xfs fs.0.total-bytes : 7946108928 fs.0.used-bytes : 3202314240 fs.0.disk.count : 1 fs.0.disk.0.alias : vda fs.0.disk.0.device : /dev/vda3 fs.1.name : vda2 fs.1.mountpoint : /boot fs.1.fstype : xfs fs.1.total-bytes : 1063256064 fs.1.used-bytes : 180252672 fs.1.disk.count : 1 fs.1.disk.0.alias : vda fs.1.disk.0.device : /dev/vda2 fs.2.name : vda1 fs.2.mountpoint : /boot/efi fs.2.fstype : vfat fs.2.total-bytes : 627900416 fs.2.used-bytes : 7065600 fs.2.disk.count : 1 fs.2.disk.0.alias : vda fs.2.disk.0.device : /dev/vda1 fs.3.name : vdb2 fs.3.mountpoint : /mnt/test2 fs.3.fstype : xfs fs.3.total-bytes : 204111872 fs.3.used-bytes : 12185600 fs.3.disk.count : 1 fs.3.disk.0.alias : vdb fs.3.disk.0.device : /dev/vdb2 fs.4.name : vdb3 fs.4.mountpoint : /mnt/test3 fs.4.fstype : xfs fs.4.total-bytes : 751706112 fs.4.used-bytes : 39084032 fs.4.disk.count : 1 fs.4.disk.0.alias : vdb fs.4.disk.0.device : /dev/vdb3 fs.5.name : vdb1 fs.5.mountpoint : /mnt/test1 fs.5.fstype : xfs fs.5.total-bytes : 99254272 fs.5.used-bytes : 6213632 fs.5.disk.count : 1 fs.5.disk.0.alias : vdb fs.5.disk.0.device : /dev/vdb1 ``` -- Best Regards. Yiding Liu

2 2

vmware ESXi in KVM
by Gunnar 11 Aug '21

11 Aug '21

I am trying to install esxi7 inside a KVM machine virt-install --name=esxi7 \ --vcpus=2 \ --memory=4096 \ --cdrom=/home/username/isos/VMware-VMvisor-Installer-7.0U2a-17867351.x86_64.iso \ --disk size=33 \ --os-variant=unknown the installation process starts but does not get fails with a "No network adapters" error. This does not happen with other VM's. What do I have to add to above command in order to attach the default network adapter to the machine? or is there any other trick I have to be aware of when it comes to installing ESXi thx ... Gunnar

3 2

RX throttling causes keep-alive timeout
by Ivan Teterevkov 05 Aug '21

05 Aug '21

Hello folks, I recently discovered that the max_client_requests configuration option affects the keep-alive RPC and can cause the connection timeout, and I wanted to verify if my understanding is correct. Let me outline the context. Under certain circumstances, one of the connected clients in my setup issued multiple concurrent long-standing live-migration requests and reached the default limit of five concurrent requests. Consequently, it triggered the RX throttling, so the server stopped reading the incoming data from this client's file descriptor. Meanwhile, the server issued the keepalive "ping" requests but ignored the "pong" responses from the client due to the RX throttling. As a result, the server concluded the client was dead and closed the connection with the "connection closed due to keepalive timeout" message after the default five "ping" attempts with five seconds timeout each. The idea of throttling makes perfect sense: the server prevents hogging of the worker thread pool (or would prevent the unbounded growth of the memory footprint if the libvirtd server continued parsing the incoming data and queued the requests). What concerns me is that the server drops the connection for the alive clients when they're throttled. One approach to this problem is implementing the EAGAIN-like handling: parse the incoming data above the limit and respond with the error response, but handle the keep-alive RPCs gracefully. However, I see two problems here: either it's a backwards-compatibility concern if implemented unconditionally or polluting the configuration space if implemented conditionally. What is the community's opinion on the above issue? Kind regards, Ivan

2 2

ERROR Couldn't find hvm kernel for Ubuntu tree.
by Kaushal Shriyan 05 Aug '21

05 Aug '21

Hi, I am running the below command to spawn Ubuntu 18.04 based Virtual Machine using KVM based technology. #virt-install --version 1.5.0 # virt-install --name=snipeitassetmanagement > --file=/linuxkvmguestosdisk/snipeitassetmanagement.img --file-size=40 > --nonsparse --vcpus=2 --ram=8096 --network=bridge:br0 --os-type=linux > --os-variant=ubuntu18.04 --graphics none > --location=/linuxkvmguestosdisk/var/lib/libvirt/isos/ubuntu-18.04.5-live-server-amd64.iso > --extra-args="console=ttyS0" > > Starting install... > Retrieving file .treeinfo... > > | 0 B 00:00:00 > Retrieving file content... > > | 0 B 00:00:00 > Retrieving file info... > > | 70 B 00:00:00 > ERROR Couldn't find hvm kernel for Ubuntu tree. > Domain installation does not appear to have been successful. > If it was, you can restart your domain by running: > virsh --connect qemu:///system start snipeitassetmanagement > otherwise, please restart your installation. > > Any clue and i look forward to hearing from you. Thanks in advance. Best Regards,

2 3

Usage of virsh commands on guest lxc container are failing
by Yuva Raj 05 Aug '21

05 Aug '21

Hi Team, I am new to the Qemu/KVM, libvirt and these technologies. Hypervisor is running on linux kernel with libvirtd version 1.3.2. I am trying to spawn LXC ubuntu(21.04) container using virsh -c lxc:// commands on the hypervisor and ubuntu container is running now. On the ubuntu 21.04 container, I have installed debian "libvirt-clients" package to use the virsh utility. Updated the /etc/libvirt/libvirt.conf with to the hypervisor Qemu URI. When I run virsh commands without URI, observing below error root@host:~# virsh list error: failed to connect to the hypervisor error: Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory root@host:~# virsh -c <Qemu URI> list Id Name State ------------------------- 2 VM running If I execute the virsh commands without "-c" option, then ubuntu 21.04 container would display the VM's running as same as hypervisor. Could you please help to manage this on the LXC ubuntu container? LIBVIRT xml used to spawn LXC ubuntu 21.04 container: <domain type='lxc'> <name>host</name> <uuid>096f46bf-80bb-4441-a512-043a9c7a64d4</uuid> <memory unit='KiB'>1048576</memory> <currentMemory unit='KiB'>1048576</currentMemory> <vcpu placement='static' cpuset='7'>1</vcpu> <os> <type arch='x86_64'>exe</type> <init>/sbin/init</init> </os> <features> <capabilities policy='allow'> <audit_control state='on'/> <audit_write state='on'/> <block_suspend state='on'/> <chown state='on'/> <ipc_lock state='on'/> <ipc_owner state='on'/> <kill state='on'/> <mac_admin state='on'/> <mac_override state='on'/> <mknod state='on'/> <net_admin state='on'/> <net_bind_service state='on'/> <net_broadcast state='on'/> <net_raw state='on'/> <sys_admin state='on'/> <sys_boot state='on'/> <sys_ptrace state='on'/> <sys_rawio state='on'/> <sys_resource state='on'/> <sys_time state='on'/> <syslog state='on'/> </capabilities> </features> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>destroy</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/lib64/libvirt/libvirt_lxc</emulator> <filesystem type='mount' accessmode='passthrough'> <source dir='/junos/lxc/jdm/jdm1/rootfs'/> <target dir='/'/> </filesystem> </devices> </domain> Thanks, Yuvaraj.

2 1

attach a pcie root port as hostdev
by Jiatong Shen 04 Aug '21

04 Aug '21

Hello community, I am working on plugging a xilinx fpga card as a hostdev. This fpga card has 2 functions, each has a different role, for some reason, I would like to attach both of them but do not want to attach them separately, so I have tried to attach a pci bridge where fpga cards connect to. but got the following error, error: Failed to attach device from bridge.xml error: internal error: Non-endpoint PCI devices cannot be assigned to guests so, my question is is it possible to attach a pci-bridge as hostdev? thank you. -- Best Regards, Jiatong Shen

2 2