[ovirt-users] Re: What does the ovirtmgmt service do & how do I work withit in regards to networking

2022-04-19 Thread Strahil Nikolov via Users 
Ovirtmgmt network is for oVirt management stuff. Usually when you deploy , it 
takes curent settings into consideration and then takes the ovirtmgmt and 
underlying network settings under it's control.Not all scenarios are supported, 
so you have to check it out.A nice point to start from is 
https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html/technical_reference/chap-network
 .
Once you have the syatem up and running, you have to configure the remaining 
ports with the help of the engine UI/API .
I think it will be best if you share the details after you install the system, 
so the users can help.
Best Regards,Strahil Nikolov
 
 
I've installed ovirt 4.4.10 several times and found myself not being able 
to reach out to the internet to perform updates to the OS or ovirt.  When 
installing ovirt I've accepted the defaults and found that networking on my 
server has stopped working.  

I've also noticed that the ovirtmgmt service has taken over the network 
port/NIC that I've assigned in the DNS.  My server has six/6 NIC's installed 
but after the install of ovirt with the defaults I'm unable to perform another 
network functions other than go to ovirt.  

How do i get ovirt to co-exist on the server as it relates to networking.  I 
just have the OS & GUI installed and then ovirt.  I've checked the firewall and 
not found anything out the ordinary.  When this happens what can I do to get 
things back to normal, the ability to apply OS and ovirt updates?  

I'm going to install ovirt again making sure that I don't take the default 
regarding the firewall, maybe this will help?  

Thanks
 
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/RF5E3GE7YB4BJNJWAMZBJYGBQIGEH6ZJ/
  
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/LETUKYVQFJVBAREZYQ3G2Q5WRRKZLNYJ/

[ovirt-users] What does the ovirtmgmt service do & how do I work withit in regards to networking

2022-04-19 Thread louisb 
I've installed ovirt 4.4.10 several times and found myself not being able to 
reach out to the internet to perform updates to the OS or ovirt.  When 
installing ovirt I've accepted the defaults and found that networking on my 
server has stopped working.  

I've also noticed that the ovirtmgmt service has taken over the network 
port/NIC that I've assigned in the DNS.  My server has six/6 NIC's installed 
but after the install of ovirt with the defaults I'm unable to perform another 
network functions other than go to ovirt.  

How do i get ovirt to co-exist on the server as it relates to networking.  I 
just have the OS & GUI installed and then ovirt.  I've checked the firewall and 
not found anything out the ordinary.  When this happens what can I do to get 
things back to normal, the ability to apply OS and ovirt updates?  

I'm going to install ovirt again making sure that I don't take the default 
regarding the firewall, maybe this will help?  

Thanks
 
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/WL3W34R7ZVBR7GL4LXEHFT5YRWORIE7E/

[ovirt-users] What does the ovirtmgmt service do & how do I work withit in regards to networking

2022-04-19 Thread louisb 
I've installed ovirt 4.4.10 several times and found myself not being able to 
reach out to the internet to perform updates to the OS or ovirt.  When 
installing ovirt I've accepted the defaults and found that networking on my 
server has stopped working.  

I've also noticed that the ovirtmgmt service has taken over the network 
port/NIC that I've assigned in the DNS.  My server has six/6 NIC's installed 
but after the install of ovirt with the defaults I'm unable to perform another 
network functions other than go to ovirt.  

How do i get ovirt to co-exist on the server as it relates to networking.  I 
just have the OS & GUI installed and then ovirt.  I've checked the firewall and 
not found anything out the ordinary.  When this happens what can I do to get 
things back to normal, the ability to apply OS and ovirt updates?  

I'm going to install ovirt again making sure that I don't take the default 
regarding the firewall, maybe this will help?  

Thanks
 
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/RF5E3GE7YB4BJNJWAMZBJYGBQIGEH6ZJ/

[ovirt-users] Re: An ovirt-node machine cannot connect to ovirt-manager after reboot

2022-04-19 Thread Strahil Nikolov via Users 
> Only a single default route network is allowed
Check your network. vdsmd service has a preexec which you can run to find which 
module is failing.
systemctl cat vdsmd.serviceThen execute the preexec command
Best Regards,Strahil Nikolov
 
 
An ovirt-node machine reboots and shows in the ovirt-manager page:
NonResponsive

Then I went to the Admin console page of this node machine and had the 
following error reported：

1.Failed command for onn-pool00-tpool.
2.Insufficient free space: 378895 extents needed, but only 2375 available
3.Failed to start Virtual Desktop Server Manager network restoration

Then I can't turn on the vdsmd service either:

[root@ovirt-node04 ~]# systemctl start vdsmd
A dependency job for vdsmd.service failed. See 'journalctl -xe' for details.

Then I use command  'journalctl -xe' show details:
[root@ovirt-node04 ~]# journalctl -xe
Apr 19 14:58:20 ovirt-node04 vdsm-tool[55011]: File 
"/usr/lib/python2.7/site-packages/vdsm/tool/network.py", line 57, in 
upgrade_networks
Apr 19 14:58:20 ovirt-node04 vdsm-tool[55011]: netupgrade.upgrade()
Apr 19 14:58:20 ovirt-node04 vdsm-tool[55011]: File 
"/usr/lib/python2.7/site-packages/vdsm/network/netupgrade.py", line 70, in 
upgrade
Apr 19 14:58:20 ovirt-node04 vdsm-tool[55011]: 
_upgrade_unified_configuration(pconfig)
Apr 19 14:58:20 ovirt-node04 vdsm-tool[55011]: File 
"/usr/lib/python2.7/site-packages/vdsm/network/netupgrade.py", line 110, in 
_upgrade_unified_configura
Apr 19 14:58:20 ovirt-node04 vdsm-tool[55011]: 
canonicalize_networks(config.networks)
Apr 19 14:58:20 ovirt-node04 vdsm-tool[55011]: File 
"/usr/lib/python2.7/site-packages/vdsm/network/canonicalize.py", line 44, in 
canonicalize_networks
Apr 19 14:58:20 ovirt-node04 vdsm-tool[55011]: 
_canonicalize_ip_default_route(nets)
Apr 19 14:58:20 ovirt-node04 vdsm-tool[55011]: File 
"/usr/lib/python2.7/site-packages/vdsm/network/canonicalize.py", line 228, in 
_canonicalize_ip_default
Apr 19 14:58:20 ovirt-node04 vdsm-tool[55011]: 'Only a single default route 
network is allowed.')
Apr 19 14:58:20 ovirt-node04 vdsm-tool[55011]: ConfigNetworkError: (21, 'Only a 
single default route network is allowed.')
Apr 19 14:58:20 ovirt-node04 systemd[1]: vdsm-network.service: control process 
exited, code=exited status=1
Apr 19 14:58:20 ovirt-node04 systemd[1]: Failed to start Virtual Desktop Server 
Manager network restoration.
-- Subject: Unit vdsm-network.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit vdsm-network.service has failed.
-- 
-- The result is failed.
Apr 19 14:58:20 ovirt-node04 systemd[1]: Dependency failed for Virtual Desktop 
Server Manager.
-- Subject: Unit vdsmd.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit vdsmd.service has failed.
-- 
-- The result is dependency.
Apr 19 14:58:20 ovirt-node04 systemd[1]: Dependency failed for MOM instance 
configured for VDSM purposes.
-- Subject: Unit mom-vdsm.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit mom-vdsm.service has failed.
-- 
-- The result is dependency.
Apr 19 14:58:20 ovirt-node04 systemd[1]: Job mom-vdsm.service/start failed with 
result 'dependency'.
Apr 19 14:58:20 ovirt-node04 systemd[1]: Job vdsmd.service/start failed with 
result 'dependency'.
Apr 19 14:58:20 ovirt-node04 systemd[1]: Unit vdsm-network.service entered 
failed state.
Apr 19 14:58:20 ovirt-node04 systemd[1]: vdsm-network.service failed.
Apr 19 14:58:20 ovirt-node04 polkitd[3463]: Unregistered Authentication Agent 
for unix-process:55005:2145554 (system bus name :1.501, object path 
/org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) 
(disconnected from bus)

How should I solve the above problem?
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/3T7AFQJQFD774W63DRK4DBNPGRXOOIDV/
  
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/5KRZ25PPD7IBKRX5XSOPIYLZ6KUDRUXR/

[ovirt-users] Re: Hosted Engine Deployment timeout waiting for VM

2022-04-19 Thread Strahil Nikolov via Users 
Is your Hypervisor's ssh hardened ?Try without any modifications .
Best Regards,Strahil Nikolov 
 
  On Mon, Apr 18, 2022 at 22:33, Jonas wrote:   
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/5FRO3EK3YRK2OPOGLVDPI2O7X53EENTM/
  
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/YJUETMLKDG27NPWR34PXZNBXI2RYHT2L/

[ovirt-users] Re: NVIDIA vgpu mdev/mediated devices are getting deleted/removed after VM shutdown with ovirt

2022-04-19 Thread Sandip Thorat via Users 
Thanks Arik for reply.

I want to add enable_large_sys_mem=1 vGPU plugin parameter . How can I do that 
with oVirt? Could you please share steps?





-Original Message-
From: Arik Hadas 
Sent: Tuesday, April 19, 2022 6:49 PM
To: Sandip Thorat 
Cc: users 
Subject: Re: [ovirt-users] NVIDIA vgpu mdev/mediated devices are getting 
deleted/removed after VM shutdown with ovirt



External email: Use caution opening links or attachments





On Tue, Apr 19, 2022 at 3:47 PM sandipt--- via Users 
mailto:users@ovirt.org>> wrote:

>

> Hi Team,

> NVIDIA vgpu mdev/mediated devices are getting deleted/removed after VM 
> shutdown with ovirt. How I can make them persistent even after VM 
> shutdown/poweroff ? I want to set some vgpu parameter in file 
> /sys/bus/mdev/devices/vgpu-id/nvidia/vgpu_params for testing to mdev. But 
> can't do as uuid of mdev are not persistent.  mdev are not there in 
> /sys/bus/mdev/devices/ after VM shutdown. We were using RHV/Red Hat 
> Virtualization Host 4.4.10 host with NVIDIA vGPU.  virsh commands are 
> helping. Can you please help?



As from oVirt 4.5, you can set such parameters via oVirt's UI/API, see:

https://bugzilla.redhat.com/1987121

(The mdev devices were also changed to managed devices in order to have them 
persisted)





> ___

> Users mailing list -- users@ovirt.org

> To unsubscribe send an email to 
> users-le...@ovirt.org Privacy

> Statement: https://www.ovirt.org/privacy-policy.html

> oVirt Code of Conduct:

> https://www.ovirt.org/community/about/community-guidelines/

> List Archives:

> https://lists.ovirt.org/archives/list/users@ovirt.org/message/YAZ5I5LT

> FZ3WXBPVNIPH2HQWVEDSQW6K/


___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/6PPFZURIXQWCIM6RY6EJ33PCFDKOMXR5/

[ovirt-users] Re: NVIDIA vgpu mdev/mediated devices are getting deleted/removed after VM shutdown with ovirt

2022-04-19 Thread Arik Hadas 
On Tue, Apr 19, 2022 at 3:47 PM sandipt--- via Users  wrote:
>
> Hi Team,
> NVIDIA vgpu mdev/mediated devices are getting deleted/removed after VM 
> shutdown with ovirt. How I can make them persistent even after VM 
> shutdown/poweroff ? I want to set some vgpu parameter in file 
> /sys/bus/mdev/devices/vgpu-id/nvidia/vgpu_params for testing to mdev. But 
> can't do as uuid of mdev are not persistent.  mdev are not there in 
> /sys/bus/mdev/devices/ after VM shutdown. We were using RHV/Red Hat 
> Virtualization Host 4.4.10 host with NVIDIA vGPU.  virsh commands are 
> helping. Can you please help?

As from oVirt 4.5, you can set such parameters via oVirt's UI/API, see:
https://bugzilla.redhat.com/1987121
(The mdev devices were also changed to managed devices in order to
have them persisted)


> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct: 
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives: 
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/YAZ5I5LTFZ3WXBPVNIPH2HQWVEDSQW6K/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/JKIR6GV6KV3OX45NI6VQFJOUHTMFZMQN/

[ovirt-users] Re: USB3 redirection

2022-04-19 Thread Li, Zhijian 


on 2022/4/19 20:12, Rik Theys wrote:

Hi,

You may need to explicitly use the Q35 chipset in your VM for this to 
work?


See https://bugzilla.redhat.com/show_bug.cgi?id=1527860


I agreed it was on the right track.




You can select the chipset of your VM in the advanced properties on 
the system tab.


But VM cannot start if i chose Q35 machine in * in the advanced 
properties on the system tab*


Anyway, thank you very much, your information is very helpful. i will 
take a look what's wrong.



Thanks

Zhijian




Regards,
Rik

On 4/19/22 14:07, Li, Zhijian wrote:

Hi Rik

many thanks for your feedbacks


on 2022/4/19 19:08, Rik Theys wrote:

Hi,

This is supported in newer versions of oVirt than 4.1.


That's strange, i was using ovirt 4.3,  I just added below extra 
configruation.


[root@d0248f99ff ~]# cat 
/etc/ovirt-engine/osinfo.conf.d/01-usb3.0.properties  | grep -v ^#

os.other.devices.usb.controller.value = nec-xhci


then after i enabled *USB-support *, it becomes back to 4 
ich9-usb-uhci like below.


[root@d0248f99ff ~]# ps aux | grep qemu
root 11466  0.0  0.0 112712   976 pts/3    S+   20:04   0:00 grep 
--color=auto qemu
qemu 12530  1.8  3.6 1984036 1179080 ? Sl   18:41   1:32 
/usr/libexec/qemu-kvm -name guest=x,debug-threads=on -S -object 
secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-81-x/master-key.aes 
-machine pc-i440fx-rhel7.6.0,accel=kvm,usb=off,dump-guest-core=off 
-cpu Skylake-Client,spec-ctrl=on,ssbd=on,md-clear=on -m 
size=1048576k,slots=16,maxmem=4194304k -realtime mlock=off -smp 
1,maxcpus=16,sockets=16,cores=1,threads=1 -object 
iothread,id=iothread1 -numa node,nodeid=0,cpus=0,mem=1024 -uuid 
2f03e393-e58f-4a61-aa71-b9f438e5f3b5 -smbios 
type=1,manufacturer=oVirt,product=oVirt 
Node,version=7-7.1908.0.el7.centos,serial=b3d2fc00-07f9-11e8-af80-76c675673e00,uuid=2f03e393-e58f-4a61-aa71-b9f438e5f3b5 
-no-user-config -nodefaults -chardev 
socket,id=charmonitor,fd=30,server,nowait -mon 
chardev=charmonitor,id=monitor,mode=control -rtc 
base=2022-04-19T10:41:22,driftfix=slew -global 
kvm-pit.lost_tick_policy=delay -no-hpet -no-shutdown -global 
PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -boot strict=on 
-device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x3.0x7 -device 
ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x3.0x1 
-device 
ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x3 
-device 
ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x3.0x2 
-device 
virtio-scsi-pci,iothread=iothread1,id=ua-df35c3c7-4869-4255-b090-8fd8b545ebba,bus=pci.0,addr=0x5 
-device 
virtio-serial-pci,id=ua-304b04db-6d2b-498f-9818-1abe1e6c4f22,max_ports=16,bus=pci.0,addr=0x4 
-drive 
file=/rhev/data-center/mnt/_data_ISO/19e68646-c43b-4269-a8f0-64b02b0f3cec/images/----/ubuntu-18.04-desktop-amd64.iso,format=raw,if=none,id=drive-ua-900e695f-d46a-41c3-bf8d-a8c5475ef085,werror=report,rerror=report,readonly=on 
-device 
ide-cd,bus=ide.1,unit=0,drive=drive-ua-900e695f-d46a-41c3-bf8d-a8c5475ef085,id=ua-900e695f-d46a-41c3-bf8d-a8c5475ef085,bootindex=1 
-drive 
file=/rhev/data-center/mnt/_data/c6434b1f-c0fe-4430-a713-31bb4de88123/images/ee401e83-5729-46cc-8bfd-a787da0eb224/029452e2-d0f6-4e8c-934c-cfbe66c68769,format=raw,if=none,id=drive-ua-ee401e83-5729-46cc-8bfd-a787da0eb224,serial=ee401e83-5729-46cc-8bfd-a787da0eb224,werror=stop,rerror=stop,cache=none,aio=threads 
-device 
scsi-hd,bus=ua-df35c3c7-4869-4255-b090-8fd8b545ebba.0,channel=0,scsi-id=0,lun=0,drive=drive-ua-ee401e83-5729-46cc-8bfd-a787da0eb224,id=ua-ee401e83-5729-46cc-8bfd-a787da0eb224,bootindex=2,write-cache=on 
-chardev socket,id=charchannel0,fd=32,server,nowait -device 
virtserialport,bus=ua-304b04db-6d2b-498f-9818-1abe1e6c4f22.0,nr=1,chardev=charchannel0,id=channel0,name=ovirt-guest-agent.0 
-chardev socket,id=charchannel1,fd=33,server,nowait -device 
virtserialport,bus=ua-304b04db-6d2b-498f-9818-1abe1e6c4f22.0,nr=2,chardev=charchannel1,id=channel1,name=org.qemu.guest_agent.0 
-chardev spicevmc,id=charchannel2,name=vdagent -device 
virtserialport,bus=ua-304b04db-6d2b-498f-9818-1abe1e6c4f22.0,nr=3,chardev=charchannel2,id=channel2,name=com.redhat.spice.0 
-device usb-tablet,id=input0,bus=usb.0,port=1 -vnc 
192.168.22.59:0,password -k en-us -spice 
port=5901,tls-port=5902,addr=192.168.22.59,x509-dir=/etc/pki/vdsm/libvirt-spice,tls-channel=main,tls-channel=display,tls-channel=inputs,tls-channel=cursor,tls-channel=playback,tls-channel=record,tls-channel=smartcard,tls-channel=usbredir,seamless-migration=on 
-device 
qxl-vga,id=ua-c5f50bba-e9f7-4379-93eb-8164724977be,ram_size=67108864,vram_size=8388608,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pci.0,addr=0x2 
-chardev 
spicevmc,id=charua-0a3e648c-39e1-4dc5-8c20-e459609b40e0,name=usbredir 
-device 
usb-redir,chardev=charua-0a3e648c-39e1-4dc5-8c20-e459609b40e0,id=ua-0a3e648c-39e1-4dc5-8c20-e459609b40e0,filter=0x03:-1:-1:-1:0|-1:-1:-1:-1:1,bus=usb.0,port=2 
-chardev

[ovirt-users] NVIDIA vgpu mdev/mediated devices are getting deleted/removed after VM shutdown with ovirt

2022-04-19 Thread sandipt--- via Users 
Hi Team,
NVIDIA vgpu mdev/mediated devices are getting deleted/removed after VM 
shutdown with ovirt. How I can make them persistent even after VM 
shutdown/poweroff ? I want to set some vgpu parameter in file 
/sys/bus/mdev/devices/vgpu-id/nvidia/vgpu_params for testing to mdev. But can't 
do as uuid of mdev are not persistent.  mdev are not there in 
/sys/bus/mdev/devices/ after VM shutdown. We were using RHV/Red Hat 
Virtualization Host 4.4.10 host with NVIDIA vGPU.  virsh commands are helping. 
Can you please help? 
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/YAZ5I5LTFZ3WXBPVNIPH2HQWVEDSQW6K/

[ovirt-users] Re: USB3 redirection

2022-04-19 Thread Li, Zhijian 

Hi Rik


I got the same problem, have you got it resolved ?


Thanks

Zhijian


Hi,

I'm trying to assign a USB3 controller to a CentOS 7.4 VM in oVirt 4.1
with USB redirection enabled.

I've created the following file in /etc/ovirt-engine/osinfo.conf.d:

01-usb.properties with content

os.other.devices.usb.controller.value = nec-xhci

and have restarted ovirt-engine.

If I disable USB-support in the web interface for the VM, the xhci
controller is added to the VM (I can see it in the qemu-kvm
commandline), but usb redirection is not available.

If I enable USB-support in the UI, no xhci controller is added (only 4
uhci controllers).

Is there a way to make the controllers for usb redirection xhci controllers?

Regards,

Rik



___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/5AMWOPRKHBSZPHXP5FQ3TY4XUYMQGTBN/

[ovirt-users] Re: USB3 redirection

2022-04-19 Thread Li, Zhijian 

Hi Rik

many thanks for your feedbacks


on 2022/4/19 19:08, Rik Theys wrote:

Hi,

This is supported in newer versions of oVirt than 4.1.


That's strange, i was using ovirt 4.3,  I just added below extra 
configruation.


[root@d0248f99ff ~]# cat 
/etc/ovirt-engine/osinfo.conf.d/01-usb3.0.properties  | grep -v ^#

os.other.devices.usb.controller.value = nec-xhci


then after i enabled *USB-support *, it becomes back to 4 ich9-usb-uhci 
like below.


[root@d0248f99ff ~]# ps aux | grep qemu
root 11466  0.0  0.0 112712   976 pts/3    S+   20:04   0:00 grep 
--color=auto qemu
qemu 12530  1.8  3.6 1984036 1179080 ? Sl   18:41   1:32 
/usr/libexec/qemu-kvm -name guest=x,debug-threads=on -S -object 
secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-81-x/master-key.aes 
-machine pc-i440fx-rhel7.6.0,accel=kvm,usb=off,dump-guest-core=off -cpu 
Skylake-Client,spec-ctrl=on,ssbd=on,md-clear=on -m 
size=1048576k,slots=16,maxmem=4194304k -realtime mlock=off -smp 
1,maxcpus=16,sockets=16,cores=1,threads=1 -object iothread,id=iothread1 
-numa node,nodeid=0,cpus=0,mem=1024 -uuid 
2f03e393-e58f-4a61-aa71-b9f438e5f3b5 -smbios 
type=1,manufacturer=oVirt,product=oVirt 
Node,version=7-7.1908.0.el7.centos,serial=b3d2fc00-07f9-11e8-af80-76c675673e00,uuid=2f03e393-e58f-4a61-aa71-b9f438e5f3b5 
-no-user-config -nodefaults -chardev 
socket,id=charmonitor,fd=30,server,nowait -mon 
chardev=charmonitor,id=monitor,mode=control -rtc 
base=2022-04-19T10:41:22,driftfix=slew -global 
kvm-pit.lost_tick_policy=delay -no-hpet -no-shutdown -global 
PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -boot strict=on 
-device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x3.0x7 -device 
ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x3.0x1 
-device 
ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x3 
-device 
ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x3.0x2 
-device 
virtio-scsi-pci,iothread=iothread1,id=ua-df35c3c7-4869-4255-b090-8fd8b545ebba,bus=pci.0,addr=0x5 
-device 
virtio-serial-pci,id=ua-304b04db-6d2b-498f-9818-1abe1e6c4f22,max_ports=16,bus=pci.0,addr=0x4 
-drive 
file=/rhev/data-center/mnt/_data_ISO/19e68646-c43b-4269-a8f0-64b02b0f3cec/images/----/ubuntu-18.04-desktop-amd64.iso,format=raw,if=none,id=drive-ua-900e695f-d46a-41c3-bf8d-a8c5475ef085,werror=report,rerror=report,readonly=on 
-device 
ide-cd,bus=ide.1,unit=0,drive=drive-ua-900e695f-d46a-41c3-bf8d-a8c5475ef085,id=ua-900e695f-d46a-41c3-bf8d-a8c5475ef085,bootindex=1 
-drive 
file=/rhev/data-center/mnt/_data/c6434b1f-c0fe-4430-a713-31bb4de88123/images/ee401e83-5729-46cc-8bfd-a787da0eb224/029452e2-d0f6-4e8c-934c-cfbe66c68769,format=raw,if=none,id=drive-ua-ee401e83-5729-46cc-8bfd-a787da0eb224,serial=ee401e83-5729-46cc-8bfd-a787da0eb224,werror=stop,rerror=stop,cache=none,aio=threads 
-device 
scsi-hd,bus=ua-df35c3c7-4869-4255-b090-8fd8b545ebba.0,channel=0,scsi-id=0,lun=0,drive=drive-ua-ee401e83-5729-46cc-8bfd-a787da0eb224,id=ua-ee401e83-5729-46cc-8bfd-a787da0eb224,bootindex=2,write-cache=on 
-chardev socket,id=charchannel0,fd=32,server,nowait -device 
virtserialport,bus=ua-304b04db-6d2b-498f-9818-1abe1e6c4f22.0,nr=1,chardev=charchannel0,id=channel0,name=ovirt-guest-agent.0 
-chardev socket,id=charchannel1,fd=33,server,nowait -device 
virtserialport,bus=ua-304b04db-6d2b-498f-9818-1abe1e6c4f22.0,nr=2,chardev=charchannel1,id=channel1,name=org.qemu.guest_agent.0 
-chardev spicevmc,id=charchannel2,name=vdagent -device 
virtserialport,bus=ua-304b04db-6d2b-498f-9818-1abe1e6c4f22.0,nr=3,chardev=charchannel2,id=channel2,name=com.redhat.spice.0 
-device usb-tablet,id=input0,bus=usb.0,port=1 -vnc 
192.168.22.59:0,password -k en-us -spice 
port=5901,tls-port=5902,addr=192.168.22.59,x509-dir=/etc/pki/vdsm/libvirt-spice,tls-channel=main,tls-channel=display,tls-channel=inputs,tls-channel=cursor,tls-channel=playback,tls-channel=record,tls-channel=smartcard,tls-channel=usbredir,seamless-migration=on 
-device 
qxl-vga,id=ua-c5f50bba-e9f7-4379-93eb-8164724977be,ram_size=67108864,vram_size=8388608,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pci.0,addr=0x2 
-chardev 
spicevmc,id=charua-0a3e648c-39e1-4dc5-8c20-e459609b40e0,name=usbredir 
-device 
usb-redir,chardev=charua-0a3e648c-39e1-4dc5-8c20-e459609b40e0,id=ua-0a3e648c-39e1-4dc5-8c20-e459609b40e0,filter=0x03:-1:-1:-1:0|-1:-1:-1:-1:1,bus=usb.0,port=2 
-chardev 
spicevmc,id=charua-760a84f3-faea-4764-a2d2-24baf3919577,name=usbredir 
-device 
usb-redir,chardev=charua-760a84f3-faea-4764-a2d2-24baf3919577,id=ua-760a84f3-faea-4764-a2d2-24baf3919577,filter=0x03:-1:-1:-1:0|-1:-1:-1:-1:1,bus=usb.0,port=3 
-chardev 
spicevmc,id=charua-7d4d715a-fc3f-4009-a03d-5e6e92ea82a1,name=usbredir 
-device 
usb-redir,chardev=charua-7d4d715a-fc3f-4009-a03d-5e6e92ea82a1,id=ua-7d4d715a-fc3f-4009-a03d-5e6e92ea82a1,filter=0x03:-1:-1:-1:0|-1:-1:-1:-1:1,bus=usb.0,port=4 
-chardev 
spicevmc,id=charua-a78ea535-6922-4dee-84b0-5b927d002cc3,name=usbredir 
-device

[ovirt-users] Re: USB3 redirection

2022-04-19 Thread Rik Theys 

Hi,

You may need to explicitly use the Q35 chipset in your VM for this to work?

See https://bugzilla.redhat.com/show_bug.cgi?id=1527860

You can select the chipset of your VM in the advanced properties on the 
system tab.


Regards,
Rik

On 4/19/22 14:07, Li, Zhijian wrote:

Hi Rik

many thanks for your feedbacks


on 2022/4/19 19:08, Rik Theys wrote:

Hi,

This is supported in newer versions of oVirt than 4.1.


That's strange, i was using ovirt 4.3,  I just added below extra 
configruation.


[root@d0248f99ff ~]# cat 
/etc/ovirt-engine/osinfo.conf.d/01-usb3.0.properties  | grep -v ^#

os.other.devices.usb.controller.value = nec-xhci


then after i enabled *USB-support *, it becomes back to 4 
ich9-usb-uhci like below.


[root@d0248f99ff ~]# ps aux | grep qemu
root 11466  0.0  0.0 112712   976 pts/3    S+   20:04   0:00 grep 
--color=auto qemu
qemu 12530  1.8  3.6 1984036 1179080 ? Sl   18:41   1:32 
/usr/libexec/qemu-kvm -name guest=x,debug-threads=on -S -object 
secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-81-x/master-key.aes 
-machine pc-i440fx-rhel7.6.0,accel=kvm,usb=off,dump-guest-core=off 
-cpu Skylake-Client,spec-ctrl=on,ssbd=on,md-clear=on -m 
size=1048576k,slots=16,maxmem=4194304k -realtime mlock=off -smp 
1,maxcpus=16,sockets=16,cores=1,threads=1 -object 
iothread,id=iothread1 -numa node,nodeid=0,cpus=0,mem=1024 -uuid 
2f03e393-e58f-4a61-aa71-b9f438e5f3b5 -smbios 
type=1,manufacturer=oVirt,product=oVirt 
Node,version=7-7.1908.0.el7.centos,serial=b3d2fc00-07f9-11e8-af80-76c675673e00,uuid=2f03e393-e58f-4a61-aa71-b9f438e5f3b5 
-no-user-config -nodefaults -chardev 
socket,id=charmonitor,fd=30,server,nowait -mon 
chardev=charmonitor,id=monitor,mode=control -rtc 
base=2022-04-19T10:41:22,driftfix=slew -global 
kvm-pit.lost_tick_policy=delay -no-hpet -no-shutdown -global 
PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -boot strict=on 
-device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x3.0x7 -device 
ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x3.0x1 
-device 
ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x3 
-device 
ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x3.0x2 
-device 
virtio-scsi-pci,iothread=iothread1,id=ua-df35c3c7-4869-4255-b090-8fd8b545ebba,bus=pci.0,addr=0x5 
-device 
virtio-serial-pci,id=ua-304b04db-6d2b-498f-9818-1abe1e6c4f22,max_ports=16,bus=pci.0,addr=0x4 
-drive 
file=/rhev/data-center/mnt/_data_ISO/19e68646-c43b-4269-a8f0-64b02b0f3cec/images/----/ubuntu-18.04-desktop-amd64.iso,format=raw,if=none,id=drive-ua-900e695f-d46a-41c3-bf8d-a8c5475ef085,werror=report,rerror=report,readonly=on 
-device 
ide-cd,bus=ide.1,unit=0,drive=drive-ua-900e695f-d46a-41c3-bf8d-a8c5475ef085,id=ua-900e695f-d46a-41c3-bf8d-a8c5475ef085,bootindex=1 
-drive 
file=/rhev/data-center/mnt/_data/c6434b1f-c0fe-4430-a713-31bb4de88123/images/ee401e83-5729-46cc-8bfd-a787da0eb224/029452e2-d0f6-4e8c-934c-cfbe66c68769,format=raw,if=none,id=drive-ua-ee401e83-5729-46cc-8bfd-a787da0eb224,serial=ee401e83-5729-46cc-8bfd-a787da0eb224,werror=stop,rerror=stop,cache=none,aio=threads 
-device 
scsi-hd,bus=ua-df35c3c7-4869-4255-b090-8fd8b545ebba.0,channel=0,scsi-id=0,lun=0,drive=drive-ua-ee401e83-5729-46cc-8bfd-a787da0eb224,id=ua-ee401e83-5729-46cc-8bfd-a787da0eb224,bootindex=2,write-cache=on 
-chardev socket,id=charchannel0,fd=32,server,nowait -device 
virtserialport,bus=ua-304b04db-6d2b-498f-9818-1abe1e6c4f22.0,nr=1,chardev=charchannel0,id=channel0,name=ovirt-guest-agent.0 
-chardev socket,id=charchannel1,fd=33,server,nowait -device 
virtserialport,bus=ua-304b04db-6d2b-498f-9818-1abe1e6c4f22.0,nr=2,chardev=charchannel1,id=channel1,name=org.qemu.guest_agent.0 
-chardev spicevmc,id=charchannel2,name=vdagent -device 
virtserialport,bus=ua-304b04db-6d2b-498f-9818-1abe1e6c4f22.0,nr=3,chardev=charchannel2,id=channel2,name=com.redhat.spice.0 
-device usb-tablet,id=input0,bus=usb.0,port=1 -vnc 
192.168.22.59:0,password -k en-us -spice 
port=5901,tls-port=5902,addr=192.168.22.59,x509-dir=/etc/pki/vdsm/libvirt-spice,tls-channel=main,tls-channel=display,tls-channel=inputs,tls-channel=cursor,tls-channel=playback,tls-channel=record,tls-channel=smartcard,tls-channel=usbredir,seamless-migration=on 
-device 
qxl-vga,id=ua-c5f50bba-e9f7-4379-93eb-8164724977be,ram_size=67108864,vram_size=8388608,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pci.0,addr=0x2 
-chardev 
spicevmc,id=charua-0a3e648c-39e1-4dc5-8c20-e459609b40e0,name=usbredir 
-device 
usb-redir,chardev=charua-0a3e648c-39e1-4dc5-8c20-e459609b40e0,id=ua-0a3e648c-39e1-4dc5-8c20-e459609b40e0,filter=0x03:-1:-1:-1:0|-1:-1:-1:-1:1,bus=usb.0,port=2 
-chardev 
spicevmc,id=charua-760a84f3-faea-4764-a2d2-24baf3919577,name=usbredir 
-device 
usb-redir,chardev=charua-760a84f3-faea-4764-a2d2-24baf3919577,id=ua-760a84f3-faea-4764-a2d2-24baf3919577,filter=0x03:-1:-1:-1:0|-1:-1:-1:-1:1,bus=usb.0,port=3 
-chardev

[ovirt-users] Re: USB3 redirection

2022-04-19 Thread Rik Theys 

Hi,

This is supported in newer versions of oVirt than 4.1.

Back then, we used a custom hook to replace the USB controller in the 
xml file on VM start, but it sometimes caused other issues.


Regards,
Rik

On 4/19/22 12:52, Li, Zhijian wrote:

Hi Rik


I got the same problem, have you got it resolved ?


Thanks

Zhijian


Hi,

I'm trying to assign a USB3 controller to a CentOS 7.4 VM in oVirt 4.1
with USB redirection enabled.

I've created the following file in /etc/ovirt-engine/osinfo.conf.d:

01-usb.properties with content

os.other.devices.usb.controller.value = nec-xhci

and have restarted ovirt-engine.

If I disable USB-support in the web interface for the VM, the xhci
controller is added to the VM (I can see it in the qemu-kvm
commandline), but usb redirection is not available.

If I enable USB-support in the UI, no xhci controller is added (only 4
uhci controllers).

Is there a way to make the controllers for usb redirection xhci 
controllers?


Regards,

Rik






--
Rik Theys
System Engineer
KU Leuven - Dept. Elektrotechniek (ESAT)
Kasteelpark Arenberg 10 bus 2440  - B-3001 Leuven-Heverlee
+32(0)16/32.11.07

<>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/3Y5ELWCNY5XYE27OBQLKHI7OYFU2SVU7/

[ovirt-users] Re: New ovirt 4.4.10 user unable to login

2022-04-19 Thread Gianluca Cecchi 
On Sat, Apr 16, 2022 at 3:24 AM  wrote:

> I just create an new user in ovirt 4.4.10 using the tool
> "ovirt-aaa-jdbc-tool".  I'm unable to log into ovirt using the newly
> created user.  I'm getting the error message: The user
> xyzabcs@internal-authz with profile [internal] is not authorized to
> perform login.
>

After configuring user authentication, you have to configure user
authorization through the web admin gui.
By default the user is not authorized to access neither the administration
portal, nor the VM portal
See here for details:
https://www.ovirt.org/documentation/administration_guide/#sect-User_Authorization

Gianluca
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/JIIGZDYOQ5JL3WA262VZ2XDQQ3TIQDUT/

[ovirt-users] Host certificate expired

2022-04-19 Thread Nyika Csaba 
Hi,

I have an ovirt cluster (4 nodes) and a stand-alone engine.
Last week one of the cluster-members node went to  "Non-responsive" status, 
because i forgot to renew the host certificate.
On this node's vms now are in "unknown" states. (but running)
How can i stop this vms and how can i start them on another nodes?

thanks
csabany___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/O6RIWBUFSRIUQU27Q22MT6MIICONX5MS/

[ovirt-users] An ovirt-node machine cannot connect to ovirt-manager after reboot

2022-04-19 Thread wangyu13476969128 
An ovirt-node machine reboots and shows in the ovirt-manager page:
NonResponsive

Then I went to the Admin console page of this node machine and had the 
following error reported：

1.Failed command for onn-pool00-tpool.
2.Insufficient free space: 378895 extents needed, but only 2375 available
3.Failed to start Virtual Desktop Server Manager network restoration

Then I can't turn on the vdsmd service either:

[root@ovirt-node04 ~]# systemctl start vdsmd
A dependency job for vdsmd.service failed. See 'journalctl -xe' for details.

Then I use command  'journalctl -xe' show details:
[root@ovirt-node04 ~]# journalctl -xe
Apr 19 14:58:20 ovirt-node04 vdsm-tool[55011]: File 
"/usr/lib/python2.7/site-packages/vdsm/tool/network.py", line 57, in 
upgrade_networks
Apr 19 14:58:20 ovirt-node04 vdsm-tool[55011]: netupgrade.upgrade()
Apr 19 14:58:20 ovirt-node04 vdsm-tool[55011]: File 
"/usr/lib/python2.7/site-packages/vdsm/network/netupgrade.py", line 70, in 
upgrade
Apr 19 14:58:20 ovirt-node04 vdsm-tool[55011]: 
_upgrade_unified_configuration(pconfig)
Apr 19 14:58:20 ovirt-node04 vdsm-tool[55011]: File 
"/usr/lib/python2.7/site-packages/vdsm/network/netupgrade.py", line 110, in 
_upgrade_unified_configura
Apr 19 14:58:20 ovirt-node04 vdsm-tool[55011]: 
canonicalize_networks(config.networks)
Apr 19 14:58:20 ovirt-node04 vdsm-tool[55011]: File 
"/usr/lib/python2.7/site-packages/vdsm/network/canonicalize.py", line 44, in 
canonicalize_networks
Apr 19 14:58:20 ovirt-node04 vdsm-tool[55011]: 
_canonicalize_ip_default_route(nets)
Apr 19 14:58:20 ovirt-node04 vdsm-tool[55011]: File 
"/usr/lib/python2.7/site-packages/vdsm/network/canonicalize.py", line 228, in 
_canonicalize_ip_default
Apr 19 14:58:20 ovirt-node04 vdsm-tool[55011]: 'Only a single default route 
network is allowed.')
Apr 19 14:58:20 ovirt-node04 vdsm-tool[55011]: ConfigNetworkError: (21, 'Only a 
single default route network is allowed.')
Apr 19 14:58:20 ovirt-node04 systemd[1]: vdsm-network.service: control process 
exited, code=exited status=1
Apr 19 14:58:20 ovirt-node04 systemd[1]: Failed to start Virtual Desktop Server 
Manager network restoration.
-- Subject: Unit vdsm-network.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit vdsm-network.service has failed.
-- 
-- The result is failed.
Apr 19 14:58:20 ovirt-node04 systemd[1]: Dependency failed for Virtual Desktop 
Server Manager.
-- Subject: Unit vdsmd.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit vdsmd.service has failed.
-- 
-- The result is dependency.
Apr 19 14:58:20 ovirt-node04 systemd[1]: Dependency failed for MOM instance 
configured for VDSM purposes.
-- Subject: Unit mom-vdsm.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit mom-vdsm.service has failed.
-- 
-- The result is dependency.
Apr 19 14:58:20 ovirt-node04 systemd[1]: Job mom-vdsm.service/start failed with 
result 'dependency'.
Apr 19 14:58:20 ovirt-node04 systemd[1]: Job vdsmd.service/start failed with 
result 'dependency'.
Apr 19 14:58:20 ovirt-node04 systemd[1]: Unit vdsm-network.service entered 
failed state.
Apr 19 14:58:20 ovirt-node04 systemd[1]: vdsm-network.service failed.
Apr 19 14:58:20 ovirt-node04 polkitd[3463]: Unregistered Authentication Agent 
for unix-process:55005:2145554 (system bus name :1.501, object path 
/org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) 
(disconnected from bus)

How should I solve the above problem?
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/3T7AFQJQFD774W63DRK4DBNPGRXOOIDV/