Re: [libvirt-users] Determining domain job kind from job stats?

Jiri Denemark <jdene...@redhat.com> writes: > On Fri, Feb 17, 2017 at 12:38:24 +0100, Milan Zamazal wrote: >> Jiri Denemark <jdene...@redhat.com> writes: >> >> > On Fri, Feb 10, 2017 at 21:50:19 +0100, Milan Zamazal wrote: >> >> Hi, is there a r

[libvirt-users] Determining domain job kind from job stats?

Hi, is there a reliable way to find out to what kind of job does the information returned from virDomainGetJobStats or provided in VIR_DOMAIN_EVENT_ID_JOB_COMPLETED event callback belong to? I'm specifically interested in distinguishing host-to-host migration jobs (e.g. those started by

Re: [libvirt-users] Determining domain job kind from job stats?

Jiri Denemark <jdene...@redhat.com> writes: > On Fri, Feb 10, 2017 at 21:50:19 +0100, Milan Zamazal wrote: >> Hi, is there a reliable way to find out to what kind of job does the >> information returned from virDomainGetJobStats or provided in >> VIR_DOMAIN_EVENT_ID_J

Re: [libvirt-users] VIR_ERR_OPERATION_INVALID from virDomainDestroyFlags call

"Daniel P. Berrange" <berra...@redhat.com> writes: > On Fri, Mar 17, 2017 at 11:55:13AM +0100, Milan Zamazal wrote: >> Hi, we experienced a strange, non-reproducible error after a successful >> migration to another host. When we called virDomainDestroyFlags with

[libvirt-users] VIR_ERR_OPERATION_INVALID from virDomainDestroyFlags call

Hi, we experienced a strange, non-reproducible error after a successful migration to another host. When we called virDomainDestroyFlags with VIR_DOMAIN_DESTROY_GRACEFUL flag after the migration on the source host, we got VIR_ERR_OPERATION_INVALID (code 55) error. The same with repeated

Re: [libvirt-users] VIR_ERR_OPERATION_INVALID from virDomainDestroyFlags call

"Daniel P. Berrange" <berra...@redhat.com> writes: > On Fri, Mar 17, 2017 at 02:07:11PM +0100, Milan Zamazal wrote: >> "Daniel P. Berrange" <berra...@redhat.com> writes: >> >> > On Fri, Mar 17, 2017 at 11:55:13AM +0100, Milan Zamazal wro

[libvirt-users] Device lease hot unplug and events

Hi, when working on hot unplugs of various devices, I've found out that hot unplugging device doesn't generate VIR_DOMAIN_EVENT_ID_DEVICE_REMOVED event. also doesn't have an alias, so it wouldn't be identifiable in the corresponding callback. Is this difference from other hotpluggable devices

Re: [libvirt-users] Device lease hot unplug and events

Peter Krempa writes: > On Mon, Oct 15, 2018 at 09:56:39 +0200, Milan Zamazal wrote: >> Peter Krempa writes: >> > >> > On Fri, Oct 12, 2018 at 19:33:54 +0200, Milan Zamazal wrote: >> >> Hi, when working on hot unplugs of various devices, I've found out th

Re: [libvirt-users] Device lease hot unplug and events

Peter Krempa writes: > On Fri, Oct 12, 2018 at 19:33:54 +0200, Milan Zamazal wrote: >> Hi, when working on hot unplugs of various devices, I've found out that >> hot unplugging device doesn't generate >> VIR_DOMAIN_EVENT_ID_DEVICE_REMOVED event. also doesn't have an >

Re: [libvirt-users] Which objects does dynamic_ownership apply to?

Michal Prívozník writes: > On 09/19/2018 12:39 PM, Milan Zamazal wrote: >> Hi, I'm playing with dynamic ownership and not all objects have their >> owners changed. > >> >> Is dynamic_ownership and its scope documented somewhere, besides the >> comment

Re: [libvirt-users] Which objects does dynamic_ownership apply to?

Michal Privoznik writes: > On 09/20/2018 12:31 PM, Milan Zamazal wrote: >> Michal Prívozník writes: >> > >>> On 09/19/2018 12:39 PM, Milan Zamazal wrote: >>>> Hi, I'm playing with dynamic ownership and not all objects have their >>>> owners

Re: [libvirt-users] Usable and non-usable CPU models in nested virtualization

Thank you for explanation, it's clear to me now. One last question: Is there a way to get supported compatibility modes on POWER? For instance, I get the following from domcapabilities on a POWER9 machine: POWER9 IBM How can I find out that POWER8 guests

Re: [libvirt-users] Usable and non-usable CPU models in nested virtualization

Jiri Denemark writes: > On Fri, Dec 07, 2018 at 11:52:38 +0100, Milan Zamazal wrote: >> Hi, some custom CPU models are reported from >> virConnectGetDomainCapabilities as usable='yes' on a physical machine > >> while as usable='no' inside a VM running on t

[libvirt-users] Usable and non-usable CPU models in nested virtualization

Hi, some custom CPU models are reported from virConnectGetDomainCapabilities as usable='yes' on a physical machine while as usable='no' inside a VM running on the same machine. That's not completely surprising. But what surprises me is that those models are still reported from

[libvirt-users] How to get list of CPUs compatible with the host CPU and vendor?

Hi, I'm trying to use virConnectGetDomainCapabilities to get the list of CPUs compatible with the host CPU. I would like to further limit the list to CPUs of the same vendor as the host CPU. How can I do that? I tried to use virConnectBaselineCPU with element and checking whether I obtain the

[libvirt-users] Which objects does dynamic_ownership apply to?

Hi, I'm playing with dynamic ownership and not all objects have their owners changed. Is dynamic_ownership and its scope documented somewhere, besides the comment in qemu.conf? And what kinds of objects are handled by dynamic ownership? While some objects seem to be handled, other objects are

[libvirt-users] Certificate checking on TLS migrations to an IP address

Hi, I'm trying to add TLS migrations to oVirt, but I've hit a problem with certificate checking. oVirt uses the destination host IP address, rather than the host name, in the migration URI passed to virDomainMigrateToURI3. One reason for doing that is that a separate migration network may be

Re: [libvirt-users] Certificate checking on TLS migrations to an IP address

Daniel P. Berrangé writes: > On Wed, Sep 04, 2019 at 03:38:25PM +0200, Milan Zamazal wrote: >> Hi, I'm trying to add TLS migrations to oVirt, but I've hit a problem >> with certificate checking. > >> >> oVirt uses the destination host IP address, rather than the

Re: [libvirt-users] Certificate checking on TLS migrations to an IP address

Daniel P. Berrangé writes: > On Wed, Sep 18, 2019 at 12:18:32PM +0200, Milan Zamazal wrote: >> Daniel P. Berrangé writes: >> > >> > On Wed, Sep 04, 2019 at 03:38:25PM +0200, Milan Zamazal wrote: >> >> Hi, I'm trying to add TLS migrations to oVirt, but I'

Re: [libvirt-users] Descriptions of mdev types?

Erik Skultety writes: > On Tue, Nov 19, 2019 at 05:38:54PM +0100, Milan Zamazal wrote: >> Hi, when retrieving an mdev device info using `virsh nodedev-dumpxml' or >> the libvirt API, something like the following is returned: > >> >> >> >>

[libvirt-users] Descriptions of mdev types?

Hi, when retrieving an mdev device info using `virsh nodedev-dumpxml' or the libvirt API, something like the following is returned: GRID M60-2B4 vfio-pci 4 ... Besides device_api, available_instances and (optional) `name', `description' of

Re: [libvirt-users] Certificate checking on TLS migrations to an IP address

Milan Zamazal writes: > Daniel P. Berrangé writes: > >> On Wed, Sep 18, 2019 at 12:18:32PM +0200, Milan Zamazal wrote: >>> Daniel P. Berrangé writes: >>> >> >>> > On Wed, Sep 04, 2019 at 03:38:25PM +0200, Milan Zamazal wrote: >>> >&

Re: How to detect completion of a paused VM migration on the destination?

Michal Privoznik writes: > On 1/21/20 3:28 PM, Milan Zamazal wrote: >> Hi, >> > >> when a normally running VM is migrated, libvirt sends >> VIR_DOMAIN_EVENT_RESUMED_MIGRATED event on the destination once the >> migration completes. I can see that when a pau

How to detect completion of a paused VM migration on the destination?

Hi, when a normally running VM is migrated, libvirt sends VIR_DOMAIN_EVENT_RESUMED_MIGRATED event on the destination once the migration completes. I can see that when a paused VM is migrated, libvirt sends VIR_DOMAIN_EVENT_SUSPENDED_PAUSED instead. Since there seems to be nothing migration

Re: Two questions about NVDIMM devices

Daniel P. Berrangé writes: > On Thu, Sep 10, 2020 at 04:26:40PM +0200, Milan Zamazal wrote: >> Daniel P. Berrangé writes: >> > >> > On Thu, Jul 02, 2020 at 01:21:15PM +0200, Milan Zamazal wrote: >> >> Hi, >> >> >> > >> &

Re: Two questions about NVDIMM devices

Daniel P. Berrangé writes: > On Thu, Jul 02, 2020 at 01:21:15PM +0200, Milan Zamazal wrote: >> Hi, >> > >> I've met two situations with NVDIMM support in libvirt where I'm not >> sure all the parties (libvirt & I) do the things correctly. >> >&

Distinguishing between host and guest initiated VM shutdown

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

Re: Distinguishing between host and guest initiated VM shutdown

Daniel P. Berrangé writes: > On Thu, Aug 27, 2020 at 10:06:25AM +0200, Milan Zamazal wrote: >> "Daniel P. Berrange" writes: >> > >> > On Wed, Aug 26, 2020 at 10:35:22PM +0200, Milan Zamazal wrote: >> >> Hi, >> >> >> > &g

Re: Distinguishing between host and guest initiated VM shutdown

"Daniel P. Berrange" writes: > On Wed, Aug 26, 2020 at 10:35:22PM +0200, Milan Zamazal wrote: >> 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

Two questions about NVDIMM devices

Hi, I've met two situations with NVDIMM support in libvirt where I'm not sure all the parties (libvirt & I) do the things correctly. The first problem is with memory alignment and size changes. In addition to the size changes applied to NVDIMMs by QEMU, libvirt also makes some NVDIMM size

Re: Two questions about NVDIMM devices

Daniel P. Berrangé writes: > On Thu, Jul 02, 2020 at 01:21:15PM +0200, Milan Zamazal wrote: >> Hi, >> > >> I've met two situations with NVDIMM support in libvirt where I'm not >> sure all the parties (libvirt & I) do the things correctly. >> >&

NVDIMM in devdax mode and SELinux (was: Two questions about NVDIMM devices)

Milan Zamazal writes: > Daniel P. Berrangé writes: > >> On Thu, Jul 02, 2020 at 01:21:15PM +0200, Milan Zamazal wrote: >>> The second problem is that a VM fails to start with a backing NVDIMM in >>> devdax mode due to SELinux preventing access to the /dev/dax*

Re: Emulated TPM devices and snapshots of running VMs

Milan Zamazal writes: > Hi, > > I would like to clarify how to make snapshots of running VMs with > emulated TPM devices. As far as I understand QEMU documentation, it's > possible to make snapshots of running VMs with TPM, but it's important > to retain the state of swtpm. D

Re: Emulated TPM devices and snapshots of running VMs

Peter Krempa writes: > On Thu, Jul 09, 2020 at 14:14:32 +0200, Milan Zamazal wrote: >> Milan Zamazal writes: >> > >> > Hi, >> > >> > I would like to clarify how to make snapshots of running VMs with >> > emulated TPM devices. As far

Re: Emulated TPM devices and snapshots of running VMs

Peter Krempa writes: > On Thu, Jul 09, 2020 at 17:54:23 +0200, Milan Zamazal wrote: >> Peter Krempa writes: >> > >> > On Thu, Jul 09, 2020 at 14:14:32 +0200, Milan Zamazal wrote: >> >> Milan Zamazal writes: >> >> >> > >> >

Emulated TPM devices and snapshots of running VMs

Hi, I would like to clarify how to make snapshots of running VMs with emulated TPM devices. As far as I understand QEMU documentation, it's possible to make snapshots of running VMs with TPM, but it's important to retain the state of swtpm. Does libvirt assist with that in any way or is it

Re: NVDIMM sizes and DIMM hot plug

Peter Krempa writes: > On Tue, Jun 16, 2020 at 12:54:29 +0200, Milan Zamazal wrote: >> Hi, >> > >> I've found out that NVDIMM size and label size matter for regular >> (non-NV) DIMM hot plug. If the NVDIMM is not aligned correctly, the >> guest OS wi

NVDIMM sizes and DIMM hot plug

Hi, I've found out that NVDIMM size and label size matter for regular (non-NV) DIMM hot plug. If the NVDIMM is not aligned correctly, the guest OS will not accept the hot plugged memory and will complain with messages such as Block size [0x800] unaligned hotplug range: start 0x22500,

Re: NVDIMM sizes and DIMM hot plug

Daniel P. Berrangé writes: > On Tue, Jun 16, 2020 at 12:54:29PM +0200, Milan Zamazal wrote: >> Hi, >> > >> I've found out that NVDIMM size and label size matter for regular >> (non-NV) DIMM hot plug. If the NVDIMM is not aligned correctly, the >> guest OS wi

Re: Memory locking limit and zero-copy migrations

Fangge Jin writes: > On Thu, Aug 18, 2022 at 2:46 PM Milan Zamazal wrote: > >> Fangge Jin writes: >> >> > I can share some test results with you: >> > 1. If no memtune->hard_limit is set when start a vm, the default memlock >> > hard limit is

Re: Memory locking limit and zero-copy migrations

Fangge Jin writes: > On Fri, Aug 19, 2022 at 4:08 AM Milan Zamazal wrote: > >> > Not sure whether you already know this, but I had a hard time >> > differentiating the two concepts: >> > 1. memlock hard limit(shown by prlimit): the hard limit for locked host

Re: NUMA node - Memory Only

Michal Prívozník writes: > On 8/9/22 12:55, Jin Huang wrote: >> Hi, everyone >> I built the libvirt 8.6.0 on my Ubuntu 20 system with the options like this: > >> meson build -Dsystem=true -Ddriver_interface=enabled >> -Ddriver_libvirtd=enabled -Ddriver_network=enabled -Ddriver_qemu=enabled >>

Re: Memory locking limit and zero-copy migrations

Peter Krempa writes: > On Wed, Aug 17, 2022 at 10:56:54 +0200, Milan Zamazal wrote: >> Hi, >> > >> do I read libvirt sources right that when is not used in the >> libvirt domain then libvirt takes proper care about setting memory >> locking limits when ze

Memory locking limit and zero-copy migrations

Hi, do I read libvirt sources right that when is not used in the libvirt domain then libvirt takes proper care about setting memory locking limits when zero-copy is requested for a migration? I also wonder whether there are any other situations where memory limits could be set by libvirt or

Re: Memory locking limit and zero-copy migrations

od. Regards, Milan > BR, > Fangge Jin > > On Wed, Aug 17, 2022 at 19:25 Milan Zamazal wrote: > >> Peter Krempa writes: >> >> > On Wed, Aug 17, 2022 at 10:56:54 +0200, Milan Zamazal wrote: >> >> Hi, >> >> >> > >> >