[ovirt-users] Ghost Snapshot Disk

[Lionel Caignec]

Hi,

i've a problem with snapshot. On one VM i've a "snapshot" ghost without name or 
uuid, only information is size (see attachment). In the snapshot tab there is 
no trace about this disk.

In database (table images) i found this : 
  f242cc9a-56c1-4ae4-aef0-f75eb01f74b1 | 2018-01-17 22:02:00+01 | 2748779069440 
| ---- | ---- | 
  4 | 2018-01-18 22:01:20.5+01   | 0dd2090c-3491-4fa1-98c3-54ae88be793c
 |   2 | 4 | 17e26476-cecb-441d-a5f7-46ab3ef387ee | 
2018-01-17 22:01:29.663334+01 | 2018-01-19 08:40:14.345229+01 | f  |
 1 |   2
 1c7650fa-542b-4ec2-83a1-d2c1c31be5fd | 2018-01-17 22:02:03+01 | 536870912 
| ---- | ---- | 
  4 | 2018-01-18 22:01:20.84+01  | 0dd2090c-3491-4fa1-98c3-54ae88be793c
 |   2 | 4 | bf834a91-c69f-4d2c-b639-116ed58296d8 | 
2018-01-17 22:01:29.836133+01 | 2018-01-19 08:40:19.083508+01 | f  |
 1 |   2
 8614b21f-c0de-40f2-b4fb-e5cf193b0743 | 2018-02-09 23:00:44+01 | 536870912 
| ---- | ---- | 
  4 | 2018-02-16 23:00:02.855+01 | 390175dc-baf4-4831-936a-5ea68fa4c969


 But i does not know which line is my disk. Is it possible to delete directly 
into database? 
 Or is it better to dump my disk to another new and delete the "corrupted one"?

 Another thing, when i try to move the disk to another storage domain i always 
get "uncaght exeption occured ..." and no error in engine.log.


 Thank you for helping.

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

Re: [ovirt-users] Confused by logical networks

[Yaniv Kaul]

On Feb 22, 2018 5:26 PM, "Paul-Erik Törrönen"  wrote:

I'm not sure how the logical networks should work and would appreciate if
someone could shed some light into the matter, I've tried reading the
documentation¹ but have not become any wiser :-/

For the sake of argument, I have two hosts in the same cluster/DC, They
both have 2 network devices each (let's call them eth0 and eth1). On both
hosts the ovirtmgmgt is connected to eth0 and uses the 10.0.0.0/8-network.
Host 1 is 10.0.0.1 and host 2 is 10.0.0.2. All four network devices are
connected to one switch.

Then I create a logical network, mylogic which should be 192.168.1.0/24,
which I assign to eth1 on each host, but define only for host 1 an
ip-address, 192.168.1.1, host 2 has also the network assigned to eth1, but
withouth an ip address.


There's no reason really to assign IPs to hosts on the logical network.
oVirt provides layer 2 (L2) connectivity to VMs. Whatever DHCP, DNS or
gateway is on that network, they'll use. It should not be one of the hosts.
Their interfaces just bridge the VM traffic over to the designated network,
nothing more.
Y.


Next I create vm1 on host 1, give it a single virtual network connection to
mylogic, and configure the guest to use 192.168.1.2 with gw 192.168.1.1.
Obviously I can from the guest ping 192.168.1.1 which is the host address
on the logical network as the guest is running on the same hardware where
the host ip address is defined.

However, and this is where my confusion lies, if I now create another vm,
vm2, on host 2, attach its network device to the mylogic network and
configure it to use 192.168.1.3 with gw 192.168.1.1, I can not ping neither
192.168.1.1 nor 192.168.1.2.

My understanding is that vm2 should be able to ping the wm1 as well as the
gateway address defined on host 1. However this does not seem to be the
case.

What have I missed here?

TIA,

Poltsi

¹ https://www.ovirt.org/documentation/admin-guide/chap-Logical_Networks/
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Confused by logical networks

[Vincent Royer]

should work out for you then.  In my case I was trying to do it all just
with static addressing without dns entries and I quickly learned that it's
just not designed to operate that way.

Cheers

*Vincent Royer*
*778-825-1057*



*SUSTAINABLE MOBILE ENERGY SOLUTIONS*




On Thu, Feb 22, 2018 at 9:16 PM, Paul-Erik Törrönen 
wrote:

> On 2018-02-22 22:56, Vincent Royer wrote:
>
>> Hope some part of this helps you!
>>
>
> Thanks for your answer, I need to digest it more in detail, but it seems
> like I indeed have missed some essential parts.
>
> I'll come back with a more detailed result later, but for the record, I do
> have a DNS server that I can manage completely in this case, and the switch
> management is also accessible to me.
>
> Poltsi
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Confused by logical networks

[Paul-Erik Törrönen]

On 2018-02-22 22:56, Vincent Royer wrote:

Hope some part of this helps you!


Thanks for your answer, I need to digest it more in detail, but it seems 
like I indeed have missed some essential parts.


I'll come back with a more detailed result later, but for the record, I 
do have a DNS server that I can manage completely in this case, and the 
switch management is also accessible to me.


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

Re: [ovirt-users] Installing Windows - no virtio-win.vfd as floppy option

[Vincent Royer]

Sure, feel free to reach out, I just did a big windows deployment and there
were lots of hurdles to overcome, but it does work well in the end.  I used
the console during windows install, but I was doing it remotely, in an RDP
session with a server on-site.  So the mouse control was all out of whack,
I had to keyboard through the setup.   Once windows is installed and joined
to the domain, you can RDP into it and it's much more bearable to operate
than the console method.

*Vincent Royer*
*778-825-1057*



*SUSTAINABLE MOBILE ENERGY SOLUTIONS*




On Thu, Feb 22, 2018 at 4:25 PM, Geoff Sweet <
geoffrsweet+ovirtus...@gmail.com> wrote:

> Yeah I just read that.  I managed to discover that there is the
> "virtio-win" packages available in my repo, but apparently they aren't
> signed.  So then I disovered the Fedora relased ones that at least are
> signed.  Guess I will give those a whirl and see where it gets me.
>
> -G
>
> On Thu, Feb 22, 2018 at 3:50 PM, Vincent Royer 
> wrote:
>
>> download the ISO separately and put it in your storage domain.  Then use
>> the "Change CD" function to load it part-way through the windows
>> installation when it is looking for the disk to install to.  Once you
>> install all the drivers, the network will start working and the drives will
>> show up and you'll be able to proceed with your windows installation.
>>
>> Following the instructions did not work for me either.
>>
>> *Vincent Royer*
>> *778-825-1057 <(778)%20825-1057>*
>>
>>
>> 
>> *SUSTAINABLE MOBILE ENERGY SOLUTIONS*
>>
>>
>>
>>
>> On Thu, Feb 22, 2018 at 3:38 PM, Geoff Sweet <
>> geoffrsweet+ovirtus...@gmail.com> wrote:
>>
>>> Howdy all, I'm following this document:
>>>
>>> https://www.ovirt.org/documentation/vmm-guide/chap-Installin
>>> g_Windows_Virtual_Machines/
>>>
>>> To launch a couple Windows VM's. The document outlines that the
>>> virtio-win.vfd file is automatically installed into the ISO storage domain
>>> for the engine host. And that you can upload it to other ISO domains as
>>> needed.  For the life of me, I can not find that file anywhere across any
>>> of my ovirt servers.  For reference this is 4.2.0.
>>>
>>> Am I missing something obvious?
>>>
>>> Thanks for any help you can offer.
>>>
>>> -Geoff
>>>
>>> ___
>>> Users mailing list
>>> Users@ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/users
>>>
>>>
>>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Installing Windows - no virtio-win.vfd as floppy option

[Geoff Sweet]

Yeah I just read that.  I managed to discover that there is the
"virtio-win" packages available in my repo, but apparently they aren't
signed.  So then I disovered the Fedora relased ones that at least are
signed.  Guess I will give those a whirl and see where it gets me.

-G

On Thu, Feb 22, 2018 at 3:50 PM, Vincent Royer 
wrote:

> download the ISO separately and put it in your storage domain.  Then use
> the "Change CD" function to load it part-way through the windows
> installation when it is looking for the disk to install to.  Once you
> install all the drivers, the network will start working and the drives will
> show up and you'll be able to proceed with your windows installation.
>
> Following the instructions did not work for me either.
>
> *Vincent Royer*
> *778-825-1057*
>
>
> 
> *SUSTAINABLE MOBILE ENERGY SOLUTIONS*
>
>
>
>
> On Thu, Feb 22, 2018 at 3:38 PM, Geoff Sweet <
> geoffrsweet+ovirtus...@gmail.com> wrote:
>
>> Howdy all, I'm following this document:
>>
>> https://www.ovirt.org/documentation/vmm-guide/chap-Installin
>> g_Windows_Virtual_Machines/
>>
>> To launch a couple Windows VM's. The document outlines that the
>> virtio-win.vfd file is automatically installed into the ISO storage domain
>> for the engine host. And that you can upload it to other ISO domains as
>> needed.  For the life of me, I can not find that file anywhere across any
>> of my ovirt servers.  For reference this is 4.2.0.
>>
>> Am I missing something obvious?
>>
>> Thanks for any help you can offer.
>>
>> -Geoff
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Installing Windows - no virtio-win.vfd as floppy option

[Vincent Royer]

download the ISO separately and put it in your storage domain.  Then use
the "Change CD" function to load it part-way through the windows
installation when it is looking for the disk to install to.  Once you
install all the drivers, the network will start working and the drives will
show up and you'll be able to proceed with your windows installation.

Following the instructions did not work for me either.

*Vincent Royer*
*778-825-1057*



*SUSTAINABLE MOBILE ENERGY SOLUTIONS*




On Thu, Feb 22, 2018 at 3:38 PM, Geoff Sweet <
geoffrsweet+ovirtus...@gmail.com> wrote:

> Howdy all, I'm following this document:
>
> https://www.ovirt.org/documentation/vmm-guide/chap-
> Installing_Windows_Virtual_Machines/
>
> To launch a couple Windows VM's. The document outlines that the
> virtio-win.vfd file is automatically installed into the ISO storage domain
> for the engine host. And that you can upload it to other ISO domains as
> needed.  For the life of me, I can not find that file anywhere across any
> of my ovirt servers.  For reference this is 4.2.0.
>
> Am I missing something obvious?
>
> Thanks for any help you can offer.
>
> -Geoff
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Installing Windows - no virtio-win.vfd as floppy option

[Geoff Sweet]

Howdy all, I'm following this document:

https://www.ovirt.org/documentation/vmm-guide/chap-Installing_Windows_Virtual_Machines/

To launch a couple Windows VM's. The document outlines that the
virtio-win.vfd file is automatically installed into the ISO storage domain
for the engine host. And that you can upload it to other ISO domains as
needed.  For the life of me, I can not find that file anywhere across any
of my ovirt servers.  For reference this is 4.2.0.

Am I missing something obvious?

Thanks for any help you can offer.

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

Re: [ovirt-users] Confused by logical networks

[Vincent Royer]

I had similar confusion, and trying to assign static IPs was just not
working for me.

Here is how I got it to work:

#1 you absolutely require a DNS server you can add entries to.  I tried to
go without, and it just does not work.

For me, management network is on vlan 10, so each host grabs a 172.16.10.xx
address.  The oVirt engine (self hosted) also grabs an address in this
subnet. I look in the DHCP leases and turn those into static assignments in
the router, but left the config on the hosts to DHCP.  Add those IPs to
your DNS so that you can reach each host, and the engine, at
hostname.domain.net (or whatever your fully qualified domain name is for
each)

Now, set your VM network to DHCP on a different, specific VLAN.  Set that
vlan up in your router with a small DHCP pool, only big enough for the VMs
you want to run. Make sure you allow that vlan through to the switchports
connected to the nic you are using for your VMs.

For me, the VMs are on vlan 30, so the subnet is 172.16.30.xx. Each VM
boots up, makes a DHCP request on vlan 30, and is assigned an address.
Then again go into your router and make this a static entry, leaving the
config in the VM to DHCP.  Once you install the agent in the VM, the IP
will show up in the engine GUI.  Then you can assign an FQDN to each vm's
IP I'm your DNS server.

Set up this way, I can migrate the VM to whichever host, and still access
it over RDP by it's FQDN.

I also have dual NICs but I set mine up as a team (bridge) instead of one
for MGMT and one for VMs.   That way, I can also unplug anyone Ethernet
cable from any machine, and nothing happens, both the MGMT and VM network
keep ticking away happily.  I have each NIC plugged into a separate switch
chassis, to gain redundancy on the switches.

Hope some part of this helps you!


On Feb 22, 2018 7:25 AM, "Paul-Erik Törrönen"  wrote:

> I'm not sure how the logical networks should work and would appreciate if
> someone could shed some light into the matter, I've tried reading the
> documentation¹ but have not become any wiser :-/
>
> For the sake of argument, I have two hosts in the same cluster/DC, They
> both have 2 network devices each (let's call them eth0 and eth1). On both
> hosts the ovirtmgmgt is connected to eth0 and uses the 10.0.0.0/8-network.
> Host 1 is 10.0.0.1 and host 2 is 10.0.0.2. All four network devices are
> connected to one switch.
>
> Then I create a logical network, mylogic which should be 192.168.1.0/24,
> which I assign to eth1 on each host, but define only for host 1 an
> ip-address, 192.168.1.1, host 2 has also the network assigned to eth1, but
> withouth an ip address.
>
> Next I create vm1 on host 1, give it a single virtual network connection
> to mylogic, and configure the guest to use 192.168.1.2 with gw 192.168.1.1.
> Obviously I can from the guest ping 192.168.1.1 which is the host address
> on the logical network as the guest is running on the same hardware where
> the host ip address is defined.
>
> However, and this is where my confusion lies, if I now create another vm,
> vm2, on host 2, attach its network device to the mylogic network and
> configure it to use 192.168.1.3 with gw 192.168.1.1, I can not ping neither
> 192.168.1.1 nor 192.168.1.2.
>
> My understanding is that vm2 should be able to ping the wm1 as well as the
> gateway address defined on host 1. However this does not seem to be the
> case.
>
> What have I missed here?
>
> TIA,
>
> Poltsi
>
> ¹ https://www.ovirt.org/documentation/admin-guide/chap-Logical_Networks/
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] rebooting hypervisors from time to time

[Erekle Magradze]

Dear all,

It would be great if someone will share any experience regarding the 
similar case, would be great to have a hint where to start investigation.


Thanks again

Cheers

Erekle


On 02/22/2018 05:05 PM, Erekle Magradze wrote:

Hello there,

I am facing the following problem from time to time one of the 
hypervisor (there are 3 of them)s is rebooting, I am using 
ovirt-release42-4.2.1-1.el7.centos.noarch and glsuter as a storage 
backend (glusterfs-3.12.5-2.el7.x86_64).


I am suspecting gluster because of the e.g. message bellow from one of 
the volumes,


Could you please help and suggest to which direction should 
investigation go?


Thanks in advance

Cheers

Erekle


[2018-02-22 15:36:10.011687] and [2018-02-22 15:37:10.955013]
[2018-02-22 15:41:10.198701] I [MSGID: 109063] 
[dht-layout.c:716:dht_layout_normalize] 0-virtimages-dht: Found 
anomalies in (null) (gfid = ----). 
Holes=1 overlaps=0
[2018-02-22 15:41:10.198704] I [MSGID: 109063] 
[dht-layout.c:716:dht_layout_normalize] 0-virtimages-dht: Found 
anomalies in (null) (gfid = ----). 
Holes=1 overlaps=0
[2018-02-22 15:42:11.293608] I [MSGID: 109063] 
[dht-layout.c:716:dht_layout_normalize] 0-virtimages-dht: Found 
anomalies in (null) (gfid = ----). 
Holes=1 overlaps=0
[2018-02-22 15:53:16.245720] I [MSGID: 100030] 
[glusterfsd.c:2524:main] 0-/usr/sbin/glusterfs: Started running 
/usr/sbin/glusterfs version 3.12.5 (args: /usr/sbin/glusterfs 
--volfile-server=10.0.0.21 --volfi
le-server=10.0.0.22 --volfile-server=10.0.0.23 
--volfile-id=/virtimages 
/rhev/data-center/mnt/glusterSD/10.0.0.21:_virtimages)
[2018-02-22 15:53:16.263712] W [MSGID: 101002] 
[options.c:995:xl_opt_validate] 0-glusterfs: option 'address-family' 
is deprecated, preferred is 'transport.address-family', continuing 
with correction
[2018-02-22 15:53:16.269595] I [MSGID: 101190] 
[event-epoll.c:613:event_dispatch_epoll_worker] 0-epoll: Started 
thread with index 1
[2018-02-22 15:53:16.273483] I [MSGID: 101190] 
[event-epoll.c:613:event_dispatch_epoll_worker] 0-epoll: Started 
thread with index 2
[2018-02-22 15:53:16.273594] W [MSGID: 101174] 
[graph.c:363:_log_if_unknown_option] 0-virtimages-readdir-ahead: 
option 'parallel-readdir' is not recognized
[2018-02-22 15:53:16.273703] I [MSGID: 114020] [client.c:2360:notify] 
0-virtimages-client-0: parent translators are ready, attempting 
connect on transport
[2018-02-22 15:53:16.276455] I [MSGID: 114020] [client.c:2360:notify] 
0-virtimages-client-1: parent translators are ready, attempting 
connect on transport
[2018-02-22 15:53:16.276683] I [rpc-clnt.c:1986:rpc_clnt_reconfig] 
0-virtimages-client-0: changing port to 49152 (from 0)
[2018-02-22 15:53:16.279191] I [MSGID: 114020] [client.c:2360:notify] 
0-virtimages-client-2: parent translators are ready, attempting 
connect on transport
[2018-02-22 15:53:16.282126] I [MSGID: 114057] 
[client-handshake.c:1478:select_server_supported_programs] 
0-virtimages-client-0: Using Program GlusterFS 3.3, Num (1298437), 
Version (330)
[2018-02-22 15:53:16.282573] I [MSGID: 114046] 
[client-handshake.c:1231:client_setvolume_cbk] 0-virtimages-client-0: 
Connected to virtimages-client-0, attached to remote volume 
'/mnt/virtimages/virtimgs'.
[2018-02-22 15:53:16.282584] I [MSGID: 114047] 
[client-handshake.c:1242:client_setvolume_cbk] 0-virtimages-client-0: 
Server and Client lk-version numbers are not same, reopening the fds
[2018-02-22 15:53:16.282665] I [MSGID: 108005] 
[afr-common.c:4929:__afr_handle_child_up_event] 
0-virtimages-replicate-0: Subvolume 'virtimages-client-0' came back 
up; going online.
[2018-02-22 15:53:16.282877] I [rpc-clnt.c:1986:rpc_clnt_reconfig] 
0-virtimages-client-1: changing port to 49152 (from 0)
[2018-02-22 15:53:16.282934] I [MSGID: 114035] 
[client-handshake.c:202:client_set_lk_version_cbk] 
0-virtimages-client-0: Server lk version = 1


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


--
Recogizer Group GmbH

Dr.rer.nat. Erekle Magradze
Lead Big Data Engineering & DevOps
Rheinwerkallee 2, 53227 Bonn
Tel: +49 228 29974555

E-Mail erekle.magra...@recogizer.de
recogizer.com

-

Recogizer Group GmbH
Geschäftsführer: Oliver Habisch, Carsten Kreutze
Handelsregister: Amtsgericht Bonn HRB 20724
Sitz der Gesellschaft: Bonn; USt-ID-Nr.: DE294195993
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten 
haben, informieren Sie bitte sofort den Absender und löschen Sie diese Mail. 
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail und der 
darin enthaltenen Informationen ist nicht gestattet.

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

Re: [ovirt-users] Upgrade Cluster Compat Level from 4.1 to 4.2

[Michal Skrivanek]

> On 22 Feb 2018, at 20:23, Arsène Gschwind  wrote:
> 
> Hi,
> 
> I could successfully upgrade our Ovirt Environment from 4.1.9 to 4.2.1, 
> really great job with the new interface.
> Everything runs well so far, the only problem I have is when trying to 
> Upgrade the Cluster Compatibility Level from 4.1 to 4.2 it throw an error :
> 
> Error while executing action: Update of cluster compatibility version failed 
> because there are VMs/Templates [spfy-tscon] with incorrect configuration. To 
> fix the issue, please go to each of them, edit and press OK. If the save does 
> not pass, fix the dialog validation.
> 
> This VM is a Windows Server 2016 System with a custom property using smbios 
> hook, could that be the problem?
> 
Hi,
if it’s a user defined custom property you need to define it for the new 
cluster level too, similarly as you did originally

Thanks,
michal
> The engine log don't help a lot:
> 
> 2018-02-22 18:49:42,026+01 ERROR 
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
> (default task-57) [595850d5] EVENT_ID: 
> CLUSTER_CANNOT_UPDATE_VM_COMPATIBILITY_VERSION(12,005), Cannot update 
> compatibility version of Vm/Template: [spfy-tscon], Message: [No Message]
> 
> Are there some other place to investigate and get some more information about 
> this error?
> Thanks a lot for any Hint/Help.
> 
> rgds,
> Arsene
> -- 
> Arsène Gschwind 
> Fa. Sapify AG im Auftrag der Universität Basel
> IT Services
> Klingelbergstr. 70 |  CH-4056 Basel  |  Switzerland
> Tel. +41 79 449 25 63  |  http://its.unibas.ch  
> ITS-ServiceDesk: support-...@unibas.ch  | +41 
> 61 267 14 11 
> 
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users

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

[ovirt-users] Upgrade Cluster Compat Level from 4.1 to 4.2

[Arsène Gschwind]

Hi,

I could successfully upgrade our Ovirt Environment from 4.1.9 to 4.2.1, 
really great job with the new interface.
Everything runs well so far, the only problem I have is when trying to 
Upgrade the Cluster Compatibility Level from 4.1 to 4.2 it throw an error :


Error while executing action: Update of cluster compatibility version 
failed because there are VMs/Templates [spfy-tscon] with incorrect 
configuration. To fix the issue, please go to each of them, edit and 
press OK. If the save does not pass, fix the dialog validation.


This VM is a Windows Server 2016 System with a custom property using 
smbios hook, could that be the problem?

The engine log don't help a lot:

/2018-02-22 18:49:42,026+01 ERROR 
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(default task-57) [595850d5] EVENT_ID: 
CLUSTER_CANNOT_UPDATE_VM_COMPATIBILITY_VERSION(12,005), Cannot update 
compatibility version of Vm/Template: [spfy-tscon], Message: [No Message]//

/

Are there some other place to investigate and get some more information 
about this error?


Thanks a lot for any Hint/Help.

rgds,
Arsene

--

*Arsène Gschwind*
Fa. Sapify AG im Auftrag der Universität Basel
IT Services
Klingelbergstr. 70 |  CH-4056 Basel  |  Switzerland
Tel. +41 79 449 25 63  | http://its.unibas.ch 
ITS-ServiceDesk: support-...@unibas.ch | +41 61 267 14 11


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

[ovirt-users] Question about sanlock lockspaces

[Artem Tambovskiy]

Hello,

I'm still troubleshooting my cluster and trying to figure out which
lockspaces should be present and which shouldn't.

If HE VM is not running both ovirt-ha-agent and ovirt-ha-broker are down
and storage disconnected by hosted-engine --disconnect-storage should I see
something related to HE storage domain in
sanlock client status output?

For some reason on one host I don't see anything and the second one still
reports about present lockspace for HE storage domain. Is this normal?

[root@ovirt1 ~]# sanlock client status
daemon b1d7fea2-e8a9-4645-b449-97702fc3808e.ovirt1.tel
p -1 helper
p -1 listener
p -1 status
p 3763
p 62861 quaggaVM
p 63111 powerDNS
p 107818 pjsip_freepbx_14
p 109092 revizorro_dev
p 109589 routerVM
s a40cc3a9-54d6-40fd-acee-525ef29c8ce3:2:/rhev/data-center/mnt/glusterSD/
ovirt2.telia.ru\:_data/a40cc3a9-54d6-40fd-acee-525ef29c8ce3/dom_md/ids:0
s 4a7f8717-9bb0-4d80-8016-498fa4b88162:1:/rhev/data-center/mnt/glusterSD/
ovirt2.telia.ru\:_engine/4a7f8717-9bb0-4d80-8016-498fa4b88162/dom_md/ids:0
r a40cc3a9-54d6-40fd-acee-525ef29c8ce3:SDM:/rhev/data-center/mnt/glusterSD/
ovirt2.telia.ru\:_data/a40cc3a9-54d6-40fd-acee-525ef29c8ce3/dom_md/leases:1048576:49
p 3763

As it looks to me lockspace
4a7f8717-9bb0-4d80-8016-498fa4b88162:1:/rhev/data-center/mnt/glusterSD/
ovirt2.telia.ru\:_engine/4a7f8717-9bb0-4d80-8016-498fa4b88162/dom_md/ids:0
shouldn't be present, and it doesn't match to the host_id, but may be I'm
wrong here...

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

[ovirt-users] Change management network

[Chris Boot]

Hi all,

I have an oVirt cluster on which I need to change which VLAN is the
management network.

The new management network is an existing VM network. I've configured IP
addresses for all the hosts on this network, and I've even moved the
HostedEngine VM onto this network. So far so good.

What I cannot seem to be able to do is actually change the "management
network" toggle in the cluster to this network: the oVirt Engine
complains saying:

"Error while executing action: Cannot edit Network. Changing management
network in a non-empty cluster is not allowed."

How can I get around this? I clearly cannot empty the cluster, as the
cluster contains all my existing VMs, hosts and HostedEngine.

Best regards,
Chris

-- 
Chris Boot
bo...@boo.tc
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] oVirt 4.2: hostdev passthrough not working any more

[Michal Skrivanek]

> On 22 Feb 2018, at 16:45, Alexandr Krivulya  wrote:
> 
> 22.02.2018 11:37, Alexandr Krivulya пишет:
>> 
>> 22.02.2018 11:30, Martin Polednik пишет:
>>> On 22/02/18 10:40 +0200, Alexandr Krivulya wrote: 
 Hello, the same problem after upgrade to 4.2.1 :( 
 
 
 18.01.2018 11:53, Daniel Helgenberger пишет: 
> Hello, 
> 
> yesterday I upgraded to 4.2.0 from 4.1.8. 
> 
> Now I notice I cannot assign host dev pass though any more; in the GUI 
> the 'Pinnded to host' list is empty; I cannot select any host for pass 
> through host pinning. 
>>> 
>>> Does the host that previously worked report device passthrough 
>>> capability? In the UI it's the "Device Passthrough: Enabled" field. 
>>> (and similarly named field in vdsm-client getCapabilities call)
>> Now "Device Passthrough: Disabled", but usb passthrough works well on 4.1
> 
> After enabling intel_iommu usb passthrough works again. But why this option 
> needed for usb now?

it should not be
sounds like a regression
can you please open a bug on that and add logs?

Thanks,
michal

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

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

[ovirt-users] rebooting hypervisors from time to time

[Erekle Magradze]

Hello there,

I am facing the following problem from time to time one of the 
hypervisor (there are 3 of them)s is rebooting, I am using 
ovirt-release42-4.2.1-1.el7.centos.noarch and glsuter as a storage 
backend (glusterfs-3.12.5-2.el7.x86_64).


I am suspecting gluster because of the e.g. message bellow from one of 
the volumes,


Could you please help and suggest to which direction should 
investigation go?


Thanks in advance

Cheers

Erekle


[2018-02-22 15:36:10.011687] and [2018-02-22 15:37:10.955013]
[2018-02-22 15:41:10.198701] I [MSGID: 109063] 
[dht-layout.c:716:dht_layout_normalize] 0-virtimages-dht: Found 
anomalies in (null) (gfid = ----). 
Holes=1 overlaps=0
[2018-02-22 15:41:10.198704] I [MSGID: 109063] 
[dht-layout.c:716:dht_layout_normalize] 0-virtimages-dht: Found 
anomalies in (null) (gfid = ----). 
Holes=1 overlaps=0
[2018-02-22 15:42:11.293608] I [MSGID: 109063] 
[dht-layout.c:716:dht_layout_normalize] 0-virtimages-dht: Found 
anomalies in (null) (gfid = ----). 
Holes=1 overlaps=0
[2018-02-22 15:53:16.245720] I [MSGID: 100030] [glusterfsd.c:2524:main] 
0-/usr/sbin/glusterfs: Started running /usr/sbin/glusterfs version 
3.12.5 (args: /usr/sbin/glusterfs --volfile-server=10.0.0.21 --volfi
le-server=10.0.0.22 --volfile-server=10.0.0.23 --volfile-id=/virtimages 
/rhev/data-center/mnt/glusterSD/10.0.0.21:_virtimages)
[2018-02-22 15:53:16.263712] W [MSGID: 101002] 
[options.c:995:xl_opt_validate] 0-glusterfs: option 'address-family' is 
deprecated, preferred is 'transport.address-family', continuing with 
correction
[2018-02-22 15:53:16.269595] I [MSGID: 101190] 
[event-epoll.c:613:event_dispatch_epoll_worker] 0-epoll: Started thread 
with index 1
[2018-02-22 15:53:16.273483] I [MSGID: 101190] 
[event-epoll.c:613:event_dispatch_epoll_worker] 0-epoll: Started thread 
with index 2
[2018-02-22 15:53:16.273594] W [MSGID: 101174] 
[graph.c:363:_log_if_unknown_option] 0-virtimages-readdir-ahead: option 
'parallel-readdir' is not recognized
[2018-02-22 15:53:16.273703] I [MSGID: 114020] [client.c:2360:notify] 
0-virtimages-client-0: parent translators are ready, attempting connect 
on transport
[2018-02-22 15:53:16.276455] I [MSGID: 114020] [client.c:2360:notify] 
0-virtimages-client-1: parent translators are ready, attempting connect 
on transport
[2018-02-22 15:53:16.276683] I [rpc-clnt.c:1986:rpc_clnt_reconfig] 
0-virtimages-client-0: changing port to 49152 (from 0)
[2018-02-22 15:53:16.279191] I [MSGID: 114020] [client.c:2360:notify] 
0-virtimages-client-2: parent translators are ready, attempting connect 
on transport
[2018-02-22 15:53:16.282126] I [MSGID: 114057] 
[client-handshake.c:1478:select_server_supported_programs] 
0-virtimages-client-0: Using Program GlusterFS 3.3, Num (1298437), 
Version (330)
[2018-02-22 15:53:16.282573] I [MSGID: 114046] 
[client-handshake.c:1231:client_setvolume_cbk] 0-virtimages-client-0: 
Connected to virtimages-client-0, attached to remote volume 
'/mnt/virtimages/virtimgs'.
[2018-02-22 15:53:16.282584] I [MSGID: 114047] 
[client-handshake.c:1242:client_setvolume_cbk] 0-virtimages-client-0: 
Server and Client lk-version numbers are not same, reopening the fds
[2018-02-22 15:53:16.282665] I [MSGID: 108005] 
[afr-common.c:4929:__afr_handle_child_up_event] 
0-virtimages-replicate-0: Subvolume 'virtimages-client-0' came back up; 
going online.
[2018-02-22 15:53:16.282877] I [rpc-clnt.c:1986:rpc_clnt_reconfig] 
0-virtimages-client-1: changing port to 49152 (from 0)
[2018-02-22 15:53:16.282934] I [MSGID: 114035] 
[client-handshake.c:202:client_set_lk_version_cbk] 
0-virtimages-client-0: Server lk version = 1


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

Re: [ovirt-users] VMs with multiple vdisks don't migrate

[Maor Lipchuk]

I encountered a bug (see [1]) which contains the same error mentioned in
your VDSM logs (see [2]), but I doubt it is related.
Milan, maybe you have any advice to troubleshoot the issue? Will the
libvirt/qemu logs can help?
I would suggest to open a bug on that issue so we can track it more
properly.

Regards,
Maor


[1]
https://bugzilla.redhat.com/show_bug.cgi?id=1486543 -  Migration leads to
VM running on 2 Hosts

[2]
2018-02-16 09:43:35,236+0100 ERROR (jsonrpc/7) [jsonrpc.JsonRpcServer]
Internal server error (__init__:577)
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/yajsonrpc/__init__.py", line 572,
in _handle_request
res = method(**params)
  File "/usr/lib/python2.7/site-packages/vdsm/rpc/Bridge.py", line 198, in
_dynamicMethod
result = fn(*methodArgs)
  File "/usr/share/vdsm/API.py", line 1454, in getAllVmIoTunePolicies
io_tune_policies_dict = self._cif.getAllVmIoTunePolicies()
  File "/usr/share/vdsm/clientIF.py", line 454, in getAllVmIoTunePolicies
'current_values': v.getIoTune()}
  File "/usr/share/vdsm/virt/vm.py", line 2859, in getIoTune
result = self.getIoTuneResponse()
  File "/usr/share/vdsm/virt/vm.py", line 2878, in getIoTuneResponse
res = self._dom.blockIoTune(
  File "/usr/lib/python2.7/site-packages/vdsm/virt/virdomain.py", line 47,
in __getattr__
% self.vmid)
NotConnectedError: VM u'755cf168-de65-42ed-b22f-efe9136f7594' was not
started yet or was shut down

On Thu, Feb 22, 2018 at 4:22 PM, fsoyer  wrote:

> Hi,
> Yes, on 2018-02-16 (vdsm logs) I tried with a VM standing on ginger
> (192.168.0.6) migrated (or failed to migrate...) to victor (192.168.0.5),
> while the engine.log in the first mail on 2018-02-12 was for VMs standing
> on victor, migrated (or failed to migrate...) to ginger. Symptoms were
> exactly the same, in both directions, and VMs works like a charm before,
> and even after (migration "killed" by a poweroff of VMs).
> Am I the only one experimenting this problem ?
>
>
> Thanks
> --
>
> Cordialement,
>
> *Frank Soyer *
>
>
>
> Le Jeudi, Février 22, 2018 00:45 CET, Maor Lipchuk 
> a écrit:
>
>
> Hi Frank,
>
> Sorry about the delay repond.
> I've been going through the logs you attached, although I could not find
> any specific indication why the migration failed because of the disk you
> were mentionning.
> Does this VM run with both disks on the target host without migration?
>
> Regards,
> Maor
>
>
> On Fri, Feb 16, 2018 at 11:03 AM, fsoyer  wrote:
>>
>> Hi Maor,
>> sorry for the double post, I've change the email adress of my account and
>> supposed that I'd need to re-post it.
>> And thank you for your time. Here are the logs. I added a vdisk to an
>> existing VM : it no more migrates, needing to poweroff it after minutes.
>> Then simply deleting the second disk makes migrate it in exactly 9s without
>> problem !
>> https://gist.github.com/fgth/4707446331d201eef574ac31b6e89561
>> https://gist.github.com/fgth/f8de9c22664aee53722af676bff8719d
>>
>> --
>>
>> Cordialement,
>>
>> *Frank Soyer *
>> Le Mercredi, Février 14, 2018 11:04 CET, Maor Lipchuk <
>> mlipc...@redhat.com> a écrit:
>>
>>
>> Hi Frank,
>>
>> I already replied on your last email.
>> Can you provide the VDSM logs from the time of the migration failure for
>> both hosts:
>>   ginger.local.systea.f r and v
>> ictor.local.systea.fr
>>
>> Thanks,
>> Maor
>>
>> On Wed, Feb 14, 2018 at 11:23 AM, fsoyer  wrote:
>>>
>>> Hi all,
>>> I discovered yesterday a problem when migrating VM with more than one
>>> vdisk.
>>> On our test servers (oVirt4.1, shared storage with Gluster), I created 2
>>> VMs needed for a test, from a template with a 20G vdisk. On this VMs I
>>> added a 100G vdisk (for this tests I didn't want to waste time to extend
>>> the existing vdisks... But I lost time finally...). The VMs with the 2
>>> vdisks works well.
>>> Now I saw some updates waiting on the host. I tried to put it in
>>> maintenance... But it stopped on the two VM. They were marked "migrating",
>>> but no more accessible. Other (small) VMs with only 1 vdisk was migrated
>>> without problem at the same time.
>>> I saw that a kvm process for the (big) VMs was launched on the source
>>> AND destination host, but after tens of minutes, the migration and the VMs
>>> was always freezed. I tried to cancel the migration for the VMs : failed.
>>> The only way to stop it was to poweroff the VMs : the kvm process died on
>>> the 2 hosts and the GUI alerted on a failed migration.
>>> In doubt, I tried to delete the second vdisk on one of this VMs : it
>>> migrates then without error ! And no access problem.
>>> I tried to extend the first vdisk of the second VM, the delete the
>>> second vdisk : it migrates now without problem !
>>>
>>> So after another test with a VM with 2 vdisks, I can say that this
>>> blocked the migration process :(
>>>
>>> In engine.log, for a VMs with 1 vdisk migrating well, we see :
>>>
>>> 2018-02-12 16:46:29,705+01 INFO  
>>> [o

Re: [ovirt-users] oVirt 4.2: hostdev passthrough not working any more

[Alexandr Krivulya]

22.02.2018 11:37, Alexandr Krivulya пишет:

22.02.2018 11:30, Martin Polednik пишет:

On 22/02/18 10:40 +0200, Alexandr Krivulya wrote:

Hello, the same problem after upgrade to 4.2.1 :(


18.01.2018 11:53, Daniel Helgenberger пишет:

Hello,

yesterday I upgraded to 4.2.0 from 4.1.8.

Now I notice I cannot assign host dev pass though any more; in the GUI
the 'Pinnded to host' list is empty; I cannot select any host for pass
through host pinning.


Does the host that previously worked report device passthrough
capability? In the UI it's the "Device Passthrough: Enabled" field.
(and similarly named field in vdsm-client getCapabilities call) 

Now "Device Passthrough: Disabled", but usb passthrough works well on 4.1


After enabling intel_iommu usb passthrough works again. But why this 
option needed for usb now?
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Let's get oVirt in Stack Overflow's Open Source Advertising again

[Allon Mureinik]

Hi all,

With Eldan's help, we have an advert for oVirt [1] suggested on Stack
Overflow's traditional Open Source Advertising campaign [2].

Like always, we need the upvotes to get it up there.

Want to see oVirt on Stack Overflow's sidebar again? Hope over and upvote.


-Allon

[1] https://meta.stackoverflow.com/a/363689/2422776
[2] https://meta.stackoverflow.com/q/362773/2422776
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Confused by logical networks

[Paul-Erik Törrönen]

I'm not sure how the logical networks should work and would appreciate 
if someone could shed some light into the matter, I've tried reading the 
documentation¹ but have not become any wiser :-/


For the sake of argument, I have two hosts in the same cluster/DC, They 
both have 2 network devices each (let's call them eth0 and eth1). On 
both hosts the ovirtmgmgt is connected to eth0 and uses the 
10.0.0.0/8-network. Host 1 is 10.0.0.1 and host 2 is 10.0.0.2. All four 
network devices are connected to one switch.


Then I create a logical network, mylogic which should be 192.168.1.0/24, 
which I assign to eth1 on each host, but define only for host 1 an 
ip-address, 192.168.1.1, host 2 has also the network assigned to eth1, 
but withouth an ip address.


Next I create vm1 on host 1, give it a single virtual network connection 
to mylogic, and configure the guest to use 192.168.1.2 with gw 
192.168.1.1. Obviously I can from the guest ping 192.168.1.1 which is 
the host address on the logical network as the guest is running on the 
same hardware where the host ip address is defined.


However, and this is where my confusion lies, if I now create another 
vm, vm2, on host 2, attach its network device to the mylogic network and 
configure it to use 192.168.1.3 with gw 192.168.1.1, I can not ping 
neither 192.168.1.1 nor 192.168.1.2.


My understanding is that vm2 should be able to ping the wm1 as well as 
the gateway address defined on host 1. However this does not seem to be 
the case.


What have I missed here?

TIA,

Poltsi

¹ https://www.ovirt.org/documentation/admin-guide/chap-Logical_Networks/
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] ?==?utf-8?q? VMs with multiple vdisks don't migrate

[fsoyer]

Hi,
Yes, on 2018-02-16 (vdsm logs) I tried with a VM standing on ginger 
(192.168.0.6) migrated (or failed to migrate...) to victor (192.168.0.5), while 
the engine.log in the first mail on 2018-02-12 was for VMs standing on victor, 
migrated (or failed to migrate...) to ginger. Symptoms were exactly the same, 
in both directions, and VMs works like a charm before, and even after 
(migration "killed" by a poweroff of VMs).
Am I the only one experimenting this problem ?


Thanks
--

Cordialement,

Frank Soyer
 

Le Jeudi, Février 22, 2018 00:45 CET, Maor Lipchuk  a 
écrit:
 Hi Frank, Sorry about the delay repond.I've been going through the logs you 
attached, although I could not find any specific indication why the migration 
failed because of the disk you were mentionning.Does this VM run with both 
disks on the target host without migration? Regards,Maor  On Fri, Feb 16, 2018 
at 11:03 AM, fsoyer  wrote:Hi Maor,
sorry for the double post, I've change the email adress of my account and 
supposed that I'd need to re-post it.
And thank you for your time. Here are the logs. I added a vdisk to an existing 
VM : it no more migrates, needing to poweroff it after minutes. Then simply 
deleting the second disk makes migrate it in exactly 9s without problem ! 
https://gist.github.com/fgth/4707446331d201eef574ac31b6e89561
https://gist.github.com/fgth/f8de9c22664aee53722af676bff8719d

--
Cordialement,

Frank Soyer Le Mercredi, Février 14, 2018 11:04 CET, Maor Lipchuk 
 a écrit:
 Hi Frank, I already replied on your last email.Can you provide the VDSM logs 
from the time of the migration failure for both hosts:  ginger.local.systea.fr 
and victor.local.systea.fr Thanks,Maor On Wed, Feb 14, 2018 at 11:23 AM, fsoyer 
 wrote:
Hi all,
I discovered yesterday a problem when migrating VM with more than one vdisk.
On our test servers (oVirt4.1, shared storage with Gluster), I created 2 VMs 
needed for a test, from a template with a 20G vdisk. On this VMs I added a 100G 
vdisk (for this tests I didn't want to waste time to extend the existing 
vdisks... But I lost time finally...). The VMs with the 2 vdisks works well.
Now I saw some updates waiting on the host. I tried to put it in maintenance... 
But it stopped on the two VM. They were marked "migrating", but no more 
accessible. Other (small) VMs with only 1 vdisk was migrated without problem at 
the same time.
I saw that a kvm process for the (big) VMs was launched on the source AND 
destination host, but after tens of minutes, the migration and the VMs was 
always freezed. I tried to cancel the migration for the VMs : failed. The only 
way to stop it was to poweroff the VMs : the kvm process died on the 2 hosts 
and the GUI alerted on a failed migration.
In doubt, I tried to delete the second vdisk on one of this VMs : it migrates 
then without error ! And no access problem.
I tried to extend the first vdisk of the second VM, the delete the second vdisk 
: it migrates now without problem !   

So after another test with a VM with 2 vdisks, I can say that this blocked the 
migration process :(

In engine.log, for a VMs with 1 vdisk migrating well, we see :2018-02-12 
16:46:29,705+01 INFO  [org.ovirt.engine.core.bll.MigrateVmToServerCommand] 
(default task-28) [2f712024-5982-46a8-82c8-fd8293da5725] Lock Acquired to 
object 'EngineLock:{exclusiveLocks='[3f57e669-5e4c-4d10-85cc-d573004a099d=VM]', 
sharedLocks=''}'
2018-02-12 16:46:29,955+01 INFO  
[org.ovirt.engine.core.bll.MigrateVmToServerCommand] 
(org.ovirt.thread.pool-6-thread-32) [2f712024-5982-46a8-82c8-fd8293da5725] 
Running command: MigrateVmToServerCommand internal: false. Entities affected :  
ID: 3f57e669-5e4c-4d10-85cc-d573004a099d Type: VMAction group MIGRATE_VM with 
role type USER
2018-02-12 16:46:30,261+01 INFO  
[org.ovirt.engine.core.vdsbroker.MigrateVDSCommand] 
(org.ovirt.thread.pool-6-thread-32) [2f712024-5982-46a8-82c8-fd8293da5725] 
START, MigrateVDSCommand( MigrateVDSCommandParameters:{runAsync='true', 
hostId='ce3938b1-b23f-4d22-840a-f17d7cd87bb1', 
vmId='3f57e669-5e4c-4d10-85cc-d573004a099d', srcHost='192.168.0.6', 
dstVdsId='d569c2dd-8f30-4878-8aea-858db285cf69', dstHost='192.168.0.5:54321', 
migrationMethod='ONLINE', tunnelMigration='false', migrationDowntime='0', 
autoConverge='true', migrateCompressed='false', consoleAddress='null', 
maxBandwidth='500', enableGuestEvents='true', maxIncomingMigrations='2', 
maxOutgoingMigrations='2', convergenceSchedule='[init=[{name=setDowntime, 
params=[100]}], stalling=[{limit=1, action={name=setDowntime, params=[150]}}, 
{limit=2, action={name=setDowntime, params=[200]}}, {limit=3, 
action={name=setDowntime, params=[300]}}, {limit=4, action={name=setDowntime, 
params=[400]}}, {limit=6, action={name=setDowntime, params=[500]}}, {limit=-1, 
action={name=abort, params=[]}}]]'}), log id: 14f61ee0
2018-02-12 16:46:30,262+01 INFO  
[org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateBrokerVDSCommand] 
(org.ovirt.thread.pool-6-thread-32) [2f712024-5982-46a8-82c8-fd82

Re: [ovirt-users] problem importing ova vm

[Arik Hadas]

On Thu, Feb 22, 2018 at 3:26 PM, Jiří Sléžka  wrote:

> On 02/22/2018 01:58 PM, Richard W.M. Jones wrote:
> > On Thu, Feb 22, 2018 at 01:27:18PM +0100, Jiří Sléžka wrote:
> >> libvirt needs authentication to connect to libvirt URI qemu:///system
> >> (see also: http://libvirt.org/auth.html http://libvirt.org/uri.html)
> >
> > You can set the backend to direct to avoid needing libvirt:
> >
> >   export LIBGUESTFS_BACKEND=direct
> >
> > Alternately you can fiddle with the libvirt polkit configuration
> > to permit access:
>
> thanks, here is full output
>
> http://mirror.slu.cz/tmp/libguestfs-test-tool.txt
>
> Jiri
>

Thanks, there is apparently something wrong with that particular host of
mine - not worth spending the time on investigating it.

Jiri, your test seems to past,
could you try invoking the import again with the latest proposed changes to
the OVF configuration (adding ovf:size to the File element and removing the
USB item) and update us?


>
> >
> >   https://libvirt.org/aclpolkit.html
> >
> > Rich.
> >
>
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] problem importing ova vm

[Jiří Sléžka]

On 02/22/2018 01:58 PM, Richard W.M. Jones wrote:
> On Thu, Feb 22, 2018 at 01:27:18PM +0100, Jiří Sléžka wrote:
>> libvirt needs authentication to connect to libvirt URI qemu:///system
>> (see also: http://libvirt.org/auth.html http://libvirt.org/uri.html)
> 
> You can set the backend to direct to avoid needing libvirt:
> 
>   export LIBGUESTFS_BACKEND=direct
> 
> Alternately you can fiddle with the libvirt polkit configuration
> to permit access:

thanks, here is full output

http://mirror.slu.cz/tmp/libguestfs-test-tool.txt

Jiri

> 
>   https://libvirt.org/aclpolkit.html
> 
> Rich.
> 




smime.p7s
Description: S/MIME Cryptographic Signature
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Unable to add Hosts to Cluster

[Mark Steele]

We have found a resolution to this issue which is a bit convoluted - and
still does not explain why this started in the first place. Once we have
prepped a HV server to be added (all the NIC's are ready, selinux,
networkmanager, firewalld, etc have been disabled, we have to do the
following:

yum install librbd1
rm /etc/yum.repos.d/CentOS-Base.repo (yes... delete the base repo...)
vi /etc/yum.repos.d/CentOS-Vault.repo
add the following:
 [vault]
 name=CentOS-$releasever - Extras
 
#mirrorlist=http://vault.centos.org/?release=$releasever&arch=$basearch&repo=extras
 baseurl=http://vault.centos.org/centos/7.0.1406/os/x86_64/
 gpgcheck=0
 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7

vi /etc/yum.repos.d/ovirt-3.5-dependencies.repo
 edit baseurls as show below:
 [ovirt-3.5-glusterfs-epel]
 name=GlusterFS is a clustered file-system capable of scaling to
several petabytes.
 
baseurl=https://download.gluster.org/pub/gluster/glusterfs/old-releases/3.6/3.6.1/RHEL/epel-7/x86_64
 enabled=1
 skip_if_unavailable=1
 gpgcheck=0
 [ovirt-3.5-glusterfs-noarch-epel]
 name=GlusterFS is a clustered file-system capable of scaling to
several petabytes.
 
baseurl=http://download.gluster.org/pub/gluster/glusterfs/old-releases/3.6/3.6.1/RHEL/epel-7/noarch
 
#baseurl=http://download.gluster.org/pub/gluster/glusterfs/LATEST/EPEL.repo/epel-$releasever/noarch
 enabled=1
 skip_if_unavailable=1
 gpgcheck=0

yum remove ovirt-release35
yum remove vdsm
yum remove libvirt

yum install ovirt-release35-002-1
yum install libvirt-1.1.1-29.el7
yum install vdsm-4.16.7-1.gitdb83943.el7

We can then successfully add the HV into the cluster.

This is using CentOS 7.0.1406 (Core) as the host OS and oVirt 3.5.0.1-1.el6

If anyone has any questions please feel free to ask.


***
*Mark Steele*
CIO / VP Technical Operations | TelVue Corporation
TelVue - We Share Your Vision
16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054
800.885.8886 x128 | mste...@telvue.com | http://www.telvue.com
twitter: http://twitter.com/telvue | facebook:
https://www.facebook.com/telvue

On Tue, Feb 20, 2018 at 11:24 AM, Yaniv Kaul  wrote:

>
>
> On Tue, Feb 20, 2018 at 12:52 PM, Mark Steele  wrote:
>
>> ​Is it possible that the HostedEngine became corrupted somehow and that
>> is preventing us from adding hosts?
>>
>
> I doubt that.
> I still suspect the libvirt auth. issue.
> Nevertheless, as commented more than once, you are running on somewhat old
> version with a recent CentOS version. Not sure this combination is tested
> or anyone's running it.
>
>
>>
>> Is creating a new hosted engine an option?
>>
>
> You could backup and restore to a new HE.
> Y.
>
>
>>
>>
>> ***
>> *Mark Steele*
>> CIO / VP Technical Operations | TelVue Corporation
>> TelVue - We Share Your Vision
>> 16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054
>> 
>> 800.885.8886 x128 <(800)%20885-8886> | mste...@telvue.com | http://
>> www.telvue.com
>> twitter: http://twitter.com/telvue | facebook: https://www.facebook
>> .com/telvue
>>
>> On Mon, Feb 19, 2018 at 9:55 AM, Mark Steele  wrote:
>>
>>> At this point I'm wondering if there is anyone in the community that
>>> freelances and would be willing to provide remote support to resolve this
>>> issue?
>>>
>>> We are running with 1/2 our normal hosts, and not being able to add
>>> anymore back into the cluster is a serious problem.
>>>
>>> Best regards,
>>>
>>>
>>> ***
>>> *Mark Steele*
>>> CIO / VP Technical Operations | TelVue Corporation
>>> TelVue - We Share Your Vision
>>> 16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054
>>> 
>>> 800.885.8886 x128 <(800)%20885-8886> | mste...@telvue.com | http://
>>> www.telvue.com
>>> twitter: http://twitter.com/telvue | facebook: https://www.facebook
>>> .com/telvue
>>>
>>> On Sat, Feb 17, 2018 at 12:53 PM, Mark Steele 
>>> wrote:
>>>
 Yaniv,

 I have one of my developers assisting me and we are continuing to run
 into issues. This is a note from him:

 Hi, I'm trying to add a host to ovirt, but I'm running into package
 dependency problems. I have existing hosts that are working and integrated
 properly, and inspecting those, I am able to match the packages between the
 new host and the existing, but when I then try to add the new host to
 ovirt, it fails on reinstall because it's trying to install packages that
 are later versions. does the installation run list from ovirt-release35
 002-1 have unspecified versions? The working hosts use libvirt-1.1.1-29,
 and vdsm-4.16.7, but it's trying to install vdsm-4.16.30, which requires a
 higher version of libvirt, at which point, the installation fails. is there
 some way I can specify which package versions the ovirt install procedure
 uses? or better yet, skip the package management step entirel

Re: [ovirt-users] problem importing ova vm

[Richard W.M. Jones]

On Thu, Feb 22, 2018 at 01:27:18PM +0100, Jiří Sléžka wrote:
> libvirt needs authentication to connect to libvirt URI qemu:///system
> (see also: http://libvirt.org/auth.html http://libvirt.org/uri.html)

You can set the backend to direct to avoid needing libvirt:

  export LIBGUESTFS_BACKEND=direct

Alternately you can fiddle with the libvirt polkit configuration
to permit access:

  https://libvirt.org/aclpolkit.html

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-p2v converts physical machines to virtual machines.  Boot with a
live CD or over the network (PXE) and turn machines into KVM guests.
http://libguestfs.org/virt-v2v
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] problem importing ova vm

[Jiří Sléžka]

On 02/22/2018 11:22 AM, Richard W.M. Jones wrote:
> On Thu, Feb 22, 2018 at 12:09:56PM +0200, Arik Hadas wrote:
>> supermin: failed to find a suitable kernel (host_cpu=x86_64).
> 
> Please run ‘libguestfs-test-tool’ and attach the complete output.

libguestfs-test-tool
 
 *IMPORTANT NOTICE
 *
 * When reporting bugs, include the COMPLETE, UNEDITED
 * output below in your bug report.
 *
 
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin
XDG_RUNTIME_DIR=/run/user/0
SELinux: Enforcing
guestfs_get_append: (null)
guestfs_get_autosync: 1
guestfs_get_backend: libvirt
guestfs_get_backend_settings: []
guestfs_get_cachedir: /var/tmp
guestfs_get_direct: 0
guestfs_get_hv: /usr/libexec/qemu-kvm
guestfs_get_memsize: 500
guestfs_get_network: 0
guestfs_get_path: /usr/lib64/guestfs
guestfs_get_pgroup: 0
guestfs_get_program: libguestfs-test-tool
guestfs_get_recovery_proc: 1
guestfs_get_smp: 1
guestfs_get_sockdir: /tmp
guestfs_get_tmpdir: /tmp
guestfs_get_trace: 0
guestfs_get_verbose: 1
host_cpu: x86_64
Launching appliance, timeout set to 600 seconds.
libguestfs: launch: program=libguestfs-test-tool
libguestfs: launch: version=1.36.3rhel=7,release=6.el7_4.3,libvirt
libguestfs: launch: backend registered: unix
libguestfs: launch: backend registered: uml
libguestfs: launch: backend registered: libvirt
libguestfs: launch: backend registered: direct
libguestfs: launch: backend=libvirt
libguestfs: launch: tmpdir=/tmp/libguestfsmsimNR
libguestfs: launch: umask=0022
libguestfs: launch: euid=0
libguestfs: libvirt version = 3002000 (3.2.0)
libguestfs: guest random name = guestfs-ii13o2gd48kt6mrz
libguestfs: connect to libvirt
libguestfs: opening libvirt handle: URI = qemu:///system, auth =
default+wrapper, flags = 0
libvirt needs authentication to connect to libvirt URI qemu:///system
(see also: http://libvirt.org/auth.html http://libvirt.org/uri.html)

(not sure if you need information after authentication (and I am not
sure which credentials it needs))

> 
>> @Richard, this is an OVA of a VM installed with Debian64 as guest OS that


>> was exported from VirtualBox, is it supported by virt-v2v?
> 
> No, we only support OVAs exported from VMware.  OVF isn't a
> real standard, it's a ploy by VMware to pretend that they
> conform to standards.

:-)

maybe supporting import from VirtualBox is the way to lowering VmWare
importance :-)

Cheers, Jiri




smime.p7s
Description: S/MIME Cryptographic Signature
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] problem importing ova vm

[Richard W.M. Jones]

On Thu, Feb 22, 2018 at 12:09:56PM +0200, Arik Hadas wrote:
> supermin: failed to find a suitable kernel (host_cpu=x86_64).

Please run ‘libguestfs-test-tool’ and attach the complete output.

> @Richard, this is an OVA of a VM installed with Debian64 as guest OS that
> was exported from VirtualBox, is it supported by virt-v2v?

No, we only support OVAs exported from VMware.  OVF isn't a
real standard, it's a ploy by VMware to pretend that they
conform to standards.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-builder quickly builds VMs from scratch
http://libguestfs.org/virt-builder.1.html
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Ovirt Cluster Setup

[Sakhi Hadebe]

Hi,

I restarted everything from scratch and followed this article
http://blogs-ramesh.blogspot.co.za/2016/01/ovirt-and-gluster-hyperconvergence.html
.

Thanks for your quick response Kasturi and Sahina

On Wed, Feb 21, 2018 at 8:54 AM, Kasturi Narra  wrote:

> Hello sakhi,
>
>   Can you please let us know what is the script it is failing
> at ?
>
> Thanks
> kasturi
>
> On Tue, Feb 20, 2018 at 1:05 PM, Sakhi Hadebe  wrote:
>
>> I have 3 Dell R515 servers all installed with centOS 7, and trying to
>> setup an oVirt Cluster.
>>
>> Disks configurations:
>> 2 x 1TB - Raid1 - OS Deployment
>> 6 x 1TB - Raid 6 - Storage
>>
>> ​Memory is 128GB
>>
>> I am following this documentation https://www.ovir
>> t.org/blog/2017/04/up-and-running-with-ovirt-4.1-and-gluster-storage/
>> and I am getting the issue below:
>>
>> PLAY [gluster_servers] **
>> ***
>>
>> TASK [Run a shell script] **
>> 
>> fatal: [ovirt2.sanren.ac.za]: FAILED! => {"msg": "The conditional check
>> 'result.rc != 0' failed. The error was: error while evaluating conditional
>> (result.rc != 0): 'dict object' has no attribute 'rc'"}
>> fatal: [ovirt3.sanren.ac.za]: FAILED! => {"msg": "The conditional check
>> 'result.rc != 0' failed. The error was: error while evaluating conditional
>> (result.rc != 0): 'dict object' has no attribute 'rc'"}
>> fatal: [ovirt1.sanren.ac.za]: FAILED! => {"msg": "The conditional check
>> 'result.rc != 0' failed. The error was: error while evaluating conditional
>> (result.rc != 0): 'dict object' has no attribute 'rc'"}
>> to retry, use: --limit @/tmp/tmpxFXyGG/run-script.retry
>>
>> PLAY RECAP 
>> *
>> ovirt1.sanren.ac.za: ok=0changed=0unreachable=0
>> failed=1
>> ovirt2.sanren.ac.za: ok=0changed=0unreachable=0
>> failed=1
>> ovirt3.sanren.ac.za: ok=0changed=0unreachable=0
>> failed=1
>>
>> *Error: Ansible(>= 2.2) is not installed.*
>> *Some of the features might not work if not installed.*
>>
>>
>> ​I have installed ansible2.4 in all the servers, but the error persists.
>>
>> Is there anything I can do to get rid of this error?
>> --
>> Regards,
>> Sakhi Hadebe
>>
>> Engineer: South African National Research Network (SANReN)Competency Area, 
>> Meraka, CSIR
>>
>> Tel:   +27 12 841 2308 <+27128414213>
>> Fax:   +27 12 841 4223 <+27128414223>
>> Cell:  +27 71 331 9622 <+27823034657>
>> Email: sa...@sanren.ac.za 
>>
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>


-- 
Regards,
Sakhi Hadebe

Engineer: South African National Research Network (SANReN)Competency
Area, Meraka, CSIR

Tel:   +27 12 841 2308 <+27128414213>
Fax:   +27 12 841 4223 <+27128414223>
Cell:  +27 71 331 9622 <+27823034657>
Email: sa...@sanren.ac.za 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] problem importing ova vm

[Arik Hadas]

So I have some good news and some bad news.

The good news is that I just used the provided OVA and identified the
issues that prevent oVirt from processing its OVF configuration:
1. The  element in the References section lacks ovf:size attribute
and oVirt unfortunately, is not prepared for this.
2. The USB item doesn't include an oVirt-specific attribute (makes sense..)
that oVirt require (that doesn't make sense..) called usbPolicy.

I'll post fixes for those issues.
In the meantime, the OVF can be modified with the following changes:
1. Add ovf:size="3221225472" to the File element (there's no need for more
than 3gb, even 2gb should be enough).
2. Remove the following Item:



  0

  usb

  USB Controller

  usb

  6

  23



The bad news is that the conversion that would finally start with those
changes then fails on my host (with virt-v2v v1.36.3) with the following
error:

supermin: failed to find a suitable kernel (host_cpu=x86_64).


I looked for kernels in /boot and modules in /lib/modules.


If this is a Xen guest, and you only have Xen domU kernels

installed, try installing a fullvirt kernel (only for

supermin use, you shouldn't boot the Xen guest with it).

libguestfs: trace: v2v: launch = -1 (error)


@Richard, this is an OVA of a VM installed with Debian64 as guest OS that
was exported from VirtualBox, is it supported by virt-v2v?

On Wed, Feb 21, 2018 at 7:10 PM, Jiří Sléžka  wrote:

> On 02/21/2018 05:35 PM, Arik Hadas wrote:
> >
> >
> > On Wed, Feb 21, 2018 at 6:03 PM, Jiří Sléžka  > > wrote:
> >
> > On 02/21/2018 03:43 PM, Jiří Sléžka wrote:
> > > On 02/20/2018 11:09 PM, Arik Hadas wrote:
> > >>
> > >>
> > >> On Tue, Feb 20, 2018 at 6:37 PM, Jiří Sléžka  > 
> > >> >> wrote:
> > >>
> > >> On 02/20/2018 03:48 PM, Arik Hadas wrote:
> > >> >
> > >> >
> > >> > On Tue, Feb 20, 2018 at 3:49 PM, Jiří Sléžka
> > mailto:jiri.sle...@slu.cz>
> > >
> > >> > 
> >  > >> >
> > >> > Hi Arik,
> > >> >
> > >> > On 02/20/2018 01:22 PM, Arik Hadas wrote:
> > >> > >
> > >> > >
> > >> > > On Tue, Feb 20, 2018 at 2:03 PM, Jiří Sléžka
> > mailto:jiri.sle...@slu.cz>
> > >
> > >> 
> > >>
> > >> > >  >   > >
> > >> 
> >  wrote:
> > >> > >
> > >> > > Hi,
> > >> > >
> > >> > >
> > >> > > Hi Jiří,
> > >> > >
> > >> > >
> > >> > >
> > >> > > I would like to try import some ova files into
> > our oVirt
> > >> instance [1]
> > >> > > [2] but I facing problems.
> > >> > >
> > >> > > I have downloaded all ova images into one of hosts
> > >> (ovirt01) into
> > >> > > direcory /ova
> > >> > >
> > >> > > ll /ova/
> > >> > > total 6532872
> > >> > > -rw-r--r--. 1 vdsm kvm 1160387072 Feb 16 16:21
> > >> HAAS-hpcowrie.ovf
> > >> > > -rw-r--r--. 1 vdsm kvm 785984 Feb 16 16:22
> > >> HAAS-hpdio.ova
> > >> > > -rw-r--r--. 1 vdsm kvm  846736896 Feb 16 16:22
> > >> HAAS-hpjdwpd.ova
> > >> > > -rw-r--r--. 1 vdsm kvm  891043328 Feb 16 16:23
> > >> HAAS-hptelnetd.ova
> > >> > > -rw-r--r--. 1 vdsm kvm  908222464 Feb 16 16:23
> > >> HAAS-hpuchotcp.ova
> > >> > > -rw-r--r--. 1 vdsm kvm  880643072 Feb 16 16:24
> > >> HAAS-hpuchoudp.ova
> > >> > > -rw-r--r--. 1 vdsm kvm  890833920 Feb 16 16:24
> > >> HAAS-hpuchoweb.ova
> > >> > >
> > >> > > Then I tried to import them - from host ovirt01
> and
> > >> directory /ova but
> > >> > > spinner spins infinitly and nothing is happen.
> > >> > >
> > >> > >
> > >> > > And does it work when you provide a path to the
> > actual ova
> > >> file, i.e.,
> > >> > > /ova/HAAS-hpdio.ova, rather than to the directory?
> > >> >
> > >> > this time it ends with "Failed to load VM configuration
> > from
> > >> 

Re: [ovirt-users] Network and VLANs

[Gabriel Stein]

s/ wrote this Bug about my Problem/There is a Bug with my Problem"/g



Gabriel Stein
--
Gabriel Ferraz Stein
Tel.: +49 (0)  170 2881531

2018-02-22 10:50 GMT+01:00 Gabriel Stein :

> Hi all,
>
> I have some problems adding VLANs to my VMs and  I don't known if there is
> a better way to do that, like a 'oVirt Way'.
>
> All I need is to have a VM on "Test Network" that communicates with
> another hardware/VMs on "Test Network". All VLANs are configured on my
> Switch, the Hosts from oVirt are connected and tagged to this VLANs.
>
> Is there a "oVirt Way" to do that other than "Setup Networks"? Can I use
> with oVirt an Virtual Switch? Or a Network Stack?
>
> I wrote this Bug about my Problem...
>
> Bug: https://bugzilla.redhat.com/show_bug.cgi?id=1540463
>
> Thanks in Advance!
>
> Best Regards,
>
> Gabriel
>
>
>
> Gabriel Stein
> --
> Gabriel Ferraz Stein
> Tel.: +49 (0)  170 2881531
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Network and VLANs

[Gabriel Stein]

Hi all,

I have some problems adding VLANs to my VMs and  I don't known if there is
a better way to do that, like a 'oVirt Way'.

All I need is to have a VM on "Test Network" that communicates with another
hardware/VMs on "Test Network". All VLANs are configured on my Switch, the
Hosts from oVirt are connected and tagged to this VLANs.

Is there a "oVirt Way" to do that other than "Setup Networks"? Can I use
with oVirt an Virtual Switch? Or a Network Stack?

I wrote this Bug about my Problem...

Bug: https://bugzilla.redhat.com/show_bug.cgi?id=1540463

Thanks in Advance!

Best Regards,

Gabriel



Gabriel Stein
--
Gabriel Ferraz Stein
Tel.: +49 (0)  170 2881531
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] oVirt 4.2: hostdev passthrough not working any more

[Alexandr Krivulya]

22.02.2018 11:30, Martin Polednik пишет:

On 22/02/18 10:40 +0200, Alexandr Krivulya wrote:

Hello, the same problem after upgrade to 4.2.1 :(


18.01.2018 11:53, Daniel Helgenberger пишет:

Hello,

yesterday I upgraded to 4.2.0 from 4.1.8.

Now I notice I cannot assign host dev pass though any more; in the GUI
the 'Pinnded to host' list is empty; I cannot select any host for pass
through host pinning.


Does the host that previously worked report device passthrough
capability? In the UI it's the "Device Passthrough: Enabled" field.
(and similarly named field in vdsm-client getCapabilities call) 

Now "Device Passthrough: Disabled", but usb passthrough works well on 4.1
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Manageiq ovn

[Mor Kalfon]

On Wed, Feb 21, 2018 at 6:17 PM, Alona Kaplan  wrote:

> Hi Alexy.
>
> First of all, please reply to users@ovirt.org list, so all our users can
> enjoy the discussion.
>
> To summarize, currently you have two questions.
>
> 1. How to automatically trigger the provider refresh after doing changes
> to the provider?
>
> There is an open RFE regrading it - https://bugzilla.redhat.com/1547415,
> you can add yourself to its CC list to track it.
>
> 2. Adding a router with external gateway is not working since an ip
> address is expected in external_fixed_ips by the ovn provider but manageiq
> doesn't provide it.
> Looking at the neutron api (https://developer.openstack.
> org/api-ref/network/v2/#create-router) seems the ip address is mandatory.
> So it is a manageiq bug (also tried to add a router with an external
> gateway with no ip address directly to neutron and got an error).
>
> As a workaround to the bug, you can add the router to the ovn-provider
> directly using the api - https://gist.github.com/dominikholler/
> f58658407ae7620280f4cb47c398d849
>
> Mor, can you please open a bug regarding the issue?
>
> ​Sure, I opened two bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1547878
https://bugzilla.redhat.com/show_bug.cgi?id=1547872

On Tue, Feb 20, 2018 at 12:32 PM, Aliaksei Nazarenka <
> aliaksei.nazare...@gmail.com> wrote:
>
>> Hi, Alona!
>> Can you help ve with add external ip for creating router procedure?
>>
>> 2018-02-19 14:52 GMT+03:00 Aliaksei Nazarenka <
>> aliaksei.nazare...@gmail.com>:
>>
>>> I do not really understand the essence of how this will work, you
>>> specify the router 10.0.0.2, while on dhcp will be distributed ip gateway
>>> 10.0.0.1? It seems to me that in the role of geystwey just had to act as a
>>> router, or am I wrong?
>>>
>>> 2018-02-19 14:46 GMT+03:00 Aliaksei Nazarenka <
>>> aliaksei.nazare...@gmail.com>:
>>>
 Dominik sent me this link here -  https://gist.github.com/domini
 kholler/f58658407ae7620280f4cb47c398d849

 2018-02-19 14:45 GMT+03:00 Aliaksei Nazarenka <
 aliaksei.nazare...@gmail.com>:

> Hi, Alona!
> Dominik said that you can help. I need to create an external gateway
> in manageiq, I did not find a native way to do this. As a result of lack 
> of
> ip address, I can not create a router. Here are the logs:
>
> 2018-02-19 14:22:16,942 root Starting server
> 2018-02-19 14:22:16,943 root Version: 1.2.5-1
> 2018-02-19 14:22:16,943 root Build date: 20180117090014
> 2018-02-19 14:22:16,944 root Githash: 12b705d
> 2018-02-19 14:23:17,250 root From: 10.0.184.20:57674 Request: POST
> /v2.0/tokens
> 2018-02-19 14:23:17,252 root Request body:
> {"auth": {"tenantName": "tenant", "passwordCredentials": {"username":
> "admin@internal", "password": ""}}}
> 2018-02-19 14:23:17,322 requests.packages.urllib3.connectionpool
> Starting new HTTPS connection (1): lbn-r-engine-01.mp.local
> 2018-02-19 14:23:17,322 requests.packages.urllib3.connectionpool
> Starting new HTTPS connection (1): lbn-r-engine-01.mp.local
> 2018-02-19 14:23:17,836 requests.packages.urllib3.connectionpool
> Starting new HTTPS connection (1): lbn-r-engine-01.mp.local
> 2018-02-19 14:23:17,836 requests.packages.urllib3.connectionpool
> Starting new HTTPS connection (1): lbn-r-engine-01.mp.local
> 2018-02-19 14:23:17,870 root Response code: 200
> 2018-02-19 14:23:17,870 root Response body: {"access": {"token":
> {"expires": "2018-02-23T15:23:17Z", "id": "lmceG8s1SROKskN-H4T93IPwgwSFb
> 8mN7UJ6qz4HObrC2PqNWcSyS_dZGIcax6dEBVIz8H6ShgDXl_2fvflbeg"},
> "serviceCatalog": [{"endpoints_links": [], "endpoints": [{"adminURL": "
> https://lbn-r-engine-01.mp.local:9696/";, "region": "RegionOne", "id":
> "0001", "internalURL": "
> https://lbn-r-engine-01.mp.local:9696/";, "publicURL": "
> https://lbn-r-engine-01.mp.local:9696/"}], "type": "network", "name":
> "neutron"}, {"endpoints_links": [], "endpoints": [{"adminURL": "
> https://lbn-r-engine-01.mp.local:35357/";, "region": "RegionOne",
> "publicURL": "https://lbn-r-engine-01.mp.local:35357/";,
> "internalURL": "https://lbn-r-engine-01.mp.local:35357/";, "id":
> "0002"}], "type": "identity", "name":
> "keystone"}, {"endpoints_links": [], "endpoints": [{"adminURL": "
> https://lbn-r-engine-01.mp.local:8774/v2.1/";, "region": "RegionOne",
> "publicURL": "https://lbn-r-engine-01.mp.local:8774/v2.1/";,
> "internalURL": "https://lbn-r-engine-01.mp.local:8774/v2.1/";, "id":
> "0002"}], "type": "compute", "name":
> "nova"}], "user": {"username": "admin", "roles_links": [], "id": "",
> "roles": [{"name": "admin"}], "name": "admin"}}}
> 2018-02-19 14:23:17,974 root From: 10.0.184.20:43600 Request: POST
> /v2.0/routers
> 2018-02-19 14:23:17,974 root Request body:
> {"router":{"name":"t

Re: [ovirt-users] oVirt 4.2: hostdev passthrough not working any more

[Martin Polednik]

On 22/02/18 10:40 +0200, Alexandr Krivulya wrote:

Hello, the same problem after upgrade to 4.2.1 :(


18.01.2018 11:53, Daniel Helgenberger пишет:

Hello,

yesterday I upgraded to 4.2.0 from 4.1.8.

Now I notice I cannot assign host dev pass though any more; in the GUI
the 'Pinnded to host' list is empty; I cannot select any host for pass
through host pinning.


Does the host that previously worked report device passthrough
capability? In the UI it's the "Device Passthrough: Enabled" field.
(and similarly named field in vdsm-client getCapabilities call)


When I was creating the particular VM in 4.1 it was working as expected.

The hostdev from before the upgrades are still present. I tried to
remove them and got an NPE (see below).

As a workaround, is the old hostusb[1] method I know back from 3.x still 
working in the 4.x
line?

AFAICT IOMMU is working


dmesg | grep -e DMAR -e IOMMU
[0.00] ACPI: DMAR 7b7e7000 002C6 (v01 HP ProLiant 0001 
HP   0001)
[0.168032] DMAR: Host address width 46
[0.168034] DMAR: DRHD base: 0x00fbffc000 flags: 0x0
[0.168047] DMAR: dmar0: reg_base_addr fbffc000 ver 1:0 cap 8d2078c106f0466 
ecap f020de
[0.168050] DMAR: DRHD base: 0x00c7ffc000 flags: 0x1
[0.168061] DMAR: dmar1: reg_base_addr c7ffc000 ver 1:0 cap 8d2078c106f0466 
ecap f020de
[0.168063] DMAR: RMRR base: 0x0079174000 end: 0x0079176fff
[0.168065] DMAR: RMRR base: 0x00791f4000 end: 0x00791f7fff
[0.168067] DMAR: RMRR base: 0x00791de000 end: 0x00791f3fff
[0.168070] DMAR: RMRR base: 0x00791cb000 end: 0x00791dbfff
[0.168071] DMAR: RMRR base: 0x00791dc000 end: 0x00791ddfff
[0.168073] DMAR: ATSR flags: 0x0
[0.168075] DMAR: ATSR flags: 0x0
[0.168079] DMAR-IR: IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
[0.168082] DMAR-IR: IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
[0.168084] DMAR-IR: IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
[0.168086] DMAR-IR: HPET id 0 under DRHD base 0xc7ffc000
[0.168088] DMAR-IR: Queued invalidation will be enabled to support x2apic 
and Intr-remapping.
[0.169073] DMAR-IR: Enabled IRQ remapping in x2apic mode

Thanks,

[1] https://www.ovirt.org/develop/release-management/features/virt/hostusb/


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

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

Re: [ovirt-users] oVirt 4.2: hostdev passthrough not working any more

[Alexandr Krivulya]

Hello, the same problem after upgrade to 4.2.1 :(


18.01.2018 11:53, Daniel Helgenberger пишет:

Hello,

yesterday I upgraded to 4.2.0 from 4.1.8.

Now I notice I cannot assign host dev pass though any more; in the GUI
the 'Pinnded to host' list is empty; I cannot select any host for pass
through host pinning.

When I was creating the particular VM in 4.1 it was working as expected.

The hostdev from before the upgrades are still present. I tried to
remove them and got an NPE (see below).

As a workaround, is the old hostusb[1] method I know back from 3.x still 
working in the 4.x
line?

AFAICT IOMMU is working


dmesg | grep -e DMAR -e IOMMU
[0.00] ACPI: DMAR 7b7e7000 002C6 (v01 HP ProLiant 0001 
HP   0001)
[0.168032] DMAR: Host address width 46
[0.168034] DMAR: DRHD base: 0x00fbffc000 flags: 0x0
[0.168047] DMAR: dmar0: reg_base_addr fbffc000 ver 1:0 cap 8d2078c106f0466 
ecap f020de
[0.168050] DMAR: DRHD base: 0x00c7ffc000 flags: 0x1
[0.168061] DMAR: dmar1: reg_base_addr c7ffc000 ver 1:0 cap 8d2078c106f0466 
ecap f020de
[0.168063] DMAR: RMRR base: 0x0079174000 end: 0x0079176fff
[0.168065] DMAR: RMRR base: 0x00791f4000 end: 0x00791f7fff
[0.168067] DMAR: RMRR base: 0x00791de000 end: 0x00791f3fff
[0.168070] DMAR: RMRR base: 0x00791cb000 end: 0x00791dbfff
[0.168071] DMAR: RMRR base: 0x00791dc000 end: 0x00791ddfff
[0.168073] DMAR: ATSR flags: 0x0
[0.168075] DMAR: ATSR flags: 0x0
[0.168079] DMAR-IR: IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
[0.168082] DMAR-IR: IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
[0.168084] DMAR-IR: IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
[0.168086] DMAR-IR: HPET id 0 under DRHD base 0xc7ffc000
[0.168088] DMAR-IR: Queued invalidation will be enabled to support x2apic 
and Intr-remapping.
[0.169073] DMAR-IR: Enabled IRQ remapping in x2apic mode

Thanks,

[1] https://www.ovirt.org/develop/release-management/features/virt/hostusb/


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