- Users - libvirt List Archives

How to hot plugin a new vhost-user-blk-pci device to running VM?
by Liang Chaojun 13 May '21

13 May '21

Hi Guy, Does anyone clear how to hot plugin a new vhost-user-blk-pci device to a running VM? Before staring vm , I pass the disk through QEMU command line like below. <qemu:commandline> <qemu:arg value='-object'/> <qemu:arg value='memory-backend-file,id=mem0,size=4G,mem-path=/dev/hugepages,share=on'/> <qemu:arg value='-numa'/> <qemu:arg value='node,memdev=mem0'/> <qemu:arg value='-chardev'/> <qemu:arg value='socket,id=spdk_vhost_blk721ea46a-b306-11eb-a280-525400a98761,path=/var/tmp/vhost.721ea46a-b306-11eb-a280-525400a98761,reconnect=1'/> <qemu:arg value='-device'/> <qemu:arg value='vhost-user-blk-pci,chardev=spdk_vhost_blk721ea46a-b306-11eb-a280-525400a98761,bootindex=1,num-queues=4'/> <qemu:arg value='-chardev'/> <qemu:arg value='socket,id=spdk_vhost_blk2f699c58-d222-4629-9fdc-400c3aadc55e,path=/var/tmp/vhost.2f699c58-d222-4629-9fdc-400c3aadc55e,reconnect=1'/> <qemu:arg value='-device'/> <qemu:arg value='vhost-user-blk-pci,chardev=spdk_vhost_blk2f699c58-d222-4629-9fdc-400c3aadc55e,num-queues=4'/> </qemu:commandline> But I don’t know how to live add a vhost-user-blk-pci device on running VM even with calling attachDevice API now. OS: redhat 7.4 Libvirt version: 3.4 Your help will be appreciated. Thanks!

1 0

boot arm64 guest stuck
by Jiatong Shen 11 May '21

11 May '21

hello community, I am stuck at a problem where a virtual machine stuck at "guest has not initialized the display" on a arm64 (FT2000+) server and the relevant qemu process will continue to have a cpu usage of 100%. I do try with different qemu and qemu-efi combined and found out that if I use qemu build qemu-system-arm/now 1:2.11+dfsg-1ubuntu7.15~cloud1 arm64 with qemu-efi/now 0~20160408.ffea0a2c-2 all and set gic-version to 2, the vm could boot. the virtual machine uses a kylink 4.0 image. I am scrubbing my head to debug the bug and find out the reason... any idea or advice will be appreciated. thank you very much for the help -- Best Regards, Jiatong Shen

1 0

trying to understand how libvirt uses firewalld
by Felix Schwarz 30 Apr '21

30 Apr '21

Hi, I recently installed a test box using CentOS 8 and installed a CentOS 8 guest via libvirt (KVM). I need to use "routed" forwarding as the datacenter only gives me individual IPs which are routed to the physical interface and the switch only accepts packets with a well-known MAC address. On the host I enabled firewalld and moved the guest to a specific firewalld zone. I verified that libvirt is detecting firewalld. My idea was that I could use this to create somewhat fine-grained filters on the host for traffic from the internet to the guest (and possibly vice-versa). However it seems like that does not work the way I wanted: It seems as if nothing changes when I allow/disallow SSH for that zone. I can still ssh from the internet to the guest. After several reads on the documentation I have a guess of what might be going on but I'd like to confirm that: https://libvirt.org/firewall.html#fw-firewalld-and-virtual-network-driver > If firewalld is active on the host, libvirt will attempt to place the bridge > interface of a libvirt virtual network into the firewalld zone named > "libvirt" (thus making all guest->host traffic on that network subject to > the rules of the "libvirt" zone). Does that mean libvirt's firewalld usage is ONLY for traffic guest->host and does not affect all other traffic (e.g. host->guest, guest<->internet)? That sounds incredibly narrow (and not very useful for me) but it would explain why I don't see any effects in my experiment... --- In a related note it would be nice if there was a way to make routed setups with individual IPs easier. This problem hunts me for more than 10 years (I think I posted something in 2009 - still the same problem basically) and it would be nice if libvirt could somehow support this use case better: I want to allow traffic guest <-> internet in a routed setup. libvirt generates iptables rules like these: Chain LIBVIRT_FWO (1 references) pkts bytes target prot opt in out source destination 0 0 ACCEPT all -- br-private * 10.11.0.0/24 0.0.0.0/0 0 0 REJECT all -- br-private * 0.0.0.0/0 0.0.0.0/0 reject-with icmp-port-unreachable 0 0 ACCEPT all -- br-public * (NETWORK IP ) 0.0.0.0/0 43 3232 REJECT all -- br-public * 0.0.0.0/0 0.0.0.0/0 reject-with icmp-port-unreachable I my case "NETWORK IP" is a /32 IPv4 and AFAIK I have to put the host's IPv4 here (which is basically the router) so I can assign the guest IP inside the VM. What I need is basically a rule like ACCEPT one above but with the GUEST IP. I have some elaborate Python script which I can use as a "network" hook but that requires parsing output of "iptables" due to libvirt's events (e.g. libvirtd restart triggers one "plugged" event per VM). Thank you very much, Felix

1 0

l3 cache and cpu pinning
by Roman Mohr 24 Apr '21

24 Apr '21

Hi, I have a question regarding enabling l3 cache emulation on Domains. Can this also be enabled without cpu-pinning, or does it need cpu pinning to emulate the l3 caches according to the cpus where the guest is pinned to? Thank you and best regards, Roman

2 7

GlusterFS pools - do they work?
by lejeczek 22 Apr '21

22 Apr '21

Hi guys. I've been a consumer of libvirt for a while but this is first time I'm trying this: -> $ virsh vol-create-as glusterfs-VMs2 fcos-node1.qcow2 20G --format qcow2 error: Failed to create vol fcos-node1.qcow2 error: this function is not supported by the connection driver: storage pool does not support volume creation I'm on CentOS Stream with glusterfs-8.4, libvirt-7 and qemu-kvm-5.2.0 What might be the issue here? many thanks, L.

1 0

external snapshot create error
by Eyüp Hakan Duran 21 Apr '21

21 Apr '21

Dear all, I have been creating external snapshots of my KVM/QEMU VMs for more than a year on a host machine that runs Manjaro Linux. The current version of libvirt I am using is 1:7.1.0-3. I just noticed that the script I am using for this purpose has been failing. More specifically the command below returns with the error message indicated underneath the command: sudo virsh snapshot-create-as --no-metadata --domain myVM myVM-state --diskspec hda,file=overlay.qcow2 --disk-only --atomic error: XML document failed to validate against schema: Unable to validate doc against /usr/share/libvirt/schemas/domainsnapshot.rng Extra element disks in interleave Element domainsnapshot failed to validate content I also tried different versions of the command above with similar results, such as: sudo virsh snapshot-create-as mvVM --no-metadata myVM-state --diskspec hda,snapshot=external,file=overlay.qcow2 --disk-only --atomic Any pointers will be greatly appreciated! Hakan Duran

2 2

could not start libvirt service
by shafnamol N 15 Apr '21

15 Apr '21

Hi, I am using *CentOS 8*. I have built *libvirt* with the following method: $ meson build -Dsystem=true $ ninja -C build $ ninja -C build install But the problem is when i started it # systemctl start libvirtd Job for libvirtd.service failed because the control process exited with error code. See "systemctl status libvirtd.service" and "journalctl -xe" for details. i tried to get the status of libvirt # systemctl status libvirtd libvirtd.service - Virtualization daemon Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) What will be the problem? Thanks for the help in advanc....

3 3

Confusion over networking configuration - I might be able to do some documentation
by Ed B 13 Apr '21

13 Apr '21

Hi libvirt users, I have been using libvirt on Debian Linux for a few months. (Mostly with virt-manager. I haven't yet learned all of the command line commands.) I'm currently confused by bridge mode networking, which I think is what I require to address the particular use case, which I will describe: My use case: Prior to this I have been using routed mode to organize my VMs. Most of the VMs I deploy are for services (web servers, mail servers, etc) so I require them to have static IP addresses on my local network. ==== An aside / comment: I *can* set those static IPs using the command line virsh net-edit (from memory) command and then change the settings in the xml files. However, since this seems like something that many users would require regularly it would be nice to be able to set static IP in the GUI when configuring with virt-manager. I assume that the same people who maintain libvirt also maintain virt-manager? If I'm wrong please re-direct me. Returning to the main discussion: It would be more convenient for me personally if I were able to set the IP addresses of these VMs using static addresses configured via an external DHCP server. I believe I can do this if my network is in "bridge" mode instead of NAT or Routed. I know this should be possible from reading information online but there doesn't seem to be any option for this in the virt-manager GUI. ==== To give more details on my setup: My network has a pfsense instance which is able to provide IP addresses to local machines. I would like to use the same pfsense machine to provide IP addresses to virtual machines. If I am not mistaken, the only way to do this would be to bridge the network on which the VMs reside to the network on which the pfsense machine resides. I will provide some screenshots to illustrate my confusion. When creating a new virtual network, I assume that I do not want to enable DHCPv4, because I want the pfsense system to allocate IP addresses. I do not know whether I should leave "Enable ipv4 network address space definition" or what the value should be. See image below. [cid:4e926d97-7a58-4350-93cc-0db7c401c075] Further in the setup (step 4), I assume I need to choose "Forward to physical network" rather than "Isolated virtual network". For the destination option, I do not know what should be chosen. I don't fully understand how this option works. For "Mode" there are three options: NAT, Routed and finally "Open". I cannot find any documentation which indicates what "Open" means. NAT and Routed are clearly not the correct options here - by a process of elimination that would imply that "Open" means "bridged" but I have a feeling that this is incorrect and I don't understand something else. Again, see screengrab below. [cid:f2ea4e34-c418-48d3-86b2-d7ff1002990a] I am quite keen to contribute something to documentation. At the moment I don't understand enough about how libvirt works to be able to do this. Apologies if my questions have been directed to the wrong people. If this is the case could you please re-direct me to the right place to ask such questions? Best regards

3 2

move mount permission denied
by Jiatong Shen 12 Apr '21

12 Apr '21

Hello community! I am faced with a mysterious [error]( https://gist.github.com/jshen28/5f29eed51e0a1308684214b35f009478) which says move mount is not permissioned. We are using libvirt with openstack-helm which running libvirt in a docker based k8s environment. /dev/termination-log is a device created and attached by k8s and mount looks like `/dev/mapper/ubuntu--vg-root on /var/log/termination-log type ext4 (rw,relatime,errors=remount-ro,data=ordered)` Any idea why this happens? appreciate the help! -- Best Regards, Jiatong Shen

2 1

how to use external snapshots with memory state
by Riccardo Ravaioli 12 Apr '21

12 Apr '21

Hi all, Best wishes for 2021! :) So I've been reading and playing around with live snapshots and still haven't figured out how to use an external memory snapshot. My goal is to take a disk+memory snapshot of a running VM and, if possible, save it in external files. As far as I understand, I can run: $ virsh snapshot-create $VM ... and that'll take an *internal* live snapshot of a given VM, consisting of its disks and memory state, which will be stored in the qcow2 disk(s) of the VM. In particular, the memory state will be stored in the first disk of the VM. I can then use the full range of snapshot commands available: revert, list, current, delete. Now, an external snapshot can be taken with: $ virsh snapshot-create-as --domain $VM mysnapshot --diskspec vda,file=/home/riccardo/disk_mysnapshot.qcow2,snapshot=external --memspec file=/home/riccardo/mem_mysnapshot.qcow2,snapshot=external ... with as many "--diskspec" as there are disks in the VM. I've read the virsh manual and the libvirt API documentation, but it's not clear to me what exactly I can do then with an external snapshot, in particular with the file containing the memory state. In articles from 7-8 years ago people state that external memory snapshots cannot be reverted... is it still the case today? If so, what's a typical usage for such files? If not with libvirt, is it possible to revert to an external memory + disk state in other ways, for instance through qemu commands? Thanks! Riccardo

2 4

live migrate storage to different volume on the same host
by Jing-Wei Su 12 Apr '21

12 Apr '21

Hello experts, I would like to move the qcow2 disk images of a running VM to a different storage because of the maintenance of the underlying storage on the same host. I found the live migration is not allowable on the same host using virsh. Is there any suggestion or better practices for this? Thank you, Derek

2 1

libvirt 7.2.0 domainbackup
by Thomas Stein 12 Apr '21

12 Apr '21

Hello one and all. Just wanted to check out the new feature domainbackup but having trouble to configure it. I thought I just have to put <domainbackup> <disks> <disk name='vda' type='file'> <target file='/var/lib/libvirt/jitsi'/> <driver type='raw'/> </disk> </disks> </domainbackup> at the top level of my domain xml file but that does not seem to work. I get: error: XML document failed to validate against schema: Unable to validate doc against /usr/share/libvirt/schemas/domain.rng Element domain has extra content: domainbackup Can someone please push me in the right direction? cheers, t.

2 5

submitting a patch to fix documentation errors
by Tom Ammon 10 Apr '21

10 Apr '21

Hello, While using the libvirt application development guide for python ( https://libvirt.org/docs/libvirt-appdev-guide-python/en-US/html/index.html) I found a couple of errors in the example code that I'd like to fix. I've created a branch and committed the fixes locally, and I'm ready to push them. I plan to use git send-email to submit the patch. Which list should I use in the --to= ? Should it be libvirt-users(a)redhat.com? This is my first contribution to this project. I've read the best practices and contributing guidelines on libvirt.org, but if I make mistakes in the workflow I'd appreciate your help to correct them. Thanks! Tom -- ----------------------------------------------------------------------------- Tom Ammon M: (737) 400-9042 thomasammon(a)gmail.com -----------------------------------------------------------------------------

2 2

Creating Virtual machine with .OVF format
by Ajay Kumar 09 Apr '21

09 Apr '21

Hello members, I would like to create virtual machine images with some pre-installed software in a .*OVF/OVA* format. So that I can use these* OVF *images/templates for any hypervisor to create a VM. Do you have any suggestions or some available web scripts/links to do this..? Thanks, Ajay

3 2

XML for working mips64el guest
by Skyler Mäntysaari 08 Apr '21

08 Apr '21

Hi there, How do I get a working xml for mips64el guest when using virt-manager? The host system is running Ubuntu, but I believe that this is the right list for things relating to libvirt. It errors with: --------------------------------------------- Unable to complete install: 'this function is not supported by the connection driver: 'mips64el' architecture is not supported by CPU driver' Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 75, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/createvm.py", line 2089, in _do_async_install guest.installer_instance.start_install(guest, meter=meter) File "/usr/share/virt-manager/virtinst/install/installer.py", line 542, in start_install domain = self._create_guest( File "/usr/share/virt-manager/virtinst/install/installer.py", line 491, in _create_guest domain = self.conn.createXML(install_xml or final_xml, 0) File "/usr/lib/python3/dist-packages/libvirt.py", line 4034, in createXML if ret is None:raise libvirtError('virDomainCreateXML() failed', conn=self) libvirt.libvirtError: this function is not supported by the connection driver: 'mips64el' architecture is not supported by CPU driver --------------------------------------------- This is what I'm trying to use: --------------------------------------------- <domain type="qemu"> <name>debian9-mips64el</name> <metadata> <libosinfo:libosinfo xmlns:libosinfo="http://libosinfo.org/xmlns/libvirt/domain/1.0"> <libosinfo:os id="http://debian.org/debian/9"/> </libosinfo:libosinfo> </metadata> <memory>1048576</memory> <currentMemory>1048576</currentMemory> <vcpu>2</vcpu> <os> <type arch="mips64el" machine="malta">hvm</type> <cmdline>nokaslr root=/dev/sda1 console=ttyS0</cmdline> <boot dev="hd"/> </os> <clock offset="utc"/> <devices> <emulator>/usr/bin/qemu-system-mips64el</emulator> <controller type="pci" index="0" model="pci-root"/> <disk type="file" device="disk"> <driver name="qemu" type="qcow2"/> <source file="/var/lib/libvirt/images/mip64el/stretch/disk.qcow2"/> <target dev="hda" bus="ide"/> </disk> <interface type="network"> <source network="default"/> <mac address="52:54:00:c5:63:f5"/> </interface> <console type="pty"/> </devices> </domain> ---------------------------------------------------------------------------------------------------------------

1 0

Re: Regarding location of Libvirt library
by Andrea Bolognani 08 Apr '21

08 Apr '21

[once again, please keep replies on-list] On Wed, 2021-04-07 at 10:46 +0530, shafnamol N wrote: > > What does running > > > > $ ls /usr/lib/systemd/system/*virt* > > > > output? > > The output is as shown below: > > # ls /usr/lib/systemd/system/*virt* > /usr/lib/systemd/system/libvirtd-admin.socket /usr/lib/systemd/system/virtnodedevd.service > /usr/lib/systemd/system/libvirtd-ro.socket /usr/lib/systemd/system/virtnodedevd.socket > /usr/lib/systemd/system/libvirtd.service /usr/lib/systemd/system/virtnwfilterd-admin.socket > /usr/lib/systemd/system/libvirtd.service_backup /usr/lib/systemd/system/virtnwfilterd-ro.socket > /usr/lib/systemd/system/libvirtd.socket /usr/lib/systemd/system/virtnwfilterd.service > /usr/lib/systemd/system/libvirtd-tcp.socket /usr/lib/systemd/system/virtnwfilterd.socket > /usr/lib/systemd/system/libvirtd-tls.socket /usr/lib/systemd/system/virtproxyd-admin.socket > /usr/lib/systemd/system/libvirt-guests.service /usr/lib/systemd/system/virtproxyd-ro.socket > /usr/lib/systemd/system/virt-guest-shutdown.target /usr/lib/systemd/system/virtproxyd.service > /usr/lib/systemd/system/virtinterfaced-admin.socket /usr/lib/systemd/system/virtproxyd.socket > /usr/lib/systemd/system/virtinterfaced-ro.socket /usr/lib/systemd/system/virtproxyd-tcp.socket > /usr/lib/systemd/system/virtinterfaced.service /usr/lib/systemd/system/virtproxyd-tls.socket > /usr/lib/systemd/system/virtinterfaced.socket /usr/lib/systemd/system/virtqemud-admin.socket > /usr/lib/systemd/system/virtlockd-admin.socket /usr/lib/systemd/system/virtqemud-ro.socket > /usr/lib/systemd/system/virtlockd.service /usr/lib/systemd/system/virtqemud.service > /usr/lib/systemd/system/virtlockd.socket /usr/lib/systemd/system/virtqemud.socket > /usr/lib/systemd/system/virtlogd-admin.socket /usr/lib/systemd/system/virtsecretd-admin.socket > /usr/lib/systemd/system/virtlogd.service /usr/lib/systemd/system/virtsecretd-ro.socket > /usr/lib/systemd/system/virtlogd.socket /usr/lib/systemd/system/virtsecretd.service > /usr/lib/systemd/system/virtlxcd-admin.socket /usr/lib/systemd/system/virtsecretd.socket > /usr/lib/systemd/system/virtlxcd-ro.socket /usr/lib/systemd/system/virtstoraged-admin.socket > /usr/lib/systemd/system/virtlxcd.service /usr/lib/systemd/system/virtstoraged-ro.socket > /usr/lib/systemd/system/virtlxcd.socket /usr/lib/systemd/system/virtstoraged.service > /usr/lib/systemd/system/virtnetworkd-admin.socket /usr/lib/systemd/system/virtstoraged.socket > /usr/lib/systemd/system/virtnetworkd-ro.socket /usr/lib/systemd/system/virtvboxd-admin.socket > /usr/lib/systemd/system/virtnetworkd.service /usr/lib/systemd/system/virtvboxd-ro.socket > /usr/lib/systemd/system/virtnetworkd.socket /usr/lib/systemd/system/virtvboxd.service > /usr/lib/systemd/system/virtnodedevd-admin.socket /usr/lib/systemd/system/virtvboxd.socket > /usr/lib/systemd/system/virtnodedevd-ro.socket libvirtd.service_backup should not be there, but I don't think that's what causing your problem. I would still recommend deleting it just in case. > > What OS are you using? > > Centos 8 > > > What does the > > > > Miscellaneous > > ... > > Init script: XXX > > > > entry look like in the summary that's displayed when you run Meson? > > Miscellaneous > Init script : systemd These all look good, so I really have no idea what's going on. Hopefully someone else on the list will be able to help you! Good luck :) -- Andrea Bolognani / Red Hat / Virtualization

2 1

Xen: libvirt.libvirtError: An error occurred, but the cause is unknown
by Mathieu Tarral 08 Apr '21

08 Apr '21

Hi, I'm facing a strange issue with libvirt and the Xen driver. Whenever I try to define or start a domain, I always get this error: "libvirt.libvirtError: An error occurred, but the cause is unknown" (in Python virt-manager interface) Which is not very helpful. Trying to use virsh directly leads to the same error message: virsh # start win10_xen error: Failed to start domain win10_xen error: An error occurred, but the cause is unknown I checked /var/log/libvirt/libxl/libxl-driver.log, but the log file is empty. However, using the xl toolstack directly to start a new domain works fine, so the issue doesn't seem to come from Xen. My environment: - Ubuntu 20.04 LTS - xen-hypervisor-4.11-amd64 (4.11.3+24-g14b62ab3e5-1ubuntu2) - libvirt0 (6.0.0-0ubuntu8.8) I really like libvirt and virt-manager to manage my VMs. Any clue how I could dig deeper and find the root cause ? Thanks.

3 3

Live migration with change to setmaxmem
by Dariusz Smigiel 08 Apr '21

08 Apr '21

Hi Team, I need to migrate beefy instance between two different hosts which is running out of resources. I was wondering, if there is a way to change maximum memory value during live migration, without shutting down the instance. Thanks, Dariusz

2 2

Re: Regarding location of Libvirt library
by Andrea Bolognani 06 Apr '21

06 Apr '21

[please keep replies on-list] On Mon, 2021-04-05 at 12:03 +0530, shafnamol N wrote: > Hi, > I have build libvirt in the following method: > $ meson build -Dsystem=true > $ ninja -C build > When i tried to get the information via > > $pkg-config --cflags --libs libvirt > > it doesnt show anything. > > But I tried > $ninja -C build install > > and then > $pkg-config --cflags --libs libvirt > It shows like: > libvirt-7.1.0]# pkg-config --cflags --libs libvirt > -lvirt This is expected: pkg-config can't find the libvirt.pc file until you've installed it :) > But the problem is when i tried to get the status of libvirt > > # systemctl status libvirtd > ● libvirtd.service > Loaded: not-found (Reason: Unit libvirtd.service not found.) > Active: failed (Result: exit-code) > > I tried with > # systemctl daemon-reload > But the problem persists.. > what will be the problem... What does running $ ls /usr/lib/systemd/system/*virt* output? What does the Miscellaneous ... Init script: XXX entry look like in the summary that's displayed when you run Meson? What OS are you using? -- Andrea Bolognani / Red Hat / Virtualization

1 0

Virtual Network API for QEMU
by Radek Simko 04 Apr '21

04 Apr '21

Hi, According to this support matrix https://libvirt.org/hvsupport.html#virNetworkDriver there is no support for any APIs other than hypervisor ones for qemu. For example virConnectNumOfNetworks is not supported. Is there any particular reason this is not supported? Has any development in that area been attempted in the past? Would contributions adding support be welcomed? Thanks, Radek Simko

4 8

GlusterFS libgfapi with TLS
by lejeczek 02 Apr '21

02 Apr '21

Hi guys. I have KVM guests stored on glusterFS volume and I recently added TLS encryption to Gluster. What changes, tweaks are required at libvirtd/qemu's end? many thanks, L.

2 2

Regarding location of Libvirt library
by shafnamol N 01 Apr '21

01 Apr '21

Hi, I have installed Libvirt 7.1.0. I configured and built libvirt based on instructions from https://libvirt.org/compiling.html. Now I developed a client program to create a VM using an XML file.As the API for it is *virDomainCreateXML,* called this API by passing XML file .It shows the following error. undefined reference to `virDomainCreateXML'. I included the header files containing the said API declaration.But need to include the library also. My question is where do the libvirt library located after building it. Thanks for the help in advance.

3 2

virsh dommemstat doesn't update its information
by Lentes, Bernd 30 Mar '21

30 Mar '21

Hi, i'm playing a bit around with my domains and the balloon driver. To get information about ballooning i use virsh dommemstat. But i only get very few information: virsh # dommemstat vm_idcc_devel actual 1044480 last_update 0 rss 1030144 Also configuring "dommemstat --domain vm_idcc_devel --period 5 --live" or "dommemstat --domain vm_idcc_devel --period 5 --current" does neither update nor extend the information. In vm_idcc_devel virtio_balloon is loaded: idcc-devel:~ # lsmod|grep balloon virtio_balloon 22788 0 Guest OS is SLES 10 SP4. Is that too old ? Host OS is SLES 12 SP5. There are other domains in which the information is updated. Here is the config from vm_idcc_devel: virsh # dumpxml vm_idcc_devel <domain type='kvm' id='7'> <name>vm_idcc_devel</name> <uuid>4993009b-42ff-45d9-b1e0-145b8c0c8f82</uuid> <memory unit='KiB'>2044928</memory> <currentMemory unit='KiB'>1044480</currentMemory> <vcpu placement='static'>1</vcpu> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-1.4'>hvm</type> <boot dev='hd'/> <boot dev='cdrom'/> <bootmenu enable='yes'/> </os> <features> <acpi/> <apic/> </features> <clock offset='localtime'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/bin/qemu-kvm</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='none'/> <source file='/mnt/ocfs2/vm_idcc_devel.raw'/> <backingStore/> <target dev='vdb' bus='ide'/> <alias name='ide0-0-0'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu'/> <target dev='hdc' bus='ide'/> <readonly/> <alias name='ide0-1-0'/> <address type='drive' controller='0' bus='1' target='0' unit='0'/> </disk> <controller type='usb' index='0' model='piix3-uhci'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <controller type='ide' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <interface type='bridge'> <mac address='52:54:00:37:92:05'/> <source bridge='br0'/> <target dev='vnet6'/> <model type='rtl8139'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/6'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/6'> <source path='/dev/pts/6'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <input type='mouse' bus='ps2'> <alias name='input0'/> </input> <input type='keyboard' bus='ps2'> <alias name='input1'/> </input> <graphics type='vnc' port='5902' autoport='no' listen='127.0.0.1'> <listen type='address' address='127.0.0.1'/> </graphics> <video> <model type='cirrus' vram='16384' heads='1' primary='yes'/> <alias name='video0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <memballoon model='virtio'> <stats period='5'/> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </memballoon> </devices> </domain> Bernd -- Bernd Lentes System Administrator Institute for Metabolism and Cell Death (MCD) Building 25 - office 122 HelmholtzZentrum München bernd.lentes(a)helmholtz-muenchen.de phone: +49 89 3187 1241 phone: +49 89 3187 3827 fax: +49 89 3187 2294 http://www.helmholtz-muenchen.de/mcd Public key: 30 82 01 0a 02 82 01 01 00 b3 72 3e ce 2c 0a 6f 58 49 2c 92 23 c7 b9 c1 ff 6c 3a 53 be f7 9e e9 24 b7 49 fa 3c e8 de 28 85 2c d3 ed f7 70 03 3f 4d 82 fc cc 96 4f 18 27 1f df 25 b3 13 00 db 4b 1d ec 7f 1b cf f9 cd e8 5b 1f 11 b3 a7 48 f8 c8 37 ed 41 ff 18 9f d7 83 51 a9 bd 86 c2 32 b3 d6 2d 77 ff 32 83 92 67 9e ae ae 9c 99 ce 42 27 6f bf d8 c2 a1 54 fd 2b 6b 12 65 0e 8a 79 56 be 53 89 70 51 02 6a eb 76 b8 92 25 2d 88 aa 57 08 42 ef 57 fb fe 00 71 8e 90 ef b2 e3 22 f3 34 4f 7b f1 c4 b1 7c 2f 1d 6f bd c8 a6 a1 1f 25 f3 e4 4b 6a 23 d3 d2 fa 27 ae 97 80 a3 f0 5a c4 50 4a 45 e3 45 4d 82 9f 8b 87 90 d0 f9 92 2d a7 d2 67 53 e6 ae 1e 72 3e e9 e0 c9 d3 1c 23 e0 75 78 4a 45 60 94 f8 e3 03 0b 09 85 08 d0 6c f3 ff ce fa 50 25 d9 da 81 7b 2a dc 9e 28 8b 83 04 b4 0a 9f 37 b8 ac 58 f1 38 43 0e 72 af 02 03 01 00 01

2 1

how to check a virtual disk
by Lentes, Bernd 29 Mar '21

29 Mar '21

Hi, we have a two-node cluster with pacemaker a SAN. The resources are inside virtual domains. The images of the virtual disks reside on the SAN. On one domain i have errors from the hd in my log: 2021-03-24T21:02:28.416504+01:00 geneious kernel: [2159685.909613] JBD2: Detected IO errors while flushing file data on dm-1-8 2021-03-24T21:02:46.505323+01:00 geneious kernel: [2159704.012213] JBD2: Detected IO errors while flushing file data on dm-1-8 2021-03-24T21:02:55.573149+01:00 geneious kernel: [2159713.078560] JBD2: Detected IO errors while flushing file data on dm-1-8 2021-03-24T21:03:23.702946+01:00 geneious kernel: [2159741.202546] JBD2: Detected IO errors while flushing file data on dm-1-8 2021-03-24T21:03:30.289606+01:00 geneious kernel: [2159747.796192] ------------[ cut here ]------------ 2021-03-24T21:03:30.289635+01:00 geneious kernel: [2159747.796207] WARNING: CPU: 0 PID: 457 at ../fs/buffer.c:1108 mark_buffer_dirty+0xe8/0x100 2021-03-24T21:03:30.289637+01:00 geneious kernel: [2159747.796208] Modules linked in: st sr_mod cdrom lp parport_pc ppdev parport xfrm_user xfrm_algo binfmt_misc uinput nf_log_ipv6 xt_comme nt nf_log_ipv4 nf_log_common xt_LOG xt_limit af_packet iscsi_ibft iscsi_boot_sysfs ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT xt_pkttype xt_tcpudp iptable_filter ip6table_mangl e nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_ipv4 nf_defrag_ipv4 ip_tables xt_conntrack nf_conntrack libcrc32c ip6table_filter ip6_tables x_tables joydev virtio_net net_fai lover failover virtio_balloon i2c_piix4 qemu_fw_cfg pcspkr button ext4 crc16 jbd2 mbcache ata_generic hid_generic usbhid ata_piix sd_mod virtio_rng ahci floppy libahci serio_raw ehci_pci bo chs_drm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops ttm drm uhci_hcd ehci_hcd usbcore virtio_pci 2021-03-24T21:03:30.289637+01:00 geneious kernel: [2159747.796374] drm_panel_orientation_quirks libata dm_mirror dm_region_hash dm_log sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_ dh_alua scsi_mod autofs4 [last unloaded: parport_pc] 2021-03-24T21:03:30.289643+01:00 geneious kernel: [2159747.796400] Supported: Yes 2021-03-24T21:03:30.289644+01:00 geneious kernel: [2159747.796405] CPU: 0 PID: 457 Comm: jbd2/dm-0-8 Not tainted 4.12.14-122.57-default #1 SLE12-SP5 2021-03-24T21:03:30.289644+01:00 geneious kernel: [2159747.796406] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.12.0-0-ga698c89-rebuilt.suse.com 04/01/2014 2021-03-24T21:03:30.289645+01:00 geneious kernel: [2159747.796407] task: ffff8ba32766c380 task.stack: ffff99954124c000 2021-03-24T21:03:30.289645+01:00 geneious kernel: [2159747.796409] RIP: 0010:mark_buffer_dirty+0xe8/0x100 2021-03-24T21:03:30.289646+01:00 geneious kernel: [2159747.796409] RSP: 0018:ffff99954124fcf0 EFLAGS: 00010246 2021-03-24T21:03:30.289650+01:00 geneious kernel: [2159747.796413] RAX: 0000000000a20828 RBX: ffff8ba209a58d90 RCX: ffff8ba3292d7958 2021-03-24T21:03:30.289651+01:00 geneious kernel: [2159747.796413] RDX: ffff8ba209a585b0 RSI: ffff8ba24270b690 RDI: ffff8ba3292d7958 2021-03-24T21:03:30.289652+01:00 geneious kernel: [2159747.796414] RBP: ffff8ba3292d7958 R08: ffff8ba209a585b0 R09: 0000000000000001 2021-03-24T21:03:30.289652+01:00 geneious kernel: [2159747.796415] R10: ffff8ba328c1c0b0 R11: ffff8ba287805380 R12: ffff8ba3292d795a 2021-03-24T21:03:30.289653+01:00 geneious kernel: [2159747.796415] R13: 0000000000000000 R14: ffff8ba3292d7958 R15: ffff8ba209a58d90 2021-03-24T21:03:30.289653+01:00 geneious kernel: [2159747.796417] FS: 0000000000000000(0000) GS:ffff8ba333c00000(0000) knlGS:0000000000000000 2021-03-24T21:03:30.289654+01:00 geneious kernel: [2159747.796417] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 2021-03-24T21:03:30.289654+01:00 geneious kernel: [2159747.796418] CR2: 0000000099bff000 CR3: 0000000101b06000 CR4: 00000000000006f0 2021-03-24T21:03:30.289655+01:00 geneious kernel: [2159747.796424] Call Trace: 2021-03-24T21:03:30.289656+01:00 geneious kernel: [2159747.796470] __jbd2_journal_refile_buffer+0xbb/0xe0 [jbd2] 2021-03-24T21:03:30.289656+01:00 geneious kernel: [2159747.796479] jbd2_journal_commit_transaction+0xf1a/0x1870 [jbd2] 2021-03-24T21:03:30.289657+01:00 geneious kernel: [2159747.796489] ? __switch_to_asm+0x41/0x70 2021-03-24T21:03:30.289658+01:00 geneious kernel: [2159747.796490] ? __switch_to_asm+0x35/0x70 2021-03-24T21:03:30.289662+01:00 geneious kernel: [2159747.796493] kjournald2+0xbb/0x230 [jbd2] 2021-03-24T21:03:30.289663+01:00 geneious kernel: [2159747.796499] ? wait_woken+0x80/0x80 2021-03-24T21:03:30.289663+01:00 geneious kernel: [2159747.796503] kthread+0xf6/0x130 2021-03-24T21:03:30.289664+01:00 geneious kernel: [2159747.796508] ? commit_timeout+0x10/0x10 [jbd2] 2021-03-24T21:03:30.289664+01:00 geneious kernel: [2159747.796510] ? kthread_bind+0x10/0x10 2021-03-24T21:03:30.289665+01:00 geneious kernel: [2159747.796511] ret_from_fork+0x35/0x40 2021-03-24T21:03:30.289665+01:00 geneious kernel: [2159747.796517] Code: 1b 48 8b 03 48 8b 7b 08 48 83 c3 18 48 89 ee e8 bf 42 76 00 48 8b 03 48 85 c0 75 e8 e9 3c ff ff ff 48 89 df 5b 5d e9 c8 35 fb ff <0f> 0b e9 26 ff ff ff 48 83 e8 01 e9 5b ff ff ff 0f 1f 84 00 00 2021-03-24T21:03:30.289670+01:00 geneious kernel: [2159747.796533] ---[ end trace db796891c8ff94af ]--- 2021-03-24T21:03:46.593225+01:00 geneious kernel: [2159764.100145] JBD2: Detected IO errors while flushing file data on dm-1-8 2021-03-24T21:05:09.372772+01:00 geneious kernel: [2159846.877201] JBD2: Detected IO errors while flushing file data on dm-1-8 2021-03-24T21:06:39.943519+01:00 geneious kernel: [2159937.381068] JBD2: Detected IO errors while flushing file data on dm-1-8 2021-03-24T21:07:42.364311+01:00 geneious kernel: [2159999.793805] JBD2: Detected IO errors while flushing file data on dm-1-8 2021-03-24T21:07:57.822133+01:00 geneious kernel: [2160015.291776] JBD2: Detected IO errors while flushing file data on dm-1-8 First i'm wondering: what is dm-1-8 ? I don't have a device like that. geneious:~ # find /dev -iname '*dm*' /dev/dm-1 /dev/dm-0 /dev/disk/by-id/dm-uuid-LVM-a9Cy1cweHgXlAEECqZL5KZBfnuigUG6lq0ntdZJxxLIIp5G8XihsuYrTbx7Rs0vc /dev/disk/by-id/dm-name-vg_local-lv_var /dev/disk/by-id/dm-uuid-LVM-a9Cy1cweHgXlAEECqZL5KZBfnuigUG6l3fdsOpBFoDWral3Fa7c6ZeYECmLd6FFj /dev/disk/by-id/dm-name-vg_local-lv_root /dev/cpu_dma_latency I just find /proc/fs/jbd2/dm-1-8. There is a file /proc/fs/jbd2/dm-1-8/info: 453005 transactions (319055 requested), each up to 8192 blocks average: 0ms waiting for transaction 12ms request delay 5124ms running transaction 0ms transaction was being locked 0ms flushing data (in ordered mode) 44ms logging transaction 8031us average transaction commit time 64 handles per transaction 5 blocks per transaction 6 logged blocks per transaction What is that ? The logfile says also something about dm-0-8: 2021-03-24T21:03:30.289644+01:00 geneious kernel: [2159747.796405] CPU: 0 PID: 457 Comm: jbd2/dm-0-8 Not tainted 4.12.14-122.57-default #1 SLE12-SP5 geneious:~ # find / -iname dm-0-8 /proc/fs/jbd2/dm-0-8 geneious:~ # ll /proc/fs/jbd2/dm-0-8 total 0 -r--r--r-- 1 root root 0 Mar 29 12:56 info geneious:~ # cat /proc/fs/jbd2/dm-0-8/info 7356 transactions (556 requested), each up to 8192 blocks average: 0ms waiting for transaction 20ms request delay 5628ms running transaction 4ms transaction was being locked 0ms flushing data (in ordered mode) 132ms logging transaction 134769us average transaction commit time 52 handles per transaction 18 blocks per transaction 19 logged blocks per transaction geneious:~ # I assume i have a harddisk problem. I'm checking currently the SAN with its own tools, via a web interface. Afterwards i want to stop the domain, boot it with a live cd and run badblocks and fsck.ext3. What else can i do ? Bernd -- Bernd Lentes System Administrator Institute for Metabolism and Cell Death (MCD) Building 25 - office 122 HelmholtzZentrum München bernd.lentes(a)helmholtz-muenchen.de phone: +49 89 3187 1241 phone: +49 89 3187 3827 fax: +49 89 3187 2294 http://www.helmholtz-muenchen.de/mcd Public key: 30 82 01 0a 02 82 01 01 00 b3 72 3e ce 2c 0a 6f 58 49 2c 92 23 c7 b9 c1 ff 6c 3a 53 be f7 9e e9 24 b7 49 fa 3c e8 de 28 85 2c d3 ed f7 70 03 3f 4d 82 fc cc 96 4f 18 27 1f df 25 b3 13 00 db 4b 1d ec 7f 1b cf f9 cd e8 5b 1f 11 b3 a7 48 f8 c8 37 ed 41 ff 18 9f d7 83 51 a9 bd 86 c2 32 b3 d6 2d 77 ff 32 83 92 67 9e ae ae 9c 99 ce 42 27 6f bf d8 c2 a1 54 fd 2b 6b 12 65 0e 8a 79 56 be 53 89 70 51 02 6a eb 76 b8 92 25 2d 88 aa 57 08 42 ef 57 fb fe 00 71 8e 90 ef b2 e3 22 f3 34 4f 7b f1 c4 b1 7c 2f 1d 6f bd c8 a6 a1 1f 25 f3 e4 4b 6a 23 d3 d2 fa 27 ae 97 80 a3 f0 5a c4 50 4a 45 e3 45 4d 82 9f 8b 87 90 d0 f9 92 2d a7 d2 67 53 e6 ae 1e 72 3e e9 e0 c9 d3 1c 23 e0 75 78 4a 45 60 94 f8 e3 03 0b 09 85 08 d0 6c f3 ff ce fa 50 25 d9 da 81 7b 2a dc 9e 28 8b 83 04 b4 0a 9f 37 b8 ac 58 f1 38 43 0e 72 af 02 03 01 00 01

2 3

vcenter on esxi on KVM on RHEL8
by Nicholas Hardiman 29 Mar '21

29 Mar '21

I tried something new at the weekend - I created a lab for ansible experiments. One PC, two ESXi VMs, some nested guests. Is this a sensible thing to attempt? vcenter ubuntu1 ubuntu2 ------- ------- ------- ESXi1 ESXI2 ---------------- ------------- KVM -------------------------------- RHEL 8 -------------------------------- ASUS PN50 Everything within ESXi1 works fine, but communication with the outside world is not fine. Before I get into troubleshooting details, I thought I'd just check if this is a reasonable thing to do, or if I'm heading in the wrong direction. Thanks, Nick -- Nick Hardiman, RHCA Senior Consultant Red Hat <https://www.redhat.com/> nhardima(a)redhat.com M: 07585-206195 Upcoming PTO: - Upcoming Training: Mon 8 - Fri 12 March <https://www.redhat.com/>

1 0