August 2021 - Users - oVirt List Archives

Why is it that after running clloud-init using run-once option, all the other configurations take effect except the network configuration?
by Tommy Sway 05 Aug '21

05 Aug '21

1、This is the cloud-init configure. 2. After booting, the network is:

2 6

Restored engine backup: The provided authorization grant for the auth code has expired.
by Nicolás 05 Aug '21

05 Aug '21

Hi, I'm restoring a full ovirt engine backup, having used the --scope=all option, for oVirt 4.3. I restored the backup on a fresh CentOS7 machine. The process went well, but when trying to log into the restored authentication system I get the following message which won't allow me to log in: The provided authorization grant for the auth code has expired. What does that mean and how can it be fixed? Thanks. Nicolás

4 10

Accessing the oVirt Console Remotely
by louisb＠ameritech.net 04 Aug '21

04 Aug '21

I've installed ovirt on the my server (HPDL380Gen10) and was able to start the configuration process on the local machine. I'm tried to access the ovirt console remotely via the web however I've had no success. I'm using the same URL that is used locally, but when I execute the URL via my Firefox browser I get the message that it is unable to connect. I've drop the firewall on both the server and client machine as a possible solution but it did not work. Is there something extra that is needed to access the ovirt console remotely? The FQDN is entered into my DNS, however, I did find that during the configuration process that IP was consumed by ovirtmgmt. I was surprised to see that I'm just assuming that its apart of congiruation process. I have other ports on my sever and I have entered them in my DNS also with the same name but a different IP address. What must I do to gain access to the ovirt console remotely, it would surely make the configuration process easy from my desk vs being in the server area. Thanks

2 1

Self hosted engine installation - Failed to deploy the VM on ISCSI storage
by ericsitunew＠gmail.com 04 Aug '21

04 Aug '21

I was trying to install the latest ovirt engine v4.4.7 but it failed at the following step when I was using the command line. I have tried installing as user root or other sudoers, but same issue. [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Copy configuration archive to storage] [ ERROR ] fatal: [localhost]: FAILED! => {"changed": true, "cmd": ["dd", "bs=20480", "count=1", "oflag=direct", "if=/var/tmp/localvmV8yIIX/5607a2c3-7e94-4403-ad86-7c3bcc745b16", "of=/rhev/data-center/mnt/blockSD/61612a87-4b25-4e09-aecd-02b63c679cf1/images/f9ebe70c-58f4-4229-a149-a18a09571d08/5607a2c3-7e94-4403-ad86-xxxxxxxxxxxx"], "delta": "0:00:00.011759", "end": "2020-08-14 09:03:35.702527", "msg": "non-zero return code", "rc": 1, "start": "2020-08-14 09:03:35.690768", "stderr": "dd: failed to open â/var/tmp/localvmV8yIIX/5607a2c3-7e94-4403-ad86-7c3bcc745b16â: Permission denied", "stderr_lines": ["dd: failed to open â/var/tmp/localvmV8yIIX/5607a2c3-7e94-4403-ad86-xxxxxxxxxxxx: Permission denied"], "stdout": "", "stdout_lines": []} [ ERROR ] Failed to execute stage 'Closing up': Failed executing ansible-playbook [ INFO ] Stage: Clean up [ INFO ] Cleaning temporary resources Just curious if anyone hits the same issue? Thank you.

3 2

Host not becoming active due to VDSM failure
by Vinícius Ferrão 03 Aug '21

03 Aug '21

Hello, I have a host that's failing to bring up VDSM, the logs don't say anything specific, but there's a Python error about DHCP on it. Is there anyone with a similar issue? [root@rhvpower ~]# systemctl status vdsmd ● vdsmd.service - Virtual Desktop Server Manager Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled; vendor preset: disabled) Active: inactive (dead) Jul 30 01:53:40 rhvpower.local.versatushpc.com.br systemd[1]: Dependency failed for Virtual Desktop Server Manager. Jul 30 01:53:40 rhvpower.local.versatushpc.com.br systemd[1]: vdsmd.service: Job vdsmd.service/start failed with result 'dependency'. Jul 30 12:34:12 rhvpower.local.versatushpc.com.br systemd[1]: Dependency failed for Virtual Desktop Server Manager. Jul 30 12:34:12 rhvpower.local.versatushpc.com.br systemd[1]: vdsmd.service: Job vdsmd.service/start failed with result 'dependency'. [root@rhvpower ~]# systemctl start vdsmd A dependency job for vdsmd.service failed. See 'journalctl -xe' for details. On the logs I got the following messages: ==> /var/log/vdsm/upgrade.log <== MainThread::DEBUG::2021-07-30 12:34:55,143::libvirtconnection::168::root::(get) trying to connect libvirt MainThread::INFO::2021-07-30 12:34:55,167::netconfpersistence::238::root::(_clearDisk) Clearing netconf: /var/lib/vdsm/staging/netconf MainThread::INFO::2021-07-30 12:34:55,178::netconfpersistence::188::root::(save) Saved new config RunningConfig({'ovirtmgmt': {'netmask': '255.255.255.0', 'bonding': 'bond0', 'ipv6autoconf': False, 'bridged': True, 'ipaddr': '10.20.0.106', 'defaultRoute': True, 'dhcpv6': False, 'gateway': '10.20.0.1', 'mtu': 1500, 'switch': 'legacy', 'stp': False, 'bootproto': 'none', 'nameservers': ['10.20.0.1']}, 'servers': {'vlan': 172, 'bonding': 'bond0', 'ipv6autoconf': False, 'bridged': True, 'dhcpv6': False, 'mtu': 1500, 'switch': 'legacy', 'defaultRoute': False, 'stp': False, 'bootproto': 'none', 'nameservers': []}, 'xcat-other': {'vlan': 2020, 'bonding': 'bond0', 'ipv6autoconf': False, 'bridged': True, 'dhcpv6': False, 'mtu': 1500, 'switch': 'legacy', 'defaultRoute': False, 'stp': False, 'bootproto': 'none', 'nameservers': []}, 'xcat-nodes1': {'vlan': 2021, 'bonding': 'bond0', 'ipv6autoconf': False, 'bridged': True, 'dhcpv6': False, 'mtu': 1500, 'switch': 'legacy', 'defaultRoute': False, 'stp': False, 'bootproto': 'none', 'nameservers': []}, 'xcat-nodes3': {'vlan': 2023, 'bonding': 'bond0', 'ipv6autoconf': False, 'bridged': True, 'dhcpv6': False, 'mtu': 1500, 'switch': 'legacy', 'defaultRoute': False, 'stp': False, 'bootproto': 'none', 'nameservers': []}, 'xcat-nodes2': {'vlan': 2022, 'bonding': 'bond0', 'ipv6autoconf': False, 'bridged': True, 'dhcpv6': False, 'mtu': 1500, 'switch': 'legacy', 'defaultRoute': False, 'stp': False, 'bootproto': 'none', 'nameservers': []}, 'nfs': {'vlan': 200, 'bonding': 'bond0', 'ipv6autoconf': False, 'bridged': True, 'dhcpv6': False, 'mtu': 1500, 'switch': 'legacy', 'defaultRoute': False, 'stp': False, 'bootproto': 'none', 'nameservers': []}, 'storage': {'vlan': 192, 'netmask': '255.255.255.240', 'bonding': 'bond0', 'ipv6autoconf': False, 'bridged': False, 'ipaddr': '192.168.10.6', 'dhcpv6': False, 'mtu': 1500, 'switch': 'legacy', 'defaultRoute': False, 'bootproto': 'none', 'nameservers': []}, 'xcat-nodes4': {'vlan': 2024, 'bonding': 'bond0', 'ipv6autoconf': False, 'bridged': True, 'dhcpv6': False, 'mtu': 1500, 'switch': 'legacy', 'defaultRoute': False, 'stp': False, 'bootproto': 'none', 'nameservers': []}}, {'bond0': {'nics': ['enP48p1s0f2', 'enP48p1s0f3'], 'options': 'mode=4', 'switch': 'legacy', 'hwaddr': '98:be:94:78:cc:72'}}, {}) to [/var/lib/vdsm/staging/netconf/nets,/var/lib/vdsm/staging/netconf/bonds,/var/lib/vdsm/staging/netconf/devices] MainThread::INFO::2021-07-30 12:34:55,179::netconfpersistence::238::root::(_clearDisk) Clearing netconf: /var/lib/vdsm/persistence/netconf MainThread::INFO::2021-07-30 12:34:55,188::netconfpersistence::188::root::(save) Saved new config PersistentConfig({'ovirtmgmt': {'netmask': '255.255.255.0', 'bonding': 'bond0', 'ipv6autoconf': False, 'bridged': True, 'ipaddr': '10.20.0.106', 'defaultRoute': True, 'dhcpv6': False, 'gateway': '10.20.0.1', 'mtu': 1500, 'switch': 'legacy', 'stp': False, 'bootproto': 'none', 'nameservers': ['10.20.0.1']}, 'servers': {'vlan': 172, 'bonding': 'bond0', 'ipv6autoconf': False, 'bridged': True, 'dhcpv6': False, 'mtu': 1500, 'switch': 'legacy', 'defaultRoute': False, 'stp': False, 'bootproto': 'none', 'nameservers': []}, 'xcat-other': {'vlan': 2020, 'bonding': 'bond0', 'ipv6autoconf': False, 'bridged': True, 'dhcpv6': False, 'mtu': 1500, 'switch': 'legacy', 'defaultRoute': False, 'stp': False, 'bootproto': 'none', 'nameservers': []}, 'xcat-nodes1': {'vlan': 2021, 'bonding': 'bond0', 'ipv6autoconf': False, 'bridged': True, 'dhcpv6': False, 'mtu': 1500, 'switch': 'legacy', 'defaultRoute': False, 'stp': False, 'bootproto': 'none', 'nameservers': []}, 'xcat-nodes3': {'vlan': 2023, 'bonding': 'bond0', 'ipv6autoconf': False, 'bridged': True, 'dhcpv6': False, 'mtu': 1500, 'switch': 'legacy', 'defaultRoute': False, 'stp': False, 'bootproto': 'none', 'nameservers': []}, 'xcat-nodes2': {'vlan': 2022, 'bonding': 'bond0', 'ipv6autoconf': False, 'bridged': True, 'dhcpv6': False, 'mtu': 1500, 'switch': 'legacy', 'defaultRoute': False, 'stp': False, 'bootproto': 'none', 'nameservers': []}, 'nfs': {'vlan': 200, 'bonding': 'bond0', 'ipv6autoconf': False, 'bridged': True, 'dhcpv6': False, 'mtu': 1500, 'switch': 'legacy', 'defaultRoute': False, 'stp': False, 'bootproto': 'none', 'nameservers': []}, 'storage': {'vlan': 192, 'netmask': '255.255.255.240', 'bonding': 'bond0', 'ipv6autoconf': False, 'bridged': False, 'ipaddr': '192.168.10.6', 'dhcpv6': False, 'mtu': 1500, 'switch': 'legacy', 'defaultRoute': False, 'bootproto': 'none', 'nameservers': []}, 'xcat-nodes4': {'vlan': 2024, 'bonding': 'bond0', 'ipv6autoconf': False, 'bridged': True, 'dhcpv6': False, 'mtu': 1500, 'switch': 'legacy', 'defaultRoute': False, 'stp': False, 'bootproto': 'none', 'nameservers': []}}, {'bond0': {'nics': ['enP48p1s0f2', 'enP48p1s0f3'], 'options': 'mode=4', 'switch': 'legacy', 'hwaddr': '98:be:94:78:cc:72'}}, {}) to [/var/lib/vdsm/persistence/netconf/nets,/var/lib/vdsm/persistence/netconf/bonds,/var/lib/vdsm/persistence/netconf/devices] MainThread::DEBUG::2021-07-30 12:34:55,188::cmdutils::130::root::(exec_cmd) /usr/share/openvswitch/scripts/ovs-ctl status (cwd None) ==> /var/log/vdsm/supervdsm.log <== restore-net::INFO::2021-07-30 12:34:55,924::restore_net_config::69::root::(_restore_sriov_config) Non persisted SRIOV devices found: {'0033:01:00.0', '0003:01:00.0'} restore-net::INFO::2021-07-30 12:34:55,924::restore_net_config::458::root::(restore) starting network restoration. restore-net::DEBUG::2021-07-30 12:34:55,942::restore_net_config::366::root::(_wait_for_for_all_devices_up) All devices are up. restore-net::DEBUG::2021-07-30 12:34:55,968::cmdutils::130::root::(exec_cmd) /sbin/tc qdisc show (cwd None) restore-net::DEBUG::2021-07-30 12:34:55,989::cmdutils::138::root::(exec_cmd) SUCCESS: <err> = b''; <rc> = 0 restore-net::DEBUG::2021-07-30 12:34:56,087::plugin::261::root::(_check_version_mismatch) NetworkManager version 1.30.0 restore-net::DEBUG::2021-07-30 12:34:56,088::context::144::root::(register_async) Async action: Retrieve applied config: ethernet enP48p1s0f2 started restore-net::DEBUG::2021-07-30 12:34:56,088::context::144::root::(register_async) Async action: Retrieve applied config: ethernet enP48p1s0f3 started restore-net::DEBUG::2021-07-30 12:34:56,088::context::144::root::(register_async) Async action: Retrieve applied config: bridge xcat-nodes3 started restore-net::DEBUG::2021-07-30 12:34:56,089::context::144::root::(register_async) Async action: Retrieve applied config: bridge xcat-other started restore-net::DEBUG::2021-07-30 12:34:56,089::context::144::root::(register_async) Async action: Retrieve applied config: bridge xcat-nodes4 started restore-net::DEBUG::2021-07-30 12:34:56,089::context::144::root::(register_async) Async action: Retrieve applied config: bridge ovirtmgmt started restore-net::DEBUG::2021-07-30 12:34:56,089::context::144::root::(register_async) Async action: Retrieve applied config: bond bond0 started restore-net::DEBUG::2021-07-30 12:34:56,089::context::144::root::(register_async) Async action: Retrieve applied config: vlan bond0.192 started restore-net::DEBUG::2021-07-30 12:34:56,089::context::144::root::(register_async) Async action: Retrieve applied config: vlan bond0.2020 started restore-net::DEBUG::2021-07-30 12:34:56,090::context::144::root::(register_async) Async action: Retrieve applied config: vlan bond0.2022 started restore-net::DEBUG::2021-07-30 12:34:56,090::context::144::root::(register_async) Async action: Retrieve applied config: vlan bond0.2024 started restore-net::DEBUG::2021-07-30 12:34:56,090::context::144::root::(register_async) Async action: Retrieve applied config: vlan bond0.172 started restore-net::DEBUG::2021-07-30 12:34:56,090::context::144::root::(register_async) Async action: Retrieve applied config: vlan bond0.2021 started restore-net::DEBUG::2021-07-30 12:34:56,090::context::144::root::(register_async) Async action: Retrieve applied config: vlan bond0.2023 started restore-net::DEBUG::2021-07-30 12:34:56,090::context::144::root::(register_async) Async action: Retrieve applied config: vlan bond0.200 started restore-net::DEBUG::2021-07-30 12:34:56,090::context::144::root::(register_async) Async action: Retrieve applied config: bridge xcat-nodes1 started restore-net::DEBUG::2021-07-30 12:34:56,090::context::144::root::(register_async) Async action: Retrieve applied config: bridge xcat-nodes2 started restore-net::DEBUG::2021-07-30 12:34:56,091::context::144::root::(register_async) Async action: Retrieve applied config: bridge nfs started restore-net::DEBUG::2021-07-30 12:34:56,091::context::144::root::(register_async) Async action: Retrieve applied config: bridge servers started restore-net::DEBUG::2021-07-30 12:34:56,091::context::144::root::(register_async) Async action: Retrieve applied config: bridge virbr0 started restore-net::DEBUG::2021-07-30 12:34:56,092::context::153::root::(finish_async) Async action: Retrieve applied config: ethernet enP48p1s0f2 finished restore-net::DEBUG::2021-07-30 12:34:56,093::context::153::root::(finish_async) Async action: Retrieve applied config: ethernet enP48p1s0f3 finished restore-net::DEBUG::2021-07-30 12:34:56,093::context::153::root::(finish_async) Async action: Retrieve applied config: bridge xcat-nodes3 finished restore-net::DEBUG::2021-07-30 12:34:56,094::context::153::root::(finish_async) Async action: Retrieve applied config: bridge xcat-other finished restore-net::DEBUG::2021-07-30 12:34:56,095::context::153::root::(finish_async) Async action: Retrieve applied config: bridge xcat-nodes4 finished restore-net::DEBUG::2021-07-30 12:34:56,096::context::153::root::(finish_async) Async action: Retrieve applied config: bridge ovirtmgmt finished restore-net::DEBUG::2021-07-30 12:34:56,097::context::153::root::(finish_async) Async action: Retrieve applied config: bond bond0 finished restore-net::DEBUG::2021-07-30 12:34:56,098::context::153::root::(finish_async) Async action: Retrieve applied config: vlan bond0.192 finished restore-net::DEBUG::2021-07-30 12:34:56,099::context::153::root::(finish_async) Async action: Retrieve applied config: vlan bond0.2020 finished restore-net::DEBUG::2021-07-30 12:34:56,099::context::153::root::(finish_async) Async action: Retrieve applied config: vlan bond0.2022 finished restore-net::DEBUG::2021-07-30 12:34:56,100::context::153::root::(finish_async) Async action: Retrieve applied config: vlan bond0.2024 finished restore-net::DEBUG::2021-07-30 12:34:56,100::context::153::root::(finish_async) Async action: Retrieve applied config: vlan bond0.172 finished restore-net::DEBUG::2021-07-30 12:34:56,101::context::153::root::(finish_async) Async action: Retrieve applied config: vlan bond0.2021 finished restore-net::DEBUG::2021-07-30 12:34:56,101::context::153::root::(finish_async) Async action: Retrieve applied config: vlan bond0.2023 finished restore-net::DEBUG::2021-07-30 12:34:56,102::context::153::root::(finish_async) Async action: Retrieve applied config: vlan bond0.200 finished restore-net::DEBUG::2021-07-30 12:34:56,102::context::153::root::(finish_async) Async action: Retrieve applied config: bridge xcat-nodes1 finished restore-net::DEBUG::2021-07-30 12:34:56,103::context::153::root::(finish_async) Async action: Retrieve applied config: bridge xcat-nodes2 finished restore-net::DEBUG::2021-07-30 12:34:56,105::context::153::root::(finish_async) Async action: Retrieve applied config: bridge nfs finished restore-net::DEBUG::2021-07-30 12:34:56,106::context::153::root::(finish_async) Async action: Retrieve applied config: bridge servers finished restore-net::DEBUG::2021-07-30 12:34:56,107::context::153::root::(finish_async) Async action: Retrieve applied config: bridge virbr0 finished restore-net::ERROR::2021-07-30 12:34:56,167::restore_net_config::462::root::(restore) restoration failed. Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/vdsm/network/restore_net_config.py", line 460, in restore unified_restoration() File "/usr/lib/python3.6/site-packages/vdsm/network/restore_net_config.py", line 112, in unified_restoration classified_conf = _classify_nets_bonds_config(available_config) File "/usr/lib/python3.6/site-packages/vdsm/network/restore_net_config.py", line 237, in _classify_nets_bonds_config net_info = NetInfo(netswitch.configurator.netinfo()) File "/usr/lib/python3.6/site-packages/vdsm/network/netswitch/configurator.py", line 323, in netinfo _netinfo = netinfo_get(vdsmnets, compatibility) File "/usr/lib/python3.6/site-packages/vdsm/network/netinfo/cache.py", line 268, in get return _get(vdsmnets) File "/usr/lib/python3.6/site-packages/vdsm/network/netinfo/cache.py", line 76, in _get extra_info.update(_get_devices_info_from_nmstate(state, devices)) File "/usr/lib/python3.6/site-packages/vdsm/network/netinfo/cache.py", line 165, in _get_devices_info_from_nmstate nmstate.get_interfaces(state, filter=devices) File "/usr/lib/python3.6/site-packages/vdsm/network/netinfo/cache.py", line 164, in <dictcomp> for ifname, ifstate in six.viewitems( File "/usr/lib/python3.6/site-packages/vdsm/network/nmstate/api.py", line 228, in is_dhcp_enabled return util_is_dhcp_enabled(family_info) File "/usr/lib/python3.6/site-packages/vdsm/network/nmstate/bridge_util.py", line 137, in is_dhcp_enabled return family_info[InterfaceIP.ENABLED] and family_info[InterfaceIP.DHCP] KeyError: 'dhcp' The engine is fencing the machine constantly but it reboots and come back with the same issue after reboot. Thanks all.

3 4

CPU performance test results in three scenarios
by Tommy Sway 03 Aug '21

03 Aug '21

Hello, I recently conducted a test to compare the CPU performance of a physical machine, a high performance VM (pass-through CPU, PIN CPU), and a common VM. Here are the results: 1. Physical machine: # sysbench --test=cpu --cpu-max-prime=100000000 --threads=2 run WARNING: the --test option is deprecated. You can pass a script name or path on the command line without any options. sysbench 1.0.17 (using system LuaJIT 2.0.4) Running the test with following options: Number of threads: 2 Initializing random number generator from current time Prime numbers limit: 100000000 Initializing worker threads... Threads started! CPU speed: events per second: 0.01 General statistics: total time: 346.0588s total number of events: 2 Latency (ms): min: 345943.52 avg: 346001.09 max: 346058.65 95th percentile: 100000.00 sum: 692002.17 Threads fairness: events (avg/stddev): 1.0000/0.00 execution time (avg/stddev): 346.0011/0.06 2. High Performance VM: # sysbench --test=cpu --cpu-max-prime=100000000 --threads=2 run WARNING: the --test option is deprecated. You can pass a script name or path on the command line without any options. sysbench 1.0.17 (using system LuaJIT 2.0.4) Running the test with following options: Number of threads: 2 Initializing random number generator from current time Prime numbers limit: 100000000 Initializing worker threads... Threads started! CPU speed: events per second: 0.01 General statistics: total time: 351.8625s total number of events: 2 Latency (ms): min: 351416.59 avg: 351639.01 max: 351861.43 95th percentile: 100000.00 sum: 703278.02 Threads fairness: events (avg/stddev): 1.0000/0.00 execution time (avg/stddev): 351.6390/0.22 3. Common VM: # sysbench --test=cpu --cpu-max-prime=100000000 --threads=2 run WARNING: the --test option is deprecated. You can pass a script name or path on the command line without any options. sysbench 1.0.17 (using system LuaJIT 2.0.4) Running the test with following options: Number of threads: 2 Initializing random number generator from current time Prime numbers limit: 100000000 Initializing worker threads... Threads started! CPU speed: events per second: 0.01 General statistics: total time: 354.9108s total number of events: 2 Latency (ms): min: 354761.26 avg: 354835.99 max: 354910.73 95th percentile: 100000.00 sum: 709671.99 Threads fairness: events (avg/stddev): 1.0000/0.00 execution time (avg/stddev): 354.8360/0.07 Result: There is little difference in CPU performance between these three scenarios, so why distinguish between high performance and regular virtual machines? I don't think it makes much sense.

3 3

The provided authorization grant for the auth code has expired.
by Nicolás 02 Aug '21

02 Aug '21

Hi, A time ago I posted a similar question and I couldn't get it solved. I couldn't spend more time on this up until now, so I'm trying again and having the same error, which I'm unable to fix. I would really appreciate some help since I cannot find any documentation for this. I'm restoring a full ovirt engine backup, having used the --scope=all option, for oVirt 4.3. I restored the backup on a fresh CentOS7 machine. The process went well, but when trying to log into the restored authentication system I get the following message which won't allow me to log in: The provided authorization grant for the auth code has expired. What does that mean and how can it be fixed? I'm also attaching a screenshot. Thanks. Nicolás

2 1

Question about cloud-init
by tommy 02 Aug '21

02 Aug '21

Hello, I have a question about cloud-init: After installing vm, I installed cloud-init immediately, and enabled its four services, and then I can use cloud-init in the admin interface. However, I don't know how cloud-init knows where to get the relevant information (such as host name, SSH secret key, etc.) that I configured on the admin interface ? For I haven't configured the data source for cloud-init. Why it can works ? Thanks!

3 5

Re: adding new host failed with error "CPU does not match the Cluster CPU Type"
by j o 02 Aug '21

02 Aug '21

When I run lscpu it shows the nx and vmx flags are present. Vitialization is enable in bios. I have vms running. Sent from my iPhone

1 0

Question about pci pass-thru
by Tony Pearce 02 Aug '21

02 Aug '21

I have recently added a fresh installed host on 4.4, with 3 x nvidia gpu's which have been passed through to a guest VM instance. The host also has a 1TB nvme SSD drive which we are using for the host OS install and /var/ partition size was modified to allow maximum space for the guest, the intent is to give maximum space to a guest for fast SSD storage. Because this is a partition, I have about 700GB that can be added or mapped to a guest "disk" image that is locked to the host. After doing the above and after learning how simple it was to map the three GPUs in pass-through mode, my question is - can I simply map a PCI SSD through to a guest in the same fashion as the GPUs? I have not yet tried and do not find much results via google search. The intent on this would be to provision the whole SSD to the guest (instead of using the SSD for the host OS and some of that space for a guest (disk) image. In this case I would use another disk for the host OS but that is fine. Has anyone done such a thing (PCI SSD passthrough) and are there any concerns? (apart from the normal concerns with VM and host passthrough) Kind regards, Tony Pearce

1 0

Set fixed VNC/Spice Password for VMs.
by Merlin Timm 02 Aug '21

02 Aug '21

Good day to all, I have a question about the console configuration of the VMs: By default, for each console connection to a VM, a password is set for 120 seconds, after that you can't use it again. We currently have the following concern: We want to access and control the VMs via the VNC/Spice of the Ovirt host. We have already tried to use the password from the console.vv for the connection and that works so far. Unfortunately we have to do this every 2 minutes when we want to connect again. We are currently building an automatic test pipeline and for this we need to access the VMs remotely before OS start and we want to be independent of a VNC server on the guest. This is only possible if we could connect to the VNC/Spice server from the Ovirt host. My question: would it be possible to fix the password or read it out via api every time you want to connect? I would appreciate a reply very much! Best regards Merlin Timm

5 12

Happy SysAdmin Day!
by Strahil Nikolov 02 Aug '21

02 Aug '21

Happy SysAdmin Day! I want to thank Duck and wish to all fellow SysAdmins in the oVirt community a Happy Holliday ! Best Regards,Strahil Nikolov

3 2

adding new host failed with error "CPU does not match the Cluster CPU Type lscpu"
by jimod4＠yahoo.com 01 Aug '21

01 Aug '21

i get the below error when i try to add a new kvm host to the cluster. I know that the cpu is a haswell. if i run "virsh capabilities" it returns <model>Haswell-noTSX-IBRS</model>. My KVM server is redhat 8.4 fully patched today on an DL-360 Gen9. oVirt is at 4.4.7.7-1.el8. i have tried many diffent CPU settings for the cluster and none of them work. this is new oVirt install. ERROR: "The host CPU does not match the Cluster CPU Type and is running in a degraded mode. It is missing the following CPU flags: vmx, model_Haswell-noTSX, nx. Please update the host CPU microcode or change the Cluster CPU Type." MIRCOCODE: root@kvm09 ~]# dmesg | grep 'microcode' [ 0.000000] microcode: microcode updated early to revision 0x46, date = 2021-01-27 [ 1.625108] microcode: sig=0x306f2, pf=0x1, revision=0x46 [ 1.625753] microcode: Microcode Update Driver: v2.2.

1 0

Change lease storage domain while VM running
by Gianluca Cecchi 01 Aug '21

01 Aug '21

Hello, on a 4.4.6 environment where I'm moving storage I want to change the lease domain for an HA VM. The VM is running and if I go and edit, change sd and then press ok button, I get a window with: " Changes that can be applied immediately: VM Lease " I don't select the "apply later" check box. But then instead when I confirm, I get an error window with: " vm_name: Cannot edit VM. Hot swapping of VM leases is not supported, please remove the current lease and then set a new one. " Possibly it is possible to hot add a lease but not swap? So I think the first window should be changed. Is this a known issue? No problem if I change the lease storage domain while the VM is powered off. I don't know if it is already fixed in 4.4.7... I'm going to check next days.. Gianluca

3 2

Re: Upload Image to NFS Storage Domain Doesn't Work
by Eyal Shenitzky 01 Aug '21

01 Aug '21

+Bella Khizgiyaev <bkhizgiy(a)redhat.com> can you please take a look? On Fri, 30 Jul 2021 at 16:15, Nur Imam Febrianto <nur_imam(a)outlook.com> wrote: > Hi, > > > > Lastly in 4.4.6, I have a problem that I couldn’t upload any image to > storage domain without clicking Test Connection. Well, after it was > acknowledge as a bug and solved at 4.4.7 now I have similar issue. If I > upload any image to Storage Domain that uses NFS it only show locked, and > then showing OK even if no data are uploaded (can confirm 5GB ISO showing > OK after only 1 second). This issue only occurs with NFS backend, another > storage domain that uses iSCSI work fine though. Any idea how to solve this > ? I’m using NFS Storage Domain for storing ISO and this issue bugged me all > the time. > > > > Thanks before. > > > > Regards, > > > > Nur Imam Febrianto > > > > > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)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/ACUKBWAM2ORQZ… > -- Regards, Eyal Shenitzky

1 0