[ovirt-users] VM pools broken in 4.3

[Rik Theys]

Hi,

It seems VM pools are completely broken since our upgrade to 4.3. Is
anybody else also experiencing this issue?

Only a single instance from a pool can be used. Afterwards the pool
becomes unusable due to a lock not being released. Once ovirt-engine is
restarted, another (single) VM from a pool can be used.

I've added my findings to bug 1462236, but I'm no longer sure the issue
is the same as the one initially reported.

When the first VM of a pool is started:

2019-05-14 13:26:46,058+02 INFO  
[org.ovirt.engine.core.vdsbroker.IsVmDuringInitiatingVDSCommand] (default 
task-6) [e3c5745c-e593-4aed-ba67-b173808140e8] START, 
IsVmDuringInitiatingVDSCommand( 
IsVmDuringInitiatingVDSCommandParameters:{vmId='d8a99676-d520-425e-9974-1b1efe6da8a5'}),
 log id: 2fb4f7f5
2019-05-14 13:26:46,058+02 INFO  
[org.ovirt.engine.core.vdsbroker.IsVmDuringInitiatingVDSCommand] (default 
task-6) [e3c5745c-e593-4aed-ba67-b173808140e8] FINISH, 
IsVmDuringInitiatingVDSCommand, return: false, log id: 2fb4f7f5
2019-05-14 13:26:46,208+02 INFO  [org.ovirt.engine.core.bll.VmPoolHandler] 
(default task-6) [e3c5745c-e593-4aed-ba67-b173808140e8] Lock Acquired to object 
'EngineLock:{exclusiveLocks='[d8a99676-d520-425e-9974-1b1efe6da8a5=VM]', 
sharedLocks=''}'

-> it has acquired a lock (lock1)

2019-05-14 13:26:46,247+02 INFO  
[org.ovirt.engine.core.bll.AttachUserToVmFromPoolAndRunCommand] (default 
task-6) [e3c5745c-e593-4aed-ba67-b173808140e8] Lock Acquired to object 
'EngineLock:{exclusiveLocks='[a5bed59c-d2fe-4fe4-bff7-52efe089ebd6=USER_VM_POOL]',
 sharedLocks=''}'

-> it has acquired another lock (lock2)

2019-05-14 13:26:46,352+02 INFO  
[org.ovirt.engine.core.bll.AttachUserToVmFromPoolAndRunCommand] (default 
task-6) [e3c5745c-e593-4aed-ba67-b173808140e8] Running command: 
AttachUserToVmFromPoolAndRunCommand internal: false. Entities affected :  ID: 
4c622213-e5f4-4032-8639-643174b698cc Type: VmPoolAction group 
VM_POOL_BASIC_OPERATIONS with role type USER
2019-05-14 13:26:46,393+02 INFO  
[org.ovirt.engine.core.bll.AddPermissionCommand] (default task-6) 
[e3c5745c-e593-4aed-ba67-b173808140e8] Running command: AddPermissionCommand 
internal: true. Entities affected :  ID: d8a99676-d520-425e-9974-1b1efe6da8a5 
Type: VMAction group MANIPULATE_PERMISSIONS with role type USER
2019-05-14 13:26:46,433+02 INFO  
[org.ovirt.engine.core.bll.AttachUserToVmFromPoolAndRunCommand] (default 
task-6) [e3c5745c-e593-4aed-ba67-b173808140e8] Succeeded giving user 
'a5bed59c-d2fe-4fe4-bff7-52efe089ebd6' permission to Vm 
'd8a99676-d520-425e-9974-1b1efe6da8a5'
2019-05-14 13:26:46,608+02 INFO  
[org.ovirt.engine.core.vdsbroker.IsVmDuringInitiatingVDSCommand] (default 
task-6) [e3c5745c-e593-4aed-ba67-b173808140e8] START, 
IsVmDuringInitiatingVDSCommand( 
IsVmDuringInitiatingVDSCommandParameters:{vmId='d8a99676-d520-425e-9974-1b1efe6da8a5'}),
 log id: 67acc561
2019-05-14 13:26:46,608+02 INFO  
[org.ovirt.engine.core.vdsbroker.IsVmDuringInitiatingVDSCommand] (default 
task-6) [e3c5745c-e593-4aed-ba67-b173808140e8] FINISH, 
IsVmDuringInitiatingVDSCommand, return: false, log id: 67acc561
2019-05-14 13:26:46,719+02 INFO  [org.ovirt.engine.core.bll.RunVmCommand] 
(default task-6) [e3c5745c-e593-4aed-ba67-b173808140e8] Running 
command:RunVmCommand internal: true. Entities affected :  ID: 
d8a99676-d520-425e-9974-1b1efe6da8a5 Type: VMAction group RUN_VM with role type 
USER
2019-05-14 13:26:46,791+02 INFO  
[org.ovirt.engine.core.vdsbroker.UpdateVmDynamicDataVDSCommand] (default 
task-6) [e3c5745c-e593-4aed-ba67-b173808140e8] START, 
UpdateVmDynamicDataVDSCommand( 
UpdateVmDynamicDataVDSCommandParameters:{hostId='null', 
vmId='d8a99676-d520-425e-9974-1b1efe6da8a5', 
vmDynamic='org.ovirt.engine.core.common.businessentities.VmDynamic@6db8c94d'}), 
log id: 2c110e4
2019-05-14 13:26:46,795+02 INFO  
[org.ovirt.engine.core.vdsbroker.UpdateVmDynamicDataVDSCommand] (default 
task-6) [e3c5745c-e593-4aed-ba67-b173808140e8] FINISH, 
UpdateVmDynamicDataVDSCommand, return: , log id: 2c110e4
2019-05-14 13:26:46,804+02 INFO  
[org.ovirt.engine.core.vdsbroker.CreateVDSCommand] (default task-6) 
[e3c5745c-e593-4aed-ba67-b173808140e8] START,CreateVDSCommand( 
CreateVDSCommandParameters:{hostId='eec7ec2b-cae1-4bb9-b933-4dff47a70bdb', 
vmId='d8a99676-d520-425e-9974-1b1efe6da8a5', vm='VM [stud-c7-1]'}), log id: 
71d599f2
2019-05-14 13:26:46,809+02 INFO  
[org.ovirt.engine.core.vdsbroker.vdsbroker.CreateBrokerVDSCommand] (default 
task-6) [e3c5745c-e593-4aed-ba67-b173808140e8] START, 
CreateBrokerVDSCommand(HostName = studvirt1, 
CreateVDSCommandParameters:{hostId='eec7ec2b-cae1-4bb9-b933-4dff47a70bdb', 
vmId='d8a99676-d520-425e-9974-1b1efe6da8a5', vm='VM [stud-c7-1]'}), log id: 
3aa6b5ff
2019-05-14 13:26:46,836+02 INFO  
[org.ovirt.engine.core.vdsbroker.builder.vminfo.VmInfoBuildUtils] (default 
task-6) [e3c5745c-e593-4aed-ba67-b173808140e8] Kernel FIPS - Guid: 
eec7ec2b-cae1-4bb9-b933-4dff47a70bdb fips: false
2019-05-14 13:26:46,903+02 INFO  
[org.ovirt.engine.core.vdsbro

Re: [ovirt-users] VM Pools and time of creating VMs

[Sven Kieske]

This is however not the main difference between pools and single
vms, because you can also create thin single vms without a pool.

pools are for mass-starting vms all dependent on the same template.
for example in a virtual desktop infrastructure (VDI) this makes sense.

On 17/02/15 19:33, Itamar Heim wrote:
> pool defaults to thinly provisioned VMs (qcow2). New (server) VMs
> default to raw/clone (full copy)

HTH

-- 
Mit freundlichen Grüßen / Regards

Sven Kieske

Systemadministrator
Mittwald CM Service GmbH & Co. KG
Königsberger Straße 6
32339 Espelkamp
T: +49-5772-293-100
F: +49-5772-293-333
https://www.mittwald.de
Geschäftsführer: Robert Meyer
St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen
Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] VM Pools and time of creating VMs

[Itamar Heim]

On 02/17/2015 08:10 PM, shimano wrote:

Hi everyone,

What's the difference in mechanisms of creating virtual machines between
normal create VM from template and create it via VM Pool?

I see that if I create VM in normal way, it takes much much more time
then create via VM Pool. It's a little bit strange for me.



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



pool defaults to thinly provisioned VMs (qcow2). New (server) VMs 
default to raw/clone (full copy)

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

[ovirt-users] VM Pools and time of creating VMs

[shimano]

Hi everyone,

What's the difference in mechanisms of creating virtual machines between
normal create VM from template and create it via VM Pool?

I see that if I create VM in normal way, it takes much much more time then
create via VM Pool. It's a little bit strange for me.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] VM Pools

[Omer Frenkel]

- Original Message -
> From: "Maurice James" 
> To: "users" 
> Sent: Monday, July 14, 2014 3:48:09 PM
> Subject: [ovirt-users] VM Pools
> 
> Are changes made to VMs in pools by the administrator persistent only for
> that VM or are they persistent across the pool? For example If I need to
> update the Pool OS via yum or windows update. I f I log on as the admin via
> the admin portal, spin up one of the VMs from the pool and run the updates
> then shut down again. Will those updates be persistent on only that 1 VM or
> the entire pool?
> 

only this vm, to get what you want, you need to use template versions [1]
which require you: 
1. to select 'latest' when creating the pool
2. after updating the vm you like, create a version from it to the template the 
pool was create from.


[1] http://www.ovirt.org/index.php?title=Features/Template_Versions

> ___
> 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] VM Pools

[Maurice James]

Are changes made to VMs in pools by the administrator persistent only for that 
VM or are they persistent across the pool? For example If I need to update the 
Pool OS via yum or windows update. I f I log on as the admin via the admin 
portal, spin up one of the VMs from the pool and run the updates then shut down 
again. Will those updates be persistent on only that 1 VM or the entire pool? 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users