Re: [ovirt-users] Passing VLAN trunk to VM

[Rogério Ceni Coelho]

Hi,

Ovirt user interface does not allow to input 4095 as a tag vlan number ...
Only values between 0 and 4094.

This is useful to me too. Maybe any other way ?

Em qui, 9 de mar de 2017 às 16:15, FERNANDO FREDIANI <
fernando.fredi...@upx.com> escreveu:

> Have you tried use Vlan 4095 ? On VMware it used to be the way to pass all
> Vlans from a vSwitch to a Vlan in a single port. And yes I have used it
> also for pfSense.
>
> Fernando
>
> On 09/03/2017 16:09, Simon Vincent wrote:
>
> Is it possible to pass multiple VLANs to a VM (pfSense) using a single
> virtual NIC? All my existing oVirt networks are setup as a single tagged
> VLAN. I know this didn't used to be supported but wondered if this has
> changed. My other option is to pass each VLAN as a separate NIC to the VM
> however if I needed to add a new VLAN I would have to add a new interface
> and reboot the VM as hot-add of NICs is not supported by pfSense.
>
>
>
>
> ___
> Users mailing listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users
>
>
> ___
> 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] Passing VLAN trunk to VM

[FERNANDO FREDIANI]

Have you tried use Vlan 4095 ? On VMware it used to be the way to pass 
all Vlans from a vSwitch to a Vlan in a single port. And yes I have used 
it also for pfSense.


Fernando


On 09/03/2017 16:09, Simon Vincent wrote:
Is it possible to pass multiple VLANs to a VM (pfSense) using a single 
virtual NIC? All my existing oVirt networks are setup as a single 
tagged VLAN. I know this didn't used to be supported but wondered if 
this has changed. My other option is to pass each VLAN as a separate 
NIC to the VM however if I needed to add a new VLAN I would have to 
add a new interface and reboot the VM as hot-add of NICs is not 
supported by pfSense.





___
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] Passing VLAN trunk to VM

[Simon Vincent]

Is it possible to pass multiple VLANs to a VM (pfSense) using a single
virtual NIC? All my existing oVirt networks are setup as a single tagged
VLAN. I know this didn't used to be supported but wondered if this has
changed. My other option is to pass each VLAN as a separate NIC to the VM
however if I needed to add a new VLAN I would have to add a new interface
and reboot the VM as hot-add of NICs is not supported by pfSense.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] HE vm fails to migrate due to host CPU incompatibility even after changing cluster CPU type

[Stefano Stagnaro]

On mer, 2017-03-08 at 13:58 +0100, Simone Tiraboschi wrote:
> 
> 
> On Wed, Mar 8, 2017 at 1:02 PM, Sandro Bonazzola  wrote:
> 
> 
> On Sat, Mar 4, 2017 at 12:04 PM, Stefano Stagnaro 
>  wrote:
> Hi guys,
> 
> I've started an oVirt 4.1 HE deployment on a Broadwell based 
> server. Then I added to HE a second, older host based on Nehalem. I've 
> downgraded the cluster CPU type to Nehalem to accommodate host2 and it 
> finally reached score 3400. However, when I try to migrate HE vm it fails 
> with the following error:
> 
> 2017-03-03 20:19:51,814 ERROR (migsrc/b0d38435) [virt.vm] 
> (vmId='b0d38435-5774-4ca9-ad24-70b57b5bc25d') unsupported configuration: 
> guest and host CPU are not compatible: Host CPU does not provide required 
> features: pclmuldq, fma, pcid, x2apic, movbe, tsc-deadline, aes, xsave, avx, 
> fsgsbase, bmi1, hle, avx2, smep, bmi2, erms, invpcid, rtm, rdseed, adx, smap, 
> 3dnowprefetch; try using 'Broadwell-noTSX' CPU model (migration:265)
> 
> I believe the problem is in the HE vm XML where the cpu is 
> still configured as Broadwell. how can I change this specific setting without 
> losing the deployment? Please find all the relevant logs at the following 
> link: https://www.dropbox.com/sh/njl9aofhdw10ses/AADf2Ql4GKVIKcbgLivbmjC2a
> 
> Besides that, I believe this is a wrong behavior because HE 
> should follow cluster properties (otherwise do not reach score 3400); do you 
> believe is it worth opening a issue on bugzilla?
> 
> 
> I would consider opening a BZ to track this. Adding some people who 
> may have some insight on the issue.
> 
> 
> The definition for the engine VM is getting extracted by ovirt-ha-agent from 
> the OVF_STORE volume, not sure why the engine doesn't update it when you 
> change cluster properties. I think it's work to fill a bug.
> Stefano, did you tried simply changing the number of cores for the engine VM 
> from the engine to force a configuration update?
> 
> 
> 
> 
> 
> 
>  
> 
> Thank you,
> Stefano.
> 
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
> 
> 
> 
> 
> -- 
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community 
> collaboration.
> See how it works at redhat.com
> 
> 

Hi Simone,

I tried to change the number of cores and, after a reboot, the cpu model has 
changed to Nehalem. The HostedEngine vm is now migrating correctly.

I will open a ticket anyway pointing to this specific behavior.

Thank you very much for the support!

-- 
Stefano Stagnaro

Prisma Telecom Testing S.r.l.
Via Petrocchi, 4
20127 Milano – Italy

Tel. 02 26113507 int 339
e-mail: stefa...@prismatelecomtesting.com
skype: stefano.stagnaro

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

Re: [ovirt-users] oVirt and Openstack Neutron: network not working

[Luca 'remix_tj' Lorenzetto]

On Thu, Mar 9, 2017 at 2:24 PM, Marcin Mirecki  wrote:
> Hello Luca,

Hello Marcin,

> The osn provider basically only connects the vnics to the osn networks,
> items like dhcp must be handled on the osn networks itself.

Yes, i know. The network is defined by neutron, which has it's own dhcp server.

> Have you tried connecting any nics manually and checking connectivity
> between them?

What do you mean?

> No connectivity with static IP's could hint at some configuration problems.
> Are osn/ovs set up correctly? Firewall blocking traffic?

there is no firewall between openstack controllers and ovirt
engine/hosts. My doubt is about configuration, i've configured in this
way:

Name: openstack-networks
Type: OpenStack Networking
Description:
Provider URL: http://openstack.example.com:9696

Flagged read-only and requires authentication

Set the authentication and tested, reports everything ok.

Nothing else has been configured. I didn't found any documentation
that clarified if is enough.

After powering on i see on openstack this:

[stack@opstrio1101 ~]$ openstack port list | grep 00:1a:4a:16:01:51
<-- this is mac address of oVirt VM
| 86c46fed-dddf-4776-a765-27d4e52e861c | nic1
| 00:1a:4a:16:01:51 | ip_address='172.25.7.4',
subnet_id='280a98ad-0fd5-4961-a307-d1bfea8355cd' |



> Can you please send us a more detailed descirption of your env (ip addr,
> brctl show, ovs-vsctl show)?

This are the output of the commands you asked from a node where a vm
that is attached to a neutron network is running:

[root@ovirt002 ~]# ip addr
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
   valid_lft forever preferred_lft forever
2: enp2s0f0:  mtu 1500 qdisc mq
master bond0 state UP qlen 1000
link/ether 00:21:5a:9b:b7:93 brd ff:ff:ff:ff:ff:ff
3: enp2s0f1:  mtu 1500 qdisc mq
master bond0 state UP qlen 1000
link/ether 00:21:5a:9b:b7:93 brd ff:ff:ff:ff:ff:ff
4: enp2s0f2:  mtu 1500 qdisc mq
master bond1 state UP qlen 1000
link/ether 00:21:5a:9b:b7:97 brd ff:ff:ff:ff:ff:ff
5: enp2s0f3:  mtu 1500 qdisc mq
master bond1 state UP qlen 1000
link/ether 00:21:5a:9b:b7:97 brd ff:ff:ff:ff:ff:ff
6: enp2s0f4:  mtu 1500 qdisc mq
state DOWN qlen 1000
link/ether 00:21:5a:9b:b7:9b brd ff:ff:ff:ff:ff:ff
7: enp2s0f5:  mtu 1500 qdisc mq
state DOWN qlen 1000
link/ether 00:21:5a:9b:b7:9d brd ff:ff:ff:ff:ff:ff
8: enp2s0f6:  mtu 1500 qdisc mq
state DOWN qlen 1000
link/ether b4:b5:2f:55:bc:eb brd ff:ff:ff:ff:ff:ff
9: enp2s0f7:  mtu 1500 qdisc mq
state DOWN qlen 1000
link/ether b4:b5:2f:55:bc:ef brd ff:ff:ff:ff:ff:ff
10: bond0:  mtu 1500 qdisc
noqueue master ovirtmgmt state UP qlen 1000
link/ether 00:21:5a:9b:b7:93 brd ff:ff:ff:ff:ff:ff
11: ovirtmgmt:  mtu 1500 qdisc
noqueue state UP qlen 1000
link/ether 00:21:5a:9b:b7:93 brd ff:ff:ff:ff:ff:ff
inet 10.5.40.192/22 brd 10.5.43.255 scope global ovirtmgmt
   valid_lft forever preferred_lft forever
inet6 fe80::221:5aff:fe9b:b793/64 scope link
   valid_lft forever preferred_lft forever
12: bond1:  mtu 1500 qdisc
noqueue master NFS state UP qlen 1000
link/ether 00:21:5a:9b:b7:97 brd ff:ff:ff:ff:ff:ff
13: NFS:  mtu 1500 qdisc noqueue
state UP qlen 1000
link/ether 00:21:5a:9b:b7:97 brd ff:ff:ff:ff:ff:ff
inet 10.5.160.46/22 brd 10.5.163.255 scope global NFS
   valid_lft forever preferred_lft forever
inet6 fe80::221:5aff:fe9b:b797/64 scope link
   valid_lft forever preferred_lft forever
14: ;vdsmdummy;:  mtu 1500 qdisc noop state DOWN qlen 1000
link/ether be:ae:6d:b7:0f:f5 brd ff:ff:ff:ff:ff:ff
16: qvo86c46fed-dd@qvb86c46fed-dd:
 mtu 1500 qdisc noqueue state
UP qlen 1000
link/ether 5e:d1:06:97:f0:19 brd ff:ff:ff:ff:ff:ff
inet6 fe80::5cd1:6ff:fe97:f019/64 scope link
   valid_lft forever preferred_lft forever
17: qvb86c46fed-dd@qvo86c46fed-dd:
 mtu 1500 qdisc noqueue state
UP qlen 1000
link/ether e6:73:ee:8e:03:09 brd ff:ff:ff:ff:ff:ff
inet6 fe80::e473:eeff:fe8e:309/64 scope link
   valid_lft forever preferred_lft forever
18: qbr86c46fed-dd:  mtu 1500 qdisc noop state
DOWN qlen 1000
link/ether fe:1a:4a:16:01:51 brd ff:ff:ff:ff:ff:ff
21: tap86c46fed-dd:  mtu 1500 qdisc
pfifo_fast master qbr86c46fed-dd state UNKNOWN qlen 1000
link/ether fe:1a:4a:16:01:51 brd ff:ff:ff:ff:ff:ff


[root@ovirt002 ~]# brctl show
bridge name bridge id STP enabled interfaces
;vdsmdummy; 8000. no
NFS 8000.00215a9bb797 no bond1
ovirtmgmt 8000.00215a9bb793 no bond0
qbr86c46fed-dd 8000.fe1a4a160151 no tap86c46fed-dd


[root@ovirt002 ~]# ovs-vsctl show
ovs-vsctl: unix:/var/run/openvswitch/db.sock: database connection
failed (No such file or directory)


If you need other clarifications i'll dig without problem in this env.

Luca




-- 
"E' assurdo impiegare gli uomini di intelligenza eccellente per fare
calcoli c

Re: [ovirt-users] cannot exceed maximum memory size

[Juan Hernández]

On 03/09/2017 04:00 PM, Jakub Niedermertl wrote:
> Based on the snipped provided at the beginning of the conversation I
> assume rest api v3 is used. I'm not sure, max memory property was
> backported there.
> 
> @Juan do we have some support for 4.1 changes in rest api v3?
> 
> In rest api v4 it's
> http://ovirt.github.io/ovirt-engine-api-model/4.1/#types/memory_policy/attributes/max
> .
> 
> 
> ...
> 
> amount in bytes
> ...
> 
> ...
> 
> 

Max memory is a version 4 feature, it isn't/won't be available in
version 3 of the API.

> 
> 
> On Thu, Mar 9, 2017 at 3:07 PM, Marcelo Leandro  wrote:
>> Thanks for reply Jakub Niedermertl,
>>
>>  I would like the explicitly specifying in my script , but i dont know
>> the parameters for use for max memory.
>> Can you help me ?
>>
>> Very Thanks.
>>
>> 2017-03-09 10:37 GMT-03:00 Jakub Niedermertl :
>>>
>>> Hi all,
>>>
>>> Since engine 4.1 there is new property of VMs/templates - max memory
>>> [1] that is required to be larger than (or equal to) memory size. The
>>> problem is probably caused by the fact that the specified memory (I
>>> assume that value of  `memo` is 20480MB) is larger that max memory
>>> that is implicitly copied from template (Blank in this case). I can
>>> see two possible solutions:
>>> * Explicitly specifying size of max memory in the script.
>>> * Increasing max memory in the template.
>>>
>>> Jakub
>>>
>>> [1]:
>>> http://www.ovirt.org/develop/release-management/features/engine/maximum-memory-size/
>>>
>>> On Thu, Mar 9, 2017 at 2:20 PM, Shahar Havivi  wrote:
 its not related to bug 1425089 (which is upgrading cluster issue) but
 its
 the same feature that cause this issue,
 Jakub what do we have bug on that issue?

 as for the default RAM limit you can find it via the engine-config tool:
 $ engine-config -g VM32BitMaxMemorySizeInMB
 $ engine-config -g VM64BitMaxMemorySizeInMB

 On Thu, Mar 9, 2017 at 2:44 PM, Maton, Brett 
 wrote:
>
> I have a similar problem creating VM's with the API, but no solution.
>
>   It seems that by default oVirt uses custom 'Instance Type' ( you can
> see
> it if you use the UI to create a VM ).
>   The default RAM limit for custom Instance Type is 4096MB.
>
>   I haven't found where you can change the settnigs for the custom
> instance type though.
>
>
>
> On 9 March 2017 at 11:52, Marcelo Leandro 
> wrote:
>>
>> can someone help me?
>>
>> 2017-03-07 16:25 GMT-03:00 Marcelo Leandro :
>>>
>>> Hello ,
>>>
>>> I am have an script that create VM , after upgrade to 4.1 I have this
>>> erro when trying create a new VM:
>>>
>>> detail: Cannot add VM. Memory size (20480MB) cannot exceed maximum
>>> memory size (4096MB).
>>>
>>> my commando fore create VM :
>>>
>>> api.vms.add(params.VM(name="teste", memory=memo , cpu=cpu,
>>> cluster=api.clusters.get(cluster),
>>> template=api.templates.get('Blank'),
>>> type_="server"))
>>>
>>> I dont how specific  the maximum memory size.
>>>
>>> Thanks
>>>
>>> Marcelo Leandro
>>
>>
>>
>> ___
>> 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
>

>>
>>

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

Re: [ovirt-users] cannot exceed maximum memory size

[Jakub Niedermertl]

Based on the snipped provided at the beginning of the conversation I
assume rest api v3 is used. I'm not sure, max memory property was
backported there.

@Juan do we have some support for 4.1 changes in rest api v3?

In rest api v4 it's
http://ovirt.github.io/ovirt-engine-api-model/4.1/#types/memory_policy/attributes/max
.


...

amount in bytes
...

...




On Thu, Mar 9, 2017 at 3:07 PM, Marcelo Leandro  wrote:
> Thanks for reply Jakub Niedermertl,
>
>  I would like the explicitly specifying in my script , but i dont know
> the parameters for use for max memory.
> Can you help me ?
>
> Very Thanks.
>
> 2017-03-09 10:37 GMT-03:00 Jakub Niedermertl :
>>
>> Hi all,
>>
>> Since engine 4.1 there is new property of VMs/templates - max memory
>> [1] that is required to be larger than (or equal to) memory size. The
>> problem is probably caused by the fact that the specified memory (I
>> assume that value of  `memo` is 20480MB) is larger that max memory
>> that is implicitly copied from template (Blank in this case). I can
>> see two possible solutions:
>> * Explicitly specifying size of max memory in the script.
>> * Increasing max memory in the template.
>>
>> Jakub
>>
>> [1]:
>> http://www.ovirt.org/develop/release-management/features/engine/maximum-memory-size/
>>
>> On Thu, Mar 9, 2017 at 2:20 PM, Shahar Havivi  wrote:
>> > its not related to bug 1425089 (which is upgrading cluster issue) but
>> > its
>> > the same feature that cause this issue,
>> > Jakub what do we have bug on that issue?
>> >
>> > as for the default RAM limit you can find it via the engine-config tool:
>> > $ engine-config -g VM32BitMaxMemorySizeInMB
>> > $ engine-config -g VM64BitMaxMemorySizeInMB
>> >
>> > On Thu, Mar 9, 2017 at 2:44 PM, Maton, Brett 
>> > wrote:
>> >>
>> >> I have a similar problem creating VM's with the API, but no solution.
>> >>
>> >>   It seems that by default oVirt uses custom 'Instance Type' ( you can
>> >> see
>> >> it if you use the UI to create a VM ).
>> >>   The default RAM limit for custom Instance Type is 4096MB.
>> >>
>> >>   I haven't found where you can change the settnigs for the custom
>> >> instance type though.
>> >>
>> >>
>> >>
>> >> On 9 March 2017 at 11:52, Marcelo Leandro 
>> >> wrote:
>> >>>
>> >>> can someone help me?
>> >>>
>> >>> 2017-03-07 16:25 GMT-03:00 Marcelo Leandro :
>> 
>>  Hello ,
>> 
>>  I am have an script that create VM , after upgrade to 4.1 I have this
>>  erro when trying create a new VM:
>> 
>>  detail: Cannot add VM. Memory size (20480MB) cannot exceed maximum
>>  memory size (4096MB).
>> 
>>  my commando fore create VM :
>> 
>>  api.vms.add(params.VM(name="teste", memory=memo , cpu=cpu,
>>  cluster=api.clusters.get(cluster),
>>  template=api.templates.get('Blank'),
>>  type_="server"))
>> 
>>  I dont how specific  the maximum memory size.
>> 
>>  Thanks
>> 
>>  Marcelo Leandro
>> >>>
>> >>>
>> >>>
>> >>> ___
>> >>> 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
>> >>
>> >
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] DWH reports in 4.X ?

[Shirly Radco]

Yes. We are working to integrate our engine and vdsm logs as well.
Hope you will find it helpful and would appreciate your input once we have
the metrics store in production.

--

Shirly Radco

BI Software Engineer
Red Hat Israel Ltd.


On Wed, Mar 8, 2017 at 4:44 PM, Eduardo Mayoral  wrote:

> Thanks for your answer!
>
> Looks certainly interesting. I am using collectd with virt plugin + carbon
> + graphite + grafana for performance graphs of the hosts and the VMs right
> now ( oVirt 4.1 with nodes in CentOS 7.3)
>
> I like the idea of using fluentd for this instead of a relational
> database. Will it handle metrics and logs as well? I am asking because of
> the kibana component.
>
> Best regards,
>
> Eduardo Mayoral Jimeno (emayo...@arsys.es)
> Administrador de sistemas. Departamento de Plataformas. Arsys internet.+34 
> 941 620 145 ext. 5153 <+34%20941%2062%2001%2045>
>
> On 08/03/17 14:51, Shirly Radco wrote:
>
> Hi Eduardo,
>
> DWH still exists, and if you have a reports tool that supports sql you can
> use it with it.
> Reports was deprecated in 3.6.
>
> We are now working on adding a new metrics store solution for oVirt.
>
> For more details you can have a look at:
> http://www.ovirt.org/develop/release-management/features/eng
> ine/metrics-store/
>
> Currently in 4.1 the hosts and engine include Collectd and Fluentd.
> In 4.2 we expect to have the metrics store ready.
>
> You can try setting up the metrics store side from upstream for now.
> https://github.com/sradco/ovirt-metrics-conf
>
> 
>
> 
> The Fluent and Collectd configuration are handled at:
> https://github.com/oVirt/ovirt-engine-metrics
>
>
> Best regards,
>
> Shirly Radco
>
> BI Software Engineer
> Red Hat Israel Ltd.
> 34 Jerusalem Road
> Building A, 4th floor
> Ra'anana, Israel 4350109
>
>
> On Tue, Mar 7, 2017 at 12:29 PM, Eduardo Mayoral 
> wrote:
>
>>
>> Hi,
>>
>> I see the DWH reports disappeared in 3.5 or maybe 3.6, there seems
>> to be no substitute por 4.X
>>
>> Is there some alternative to have some pre-made reports from the DWH
>> on 4.X ? Maybe not something on the oVirt project itself but from
>> someone on the community?
>>
>> Thanks in advance!
>>
>> --
>> Eduardo Mayoral Jimeno (emayo...@arsys.es)
>> Administrador de sistemas. Departamento de Plataformas. Arsys internet.
>> +34 941 620 145 ext. 5153
>>
>> ___
>> 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] [ANN] oVirt 4.1.1 Second Release Candidate

[Sandro Bonazzola]

The oVirt Project is pleased to announce the availability of the Second
Release Candidate of oVirt 4.1.1 for testing, as of March 9th, 2017

This is pre-release software. Please take a look at our community page[1]
to know how to ask questions and interact with developers and users.
All issues or bugs should be reported via oVirt Bugzilla[2].
This pre-release should not to be used in production.

This update is the second release candidate of the first in a series of
stabilization updates to the 4.1 series.
4.1.1 brings 32 enhancements and more than 370 bugfixes,
including more than 150 high or urgent
severity fixes, on top of oVirt 4.1 series

This release is available now for:
* Fedora 24 (tech preview)
* Red Hat Enterprise Linux 7.3 or later
* CentOS Linux (or similar) 7.3 or later

This release supports Hypervisor Hosts running:
* Red Hat Enterprise Linux 7.3 or later
* CentOS Linux (or similar) 7.3 or later
* Fedora 24 (tech preview)

See the release notes draft [3] for installation / upgrade instructions and
a list of new features and bugs fixed.

Notes:
- oVirt Live and oVirt node have been already built [4]
- oVirt Engine Appliance had been already built

Additional Resources:
* Read more about the oVirt 4.1.1 release highlights:
http://www.ovirt.org/release/4.1.1/
* Get more oVirt Project updates on Twitter: https://twitter.com/ovirt
* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/

[1] https://www.ovirt.org/community/
[2] https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt
[3] http://www.ovirt.org/release/4.1.1/
[4] http://resources.ovirt.org/pub/ovirt-4.1-pre/iso/



-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] cannot exceed maximum memory size

[Marcelo Leandro]

Thanks for reply Jakub Niedermertl,

 I would like the explicitly specifying in my script , but i dont know
the parameters for use for max memory.
Can you help me ?

Very Thanks.

2017-03-09 10:37 GMT-03:00 Jakub Niedermertl :

> Hi all,
>
> Since engine 4.1 there is new property of VMs/templates - max memory
> [1] that is required to be larger than (or equal to) memory size. The
> problem is probably caused by the fact that the specified memory (I
> assume that value of  `memo` is 20480MB) is larger that max memory
> that is implicitly copied from template (Blank in this case). I can
> see two possible solutions:
> * Explicitly specifying size of max memory in the script.
> * Increasing max memory in the template.
>
> Jakub
>
> [1]: http://www.ovirt.org/develop/release-management/features/
> engine/maximum-memory-size/
>
> On Thu, Mar 9, 2017 at 2:20 PM, Shahar Havivi  wrote:
> > its not related to bug 1425089 (which is upgrading cluster issue) but its
> > the same feature that cause this issue,
> > Jakub what do we have bug on that issue?
> >
> > as for the default RAM limit you can find it via the engine-config tool:
> > $ engine-config -g VM32BitMaxMemorySizeInMB
> > $ engine-config -g VM64BitMaxMemorySizeInMB
> >
> > On Thu, Mar 9, 2017 at 2:44 PM, Maton, Brett 
> > wrote:
> >>
> >> I have a similar problem creating VM's with the API, but no solution.
> >>
> >>   It seems that by default oVirt uses custom 'Instance Type' ( you can
> see
> >> it if you use the UI to create a VM ).
> >>   The default RAM limit for custom Instance Type is 4096MB.
> >>
> >>   I haven't found where you can change the settnigs for the custom
> >> instance type though.
> >>
> >>
> >>
> >> On 9 March 2017 at 11:52, Marcelo Leandro 
> wrote:
> >>>
> >>> can someone help me?
> >>>
> >>> 2017-03-07 16:25 GMT-03:00 Marcelo Leandro :
> 
>  Hello ,
> 
>  I am have an script that create VM , after upgrade to 4.1 I have this
>  erro when trying create a new VM:
> 
>  detail: Cannot add VM. Memory size (20480MB) cannot exceed maximum
>  memory size (4096MB).
> 
>  my commando fore create VM :
> 
>  api.vms.add(params.VM(name="teste", memory=memo , cpu=cpu,
>  cluster=api.clusters.get(cluster), template=api.templates.get('
> Blank'),
>  type_="server"))
> 
>  I dont how specific  the maximum memory size.
> 
>  Thanks
> 
>  Marcelo Leandro
> >>>
> >>>
> >>>
> >>> ___
> >>> 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
> >>
> >
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Unable to add permissions for LDAP users

[Richard Neuboeck]

Hi,

I seem to experience the same problem right now and am at a bit of a
loss as to where to dig for some more troubleshooting information. I
would highly appreciate some help.

Here is what I have and what I did:

ovirt-engine-4.1.0.4-1.el7.centos.noarch
ovirt-engine-extension-aaa-ldap-1.3.0-1.el7.noarch

I executed ovirt-engine-extension-aaa-ldap-setup. My LDAP provider
is 389ds (FreeIPA). I can successfully run a search and also login
from the setup script.

After running the setup I rebootet the Engine VM to make sure
everything is restarted.

In the web UI configuration for 'System Permissions' I'm able to
find users from LDAP but when I try to 'Add' a selected user the UI
shows me this error: 'User admin@internal-authz failed to grant
permission for Role SuperUser on System to User/Group .'.

In then engine.log the following lines are generated:
2017-03-09 14:02:49,308+01 INFO
[org.ovirt.engine.core.bll.AddSystemPermissionCommand]
(org.ovirt.thread.pool-6-thread-4)
[1ebae5e0-e5f6-49ba-ac80-95266c582893] Running command:
AddSystemPermissionCommand internal: false. Entities affected :  ID:
aaa0----123456789aaa Type: SystemAction group
MANIPULATE_PERMISSIONS with role type USER,  ID:
aaa0----123456789aaa Type: SystemAction group
ADD_USERS_AND_GROUPS_FROM_DIRECTORY with role type USER
2017-03-09 14:02:49,319+01 ERROR
[org.ovirt.engine.core.bll.AddSystemPermissionCommand]
(org.ovirt.thread.pool-6-thread-4)
[1ebae5e0-e5f6-49ba-ac80-95266c582893] Transaction rolled-back for
command 'org.ovirt.engine.core.bll.AddSystemPermissionCommand'.
2017-03-09 14:02:49,328+01 ERROR
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(org.ovirt.thread.pool-6-thread-4)
[1ebae5e0-e5f6-49ba-ac80-95266c582893] EVENT_ID:
USER_ADD_SYSTEM_PERMISSION_FAILED(867), Correlation ID:
1ebae5e0-e5f6-49ba-ac80-95266c582893, Call Stack: null, Custom Event
ID: -1, Message: User admin@internal-authz failed to grant
permission for Role SuperUser on System to User/Group .


So far I've re-run the ldap-setup routine. I made sure all newly
generated files in /etc/ovirt-engine/[aaa|extensions.d] are owned by
ovirt:ovirt (instead of root) and have 0600 as permission (instead
of 0644). That didn't change anything.

I've also found an older bug report but for oVirt 3.5
https://bugzilla.redhat.com/show_bug.cgi?id=1121954
That didn't reveal any new either.

Any ideas what I could try next?

Thanks!
Cheers
Richard




On 10/06/2016 04:36 PM, Ondra Machacek wrote:
> On 10/06/2016 01:47 PM, Michael Burch wrote:
>> I'm using the latest ovirt on CentOS7 with the aaa-ldap extension.
>> I can
>> successfully authenticate as an LDAP user. I can also login as
>> admin@internal and search for, find, and select LDAP users but I
>> cannot
>> add permissions for them. Each time I get the error "User
>> admin@internal-authz failed to grant permission for Role UserRole on
>> System to User/Group ."
> 
> This error usually means bad unique attribute used.
> 
>>
>>
>> I have no control over the LDAP server, which uses custom
>> objectClasses
>> and uses groupOfNames instead of PosixGroups. I assume I need to set
>> sequence variables to accommodate our group configuration but I'm
>> at a
>> loss as to where to begin. the The config I have is as follows:
>>
>>
>> include = 
>>
>> vars.server = labauth.lan.lab.org
>>
>> pool.authz.auth.type = none
>> pool.default.serverset.type = single
>> pool.default.serverset.single.server = ${global:vars.server}
>> pool.default.ssl.startTLS = true
>> pool.default.ssl.insecure = true
>>
>> pool.default.connection-options.connectTimeoutMillis = 1
>> pool.default.connection-options.responseTimeoutMillis = 9
>> sequence-init.init.100-my-basedn-init-vars = my-basedn-init-vars
>> sequence.my-basedn-init-vars.010.description = set baseDN
>> sequence.my-basedn-init-vars.010.type = var-set
>> sequence.my-basedn-init-vars.010.var-set.variable = simple_baseDN
>> sequence.my-basedn-init-vars.010.var-set.value = o=LANLAB
>>
>> sequence-init.init.101-my-objectclass-init-vars =
>> my-objectclass-init-vars
>> sequence.my-objectclass-init-vars.020.description = set objectClass
>> sequence.my-objectclass-init-vars.020.type = var-set
>> sequence.my-objectclass-init-vars.020.var-set.variable =
>> simple_filterUserObject
>> sequence.my-objectclass-init-vars.020.var-set.value =
>> (objectClass=labPerson)(uid=*)
>>
>> search.default.search-request.derefPolicy = NEVER
>>
>> sequence-init.init.900-local-init-vars = local-init-vars
>> sequence.local-init-vars.010.description = override name space
>> sequence.local-init-vars.010.type = var-set
>> sequence.local-init-vars.010.var-set.variable =
>> simple_namespaceDefault
>> sequence.local-init-vars.010.var-set.value = *
> 
> What's this^ for? I think it's unusable.
> 
>>
>> sequence.local-init-vars.020.description = apply filter to users
>> sequence.local-init-vars.020.type = var-set
>> sequence.local-init-vars.020.var-set.variable =
>> simple_filte

Re: [ovirt-users] oVirt VM backup and restore

[Juan Hernández]

On 03/09/2017 02:10 PM, Nathanaël Blanchet wrote:
> 
> 
> Le 09/03/2017 à 12:10, Juan Hernández a écrit :
>> On 03/09/2017 11:57 AM, Gianluca Cecchi wrote:
>>> On Thu, Mar 9, 2017 at 11:39 AM, Nathanaël Blanchet >> > wrote:
>>>
>>>
>>>
>>>  Le 09/03/2017 à 10:25, Gianluca Cecchi a écrit :
  On Wed, Mar 8, 2017 at 6:05 PM, Gianluca Cecchi
  mailto:gianluca.cec...@gmail.com>>
 wrote:



  NOTE: during the snapshot creation I see in web admin console
  the VM in paused state and also not responsive in both console
  and ssh session.
  After a couple of seconds it comes back and as a confirmation
  I see this in its messages:

  Mar  8 17:38:57 T-ORACLE73 chronyd[616]: System clock wrong by
  19.077230 seconds, adjustment started

  Is this expected?




  Possibly the default changed at some point in time, so that now it
  saves memory and so this implies pause of VM
>>>  Saving memory is essential in some apàplications like DB, so you
>>>  won't bypass vm pauses for such a stuff
>>>
>>>
>>> Yes, indeed, the important thing is to have an option so that you can
>>> set it True or False, depending on the VM you are saving, the
>>> application that is running isnide it and the way you want to do backup
>>> of the application.
>>> Nevertheless, RDBMS and also other applications often have some
>>> mechanism to be "frozen in a consistent state" so that you can save what
>>> you have on disk without need to save memory to have a consistent
>>> backup.
>>> Oracle for example has functionality to be put in "backup mode" where
>>> you issue "begin backup" before the snapshot and "end backup" right
>>> after snapshot completion.
>>> I see that POstgreSQL has similar functionality (not tested myself):
>>> https://www.postgresql.org/docs/9.4/static/continuous-archiving.html#BACKUP-LOWLEVEL-BASE-BACKUP
>>>
>>> and the same for other ones.
>>>
>>> Gianluca
>>>
>> Just wanted to add that freezing activity is not only important for
>> databases, but also for plain file systems. In order to do a consistent
>> backup it is important to freeze the file systems before creating a live
>> snapshot, and thaw it afterwards. oVirt does that automatically, but
>> only if the guest agent is installed and running. So, remember to have
>> the guest agent installed and running in the virtual machines that you
>> plan to backup using this mechanism.
> Very useful piece of information, so does that mean memory save feature
> not to be really useful? if so, it shouldn't be the default, so that vm
> never go into pause state unusefully.

I didn't mean that saving memory isn't useful. It is very useful, for
certain use cases. For the backup use case I think it is better to
disable it.

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

Re: [ovirt-users] cannot exceed maximum memory size

[Jakub Niedermertl]

Hi all,

Since engine 4.1 there is new property of VMs/templates - max memory
[1] that is required to be larger than (or equal to) memory size. The
problem is probably caused by the fact that the specified memory (I
assume that value of  `memo` is 20480MB) is larger that max memory
that is implicitly copied from template (Blank in this case). I can
see two possible solutions:
* Explicitly specifying size of max memory in the script.
* Increasing max memory in the template.

Jakub

[1]: 
http://www.ovirt.org/develop/release-management/features/engine/maximum-memory-size/

On Thu, Mar 9, 2017 at 2:20 PM, Shahar Havivi  wrote:
> its not related to bug 1425089 (which is upgrading cluster issue) but its
> the same feature that cause this issue,
> Jakub what do we have bug on that issue?
>
> as for the default RAM limit you can find it via the engine-config tool:
> $ engine-config -g VM32BitMaxMemorySizeInMB
> $ engine-config -g VM64BitMaxMemorySizeInMB
>
> On Thu, Mar 9, 2017 at 2:44 PM, Maton, Brett 
> wrote:
>>
>> I have a similar problem creating VM's with the API, but no solution.
>>
>>   It seems that by default oVirt uses custom 'Instance Type' ( you can see
>> it if you use the UI to create a VM ).
>>   The default RAM limit for custom Instance Type is 4096MB.
>>
>>   I haven't found where you can change the settnigs for the custom
>> instance type though.
>>
>>
>>
>> On 9 March 2017 at 11:52, Marcelo Leandro  wrote:
>>>
>>> can someone help me?
>>>
>>> 2017-03-07 16:25 GMT-03:00 Marcelo Leandro :

 Hello ,

 I am have an script that create VM , after upgrade to 4.1 I have this
 erro when trying create a new VM:

 detail: Cannot add VM. Memory size (20480MB) cannot exceed maximum
 memory size (4096MB).

 my commando fore create VM :

 api.vms.add(params.VM(name="teste", memory=memo , cpu=cpu,
 cluster=api.clusters.get(cluster), template=api.templates.get('Blank'),
 type_="server"))

 I dont how specific  the maximum memory size.

 Thanks

 Marcelo Leandro
>>>
>>>
>>>
>>> ___
>>> 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
>>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] oVirt and Openstack Neutron: network not working

[Marcin Mirecki]

Hello Luca,
The osn provider basically only connects the vnics to the osn networks,
items like dhcp must be handled on the osn networks itself.
Have you tried connecting any nics manually and checking connectivity
between them?
No connectivity with static IP's could hint at some configuration problems.
Are osn/ovs set up correctly? Firewall blocking traffic?
Can you please send us a more detailed descirption of your env (ip addr,
brctl show, ovs-vsctl show)?

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

Re: [ovirt-users] cannot exceed maximum memory size

[Shahar Havivi]

its not related to bug 1425089 (which is upgrading cluster issue) but its
the same feature that cause this issue,
Jakub what do we have bug on that issue?

as for the default RAM limit you can find it via the engine-config tool:
$ engine-config -g VM32BitMaxMemorySizeInMB
$ engine-config -g VM64BitMaxMemorySizeInMB

On Thu, Mar 9, 2017 at 2:44 PM, Maton, Brett 
wrote:

> I have a similar problem creating VM's with the API, but no solution.
>
>   It seems that by default oVirt uses custom 'Instance Type' ( you can see
> it if you use the UI to create a VM ).
>   The default RAM limit for custom Instance Type is 4096MB.
>
>   I haven't found where you can change the settnigs for the custom
> instance type though.
>
>
>
> On 9 March 2017 at 11:52, Marcelo Leandro  wrote:
>
>> can someone help me?
>>
>> 2017-03-07 16:25 GMT-03:00 Marcelo Leandro :
>>
>>> Hello ,
>>>
>>> I am have an script that create VM , after upgrade to 4.1 I have this
>>> erro when trying create a new VM:
>>>
>>> detail: Cannot add VM. Memory size (20480MB) cannot exceed maximum
>>> memory size (4096MB).
>>>
>>> my commando fore create VM :
>>>
>>> api.vms.add(params.VM(name="teste", memory=memo , cpu=cpu,
>>> cluster=api.clusters.get(cluster), template=api.templates.get('Blank'),
>>> type_="server"))
>>>
>>> I dont how specific  the maximum memory size.
>>>
>>> Thanks
>>>
>>> Marcelo Leandro
>>>
>>
>>
>> ___
>> 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
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] oVirt VM backup and restore

[Nathanaël Blanchet]

Le 09/03/2017 à 12:10, Juan Hernández a écrit :

On 03/09/2017 11:57 AM, Gianluca Cecchi wrote:

On Thu, Mar 9, 2017 at 11:39 AM, Nathanaël Blanchet mailto:blanc...@abes.fr>> wrote:



 Le 09/03/2017 à 10:25, Gianluca Cecchi a écrit :

 On Wed, Mar 8, 2017 at 6:05 PM, Gianluca Cecchi
 mailto:gianluca.cec...@gmail.com>> wrote:



 NOTE: during the snapshot creation I see in web admin console
 the VM in paused state and also not responsive in both console
 and ssh session.
 After a couple of seconds it comes back and as a confirmation
 I see this in its messages:

 Mar  8 17:38:57 T-ORACLE73 chronyd[616]: System clock wrong by
 19.077230 seconds, adjustment started

 Is this expected?




 Possibly the default changed at some point in time, so that now it
 saves memory and so this implies pause of VM

 Saving memory is essential in some apàplications like DB, so you
 won't bypass vm pauses for such a stuff


Yes, indeed, the important thing is to have an option so that you can
set it True or False, depending on the VM you are saving, the
application that is running isnide it and the way you want to do backup
of the application.
Nevertheless, RDBMS and also other applications often have some
mechanism to be "frozen in a consistent state" so that you can save what
you have on disk without need to save memory to have a consistent backup.
Oracle for example has functionality to be put in "backup mode" where
you issue "begin backup" before the snapshot and "end backup" right
after snapshot completion.
I see that POstgreSQL has similar functionality (not tested myself):
https://www.postgresql.org/docs/9.4/static/continuous-archiving.html#BACKUP-LOWLEVEL-BASE-BACKUP
and the same for other ones.

Gianluca


Just wanted to add that freezing activity is not only important for
databases, but also for plain file systems. In order to do a consistent
backup it is important to freeze the file systems before creating a live
snapshot, and thaw it afterwards. oVirt does that automatically, but
only if the guest agent is installed and running. So, remember to have
the guest agent installed and running in the virtual machines that you
plan to backup using this mechanism.
Very useful piece of information, so does that mean memory save feature 
not to be really useful? if so, it shouldn't be the default, so that vm 
never go into pause state unusefully.




--
Nathanaël Blanchet

Supervision réseau
Pôle Infrastrutures Informatiques
227 avenue Professeur-Jean-Louis-Viala
34193 MONTPELLIER CEDEX 5   
Tél. 33 (0)4 67 54 84 55
Fax  33 (0)4 67 54 84 14
blanc...@abes.fr

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

Re: [ovirt-users] cannot exceed maximum memory size

[Maton, Brett]

I have a similar problem creating VM's with the API, but no solution.

  It seems that by default oVirt uses custom 'Instance Type' ( you can see
it if you use the UI to create a VM ).
  The default RAM limit for custom Instance Type is 4096MB.

  I haven't found where you can change the settnigs for the custom instance
type though.



On 9 March 2017 at 11:52, Marcelo Leandro  wrote:

> can someone help me?
>
> 2017-03-07 16:25 GMT-03:00 Marcelo Leandro :
>
>> Hello ,
>>
>> I am have an script that create VM , after upgrade to 4.1 I have this
>> erro when trying create a new VM:
>>
>> detail: Cannot add VM. Memory size (20480MB) cannot exceed maximum memory
>> size (4096MB).
>>
>> my commando fore create VM :
>>
>> api.vms.add(params.VM(name="teste", memory=memo , cpu=cpu,
>> cluster=api.clusters.get(cluster), template=api.templates.get('Blank'),
>> type_="server"))
>>
>> I dont how specific  the maximum memory size.
>>
>> Thanks
>>
>> Marcelo Leandro
>>
>
>
> ___
> 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] cannot exceed maximum memory size

[Yedidyah Bar David]

On Thu, Mar 9, 2017 at 1:52 PM, Marcelo Leandro  wrote:
> can someone help me?
>
> 2017-03-07 16:25 GMT-03:00 Marcelo Leandro :
>>
>> Hello ,
>>
>> I am have an script that create VM , after upgrade to 4.1 I have this erro
>> when trying create a new VM:
>>
>> detail: Cannot add VM. Memory size (20480MB) cannot exceed maximum memory
>> size (4096MB).
>>
>> my commando fore create VM :
>>
>> api.vms.add(params.VM(name="teste", memory=memo , cpu=cpu,
>> cluster=api.clusters.get(cluster), template=api.templates.get('Blank'),
>> type_="server"))
>>
>> I dont how specific  the maximum memory size.

Not sure, adding Shahar as the owner of this seemingly-similar bug:

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

I guess 4.1 enforces some memory limits that 4.0 didn't. If I am
right, you'll have to increase these limits.

Best,

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



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

Re: [ovirt-users] Moving from fc based to iSCSI based

[Fred Rolland]

I don't think it will work.
We rely heavily on LVM when working with iSCSI and FC and I am not sure how
LVM will handle this kind of operation.
A storage domain is a VG that contains PVs (LUNS), and each disk is a LV.

On Wed, Mar 8, 2017 at 6:02 PM, Gianluca Cecchi 
wrote:

> On Wed, Mar 8, 2017 at 3:33 PM, Fred Rolland  wrote:
>
>> I cannot think of another option other to have an export domain in the
>> middle that can be accessed from all the hosts.
>>
>>
>> On Wed, Mar 8, 2017 at 3:50 PM, Gianluca Cecchi <
>> gianluca.cec...@gmail.com> wrote:
>>
>>> On Wed, Mar 8, 2017 at 1:30 PM, Fred Rolland 
>>> wrote:
>>>
 Hi,

 Storage domains are per Data Center, and all hosts in this DC should be
 able to access the SDs, no matter in which cluster they are...

 Are you sure your hosts are on the same DC ?

 Thanks,

 Freddy


>>> No, my scenario was a planning workflow.
>>> At this moment I only have Host1 and Host2 that are connected to an
>>> FC-SAN.
>>> I have to move data to an iSCSI storage and also oVirt hosts to Host3
>>> and Host4 (yet to be deployed).
>>> So I'm trying to understand if I can do it in pieces bypassing
>>> export/import
>>>
>>> I forgot that it is DC the constraint for SD accessibility.
>>> Any suggestion to accomplish the desired target?
>>>
>>> Thanks,
>>> Gianluca
>>>
>>>
>>
> Is it realistic to think something similar to the workflow described
> below, based on the import storage domain functionality described here:
> http://www.ovirt.org/develop/release-management/features/
> storage/importstoragedomain
>
> and in particular one of its targets:
> Transfer VMs between setups without the need to copy the data into and out
> of the export domain.
>
>
> Prerequisite:
> - Host1 has network connectivity with Host3
> - Host1 is part of a DC that contains an FC based storage domain, composed
> of SAN LUN A of X Tb
> - Host3 is part of another DC and has connection in place with iSCSI LUN B
> of X Tb
>
> Workflow:
> - Stop the VMs that are on the source FC domain
> - Put source storage domain into maintenance
> - Detach source storage domain
> - Clone LUN A to LUN B at low level
> (eg dd command via network
> Similar to when you clone an entire disk from a server to another
> server
> )
> - import domain on DC where Host3 lives giving the correct iSCSI
> parameters...
>
> Do the OVF_STORE disks on the storage domain contain information about the
> fact of it being an FC or an iSCSI storage domain, preventing then a
> possible import operation?
>
> This is a test environment where I would like to transfer 4Tb of data from
> FC SAN in decommission phase to an iSCSI SAN, and if I can by-pass export /
> import phases, even giving some downtime, would be good.
>
> Thanks for reading,
> Gianluca
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] cannot exceed maximum memory size

[Marcelo Leandro]

can someone help me?

2017-03-07 16:25 GMT-03:00 Marcelo Leandro :

> Hello ,
>
> I am have an script that create VM , after upgrade to 4.1 I have this erro
> when trying create a new VM:
>
> detail: Cannot add VM. Memory size (20480MB) cannot exceed maximum memory
> size (4096MB).
>
> my commando fore create VM :
>
> api.vms.add(params.VM(name="teste", memory=memo , cpu=cpu,
> cluster=api.clusters.get(cluster), template=api.templates.get('Blank'),
> type_="server"))
>
> I dont how specific  the maximum memory size.
>
> Thanks
>
> Marcelo Leandro
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] oVirt VM backup and restore

[Gianluca Cecchi]

On Thu, Mar 9, 2017 at 12:11 PM, Maton, Brett 
wrote:

> Good point
>
>
>> Just wanted to add that freezing activity is not only important for
>> databases, but also for plain file systems. In order to do a consistent
>> backup it is important to freeze the file systems before creating a live
>> snapshot, and thaw it afterwards. oVirt does that automatically, but
>> only if the guest agent is installed and running. So, remember to have
>> the guest agent installed and running in the virtual machines that you
>> plan to backup using this mechanism.
>>
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>
>
Yes, indeed.
I forgot to write it before, but I did verify that my VM with guest agent
installed had this inside its /var/log/messages file:

Mar  9 10:49:36 T-ORACLE73 qemu-ga: info: guest-fsfreeze called
Mar  9 10:49:36 T-ORACLE73 qemu-ga: info: executing fsfreeze hook with arg
'freeze'
Mar  9 10:49:37 T-ORACLE73 qemu-ga: info: executing fsfreeze hook with arg
'thaw'

Also, with vm_backup.py utility, I verified that inside the VM where the
snapshotted disk was attached (c7testovn1), I got this:

Mar  9 10:49:42 c7testovn1 kernel: pci :00:09.0: BAR 4: assigned [mem
0x4000-0x40003fff 64bit pref]
Mar  9 10:49:42 c7testovn1 kernel: pci :00:09.0: BAR 1: assigned [mem
0x40004000-0x40004fff]
Mar  9 10:49:42 c7testovn1 kernel: pci :00:09.0: BAR 0: assigned [io
 0x1000-0x103f]
Mar  9 10:49:42 c7testovn1 kernel: virtio-pci :00:09.0: enabling device
( -> 0003)
Mar  9 10:49:42 c7testovn1 kernel: vdb: vdb1 vdb2
Mar  9 10:49:42 c7testovn1 systemd: Starting LVM2 PV scan on device
252:18...
Mar  9 10:49:42 c7testovn1 lvm: 2 logical volume(s) in volume group
"mainvg" now active
Mar  9 10:49:42 c7testovn1 systemd: Started LVM2 PV scan on device 252:18.
Mar  9 10:49:44 c7testovn1 systemd: Stopping LVM2 PV scan on device
252:18...
Mar  9 10:49:44 c7testovn1 lvm: Device 252:18 not found. Cleared from
lvmetad cache.
Mar  9 10:49:44 c7testovn1 systemd: Stopped LVM2 PV scan on device 252:18.

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

Re: [ovirt-users] oVirt VM backup and restore

[Maton, Brett]

Good point

On 9 March 2017 at 11:10, Juan Hernández  wrote:

> On 03/09/2017 11:57 AM, Gianluca Cecchi wrote:
> > On Thu, Mar 9, 2017 at 11:39 AM, Nathanaël Blanchet  > > wrote:
> >
> >
> >
> > Le 09/03/2017 à 10:25, Gianluca Cecchi a écrit :
> >> On Wed, Mar 8, 2017 at 6:05 PM, Gianluca Cecchi
> >> mailto:gianluca.cec...@gmail.com>>
> wrote:
> >>
> >>
> >>
> >> NOTE: during the snapshot creation I see in web admin console
> >> the VM in paused state and also not responsive in both console
> >> and ssh session.
> >> After a couple of seconds it comes back and as a confirmation
> >> I see this in its messages:
> >>
> >> Mar  8 17:38:57 T-ORACLE73 chronyd[616]: System clock wrong by
> >> 19.077230 seconds, adjustment started
> >>
> >> Is this expected?
> >>
> >>
> >>
> >>
> >> Possibly the default changed at some point in time, so that now it
> >> saves memory and so this implies pause of VM
> > Saving memory is essential in some apàplications like DB, so you
> > won't bypass vm pauses for such a stuff
> >
> >
> > Yes, indeed, the important thing is to have an option so that you can
> > set it True or False, depending on the VM you are saving, the
> > application that is running isnide it and the way you want to do backup
> > of the application.
> > Nevertheless, RDBMS and also other applications often have some
> > mechanism to be "frozen in a consistent state" so that you can save what
> > you have on disk without need to save memory to have a consistent backup.
> > Oracle for example has functionality to be put in "backup mode" where
> > you issue "begin backup" before the snapshot and "end backup" right
> > after snapshot completion.
> > I see that POstgreSQL has similar functionality (not tested myself):
> > https://www.postgresql.org/docs/9.4/static/continuous-
> archiving.html#BACKUP-LOWLEVEL-BASE-BACKUP
> > and the same for other ones.
> >
> > Gianluca
> >
>
> Just wanted to add that freezing activity is not only important for
> databases, but also for plain file systems. In order to do a consistent
> backup it is important to freeze the file systems before creating a live
> snapshot, and thaw it afterwards. oVirt does that automatically, but
> only if the guest agent is installed and running. So, remember to have
> the guest agent installed and running in the virtual machines that you
> plan to backup using this mechanism.
>
>
> ___
> 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 VM backup and restore

[Juan Hernández]

On 03/09/2017 11:57 AM, Gianluca Cecchi wrote:
> On Thu, Mar 9, 2017 at 11:39 AM, Nathanaël Blanchet  > wrote:
> 
> 
> 
> Le 09/03/2017 à 10:25, Gianluca Cecchi a écrit :
>> On Wed, Mar 8, 2017 at 6:05 PM, Gianluca Cecchi
>> mailto:gianluca.cec...@gmail.com>> wrote:
>>
>>
>>
>> NOTE: during the snapshot creation I see in web admin console
>> the VM in paused state and also not responsive in both console
>> and ssh session.
>> After a couple of seconds it comes back and as a confirmation
>> I see this in its messages:
>>
>> Mar  8 17:38:57 T-ORACLE73 chronyd[616]: System clock wrong by
>> 19.077230 seconds, adjustment started
>>
>> Is this expected?
>>
>>
>>
>>
>> Possibly the default changed at some point in time, so that now it
>> saves memory and so this implies pause of VM
> Saving memory is essential in some apàplications like DB, so you
> won't bypass vm pauses for such a stuff
> 
> 
> Yes, indeed, the important thing is to have an option so that you can
> set it True or False, depending on the VM you are saving, the
> application that is running isnide it and the way you want to do backup
> of the application.
> Nevertheless, RDBMS and also other applications often have some
> mechanism to be "frozen in a consistent state" so that you can save what
> you have on disk without need to save memory to have a consistent backup.
> Oracle for example has functionality to be put in "backup mode" where
> you issue "begin backup" before the snapshot and "end backup" right
> after snapshot completion.
> I see that POstgreSQL has similar functionality (not tested myself):
> https://www.postgresql.org/docs/9.4/static/continuous-archiving.html#BACKUP-LOWLEVEL-BASE-BACKUP
> and the same for other ones.
> 
> Gianluca 
> 

Just wanted to add that freezing activity is not only important for
databases, but also for plain file systems. In order to do a consistent
backup it is important to freeze the file systems before creating a live
snapshot, and thaw it afterwards. oVirt does that automatically, but
only if the guest agent is installed and running. So, remember to have
the guest agent installed and running in the virtual machines that you
plan to backup using this mechanism.


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

Re: [ovirt-users] oVirt VM backup and restore

[Maton, Brett]

My 2cents

  I think it would be very handy to be able to choose to save the memory
state or not.

  As for anything requiring the memory state depends very much on what your
recovery procedure is.

  Gianluca, PostgreSQL pg_start / end backup works very well.  I can't
remember exactly how it works but it's something along the lines of
stopping (disk) writes to the database and storing change in WAL (redo in
oracle speak) until the backup is complete then applying any changes to the
database files on disk.
  Basically means that the database files won't change during the backup
process.

On 9 March 2017 at 10:57, Gianluca Cecchi  wrote:

> On Thu, Mar 9, 2017 at 11:39 AM, Nathanaël Blanchet 
> wrote:
>
>>
>>
>> Le 09/03/2017 à 10:25, Gianluca Cecchi a écrit :
>>
>> On Wed, Mar 8, 2017 at 6:05 PM, Gianluca Cecchi <
>> gianluca.cec...@gmail.com> wrote:
>>
>>>
>>>
>>> NOTE: during the snapshot creation I see in web admin console the VM in
>>> paused state and also not responsive in both console and ssh session.
>>> After a couple of seconds it comes back and as a confirmation I see this
>>> in its messages:
>>>
>>> Mar  8 17:38:57 T-ORACLE73 chronyd[616]: System clock wrong by 19.077230
>>> seconds, adjustment started
>>>
>>> Is this expected?
>>>
>>>
>>>
>>>
>> Possibly the default changed at some point in time, so that now it saves
>> memory and so this implies pause of VM
>>
>> Saving memory is essential in some apàplications like DB, so you won't
>> bypass vm pauses for such a stuff
>>
>>
> Yes, indeed, the important thing is to have an option so that you can set
> it True or False, depending on the VM you are saving, the application that
> is running isnide it and the way you want to do backup of the application.
> Nevertheless, RDBMS and also other applications often have some mechanism
> to be "frozen in a consistent state" so that you can save what you have on
> disk without need to save memory to have a consistent backup.
> Oracle for example has functionality to be put in "backup mode" where you
> issue "begin backup" before the snapshot and "end backup" right after
> snapshot completion.
> I see that POstgreSQL has similar functionality (not tested myself):
> https://www.postgresql.org/docs/9.4/static/continuous-
> archiving.html#BACKUP-LOWLEVEL-BASE-BACKUP
> and the same for other ones.
>
> Gianluca
>
>
> ___
> 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 VM backup and restore

[Gianluca Cecchi]

On Thu, Mar 9, 2017 at 11:39 AM, Nathanaël Blanchet 
wrote:

>
>
> Le 09/03/2017 à 10:25, Gianluca Cecchi a écrit :
>
> On Wed, Mar 8, 2017 at 6:05 PM, Gianluca Cecchi  > wrote:
>
>>
>>
>> NOTE: during the snapshot creation I see in web admin console the VM in
>> paused state and also not responsive in both console and ssh session.
>> After a couple of seconds it comes back and as a confirmation I see this
>> in its messages:
>>
>> Mar  8 17:38:57 T-ORACLE73 chronyd[616]: System clock wrong by 19.077230
>> seconds, adjustment started
>>
>> Is this expected?
>>
>>
>>
>>
> Possibly the default changed at some point in time, so that now it saves
> memory and so this implies pause of VM
>
> Saving memory is essential in some apàplications like DB, so you won't
> bypass vm pauses for such a stuff
>
>
Yes, indeed, the important thing is to have an option so that you can set
it True or False, depending on the VM you are saving, the application that
is running isnide it and the way you want to do backup of the application.
Nevertheless, RDBMS and also other applications often have some mechanism
to be "frozen in a consistent state" so that you can save what you have on
disk without need to save memory to have a consistent backup.
Oracle for example has functionality to be put in "backup mode" where you
issue "begin backup" before the snapshot and "end backup" right after
snapshot completion.
I see that POstgreSQL has similar functionality (not tested myself):
https://www.postgresql.org/docs/9.4/static/continuous-archiving.html#BACKUP-LOWLEVEL-BASE-BACKUP
and the same for other ones.

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

Re: [ovirt-users] oVirt VM backup and restore

[Yaniv Kaul]

On Thu, Mar 9, 2017 at 12:40 PM Nathanaël Blanchet  wrote:

>
>
> Le 09/03/2017 à 10:25, Gianluca Cecchi a écrit :
>
> On Wed, Mar 8, 2017 at 6:05 PM, Gianluca Cecchi  > wrote:
>
>
>
> NOTE: during the snapshot creation I see in web admin console the VM in
> paused state and also not responsive in both console and ssh session.
> After a couple of seconds it comes back and as a confirmation I see this
> in its messages:
>
> Mar  8 17:38:57 T-ORACLE73 chronyd[616]: System clock wrong by 19.077230
> seconds, adjustment started
>
> Is this expected?
>
>
>
>
> Possibly the default changed at some point in time, so that now it saves
> memory and so this implies pause of VM
>
> Saving memory is essential in some apàplications like DB, so you won't
> bypass vm pauses for such a stuff
>

In a database, you actually want to ensure all transactions are complete
for an application-complete snapshot. I don't think memory is needed.
Y.


>
> In the mean time I verified changing backup.py this way solves the problem
> (the 3.6 api deprecation still in place... ;-):
>
> $ diff backup.py backup.py.orig
> 123c123
> <
> vm.snapshots.add(params.Snapshot(description=config.get_snapshot_description(),
> vm=vm,persist_memorystate=False))
> ---
> >
> vm.snapshots.add(params.Snapshot(description=config.get_snapshot_description(),
> vm=vm))
>
> The snapshot doesn't include memory and no problem at VM OS side now
>
> Tested also getting the parameter from config file
>
> Modifications needed in this case:
>
> 1)
> $ diff backup.py backup.py.orig
> 123c123
> <
> vm.snapshots.add(params.Snapshot(description=config.get_snapshot_description(),
> vm=vm,persist_memorystate=config.get_persist_memorystate()))
> ---
> >
> vm.snapshots.add(params.Snapshot(description=config.get_snapshot_description(),
> vm=vm))
>
>
> 2)
> $ diff config.py config.py.orig
> 34d33
> < self.__persist_memorystate =
> config_parser.getboolean(section, "persist_memorystate")
> 113,116d111
> <
> <
> < def get_persist_memorystate(self):
> < return self.__persist_memorystate
>
>
> And in config file called add:
>
> # Save Memory in snapshot
> persist_memorystate=False
>
> It could be further improved if one wants to differentiate save memory for
> some VMs and not for other ones
>
> HIH other ones,
> Gianluca
>
>
> --
> Nathanaël Blanchet
>
> Supervision réseau
> Pôle Infrastrutures Informatiques
> 227 avenue Professeur-Jean-Louis-Viala
> 34193 MONTPELLIER CEDEX 5 
> Tél. 33 (0)4 67 54 84 55
> Fax  33 (0)4 67 54 84 14blanc...@abes.fr
>
> ___
> 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] "patched upgrade" from 4.0 (not appliance) => 4.1 (appliance) fails

[Yedidyah Bar David]

On Thu, Mar 9, 2017 at 12:30 PM, Nelson Lameiras <
nelson.lamei...@lyra-network.com> wrote:

> Hello,
>
> I'm trying to upgrade our ovirt-engine from 4.0 (centos manually
> installed) to 4.1.0 (appliance) using "hosted-engine --upgrade-appliance".
>

IIRC we do not support this flow currently. I agree it might be useful.
Would you like to open an RFE bz?


>
> Our test setup :
> 2 hosts with centos 7.3 with ovirt4.0 (latest updates)
> 1 ovirt-engine 4.0 (latest update)
>
> This method uses a manual backup from current engine and injects it to new
> appliance. Since "old" ovirt-engine is a manually installed 4.0 (latest
> version) as opposed to an appliance, upgrade process warns that it doesn't
> recognise the current engine with a somewhat deprecated message :
>
> [WARNING] Unable to detect engine version
> [WARNING] Unsupported upgrade path
>   This procedure has been designed and tested only for upgrading
> the engine VM from ['3.6'] to ['4.0'].
>   Any other usage is highly experimental and potentially dangerous:
> Current engine: unknown
> Selected appliance: 4.1-20170201.1.el7.centos
>   Do you want to abort the upgrade process? (Yes, No) [Yes]: no
> [WARNING] Proceeding on an unsupported and highly experimental path
>

Indeed.


>
> This fails, according to a bug already posted on
> https://bugzilla.redhat.com/show_bug.cgi?id=1420283 which is resolved in
> future 4.1.1
>

It might not be clear from the bug content, but:
1. It only affects RHV, not oVirt.
2. It does not fix your problem. It only allows the upgrade tool in version
4.1 to migrate a 3.6 engine to a _4.0_ appliance (not 4.1).


>
> So I tried to manually patch the file corrected in gerrit
> https://gerrit.ovirt.org/#/c/71965/ and - after multiple tries - it still
> fails at the end with the following error :
>
> ...
> [ INFO  ] Running engine-setup on the appliance
>   |- Preparing to restore:
>   |- - Unpacking file '/root/engine_backup.tar.gz'
>   |- FATAL: Backup was created by version '4.0' and can not be
> restored using the installed version 4.1
>

This is your real problem.


>   |- HE_APPLIANCE_ENGINE_RESTORE_FAIL
> [ ERROR ] Engine backup restore failed on the appliance
> [ ERROR ] Failed to execute stage 'Closing up': engine-backup failed
> restoring the engine backup on the appliance Please check its log on the
> appliance.
>
> When checking upgrade log, there's not much more error information other
> than :
>
> 2017-03-08 18:08:30 INFO otopi.plugins.gr_he_common.engine.health
> health._closeup:127 Running engine-setup on the appliance
> 2017-03-08 18:08:44 DEBUG otopi.plugins.otopi.dialog.human
> dialog.__logString:204 DIALOG:SEND |- Preparing to restore:
> 2017-03-08 18:08:44 DEBUG otopi.plugins.otopi.dialog.human
> dialog.__logString:204 DIALOG:SEND |- - Unpacking file
> '/root/engine_backup.tar.gz'
> 2017-03-08 18:08:44 DEBUG otopi.plugins.otopi.dialog.human
> dialog.__logString:204 DIALOG:SEND |- FATAL: Backup was
> created by version '4.0' and can not be restored using the installed
> version 4.1
> 2017-03-08 18:08:44 DEBUG otopi.plugins.otopi.dialog.human
> dialog.__logString:204 DIALOG:SEND |-
> HE_APPLIANCE_ENGINE_RESTORE_FAIL
> 2017-03-08 18:08:44 ERROR otopi.plugins.gr_he_common.engine.health
> health._closeup:154 Engine backup restore failed on the appliance
> 2017-03-08 18:08:44 DEBUG otopi.context context._executeMethod:142 method
> exception
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/site-packages/otopi/context.py", line 132, in
> _executeMethod
> method['method']()
>   File 
> "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/gr-he-common/engine/health.py",
> line 158, in _closeup
> 'engine-backup failed restoring the engine backup '
> RuntimeError: engine-backup failed restoring the engine backup on the
> appliance
>
>
Please check its log on the appliance.
> 2017-03-08 18:08:44 ERROR otopi.context context._executeMethod:151 Failed
> to execute stage 'Closing up': engine-backup failed restoring the engine
> backup on the appliance
> Please check its log on the appliance.
>

Indeed.

If you want to "fix" that, you can try to patch engine-backup - search in
it for VALID_BACKUP_RESTORE_PAIRS, there is a comment about enabling
4.0->4.1 upgrade. But as I wrote, this is not supported, and I am not aware
of anyone testing it - so things might break later on.


> 2017-03-08 18:08:44 DEBUG otopi.context context.dumpEnvironment:760
> ENVIRONMENT DUMP - BEGIN
>
> In "new" engine setup log, the only thing which catched my eye is :
>
> 2017-03-08 18:08:45 DEBUG otopi.context context.dumpEnvironment:774
> ENVIRONMENT DUMP - END
> 2017-03-08 18:08:45 DEBUG otopi.context context._executeMethod:128 Stage
> boot METHOD otopi.plugins.otopi.packagers.dnfpackager.Plugin._boot
> 2017-03-08 18:08:45 DEBUG otopi.plugins.otopi.packagers.dnfpackager
> dnfpa

Re: [ovirt-users] oVirt VM backup and restore

[Nathanaël Blanchet]

Le 09/03/2017 à 10:25, Gianluca Cecchi a écrit :
On Wed, Mar 8, 2017 at 6:05 PM, Gianluca Cecchi 
mailto:gianluca.cec...@gmail.com>> wrote:




NOTE: during the snapshot creation I see in web admin console the
VM in paused state and also not responsive in both console and ssh
session.
After a couple of seconds it comes back and as a confirmation I
see this in its messages:

Mar  8 17:38:57 T-ORACLE73 chronyd[616]: System clock wrong by
19.077230 seconds, adjustment started

Is this expected?




Possibly the default changed at some point in time, so that now it 
saves memory and so this implies pause of VM
Saving memory is essential in some apàplications like DB, so you won't 
bypass vm pauses for such a stuff
In the mean time I verified changing backup.py this way solves the 
problem (the 3.6 api deprecation still in place... ;-):


$ diff backup.py backup.py.orig
123c123
< 
vm.snapshots.add(params.Snapshot(description=config.get_snapshot_description(), 
vm=vm,persist_memorystate=False))

---
> 
vm.snapshots.add(params.Snapshot(description=config.get_snapshot_description(), 
vm=vm))


The snapshot doesn't include memory and no problem at VM OS side now

Tested also getting the parameter from config file

Modifications needed in this case:

1)
$ diff backup.py backup.py.orig
123c123
< 
vm.snapshots.add(params.Snapshot(description=config.get_snapshot_description(), 
vm=vm,persist_memorystate=config.get_persist_memorystate()))

---
> 
vm.snapshots.add(params.Snapshot(description=config.get_snapshot_description(), 
vm=vm))



2)
$ diff config.py config.py.orig
34d33
< self.__persist_memorystate = 
config_parser.getboolean(section, "persist_memorystate")

113,116d111
<
<
< def get_persist_memorystate(self):
< return self.__persist_memorystate


And in config file called add:

# Save Memory in snapshot
persist_memorystate=False

It could be further improved if one wants to differentiate save memory 
for some VMs and not for other ones


HIH other ones,
Gianluca


--
Nathanaël Blanchet

Supervision réseau
Pôle Infrastrutures Informatiques
227 avenue Professeur-Jean-Louis-Viala
34193 MONTPELLIER CEDEX 5   
Tél. 33 (0)4 67 54 84 55
Fax  33 (0)4 67 54 84 14
blanc...@abes.fr

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

[ovirt-users] "patched upgrade" from 4.0 (not appliance) => 4.1 (appliance) fails

[Nelson Lameiras]

Hello, 

I'm trying to upgrade our ovirt-engine from 4.0 (centos manually installed) to 
4.1.0 (appliance) using "hosted-engine --upgrade-appliance". 

Our test setup : 
2 hosts with centos 7.3 with ovirt4.0 (latest updates) 
1 ovirt-engine 4.0 (latest update) 

This method uses a manual backup from current engine and injects it to new 
appliance. Since "old" ovirt-engine is a manually installed 4.0 (latest 
version) as opposed to an appliance, upgrade process warns that it doesn't 
recognise the current engine with a somewhat deprecated message : 

[WARNING] Unable to detect engine version 
[WARNING] Unsupported upgrade path 
This procedure has been designed and tested only for upgrading the engine VM 
from ['3.6'] to ['4.0']. 
Any other usage is highly experimental and potentially dangerous: 
Current engine: unknown 
Selected appliance: 4.1-20170201.1.el7.centos 
Do you want to abort the upgrade process? (Yes, No) [Yes]: no 
[WARNING] Proceeding on an unsupported and highly experimental path 

This fails, according to a bug already posted on 
https://bugzilla.redhat.com/show_bug.cgi?id=1420283 which is resolved in future 
4.1.1 

So I tried to manually patch the file corrected in gerrit 
https://gerrit.ovirt.org/#/c/71965/ and - after multiple tries - it still fails 
at the end with the following error : 

... 
[ INFO ] Running engine-setup on the appliance 
|- Preparing to restore: 
|- - Unpacking file '/root/engine_backup.tar.gz' 
|- FATAL: Backup was created by version '4.0' and can not be restored using the 
installed version 4.1 
|- HE_APPLIANCE_ENGINE_RESTORE_FAIL 
[ ERROR ] Engine backup restore failed on the appliance 
[ ERROR ] Failed to execute stage 'Closing up': engine-backup failed restoring 
the engine backup on the appliance Please check its log on the appliance. 

When checking upgrade log, there's not much more error information other than : 

2017-03-08 18:08:30 INFO otopi.plugins.gr_he_common.engine.health 
health._closeup:127 Running engine-setup on the appliance 
2017-03-08 18:08:44 DEBUG otopi.plugins.otopi.dialog.human 
dialog.__logString:204 DIALOG:SEND |- Preparing to restore: 
2017-03-08 18:08:44 DEBUG otopi.plugins.otopi.dialog.human 
dialog.__logString:204 DIALOG:SEND |- - Unpacking file 
'/root/engine_backup.tar.gz' 
2017-03-08 18:08:44 DEBUG otopi.plugins.otopi.dialog.human 
dialog.__logString:204 DIALOG:SEND |- FATAL: Backup was created by version 
'4.0' and can not be restored using the installed version 4.1 
2017-03-08 18:08:44 DEBUG otopi.plugins.otopi.dialog.human 
dialog.__logString:204 DIALOG:SEND |- HE_APPLIANCE_ENGINE_RESTORE_FAIL 
2017-03-08 18:08:44 ERROR otopi.plugins.gr_he_common.engine.health 
health._closeup:154 Engine backup restore failed on the appliance 
2017-03-08 18:08:44 DEBUG otopi.context context._executeMethod:142 method 
exception 
Traceback (most recent call last): 
File "/usr/lib/python2.7/site-packages/otopi/context.py", line 132, in 
_executeMethod 
method['method']() 
File 
"/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/gr-he-common/engine/health.py",
 line 158, in _closeup 
'engine-backup failed restoring the engine backup ' 
RuntimeError: engine-backup failed restoring the engine backup on the appliance 
Please check its log on the appliance. 
2017-03-08 18:08:44 ERROR otopi.context context._executeMethod:151 Failed to 
execute stage 'Closing up': engine-backup failed restoring the engine backup on 
the appliance 
Please check its log on the appliance. 
2017-03-08 18:08:44 DEBUG otopi.context context.dumpEnvironment:760 ENVIRONMENT 
DUMP - BEGIN 

In "new" engine setup log, the only thing which catched my eye is : 

2017-03-08 18:08:45 DEBUG otopi.context context.dumpEnvironment:774 ENVIRONMENT 
DUMP - END 
2017-03-08 18:08:45 DEBUG otopi.context context._executeMethod:128 Stage boot 
METHOD otopi.plugins.otopi.packagers.dnfpackager.Plugin._boot 
2017-03-08 18:08:45 DEBUG otopi.plugins.otopi.packagers.dnfpackager 
dnfpackager._boot:163 Cannot initialize minidnf 
Traceback (most recent call last): 
File "/usr/share/otopi/plugins/otopi/packagers/dnfpackager.py", line 150, in 
_boot 
constants.PackEnv.DNF_DISABLED_PLUGINS 
File "/usr/share/otopi/plugins/otopi/packagers/dnfpackager.py", line 60, in 
_getMiniDNF 
from otopi import minidnf 
File "/usr/lib/python2.7/site-packages/otopi/minidnf.py", line 16, in  
import dnf 
ImportError: No module named dnf 
2017-03-08 18:08:45 DEBUG otopi.context context.dumpEnvironment:760 ENVIRONMENT 
DUMP - BEGIN 

I'm not sure if my patched file ( runvm.py ) should be enough to make it work, 
but maybe this can bring some new information to you. 
Really hopping that 4.1.1 oVirt will resolve this issue as we are eager to 
start using appliances. 

(I can provide you with more/full log files if necessary) 

cordialement, regards, 


Nelson LAMEIRAS 
Ingénieur Systèmes et Réseaux / Systems and Networks engineer 
Tel: +33 5 32 09 09 70 
nelson.lamei...@lyra-network.com 

www.lyra-network.com | www.

Re: [ovirt-users] oVirt VM backup and restore

[Juan Hernández]

On 03/09/2017 11:11 AM, Gianluca Cecchi wrote:
> On Thu, Mar 9, 2017 at 10:58 AM, Juan Hernández  > wrote:
> 
> 
> 
> Very good point Gialuca, you are right, the 'persist_memorystate' flag
> is 'true' by default, and that makes the pause longer. Would you be so
> kind to add it to the 'vm_backup.py' example that is part of version 4
> of the SDK?
> 
> 
> 
> https://github.com/oVirt/ovirt-engine-sdk/blob/master/sdk/examples/vm_backup.py#L143-L151
> 
> 
> 
> (Note that that Gibhub is just a mirror, the change needs to be submited
> using gerrit.ovirt.org ).
> 
> 
> 
> I already verified (on a 4.1 infra) that changing vm_backup.py
> downloaded yesterday from master this way (apart connection paramters):
> 
> $ diff vm_backup.py vm_backup.py.orig 
>  150d149
> < persist_memorystate=False,
> 
> I get the backup result and snapshot is correctly without memory saved
> (and no pause at VM side)
> 
> In engine events I get:
> 
> Mar 9, 2017 10:50:39 AM Snapshot
> 'Oracle7-backup-c6bf637e-cdeb-4923-a39f-55a14d7bad7b' deletion for VM
> 'Oracle7' has been completed.
> Mar 9, 2017 10:49:48 AM Backup of virtual machine 'Oracle7' using
> snapshot 'Oracle7-backup-c6bf637e-cdeb-4923-a39f-55a14d7bad7b' is completed.
> Mar 9, 2017 10:49:48 AM Snapshot
> 'Oracle7-backup-c6bf637e-cdeb-4923-a39f-55a14d7bad7b' deletion for VM
> 'Oracle7' was initiated by admin@internal-authz.
> Mar 9, 2017 10:49:47 AM  Disk Oracle7_Disk1 was successfully detached
> from VM c7testovn1 by admin@internal-authz.
> Mar 9, 2017 10:49:45 AM Disk Oracle7_Disk1 was successfully attached to
> VM c7testovn1 by admin@internal-authz.
> Mar 9, 2017 10:49:41 AM Snapshot
> 'Oracle7-backup-c6bf637e-cdeb-4923-a39f-55a14d7bad7b' creation for VM
> 'Oracle7' has been completed.
> Mar 9, 2017 10:49:29 AM Snapshot
> 'Oracle7-backup-c6bf637e-cdeb-4923-a39f-55a14d7bad7b' creation for VM
> 'Oracle7' was initiated by admin@internal-authz.
> Mar 9, 2017 10:49:28 AM Backup of virtual machine 'Oracle7' using
> snapshot 'Oracle7-backup-c6bf637e-cdeb-4923-a39f-55a14d7bad7b' is starting.
> 
> 
> I have almost no experience in gerrit/github, unfortunately... only a
> beginner experience in svn ... ;-)
> If you give me some pointers I can try to apply what you asked...
> 
> Gianluca

I see that you already have a gerrit.ovirt.org, so it shouldn't be
difficult. The initial setup should be like this:

  $ git config --global user.name youruser
  $ git config --global user.email your@email
  $ git clone ssh://youru...@gerrit.ovirt.org:29418/ovirt-engine-sdk
  $ gitdir=$(git rev-parse --git-dir); scp -p -P 29418
youru...@gerrit.ovirt.org:hooks/commit-msg ${gitdir}/hooks/

Then, to submit the patch:

  $ cd ovirt-engine-sdk
  $ Edit the vm_backup.py file, and make your changes.
  $ git commit -a -s
  $ git push origin HEAD:refs/for/master

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

Re: [ovirt-users] oVirt VM backup and restore

[Gianluca Cecchi]

On Thu, Mar 9, 2017 at 10:58 AM, Juan Hernández  wrote:

>
>
> Very good point Gialuca, you are right, the 'persist_memorystate' flag
> is 'true' by default, and that makes the pause longer. Would you be so
> kind to add it to the 'vm_backup.py' example that is part of version 4
> of the SDK?
>
>
> https://github.com/oVirt/ovirt-engine-sdk/blob/master/
> sdk/examples/vm_backup.py#L143-L151
>
> (Note that that Gibhub is just a mirror, the change needs to be submited
> using gerrit.ovirt.org).
>
>
>
I already verified (on a 4.1 infra) that changing vm_backup.py downloaded
yesterday from master this way (apart connection paramters):

$ diff vm_backup.py vm_backup.py.orig
 150d149
< persist_memorystate=False,

I get the backup result and snapshot is correctly without memory saved (and
no pause at VM side)

In engine events I get:

Mar 9, 2017 10:50:39 AM Snapshot
'Oracle7-backup-c6bf637e-cdeb-4923-a39f-55a14d7bad7b' deletion for VM
'Oracle7' has been completed.
Mar 9, 2017 10:49:48 AM Backup of virtual machine 'Oracle7' using snapshot
'Oracle7-backup-c6bf637e-cdeb-4923-a39f-55a14d7bad7b' is completed.
Mar 9, 2017 10:49:48 AM Snapshot
'Oracle7-backup-c6bf637e-cdeb-4923-a39f-55a14d7bad7b' deletion for VM
'Oracle7' was initiated by admin@internal-authz.
Mar 9, 2017 10:49:47 AM  Disk Oracle7_Disk1 was successfully detached from
VM c7testovn1 by admin@internal-authz.
Mar 9, 2017 10:49:45 AM Disk Oracle7_Disk1 was successfully attached to VM
c7testovn1 by admin@internal-authz.
Mar 9, 2017 10:49:41 AM Snapshot
'Oracle7-backup-c6bf637e-cdeb-4923-a39f-55a14d7bad7b' creation for VM
'Oracle7' has been completed.
Mar 9, 2017 10:49:29 AM Snapshot
'Oracle7-backup-c6bf637e-cdeb-4923-a39f-55a14d7bad7b' creation for VM
'Oracle7' was initiated by admin@internal-authz.
Mar 9, 2017 10:49:28 AM Backup of virtual machine 'Oracle7' using snapshot
'Oracle7-backup-c6bf637e-cdeb-4923-a39f-55a14d7bad7b' is starting.


I have almost no experience in gerrit/github, unfortunately... only a
beginner experience in svn ... ;-)
If you give me some pointers I can try to apply what you asked...

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

Re: [ovirt-users] oVirt VM backup and restore

[Juan Hernández]

On 03/09/2017 10:25 AM, Gianluca Cecchi wrote:
> On Wed, Mar 8, 2017 at 6:05 PM, Gianluca Cecchi
> mailto:gianluca.cec...@gmail.com>> wrote:
> 
> 
> 
> NOTE: during the snapshot creation I see in web admin console the VM
> in paused state and also not responsive in both console and ssh session.
> After a couple of seconds it comes back and as a confirmation I see
> this in its messages:
> 
> Mar  8 17:38:57 T-ORACLE73 chronyd[616]: System clock wrong by
> 19.077230 seconds, adjustment started
> 
> Is this expected?
> 
> 
> 
> 
> Possibly the default changed at some point in time, so that now it saves
> memory and so this implies pause of VM
> 
> In the mean time I verified changing backup.py this way solves the
> problem (the 3.6 api deprecation still in place... ;-):
> 
> $ diff backup.py backup.py.orig 
> 123c123
> <
> vm.snapshots.add(params.Snapshot(description=config.get_snapshot_description(),
> vm=vm,persist_memorystate=False))
> ---
>>
> vm.snapshots.add(params.Snapshot(description=config.get_snapshot_description(),
> vm=vm))
> 
> The snapshot doesn't include memory and no problem at VM OS side now
> 
> Tested also getting the parameter from config file
> 
> Modifications needed in this case:
> 
> 1)
> $ diff backup.py backup.py.orig 
> 123c123
> <
> vm.snapshots.add(params.Snapshot(description=config.get_snapshot_description(),
> vm=vm,persist_memorystate=config.get_persist_memorystate()))
> ---
>>
> vm.snapshots.add(params.Snapshot(description=config.get_snapshot_description(),
> vm=vm))
> 
> 
> 2)
> $ diff config.py config.py.orig 
> 34d33
> < self.__persist_memorystate =
> config_parser.getboolean(section, "persist_memorystate")
> 113,116d111
> < 
> < 
> < def get_persist_memorystate(self):
> < return self.__persist_memorystate
> 
> 
> And in config file called add:
> 
> # Save Memory in snapshot
> persist_memorystate=False
> 
> It could be further improved if one wants to differentiate save memory
> for some VMs and not for other ones
> 
> HIH other ones,
> Gianluca
> 

Very good point Gialuca, you are right, the 'persist_memorystate' flag
is 'true' by default, and that makes the pause longer. Would you be so
kind to add it to the 'vm_backup.py' example that is part of version 4
of the SDK?


https://github.com/oVirt/ovirt-engine-sdk/blob/master/sdk/examples/vm_backup.py#L143-L151

(Note that that Gibhub is just a mirror, the change needs to be submited
using gerrit.ovirt.org).





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

Re: [ovirt-users] oVirt backup and VM pauses.

[Misak Khachatryan]

Thank You Gianluca, reading it right now !!!

Best regards,
Misak Khachatryan


On Thu, Mar 9, 2017 at 1:27 PM, Gianluca Cecchi
 wrote:
> On Thu, Mar 9, 2017 at 7:34 AM, Maton, Brett 
> wrote:
>>
>> I noticed similar behavior, I think if the memory state isn't backed-up
>> then the machines won't be paused.
>> Not seen an option in script to 'flip' the flag, but then again I haven't
>> looked at the script in enough detail to see what needs changing.
>>
>
>
> See my solution in another thread here:
> http://lists.ovirt.org/pipermail/users/2017-March/080338.html
>
> HIH,
> Gianluca
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] oVirt backup and VM pauses.

[Gianluca Cecchi]

On Thu, Mar 9, 2017 at 7:34 AM, Maton, Brett 
wrote:

> I noticed similar behavior, I think if the memory state isn't backed-up
> then the machines won't be paused.
> Not seen an option in script to 'flip' the flag, but then again I haven't
> looked at the script in enough detail to see what needs changing.
>
>

See my solution in another thread here:
http://lists.ovirt.org/pipermail/users/2017-March/080338.html

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

Re: [ovirt-users] oVirt VM backup and restore

[Gianluca Cecchi]

On Wed, Mar 8, 2017 at 6:05 PM, Gianluca Cecchi 
wrote:

>
>
> NOTE: during the snapshot creation I see in web admin console the VM in
> paused state and also not responsive in both console and ssh session.
> After a couple of seconds it comes back and as a confirmation I see this
> in its messages:
>
> Mar  8 17:38:57 T-ORACLE73 chronyd[616]: System clock wrong by 19.077230
> seconds, adjustment started
>
> Is this expected?
>
>
>
>
Possibly the default changed at some point in time, so that now it saves
memory and so this implies pause of VM

In the mean time I verified changing backup.py this way solves the problem
(the 3.6 api deprecation still in place... ;-):

$ diff backup.py backup.py.orig
123c123
<
vm.snapshots.add(params.Snapshot(description=config.get_snapshot_description(),
vm=vm,persist_memorystate=False))
---
>
vm.snapshots.add(params.Snapshot(description=config.get_snapshot_description(),
vm=vm))

The snapshot doesn't include memory and no problem at VM OS side now

Tested also getting the parameter from config file

Modifications needed in this case:

1)
$ diff backup.py backup.py.orig
123c123
<
vm.snapshots.add(params.Snapshot(description=config.get_snapshot_description(),
vm=vm,persist_memorystate=config.get_persist_memorystate()))
---
>
vm.snapshots.add(params.Snapshot(description=config.get_snapshot_description(),
vm=vm))


2)
$ diff config.py config.py.orig
34d33
< self.__persist_memorystate =
config_parser.getboolean(section, "persist_memorystate")
113,116d111
<
<
< def get_persist_memorystate(self):
< return self.__persist_memorystate


And in config file called add:

# Save Memory in snapshot
persist_memorystate=False

It could be further improved if one wants to differentiate save memory for
some VMs and not for other ones

HIH other ones,
Gianluca
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Shrink gluster logical volume under Ovirt 4.0

[Ian Neilsen]

Hi Sahina

I was shrinking the underlying LV/filesystem of bricks associated with the
gluster volume.
Im successfully all the way through doing this now.

I place cluster into global maintenance and went about resizing the
lv/filesystem for each server.

I think it's working. :-)

Thanks for the reply
Ian


On 9 March 2017 at 16:44, Sahina Bose  wrote:

> Are you shrinking the gluster volume by removing bricks, or are you
> shrinking the underlying LV/filesystem of the bricks associated with
> gluster volume?
> If latter, you need to move storage domain to maintenance and umount from
> all hosts.
>
> On Thu, Mar 9, 2017 at 4:56 AM, Ian Neilsen  wrote:
>
>>
>> Hi all
>>
>> I need to shrink/reduce the size of a gluster logical volume under Ovirt
>> 4.0.
>>
>> Is there anything I should be aware of before reducing the file system
>> and logical volume on my servers?
>>
>> I ask because I see under "df -h" the following;
>> 192.168.3.10:data   5.7T  3.4G  5.7T   1% /rhev/data-center/mnt/glusterS
>> D/192.168.3.10:data
>>
>> The storage domain is not connected yet via oVirt manager, well at least
>> it isnt showing. Im running in hosted mode converged.
>>
>>
>> Thanks in advance
>> --
>> Ian Neilsen
>>
>> Mobile: 0424 379 762
>> Linkedin: http://au.linkedin.com/in/ianneilsen
>> Twitter : ineilsen
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>


-- 
Ian Neilsen

Mobile: 0424 379 762
Linkedin: http://au.linkedin.com/in/ianneilsen
Twitter : ineilsen
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users