January 2022 - Users - libvirt List Archives

unsubscribe
by FRANK, Michael 11 Jan '22

11 Jan '22

unsubscribe The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, please notify Airbus immediately and delete this e-mail. Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately. All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free.

1 0

error during host deploy
by Dana Elfassy 11 Jan '22

11 Jan '22

Hi, While running a test case of adding hosts on ovirt system tests there was a failure while the following command was executed: vdsm-tool configure --force On libvirtd log I found this error: 2021-12-17 00:11:41.753+0000: 28031: error : virNetTLSContextNew:732 : Unable to generate diffie-hellman parameters: Error in public key generation. How would you suggest to debug this failure? attaching libvirtd & journalctl logs libvirt version: 7.10.0, package: 1.module_el8.6.0+1046+bd8eec5e Thanks, Dana The error from host deploy log: "2021-12-17 01":"11":"45 CET - fatal":[ ost-basic-suite-master-host-0 ]:"FAILED! =>"{ "changed":true, "cmd":[ "vdsm-tool", "configure", "--force" ], "delta":"0:00:06.908971", "end":"2021-12-17 01:11:42.815057", "msg":"non-zero return code", "rc":1, "start":"2021-12-17 01:11:35.906086", "stderr":"Error: ServiceOperationError: _systemctlStart failed\nb'Job for libvirtd.service failed because a fatal signal was delivered causing the control process to dump core.\\nSee \"systemctl status libvirtd.service\" and \"journalctl -xe\" for details.\\n' ", "stderr_lines":[ "Error: ServiceOperationError: _systemctlStart failed", "b'Job for libvirtd.service failed because a fatal signal was delivered causing the control process to dump core.\\nSee \"systemctl status libvirtd.service\" and \"journalctl -xe\" for details.\\n' " ], "stdout":"\nChecking configuration status...\n\nlvm is configured for vdsm\nCurrent revision of multipath.conf detected, preserving\nlibvirt is already configured for vdsm\nSUCCESS: ssl configured to true. No conflicts\nsanlock is configured for vdsm\nManaged volume database is already configured\n\nRunning configure...\nReconfiguration of libvirt is done.\nReconfiguration of passwd is done.", "stdout_lines":[ "", "Checking configuration status...", "", "lvm is configured for vdsm", "Current revision of multipath.conf detected, preserving", "libvirt is already configured for vdsm", "SUCCESS: ssl configured to true. No conflicts", "sanlock is configured for vdsm", "Managed volume database is already configured", "", "Running configure...", "Reconfiguration of libvirt is done.", "Reconfiguration of passwd is done." ] }

2 8

回复： Failed in using LD_PRELOAD to hook mmap system call in qemu(through libvirt)
by Xiong。 07 Jan '22

07 Jan '22

On Thu, Jan 06, 2022 at 07:44:25PM +0800, Xiong。 wrote: > Dear sir: >     I want to hook mmap system call in qemu, and I use > libvirt to passthrough the environment argument like this: >  <qemu:commandline> >    <qemu:env name='LD_PRELOAD' value='/glibcHookMMAP.so'/> >  </qemu:commandline> > But it failed. I can hardly find out what is the matter! > The log in libvirt like this:ERROR: ld.so: object > '/glibcHookMMAP.so' from LD_PRELOAD cannot be preloaded > (cannot open shared object file): ignored.    Firstly, > I think it's the problem of authority. But the file > glibcHookMMAP.so has been done with command `chmod 777`. > My environment is as follows: Ubuntu 18.04.2 Linux > 5.4.0-92 libvirt 4.0.0 qemu 2.11.1 On Thu, Jan 06, 2022 at 09:47:25PM +0800, Daniel P. Berrangé。 wrote: > Aside from normal file permissions, the other likely problem on Ubuntu > will be AppArmor policy. It likely won't allow QEMU to load files from > the / directory - if you put your .so in /usr/local/lib it might > work. On Thu, Jan 07, 2022 at 09:27:25AM +0800, Xiong。 wrote: > I have a try, but it does not work and makes the same warning: > ld.so: object '/usr/local/lib/glibcHookMMAP.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. > However, I use qemu command directly and it works. Command is like this: > sudo LD_PRELOAD=/usr/local/lib/glibcHookMMAP.so qemu-system-x86_64 -enable-kvm ...(other args). > After that, I get print information with my hook program. And I think the problem is in passing the environment args in libvirt. Sorry, I find out what's the matter. The AppArmor policy limits the libvirt, and modifing configuration works. Thank you for your advise!

1 0

Failed in using LD_PRELOAD to hook mmap system call in qemu(through libvirt)
by Xiong。 07 Jan '22

07 Jan '22

Dear sir:      I want to hook mmap system call in qemu, and I use libvirt to passthrough the environment argument like this:<qemu:commandline> <qemu:env name='LD_PRELOAD' value='/glibcHookMMAP.so'/> </qemu:commandline>    But it failed. I can hardly find out what is the matter! The log in libvirt like this:ERROR: ld.so: object '/glibcHookMMAP.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.    Firstly, I think it's the problem of authority. But the file glibcHookMMAP.so has been done with command `chmod 777`.    My environment is as follows: Ubuntu 18.04.2 Linux 5.4.0-92 libvirt 4.0.0 qemu 2.11.1     Look forward to your feedbacks.     Sincerely yours

2 2

config vhost-user-scsi
by Jiatong Shen 06 Jan '22

06 Jan '22

Hello, I am trying spdk vhost-user. I managed to plug in vhost-user-blk, but did not find the doc guiding me through setting up vhost-user-scsi. Is it supported now? Thank you. -- Best Regards, Jiatong Shen

1 0

Allow unsafe migration - ?
by lejeczek 05 Jan '22

05 Jan '22

Hi guys. Is it possible to allow 'unsafe' migration globally? many thanks, L.

3 4

simulating multiple hypervisors with the test driver
by Tom Ammon 05 Jan '22

05 Jan '22

Hello, I'm working on a python application that will manage multiple remote libvirt hypervisors. I've been using the test:///default uri for single-hypervisor tests, and it works great. I'd like to simulate connecting to two different remote hypervisors, however, in my testing so far it appears that multiple connections to the test:///default uri just look like different connections to the same hypervisor. Here's what I tried : conn_one = libvirt.open('test:///default') <build and start some domains> one_vms = conn_one.listAllDomains(0) for x in one_vms: print(f"The vm in set one is {x.name()}") <get list of all the domains I just built> conn_two = libvirt.open('test:///default') <build and start some different domains> two_vms = conn_two.listAllDomains(0) for z in two_vms: print(f"The vm in set one is {z.name()}") <get list of ALL domains including those created with conn_one, not just those created using the conn_two instance> What I would like is to be able to spin up two completely independent instances of the test driver so that it can simulate two different hypervisors/instances of libvirtd. Is that possible? Thanks, Tom -- ----------------------------------------------------------------------------- Tom Ammon M: (737) 400-9042 thomasammon(a)gmail.com -----------------------------------------------------------------------------

2 2

Best way to install guest when it is not listed in output of osinfo-query os
by john doe 04 Jan '22

04 Jan '22

Hello all, I would like to install Debian Bullseye using virt-install, as part of the command I usually specify the OS used with the option '--os-variant'. This works great untill Buster ('debian10'), but now the guest is Bullseye ('debian11') and is not listed in the output of 'osinfo-query os' (1). If I don't use the '--os-variant' flag I get the following warning: "WARNING No operating system detected, VM performance may suffer. Specify an OS with --os-variant for optimal results." Should I ignore the warning or what is the best way forward to install a Debian Bullseye guest? Both the host and the guest are Debian 11. 1) https://lists.debian.org/debian-user/2021/12/msg00742.html -- John Doe

5 6