- Users - oVirt List Archives

Upgraded ovirt-4.2 to ovirt-4.3 and VM run fails
by Gobinda Das 29 Apr '19

29 Apr '19

Hi, I have upgraded ovirt-4.2 to ovirt-4.3 and after upgrade while starting vms giving me error: Cannot run VM. There is no host that satisfies current scheduling constraints. See below for details: The host *node1.test.com <http://node1.test.com>* did not satisfy internal filter ClusterInMaintenance because the cluster is in maintenance and only highly available VMs are allowed to start. The host *node2.test.com <http://node2.test.com>* did not satisfy internal filter ClusterInMaintenance because the cluster is in maintenance and only highly available VMs are allowed to start. The host *node3.test.com <http://node3.test.com>* did not satisfy internal filter ClusterInMaintenance because the cluster is in maintenance and only highly available VMs are allowed to start. Eventhough cluster is not in maintenance mode. This setup is using gluster6 for storage. -- Thanks, Gobinda

2 1

HA VMs fail to start on host failure
by tezmobile＠googlemail.com 29 Apr '19

29 Apr '19

In a host failure situation, we see that oVirt tries to restart the VMs on other hosts in the cluster but this (more often than not) fails due to kvm being unable to acquire a write lock on the qcow2 image. We see ovirt attempt to restart the VMs several times, each time on different hosts but with the same outcome after which it gives up trying. After this we must log into the oVirt web interface and start the VM manually, which works fine (by this time we assume enough time has passed for the lock to clear itself). This behaviour is experienced with Centos 7.6, Libvirt 4.5.0-10, vdsm 4.30.13-1 Log excerpt from hosted engine: 2019-04-24 17:05:26,653+01 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (EE-ManagedThreadFactory-engineScheduled-Thread-82) [] VM 'ef7e04f0-764a-4cfe-96bf-c0862f1f5b83'(vm-21.example.local) moved from 'WaitForLaunch' --> 'Down' 2019-04-24 17:05:26,710+01 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-82) [] EVENT_ID: VM_DOWN_ERROR(119), VM vm-21.example.local is down with error. Exit message: internal error: process exited while connecting to monitor: 2019-04-24T16:04:48.049352Z qemu-kvm: -drive file=/rhev/data-center/mnt/192.168.111.111:_/21a1390b-b73b-46b1-85b9-2bbf9bba5308/images/c9d96ab6-cb0b-4fba-9b07-096ff750c7f7/16da3660-1afe-40a3-b868-3a74e74bab2f,format=qcow2,if=none,id=drive-ua-c9d96ab6-cb0b-4fba-9b07-096ff750c7f7,serial=c9d96ab6-cb0b-4fba-9b07-096ff750c7f7,werror=stop,rerror=stop,cache=none,aio=threads: 'serial' is deprecated, please use the corresponding option of '-device' instead 2019-04-24T16:04:48.079989Z qemu-kvm: -drive file=/rhev/data-center/mnt/192.168.111.111:_/21a1390b-b73b-46b1-85b9-2bbf9bba5308/images/c9d96ab6-cb0b-4fba-9b07-096ff750c7f7/16da3660-1afe-40a3-b868-3a74e74bab2f,format=qcow2,if=none,id=drive-ua-c9d96ab6-cb0b-4fba-9b07-096ff750c7f7,serial=c9d96ab6-cb0b-4fba-9b07-096ff750c7f7,werror=stop,rerror=stop,cache=none,aio=threads: Failed to get "write" lock So my question is, how can I either force oVirt to continue to try restarting the VM or delay the initial VM restart for enough time to allow locks to clear?

1 0

Template Disk Corruption
by Alex McWhirter 29 Apr '19

29 Apr '19

1. Create server template from server VM (so it's a full copy of the disk) 2. From template create a VM, override server to desktop, so that it become a qcow2 overlay to the template raw disk. 3. Boot VM 4. Shutdown VM 5. Delete VM Template disk is now corrupt, any new machines made from it will not boot. I can't see why this happens as the desktop optimized VM should have just been an overlay qcow file...

2 5

oVirt 4.3.2 Error: genev_sys_6081 is not present in the system
by Dee Slaw 29 Apr '19

29 Apr '19

Hello, I've installed oVirt 4.3.2 and the problem is that it log messages: VDSM ovirt-04 command Get Host Statistics failed: Internal JSON-RPC error: {'reason': '[Errno 19] genev_sys_6081 is not present in the system'} in Open Virtualization Manager. It also keeps on logging in /var/log/messages: Mar 22 11:51:03 ovirt-04 NetworkManager[8725]: <info> [1553244663.9861] device (genev_sys_6081): carrier: link connected Mar 22 11:51:03 ovirt-04 NetworkManager[8725]: <info> [1553244663.9864] manager: (genev_sys_6081): new Generic device (/org/freedesktop/NetworkManager/Devices/34160) Mar 22 11:51:03 ovirt-04 NetworkManager[8725]: <info> [1553244663.9866] device (genev_sys_6081): enslaved to non-master-type device ovs-system; ignoring Mar 22 11:51:03 ovirt-04 NetworkManager[8725]: <info> [1553244663.9906] device (genev_sys_6081): enslaved to non-master-type device ovs-system; ignoring Mar 22 11:51:03 ovirt-04 kernel: device genev_sys_6081 left promiscuous mode Mar 22 11:51:04 ovirt-04 kernel: device genev_sys_6081 entered promiscuous mode Mar 22 11:51:04 ovirt-04 NetworkManager[8725]: <info> [1553244664.0038] device (genev_sys_6081): carrier: link connected Mar 22 11:51:04 ovirt-04 NetworkManager[8725]: <info> [1553244664.0042] manager: (genev_sys_6081): new Generic device (/org/freedesktop/NetworkManager/Devices/34161) Mar 22 11:51:04 ovirt-04 NetworkManager[8725]: <info> [1553244664.0044] device (genev_sys_6081): enslaved to non-master-type device ovs-system; ignoring Mar 22 11:51:04 ovirt-04 NetworkManager[8725]: <info> [1553244664.0082] device (genev_sys_6081): enslaved to non-master-type device ovs-system; ignoring Mar 22 11:51:04 ovirt-04 kernel: device genev_sys_6081 left promiscuous mode Mar 22 11:51:04 ovirt-04 kernel: device genev_sys_6081 entered promiscuous mode Also I can see the following in /var/log/openvswitch: 2019-03-22T08:53:12.413Z|131047|bridge|WARN|could not add network device ovn-034a1c-0 to ofproto (File exists) 2019-03-22T08:53:12.431Z|131048|tunnel|WARN|ovn-a21088-0: attempting to add tunnel port with same config as port 'ovn-0836d7-0' (::->192.168.10.24, key=flow, legacy_l2, dp port=2) 2019-03-22T08:53:12.466Z|131055|connmgr|WARN|accept failed (Too many open files) 2019-03-22T08:53:12.466Z|131056|unixctl|WARN|punix:/var/run/openvswitch/ovs-vswitchd.9103.ctl: accept failed: Too many open files In ovsdb-server.log: 2019-03-22T03:24:12.583Z|05792|jsonrpc|WARN|unix#28684: receive error: Connection reset by peer 2019-03-22T03:24:12.583Z|05793|reconnect|WARN|unix#28684: connection dropped (Connection reset by peer) How to fix this issue with geneve tunnels?

4 11

Re: All Windows vms report "Actual timezone in guest doesn't match configuration"
by Strahil 29 Apr '19

29 Apr '19

What happens when you restart ovirt agent services ? Best Regards, Strqhil NikolovOn Apr 26, 2019 03:06, michael(a)wanderingmad.com wrote: > > All of my windows VMs have a yellow exclamation point with the timezone error. The configuration in ovirt says eastern time, and I've tried changing the VM from eastern time to US eastern time, and error does not go away. This is with the latest ovirt guest tools for windows. > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/XL6XHN5KIEM7G…

2 1

Fetching DiskAttachmentService in ovirt-python-sdk-4
by Kaustav Majumder 29 Apr '19

29 Apr '19

Hi, I am trying to detach and delete disk from my vm. I found this service in the docs DiskAttachmentService http://ovirt.github.io/ovirt-engine-sdk/master/services.m.html#ovirtsdk4.se… I am not able to fetch this service. Below if the snippet of code I am trying. https://pastebin.com/UUu0Pfc8 Error--> File "./pre_setup/delete_vm_disk.py", line 19, in remove_attached_vm_disk attachment.remove(detach_only=False) AttributeError: 'DiskAttachment' object has no attribute 'remove' -- Thanks, Kaustav Majumder

3 4

One Way Flights Deals - Tripiflights
by marketings＠tripiflights.com 29 Apr '19

29 Apr '19

searching for one way flights deals . tripiflights is the perfect place for you. Here you will get best options at reasonable rates - https://go2article.com/article/one-way-flights-deals-tripiflights/

1 0

unable to upload disk images after upgrade to 4.3.3 -- ticket failures
by Edward Berger 29 Apr '19

29 Apr '19

Previously I had issues with the upgrades to 4.3.3 failing because of "stale" image transfer data, so I removed it from the database using the info given here on the mailing list and was able to complete the oVirt node and engine upgrades. Now I have a new problem. I can't upload a disk image anymore, which used to work. "test connection" returns success. In the dashboard Storage/Disks view, it starts and then stops with "paused by system" I tried pointing it at another node, same problem. I tried restarting services ovirt-imageio-proxy on engine and ovirt-imageio-daemon on the node, same failure. in the dashboard events when trying to upload disk I get this error Transfer was stopped by system. Reason: failed to add image ticket to ovirt-imageio-proxy. or when trying to resume transfer "paused by system" giving it the local path again. Transfer was stopped by system. Reason: failure in transfer image ticket renewal. I'm not sure what logs I should be looking deeper into.. Here's what the database says engine=# select * from image_transfers; -[ RECORD 1 ]-------------+------------------------------------- command_id | 59dce2b1-f8ba-44dd-9df9-c6e39773a3f9 command_type | 1024 phase | 4 last_updated | 2019-04-23 12:22:25.098-04 message | Uploading from byte 0 vds_id | disk_id | 6693d5ac-d3eb-43d7-9abe-97c5197efc23 imaged_ticket_id | proxy_uri | signed_ticket | bytes_sent | 0 bytes_total | 1996488704 type | 2 active | f daemon_uri | client_inactivity_timeout | 60 -[ RECORD 2 ]-------------+------------------------------------- command_id | 16898219-be5b-4826-8f20-3355fa47272a command_type | 1024 phase | 4 last_updated | 2019-04-23 16:15:34.591-04 message | Uploading from byte 0 vds_id | disk_id | 3b8e3053-bfe4-49d3-abd2-5452b1674400 imaged_ticket_id | proxy_uri | signed_ticket | bytes_sent | 0 bytes_total | 1998585856 type | 2 active | f daemon_uri | client_inactivity_timeout | 60 I really need the image uploading to work. Any suggestions on what to do next?

2 2

removal of vdsm-hook-macspoof
by Dan Kenigsberg 28 Apr '19

28 Apr '19

vdsm-hook-macspoof was created to let VM owners override the vdsm-no-mac-spoofing that was once hard-coded on each vNIC. Since ovirt-4.0's Bug 1317441 - [RFE] Allow MAC Anti-Spoofing per interface instead of globally the hook is no longer needed, because ovirt-engine supports selection of filters, including the "Empty" one. Thus, we can finally drop vdsm-hook-macspoof from vdsm code. https://gerrit.ovirt.org/#/c/94613/ does that. If someone still depends on setting the ifacemacspoof custom property, they can find and fix the vnic profiles using a script similar to the following one. Note that ovirtlib does not yet have an easy-to-pull canonical location. from __future__ import print_function import sys from ovirtlib.system import SDKSystemRoot from ovirtlib.netlib import Network, VnicProfile, CustomProperty, NetworkFilter from ovirtlib.datacenterlib import DataCenter system = SDKSystemRoot() system.connect(url=URL, insecure=True, password=PASSWORD, username=USER) spoof_cp = CustomProperty(name='ifacemacspoof', value='true') broken_profiles = [ profile for profile in VnicProfile.iterate(system) if spoof_cp in profile.custom_properties and profile.filter and profile.filter.name == 'vdsm-no-mac-spoofing'] if broken_profiles: if '--modify' in sys.argv: print('clearing vdsm-no-mac-spoof filter from profiles:') for profiles in broken_profiles: print(profile.name) profile.filter = None else: print('''ifacemacspoof custom property is no longer supported by vdsm. vnic profiles that depended on it for connectivity, e.g they serve VMs with in-guest bonds or vlans, must use an empty network filter instead. profiles with ifacemacspoof and vdsm-no-mac-spoof filter:''') for profiles in broken_profiles: print(profile.name) print('run again with --modify to remove the filter') else: print('no profile with ifacemacspoof and vdsm-no-mac-spoof was found.')

1 0

Resuming VM from suspend that is based on iscsi/fc raise an exception.
by 王猛 28 Apr '19

28 Apr '19

Hi, When I resume a VM from suspend that is based on iscsi or fcp, there's always an exception: ----- 2019-04-17 19:33:58,835+0800 ERROR (vm/baaabf11) [virt.vm] (vmId='baaabf11-172d-4fac-9862-86ff05feb085') The vm start process failed (vm:937) 378 Traceback (most recent call last): 379 File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 866, in _startUnderlyingVm 380 self._run() 381 File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2819, in _run 382 self._connection.restore(fname) 383 File "/usr/lib/python2.7/site-packages/vdsm/common/libvirtconnection.py", line 131, in wrapper 384 ret = f(*args, **kwargs) 385 File "/usr/lib/python2.7/site-packages/vdsm/common/function.py", line 94, in wrapper 386 return func(inst, *args, **kwargs) 387 File "/usr/lib64/python2.7/site-packages/libvirt.py", line 4513, in restore 388 if ret == -1: raise libvirtError ('virDomainRestore() failed', conn=self) 389 libvirtError: internal error: Child process (gzip -dc) unexpected exit status 2: 390 gzip: stdin: decompression OK, trailing garbage ignored 391 392 2019-04-17 19:33:58,835+0800 INFO (vm/baaabf11) [virt.vm] (vmId='baaabf11-172d-4fac-9862-86ff05feb085') Changed state to Down: internal error: Child process (gzip -dc) unexpected exit status 2: 393 gzip: stdin: decompression OK, trailing garbage ignored 394 (code=1) (vm:1675) ---------- After i read the Bug 1503468 (https://bugzilla.redhat.com/show_bug.cgi?id=1503468#c40) I know the reason why that happened. But how should I avoid this exception? The only method i know and tested is to change gzip to lzop in /etc/libvirt/qemu.conf. But this is not the way to solve the problem. -- 王猛软件研发手机：13021702660 地址：济南市高新区银荷大厦B座10层 250101 邮箱: wang_meng(a)massclouds.com 网址: www.massclouds.com 山东乾云启创信息科技有限公司

1 0