[ovirt-users] Re: New host: no network interfaces visible

2020-10-22 Thread Richard Chan
Hi Ales, the problem was resolved by starting NetworkManager.

Previously our workflow had always been to disable firewalld, and
NetworkManager.

Is it the case that newer ovirt 4.3.x uses NetworkManager to enumerate
physical devices?

What resolved the situation: create a single ethernet NIC (no ovirtmgmt
bridge) for the management VLAN with NetworkManager
running - connect to engine -  suddenly all the physical NICs were visible
in oVirt and it took over. It created the ovirtmgmt bridge consuming the
original NIC card, and I could proceed with the rest of the networks. It
also moved all the network devices to the NM_CONTROLLED=no state.

What was most unexpected in 4.3.10 (w/ a fresh host) was that
NetworkManager was needed to "bootstrap" the host.

Regards
Richard Chan





On Mon, Oct 19, 2020 at 1:57 PM Ales Musil  wrote:

>
>
> On Thu, Oct 15, 2020 at 2:39 PM Richard Chan 
> wrote:
>
>> What could cause no Network Interfaces visible in installing a new host?
>>
>> I have added a new host to oVirt 4.3.10, the initial SSH installs all the
>> packages (all with failed=0 in host-deploy/*log). The installation is shown
>> as failed without any meaningful message.
>>
>> However the Network Interfaces page is blank, what could cause this?
>>
>> Host in CentOS 7.8 tried with/without biosdevname.
>>
>>
>> --
>> Richard Chan
>>
>> ___
>> 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/UWXJCPL6CNNQN37RY4DUGVGDBOTDK23B/
>>
>
>
> Hello Richard,
>
> can you please share relevant logs from the host deploy?
> It should be located on the engine machine
> /var/log/ovirt-engine/host-deploy/.
>
> Thanks.
>
> Regards,
> Ales Musil
>
> --
>
> Ales Musil
>
> Software Engineer - RHV Network
>
> Red Hat EMEA <https://www.redhat.com>
>
> amu...@redhat.comIM: amusil
> <https://red.ht/sig>
>


-- 
Richard Chan
Chief Architect

TreeBox Solutions Pte Ltd
1 Commonwealth Lane #03-01
Singapore 149544
Tel: 6570 3725
http://www.treeboxsolutions.com

Co.Reg.No. 201100585R
___
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/GYEP5AU7WFER3OFWBKXCXLTYNXOI2HVW/


[ovirt-users] New host: no network interfaces visible

2020-10-15 Thread Richard Chan
What could cause no Network Interfaces visible in installing a new host?

I have added a new host to oVirt 4.3.10, the initial SSH installs all the
packages (all with failed=0 in host-deploy/*log). The installation is shown
as failed without any meaningful message.

However the Network Interfaces page is blank, what could cause this?

Host in CentOS 7.8 tried with/without biosdevname.


-- 
Richard Chan
___
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/UWXJCPL6CNNQN37RY4DUGVGDBOTDK23B/


[ovirt-users] Re: 4.2.8: NPE starting a specific VM

2019-07-07 Thread Richard Chan
There was a NIC that was Up + Unplugged. I have removed all NICs and
recreated them. The NPE remains.

On Sat, Jul 6, 2019 at 10:00 PM Arik Hadas  wrote:

> On Fri, Jul 5, 2019 at 7:44 PM Richard Chan 
> wrote:
>
>> This VM and interface cause NPE
>>
>>  id  |   vm_guid
>>| vmt_guid | mac_addr  | name | speed | type |
>> _create_date  | _update_date  | linked |
>> vnic_profile_id
>>
>> --+--+--+---+--+---+--+---+---++--
>>  29c09fc1-1ddf-40e1-8355-1acbdd84f913 |
>> cb5dee7e-5bc6-4eb3-88a9-614a90ebfd71 |  | 00:1a:4a:2f:48:83 | nic1
>> | 1 |3 | 2017-04-26 23:31:58.662743+08 | 2019-07-06
>> 00:35:27.401616+08 | t  | 0f1c7d97-a156-416c-a62a-ed7d5bc3dc0e
>> (1 row)
>>
>> On Fri, Jul 5, 2019 at 7:03 PM Dominik Holler  wrote:
>>
>>> Can you please share the output of
>>> /usr/share/ovirt-engine/dbscripts/engine-psql.sh  -c "select * from
>>> vm_interface"
>>> ? You are welcme to restrict like
>>> /usr/share/ovirt-engine/dbscripts/engine-psql.sh  -c "select * from
>>> vm_interface where vm_guid='xxx' "
>>> if you know the id of the vm.
>>>
>>>
>>> On Fri, Jul 5, 2019 at 9:46 AM Richard Chan <
>>> rich...@treeboxsolutions.com> wrote:
>>>
>>>> Encountering a NPE on 4.2.8. This is the first start after a 4.1 to 4.2
>>>> upgrade.
>>>>
>>>> 2019-07-05 15:36:56,912+08 ERROR
>>>> [org.ovirt.engine.core.vdsbroker.CreateVDSCommand]
>>>> (EE-ManagedThreadFactory-engine-Thread-45700) [64500cdd-b623-4bb1-a7a1-841
>>>> 6b4e6723b] Failed to create VM: java.lang.NullPointerException
>>>> at
>>>> org.ovirt.engine.core.vdsbroker.builder.vminfo.LibvirtVmXmlBuilder.lambda$writeInterfaces$26(LibvirtVmXmlBuilder.java:1198)
>>>> [vdsbroker.jar:]
>>>> at
>>>> java.util.Comparator.lambda$comparing$77a9974f$1(Comparator.java:469)
>>>> [rt.jar:1.8.0_212]
>>>> at java.util.TimSort.countRunAndMakeAscending(TimSort.java:355)
>>>> [rt.jar:1.8.0_212]
>>>> at java.util.TimSort.sort(TimSort.java:220) [rt.jar:1.8.0_212]
>>>> at java.util.Arrays.sort(Arrays.java:1512) [rt.jar:1.8.0_212]
>>>> at
>>>> java.util.stream.SortedOps$SizedRefSortingSink.end(SortedOps.java:348)
>>>> [rt.jar:1.8.0_212]
>>>> at
>>>> java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:483)
>>>> [rt.jar:1.8.0_212]
>>>> at
>>>> java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:472)
>>>> [rt.jar:1.8.0_212]
>>>> at
>>>> java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151)
>>>> [rt.jar:1.8.0_212]
>>>> at
>>>> java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174)
>>>> [rt.jar:1.8.0_212]
>>>> at
>>>> java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
>>>> [rt.jar:1.8.0_212]
>>>> at
>>>> java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:418)
>>>> [rt.jar:1.8.0_212]
>>>> at
>>>> org.ovirt.engine.core.vdsbroker.builder.vminfo.LibvirtVmXmlBuilder.writeInterfaces(LibvirtVmXmlBuilder.java:1199)
>>>> [vdsbroker.jar:]
>>>> at
>>>> org.ovirt.engine.core.vdsbroker.builder.vminfo.LibvirtVmXmlBuilder.writeDevices(LibvirtVmXmlBuilder.java:1045)
>>>> [vdsbroker.jar:]
>>>> at
>>>> org.ovirt.engine.core.vdsbroker.builder.vminfo.LibvirtVmXmlBuilder.buildCreateVm(LibvirtVmXmlBuilder.java:254)
>>>> [vdsbroker.jar:]
>>>> at
>>>> org.ovirt.engine.core.vdsbroker.vdsbroker.CreateBrokerVDSCommand.generateDomainXml(CreateBrokerVDSCommand.java:93)
>>>> [vdsbroker.jar:]
>>>> at
>>>> org.ovirt.engine.core.vdsbroker.vdsbroker.CreateBrokerVDSCommand.createInfo(CreateBrokerVDSCommand.java:50)
>>>> [vdsbroker.jar:]
>>>> at
>>>> org.ovirt.engine.core.vdsbroker.vdsbroker.CreateBrokerVDSCommand.executeVdsBrokerCommand(CreateBrokerVDSCommand.java:42)
>>>> [

[ovirt-users] Experience 4.1.x -> 4.2.8 -> 4.3.4 upgrade lessons

2019-07-05 Thread Richard Chan
Hi oVirters,

Did a 4.1 - > 4.2.8 -> 4.3.4 upgrade in two hops. Here is my experience,
hope it can save you some pain.

Gotchas
1. For shutdown VMs, their disks were deactivated (though still attached)
2. For shutdown VMs, their NICs were "Up" but "Unplugged"
3. VM Custom Compatibility Version is hard to find. (If it is too old say
3.6, 4.1) they won't start up.  The location is:  VM -> Edit -> System ->
Advanced Parameters (click this)

"Advanced Parameters" is an expandable widget that is quite small when
collapsed. When it is expanded then you will see "Custom Compatibility
Version"

4. Storage Domain migration to V5: I use a NFS storoage domain. This is
migrated to the "V5" format and a lot of cleanup is done. If you have stray
files or images not owned by 36:36 (vdsm:kvm on my NFS server), the V5
upgrade will fail, there will be no SPM, and the Data Center will oscillate
between Non-responsive and Contending.

Why would there be non 36:36 uid/gid files? This is a long story, but from
the older 3.x days when there was less functionality, we would sometimes
directly manipulate the filesystem and/or qcow2 images using guestfish or
equivalent tools which would change the owner to qemu:qemu. Forgetting to
chown back to vdsm:kvm is a recipe for pain.

Cheers!

-- 
Richard Chan
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/HSPSXO3JQ5ZMECSB3UMJCNPOSNO5PKRR/


[ovirt-users] Re: 4.2.8: NPE starting a specific VM

2019-07-05 Thread Richard Chan
This VM and interface cause NPE

 id  |   vm_guid
 | vmt_guid | mac_addr  | name | speed | type |
_create_date  | _update_date  | linked |
vnic_profile_id
--+--+--+---+--+---+--+---+---++--
 29c09fc1-1ddf-40e1-8355-1acbdd84f913 |
cb5dee7e-5bc6-4eb3-88a9-614a90ebfd71 |  | 00:1a:4a:2f:48:83 | nic1
| 1 |3 | 2017-04-26 23:31:58.662743+08 | 2019-07-06
00:35:27.401616+08 | t  | 0f1c7d97-a156-416c-a62a-ed7d5bc3dc0e
(1 row)

On Fri, Jul 5, 2019 at 7:03 PM Dominik Holler  wrote:

> Can you please share the output of
> /usr/share/ovirt-engine/dbscripts/engine-psql.sh  -c "select * from
> vm_interface"
> ? You are welcme to restrict like
> /usr/share/ovirt-engine/dbscripts/engine-psql.sh  -c "select * from
> vm_interface where vm_guid='xxx' "
> if you know the id of the vm.
>
>
> On Fri, Jul 5, 2019 at 9:46 AM Richard Chan 
> wrote:
>
>> Encountering a NPE on 4.2.8. This is the first start after a 4.1 to 4.2
>> upgrade.
>>
>> 2019-07-05 15:36:56,912+08 ERROR
>> [org.ovirt.engine.core.vdsbroker.CreateVDSCommand]
>> (EE-ManagedThreadFactory-engine-Thread-45700) [64500cdd-b623-4bb1-a7a1-841
>> 6b4e6723b] Failed to create VM: java.lang.NullPointerException
>> at
>> org.ovirt.engine.core.vdsbroker.builder.vminfo.LibvirtVmXmlBuilder.lambda$writeInterfaces$26(LibvirtVmXmlBuilder.java:1198)
>> [vdsbroker.jar:]
>> at
>> java.util.Comparator.lambda$comparing$77a9974f$1(Comparator.java:469)
>> [rt.jar:1.8.0_212]
>> at java.util.TimSort.countRunAndMakeAscending(TimSort.java:355)
>> [rt.jar:1.8.0_212]
>> at java.util.TimSort.sort(TimSort.java:220) [rt.jar:1.8.0_212]
>> at java.util.Arrays.sort(Arrays.java:1512) [rt.jar:1.8.0_212]
>> at
>> java.util.stream.SortedOps$SizedRefSortingSink.end(SortedOps.java:348)
>> [rt.jar:1.8.0_212]
>> at
>> java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:483)
>> [rt.jar:1.8.0_212]
>> at
>> java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:472)
>> [rt.jar:1.8.0_212]
>> at
>> java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151)
>> [rt.jar:1.8.0_212]
>> at
>> java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174)
>> [rt.jar:1.8.0_212]
>> at
>> java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
>> [rt.jar:1.8.0_212]
>> at
>> java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:418)
>> [rt.jar:1.8.0_212]
>> at
>> org.ovirt.engine.core.vdsbroker.builder.vminfo.LibvirtVmXmlBuilder.writeInterfaces(LibvirtVmXmlBuilder.java:1199)
>> [vdsbroker.jar:]
>> at
>> org.ovirt.engine.core.vdsbroker.builder.vminfo.LibvirtVmXmlBuilder.writeDevices(LibvirtVmXmlBuilder.java:1045)
>> [vdsbroker.jar:]
>> at
>> org.ovirt.engine.core.vdsbroker.builder.vminfo.LibvirtVmXmlBuilder.buildCreateVm(LibvirtVmXmlBuilder.java:254)
>> [vdsbroker.jar:]
>> at
>> org.ovirt.engine.core.vdsbroker.vdsbroker.CreateBrokerVDSCommand.generateDomainXml(CreateBrokerVDSCommand.java:93)
>> [vdsbroker.jar:]
>> at
>> org.ovirt.engine.core.vdsbroker.vdsbroker.CreateBrokerVDSCommand.createInfo(CreateBrokerVDSCommand.java:50)
>> [vdsbroker.jar:]
>> at
>> org.ovirt.engine.core.vdsbroker.vdsbroker.CreateBrokerVDSCommand.executeVdsBrokerCommand(CreateBrokerVDSCommand.java:42)
>> [vdsbroker.jar:]
>> at
>> org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.executeVdsCommandWithNetworkEvent(VdsBrokerCommand.java:123)
>> [vdsbroker.jar:]
>> at
>> org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.executeVDSCommand(VdsBrokerCommand.java:111)
>> [vdsbroker.jar:]
>> at
>> org.ovirt.engine.core.vdsbroker.VDSCommandBase.executeCommand(VDSCommandBase.java:73)
>> [vdsbroker.jar:]
>> at
>> org.ovirt.engine.core.dal.VdcCommandBase.execute(VdcCommandBase.java:33)
>> [dal.jar:]
>>
>> This leads to Failed to run VM message. Any ideas?
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> Thanks
>> Richard Chan
>> ___
>> Users mailing list -- users@ovirt.org
>> To unsubscribe send an email t

[ovirt-users] Re: Upgraded to 4.3: getting SpmStart failure

2019-07-05 Thread Richard Chan
This is in the engine.log

[storage.StoragePool] Trying to upgrade master domain
`f9aaa65a-0ac7-4c61-a27d-15af3901
6419` (sp:479)
2019-07-06 00:24:14,056+0800 INFO  (tasks/5) [storage.StorageDomain]
Converting domain f9aaa65a-0ac7-4c61-a27d-15af39016419 volumes
metadata from version 4 to version 5 (fileSD:811)
2019-07-06 00:24:14,121+0800 INFO  (tasks/5) [storage.StorageDomain]
Removing remnants of deleted images [] (fileSD:740)
2019-07-06 00:24:14,121+0800 ERROR (tasks/5) [storage.StoragePool]
Unexpected error (sp:383)
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/vdsm/storage/sp.py", line 333, in
startSpm

On Fri, Jul 5, 2019 at 11:31 PM Strahil  wrote:

> Can you run the engine manually on another server ?
> hosted-engine --vm-start
>
> Best Regards,
> Strahil Nikolov
> On Jul 5, 2019 18:05, Richard Chan  wrote:
>
> My engine is getting SpmStart failure.
>
> What is the best way to troubleshoot this?
>
>
> --
> Richard Chan
>
>

-- 
Richard Chan
Chief Architect

TreeBox Solutions Pte Ltd
1 Commonwealth Lane #03-01
Singapore 149544
Tel: 6570 3725
http://www.treeboxsolutions.com

Co.Reg.No. 201100585R
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/GW7HOCWLI2OVGC2OR7A6AAAYCBXGOPLT/


[ovirt-users] Re: Upgraded to 4.3: getting SpmStart failure

2019-07-05 Thread Richard Chan
Unfortunately, this is a separate engine running external to the oVirt
cluster.
The main error on the hosts is: any idea what this Volume is referring to?
I have 3 existings storage domains
ISO EXPORT and DATA all upgraded to 4.3
None have this UUID.


VolumeDoesNotExist: Volume does not exist:
(u'1d1b6dfd-197a-4583-8398-6b941dbca854',)

2019-07-05 23:02:15,954+0800 ERROR (tasks/0) [storage.StoragePool] failed:
Volume does not exist: (u'1d1b6dfd-197a-4583-8398-6b941dbca854',) (sp:384)
2019-07-05 23:02:15,954+0800 INFO  (tasks/0) [storage.SANLock] Releasing
Lease(name='SDM',
path=u'/rhev/data-center/mnt/192.168.88.40:_genie_ovirt_data/f9aaa65a-0ac7-4c61-a27d-15af39016419/dom_md/leases',
offset=1048576) (clusterlock:488)
2019-07-05 23:02:15,955+0800 INFO  (tasks/0) [storage.SANLock] Successfully
released Lease(name='SDM',
path=u'/rhev/data-center/mnt/192.168.88.40:_genie_ovirt_data/f9aaa65a-0ac7-4c61-a27d-15af39016419/dom_md/leases',
offset=1048576) (clusterlock:497)
2019-07-05 23:02:15,955+0800 ERROR (tasks/0) [storage.TaskManager.Task]
(Task='159b9026-7034-43c2-9587-8fec036e92ba') Unexpected error (task:875)
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 882,
in _run
return fn(*args, **kargs)
  File "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 336,
in run
return self.cmd(*self.argslist, **self.argsdict)
  File "/usr/lib/python2.7/site-packages/vdsm/storage/sp.py", line 333, in
startSpm
self._upgradePool(expectedDomVersion, __securityOverride=True)
  File "/usr/lib/python2.7/site-packages/vdsm/storage/securable.py", line
79, in wrapper
return method(self, *args, **kwargs)
  File "/usr/lib/python2.7/site-packages/vdsm/storage/sp.py", line 484, in
_upgradePool
str(targetDomVersion))
  File "/usr/lib/python2.7/site-packages/vdsm/storage/sp.py", line 1108, in
_convertDomain
targetFormat)
  File "/usr/lib/python2.7/site-packages/vdsm/storage/formatconverter.py",
line 447, in convert
converter(repoPath, hostId, imageRepo, isMsd)
  File "/usr/lib/python2.7/site-packages/vdsm/storage/formatconverter.py",
line 405, in v5DomainConverter
domain.convert_volumes_metadata(target_version)
  File "/usr/lib/python2.7/site-packages/vdsm/storage/fileSD.py", line 813,
in convert_volumes_metadata
for vol in self.iter_volumes():
  File "/usr/lib/python2.7/site-packages/vdsm/storage/sd.py", line 764, in
iter_volumes
yield self.produceVolume(img_id, vol_id)
  File "/usr/lib/python2.7/site-packages/vdsm/storage/sd.py", line 846, in
produceVolume
volUUID)
  File "/usr/lib/python2.7/site-packages/vdsm/storage/volume.py", line 817,
in __init__
self._manifest = self.manifestClass(repoPath, sdUUID, imgUUID, volUUID)
  File "/usr/lib/python2.7/site-packages/vdsm/storage/fileVolume.py", line
71, in __init__
volUUID)
  File "/usr/lib/python2.7/site-packages/vdsm/storage/volume.py", line 86,
in __init__
self.validate()
  File "/usr/lib/python2.7/site-packages/vdsm/storage/volume.py", line 112,
in validate
self.validateVolumePath()
  File "/usr/lib/python2.7/site-packages/vdsm/storage/fileVolume.py", line
131, in validateVolumePath
raise se.VolumeDoesNotExist(self.volUUID)

On Fri, Jul 5, 2019 at 11:31 PM Strahil  wrote:

> Can you run the engine manually on another server ?
> hosted-engine --vm-start
>
> Best Regards,
> Strahil Nikolov
> On Jul 5, 2019 18:05, Richard Chan  wrote:
>
> My engine is getting SpmStart failure.
>
> What is the best way to troubleshoot this?
>
>
> --
> Richard Chan
>
>

-- 
Richard Chan
Chief Architect

TreeBox Solutions Pte Ltd
1 Commonwealth Lane #03-01
Singapore 149544
Tel: 6570 3725
http://www.treeboxsolutions.com

Co.Reg.No. 201100585R
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/3A5Y2JMNHBTPWET4LOFTONYPEGORLGZK/


[ovirt-users] Upgraded to 4.3: getting SpmStart failure

2019-07-05 Thread Richard Chan
My engine is getting SpmStart failure.

What is the best way to troubleshoot this?


-- 
Richard Chan
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/7B5NVNYOTFAEIIWUTOQWJ7NL56J6DAIR/


[ovirt-users] Re: 4.3 won't upgrade engine in standalone KVM VM: low_custom_compatibility_version 'agent03'

2019-07-05 Thread Richard Chan
Ah - it found a oVirt VM called agent03 - that has nothing to do with the
engine VM.

I think I confused myself, and thought engine-setup did not like the engine
VM.
Actually it was complaining about an existing oVirt VM...Hmmm - this VM was
indeed set to 3.6.

Thank you!!

On Fri, Jul 5, 2019 at 9:22 PM Simone Tiraboschi 
wrote:

>
>
> On Fri, Jul 5, 2019 at 3:15 PM Simone Tiraboschi 
> wrote:
>
>>
>>
>> On Fri, Jul 5, 2019 at 3:06 PM Richard Chan 
>> wrote:
>>
>>> In libvirt/virsh  the VM is called "ovirt7"; here is the domain
>>> definition. This VM has been upgraded from
>>> 3.6->4.0->4.1->4.2. This is the first time engine-setup has complained
>>> about the "level" of the VM.
>>>
>>> libvirt domain definition:
>>>
>>
>> oVirt VMs contains something like:
>>
>>   http://ovirt.org/vm/tune/1.0; xmlns:ovirt-vm="
>> http://ovirt.org/vm/1.0;>
>> 
>> http://ovirt.org/vm/1.0;>
>> 4.2
>>
>> in the XML for libvirt so you are checking the wrong VM.
>>
>
> Please try executing this on your engine VM:
>
> sudo -u postgres scl enable rh-postgresql95 -- psql -d engine -c "select *
> from vms where vm_name='agent03'"
>
>
>>
>>
>>>
>>> 
>>>   ovirt7
>>>   cdb0f3fd-42c7-4a16-bcd1-5d65f19aca19
>>>   8388608
>>>   8388608
>>>   2
>>>   
>>> /machine
>>>   
>>>   
>>> hvm
>>> >> type='pflash'>/usr/share/edk2.git/ovmf-x64/OVMF_CODE-pure-efi.fd
>>> /var/lib/libvirt/qemu/nvram/ovirt7_VARS.fd
>>> 
>>>   
>>>   
>>> 
>>> 
>>> 
>>>   
>>>   
>>> Haswell-noTSX
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>>   
>>>   
>>> 
>>> 
>>> 
>>>   
>>>   destroy
>>>   restart
>>>   destroy
>>>   
>>> 
>>> 
>>>   
>>>   
>>> /usr/libexec/qemu-kvm
>>> 
>>>   
>>>   
>>>   
>>> 
>>> 
>>> 
>>>   
>>>   
>>>   
>>>   
>>> 
>>> 
>>>   
>>>   
>>>   
>>> 
>>> >> file='/var/lib/libvirt/images/ovirt7/database_01.WAEqcow2'/>
>>> 
>>>   
>>>   
>>>   
>>>   
>>> 
>>> 
>>>   
>>>   >> function='0x7'/>
>>> 
>>> 
>>>   
>>>   
>>>   >> function='0x0' multifunction='on'/>
>>> 
>>> 
>>>   
>>>   
>>>   >> function='0x1'/>
>>> 
>>> 
>>>   
>>>   
>>>   >> function='0x2'/>
>>> 
>>> 
>>>   
>>>   >> function='0x0'/>
>>> 
>>> 
>>>   
>>> 
>>> 
>>>   
>>>   >> function='0x0'/>
>>> 
>>> 
>>>   
>>>   
>>>   
>>>   
>>>   
>>>   >> function='0x0'/>
>>> 
>>> 
>>>   
>>>   
>>>   
>>> 
>>> 
>>>   
>>>   
>>>   
>>> 
>>> 
>>>   >> path='/var/lib/libvirt/qemu/channel/target/domain-15-ovirt7/org.qemu.guest_agent.0'/>
>>>   >> state='connected'/>
>>>   
>>>   
>>> 
>>> 
>>>   >> state='disconnected'/>
>>>   
>>>   
>>> 
>>> 
>>>   
>>>   
>>> 
>>> 
>>>   
>>> 
>>> 
>>>   
>>> 
>>> 
>>>   
>>> 
>>> 
>>>   
>>>   >> function='0x0'/>
>>> 
>>> 
>>>   >> heads='1' primary='yes'/>
>>>   
>>>   >> function='0x0'/>
>>> 
>>> 
>

[ovirt-users] Re: 4.3 won't upgrade engine in standalone KVM VM: low_custom_compatibility_version 'agent03'

2019-07-05 Thread Richard Chan
This engine VM running as part of the oVirt cluster (not hosted engine/not
running under oVirt).

It is running on a separate libvirt/KVM server. This hypervisor is totally
separate and standalone: it is not a oVirt host.

This VM has been controlling the oVirt hosts since 3.6 days.

Inside this VM I have installed ovirt-release43.rpm and now running
engine-setup.

On Fri, Jul 5, 2019 at 9:15 PM Simone Tiraboschi 
wrote:

>
>
> On Fri, Jul 5, 2019 at 3:06 PM Richard Chan 
> wrote:
>
>> In libvirt/virsh  the VM is called "ovirt7"; here is the domain
>> definition. This VM has been upgraded from
>> 3.6->4.0->4.1->4.2. This is the first time engine-setup has complained
>> about the "level" of the VM.
>>
>> libvirt domain definition:
>>
>
> oVirt VMs contains something like:
>
>   http://ovirt.org/vm/tune/1.0; xmlns:ovirt-vm="
> http://ovirt.org/vm/1.0;>
> 
> http://ovirt.org/vm/1.0;>
> 4.2
>
> in the XML for libvirt so you are checking the wrong VM.
>
>
>>
>> 
>>   ovirt7
>>   cdb0f3fd-42c7-4a16-bcd1-5d65f19aca19
>>   8388608
>>   8388608
>>   2
>>   
>> /machine
>>   
>>   
>> hvm
>> > type='pflash'>/usr/share/edk2.git/ovmf-x64/OVMF_CODE-pure-efi.fd
>> /var/lib/libvirt/qemu/nvram/ovirt7_VARS.fd
>> 
>>   
>>   
>> 
>> 
>> 
>>   
>>   
>> Haswell-noTSX
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>>   
>>   
>> 
>> 
>> 
>>   
>>   destroy
>>   restart
>>   destroy
>>   
>> 
>> 
>>   
>>   
>> /usr/libexec/qemu-kvm
>> 
>>   
>>   
>>   
>> 
>> 
>> 
>>   
>>   
>>   
>>   
>> 
>> 
>>   
>>   
>>   
>> 
>> > file='/var/lib/libvirt/images/ovirt7/database_01.WAEqcow2'/>
>> 
>>   
>>   
>>   
>>   
>> 
>> 
>>   
>>   > function='0x7'/>
>> 
>> 
>>   
>>   
>>   > function='0x0' multifunction='on'/>
>> 
>> 
>>   
>>   
>>   > function='0x1'/>
>> 
>> 
>>   
>>   
>>   > function='0x2'/>
>> 
>> 
>>   
>>   > function='0x0'/>
>> 
>> 
>>   
>> 
>> 
>>   
>>   > function='0x0'/>
>> 
>> 
>>   
>>   
>>   
>>   
>>   
>>   > function='0x0'/>
>> 
>> 
>>   
>>   
>>   
>> 
>> 
>>   
>>   
>>   
>> 
>>     
>>   > path='/var/lib/libvirt/qemu/channel/target/domain-15-ovirt7/org.qemu.guest_agent.0'/>
>>   > state='connected'/>
>>   
>>   
>> 
>> 
>>   > state='disconnected'/>
>>   
>>   
>> 
>> 
>>   
>>   
>> 
>> 
>>   
>> 
>> 
>>   
>> 
>> 
>>   
>> 
>> 
>>   
>>   > function='0x0'/>
>> 
>> 
>>   > primary='yes'/>
>>   
>>   > function='0x0'/>
>> 
>> 
>>   
>>   
>> 
>> 
>>   
>>   
>> 
>> 
>>   
>>   > function='0x0'/>
>> 
>>   
>>   
>> system_u:system_r:svirt_t:s0:c194,c775
>> system_u:object_r:svirt_image_t:s0:c194,c775
>>   
>>   
>> +107:+107
>> +107:+107
>>   
>> 
>>
>> On Fri, Jul 5, 2019 at 8:53 PM Simone Tiraboschi 
>> wrote:
>>
>>>
>>>
>>> On Fri, Jul 5, 2019 at 2:48 PM Richard Chan <
>>> rich...@treeboxsolutions.com> wrote:
>>>
>>>> Hi,
>>>>
>>>>  I am running 4.2 engine in a standalone libvirt KVM VM (running on a
>>>> hypervisor that is not part of the oVirt infrastructure); i.e., I am not
>>>> using hosted engine but still running engine in a VM.
>>>>

[ovirt-users] Re: 4.3 won't upgrade engine in standalone KVM VM: low_custom_compatibility_version 'agent03'

2019-07-05 Thread Richard Chan
In libvirt/virsh  the VM is called "ovirt7"; here is the domain definition.
This VM has been upgraded from
3.6->4.0->4.1->4.2. This is the first time engine-setup has complained
about the "level" of the VM.

libvirt domain definition:


  ovirt7
  cdb0f3fd-42c7-4a16-bcd1-5d65f19aca19
  8388608
  8388608
  2
  
/machine
  
  
hvm
/usr/share/edk2.git/ovmf-x64/OVMF_CODE-pure-efi.fd
/var/lib/libvirt/qemu/nvram/ovirt7_VARS.fd

  
  



  
  
Haswell-noTSX







  
  



  
  destroy
  restart
  destroy
  


  
  
/usr/libexec/qemu-kvm

  
  
  



  
  
  
  


  
  
  



  
  
  
  


  
  


  
  
  


  
  
  


  
  
  


  
  


  


  
  


  
  
  
  
  
  


  
  
  


  
  
  


  
  
  
  


  
  
  


  
  


  


  


  


  
  


  
  
  


  
  


  
  


  
  

  
  
system_u:system_r:svirt_t:s0:c194,c775
system_u:object_r:svirt_image_t:s0:c194,c775
  
  
+107:+107
+107:+107
  


On Fri, Jul 5, 2019 at 8:53 PM Simone Tiraboschi 
wrote:

>
>
> On Fri, Jul 5, 2019 at 2:48 PM Richard Chan 
> wrote:
>
>> Hi,
>>
>>  I am running 4.2 engine in a standalone libvirt KVM VM (running on a
>> hypervisor that is not part of the oVirt infrastructure); i.e., I am not
>> using hosted engine but still running engine in a VM.
>>
>> Now 4.3 won't upgrade inside this libvirt KVM VM:
>>
>> Failed to execute stage 'Setup validation': Cannot upgrade the Engine due
>> to low custom_compatibility_version for virtual
>>  machines: ['agent03']. Please edit this virtual machines, in edit VM
>> dialog go to System->Advanced Parameters -> Custom Compatibility Version
>> and either reset to empty (cluster default) or set a value supported by the
>> new installation: 4.1, 4.2, 4.3.
>>
>> engine-setup has probably detected that it is running inside a VM:
>> 1. Where did it get 'agent03' string from
>> 2. Any suggestions how to fool engine-setup to think this is 4.3
>>
>
> The engine is not going to check anything on hosts that are unknown at
> engine eyes.
> I think that you simply have in the engine a VM called 'agent03'.
> Please check it.
>
>
>>
>> Here is the dmidecode of the standalone engine VM:
>>
>> # dmidecode 3.1
>> Getting SMBIOS data from sysfs.
>> SMBIOS 2.8 present.
>> 11 structures occupying 591 bytes.
>> Table at 0xBFED7000.
>>
>> Handle 0x0100, DMI type 1, 27 bytes
>> System Information
>> Manufacturer: Red Hat
>> Product Name: KVM
>> Version: RHEL 7.3.0 PC (i440FX + PIIX, 1996)
>> Serial Number: Not Specified
>> UUID: cdb0f3fd-42c7-4a16-bcd1-5d65f19aca19
>> Wake-up Type: Power Switch
>> SKU Number: Not Specified
>> Family: Red Hat Enterprise Linux
>>
>> Handle 0x0300, DMI type 3, 21 bytes
>> Chassis Information
>> Manufacturer: Red Hat
>> Type: Other
>> Lock: Not Present
>> Version: RHEL 7.3.0 PC (i440FX + PIIX, 1996)
>> Serial Number: Not Specified
>> Asset Tag: Not Specified
>> Boot-up State: Safe
>> Power Supply State: Safe
>> Thermal State: Safe
>> Security Status: Unknown
>> OEM Information: 0x
>> Height: Unspecified
>> Number Of Power Cords: Unspecified
>> Contained Elements: 0
>>
>> Handle 0x0400, DMI type 4, 42 bytes
>> Processor Information
>> Socket Designation: CPU 0
>> Type: Central Processor
>> Family: Other
>> Manufacturer: Red Hat
>> ID: C1 06 03 00 FF FB 8B 07
>> Version: RHEL 7.3.0 PC (i440FX + PIIX, 1996)
>> Voltage: Unknown
>> External Clock: Unknown
>> Max Speed: 2000 MHz
>> Current Speed: 2000 MHz
>> Status: Populated, Enabled
>> Upgrade: Other
>> L1 Cache Handle: Not Provided
>> L2 Cache Handle: Not Provided
>> L3 Cache Handle: Not Provided
>> Serial Number: Not Specified
>> Asset Tag: Not Specified
>> Part Number: Not Specified
>> Core Count: 1
>> Core Enabled: 1
>> Thread Count: 1
>> Characteristics: None
>>
>> Handle 0x0401, DMI type 4, 42 bytes
>> Processor Information
>> Socket Designation: CPU 1
>> Type: Central 

[ovirt-users] 4.3 won't upgrade engine in standalone KVM VM: low_custom_compatibility_version 'agent03'

2019-07-05 Thread Richard Chan
Hi,

 I am running 4.2 engine in a standalone libvirt KVM VM (running on a
hypervisor that is not part of the oVirt infrastructure); i.e., I am not
using hosted engine but still running engine in a VM.

Now 4.3 won't upgrade inside this libvirt KVM VM:

Failed to execute stage 'Setup validation': Cannot upgrade the Engine due
to low custom_compatibility_version for virtual
 machines: ['agent03']. Please edit this virtual machines, in edit VM
dialog go to System->Advanced Parameters -> Custom Compatibility Version
and either reset to empty (cluster default) or set a value supported by the
new installation: 4.1, 4.2, 4.3.

engine-setup has probably detected that it is running inside a VM:
1. Where did it get 'agent03' string from
2. Any suggestions how to fool engine-setup to think this is 4.3

Here is the dmidecode of the standalone engine VM:

# dmidecode 3.1
Getting SMBIOS data from sysfs.
SMBIOS 2.8 present.
11 structures occupying 591 bytes.
Table at 0xBFED7000.

Handle 0x0100, DMI type 1, 27 bytes
System Information
Manufacturer: Red Hat
Product Name: KVM
Version: RHEL 7.3.0 PC (i440FX + PIIX, 1996)
Serial Number: Not Specified
UUID: cdb0f3fd-42c7-4a16-bcd1-5d65f19aca19
Wake-up Type: Power Switch
SKU Number: Not Specified
Family: Red Hat Enterprise Linux

Handle 0x0300, DMI type 3, 21 bytes
Chassis Information
Manufacturer: Red Hat
Type: Other
Lock: Not Present
Version: RHEL 7.3.0 PC (i440FX + PIIX, 1996)
Serial Number: Not Specified
Asset Tag: Not Specified
Boot-up State: Safe
Power Supply State: Safe
Thermal State: Safe
Security Status: Unknown
OEM Information: 0x
Height: Unspecified
Number Of Power Cords: Unspecified
Contained Elements: 0

Handle 0x0400, DMI type 4, 42 bytes
Processor Information
Socket Designation: CPU 0
Type: Central Processor
Family: Other
Manufacturer: Red Hat
ID: C1 06 03 00 FF FB 8B 07
Version: RHEL 7.3.0 PC (i440FX + PIIX, 1996)
Voltage: Unknown
External Clock: Unknown
Max Speed: 2000 MHz
Current Speed: 2000 MHz
Status: Populated, Enabled
Upgrade: Other
L1 Cache Handle: Not Provided
L2 Cache Handle: Not Provided
L3 Cache Handle: Not Provided
Serial Number: Not Specified
Asset Tag: Not Specified
Part Number: Not Specified
Core Count: 1
Core Enabled: 1
Thread Count: 1
Characteristics: None

Handle 0x0401, DMI type 4, 42 bytes
Processor Information
Socket Designation: CPU 1
Type: Central Processor
Family: Other
Manufacturer: Red Hat
ID: C1 06 03 00 FF FB 8B 07
Version: RHEL 7.3.0 PC (i440FX + PIIX, 1996)
Voltage: Unknown
External Clock: Unknown
Max Speed: 2000 MHz
Current Speed: 2000 MHz
Status: Populated, Enabled
Upgrade: Other
L1 Cache Handle: Not Provided
L2 Cache Handle: Not Provided
L3 Cache Handle: Not Provided
Serial Number: Not Specified
Asset Tag: Not Specified
Part Number: Not Specified
Core Count: 1
Core Enabled: 1
Thread Count: 1
Characteristics: None

Handle 0x1000, DMI type 16, 23 bytes
Physical Memory Array
Location: Other
Use: System Memory
Error Correction Type: Multi-bit ECC
Maximum Capacity: 8 GB
Error Information Handle: Not Provided
Number Of Devices: 1

Handle 0x1100, DMI type 17, 40 bytes
Memory Device
Array Handle: 0x1000
Error Information Handle: Not Provided
Total Width: Unknown
Data Width: Unknown
Size: 8192 MB
Form Factor: DIMM
Set: None
Locator: DIMM 0
Bank Locator: Not Specified
Type: RAM
Type Detail: Other
Speed: Unknown
Manufacturer: Red Hat
Serial Number: Not Specified
Asset Tag: Not Specified
Part Number: Not Specified
Rank: Unknown
Configured Clock Speed: Unknown
Minimum Voltage: Unknown
Maximum Voltage: Unknown
Configured Voltage: Unknown

Handle 0x1300, DMI type 19, 31 bytes
Memory Array Mapped Address
Starting Address: 0x000
Ending Address: 0x000BFFF
Range Size: 3 GB
Physical Array Handle: 0x1000
Partition Width: 1

Handle 0x1301, DMI type 19, 31 bytes
Memory Array Mapped Address
Starting Address: 0x001
Ending Address: 0x0023FFF
Range Size: 5 GB
Physical Array Handle: 0x1000
Partition Width: 1

Handle 0x2000, DMI type 32, 11 bytes
System Boot Information
Status: No errors detected

Handle 0x, DMI type 0, 24 bytes
BIOS Information
Vendor: EFI Development Kit II / OVMF
Version: 0.0.0
Release Date: 02/06/2015
Address: 0xE8000
Runtime Size: 96 kB
ROM Size: 64 kB
Characteristics:
BIOS characteristics not supported
Targeted content distribution is supported
UEFI is supported
System is a virtual machine
BIOS Revision: 0.0

Handle 0xFEFF, DMI type 127, 4 bytes
End Of Table

Cheers

-- 
Richard Chan
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/VW6LVDLBNMZBXO5AW5CYG2BHACZSMPLR/


[ovirt-users] 4.2.8: NPE starting a specific VM

2019-07-05 Thread Richard Chan
Encountering a NPE on 4.2.8. This is the first start after a 4.1 to 4.2
upgrade.

2019-07-05 15:36:56,912+08 ERROR
[org.ovirt.engine.core.vdsbroker.CreateVDSCommand]
(EE-ManagedThreadFactory-engine-Thread-45700) [64500cdd-b623-4bb1-a7a1-841
6b4e6723b] Failed to create VM: java.lang.NullPointerException
at
org.ovirt.engine.core.vdsbroker.builder.vminfo.LibvirtVmXmlBuilder.lambda$writeInterfaces$26(LibvirtVmXmlBuilder.java:1198)
[vdsbroker.jar:]
at
java.util.Comparator.lambda$comparing$77a9974f$1(Comparator.java:469)
[rt.jar:1.8.0_212]
at java.util.TimSort.countRunAndMakeAscending(TimSort.java:355)
[rt.jar:1.8.0_212]
at java.util.TimSort.sort(TimSort.java:220) [rt.jar:1.8.0_212]
at java.util.Arrays.sort(Arrays.java:1512) [rt.jar:1.8.0_212]
at
java.util.stream.SortedOps$SizedRefSortingSink.end(SortedOps.java:348)
[rt.jar:1.8.0_212]
at
java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:483)
[rt.jar:1.8.0_212]
at
java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:472)
[rt.jar:1.8.0_212]
at
java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151)
[rt.jar:1.8.0_212]
at
java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174)
[rt.jar:1.8.0_212]
at
java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
[rt.jar:1.8.0_212]
at
java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:418)
[rt.jar:1.8.0_212]
at
org.ovirt.engine.core.vdsbroker.builder.vminfo.LibvirtVmXmlBuilder.writeInterfaces(LibvirtVmXmlBuilder.java:1199)
[vdsbroker.jar:]
at
org.ovirt.engine.core.vdsbroker.builder.vminfo.LibvirtVmXmlBuilder.writeDevices(LibvirtVmXmlBuilder.java:1045)
[vdsbroker.jar:]
at
org.ovirt.engine.core.vdsbroker.builder.vminfo.LibvirtVmXmlBuilder.buildCreateVm(LibvirtVmXmlBuilder.java:254)
[vdsbroker.jar:]
at
org.ovirt.engine.core.vdsbroker.vdsbroker.CreateBrokerVDSCommand.generateDomainXml(CreateBrokerVDSCommand.java:93)
[vdsbroker.jar:]
at
org.ovirt.engine.core.vdsbroker.vdsbroker.CreateBrokerVDSCommand.createInfo(CreateBrokerVDSCommand.java:50)
[vdsbroker.jar:]
at
org.ovirt.engine.core.vdsbroker.vdsbroker.CreateBrokerVDSCommand.executeVdsBrokerCommand(CreateBrokerVDSCommand.java:42)
[vdsbroker.jar:]
at
org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.executeVdsCommandWithNetworkEvent(VdsBrokerCommand.java:123)
[vdsbroker.jar:]
at
org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.executeVDSCommand(VdsBrokerCommand.java:111)
[vdsbroker.jar:]
at
org.ovirt.engine.core.vdsbroker.VDSCommandBase.executeCommand(VDSCommandBase.java:73)
[vdsbroker.jar:]
at
org.ovirt.engine.core.dal.VdcCommandBase.execute(VdcCommandBase.java:33)
[dal.jar:]

This leads to Failed to run VM message. Any ideas?









Thanks
Richard Chan
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/ICCUANEM2C3FUJFGJYXT22XB6O54JBWN/


[ovirt-users] Best practice for iSCSI storage domains

2017-12-06 Thread Richard Chan
What is the best practice for iSCSI storage domains:

Many small targets vs a few large targets?

Specific example: if you wanted a 8TB storage domain would you prepare a
single 8TB LUN or (for example) 8 x 1 TB LUNs.



-- 
Richard Chan
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] q35 + virtio-scsi: contention for sda between cdrom and disk

2017-08-10 Thread Richard Chan
q35 + virtio-scsi VM won't start because both cdrom and harddisk are mapped
to sda

I have created a q35 VM using virt-shell:

add vm  --template-id  ---- --cluster-id
16dc2c02-7d14-40a9-b170-cfdfdf63565b  --name TESTVM --virtio_scsi-enabled 1
--os-type rhel_7x64 --custom_emulated_machine pc-q35-rhel7.3.0

When I try to start the VM vdsm shows:













ea86ae1b-893a-47ac-bde8-8c54b4c30e80



As a result the VM won't start. If the disk is virtio (vda) it works.
Anyway to remove the cdrom device from the VM definition?



-- 
Richard Chan
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] How to create q35 + OVMF VM from 4.1 UI?

2017-08-10 Thread Richard Chan
I must be missing something obvious in the web UI, but I can't see where to
create a VM with type q35 + OVMF? In virt-manager it is under
Overview->Firrmware and Overview->Chipset. What is the equivalent in oVirt?



OT: I understand that RHEL 7.4 is having issues with OVMF VMs,

"Attempting to boot a guest virtual machine that uses the Open Virtual
Machine Firmware (OVMF) on a Red Hat Enterprise Linux host using the
qemu-kvm package currently fails, with the guest becoming unresponsive and
displaying a blank screen. (BZ#1174132)" However this BZ# doesn't seem
accessible to the hoi polloi. Any ideas what this is about?


-- 
Richard Chan
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] supervdsmd IOError to /dev/stdout

2017-08-03 Thread Richard Chan
Did it change the file permissions when you copied
svdsm.logger.conf.rpmnew?  No, the file permission were the same root:root
0644

Yes reproducible with 3.6 config file - it is definitely due to the 3.6
svdsm.logger.conf: when I copied the rpmnew file from 4.1, it works again.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] supervdsmd IOError to /dev/stdout

2017-08-01 Thread Richard Chan
Hi,

Could this be the cause of the access issue (old system upgraded from 3.4
all the way to 4.1)?
## change in python class name??

 [handler_logfile]
-class=logUtils.UserGroupEnforcingHandler
+class=vdsm.logUtils.UserGroupEnforcingHandler

When I copied  svdsm.logger.conf.rpmnew over svdsm.logger.conf, it could
start up.

Thanks!



On Tue, Aug 1, 2017 at 5:02 PM, Yaniv Bronheim <ybron...@redhat.com> wrote:

> Hi,
>
> Seems like I already bumped in such issue awhile ago -
> https://bugzilla.redhat.com/show_bug.cgi?id=1216880
> but now I see what's wrong -  it happens after failing to read
> /etc/vdsm/svdsm.logger.conf for some reason
> then we have a bug in our fallback which tries to run
> logging.basicConfig(filename='/dev/stdout', filemode='w+',
> level=logging.DEBUG)
>
> and this fails while running as systemd daemon
>
> sorry about that. check why it can't load  /etc/vdsm/svdsm.logger.conf
> and update us
> after fixing the access issue check if you can run
> logging.config.fileConfig("/etc/vdsm/svdsm.logger.conf" ,
> disable_existing_loggers=False)
> Then supervdsmd should start properly
>
> I'll reopen the bugzilla and fix the wrong fallback to syslog print
>
> Thanks!
>
>
> On Sun, Jul 30, 2017 at 3:23 PM Richard Chan <rich...@treeboxsolutions.com>
> wrote:
>
>> Hi Yaniv,
>>
>> On this one node, it happened from 3.6 -> 4.0. It persisted after
>> 4.0->4.1.
>> Current: vdsm-4.19.24-1.el7.centos.x86_64
>>
>>
>> In systemd override I now have to have:
>> StandardOutput=null
>>
>>
>>
>>
>> Jul 29 01:19:21  systemd[1]: Starting Auxiliary vdsm service for
>> running helper functions as root...
>> Jul 29 01:19:21  python2[39124]: detected unhandled Python
>> exception in '/usr/share/vdsm/supervdsmServer'
>> Jul 29 01:19:21  daemonAdapter[39124]: Traceback (most recent
>> call last):
>> Jul 29 01:19:21  daemonAdapter[39124]: File 
>> "/usr/share/vdsm/supervdsmServer",
>> line 45, in 
>> Jul 29 01:19:21  daemonAdapter[39124]: level=logging.DEBUG)
>> Jul 29 01:19:21  daemonAdapter[39124]: File
>> "/usr/lib64/python2.7/logging/__init__.py", line 1529, in basicConfig
>> Jul 29 01:19:21  daemonAdapter[39124]: hdlr =
>> FileHandler(filename, mode)
>> Jul 29 01:19:21  daemonAdapter[39124]: File
>> "/usr/lib64/python2.7/logging/__init__.py", line 902, in __init__
>> Jul 29 01:19:21  daemonAdapter[39124]:
>> StreamHandler.__init__(self, self._open())
>> Jul 29 01:19:21  daemonAdapter[39124]: File
>> "/usr/lib64/python2.7/logging/__init__.py", line 925, in _open
>> Jul 29 01:19:21  daemonAdapter[39124]: stream =
>> open(self.baseFilename, self.mode)
>> Jul 29 01:19:21  daemonAdapter[39124]: IOError: [Errno 6] No such
>> device or address: '/dev/stdout'
>> Jul 29 01:19:21  systemd[1]: supervdsmd.service: main process
>> exited, code=exited, status=1/FAILURE
>>
>>
>>
>> On Sun, Jul 30, 2017 at 3:47 PM, Yaniv Kaul <yk...@redhat.com> wrote:
>>
>>>
>>>
>>> On Fri, Jul 28, 2017 at 8:37 PM, Richard Chan <
>>> rich...@treeboxsolutions.com> wrote:
>>>
>>>> After an upgrade to 4.0 I have a single host that cannot start
>>>> supervdsmd because of IOError on /dev/stdout. All other hosts upgraded
>>>> correctly.
>>>>
>>>
>>> Upgrade from which version? 3.6? Did you stay on 4.0 or continued to 4.1?
>>>
>>>
>>>>
>>>> In the systemd unit I have to hack StandardOutput=null.
>>>>
>>>> Any thing I have overlooked? The hosts are all identical and it is just
>>>> this one
>>>> that has this weird behaviour.
>>>>
>>>
>>> Any logs that you can share?
>>>  Y.
>>>
>>>
>>>>
>>>> --
>>>> Richard Chan
>>>>
>>>>
>>>> ___
>>>> Users mailing list
>>>> Users@ovirt.org
>>>> http://lists.ovirt.org/mailman/listinfo/users
>>>>
>>>>
>>>
>>
>>
>> --
>> Richard Chan
>> Chief Architect
>>
>> TreeBox Solutions Pte Ltd
>> 1 Commonwealth Lane #03-01
>> Singapore 149544
>> Tel: 6570 3725
>> http://www.treeboxsolutions.com
>>
>> Co.Reg.No. 201100585R
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
> --
> Yaniv Bronhaim.
>



-- 
Richard Chan
Chief Architect

TreeBox Solutions Pte Ltd
1 Commonwealth Lane #03-01
Singapore 149544
Tel: 6570 3725
http://www.treeboxsolutions.com

Co.Reg.No. 201100585R
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] supervdsmd IOError to /dev/stdout

2017-07-30 Thread Richard Chan
Hi Yaniv,

On this one node, it happened from 3.6 -> 4.0. It persisted after 4.0->4.1.
Current: vdsm-4.19.24-1.el7.centos.x86_64


In systemd override I now have to have:
StandardOutput=null




Jul 29 01:19:21  systemd[1]: Starting Auxiliary vdsm service for
running helper functions as root...
Jul 29 01:19:21  python2[39124]: detected unhandled Python
exception in '/usr/share/vdsm/supervdsmServer'
Jul 29 01:19:21  daemonAdapter[39124]: Traceback (most recent call
last):
Jul 29 01:19:21  daemonAdapter[39124]: File
"/usr/share/vdsm/supervdsmServer", line 45, in 
Jul 29 01:19:21  daemonAdapter[39124]: level=logging.DEBUG)
Jul 29 01:19:21  daemonAdapter[39124]: File
"/usr/lib64/python2.7/logging/__init__.py", line 1529, in basicConfig
Jul 29 01:19:21  daemonAdapter[39124]: hdlr = FileHandler(filename,
mode)
Jul 29 01:19:21  daemonAdapter[39124]: File
"/usr/lib64/python2.7/logging/__init__.py", line 902, in __init__
Jul 29 01:19:21  daemonAdapter[39124]: StreamHandler.__init__(self,
self._open())
Jul 29 01:19:21  daemonAdapter[39124]: File
"/usr/lib64/python2.7/logging/__init__.py", line 925, in _open
Jul 29 01:19:21  daemonAdapter[39124]: stream =
open(self.baseFilename, self.mode)
Jul 29 01:19:21  daemonAdapter[39124]: IOError: [Errno 6] No such
device or address: '/dev/stdout'
Jul 29 01:19:21  systemd[1]: supervdsmd.service: main process
exited, code=exited, status=1/FAILURE



On Sun, Jul 30, 2017 at 3:47 PM, Yaniv Kaul <yk...@redhat.com> wrote:

>
>
> On Fri, Jul 28, 2017 at 8:37 PM, Richard Chan <
> rich...@treeboxsolutions.com> wrote:
>
>> After an upgrade to 4.0 I have a single host that cannot start supervdsmd
>> because of IOError on /dev/stdout. All other hosts upgraded correctly.
>>
>
> Upgrade from which version? 3.6? Did you stay on 4.0 or continued to 4.1?
>
>
>>
>> In the systemd unit I have to hack StandardOutput=null.
>>
>> Any thing I have overlooked? The hosts are all identical and it is just
>> this one
>> that has this weird behaviour.
>>
>
> Any logs that you can share?
>  Y.
>
>
>>
>> --
>> Richard Chan
>>
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>


-- 
Richard Chan
Chief Architect

TreeBox Solutions Pte Ltd
1 Commonwealth Lane #03-01
Singapore 149544
Tel: 6570 3725
http://www.treeboxsolutions.com

Co.Reg.No. 201100585R
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] Quick way to generate vmconsole host keys?

2017-07-29 Thread Richard Chan
Is there a quick way to generate the vmconsole host keys without putting
the host into maintenance and reinstalling?


-- 
Richard Chan
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] [SOLVED] Re: How to stop "Failed to stop image transfer session. Ticket does not exist for image" spam

2017-07-29 Thread Richard Chan
Solved: I did not see the "Cancel" option in the disk page when the disk
upload is stalled. Apologies for the noise.

On Sat, Jul 29, 2017 at 2:57 PM, Richard Chan <rich...@treeboxsolutions.com>
wrote:

> Using oVirt 4.1.3 - I have some failed disk uploads but the logs are being
> spammed by
>
>
> "Failed to stop image transfer session. Ticket does not exist for image"
>
> How to stop this? Thnaks!
>
>
> --
> Richard Chan
>
>


-- 
Richard Chan
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] Chrome 59 still will not upload to imageio, firefox ok

2017-07-29 Thread Richard Chan
oVirt 4.1.4

I have imageio proxy working with web ui on firefox.

On Chrome 59 I read bz# https://bugzilla.redhat.com/show_bug.cgi?id=1430598

and set "EnableCommonNameFallbackForLocalAnchors": true.

However the upload fails with

Make sure ovirt-imageio-proxy service is installed and configured, and
ovirt-engine's certificate is registered as a valid CA in the browser. The
certificate can be fetched from https://
/ovirt-engine/services/pki-resource?resource=ca-certificate=X509-PEM-CA

In the terminal I see
:ERROR:cert_verify_proc_nss.cc(923)] CERT_PKIXVerifyCert for 
failed err=-8172

for both the web UI and imageio proxy. Any suggestions?


-- 
Richard Chan
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] imageio: Error setting ImageProxyAddress's value. No such entry with version general.

2017-07-29 Thread Richard Chan
oVirt 4.1.4 - engine-setup of imageio proxy on a host, at the end it
requires:

engine-config -s ImageProxyAddress=:54323

But on engine:

Error setting ImageProxyAddress's value. No such entry with version general.

Any ideas thanks!



-- 
Richard Chan
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] How to stop "Failed to stop image transfer session. Ticket does not exist for image" spam

2017-07-29 Thread Richard Chan
Using oVirt 4.1.3 - I have some failed disk uploads but the logs are being
spammed by


"Failed to stop image transfer session. Ticket does not exist for image"

How to stop this? Thnaks!


-- 
Richard Chan
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] supervdsmd IOError to /dev/stdout

2017-07-28 Thread Richard Chan
After an upgrade to 4.0 I have a single host that cannot start supervdsmd
because of IOError on /dev/stdout. All other hosts upgraded correctly.

In the systemd unit I have to hack StandardOutput=null.

Any thing I have overlooked? The hosts are all identical and it is just
this one
that has this weird behaviour.


-- 
Richard Chan
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Overlapping packages in CentOS 7 repo files from ovirt and mirror.centos.org

2017-01-02 Thread Richard Chan
"The fact you see overlapping versions in oVirt repo and CentOS
Virtualization SIG repositories is due to the fact the two repositories are
independent. You can use either the oVIrt one (built by oVirt release
engineering) or the CentOS one (built by CentOS Virt SIG)."


We are actually ok with using resources.ovirt.org packages but the CentOS
VIrtualization SIG repo was enabled by ovirt-release40-4.0.5-2.noarch
itself:


/etc/yum.repos.d/ovirt-4.0-dependencies.repo:

[centos-ovirt40-release]
name=CentOS-7 - oVirt 4.0
baseurl=http://mirror.centos.org/centos/7/virt/$basearch/ovirt-4.0/
gpgcheck=0
enabled=1

This stanza does not use priority= or includepkgs= so is it deterministic
that vdsm comes from resources.ovirt.org?

1. When I did a test run of "yum install vdsm":
 vdsm-* packages were pulled from ovirt-4.0 (yay!)
but
  python-*
  safelease
  ioprocess
  openvswitch
  ovirt-imageio-*
came from centos-ovirt40-release.

2. To be deterministic, i.e., force vdsm* from ovirt-4.0 insteaad of
accidentally getting from CentOS SIG,  I am considering (similar to the
epel repo stanza)

[centos-ovirt40-release]
name=CentOS-7 - oVirt 4.0
baseurl=http://mirror.centos.org/centos/7/virt/$basearch/ovirt-4.0/
includepkgs=python-* safelease ioprocess openvswitch ovirt-imageio-*
## or exclude=vdsm*
gpgcheck=0
enabled=1


What do you think about this tightening? Thanks.



> Richard Chan
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] Overlapping packages in CentOS 7 repo files from ovirt and mirror.centos.org

2016-12-29 Thread Richard Chan
Hi all,

The repo files for ovirt-4.0 seem to have overlapping packages from (el7 vs
centos.el7 naming).

resources.ovirt.org: ovirt-4.0

and

mirror.centos.org/centos/7/virt/x86_64/ovirt-4.0/: centos-ovirt40-release

for example

vdsm-4.18.15.3-1.el7.centos.x86_64.rpm

vs

vdsm-4.18.15.3-1.el7.x86_64.rpm


Which one should "win"? We need this for auditing purposes.

Thanks.


-- 
Richard Chan
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] 3.6.7 engine: compatible with host centos 7.3/vdsm 4.18/qemu 2.6?

2016-12-15 Thread Richard Chan
Thanks - I have one more question about overlapping repositories from
ovirt proper and centos virt SIG

ovirt-4.0.repo:

A. http://resources.ovirt.org/pub/ovirt-4.0/rpm/el7/ (from mirrorlist)

ovirt-4.0-dependencies.repo:

B. http://mirror.centos.org/centos/7/virt/$basearch/ovirt-4.0/

For auditing purposes, is the following understanding correct?
a. B is a subset of A (meant only for host/node)
b. B RPMs are identical with  A RPMs except signed with a different key.
c. A default installation (i.e. don't edit *.repo files)  will pull RPMs
from ovirt rather than centos.



Richard




___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] 3.6.7 engine: compatible with host centos 7.3/vdsm 4.18/qemu 2.6?

2016-12-15 Thread Richard Chan
Planning and upgrade from 3.6.8 to 4.0.6:

4.0.6 mentions supporting CentOS 7.3 and qemu-kvm-ev 2.6

Is it possible in a 3.6.7 environment to upgrade all the hosts first to
CentOS 7.3, vdsm 4.18, and qemu-kvm-ev 2.6 before tackling the engine? In
other words, is the 4.0.6 host stack compatible with a 3.6.7 engine?



-- 
Richard Chan
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] 3.6.5.3: UI Uncaught Exception: New VM from Template

2016-05-10 Thread Richard Chan
On Tue, May 10, 2016 at 11:34 PM, Alexander Wels <aw...@redhat.com> wrote:

>
> Looks like they already did that as the bottom stack trace has this in it:
> org.ovirt.engine.ui.uicommonweb.models.storage.DisksAllocationModel.
> $updateImageToDestinationDomainMap(DisksAllocationModel.java:288)
>
> So looks like an issue in DiskAllocationModel.
>

[SOLVED: user permissions problem]
I managed to solve the issue: the user did not have sufficient permissions
on the Storage domain. Assigning the user PowerUser role made VM creation
from template work.

RFE: the UI error messages and even the unobfuscated stack trace are not
really very helpful. Is there any way that error reporting can be improved?
Some pop-up "Insufficient permissions" like the ovirt-shell command line?




Richard Chan
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] 3.6.5.3: UI Uncaught Exception: New VM from Template

2016-05-07 Thread Richard Chan
Hello list, I hope you can help with a UI exception from New VM from
Template.

1. User (PowerUser) is able to create New VMs manually
2. New VM from template gives a UI exception:

__gwt$exception: : Cannot read property 'f' of undefined

2016-05-08 11:04:50,875 ERROR
[org.ovirt.engine.ui.frontend.server.gwt.OvirtRemoteLoggingService]
(default task-28) [] Permutation name: 56114F8548175924C03C3BC67436871E
2016-05-08 11:04:50,875 ERROR
[org.ovirt.engine.ui.frontend.server.gwt.OvirtRemoteLoggingService]
(default task-28) [] Uncaught exception: :
com.google.gwt.core.client.JavaScriptException: (TypeError)
 __gwt$exception: : f is undefined
at
org.ovirt.engine.ui.uicommonweb.models.storage.DisksAllocationModel.$updateImageToDestinationDomainMap(DisksAllocationModel.java:288)
at
org.ovirt.engine.ui.uicommonweb.models.storage.DisksAllocationModel.$getImageToDestinationDomainMap(DisksAllocationModel.java:130)
at
org.ovirt.engine.ui.uicommonweb.models.templates.VmBaseListModel.$saveNewVm(VmBaseListModel.java:354)
at
org.ovirt.engine.ui.uicommonweb.models.templates.VmBaseListModel.$onSaveVM(VmBaseListModel.java:331)
at
org.ovirt.engine.ui.uicommonweb.models.templates.VmBaseListModel$6.onSuccess(VmBaseListModel.java:309)
at
org.ovirt.engine.ui.frontend.Frontend$2.$onSuccess(Frontend.java:244)
[frontend.jar:]





-- 
Richard Chan
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users