correct: before_vdsm_start -> before_vm_start
On 06/06/2022 09:34, lizhij...@fujitsu.com wrote:
> Hey folks
>
> I have a ovirt-4.3 environment, where i have a before_vdsm_start hook to
> change default usb2
> device to usb3(qemu-xhci). But i noticed that the vm still uses the usb3
> device
Hey folks
I have a ovirt-4.3 environment, where i have a before_vdsm_start hook to change
default usb2
device to usb3(qemu-xhci). But i noticed that the vm still uses the usb3 device
after i removed
the before_vdsm_start hook. So i wonder if the xml updated by before_vdsm_start
hook will
be
That's an AMD Jaguar architecture CPU according to CPU-World.
It's meant for low-power desktop use, and was initially produced in
2014. As the flags show, It does support svm.
Only an AMD cpu type will work with AMD host CPUs. However, if you've
already tried the existing Opteron types and it
You can use the all_disks_for_vms view, instead of all_disks. Then add
the vm_id and / or vm_names columns.
For example:
/usr/share/ovirt-engine/dbscripts/engine-psql.sh -c "select
disk_id,image_guid,disk_alias,disk_profile_name,vm_id,vm_names from
all_disks_for_vms where disk_content_type='0'
On Mon, May 30, 2022 at 4:44 PM _isi _ wrote:
> Do you mean something like this ?
>
> /usr/share/ovirt-engine/dbscripts/engine-psql.sh -c "select
> disk_id,image_guid,disk_alias,disk_profile_name from all_disks where
> disk_content_type='0' order by disk_alias" > /root/disk_ids-to_vms.txt
>
>
On 2022-06-03 21:34, Pavel Mlčoch wrote:
Know anybody which CPU type can be used for Athlon5350 or how to solve
this error?
You can check the supported CPU type by running the following command:
virsh -r capabilities | grep model
Regards
- Frank
6 matches
Mail list logo
