- Users - oVirt List Archives

unable to bring up hosted engine after botched 4.2 upgrade
by Jayme 12 Jan '18

12 Jan '18

Please help, I'm really not sure what else to try at this point. Thank you for reading! I'm still working on trying to get my hosted engine running after a botched upgrade to 4.2. Storage is NFS mounted from within one of the hosts. Right now I have 3 centos7 hosts that are fully updated with yum packages from ovirt 4.2, the engine was fully updated with yum packages and failed to come up after reboot. As of right now, everything should have full yum updates and all having 4.2 rpms. I have global maintenance mode on right now and started hosted-engine on one of the three host and the status is currently: Engine status : {"reason": "failed liveliness check”; "health": "bad", "vm": "up", "detail": "Up"} this is what I get when trying to enter hosted-vm --console The engine VM is running on this host error: failed to get domain 'HostedEngine' error: Domain not found: no domain with matching name 'HostedEngine' Here are logs from various sources when I start the VM on HOST3: hosted-engine --vm-start Command VM.getStats with args {'vmID': '4013c829-c9d7-4b72-90d5-6fe58137504c'} failed: (code=1, message=Virtual machine does not exist: {'vmId': u'4013c829-c9d7-4b72-90d5-6fe58137504c'}) Jan 11 16:55:57 cultivar3 systemd-machined: New machine qemu-110-Cultivar. Jan 11 16:55:57 cultivar3 systemd: Started Virtual Machine qemu-110-Cultivar. Jan 11 16:55:57 cultivar3 systemd: Starting Virtual Machine qemu-110-Cultivar. Jan 11 16:55:57 cultivar3 kvm: 3 guests now active ==> /var/log/vdsm/vdsm.log <== File "/usr/lib/python2.7/site-packages/vdsm/common/api.py", line 48, in method ret = func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/storage/hsm.py", line 2718, in getStorageDomainInfo dom = self.validateSdUUID(sdUUID) File "/usr/lib/python2.7/site-packages/vdsm/storage/hsm.py", line 304, in validateSdUUID sdDom.validate() File "/usr/lib/python2.7/site-packages/vdsm/storage/fileSD.py", line 515, in validate raise se.StorageDomainAccessError(self.sdUUID) StorageDomainAccessError: Domain is either partially accessible or entirely inaccessible: (u'248f46f0-d793-4581-9810-c9d965e2f286',) jsonrpc/2::ERROR::2018-01-11 16:55:16,144::dispatcher::82::storage.Dispatcher::(wrapper) FINISH getStorageDomainInfo error=Domain is either partially accessible or entirely inaccessible: (u'248f46f0-d793-4581-9810-c9d965e2f286',) ==> /var/log/libvirt/qemu/Cultivar.log <== LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin QEMU_AUDIO_DRV=spice /usr/libexec/qemu-kvm -name guest=Cultivar,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-108-Cultivar/master-key.aes -machine pc-i440fx-rhel7.3.0,accel=kvm,usb=off,dump-guest-core=off -cpu Conroe -m 8192 -realtime mlock=off -smp 2,maxcpus=16,sockets=16,cores=1,threads=1 -uuid 4013c829-c9d7-4b72-90d5-6fe58137504c -smbios 'type=1,manufacturer=oVirt,product=oVirt Node,version=7-4.1708.el7.centos,serial=44454C4C-4300-1034-8035-CAC04F424331,uuid=4013c829-c9d7-4b72-90d5-6fe58137504c' -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-108-Cultivar/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=2018-01-11T20:33:19,driftfix=slew -global kvm-pit.lost_tick_policy=delay -no-hpet -no-reboot -boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x4 -drive file=/var/run/vdsm/storage/248f46f0-d793-4581-9810-c9d965e2f286/c2dde892-f978-4dfc-a421-c8e04cf387f9/23aa0a66-fa6c-4967-a1e5-fbe47c0cd705,format=raw,if=none,id=drive-virtio-disk0,serial=c2dde892-f978-4dfc-a421-c8e04cf387f9,cache=none,werror=stop,rerror=stop,aio=threads -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive if=none,id=drive-ide0-1-0,readonly=on -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev tap,fd=30,id=hostnet0,vhost=on,vhostfd=32 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=00:16:3e:7f:d6:83,bus=pci.0,addr=0x3 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channels/4013c829-c9d7-4b72-90d5-6fe58137504c.com.redhat.rhevm.vdsm,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.rhevm.vdsm -chardev socket,id=charchannel1,path=/var/lib/libvirt/qemu/channels/4013c829-c9d7-4b72-90d5-6fe58137504c.org.qemu.guest_agent.0,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=channel1,name=org.qemu.guest_agent.0 -chardev spicevmc,id=charchannel2,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=3,chardev=charchannel2,id=channel2,name=com.redhat.spice.0 -chardev socket,id=charchannel3,path=/var/lib/libvirt/qemu/channels/4013c829-c9d7-4b72-90d5-6fe58137504c.org.ovirt.hosted-engine-setup.0,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=4,chardev=charchannel3,id=channel3,name=org.ovirt.hosted-engine-setup.0 -chardev pty,id=charconsole0 -device virtconsole,chardev=charconsole0,id=console0 -spice tls-port=5900,addr=0,x509-dir=/etc/pki/vdsm/libvirt-spice,tls-channel=default,seamless-migration=on -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -object rng-random,id=objrng0,filename=/dev/urandom -device virtio-rng-pci,rng=objrng0,id=rng0,bus=pci.0,addr=0x5 -msg timestamp=on 2018-01-11T20:33:19.699999Z qemu-kvm: -chardev pty,id=charconsole0: char device redirected to /dev/pts/2 (label charconsole0) 2018-01-11 20:38:11.640+0000: shutting down, reason=shutdown 2018-01-11 20:39:02.122+0000: starting up libvirt version: 3.2.0, package: 14.el7_4.7 (CentOS BuildSystem <http://bugs.centos.org>, 2018-01-04-19:31:34, c1bm.rdu2.centos.org) qemu version: 2.9.0(qemu-kvm-ev-2.9.0-16.el7_4.13.1), hostname: cultivar3 LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin QEMU_AUDIO_DRV=spice /usr/libexec/qemu-kvm -name guest=Cultivar,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-109-Cultivar/master-key.aes -machine pc-i440fx-rhel7.3.0,accel=kvm,usb=off,dump-guest-core=off -cpu Conroe -m 8192 -realtime mlock=off -smp 2,maxcpus=16,sockets=16,cores=1,threads=1 -uuid 4013c829-c9d7-4b72-90d5-6fe58137504c -smbios 'type=1,manufacturer=oVirt,product=oVirt Node,version=7-4.1708.el7.centos,serial=44454C4C-4300-1034-8035-CAC04F424331,uuid=4013c829-c9d7-4b72-90d5-6fe58137504c' -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-109-Cultivar/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=2018-01-11T20:39:02,driftfix=slew -global kvm-pit.lost_tick_policy=delay -no-hpet -no-reboot -boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x4 -drive file=/var/run/vdsm/storage/248f46f0-d793-4581-9810-c9d965e2f286/c2dde892-f978-4dfc-a421-c8e04cf387f9/23aa0a66-fa6c-4967-a1e5-fbe47c0cd705,format=raw,if=none,id=drive-virtio-disk0,serial=c2dde892-f978-4dfc-a421-c8e04cf387f9,cache=none,werror=stop,rerror=stop,aio=threads -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive if=none,id=drive-ide0-1-0,readonly=on -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev tap,fd=30,id=hostnet0,vhost=on,vhostfd=32 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=00:16:3e:7f:d6:83,bus=pci.0,addr=0x3 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channels/4013c829-c9d7-4b72-90d5-6fe58137504c.com.redhat.rhevm.vdsm,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.rhevm.vdsm -chardev socket,id=charchannel1,path=/var/lib/libvirt/qemu/channels/4013c829-c9d7-4b72-90d5-6fe58137504c.org.qemu.guest_agent.0,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=channel1,name=org.qemu.guest_agent.0 -chardev spicevmc,id=charchannel2,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=3,chardev=charchannel2,id=channel2,name=com.redhat.spice.0 -chardev socket,id=charchannel3,path=/var/lib/libvirt/qemu/channels/4013c829-c9d7-4b72-90d5-6fe58137504c.org.ovirt.hosted-engine-setup.0,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=4,chardev=charchannel3,id=channel3,name=org.ovirt.hosted-engine-setup.0 -chardev pty,id=charconsole0 -device virtconsole,chardev=charconsole0,id=console0 -spice tls-port=5900,addr=0,x509-dir=/etc/pki/vdsm/libvirt-spice,tls-channel=default,seamless-migration=on -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -object rng-random,id=objrng0,filename=/dev/urandom -device virtio-rng-pci,rng=objrng0,id=rng0,bus=pci.0,addr=0x5 -msg timestamp=on 2018-01-11T20:39:02.380773Z qemu-kvm: -chardev pty,id=charconsole0: char device redirected to /dev/pts/2 (label charconsole0) 2018-01-11 20:53:11.407+0000: shutting down, reason=shutdown 2018-01-11 20:55:57.210+0000: starting up libvirt version: 3.2.0, package: 14.el7_4.7 (CentOS BuildSystem <http://bugs.centos.org>, 2018-01-04-19:31:34, c1bm.rdu2.centos.org) qemu version: 2.9.0(qemu-kvm-ev-2.9.0-16.el7_4.13.1), hostname: cultivar3.grove.silverorange.com LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin QEMU_AUDIO_DRV=spice /usr/libexec/qemu-kvm -name guest=Cultivar,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-110-Cultivar/master-key.aes -machine pc-i440fx-rhel7.3.0,accel=kvm,usb=off,dump-guest-core=off -cpu Conroe -m 8192 -realtime mlock=off -smp 2,maxcpus=16,sockets=16,cores=1,threads=1 -uuid 4013c829-c9d7-4b72-90d5-6fe58137504c -smbios 'type=1,manufacturer=oVirt,product=oVirt Node,version=7-4.1708.el7.centos,serial=44454C4C-4300-1034-8035-CAC04F424331,uuid=4013c829-c9d7-4b72-90d5-6fe58137504c' -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-110-Cultivar/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=2018-01-11T20:55:57,driftfix=slew -global kvm-pit.lost_tick_policy=delay -no-hpet -no-reboot -boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x4 -drive file=/var/run/vdsm/storage/248f46f0-d793-4581-9810-c9d965e2f286/c2dde892-f978-4dfc-a421-c8e04cf387f9/23aa0a66-fa6c-4967-a1e5-fbe47c0cd705,format=raw,if=none,id=drive-virtio-disk0,serial=c2dde892-f978-4dfc-a421-c8e04cf387f9,cache=none,werror=stop,rerror=stop,aio=threads -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive if=none,id=drive-ide0-1-0,readonly=on -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev tap,fd=30,id=hostnet0,vhost=on,vhostfd=32 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=00:16:3e:7f:d6:83,bus=pci.0,addr=0x3 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channels/4013c829-c9d7-4b72-90d5-6fe58137504c.com.redhat.rhevm.vdsm,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.rhevm.vdsm -chardev socket,id=charchannel1,path=/var/lib/libvirt/qemu/channels/4013c829-c9d7-4b72-90d5-6fe58137504c.org.qemu.guest_agent.0,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=channel1,name=org.qemu.guest_agent.0 -chardev spicevmc,id=charchannel2,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=3,chardev=charchannel2,id=channel2,name=com.redhat.spice.0 -chardev socket,id=charchannel3,path=/var/lib/libvirt/qemu/channels/4013c829-c9d7-4b72-90d5-6fe58137504c.org.ovirt.hosted-engine-setup.0,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=4,chardev=charchannel3,id=channel3,name=org.ovirt.hosted-engine-setup.0 -chardev pty,id=charconsole0 -device virtconsole,chardev=charconsole0,id=console0 -spice tls-port=5900,addr=0,x509-dir=/etc/pki/vdsm/libvirt-spice,tls-channel=default,seamless-migration=on -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -object rng-random,id=objrng0,filename=/dev/urandom -device virtio-rng-pci,rng=objrng0,id=rng0,bus=pci.0,addr=0x5 -msg timestamp=on 2018-01-11T20:55:57.468037Z qemu-kvm: -chardev pty,id=charconsole0: char device redirected to /dev/pts/2 (label charconsole0) ==> /var/log/ovirt-hosted-engine-ha/broker.log <== File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/storage_broker.py", line 151, in get_raw_stats f = os.open(path, direct_flag | os.O_RDONLY | os.O_SYNC) OSError: [Errno 2] No such file or directory: '/var/run/vdsm/storage/248f46f0-d793-4581-9810-c9d965e2f286/14a20941-1b84-4b82-be8f-ace38d7c037a/8582bdfc-ef54-47af-9f1e-f5b7ec1f1cf8' StatusStorageThread::ERROR::2018-01-11 16:55:15,761::status_broker::92::ovirt_hosted_engine_ha.broker.status_broker.StatusBroker.Update::(run) Failed to read state. Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/status_broker.py", line 88, in run self._storage_broker.get_raw_stats() File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/storage_broker.py", line 162, in get_raw_stats .format(str(e))) RequestError: failed to read metadata: [Errno 2] No such file or directory: '/var/run/vdsm/storage/248f46f0-d793-4581-9810-c9d965e2f286/14a20941-1b84-4b82-be8f-ace38d7c037a/8582bdfc-ef54-47af-9f1e-f5b7ec1f1cf8' ==> /var/log/ovirt-hosted-engine-ha/agent.log <== result = refresh_method() File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/env/config.py", line 519, in refresh_vm_conf content = self._get_file_content_from_shared_storage(VM) File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/env/config.py", line 484, in _get_file_content_from_shared_storage config_volume_path = self._get_config_volume_path() File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/env/config.py", line 188, in _get_config_volume_path conf_vol_uuid File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/heconflib.py", line 358, in get_volume_path root=envconst.SD_RUN_DIR, RuntimeError: Path to volume 4838749f-216d-406b-b245-98d0343fcf7f not found in /run/vdsm/storag ==> /var/log/vdsm/vdsm.log <== periodic/42::ERROR::2018-01-11 16:56:11,446::vmstats::260::virt.vmstats::(send_metrics) VM metrics collection failed Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/virt/vmstats.py", line 197, in send_metrics data[prefix + '.cpu.usage'] = stat['cpuUsage'] KeyError: 'cpuUsage'

4 8

Some major problems after 4.2 upgrade, could really use some assistance
by Jayme 12 Jan '18

12 Jan '18

I performed Ovirt 4.2 upgrade on a 3 host cluster with NFS shared storage. The shared storage is mounted from one of the hosts. I upgraded the hosted engine first, downloading the 4.2 rpm, doing a yum update then engine setup which seemed to complete successfully, at the end it powered down the hosted VM but it never came back up. I was unable to start it. I proceeded to upgrade the three hosts, ovirt 4.2 rpm and a full yum update. I also rebooted each of the three hosts. After some time the hosts did come back and almost all of the VMs are running again and seem to be working ok with the exception of two: 1. The hosted VM still will not start, I've tried everything I can think of. 2. A VM that I know existed is not running and does not appear to exist, I have no idea where it is or how to start it. 1. Hosted engine >From one of the hosts I get a weird error trying to start it: # hosted-engine --vm-start Command VM.getStats with args {'vmID': '4013c829-c9d7-4b72-90d5-6fe58137504c'} failed: (code=1, message=Virtual machine does not exist: {'vmId': u'4013c829-c9d7-4b72-90d5-6fe58137504c'}) >From the two other hosts I do not get the same error as above, sometimes it appears to start but --vm-status shows errors such as: Engine status : {"reason": "failed liveliness check", "health": "bad", "vm": "up", "detail": "Up"} Seeing these errors in syslog: Jan 11 01:06:30 host0 libvirtd: 2018-01-11 05:06:30.473+0000: 1910: error : qemuOpenFileAs:3183 : Failed to open file '/var/run/vdsm/storage/248f46f0-d793-4581-9810-c9d965e2f286/c2dde892-f978-4dfc-a421-c8e04cf387f9/23aa0a66-fa6c-4967-a1e5-fbe47c0cd705': No such file or directory Jan 11 01:06:30 host0 libvirtd: 2018-01-11 05:06:30.473+0000: 1910: error : qemuDomainStorageOpenStat:11492 : cannot stat file '/var/run/vdsm/storage/248f46f0-d793-4581-9810-c9d965e2f286/c2dde892-f978-4dfc-a421-c8e04cf387f9/23aa0a66-fa6c-4967-a1e5-fbe47c0cd705': Bad file descriptor 2. Missing VM. virsh -r list on each host does not show the VM at all. I know it existed and is important. The log on one of the hosts even shows that it started it recently then stopped in 10 or so minutes later: Jan 10 18:47:17 host3 systemd-machined: New machine qemu-9-Berna. Jan 10 18:47:17 host3 systemd: Started Virtual Machine qemu-9-Berna. Jan 10 18:47:17 host3 systemd: Starting Virtual Machine qemu-9-Berna. Jan 10 18:54:45 host3 systemd-machined: Machine qemu-9-Berna terminated. How can I find out the status of the "Berna" VM and get it running again? Thanks so much!

3 2

hosted_engine
by volga629＠networklab.ca 12 Jan '18

12 Jan '18

Hello Everyone, Is possible in 4.2 migrate hosted_engine to another storage from same type. Right now I am trying migrate from old to new iscsi storage. volga629

2 1

non operational node
by Tomeu Sastre Cabanellas 12 Jan '18

12 Jan '18

hi there, i'm testing ovirt 4.2 because I want to migrate all our VMs from XenServer, I have set a engine and a node, when conecting to the node I receive a "non-operational" and I cannot set it to ON. I'm an experienced engineer, but I'm new with oVirt, any clue where do I have to start to check ? thanks a lot. [image: Inline images 1]

3 2

wheel next to the up triangle in the UI
by Nathanaël Blanchet 12 Jan '18

12 Jan '18

Hi all, I'm using vagrant ovirt4 plugin to provision some vms, and I noticed that a wheel is still present next to the up status of those vms. What does that mean? -- Nathanaël Blanchet Supervision réseau Pôle Infrastrutures Informatiques 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanchet(a)abes.fr

2 3

[ANN] oVirt 4.2.1 First Release Candidate is now available
by Sandro Bonazzola 12 Jan '18

12 Jan '18

The oVirt Project is pleased to announce the availability of the oVirt 4.2.1 First Release Candidate, as of January 12th, 2017 This update is the first in a series of stabilization updates to the 4.2 series. This release is available now for: * Red Hat Enterprise Linux 7.4 or later * CentOS Linux (or similar) 7.4 or later This release supports Hypervisor Hosts running: * Red Hat Enterprise Linux 7.4 or later * CentOS Linux (or similar) 7.4 or later * oVirt Node 4.2 See the release notes [1] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available - oVirt Live is already available [2] - oVirt Node will be available soon [2] Additional Resources: * Read more about the oVirt 4.2.1 release highlights: http://www.ovirt.org/release/4.2.1/ * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/4.2.1/ [2] http://resources.ovirt.org/pub/ovirt-4.2-pre/iso/ -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

1 0

unlock_entity.sh oVirt 4.2
by Grundmann, Christian 12 Jan '18

12 Jan '18

--_000_6A17C71B52524C408E7AAF69103E9E490FFBF1A1fabamailserverf_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, i have a VM on oVirt 4.2 which is locked after a snapshot revert. i unlocked the disk/snapshot and vm with unlock_entity.sh it now shows no locks /usr/share/ovirt-engine/setup/dbutils/unlock_entity.sh -t all -q Locked VMs: Locked templates: Locked disks: Locked snapshots: But the VM still shows "Image Locked" How can I unlock them? Thx Christian --_000_6A17C71B52524C408E7AAF69103E9E490FFBF1A1fabamailserverf_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr= osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:= //www.w3.org/TR/REC-html40"> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"= > <meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)"> <style></style> </head> <body lang=3D"DE" link=3D"#0563C1" vlink=3D"#954F72"> <div class=3D"WordSection1"> Hi,<o:p></o:p> i have a VM on oVirt 4.2 which is locked after a sna= pshot revert.<o:p></o:p> <o:p> </o:p> i unlocked the disk/snapshot and vm with unlock_enti= ty.sh<o:p></o:p> <o:p> </o:p> it now shows no locks<o:p></o:p> <o:p> </o:p> /usr/share/ovirt-eng= ine/setup/dbutils/unlock_entity.sh -t all -q<o:p></o:p> Locked VMs:<o:p></o:= p> <o:p> </o:p></s= pan> Locked templates:<o:= p></o:p> <o:p> </o:p></s= pan> Locked disks:<o:p></= o:p> <o:p> </o:p></s= pan> Locked snapshots:<o:= p></o:p> <o:p> </o:p></s= pan> <o:p> </o:p> But the VM still shows „Image Locked“<o:= p></o:p> <o:p> </o:p> How can I unlock them?<o:p></o:p> <o:p> </o:p> Thx Christian<o:p></o:p> </div> </body> </html> --_000_6A17C71B52524C408E7AAF69103E9E490FFBF1A1fabamailserverf_--

1 0

10Gb Networking with OVN
by Beau Sapach 12 Jan '18

12 Jan '18

Hello everyone, I see here: https://www.ovirt.org/blog/2017/09/introducing-ovirt-4.2.0/ that version 4.2 will have OVN support. Does anyone know if this will allow VMs to take advantage of 10Gb networking without needing SR-IOV? -- Beau Sapach *System Administrator | Information Technology Services | University of Alberta Libraries* *Phone: 780.492.4181 | Email: Beau.Sapach(a)ualberta.ca <Beau.Sapach(a)ualberta.ca>*

4 6

Re: [ovirt-users] Some major problems after 4.2 upgrade, could really use some assistance
by Jayme 11 Jan '18

11 Jan '18

This is becoming critical for me, does anyone have any ideas or recommendations on what I can do to recover access to hosted VM? As of right now I have three hosts that are fully updated, they have the 4.2 repo and a full yum update was performed on them, there are no new updates to apply. The hosted engine had updates as well as a full and complete engine-setup, but did not return after being shut down. There must be some way I can get the engine running again? Please On Thu, Jan 11, 2018 at 8:24 AM, Jayme <jaymef(a)gmail.com> wrote: > The hosts have all ready been fully updated with 4.2 packages though. > > ex. > > ovirt-host.x86_64 > 4.2.0-1.el7.centos @ovirt-4.2 > ovirt-host-dependencies.x86_64 > 4.2.0-1.el7.centos @ovirt-4.2 > ovirt-host-deploy.noarch > 1.7.0-1.el7.centos @ovirt-4.2 > ovirt-hosted-engine-ha.noarch > 2.2.2-1.el7.centos @ovirt-4.2 > ovirt-hosted-engine-setup.noarch > 2.2.3-1.el7.centos @ovirt-4.2 > > On Thu, Jan 11, 2018 at 8:16 AM, Martin Sivak <msivak(a)redhat.com> wrote: > >> Hi, >> >> yes, you need to upgrade the hosts. Just take the >> ovirt-hosted-engine-ha and ovirt-hosted-engine-setup packages from >> ovirt 4.2 repositories. >> >> Martin >> >> On Thu, Jan 11, 2018 at 11:40 AM, Jayme <jaymef(a)gmail.com> wrote: >> > How do I upgrade the hosted engine packages when I can't reach it or do >> you >> > mean upgrade the hosts if so how exactly do I do that. As for the >> missing VM >> > it appears that the disk image is there but it's missing XML file I >> have no >> > idea why or how to recreate it. >> > >> > On Jan 11, 2018 4:43 AM, "Martin Sivak" <msivak(a)redhat.com> wrote: >> >> >> >> Hi, >> >> >> >> you hit one known issue we already have fixes for (4.1 hosts with 4.2 >> >> engine): >> >> https://gerrit.ovirt.org/#/q/status:open+project:ovirt-hoste >> d-engine-ha+branch:v2.1.z+topic:ovf_42_for_41 >> >> >> >> You can try hotfixing it by upgrading hosted engine packages to 4.2 or >> >> applying the patches manually and installing python-lxml. >> >> >> >> I am not sure what happened to your other VM. >> >> >> >> Best regards >> >> >> >> Martin Sivak >> >> >> >> On Thu, Jan 11, 2018 at 6:15 AM, Jayme <jaymef(a)gmail.com> wrote: >> >> > I performed Ovirt 4.2 upgrade on a 3 host cluster with NFS shared >> >> > storage. >> >> > The shared storage is mounted from one of the hosts. >> >> > >> >> > I upgraded the hosted engine first, downloading the 4.2 rpm, doing a >> yum >> >> > update then engine setup which seemed to complete successfully, at >> the >> >> > end >> >> > it powered down the hosted VM but it never came back up. I was >> unable >> >> > to >> >> > start it. >> >> > >> >> > I proceeded to upgrade the three hosts, ovirt 4.2 rpm and a full yum >> >> > update. >> >> > I also rebooted each of the three hosts. >> >> > >> >> > After some time the hosts did come back and almost all of the VMs are >> >> > running again and seem to be working ok with the exception of two: >> >> > >> >> > 1. The hosted VM still will not start, I've tried everything I can >> think >> >> > of. >> >> > >> >> > 2. A VM that I know existed is not running and does not appear to >> exist, >> >> > I >> >> > have no idea where it is or how to start it. >> >> > >> >> > 1. Hosted engine >> >> > >> >> > From one of the hosts I get a weird error trying to start it: >> >> > >> >> > # hosted-engine --vm-start >> >> > Command VM.getStats with args {'vmID': >> >> > '4013c829-c9d7-4b72-90d5-6fe58137504c'} failed: >> >> > (code=1, message=Virtual machine does not exist: {'vmId': >> >> > u'4013c829-c9d7-4b72-90d5-6fe58137504c'}) >> >> > >> >> > From the two other hosts I do not get the same error as above, >> sometimes >> >> > it >> >> > appears to start but --vm-status shows errors such as: Engine status >> >> > : {"reason": "failed liveliness check", "health": "bad", "vm": "up", >> >> > "detail": "Up"} >> >> > >> >> > Seeing these errors in syslog: >> >> > >> >> > Jan 11 01:06:30 host0 libvirtd: 2018-01-11 05:06:30.473+0000: 1910: >> >> > error : >> >> > qemuOpenFileAs:3183 : Failed to open file >> >> > >> >> > '/var/run/vdsm/storage/248f46f0-d793-4581-9810-c9d965e2f286/ >> c2dde892-f978-4dfc-a421-c8e04cf387f9/23aa0a66-fa6c- >> 4967-a1e5-fbe47c0cd705': >> >> > No such file or directory >> >> > >> >> > Jan 11 01:06:30 host0 libvirtd: 2018-01-11 05:06:30.473+0000: 1910: >> >> > error : >> >> > qemuDomainStorageOpenStat:11492 : cannot stat file >> >> > >> >> > '/var/run/vdsm/storage/248f46f0-d793-4581-9810-c9d965e2f286/ >> c2dde892-f978-4dfc-a421-c8e04cf387f9/23aa0a66-fa6c- >> 4967-a1e5-fbe47c0cd705': >> >> > Bad file descriptor >> >> > >> >> > 2. Missing VM. virsh -r list on each host does not show the VM at >> all. >> >> > I >> >> > know it existed and is important. The log on one of the hosts even >> >> > shows >> >> > that it started it recently then stopped in 10 or so minutes later: >> >> > >> >> > Jan 10 18:47:17 host3 systemd-machined: New machine qemu-9-Berna. >> >> > Jan 10 18:47:17 host3 systemd: Started Virtual Machine qemu-9-Berna. >> >> > Jan 10 18:47:17 host3 systemd: Starting Virtual Machine qemu-9-Berna. >> >> > Jan 10 18:54:45 host3 systemd-machined: Machine qemu-9-Berna >> terminated. >> >> > >> >> > How can I find out the status of the "Berna" VM and get it running >> >> > again? >> >> > >> >> > Thanks so much! >> >> > >> >> > _______________________________________________ >> >> > Users mailing list >> >> > Users(a)ovirt.org >> >> > http://lists.ovirt.org/mailman/listinfo/users >> >> > >> > >

2 1

snapshotting
by Erekle Magradze 11 Jan '18

11 Jan '18

Hello, Could you please share your experience with snapshotting the VMs in oVirt 4.1 with GlusterFS as a storage? Thanks in advance Erekle

1 0