Re: [ovirt-users] help.. vm trapped in limbo aka can't acquire exclusive lock

[Arik Hadas]

Hi Jeremiah,

Thanks for providing the relevant information from the engine log.

A fix was just merged to 3.4 branch.
For more info about the bug and the solution see: 
https://bugzilla.redhat.com/1086280

Note that in the meantime you can unlock the VM by restarting the engine as Roy 
mentioned.

Regards,
Arik

- Original Message -
> 
> 
> - Forwarded Message -
> > From: "Jeremiah Jahn" 
> > To: "Yair Zaslavsky" 
> > Cc: users@ovirt.org
> > Sent: Thursday, April 10, 2014 5:48:24 AM
> > Subject: Re: [ovirt-users] help.. vm trapped in limbo aka can't acquire
> > exclusive lock
> > 
> > here's the start of the problem. If you really want the WHOLE log I
> > can do that too, but this is where I ask it to migrate, and where it
> > fails. After which it just keeps repeating that it can't get the lock.
> > 
> > 
> > 
> > 2014-04-09 14:18:48,050 INFO
> > [org.ovirt.engine.core.bll.MigrateVmCommand]
> > (DefaultQuartzScheduler_Worker-33) Lock freed to object EngineLock
> > [exclusiveLocks= key:
> > 0af0aaf6-85cf-4c67-9744-68a63601ab85 value: VM
> > , sharedLocks= ]
> > 2014-04-09 14:19:32,177 INFO
> > [org.ovirt.engine.core.bll.MigrateVmCommand] (ajp--127.0.0.1-8702-1)
> > [4350ffd] Lock Acquired to object EngineLock [exclusiveLocks= key:
> > b0108933-deb2-4fa0-ae74-e10cefbb0cea value: VM
> > , sharedLocks= ]
> > 2014-04-09 14:19:32,199 INFO
> > [org.ovirt.engine.core.bll.MigrateVmCommand]
> > (org.ovirt.thread.pool-6-thread-16) [4350ffd] Running command:
> > MigrateVmCommand internal: false. Entities affected :  ID:
> > b0108933-deb2-4fa0-ae74-e10cefbb0cea Type: VM
> > 2014-04-09 14:19:32,203 INFO
> > [org.ovirt.engine.core.bll.scheduling.policyunits.HaReservationWeightPolicyUnit]
> > (org.ovirt.thread.pool-6-thread-16) [4350ffd] Started HA reservation
> > scoring method
> > 2014-04-09 14:19:32,208 INFO
> > [org.ovirt.engine.core.vdsbroker.MigrateVDSCommand]
> > (org.ovirt.thread.pool-6-thread-16) [4350ffd] START,
> > MigrateVDSCommand(HostName = kvm01.virt, HostId =
> > fa455012-b929-4805-a5c1-50e6c788039a,
> > vmId=b0108933-deb2-4fa0-ae74-e10cefbb0cea, srcHost=10.10.4.31,
> > dstVdsId=ce6b5b29-778f-4812-97b5-950f3d3b6c71,
> > dstHost=10.10.4.34:54321, migrationMethod=ONLINE,
> > tunnelMigration=false, migrationDowntime=0), log id: 745cd0ba
> > 2014-04-09 14:19:32,209 INFO
> > [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateBrokerVDSCommand]
> > (org.ovirt.thread.pool-6-thread-16) [4350ffd]
> > VdsBroker::migrate::Entered
> > (vm_guid=b0108933-deb2-4fa0-ae74-e10cefbb0cea, srcHost=10.10.4.31,
> > dstHost=10.10.4.34:54321,  method=online
> > 2014-04-09 14:19:32,210 INFO
> > [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateBrokerVDSCommand]
> > (org.ovirt.thread.pool-6-thread-16) [4350ffd] START,
> > MigrateBrokerVDSCommand(HostName = kvm01.virt, HostId =
> > fa455012-b929-4805-a5c1-50e6c788039a,
> > vmId=b0108933-deb2-4fa0-ae74-e10cefbb0cea, srcHost=10.10.4.31,
> > dstVdsId=ce6b5b29-778f-4812-97b5-950f3d3b6c71,
> > dstHost=10.10.4.34:54321, migrationMethod=ONLINE,
> > tunnelMigration=false, migrationDowntime=0), log id: 5de39b66
> > 2014-04-09 14:19:32,224 INFO
> > [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateBrokerVDSCommand]
> > (org.ovirt.thread.pool-6-thread-16) [4350ffd] FINISH,
> > MigrateBrokerVDSCommand, log id: 5de39b66
> > 2014-04-09 14:19:32,228 INFO
> > [org.ovirt.engine.core.vdsbroker.MigrateVDSCommand]
> > (org.ovirt.thread.pool-6-thread-16) [4350ffd] FINISH,
> > MigrateVDSCommand, return: MigratingFrom, log id: 745cd0ba
> > 2014-04-09 14:19:32,233 INFO
> > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> > (org.ovirt.thread.pool-6-thread-16) [4350ffd] Correlation ID: 4350ffd,
> > Job ID: 433cbdce-90b3-41ed-bbfe-3a10ea2c6616, Call Stack: null, Custom
> > Event ID: -1, Message: Migration started (VM: web.judici, Source:
> > kvm01.virt, Destination: kvm04, User: admin).
> > 2014-04-09 14:19:33,465 INFO
> > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo]
> > (DefaultQuartzScheduler_Worker-62) RefreshVmList vm id
> > b0108933-deb2-4fa0-ae74-e10cefbb0cea is migrating to vds kvm04
> > ignoring it in the refresh until migration is done
> > 2014-04-09 14:19:34,268 INFO
> > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo]
> > (DefaultQuartzScheduler_Worker-74) VM web.judici
> > b0108933-deb2-4fa0-ae74-e10cefbb0cea moved from MigratingFrom --> Up
> > 2014-04-09 14:19:34,269 INFO
> > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo]
> > (DefaultQuartzScheduler_Worker-74) Adding VM
> > b0108933-deb2-4fa0-ae74-e10cefbb0cea to re-run list
> > 2014-04-09 14:19:34,269 INFO
> > [org.ovirt.engine.core.vdsbroker.vdsbroker.FullListVdsCommand]
> > (DefaultQuartzScheduler_Worker-74) START, FullListVdsCommand(HostName
> > = kvm01.virt, HostId = fa455012-b929-4805-a5c1-50e6c788039a,
> > vds=Host[kvm01.virt], vmIds=[b0108933-deb2-4fa0-ae74-e10cefbb0cea]),
> > log id: 6936226f
> > 2014-04-09 14:19:34,279 INFO
> > [org.ovirt.engine.core.vdsbroker.vdsbroker.Full

Re: [ovirt-users] Import OVA

[Arik Hadas]

If that's a VMware-compatible OVA then a better approach (the approach that
was previously proposed requires you to convert the vmdk disks separately)
would be to copy the OVA file to one of the hosts managed by oVirt, change
its permissions to vdsm:kvm, and import it using the import dialog in the
virtual machines tab.

On Tue, Apr 25, 2017 at 6:34 PM, Andy  wrote:

> Ahh makes sense,  will give that a try.  thank you much for the info.
>
>
> On Tuesday, April 25, 2017, 8:21:43 AM EDT, Fred Rolland <
> froll...@redhat.com> wrote:
> Hi,
>
> You can upload a disk in the "disks" tab.
> You will need to create the VM manually, and attached the disk to it.
>
> Regards,
>
> Fred
>
> On Tue, Apr 25, 2017 at 3:06 PM, Andy Kress  wrote:
>
> All,
>
> I am using the latest version of Ovirt 4.1.1.8-1 running in CentOS 7.3 and
> would like to import an OVA.  Since it appears the image-uploader utility
> is deprecated, does anyone have information on how to accomplish this?
> I cannot import it through the UI directly and rather than importing the
> OVA to a VMWARE environment and pulling it in, I would like to know how to
> directly do this.
>
> Thanks
>
> AK
> __ _
> 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] Import OVA

[Arik Hadas]

On Tue, Apr 25, 2017 at 8:26 PM, Andy Kress  wrote:

> This is a KVM native OVA.  Other than pulling apart the archive and
> importing the disks directly, then attaching the disk to a VM, is there a
> more efficient process??
>

Unfortunately, not yet. A better process is planned for 4.2:
https://github.com/oVirt/ovirt-site/pull/828/files


>
> Thanks
>
> On Apr 25, 2017, at 12:02 PM, Arik Hadas  wrote:
>
> If that's a VMware-compatible OVA then a better approach (the approach
> that was previously proposed requires you to convert the vmdk disks
> separately) would be to copy the OVA file to one of the hosts managed by
> oVirt, change its permissions to vdsm:kvm, and import it using the import
> dialog in the virtual machines tab.
>
> On Tue, Apr 25, 2017 at 6:34 PM, Andy  wrote:
>
>> Ahh makes sense,  will give that a try.  thank you much for the info.
>>
>>
>> On Tuesday, April 25, 2017, 8:21:43 AM EDT, Fred Rolland <
>> froll...@redhat.com> wrote:
>> Hi,
>>
>> You can upload a disk in the "disks" tab.
>> You will need to create the VM manually, and attached the disk to it.
>>
>> Regards,
>>
>> Fred
>>
>> On Tue, Apr 25, 2017 at 3:06 PM, Andy Kress 
>> wrote:
>>
>> All,
>>
>> I am using the latest version of Ovirt 4.1.1.8-1 running in CentOS 7.3
>> and would like to import an OVA.  Since it appears the image-uploader
>> utility is deprecated, does anyone have information on how to accomplish
>> this?
>> I cannot import it through the UI directly and rather than importing the
>> OVA to a VMWARE environment and pulling it in, I would like to know how to
>> directly do this.
>>
>> Thanks
>>
>> AK
>> __ _
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/ mailman/listinfo/users
>> <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

[ovirt-users] Feature: enhanced OVA support

[Arik Hadas]

Hi everyone,

We would like to share our plan for extending the currently provided
support for OVA files with:
1. Support for uploading OVA.
2. Support for exporting a VM/template as OVA.
3. Support for importing OVA that was generated by oVirt (today, we only
support those that are VMware-compatible).
4. Support for downloading OVA.

This can be found on the feature page

.

Your feedback and cooperation will be highly appreciated.

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

Re: [ovirt-users] Feature: enhanced OVA support

[Arik Hadas]

On Mon, May 15, 2017 at 6:11 PM, Derek Atkins  wrote:

> Hi,
>
> Arik Hadas  writes:
>
> > Hi everyone,
> >
> > We would like to share our plan for extending the currently provided
> support
> > for OVA files with:
> > 1. Support for uploading OVA.
> > 2. Support for exporting a VM/template as OVA.
> > 3. Support for importing OVA that was generated by oVirt (today, we only
> > support those that are VMware-compatible).
> > 4. Support for downloading OVA.
> >
> > This can be found on the feature page.
> >
> > Your feedback and cooperation will be highly appreciated.
>
> Sounds like a great plan.
>
> What's the chance that the export would enable an OVA that could be
> loaded back into VMware?
>

I'm afraid that would be too costly.
As far as I know, there are pretty good conversion tools for converting VMs
from KVM to VMware today [1] (which, btw, I consider to be a strength as
Eduardo mentioned before. we certainly not in favor of vendor lock-in). It
would only make sense for them to support converting the OVA we produce,
much like we extended virt-v2v for converting VMware's OVA not long ago -
and I'm pretty sure they won't object to do this, they have all the
building blocks - getting a VM as a single archive that complies with the
OVA standard should make it easy for them).

[1] https://www.youtube.com/watch?v=DJedam7TJWo (the relevant part starts
at 14:40)


>
> > Thanks,
> > Arik
>
> -derek
>
> --
>Derek Atkins 617-623-3745
>de...@ihtfp.com www.ihtfp.com
>Computer and Internet Security Consultant
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Feature: enhanced OVA support

[Arik Hadas]

On Mon, May 15, 2017 at 8:05 PM, Richard W.M. Jones 
wrote:

> On Sun, May 14, 2017 at 04:56:56PM +0300, Arik Hadas wrote:
> > Hi everyone,
> >
> > We would like to share our plan for extending the currently provided
> > support for OVA files with:
> > 1. Support for uploading OVA.
> > 2. Support for exporting a VM/template as OVA.
> > 3. Support for importing OVA that was generated by oVirt (today, we only
> > support those that are VMware-compatible).
> > 4. Support for downloading OVA.
> >
> > This can be found on the feature page
> > <http://www.ovirt.org/develop/release-management/features/
> virt/enhance-import-export-with-ova/>
> > .
> >
> > Your feedback and cooperation will be highly appreciated.
>
> The plan as stated seems fine, but I have some reservations which I
> don't think are answered by the page:
>
> (1) How will oVirt know the difference between an OVA generated
> by oVirt and one generated by VMware (or indeed other sources)?
> A VMware OVF has an XML comment:
>
> 
>
> but not any official metadata that I could see.


So that's something that we have not decided on yet.
Indeed, we need some indication of the system that generated the OVA and it
makes sense to have it inside the OVF. I thought about a field that is part
of the VM configuration, like the "origin" field of VMs in ovirt-engine.
Having a comment like you mentioned is also an option.


>
> (By the way, I don't think importing via virt-v2v vs directly will be
> any quicker.  The v2v conversion / device installation takes only a
> fraction of the time.  Most of the time is consumed doing the format
> conversion from VMDK to qcow2.  However you are correct that when you
> know that the source is oVirt/KVM, you should not run virt-v2v.)
>

Note that the disks within the OVA will be of type qcow2. So not only that
no v2v conversion / device installation is needed, but also no format
conversion will be needed on the import and upload flows.


>
> (2) I think you're going to have a lot of fun generating OVAs which
> work on VMware.  As Yaniv says, the devices aren't the same so you'd
> be having to do some virt-v2v -like driver installation / registry
> modification.  Plus the OVF file is essentially a VMware data dump
> encoded as XML.  OVF isn't a real standard.  I bet there are a million
> strange corner cases.  Even writing VMDK files is full of pitfalls.
>
> VMware has a reasonable V2V import tool (actually their P2V tooling is
> very decent).  Of course it's proprietary, but then so is their
> hypervisor.  Maybe oVirt can drive their tools?
>

No no, that fun is not part of the plan :)
The OVAs we'll generate are supposed to contain:
1. OVF - it should be similar to the one virt-v2v generates for oVirt (that
is similar to the one we use internally in oVirt for snapshots and for
backup within storage domains, i.e., OVF-stores). We will definitely need
some extensions, like an indication that the OVA was generated by oVirt. We
may make some tweaks here and there, like removing network interfaces from
the list of resources. But we already are generally aligned with what the
specification says about OVFs.

2. qcow2 disks - thus, no conversion (device installation) and no format
conversion will be needed (we may consider to convert them to raw later on,
since they are expected to be the base volumes of the disks, not sure it
worth the effort though).

I will add this to the feature page.

We are aware to the fact that with this design, the OVAs could not be
directly consumed by others, like VMware. But this could make it easier for
them to make the needed conversion - they won't need to query the VM
configuration from oVirt and won't need to lookup the disks inside oVirt's
storage domains. Anyway, we assume that this conversion is done by other
tools.


> Rich.
>
> --
> Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~
> rjones
> Read my programming and virtualization blog: http://rwmj.wordpress.com
> Fedora Windows cross-compiler. Compile Windows programs, test, and
> build Windows installers. Over 100 libraries supported.
> http://fedoraproject.org/wiki/MinGW
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Permissions to Import VMs

[Arik Hadas]

On Mon, May 15, 2017 at 11:36 PM, Peter Wood  wrote:

> Hi,
>
> I have a group of local users with permissions to create VMs, templates,
> and VMs from templates. They are allowed to work only in one of the
> clusters in the datacenter.
>
> Now I want one of the local users to be able to import VMs and convert
> them into templates and I just can't find the recipe for that.
>
> The group has these permissions:
>
> LocalUsersGroup -> [PowerUserRole] -> DEV1 (Cluster)
> LocalUsersGroup -> [PowerUserRole] -> SAN (Storage)
> LocalUsersGroup -> [TemplateCreator] -> OFFICE (Datacenter)
>
> LocalUserA is part of LocalUsersGroup and should be able to:
>   - Import a VM
>   - Convert the VM to a template for everyone to use
>   - Delete the VM
>
> I tried this: LocalUserA -> [VmImporterExporter] -> System
>
> LocalUserA can now import VMs and convert them to templates but it can't
> delete the imported VMs. For some reason [UserVmManager] role is not
> assigned to LocalUserA on the VMs that were imported.
>

Right, that seems to be a bug. The import operation should set the user
that executes it with UserVmManager role on the imported VM, just like add
VM does for regular VM creation.
Could you please file a bug?


>
> Before I start messing around I'd appreciate somebody's else opinion on
> how this should be done.
>
>
Thank you for your time,
>
> -- Peter
>
>
>
> ___
> 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] Feature: enhanced OVA support

[Arik Hadas]

On Tue, May 16, 2017 at 5:56 PM, Adam Litke  wrote:

> Great feature!  I am glad to see you plan to use the existing imageio
> framework for transferring data.
>

Yep, and that's the part we need the feedback on the most.


>
> Will you allow export of VMs from a particular snapshot?  I guess that's
> how you'll have to do it if you want to support export of running VMs.
>

Exactly, that's how we intend to support exporting VMs with no downtime.


>
> I think you should definitely have a comment in the ovf to indicate that
> an OVA was generated by a oVirt.  People will try to use this new feature
> to import random OVAs from who knows where.  I'd also recommend adding a
> version to this comment:  or
> perhaps even a schema version in case you need to deal with compatibility
> issues in the future.
>
>
So yeah, there will be some sort of marking - either by a field or a
comment. We'll see about that.
As for the schema version, it already exists in OVFs generated by oVirt
today exactly for that purpose.


> I agree with Yaniv Kaul that we should offer to sparsify the VM to
> optimize it for export.  We should also return compressed data.  When
> exporting, does it make sense to cache the stored OVA file in some sort of
> ephemeral storage (host local is fine, storage domain may be better) in
> order to allow the client to resume or restart an interrupted download
> without having to start from scratch?
>
>
Well, on the one hand it makes sense and I would expect such a mechanism to
be used for image-download as well. On the other hand, we don't support
this concept of pausing ongoing operations or resuming interrupted
opeations on the engine side, so in the context of ova-download (where the
streaming process is comprised of several steps orchestrated by the engine)
supporting this may require too much effort.


>
> On Sun, May 14, 2017 at 9:56 AM, Arik Hadas  wrote:
>
>> Hi everyone,
>>
>> We would like to share our plan for extending the currently provided
>> support for OVA files with:
>> 1. Support for uploading OVA.
>> 2. Support for exporting a VM/template as OVA.
>> 3. Support for importing OVA that was generated by oVirt (today, we only
>> support those that are VMware-compatible).
>> 4. Support for downloading OVA.
>>
>> This can be found on the feature page
>> <http://www.ovirt.org/develop/release-management/features/virt/enhance-import-export-with-ova/>
>> .
>>
>> Your feedback and cooperation will be highly appreciated.
>>
>> Thanks,
>> Arik
>>
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>
>
> --
> Adam Litke
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] How to use virt-sysprep

[Arik Hadas]

On Thu, May 18, 2017 at 10:40 AM, Luca 'remix_tj' Lorenzetto <
lorenzetto.l...@gmail.com> wrote:

> Hello Joel,
>
> as far as i know, virt-sysprep has to be executed inside the VM before
> cloning it to template. This removes some infos from the VM like udev
> rules & ssh keys.
>
>
So this has changed in 4.1. You can now choose to seal a template during
its creation. This will take a VM, that may have not been sealed, create a
template out of it and then invoke virt-sysprep on the template's disks.

Joel, in the 'make template' dialog you'll see a checkbox (at the bottom)
for 'Seal Template' that will do the trick. There is also a 'seal'
parameter in the REST-API, of course [1].

[1]
https://github.com/oVirt/ovirt-engine-api-model/blob/master/src/main/java/services/TemplatesService.java#L168


>
> Luca
>
> On Wed, May 17, 2017 at 8:53 PM, Joel Diaz  wrote:
> > Good afternoon ovirt users,
> >
> > I'm new to ovirt. I've created templates in the past using this guide,
> > https://github.com/rharmonson/richtech/wiki/CentOS-7-1511-
> Minimal-oVirt-Template
> > .
> >
> > I was going over the list of features and stumbled on to virt-sysprep.
> >
> > http://www.ovirt.org/develop/release-management/features/virt-sysprep/
> >
> >  http://libguestfs.org/virt-sysprep.1.html
> >
> > How can I use virt-sysprep from within ovirt to create templates?
> >
> > Thank you for your help,
> >
> > Joel
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Joel
> >
> >
> > ___
> > Users mailing list
> > Users@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/users
> >
>
>
>
> --
> "E' assurdo impiegare gli uomini di intelligenza eccellente per fare
> calcoli che potrebbero essere affidati a chiunque se si usassero delle
> macchine"
> Gottfried Wilhelm von Leibnitz, Filosofo e Matematico (1646-1716)
>
> "Internet è la più grande biblioteca del mondo.
> Ma il problema è che i libri sono tutti sparsi sul pavimento"
> John Allen Paulos, Matematico (1945-vivente)
>
> Luca 'remix_tj' Lorenzetto, http://www.remixtj.net , <
> lorenzetto.l...@gmail.com>
> ___
> 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] How to use virt-sysprep

[Arik Hadas]

On Fri, May 19, 2017 at 4:10 PM, Joel Diaz  wrote:

> Arik,
>
> Very cool. It's exactly what I was looking for.
>
> However, I don't see that checkbox. I've attached an image of what the
> template window looks like on my end. Maybe I'm looking in the wrong place?
>

No , you're looking at the right place. This feature got in pretty late in
the release cycle of 4.1, so it is available from 4.1.2. Maybe the version
you are using is lower than that?


>
> Thanks for the response,
>
> On May 18, 2017 12:29 PM, "Arik Hadas"  wrote:
>
>>
>>
>> On Thu, May 18, 2017 at 10:40 AM, Luca 'remix_tj' Lorenzetto <
>> lorenzetto.l...@gmail.com> wrote:
>>
>>> Hello Joel,
>>>
>>> as far as i know, virt-sysprep has to be executed inside the VM before
>>> cloning it to template. This removes some infos from the VM like udev
>>> rules & ssh keys.
>>>
>>>
>> So this has changed in 4.1. You can now choose to seal a template during
>> its creation. This will take a VM, that may have not been sealed, create a
>> template out of it and then invoke virt-sysprep on the template's disks.
>>
>> Joel, in the 'make template' dialog you'll see a checkbox (at the bottom)
>> for 'Seal Template' that will do the trick. There is also a 'seal'
>> parameter in the REST-API, of course [1].
>>
>> [1] https://github.com/oVirt/ovirt-engine-api-model/blob/mas
>> ter/src/main/java/services/TemplatesService.java#L168
>>
>>
>>>
>>> Luca
>>>
>>> On Wed, May 17, 2017 at 8:53 PM, Joel Diaz  wrote:
>>> > Good afternoon ovirt users,
>>> >
>>> > I'm new to ovirt. I've created templates in the past using this guide,
>>> > https://github.com/rharmonson/richtech/wiki/CentOS-7-1511-Mi
>>> nimal-oVirt-Template
>>> > .
>>> >
>>> > I was going over the list of features and stumbled on to virt-sysprep.
>>> >
>>> > http://www.ovirt.org/develop/release-management/features/virt-sysprep/
>>> >
>>> >  http://libguestfs.org/virt-sysprep.1.html
>>> >
>>> > How can I use virt-sysprep from within ovirt to create templates?
>>> >
>>> > Thank you for your help,
>>> >
>>> > Joel
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > Joel
>>> >
>>> >
>>> > ___
>>> > Users mailing list
>>> > Users@ovirt.org
>>> > http://lists.ovirt.org/mailman/listinfo/users
>>> >
>>>
>>>
>>>
>>> --
>>> "E' assurdo impiegare gli uomini di intelligenza eccellente per fare
>>> calcoli che potrebbero essere affidati a chiunque se si usassero delle
>>> macchine"
>>> Gottfried Wilhelm von Leibnitz, Filosofo e Matematico (1646-1716)
>>>
>>> "Internet è la più grande biblioteca del mondo.
>>> Ma il problema è che i libri sono tutti sparsi sul pavimento"
>>> John Allen Paulos, Matematico (1945-vivente)
>>>
>>> Luca 'remix_tj' Lorenzetto, http://www.remixtj.net , <
>>> lorenzetto.l...@gmail.com>
>>> ___
>>> 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] How to use virt-sysprep

[Arik Hadas]

On Fri, May 19, 2017 at 7:22 PM, Joel Diaz  wrote:

> I ran yum update on my three host and the engine VM so I believe an up to
> date on all the packages. How can I check if I am on version 4.1.2?
>

You can find the engine's version in the 'About' dialog (at the top-right
corner of the screen of the webadmin). If you don't use the
'ovirt-4.1-snapshot' repository then it makes sense that you didn't get
this update yet.


> I restarted the httpd and ovirt-engine service after the updates, but
> still don't the seal option.
>
> Thanks,
>
> On May 19, 2017 11:49 AM, "Arik Hadas"  wrote:
>
>
>
> On Fri, May 19, 2017 at 4:10 PM, Joel Diaz  wrote:
>
>> Arik,
>>
>> Very cool. It's exactly what I was looking for.
>>
>> However, I don't see that checkbox. I've attached an image of what the
>> template window looks like on my end. Maybe I'm looking in the wrong place?
>>
>
> No , you're looking at the right place. This feature got in pretty late in
> the release cycle of 4.1, so it is available from 4.1.2. Maybe the version
> you are using is lower than that?
>
>
>>
>> Thanks for the response,
>>
>> On May 18, 2017 12:29 PM, "Arik Hadas"  wrote:
>>
>>>
>>>
>>> On Thu, May 18, 2017 at 10:40 AM, Luca 'remix_tj' Lorenzetto <
>>> lorenzetto.l...@gmail.com> wrote:
>>>
>>>> Hello Joel,
>>>>
>>>> as far as i know, virt-sysprep has to be executed inside the VM before
>>>> cloning it to template. This removes some infos from the VM like udev
>>>> rules & ssh keys.
>>>>
>>>>
>>> So this has changed in 4.1. You can now choose to seal a template during
>>> its creation. This will take a VM, that may have not been sealed, create a
>>> template out of it and then invoke virt-sysprep on the template's disks.
>>>
>>> Joel, in the 'make template' dialog you'll see a checkbox (at the
>>> bottom) for 'Seal Template' that will do the trick. There is also a 'seal'
>>> parameter in the REST-API, of course [1].
>>>
>>> [1] https://github.com/oVirt/ovirt-engine-api-model/blob/mas
>>> ter/src/main/java/services/TemplatesService.java#L168
>>>
>>>
>>>>
>>>> Luca
>>>>
>>>> On Wed, May 17, 2017 at 8:53 PM, Joel Diaz 
>>>> wrote:
>>>> > Good afternoon ovirt users,
>>>> >
>>>> > I'm new to ovirt. I've created templates in the past using this guide,
>>>> > https://github.com/rharmonson/richtech/wiki/CentOS-7-1511-Mi
>>>> nimal-oVirt-Template
>>>> > .
>>>> >
>>>> > I was going over the list of features and stumbled on to virt-sysprep.
>>>> >
>>>> > http://www.ovirt.org/develop/release-management/features/vir
>>>> t-sysprep/
>>>> >
>>>> >  http://libguestfs.org/virt-sysprep.1.html
>>>> >
>>>> > How can I use virt-sysprep from within ovirt to create templates?
>>>> >
>>>> > Thank you for your help,
>>>> >
>>>> > Joel
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >
>>>> > Joel
>>>> >
>>>> >
>>>> > ___
>>>> > Users mailing list
>>>> > Users@ovirt.org
>>>> > http://lists.ovirt.org/mailman/listinfo/users
>>>> >
>>>>
>>>>
>>>>
>>>> --
>>>> "E' assurdo impiegare gli uomini di intelligenza eccellente per fare
>>>> calcoli che potrebbero essere affidati a chiunque se si usassero delle
>>>> macchine"
>>>> Gottfried Wilhelm von Leibnitz, Filosofo e Matematico (1646-1716)
>>>>
>>>> "Internet è la più grande biblioteca del mondo.
>>>> Ma il problema è che i libri sono tutti sparsi sul pavimento"
>>>> John Allen Paulos, Matematico (1945-vivente)
>>>>
>>>> Luca 'remix_tj' Lorenzetto, http://www.remixtj.net , <
>>>> lorenzetto.l...@gmail.com>
>>>> ___
>>>> 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] How to use virt-sysprep

[Arik Hadas]

On Fri, May 19, 2017 at 9:42 PM, Joel Diaz  wrote:

> Arik,
>
> After adding the snapshot repo, and updating the engine, I now see the
> seal option.
>

Great. Note that you probably need to update the hosts with the snapshot
repository as well for this operation to work.


>
> Thanks again,
>
> Joel
>
>
>
> On May 19, 2017 1:07 PM, "Arik Hadas"  wrote:
>
>>
>>
>> On Fri, May 19, 2017 at 7:22 PM, Joel Diaz  wrote:
>>
>>> I ran yum update on my three host and the engine VM so I believe an up
>>> to date on all the packages. How can I check if I am on version 4.1.2?
>>>
>>
>> You can find the engine's version in the 'About' dialog (at the top-right
>> corner of the screen of the webadmin). If you don't use the
>> 'ovirt-4.1-snapshot' repository then it makes sense that you didn't get
>> this update yet.
>>
>>
>>> I restarted the httpd and ovirt-engine service after the updates, but
>>> still don't the seal option.
>>>
>>> Thanks,
>>>
>>> On May 19, 2017 11:49 AM, "Arik Hadas"  wrote:
>>>
>>>
>>>
>>> On Fri, May 19, 2017 at 4:10 PM, Joel Diaz  wrote:
>>>
>>>> Arik,
>>>>
>>>> Very cool. It's exactly what I was looking for.
>>>>
>>>> However, I don't see that checkbox. I've attached an image of what the
>>>> template window looks like on my end. Maybe I'm looking in the wrong place?
>>>>
>>>
>>> No , you're looking at the right place. This feature got in pretty late
>>> in the release cycle of 4.1, so it is available from 4.1.2. Maybe the
>>> version you are using is lower than that?
>>>
>>>
>>>>
>>>> Thanks for the response,
>>>>
>>>> On May 18, 2017 12:29 PM, "Arik Hadas"  wrote:
>>>>
>>>>>
>>>>>
>>>>> On Thu, May 18, 2017 at 10:40 AM, Luca 'remix_tj' Lorenzetto <
>>>>> lorenzetto.l...@gmail.com> wrote:
>>>>>
>>>>>> Hello Joel,
>>>>>>
>>>>>> as far as i know, virt-sysprep has to be executed inside the VM before
>>>>>> cloning it to template. This removes some infos from the VM like udev
>>>>>> rules & ssh keys.
>>>>>>
>>>>>>
>>>>> So this has changed in 4.1. You can now choose to seal a template
>>>>> during its creation. This will take a VM, that may have not been sealed,
>>>>> create a template out of it and then invoke virt-sysprep on the template's
>>>>> disks.
>>>>>
>>>>> Joel, in the 'make template' dialog you'll see a checkbox (at the
>>>>> bottom) for 'Seal Template' that will do the trick. There is also a 'seal'
>>>>> parameter in the REST-API, of course [1].
>>>>>
>>>>> [1] https://github.com/oVirt/ovirt-engine-api-model/blob/mas
>>>>> ter/src/main/java/services/TemplatesService.java#L168
>>>>>
>>>>>
>>>>>>
>>>>>> Luca
>>>>>>
>>>>>> On Wed, May 17, 2017 at 8:53 PM, Joel Diaz 
>>>>>> wrote:
>>>>>> > Good afternoon ovirt users,
>>>>>> >
>>>>>> > I'm new to ovirt. I've created templates in the past using this
>>>>>> guide,
>>>>>> > https://github.com/rharmonson/richtech/wiki/CentOS-7-1511-Mi
>>>>>> nimal-oVirt-Template
>>>>>> > .
>>>>>> >
>>>>>> > I was going over the list of features and stumbled on to
>>>>>> virt-sysprep.
>>>>>> >
>>>>>> > http://www.ovirt.org/develop/release-management/features/vir
>>>>>> t-sysprep/
>>>>>> >
>>>>>> >  http://libguestfs.org/virt-sysprep.1.html
>>>>>> >
>>>>>> > How can I use virt-sysprep from within ovirt to create templates?
>>>>>> >
>>>>>> > Thank you for your help,
>>>>>> >
>>>>>> > Joel
>>>>>> >
>>>>>> >
>>>>>> >
>>>>>> >
>>>>>> >
>>>>>> >
>>>>>> >
>>>>>> >
>>>>>> >
>>>>>> >
>>>>>> >
>>>>>> >
>>>>>> >
>>>>>> >
>>>>>> >
>>>>>> >
>>>>>> > Joel
>>>>>> >
>>>>>> >
>>>>>> > ___
>>>>>> > Users mailing list
>>>>>> > Users@ovirt.org
>>>>>> > http://lists.ovirt.org/mailman/listinfo/users
>>>>>> >
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> "E' assurdo impiegare gli uomini di intelligenza eccellente per fare
>>>>>> calcoli che potrebbero essere affidati a chiunque se si usassero delle
>>>>>> macchine"
>>>>>> Gottfried Wilhelm von Leibnitz, Filosofo e Matematico (1646-1716)
>>>>>>
>>>>>> "Internet è la più grande biblioteca del mondo.
>>>>>> Ma il problema è che i libri sono tutti sparsi sul pavimento"
>>>>>> John Allen Paulos, Matematico (1945-vivente)
>>>>>>
>>>>>> Luca 'remix_tj' Lorenzetto, http://www.remixtj.net , <
>>>>>> lorenzetto.l...@gmail.com>
>>>>>> ___
>>>>>> 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] Permissions to Import VMs

[Arik Hadas]

On Sat, May 20, 2017 at 12:15 AM, Peter Wood  wrote:

> I did create a bug report and it was closed with the explanation that
> UserVmManager role is not assigned because I'm using the Administration
> portal... (???). What other portal do I use? Import/Export is Admin type
> operation.
>
> See here:
> https://bugzilla.redhat.com/show_bug.cgi?id=1451501
>
>
> Very simple steps to test it:
>
> - Create a local user called LocalUserA
>
> - Grant permissions to create VMs in DEV1 cluster and Import/Export VMs:
>
> LocalUserA -> [PowerUserRole] -> DEV1 (Cluster)
> LocalUserA -> [PowerUserRole] -> SAN (Storage Data Master)
> LocalUserA -> [VmImporterExporter] -> DEV1 (Cluster)
> LocalUserA -> [VmImporterExporter] -> SAN (Storage Data Master)
> LocalUserA -> [VmImporterExporter] -> SD-Export (Storage Export type)
>
> - Login to the Administration Portal as LocalUserA@internal
>
> - Create a VM, Export the VM, Import the VM
>
>   Role UserVmManager is not set for the imported VM.
>   User LocalUserA can not even boot up the VM due to insufficient
> permissions.
>
> How do I setup LocalUserA so it can import VMs and work with them?
>
>
Thanks for this information Peter.
I proposed a patch. Let's discuss it in bugzilla.


> Thank you,
>
> -- Peter
>
>
> On Tue, May 16, 2017 at 4:11 AM, Arik Hadas  wrote:
>
>>
>>
>> On Mon, May 15, 2017 at 11:36 PM, Peter Wood 
>> wrote:
>>
>>> Hi,
>>>
>>> I have a group of local users with permissions to create VMs, templates,
>>> and VMs from templates. They are allowed to work only in one of the
>>> clusters in the datacenter.
>>>
>>> Now I want one of the local users to be able to import VMs and convert
>>> them into templates and I just can't find the recipe for that.
>>>
>>> The group has these permissions:
>>>
>>> LocalUsersGroup -> [PowerUserRole] -> DEV1 (Cluster)
>>> LocalUsersGroup -> [PowerUserRole] -> SAN (Storage)
>>> LocalUsersGroup -> [TemplateCreator] -> OFFICE (Datacenter)
>>>
>>> LocalUserA is part of LocalUsersGroup and should be able to:
>>>   - Import a VM
>>>   - Convert the VM to a template for everyone to use
>>>   - Delete the VM
>>>
>>> I tried this: LocalUserA -> [VmImporterExporter] -> System
>>>
>>> LocalUserA can now import VMs and convert them to templates but it can't
>>> delete the imported VMs. For some reason [UserVmManager] role is not
>>> assigned to LocalUserA on the VMs that were imported.
>>>
>>
>> Right, that seems to be a bug. The import operation should set the user
>> that executes it with UserVmManager role on the imported VM, just like add
>> VM does for regular VM creation.
>> Could you please file a bug?
>>
>>
>>>
>>> Before I start messing around I'd appreciate somebody's else opinion on
>>> how this should be done.
>>>
>>>
>> Thank you for your time,
>>>
>>> -- Peter
>>>
>>>
>>>
>>> ___
>>> 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] Importing VMs from kvm to oVirt. "VM zarafa is down with error. Exit message: Failed to find the libvirt domain."

[Arik Hadas]

On Wed, May 31, 2017 at 6:34 PM, Luca 'remix_tj' Lorenzetto <
lorenzetto.l...@gmail.com> wrote:

> Hello Marc,
>
> could you please attach your vdsm.log of the host where virt-v2v (the
> conversion tool) is running? In that logs you'll have more details
> about, and maybe we can try launching manually the conversion command
> and see what's happening.
>

Note that since it is a kvm VM, virt-v2v is not involved in the process.


>
> Luca
>
> On Wed, May 31, 2017 at 5:13 PM, Marc Pfaendler
>  wrote:
> > Hello
> >
> > I'm trying to import an existing kvm VM into oVirt 4.1. It a new server
> with
> > a fresh installation of oVirt.
> >
> > I'm working with the oVirt gui to achieve this.
> > After moving the VM from the old system into the export folder, the gui
> > allows me to import it.
> > The import seems to succeed. But after the VM is imported it fails to
> start.
>

So the VM resided in some oVirt data center (the old system), you exported
the VM into an export domain (export folder), detached the export domain
from that data center, attached it to a new one, imported the VM and it
doesn't run now?


> >
> > Giving this error:
> >"VM zarafa is down with error. Exit message: Failed to find the
> > libvirt domain."
>

Please file a bug and attach the engine log, vdsm log and qemu log (the
latter can be found in /var/log/libvirt/qemu), covering the time you run
the VM.


> >
> >
> >
> > Cheers
> > Marc
> > ___
> > Users mailing list
> > Users@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/users
>
>
>
> --
> "E' assurdo impiegare gli uomini di intelligenza eccellente per fare
> calcoli che potrebbero essere affidati a chiunque se si usassero delle
> macchine"
> Gottfried Wilhelm von Leibnitz, Filosofo e Matematico (1646-1716)
>
> "Internet è la più grande biblioteca del mondo.
> Ma il problema è che i libri sono tutti sparsi sul pavimento"
> John Allen Paulos, Matematico (1945-vivente)
>
> Luca 'remix_tj' Lorenzetto, http://www.remixtj.net , <
> lorenzetto.l...@gmail.com>
> ___
> 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] [Libguestfs] virt-v2v import from KVM without storage-pool ?

[Arik Hadas]

On Wed, Jul 5, 2017 at 4:15 PM, Richard W.M. Jones 
wrote:

> On Wed, Jul 05, 2017 at 11:14:09AM +0200, Matthias Leopold wrote:
> > hi,
> >
> > i'm trying to import a VM in oVirt from a KVM host that doesn't use
> > storage pools. this fails with the following message in
> > /var/log/vdsm/vdsm.log:
> >
> > 2017-07-05 09:34:20,513+0200 ERROR (jsonrpc/5) [root] Error getting
> > disk size (v2v:1089)
> > Traceback (most recent call last):
> >   File "/usr/lib/python2.7/site-packages/vdsm/v2v.py", line 1078, in
> > _get_disk_info
> > vol = conn.storageVolLookupByPath(disk['alias'])
> >   File "/usr/lib64/python2.7/site-packages/libvirt.py", line 4770,
> > in storageVolLookupByPath
> > if ret is None:raise libvirtError('virStorageVolLookupByPath()
> > failed', conn=self)
> > libvirtError: Storage volume not found: no storage vol with matching path
> >
> > the disks in the origin VM are defined as
> >
> > 
> >   
> >   
> >
> > 
> >   
> >   
> >
> > is this a virt-v2v or oVirt problem?
>
> Well the stack trace is in the oVirt code, so I guess it's an oVirt
> problem.  Adding ovirt-users mailing list.
>

Right, import of KVM VMs to oVirt doesn't involve virt-v2v.
The current process gets the virtual size (i.e., capacity) and the actual
size (i.e., allocation) of the volume using libvirt api that seems to rely
on having the volume in a storage pool. So the process would need to be
extended in order to support the case of having volumes that are not part
of a storage pool.


>
> Rich.
>
> --
> Richard Jones, Virtualization Group, Red Hat
> http://people.redhat.com/~rjones
> Read my programming and virtualization blog: http://rwmj.wordpress.com
> virt-df lists disk usage of guests without needing to install any
> software inside the virtual machine.  Supports Linux and Windows.
> http://people.redhat.com/~rjones/virt-df/
>
> ___
> Libguestfs mailing list
> libgues...@redhat.com
> https://www.redhat.com/mailman/listinfo/libguestfs
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] virt-v2v to glusterfs storage domain

[Arik Hadas]

On Fri, Jul 7, 2017 at 9:38 PM, Ramachandra Reddy Ankireddypalle <
rcreddy.ankireddypa...@gmail.com> wrote:

> Hi,
>  Does virt-v2v command work with glusterfs storage domain. I have an
> OVA image and that needs to be imported to glusterfs storage domain. Please
> provide some pointers to this.
>

 I don't see a reason why it wouldn't work.
Assuming that the import operation is triggered from oVirt, the engine then
creates the target disk(s) and prepares the image(s) on the host that the
conversion will be executed on as it regularly does. virt-v2v then just to
write to that "prepared" image.
In the import dialog you can select the target storage domain. I would
suggest that you just try to pick the glusterfs storage domain and see if
it works. It should work, if not - please let us know.


>
> Thanks and Regards,
> Ram
>
> ___
> 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] virt-v2v to glusterfs storage domain

[Arik Hadas]

On Mon, Jul 10, 2017 at 7:54 PM, Ramachandra Reddy Ankireddypalle <
rcreddy.ankireddypa...@gmail.com> wrote:

> Thanks for looking in to this. I am looking for a way to achieve this
> through command/script. I tried using virtv2v as below.
>
> [root@hcadev3 tmp]# virt-v2v -i ova 1Deepakvm2.ova -o rhev -of qcow2 -os
> hcadev3:/dav_vm_vol
> [   0.0] Opening the source -i ova 1Deepakvm2.ova
> [   1.2] Creating an overlay to protect the source from being modified
> [   2.3] Initializing the target -o rhev -os hcadev3:/dav_vm_vol
> mount.nfs: requested NFS version or transport protocol is not supported
>
> I am looking for a way to provide an option to virt-v2v to understand that
> dav_vm_vol is a glusterfs volume and that it can be accessed from node
> hcadev3.
>

So the "-o rhev" should not be used in that case because then virt-v2v
assumes the target is an export domain and tries to mount it as NFS.
If this has to be done via the command line then the flag that needs to be
used in virt-v2v is "-o vdsm" but it requires you to create the images and
mount them to the host that the conversion is executed on by yourself + to
execute virt-v2v with vdsm's permissions - which is complicated. That is
why this option was not intended for invocation by users from the command
line (but to be used by vdsm), however, that's possible.
It would be simpler to use the REST-API based clients in that case.


>
> On Mon, Jul 10, 2017 at 2:36 AM, Arik Hadas  wrote:
>
>>
>>
>> On Fri, Jul 7, 2017 at 9:38 PM, Ramachandra Reddy Ankireddypalle <
>> rcreddy.ankireddypa...@gmail.com> wrote:
>>
>>> Hi,
>>>  Does virt-v2v command work with glusterfs storage domain. I have an
>>> OVA image and that needs to be imported to glusterfs storage domain. Please
>>> provide some pointers to this.
>>>
>>
>>  I don't see a reason why it wouldn't work.
>> Assuming that the import operation is triggered from oVirt, the engine
>> then creates the target disk(s) and prepares the image(s) on the host that
>> the conversion will be executed on as it regularly does. virt-v2v then just
>> to write to that "prepared" image.
>> In the import dialog you can select the target storage domain. I would
>> suggest that you just try to pick the glusterfs storage domain and see if
>> it works. It should work, if not - please let us know.
>>
>>
>>>
>>> Thanks and Regards,
>>> Ram
>>>
>>> ___
>>> 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] Template for imported VMs?

[Arik Hadas]

On Tue, Jul 11, 2017 at 1:28 PM, Eduardo Mayoral  wrote:

> Hi,
>
> I am using oVirt 4.1 and I am importing a significant number of VMs
> from VMWare. So far, everything is fine.
>
> However, I find that after importing each VM I have to modify some
> parameters of the imported VM (Timezone, VM type from desktop to server,
> VNC console...).
>
> I have those parameters changed on the "blank" template, but it
> seems that the import process is not picking that template as the base
>

That's true, we don't take anything from the blank template on import at
the moment.
Although this approach makes sense to some degree, because the blank
template is used as a base for new VMs unless stated otherwise, it is
debatable whether this approach should be used for imported VMs - some may
find such a relation between the (remote) imported VMs and the (local)
blank template odd/unexpected .


> for the imported VM. Where is the import process picking the defaults
> for the imported VM from? Can those be changed? I have failed to find
> that information on the docs.
>

Unfortunately, there is no way to set those defaults at the moment. You
will have to edit the VMs after the import process is done. There are some
plans to simplify that process though.


>
> 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

Re: [ovirt-users] [ovirt 4.1] how to increase HA VM retry count ?

[Arik Hadas]

On Wed, Jul 12, 2017 at 4:05 PM, TranceWorldLogic . <
tranceworldlo...@gmail.com> wrote:

> Hi,
>
> I want to retry VM start procedure.
> Is this variable use for same ? because as per name it look to me it will
> try to do fencing if it fail.
>

So in that case the configuration value that you look for is:
MaxNumOfTriesToRunFailedAutoStartVm


>
> Thanks,
> ~Rohit
>
> On Wed, Jul 12, 2017 at 3:21 PM, Eli Mesika  wrote:
>
>> Hi
>>
>> You have the following configuration parameters :
>>
>> FenceStartStatusRetries (default 10)
>> FenceStartStatusDelayBetweenRetriesInSec (default 18 sec)
>>
>> FenceStopStatusRetries(default 10)
>> FenceStopStatusDelayBetweenRetriesInSec(default 18 sec)
>>
>>
>> You can use the engine-config utility to change any of those (requires
>> engine restart)
>>
>> For example
>>
>> engine-config -s FenceStartStatusRetries=30
>>
>>
>>
>>
>> On Wed, Jul 12, 2017 at 12:27 PM, TranceWorldLogic . <
>> tranceworldlo...@gmail.com> wrote:
>>
>>> Hi,
>>>
>>> I have created HA VM with priority as High.
>>> And then I block host network connection using firewall rule as shown
>>> below.
>>> e.g.
>>> iptables -I INPUT -j DROP; iptables -I OUTPUT -j DROP;
>>>
>>> As expected ovirt had call fencing to power off host and power on it
>>> again.
>>> At backgroud ovirt tried 10 time to start that VM but as host down it
>>> fail to start.
>>> And after 10 trial it giveup to start VM.
>>>
>>> Is there any way to increase trail count ?
>>> And also let me know how to change retry timer.
>>>
>>> Thanks,
>>> ~Rohit
>>>
>>>
>>> ___
>>> 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] After upgrading to 4.1.4 unable to start VM or migrate them

[Arik Hadas]

Hi,
Please provide the engine log so we can figure out which validation fails.

On Mon, Jul 31, 2017 at 4:57 PM, Arman Khalatyan  wrote:

> Hi,
> I am running in to trouble with 4.1.4 after engine upgrade I am not able
> to start or migrate virtual machines:
> getting following error:
> General command validation failure
> Are there any workarounds?
>
> ​
>
> ___
> 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] Cloning VM on a different data domain than master

[Arik Hadas]

On Tue, Aug 22, 2017 at 7:02 PM, Christopher Cox 
wrote:

> On 08/22/2017 07:20 AM, Yohan JAROSZ wrote:
>
>> Dear list,
>>
>> When cloning a VM, is it possible to select the data domain to which it
>> would clone.
>> I have two data domains attached to my cluster and it automatically clone
>> the VM to the master one.
>>
>
>
> Clones are not copies, but rather built using snapshots, which is why they
> are on the same storage domain(s) as the original disk(s).
>
>
That is incorrect. Disks of a VM that was cloned from an existing VM *are*
copies of the disks the latter.
The process of cloning a VM from an existing VM is similar to cloning a VM
from a snapshot. When cloning from a snapshot we enable the user to choose
a target storage domain for each disk. We don't provide this option in the
webadmin when cloning from an existing VM. There is a chance, however, that
it works from REST-API since both operationgs use similar parameters and
the same code for creating the disks. Need to try.


>
> ___
> 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] Huge pages in guest with newer oVirt versions

[Arik Hadas]

On Mon, Sep 18, 2017 at 10:50 PM, Martin Polednik 
wrote:

> The hugepages are no longer a hook, but part of the code base. They

can be configured via engine property `hugepages`, where the value of
> property is size of the pages in KiB (1048576 = 1G, 2048 = 2M).
>

Note that the question is about 4.1 and it doesn't seem like this change
was backported to the 4.1 branch, right?


> Specifying any other size not supported by the architecture (or just
> "1") will use platform's default hugepage size.
>

I wonder if the end-to-end scenario, i.e., using the engine, of this ever
worked.
This feature is broken on the master branch because of the switch to engine
xml and is supposed to be fixed by [1]. However, while testing that fix I
noticed that a check done by the scheduler [2] actually prevents us from
setting a value that is not supported by the host.
Is this part really important?

[1] https://gerrit.ovirt.org/#/c/81860/
[2]
https://github.com/oVirt/ovirt-engine/blob/master/backend/manager/modules/bll/src/main/java/org/ovirt/engine/core/bll/scheduling/policyunits/HugePagesFilterPolicyUnit.java#L56


>
> On Mon, Sep 18, 2017 at 11:39 AM, Gianluca Cecchi
>  wrote:
> > Hello,
> > I would like to go again in deep with what preliminary tested and already
> > discussed here:
> >
> > http://lists.ovirt.org/pipermail/users/2017-April/081320.html
> >
> > I'm testing an oVirt node in 4.1.6-pre
> >
> > I don't find the vdsm hook for huge pages; doing a search I get these:
> >
> > vdsm-hook-ethtool-options.noarch : Allow setting custom ethtool options
> for
> > vdsm controlled nics
> > vdsm-hook-fcoe.noarch : Hook to enable FCoE support
> > vdsm-hook-openstacknet.noarch : OpenStack Network vNICs support for VDSM
> > vdsm-hook-vfio-mdev.noarch : Hook to enable mdev-capable devices.
> > vdsm-hook-vhostmd.noarch : VDSM hook set for interaction with vhostmd
> > vdsm-hook-vmfex-dev.noarch : VM-FEX vNIC support for VDSM
> >
> > Did anything change between 4.1.1 and 4.1.5/4.1.6?
> >
> > I'm making preliminary tests with an Oracle RDBMS and HammerDB in both a
> > physical server and a "big" VM inside another same hw server configured
> with
> > oVirt.
> >
> > Results are not bad, but I would like to see having huge pages inside the
> > guest how could change results.
> >
> > Just for reference:
> >
> > The 2 Physical server are blades with each one:
> > 2 sockets, each one with 14 cores and ht enabled, so in total 56
> > computational threads
> > 256Gb ram
> > huge pages enabled
> >
> > VM configured with this virtual hw on one of them:
> > 2 sockets, each one with 6 cores and ht so in total 24 computational
> threads
> > 64Gb ram
> > no huge pages at the moment
> >
> > Oracle SGA is 32Gb on both physical rdbms and virtual one.
> >
> > Thanks for any insight to test huge pages in guest
> >
> > 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
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] oVirt HA behavior

[Arik Hadas]

On Tue, Sep 19, 2017 at 11:41 AM, Alex K  wrote:

> Hi again,
>
> I performed a different test by isolating one host (say host A) through
> removing all its network interfaces (thus power management through IPMI was
> also not avaialble).
> The VMs (with VM lease enabled) were successfully restarted to another
> host.
> When connecting back the host A, the cluster performed a power management
> and the host became a member of the cluster.
> The VMs that were running on the host A were found "paused", which is
> normal.
> After 15 minutes I see that the VMs at host A are still in "paused" state
> and I would expect that the cluster should decide at some point to shutdown
> the paused VMs and continue with the VMs that are already running at other
> hosts.
>
> Is this behavior normal?
>

I believe it is not the expected behavior - the VM should not stay in
paused state when its lease expires. But we know about this, see comment 9
in [1].

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1459865


>
> Thanx,
> Alex
>
> On Tue, Sep 19, 2017 at 10:18 AM, Alex K  wrote:
>
>> Hi All,
>>
>> Just completed the tests and it works great.
>> VM leases is just what I needed.
>>
>> Thanx,
>> Alex
>>
>> On Tue, Sep 19, 2017 at 10:16 AM, Yaniv Kaul  wrote:
>>
>>>
>>>
>>> On Tue, Sep 19, 2017 at 1:00 AM, Alex K  wrote:
>>>
 Enabling VM leases could be an answer to this. Will test tomorrow.


>>> Indeed. Let us know how it worked for you.
>>>
>>>
 Thanx,
 Alex

 On Sep 18, 2017 7:50 PM, "Alex K"  wrote:

 Hi All,

 I have the following issue with the HA behavior of oVirt 4.1 and need
 to check with you if there is any work around from your experience.

 I have 3 servers (A, B, C) with hosted engine in self hosted setup on
 top gluster with replica 3 + 1 arbiter. All good except one point:

 The hosts have been configured with power management using IPMI (server
 iLO).
 If I disconnect power from one host (say C) (or disconnect all network
 cables of the host) the two other hosts go to a loop where they try to
 verify the status of the host C by issuing power management commands to the
 host C. Since power of host is off the server iLO does not respond on the
 network and the power management of host C fails, leaving the VMs that were
 running on the host C in an unknown state and they are never restarted to
 the other hosts.

 Is there any fencing option to change this behavior so as if both
 available hosts fail to do power management of the unresponsive host to
 decide that the host is down and to restart the VMs of that host to the
 other available hosts.


>>> No, this is a bad assumption. Perhaps they are the ones isolated form it?
>>> Y.
>>>
>>>

 I could also add additional power management through UPS to avoid this
 issue but this is not currently an option and I am interested to see if
 this behavior can be tweaked.

 Thanx,
 Alex



 ___
 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 HA behavior

[Arik Hadas]

On Tue, Sep 19, 2017 at 12:44 PM, Alex K  wrote:

> A second test did not yield the same result.
> This time the VMs were restarted to another host and when the lost host
> recovered no VMs were running on it.
> Seems that there is a racing issue somewhere.
>

Did you test with the same VM? were the disks + lease located on the same
storage domains in both tests? did the VM run on the same host (and if not,
is the libvirt + qemu versions different between the two?).
It may be a racing issue but not necessarily. There is an observation in
the bug I mentioned before that it happens only (/more) with certain
storage types...


>
> Thanx,
> Alex
>
>
> On Tue, Sep 19, 2017 at 11:52 AM, Arik Hadas  wrote:
>
>>
>>
>> On Tue, Sep 19, 2017 at 11:41 AM, Alex K  wrote:
>>
>>> Hi again,
>>>
>>> I performed a different test by isolating one host (say host A) through
>>> removing all its network interfaces (thus power management through IPMI was
>>> also not avaialble).
>>> The VMs (with VM lease enabled) were successfully restarted to another
>>> host.
>>> When connecting back the host A, the cluster performed a power
>>> management and the host became a member of the cluster.
>>> The VMs that were running on the host A were found "paused", which is
>>> normal.
>>> After 15 minutes I see that the VMs at host A are still in "paused"
>>> state and I would expect that the cluster should decide at some point to
>>> shutdown the paused VMs and continue with the VMs that are already running
>>> at other hosts.
>>>
>>> Is this behavior normal?
>>>
>>
>> I believe it is not the expected behavior - the VM should not stay in
>> paused state when its lease expires. But we know about this, see comment 9
>> in [1].
>>
>> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1459865
>>
>>
>>>
>>> Thanx,
>>> Alex
>>>
>>> On Tue, Sep 19, 2017 at 10:18 AM, Alex K 
>>> wrote:
>>>
>>>> Hi All,
>>>>
>>>> Just completed the tests and it works great.
>>>> VM leases is just what I needed.
>>>>
>>>> Thanx,
>>>> Alex
>>>>
>>>> On Tue, Sep 19, 2017 at 10:16 AM, Yaniv Kaul  wrote:
>>>>
>>>>>
>>>>>
>>>>> On Tue, Sep 19, 2017 at 1:00 AM, Alex K 
>>>>> wrote:
>>>>>
>>>>>> Enabling VM leases could be an answer to this. Will test tomorrow.
>>>>>>
>>>>>>
>>>>> Indeed. Let us know how it worked for you.
>>>>>
>>>>>
>>>>>> Thanx,
>>>>>> Alex
>>>>>>
>>>>>> On Sep 18, 2017 7:50 PM, "Alex K"  wrote:
>>>>>>
>>>>>> Hi All,
>>>>>>
>>>>>> I have the following issue with the HA behavior of oVirt 4.1 and need
>>>>>> to check with you if there is any work around from your experience.
>>>>>>
>>>>>> I have 3 servers (A, B, C) with hosted engine in self hosted setup on
>>>>>> top gluster with replica 3 + 1 arbiter. All good except one point:
>>>>>>
>>>>>> The hosts have been configured with power management using IPMI
>>>>>> (server iLO).
>>>>>> If I disconnect power from one host (say C) (or disconnect all
>>>>>> network cables of the host) the two other hosts go to a loop where they 
>>>>>> try
>>>>>> to verify the status of the host C by issuing power management commands 
>>>>>> to
>>>>>> the host C. Since power of host is off the server iLO does not respond on
>>>>>> the network and the power management of host C fails, leaving the VMs 
>>>>>> that
>>>>>> were running on the host C in an unknown state and they are never 
>>>>>> restarted
>>>>>> to the other hosts.
>>>>>>
>>>>>> Is there any fencing option to change this behavior so as if both
>>>>>> available hosts fail to do power management of the unresponsive host to
>>>>>> decide that the host is down and to restart the VMs of that host to the
>>>>>> other available hosts.
>>>>>>
>>>>>>
>>>>> No, this is a bad assumption. Perhaps they are the ones isolated form
>>>>> it?
>>>>> Y.
>>>>>
>>>>>
>>>>>>
>>>>>> I could also add additional power management through UPS to avoid
>>>>>> this issue but this is not currently an option and I am interested to see
>>>>>> if this behavior can be tweaked.
>>>>>>
>>>>>> Thanx,
>>>>>> Alex
>>>>>>
>>>>>>
>>>>>>
>>>>>> ___
>>>>>> 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] Odp: How to import OVA file into oVirt

[Arik Hadas]

On Tue, Sep 19, 2017 at 4:52 PM, gabriel_skup...@o2.pl <
gabriel_skup...@o2.pl> wrote:

> I also tried to use the Import Virtual Machines option, there is an option
> to set the source to Vmware Virtual Appliance (OVA) but I don't know how to
> fill in the Path box. Tried http://ip_address/file.ova
>  but did not work.
>

Yes, that's the right way of doing that.
In the path you should specify the local path to the file on the host, for
example if you placed in the export domain it will be something like:
/rhev/data-center///.../file.ova
but you can put it also in /tmp in some specific host and select that host
as a proxy.


>
> G.
>
> Dnia 19 września 2017 15:40 gabriel_skup...@o2.pl 
> napisał(a):
>
> I am trying to import OVA file into my test oVirt env. I already have the
> export domain configured but when I go to the "VM Import" tab the "Import"
> button in inactive.
>
> oVirt 4.1.5/4.1.6
>
> Any clue?
>
> G.
> ___
> 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 HA behavior

[Arik Hadas]

On Tue, Sep 19, 2017 at 3:27 PM, Alex K  wrote:

> On Tue, Sep 19, 2017 at 2:26 PM, Arik Hadas  wrote:
>
>>
>> On Tue, Sep 19, 2017 at 12:44 PM, Alex K  wrote:
>>
>>> A second test did not yield the same result.
>>> This time the VMs were restarted to another host and when the lost host
>>> recovered no VMs were running on it.
>>> Seems that there is a racing issue somewhere.
>>>
>>
>> Did you test with the same VM?
>>
> Yes
>
>> were the disks + lease located on the same storage domains in both tests?
>>
> Yes. On all cases the leases are on same storage domain, the same where
> the VM disks reside.
>
>> did the VM run on the same host (and if not, is the libvirt + qemu
>> versions different between the two?).
>>
> Yes
>
>> It may be a racing issue but not necessarily. There is an observation in
>> the bug I mentioned before that it happens only (/more) with certain
>> storage types...
>>
> The storage is based on gluster volume, replica 3 with 1 arbiter.
> The gluster version is 3.8.12.
> A third test yielded the same issue, VMs on recovered host remained in
> paused status.
>
>

Ack, thanks.
So I suggest you to add yourself (as CC) to [1] so you will be informed
about the resolution for this. In light of your answers it does look like a
racing issue.

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1459865


>
>>
>>>
>>> Thanx,
>>> Alex
>>>
>>>
>>> On Tue, Sep 19, 2017 at 11:52 AM, Arik Hadas  wrote:
>>>
>>>>
>>>>
>>>> On Tue, Sep 19, 2017 at 11:41 AM, Alex K 
>>>> wrote:
>>>>
>>>>> Hi again,
>>>>>
>>>>> I performed a different test by isolating one host (say host A)
>>>>> through removing all its network interfaces (thus power management through
>>>>> IPMI was also not avaialble).
>>>>> The VMs (with VM lease enabled) were successfully restarted to another
>>>>> host.
>>>>> When connecting back the host A, the cluster performed a power
>>>>> management and the host became a member of the cluster.
>>>>> The VMs that were running on the host A were found "paused", which is
>>>>> normal.
>>>>> After 15 minutes I see that the VMs at host A are still in "paused"
>>>>> state and I would expect that the cluster should decide at some point to
>>>>> shutdown the paused VMs and continue with the VMs that are already running
>>>>> at other hosts.
>>>>>
>>>>> Is this behavior normal?
>>>>>
>>>>
>>>> I believe it is not the expected behavior - the VM should not stay in
>>>> paused state when its lease expires. But we know about this, see comment 9
>>>> in [1].
>>>>
>>>> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1459865
>>>>
>>>>
>>>>>
>>>>> Thanx,
>>>>> Alex
>>>>>
>>>>> On Tue, Sep 19, 2017 at 10:18 AM, Alex K 
>>>>> wrote:
>>>>>
>>>>>> Hi All,
>>>>>>
>>>>>> Just completed the tests and it works great.
>>>>>> VM leases is just what I needed.
>>>>>>
>>>>>> Thanx,
>>>>>> Alex
>>>>>>
>>>>>> On Tue, Sep 19, 2017 at 10:16 AM, Yaniv Kaul 
>>>>>> wrote:
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Tue, Sep 19, 2017 at 1:00 AM, Alex K 
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Enabling VM leases could be an answer to this. Will test tomorrow.
>>>>>>>>
>>>>>>>>
>>>>>>> Indeed. Let us know how it worked for you.
>>>>>>>
>>>>>>>
>>>>>>>> Thanx,
>>>>>>>> Alex
>>>>>>>>
>>>>>>>> On Sep 18, 2017 7:50 PM, "Alex K"  wrote:
>>>>>>>>
>>>>>>>> Hi All,
>>>>>>>>
>>>>>>>> I have the following issue with the HA behavior of oVirt 4.1 and
>>>>>>>> need to check with you if there is any work around from your 
>>>>>>>> experience.
>>>>>

Re: [ovirt-users] Odp: How to import OVA file into oVirt

[Arik Hadas]

On Wed, Sep 20, 2017 at 11:59 AM, gabriel_skup...@o2.pl <
gabriel_skup...@o2.pl> wrote:

>
> Dnia 19 września 2017 16:03 Arik Hadas  napisał(a):
>
>
>
> On Tue, Sep 19, 2017 at 4:52 PM, 
> gabriel_skup...@o2.pl < gabriel_skup...@o2.pl>
> wrote:
>
> I also tried to use the Import Virtual Machines option, there is an option
> to set the source to Vmware Virtual Appliance (OVA) but I don't know how to
> fill in the Path box. Tried http://ip_address/file.ova
> <https://domanin/file.ova> but did not work.
>
>
> Yes, that's the right way of doing that.
> In the path you should specify the local path to the file on the host, for
> example if you placed in the export domain it will be something like:
> /rhev/data-center///.../file.ova
> but you can put it also in /tmp in some specific host and select that host
> as a proxy.
>
>
> Thanks, it works but now. I am getting:
> -Failed to convert Vm ASAv
> and then
> -Failed to import Vm ASAv to Data Center Default, Cluster Default.
>
> Do you know how to troubleshoot it?
>

So you managed to reach the conversion phase - that's a good progress.
We'll need the VDSM log that covers the time of the conversion on the host
that was selected as proxy in order to investigate the failure. Could you
please file a bug [1] and attach the log to that bug?

[1] https://bugzilla.redhat.com/enter_bug.cgi?product=vdsm


>
>
>
>
> G.
>
> Dnia 19 września 2017 15:40 gabriel_skup...@o2.pl <
> gabriel_skup...@o2.pl> napisał(a):
>
> I am trying to import OVA file into my test oVirt env. I already have the
> export domain configured but when I go to the "VM Import" tab the "Import"
> button in inactive.
>
> oVirt 4.1.5/4.1.6
>
> Any clue?
>
> G.
> ___
> 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] Odp: How to import OVA file into oVirt

[Arik Hadas]

On Wed, Sep 20, 2017 at 12:55 PM, gabriel_skup...@o2.pl <
gabriel_skup...@o2.pl> wrote:

>
> Dnia 20 września 2017 11:25 Arik Hadas  napisał(a):
>
>
>
> On Wed, Sep 20, 2017 at 11:59 AM, 
> gabriel_skup...@o2.pl < gabriel_skup...@o2.pl>
> wrote:
>
>
> Dnia 19 września 2017 16:03 Arik Hadas < 
> aha...@redhat.com> napisał(a):
>
>
>
> On Tue, Sep 19, 2017 at 4:52 PM, 
> gabriel_skup...@o2.pl < 
> gabriel_skup...@o2.pl> wrote:
>
> I also tried to use the Import Virtual Machines option, there is an option
> to set the source to Vmware Virtual Appliance (OVA) but I don't know how to
> fill in the Path box. Tried http://ip_address/file.ova
> <https://domanin/file.ova> but did not work.
>
>
> Yes, that's the right way of doing that.
> In the path you should specify the local path to the file on the host, for
> example if you placed in the export domain it will be something like:
> /rhev/data-center///.../file.ova
> but you can put it also in /tmp in some specific host and select that host
> as a proxy.
>
>
> Thanks, it works but now. I am getting:
> -Failed to convert Vm ASAv
> and then
> -Failed to import Vm ASAv to Data Center Default, Cluster Default.
>
> Do you know how to troubleshoot it?
>
>
> So you managed to reach the conversion phase - that's a good progress.
> We'll need the VDSM log that covers the time of the conversion on the host
> that was selected as proxy in order to investigate the failure. Could you
> please file a bug [1] and attach the log to that bug?
>
> [1] https://bugzilla.redhat.com/enter_bug.cgi?product=vdsm
>
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1493480
>

Thanks.
Let's discuss it there.


>
>
>
>
>
>
>
>
>
> G.
>
> Dnia 19 września 2017 15:40 
> gabriel_skup...@o2.pl < 
> gabriel_skup...@o2.pl> napisał(a):
>
> I am trying to import OVA file into my test oVirt env. I already have the
> export domain configured but when I go to the "VM Import" tab the "Import"
> button in inactive.
>
> oVirt 4.1.5/4.1.6
>
> Any clue?
>
> G.
> ___
> 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] VM-Clone issue

[Arik Hadas]

On Thu, Oct 5, 2017 at 3:15 PM, Shamam Amir 
wrote:

> Dear All,
> We are using oVirt release *Version 4.1.5.2.  *I was trying to make a
> clone of a VM but I got the following message* "*Error while executing
> action CloneVm: Internal Engine Error", I found that when cloud-init is
> used in the vm's edit section, this error occurs, but when the vm is
> configured without cloud init, the clone was completed successfully.  I
> wondered if this is a bug or something else?
>
> The log file is in this link
> https://paste.fedoraproject.org/paste/f~sHprL93BNZ-iJzoFDyww
>

That's a bug.
A recent fix for [1] changed the engine to take the root password from the
VM-init configuration that is set on the template in some scenarios of
adding a VM but when cloning a VM that is set with VM-init configuration
and that is based on a template which is not set with VM-init
configuration, this leads to a NullPointerException. Could you please file
a bug?

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1448831


>
> Best Regards
>
> ___
> 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] Stucked VM Migration and now only run once

[Arik Hadas]

You wrote that reboot didn't help, is it the host that you rebooted? Because 
engine restart will release the migration's lock and you'll be able to run the 
VM normally for sure.

Since you managed to run the VM using run-once while it was locked, I guess 
you're using ovirt 3.3.1/3.3.2/3.3.3/3.3.4 right?
We fixed several flows in which the migration's lock was not released since 
then, so I suggest to upgrade the system.
If it happens with any other version, please provide the logs Oved mentioned 
and specify which version of engine you're using.

Thanks,
Arik

- Original Message -
> Can you provide the engine and host logs?
> Also, please specify when the migration happened, and in addition when did
> you try to run the VM.
> It will help understand the flow in the logs.
> 
> Thanks,
> Oved
> 
> - Original Message -
> > From: "Kurt Woitschach" 
> > To: users@ovirt.org
> > Sent: Saturday, December 27, 2014 9:22:35 PM
> > Subject: [ovirt-users] Stucked VM Migration and now only run once
> > 
> > Hi all,
> > 
> > we have a Problem with a VM that can only be started in run-once mode.
> > 
> > After a temporary network disconnect on the hosting node, the vm (and
> > some others) was down. When I tried to start regularly, it showed a
> > currently beeing migrated status.
> > I only could start it with run-once.
> > 
> > Reboot didn't make a change.
> > 
> > Any ideas?
> > 
> > 
> > Greets
> > Kurt
> > 
> > --
> > 
> > 
> > Kurt Woitschach-Müller  kurt.woitschach-muel...@tngtech.com *
> > +49-1743180076
> > TNG Technology Consulting GmbH, Betastr. 13a, 85774 Unterföhring
> > Geschäftsführer: Henrik Klagges, Gerhard Müller, Christoph Stock
> > Sitz: Unterföhring * Amtsgericht München * HRB 135082
> > 
> > 
> > 
> > ___
> > 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] Integrated process for import VMs from VMware!

[Arik Hadas]

Hi All,

We are working these days on implementing an integrated process for import 
virtual machines from different sources, other than oVirt's export/data 
domains, that will be introduced in oVirt 3.6.
A glimpse on how you can use it to import a VM from VMware into oVirt is 
available at:
https://www.youtube.com/watch?v=QSss__Nl5rU

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

Re: [ovirt-users] [ovirt-devel] HA not working 3.4.2

[Arik Hadas]

Hi,

- Original Message -
> Hi i was testing HA of ovirt,(i am from Xenserver background and trying to
> use KVM solution in our environment)
> 
> Have 2 hosts with NFS storage and i tested migration between these two hosts.
> 
> On Host2 while VM was running on it, i unplugged Power cable and it took long
> minutes to update that VM is down,okkk now long wait..
> ..
> .
> ...
> 
> VM state changed to unkown and not booted on second Node ie Host1
> 
> its been half an hour and still the VM is not restarted
> 
> What can be the issue?What should i do it make the VM in real HA so that it
> will be restarted on the active node.

We don't restart the VM in that case on purpose, since we really don't know
what's the status of the VM - the host might have been just disconnected from
the network while the VM is still running (and connected to the storage),
so if we'll also run the VM on a different host, we'll get "split-brain".

In order to restart HA VMs which were running on host that went down, you either
needs to have power-management defined for that host (for automatic restart) or
to trigger it manually by selecting "confirm host has been rebooted" when the
host is changed to non-responsive state (and you need to have additional host
which is up of course).

> 
> How HA is enabled
> what i did was while creating vm> Advanced option>High Availability>Highly
> Available
> 
> I am sure this can be a configuration error,Can some one please help me with
> enabling HA.
> 
> Please Help
> 
> Thanks
> 
> ___
> Devel mailing list
> de...@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Orphaned record in the engine DB prevents host removal

[Arik Hadas]

- Original Message -
> On 04/07/14 14:45, Oved Ourfali wrote:
> > Is there a migration of this VM in progress? Did it migrate recently?
> Thank you Oved, I have already solved the problem, I have posted the
> solution to the list.
> 
> However I don't understand how the data is recorded in the table
> "vm_dyanmic".
> 
> I guess that in this table the engine records the current status data of
> the vm's in the datacenter. In my engine DB almost all the registries in
> the "vm_dynamic" table have a vm id in the "migrating_to_vds" field,
> this id is the same in the "run_on_vds" field.
> 
> Is it right that the "migrating_to_vds" field have a value after the vm
> has been migrated??

Yes, we're about to fix it.

Note that there is an open bug for this issue:
https://bugzilla.redhat.com/show_bug.cgi?id=1112359
If you will be able to provide the info I've asked for there,
it could help us to solve it faster :)

Arik

> 
> My setup:
> 
> oVirt Engine Version: 3.4.0-1.el6
> Nodes (vds's, hosts, etc.): Centos 6.5 ovirt-node 3.4, vdsm-4.14.6-0.el6
> 
> Thank you, and happy weekend!
> 
> Federico
> > I suggest to attach the engine log here as well, if possible, for
> > examination. Cc-ing some guys that might help but bare in mind that for
> > some of them it is already weekend.
> >
> > Oved
> >
> > On Jul 4, 2014 6:07 PM, Federico Alberto Sayd  wrote:
> >> Hello People:
> >>
> >> I am trying to remove a host from ovirt-engine but I have fouHello People:
> > I am trying to remove a host from ovirt-engine but I have found that a
> > orphaned record in the engine DB prevents the removal of the host.
> > The host is in maintenance mode, it doesn't have vm's running on it.
> > The engine logs says that there is a reference to the id of the host
> > (vds_id in the table vds_static) in the field "migrating_to_vds" in the
> > table "dynamic_vds". Obviously this is a orphaned record, but a
> > constraint in the table "dynamic_vds" prevents the removal of the host.
> > How can I solve this?
> > Someone that knows the internals of engine's DB that can confirm if I
> > can remove the problematic registry in order to remove the host??
> > Another solution?
> >
> > I really need to remove this host. Please help and
> >
> > Thanks!
> > ___
> > 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] Orphaned record in the engine DB prevents host removal

[Arik Hadas]

- Original Message -
> 
> 
> El Domingo, 6 de Julio de 2014 07.06 CLT, Arik Hadas  Ha
> escrito:
> 
> 
> 
> 
> - Original Message -
> > On 04/07/14 14:45, Oved Ourfali wrote:
> > > Is there a migration of this VM in progress? Did it migrate recently?
> > Thank you Oved, I have already solved the problem, I have posted the
> > solution to the list.
> > 
> > However I don't understand how the data is recorded in the table
> > "vm_dyanmic".
> > 
> > I guess that in this table the engine records the current status data of
> > the vm's in the datacenter. In my engine DB almost all the registries in
> > the "vm_dynamic" table have a vm id in the "migrating_to_vds" field,
> > this id is the same in the "run_on_vds" field.
> > 
> > Is it right that the "migrating_to_vds" field have a value after the vm
> &g t; has been migrated??
> 
> Yes, we're about to fix it.
> 
> Note that there is an open bug for this issue:
> https://bugzilla.redhat.com/show_bug.cgi?id=1112359
> If you will be able to provide the info I've asked for there,
> it could help us to solve it faster :)
> 
> Arik
> 
> > 
> > My setup:
> > 
> > oVirt Engine Version: 3.4.0-1.el6
> > Nodes (vds's, hosts, etc.): Centos 6.5 ovirt-node 3.4, vdsm-4.14.6-0.el6
> > 
> > Thank you, and happy weekend!
> > 
> > Federico
> > > I suggest to attach the engine log here as well, if possible, for
> > > examination. Cc-ing some guys that might help but bare in mind that for
> > > some of them it is already weekend.
> > > 
> > > Oved
> > > 
> > > On Jul 4, 2014 6:07 PM, Federico Alberto Sayd wrote:
> > >> Hello People:
> > >> 
> > >> I am trying t o remove a host from ovirt-engine but I have fouHello
> > >> People:
> > > I am trying to remove a host from ovirt-engine but I have found that a
> > > orphaned record in the engine DB prevents the removal of the host.
> > > The host is in maintenance mode, it doesn't have vm's running on it.
> > > The engine logs says that there is a reference to the id of the host
> > > (vds_id in the table vds_static) in the field "migrating_to_vds" in the
> > > table "dynamic_vds". Obviously this is a orphaned record, but a
> > > constraint in the table "dynamic_vds" prevents the removal of the host.
> > > How can I solve this?
> > > Someone that knows the internals of engine's DB that can confirm if I
> > > can remove the problematic registry in order to remove the host??
> > > Another solution?
> > > 
> > > I really need to remove this h ost. Please help and
> > > 
> > > Thanks!
> > > ___
> > > Users mailing list
> > > Users@ovirt.org
> > > http://lists.ovirt.org/mailman/listinfo/user
> Indeed, you are right, is the same bug. I didn't find this bug when googled
> the problem. I have attached an extract of the logs when I tried to remove
> the host, it looks identical to the logs reported in the bug except that
> postgres transactions are logged in Spanish.

Thanks

> I will try to find the log entry when the vm was migrated and the value was
> not correctly updated in the "migrating_to_vds" field. I think that that is
> the more critical bug.

I was able to reproduce it on 3.4 branch and to understand the problem.
On master it was fixed by: http://gerrit.ovirt.org/#/c/24799/
I'll backport this patch and it will solve it on 3.4 as well.

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

Re: [ovirt-users] virtio-serial0 duplicate id

[Arik Hadas]

- Original Message -
> 
> > On 11 Feb 2016, at 17:02, Johannes Tiefenbacher  wrote:
> > 
> > Hi,
> > finally I am posting something to this list :) I read it for quite some
> > time now and I am an ovirt user since 3.0.
> 
> Hi,
> welcome:)
> 
> > 
> > 
> > I updated an engine installation from 3.2 to 3.6 (stepwise of course, and
> > yes I know that's pretty outdated ;-). Then I updated the associated
> > Centos6 hosts vdsm as well, from 3.10.x to 3.16.30. I also set my cluster
> > comp level to 3.5(3.6 comp level is only possible with El7 hosts if I
> > understood correctly).
> > 
> > After my first failover test a VM could not be restarted, altough the host
> > where it was running could correctly be fenced.
> > 
> > The reason according to engine's log was this:
> > 
> > VM  is down with error. Exit message: internal error process exited
> > while connecting to monitor: qemu-kvm: -device
> > virtio-serial-pci,id=virtio-serial0,max_ports=16,bus=pci.0,addr=0x4:
> > Duplicate ID 'virtio-serial0' for device
> > 
> > 
> > I then recognized that I am not able to run this VM on any host. Ich
> > checked the virtual hardware in the engine database and could confirm that
> > ALL my VMs had this problem: 2 devices with alias='virtio-serial0’
> 
> it may very well be a bug, but it would be quite difficult to say unless it
> is reproducible. It may be broken from earlier releases
> Arik/Shmuel, maybe it rings a bell?

In 3.6 we changed virtio-serial to be a managed device.
The script named 03_06_0310_change_virtio_serial_to_managed_device.sql changes 
unmanaged virtio-serial devices (that were all unmanaged before) to be managed.
A potential flow that will cause this duplication I can think of is:
1. Have a running VM in a pre-3.6 engine - it has unmanaged virtio-serial
2. Upgrade to 3.6 while the VM is running - the unmanaged virtio-serial becomes 
managed
3. Do something that will change the hash of the devices
=> the engine will add an additional unmanaged virtio-serial device

Why didn't it happen before? because the handling of unmanaged devices was:
1. Upon change in the VM devices (their hash), ask for all the devices 
(full-list)
2. Remove all previous unmanaged devices
3. Add every device that does not exist in the database
When we add an unmanaged device we generate a new ID (!) - therefore we had to 
remove all the previous unmanaged devices before adding the new ones.
If the previous unmanaged virtio-serial became managed, it is not removed and 
we will end up having two virtio-serial devices.

@Johannes - is it true that the VM was running before the engine got updated to 
3.6 and wasn't powered-off since then?

I managed to simulate this.
We probably need to prevent the addition of unmanaged virtio-serial in 3.6 
engine but IMO we should also use the ID reported by VDSM instead of generating 
a new one to eliminate similar issues in the future.
@Eli, Omer - can you recall why can't we use the ID we get from VDSM for the 
unmanaged devices?
(we can continue this discussion in devel-list or in bugzilla..)

> 
> > 
> > e.g.:
> > 
> > 
> > engine=# SELECT * FROM vm_device WHERE vm_device.device = 'virtio-serial'
> > AND vm_id = 'cbfa359f-d0b8-484b-8ec0-cf9b8e4bb3ec' ORDER BY vm_id;
> > -[ RECORD 1
> > ]-+-
> > device_id | 2821d03c-ce88-4613-9095-e88eadcd3792
> > vm_id | cbfa359f-d0b8-484b-8ec0-cf9b8e4bb3ec
> > type  | controller
> > device| virtio-serial
> > address   |
> > boot_order| 0
> > spec_params   | { }
> > is_managed| t
> > is_plugged| f
> > is_readonly   | f
> > _create_date  | 2016-01-14 08:30:43.797161+01
> > _update_date  | 2016-02-10 10:04:56.228724+01
> > alias | virtio-serial0
> > custom_properties | { }
> > snapshot_id   |
> > logical_name  |
> > is_using_scsi_reservation | f
> > -[ RECORD 2
> > ]-+-
> > device_id | 29e0805f-d836-451a-9ec3-9031baa995e6
> > vm_id | cbfa359f-d0b8-484b-8ec0-cf9b8e4bb3ec
> > type  | controller
> > device| virtio-serial
> > address   | {bus=0x00, domain=0x, type=pci, slot=0x04,
> > function=0x0}
> > boot_order| 0
> > spec_params   | { }
> > is_managed| f
> > is_plugged| t
> > is_readonly   | f
> > _create_date  | 2016-02-11 13:47:02.69992+01
> > _update_date  |
> > alias | virtio-serial0
> > custom_properties |
> > snapshot_id   |
> > logical_name  |
> > is_using_scsi_reservation | f
> > 
> > 
> > 
> > My solution was 

Re: [ovirt-users] virtio-serial0 duplicate id

[Arik Hadas]

- Original Message -
> 
> 
> - Original Message -
> > 
> > > On 11 Feb 2016, at 17:02, Johannes Tiefenbacher  wrote:
> > > 
> > > Hi,
> > > finally I am posting something to this list :) I read it for quite some
> > > time now and I am an ovirt user since 3.0.
> > 
> > Hi,
> > welcome:)
> > 
> > > 
> > > 
> > > I updated an engine installation from 3.2 to 3.6 (stepwise of course, and
> > > yes I know that's pretty outdated ;-). Then I updated the associated
> > > Centos6 hosts vdsm as well, from 3.10.x to 3.16.30. I also set my cluster
> > > comp level to 3.5(3.6 comp level is only possible with El7 hosts if I
> > > understood correctly).
> > > 
> > > After my first failover test a VM could not be restarted, altough the
> > > host
> > > where it was running could correctly be fenced.
> > > 
> > > The reason according to engine's log was this:
> > > 
> > > VM  is down with error. Exit message: internal error process
> > > exited
> > > while connecting to monitor: qemu-kvm: -device
> > > virtio-serial-pci,id=virtio-serial0,max_ports=16,bus=pci.0,addr=0x4:
> > > Duplicate ID 'virtio-serial0' for device
> > > 
> > > 
> > > I then recognized that I am not able to run this VM on any host. Ich
> > > checked the virtual hardware in the engine database and could confirm
> > > that
> > > ALL my VMs had this problem: 2 devices with alias='virtio-serial0’
> > 
> > it may very well be a bug, but it would be quite difficult to say unless it
> > is reproducible. It may be broken from earlier releases
> > Arik/Shmuel, maybe it rings a bell?
> 
> In 3.6 we changed virtio-serial to be a managed device.
> The script named 03_06_0310_change_virtio_serial_to_managed_device.sql
> changes unmanaged virtio-serial devices (that were all unmanaged before) to
> be managed.
> A potential flow that will cause this duplication I can think of is:
> 1. Have a running VM in a pre-3.6 engine - it has unmanaged virtio-serial
> 2. Upgrade to 3.6 while the VM is running - the unmanaged virtio-serial
> becomes managed
> 3. Do something that will change the hash of the devices
> => the engine will add an additional unmanaged virtio-serial device
> 
> Why didn't it happen before? because the handling of unmanaged devices was:
> 1. Upon change in the VM devices (their hash), ask for all the devices
> (full-list)
> 2. Remove all previous unmanaged devices
> 3. Add every device that does not exist in the database
> When we add an unmanaged device we generate a new ID (!) - therefore we had
> to remove all the previous unmanaged devices before adding the new ones.
> If the previous unmanaged virtio-serial became managed, it is not removed and
> we will end up having two virtio-serial devices.
> 
> @Johannes - is it true that the VM was running before the engine got updated
> to 3.6 and wasn't powered-off since then?
> 
> I managed to simulate this.
> We probably need to prevent the addition of unmanaged virtio-serial in 3.6
> engine but IMO we should also use the ID reported by VDSM instead of
> generating a new one to eliminate similar issues in the future.
> @Eli, Omer - can you recall why can't we use the ID we get from VDSM for the
> unmanaged devices?
> (we can continue this discussion in devel-list or in bugzilla..)
> 
> > 
> > > 
> > > e.g.:
> > > 
> > > 
> > > engine=# SELECT * FROM vm_device WHERE vm_device.device = 'virtio-serial'
> > > AND vm_id = 'cbfa359f-d0b8-484b-8ec0-cf9b8e4bb3ec' ORDER BY vm_id;
> > > -[ RECORD 1
> > > ]-+-
> > > device_id | 2821d03c-ce88-4613-9095-e88eadcd3792
> > > vm_id | cbfa359f-d0b8-484b-8ec0-cf9b8e4bb3ec
> > > type  | controller
> > > device| virtio-serial
> > > address   |
> > > boot_order| 0
> > > spec_params   | { }
> > > is_managed| t
> > > is_plugged| f
> > > is_readonly   | f
> > > _create_date  | 2016-01-14 08:30:43.797161+01
> > > _update_date  | 2016-02-10 10:04:56.228724+01
> > > alias | virtio-serial0
> > > custom_properties | { }
> > > snapshot_id   |
> > > logical_name  |
> > > is_using_scsi_reservation | f
> > > -[ RECORD 2
> > > ]-+-
> > > device_id | 29e0805f-d836-451a-9ec3-9031baa995e6
> > > vm_id | cbfa359f-d0b8-484b-8ec0-cf9b8e4bb3ec
> > > type  | controller
> > > device| virtio-serial
> > > address   | {bus=0x00, domain=0x, type=pci,
> > > slot=0x04,
> > > function=0x0}
> > > boot_order| 0
> > > spec_params   | { }
> > > is_managed| f
> > > is_plugged| t
> > > is_readonly   | f
> > > _create_date  | 2016-02

Re: [ovirt-users] VMs running in DB, but not in VDS

[Arik Hadas]

Hi Satheesaran,

Could you please add the full engine.log?
It would be best to open a bug and attach the log to it

Thanks,
Arik

- Original Message -
> 
> 
> Hello All,
> 
> I was powering off lot of VMs ( around 29 vms ) in one go, by selecting
> them all,
> and 'power off' option.
> 
> While doing so, I see that 2 of the VMs are stuck in powering down state.
> 
> I see the following exception in engine.log
> 
> 2016-06-20 05:10:57,645 ERROR
> [org.ovirt.engine.core.vdsbroker.VmsMonitoring]
> (DefaultQuartzScheduler_Worker-53) [7f967349] Failed during vms
> monitoring on host host1.lab.eng.blr.redhat
> .com error is: java.lang.ClassCastException
> 2016-06-20 05:10:57,645 ERROR
> [org.ovirt.engine.core.vdsbroker.VmsMonitoring]
> (DefaultQuartzScheduler_Worker-53) [7f967349] Exception::
> java.lang.ClassCastException
> 
> 
> and also the following error messages
> 
> 
> 2016-06-20 05:12:01,950 INFO
> [org.ovirt.engine.core.vdsbroker.VmAnalyzer]
> (DefaultQuartzScheduler_Worker-90) [] VM
> '59d48f24-d6b8-4e9e-b020-b728ed239da3(appvm03) is running in db and not
> running in VDS 'host1.lab.eng.blr.redhat.com'
> 2016-06-20 05:12:01,950 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.FullListVDSCommand]
> (DefaultQuartzScheduler_Worker-90) [] START, FullListVDSCommand(HostName
> = , FullListVDSCommandParameters:{runAsync='true',
> hostId='f4a25596-079b-44ed-970b-2142c67b9873',
> vds='Host[,f4a25596-079b-44ed-970b-2142c67b9873]',
> vmIds='[10c5e550-4b07-4a25-9a96-ae016864f2a8]'}), log id: 28c780ea
> 2016-06-20 05:12:02,038 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.FullListVDSCommand]
> (DefaultQuartzScheduler_Worker-90) [] FINISH, FullListVDSCommand,
> return: [{status=Up, nicModel=rtl8139,pv, emulatedMachine=rhel6.5.0,
> guestDiskMapping={e5051a6c-dc96-44eb-b={name=/dev/vda},
> QEMU_DVD-ROM_QM3={name=/dev/sr0}},
> vmId=10c5e550-4b07-4a25-9a96-ae016864f2a8, pid=6368,
> devices=[Ljava.lang.Object;@67be1679, smp=2, vmType=kvm, displayIp=0,
> display=vnc, displaySecurePort=-1, memSize=4096, displayPort=5900,
> spiceSecureChannels=smain,sdisplay,sinputs,scursor,splayback,srecord,ssmartcard,susbredir,
> statusTime=4726355820, vmName=HostedEngine, clientIp=,
> pauseCode=NOERR}], log id: 28c780ea
> 2016-06-20 05:12:02,040 INFO
> [org.ovirt.engine.core.vdsbroker.VmsMonitoring]
> (DefaultQuartzScheduler_Worker-90) [] Received a memballoon Device
> without an address when processing VM
> 10c5e550-4b07-4a25-9a96-ae016864f2a8 devices, skipping device:
> {device=memballoon, specParams={model=none}, deviceType=balloon,
> type=balloon, alias=balloon0}
> 2016-06-20 05:12:02,040 ERROR
> [org.ovirt.engine.core.vdsbroker.VmsMonitoring]
> (DefaultQuartzScheduler_Worker-90) [] Failed during vms monitoring on
> host host1.lab.eng.blr.redhat.com error is: java.lang.ClassCastException
> 2016-06-20 05:12:02,040 ERROR
> [org.ovirt.engine.core.vdsbroker.VmsMonitoring]
> (DefaultQuartzScheduler_Worker-90) [] Exception::
> java.lang.ClassCastException
> 
> 
> 
> Any help ?
> 
> Thanks,
> Satheesaran S
> 
> 
> 
> ___
> 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] Importing *.ova appliance

[Arik Hadas]

Hi Anantha,

Yes, it is supported but only for OVA appliances that are generated by vSphere 
5.5 and above.
What kind of OVA did you try to import from? (how it was generated?)

Regards,
Arik


- Original Message -
> Hi,
> 
> How do we import a *.ova appliance in oVirt? Starting 3.6.6, we see this
> option in import dialog but, even if we specify the location of OVA files,
> it reports "did not find any VM to import".
> 
> Does oVirt still not support importing OVA appliance?
> --
> 
> Thanks & Regards,
> Anantha Raghava
> 
> 
> ___
> 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] 3.6 -> 4.0 upgrade fails on schema refresh

[Arik Hadas]

Hi,

This is a bit aggressive solution to remove all snapshots with the memory.

Can you confirm that a storage domain that was active while creating the 
snapshot with memory was removed from the system?
This is something that was not covered and could lead to the reported issue.

Until we come up with a proper solution, you can use the following query to 
identify the exact problematic snapshots and remove them before upgrading:
select vm_name, snapshots.description as snapshot_name, snapshot_id from 
snapshots join vm_static on vm_id=vm_guid where CAST(split_part(memory_volume, 
',', 1) AS UUID) not in (select id from storage_domain_static);

Regards,
Arik

- Original Message -
> Hi,
> 
> We have had a similar issue when upgrading, digging into it we found out
> that this was caused by snapshots that had the "Save memory" option
> enabled. We finally ended up deleting any snapshot that had this option
> enabled and then we tried to upgrade, this time the process went smooth.
> 
> Hope this helps.
> 
> Regards.
> 
> El 2016-07-05 18:49, Matt . escribió:
> > OK some update on this.
> > 
> > Removed the db-migrate-script package and reinstalled ovirt-engine and
> > ovirt-engine-setup.
> > 
> > I still have that error and this is the loggingpart:
> > 
> > CONTEXT:  SQL statement "DROP INDEX  IF EXISTS
> > idx_vm_static_template_version_name; CREATE INDEX
> > idx_vm_static_template_version_nam$
> > PL/pgSQL function fn_db_create_index(character varying,character
> > varying,text,text) line 12 at EXECUTE statement
> > psql:/usr/share/ovirt-engine/dbscripts/upgrade/04_00_0140_convert_memory_snapshots_to_disks.sql:93:
> > ERROR:
> > insert or update on table "image_storage_domain_map" violates foreign
> > key constraint
> > "fk_image_storage_domain_map_storage_domain_static"
> > DETAIL:  Key (storage_domain_id)=(006552b0-cae3-4ccb-9baa-ee8c3b8e42cf)
> > is not present in table "storage_domain_static".
> > FATAL: Cannot execute sql command:
> > --file=/usr/share/ovirt-engine/dbscripts/upgrade/04_00_0140_convert_memory_snapshots_to_disks.sql
> > 
> > 2016-07-05 19:40:29 ERROR
> > otopi.plugins.ovirt_engine_setup.ovirt_engine.db.schema
> > schema._misc:313 schema.sh: FATAL:
> > sql command:
> > --file=/usr/share/ovirt-engine/dbscripts/upgrade/04_00_0140_convert_memory_snapshots_to_disks.sql
> > 2016-07-05 19:40:29 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-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/db/schema.py",
> > line 315, in _misc
> > raise RuntimeError(_('Engine schema refresh failed'))
> > RuntimeError: Engine schema refresh failed
> > 
> > Any idea ?
> > 
> > 2016-07-05 15:25 GMT+02:00 Matt . :
> >> I just found out that the file
> >> 
> >> 04_00_0140_convert_memory_snapshots_to_disks.sql
> >> 
> >> is not located in:
> >> 
> >> /usr/share/ovirt-engine/dbscripts/upgrade/
> > ___
> > 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] 3.6 -> 4.0 upgrade fails on schema refresh

[Arik Hadas]

- Original Message -
> El 2016-07-06 11:11, nico...@devels.es escribió:
> > Hi Arik,
> > 
> > El 2016-07-06 10:27, Arik Hadas escribió:
> >> Hi,
> >> 
> >> This is a bit aggressive solution to remove all snapshots with the
> >> memory.
> >> 
> >> Can you confirm that a storage domain that was active while creating
> >> the snapshot with memory was removed from the system?
> >> This is something that was not covered and could lead to the reported
> >> issue.
> >> 
> > 
> > Some of them were available when we did remove a storage backend,
> > indeed. Some were newer, the problem is that I don't know which one
> > actually failed since when this happened we were in a hurry and needed
> > to upgrade ASAP.
> > 
> >> Until we come up with a proper solution, you can use the following
> >> query to identify the exact problematic snapshots and remove them
> >> before upgrading:
> >> select vm_name, snapshots.description as snapshot_name, snapshot_id
> >> from snapshots join vm_static on vm_id=vm_guid where
> >> CAST(split_part(memory_volume, ',', 1) AS UUID) not in (select id from
> >> storage_domain_static);
> >> 
> > 
> > Thanks. We have another oVirt infrastructure and I see this query is
> > returning one row. I'll report back when we upgrade this second
> > infrastructure and provide some details.
> > 
> 
> We've upgraded our second oVirt infrastructure as well, here are the
> steps:
> 
> 1) I run the query you provided, it returned one row.
> 2) I tried upgrading to 4.0 without deleting that snapshot: it failed
> with the error below.
> 3) I deleted the snapshot
> 4) Now I tried upgrading again and everything went smoothly.
> 
> I'd say this is the same issue, apparently.
> 
> Thanks.

Thanks for the update.
I opened a bug for this issue [1].
We will probably just remove the memory from this kind of snapshots 
automatically during the upgrade.

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1353219

> 
> > Regards.
> > 
> >> Regards,
> >> Arik
> >> 
> >> - Original Message -
> >>> Hi,
> >>> 
> >>> We have had a similar issue when upgrading, digging into it we found
> >>> out
> >>> that this was caused by snapshots that had the "Save memory" option
> >>> enabled. We finally ended up deleting any snapshot that had this
> >>> option
> >>> enabled and then we tried to upgrade, this time the process went
> >>> smooth.
> >>> 
> >>> Hope this helps.
> >>> 
> >>> Regards.
> >>> 
> >>> El 2016-07-05 18:49, Matt . escribió:
> >>> > OK some update on this.
> >>> >
> >>> > Removed the db-migrate-script package and reinstalled ovirt-engine and
> >>> > ovirt-engine-setup.
> >>> >
> >>> > I still have that error and this is the loggingpart:
> >>> >
> >>> > CONTEXT:  SQL statement "DROP INDEX  IF EXISTS
> >>> > idx_vm_static_template_version_name; CREATE INDEX
> >>> > idx_vm_static_template_version_nam$
> >>> > PL/pgSQL function fn_db_create_index(character varying,character
> >>> > varying,text,text) line 12 at EXECUTE statement
> >>> > psql:/usr/share/ovirt-engine/dbscripts/upgrade/04_00_0140_convert_memory_snapshots_to_disks.sql:93:
> >>> > ERROR:
> >>> > insert or update on table "image_storage_domain_map" violates foreign
> >>> > key constraint
> >>> > "fk_image_storage_domain_map_storage_domain_static"
> >>> > DETAIL:  Key (storage_domain_id)=(006552b0-cae3-4ccb-9baa-ee8c3b8e42cf)
> >>> > is not present in table "storage_domain_static".
> >>> > FATAL: Cannot execute sql command:
> >>> > --file=/usr/share/ovirt-engine/dbscripts/upgrade/04_00_0140_convert_memory_snapshots_to_disks.sql
> >>> >
> >>> > 2016-07-05 19:40:29 ERROR
> >>> > otopi.plugins.ovirt_engine_setup.ovirt_engine.db.schema
> >>> > schema._misc:313 schema.sh: FATAL:
> >>> > sql command:
> >>> > --file=/usr/share/ovirt-engine/dbscripts/upgrade/04_00_0140_convert_memory_snapshots_to_disks.sql
> >>> > 2016-07-05 19:40:29 DEBUG otopi.context context._executeMethod:142
> >>> > method exception
> &

[ovirt-users] Blog post: Monitoring Improvements in oVirt

[Arik Hadas]

Hi all,

I wrote a blog post that summarizes the recent improvements in the code that 
monitors virtual machines in oVirt.
It describes the changes that were done and shows a comparison of different 
aspects of oVirt with these changes
(based on the master branch) vs oVirt 3.6 without these changes:
http://ahadas.github.io/monitoring-improvements-in-ovirt/

It is mostly a technical post.

However, users might find it interesting as well.
Note that the measurements were taken on an environment with 1 host and 6000 
running VMs (in a pool).
Each VM had a network interface and was diskless.
Obviously, this is not a typical setup but it was useful to easily expose some 
of weak sides of the monitoring.

Your feedback is always welcome!

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

Re: [ovirt-users] [ovirt-devel] Blog post: Monitoring Improvements in oVirt

[Arik Hadas]

- Original Message -
> Hi Arik,
> 
> Very nice output..

Thank you

> 
> see also our mojo page:
> 
> https://mojo.redhat.com/groups/rhev-m-scalability-performance-team
> 
> can you elaborate how did you rampup 6K vms?

1. Created a cluster with 1 real host, 1 fake-VDSM based host and 1 storage 
domain (so the storage pool will be up).
2. Created a pool with 6000 VMs that is based on template with one network 
interface and no disks.
3. Ran all the VMs on fake-VDSM (they were pinned to that host)

At that point I had a fake-VDSM host that runs 6K VMs.
Then, 1. I put all the things in my master-based setup to maintenance and 
removed all VMs.
  2. Configured 1 cluster with this host - all the 6K VMs were added as 
external VMs.
And on 3.6 I did the same - created a cluster only with that host (and the VMs 
were added as external VMs).

By this, I had the exact same setup on both 3.6 and 4.0 and I didn't have 
anything else that could influence the measurements.

Note that that's why many of the numbers presented in the post should not be 
considered as absolute values but only
as a relative values between 3.6 and 4.0 setups.
My point is that when I say that saving the statistics took 2% of the 
interactions with the database, this '2%'
would probably be different in other environments and lower when the system 
does other things my system did not do.

> 
> also can you elaborate the following:
> 
> - HW definition?

Dell optiplex 780, 16GB of RAM, 4 CPUs with 4 cores-per-CPI
Both the engine and fake VDSM were running on that host.

> 
> - java HEAP Size?

I didn't change it manually - initial and maximum heap size of 3971M

> 
> - any postgres tuning ?

No, I kept the default settings.

> 
> 
> we are about to scale out the latest 4.0 RHEVM
> 
> any relevant changes that we should aware of?

Note that only part of these changes are in 4.0.
What bothers me and worth checking on 4.0 is the memory consumption -
in 4.0 we already cache VM statistics but many of the changes that probably lead
of the overall decrement of the memory consumption are missing there.
So it would be interesting to see what is the implication of storing more data
in memory in 4.0 - if it is problematic we can easily remove this cache as it
is rarely used in 4.0.

> 
> -Eldad
> 
> 
> 
> On 07/24/2016 05:15 PM, Arik Hadas wrote:
> > Hi all,
> >
> > I wrote a blog post that summarizes the recent improvements in the code
> > that monitors virtual machines in oVirt.
> > It describes the changes that were done and shows a comparison of different
> > aspects of oVirt with these changes
> > (based on the master branch) vs oVirt 3.6 without these changes:
> > http://ahadas.github.io/monitoring-improvements-in-ovirt/
> >
> > It is mostly a technical post.
> >
> > However, users might find it interesting as well.
> > Note that the measurements were taken on an environment with 1 host and
> > 6000 running VMs (in a pool).
> > Each VM had a network interface and was diskless.
> > Obviously, this is not a typical setup but it was useful to easily expose
> > some of weak sides of the monitoring.
> >
> > Your feedback is always welcome!
> >
> > Regards,
> > Arik
> > ___
> > Devel mailing list
> > de...@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/devel
> 
> 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Migrate machines in unknown state?

[Arik Hadas]

- Original Message -
> Hi,
> 
> We're running oVirt 4.0.1 and today I found out that one of our hosts
> has all its VMs in an unknown state. I actually don't know how (and
> when) did this happen, but I'd like to restore service possibly without
> turning off these machines. The host is up, the VMs are up, 'qemu'
> process exists, no errors, it's just the VMs running on it that have a
> '?' where status is defined.
> 
> Is it safe in this case to simply modify database and set those VM's
> status to 'up'? I remember having to do this a time ago when we faced
> storage issues, it didn't break anything back then. If not, is there a
> "safe" way to migrate those VMs to a different host and restart the host
> that marked them as unknown?

Hi Nicolás,

I assume that the host these VMs are running on is empty in the webadmin,
right? if that is the case then you've probably hit [1]. Changing their
status to up is not the way to go since these VMs will not be monitored.

Yes, there is no other way to resolve it other than changing the DB but
the change should be to update run_on_vds field of these VMs to the host
you know they are running on. Their status will then be updates in 15 sec.

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1354494

Arik.

> 
> Thanks.
> 
> Nicolás
> 
> ___
> 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] Migrate machines in unknown state?

[Arik Hadas]

- Original Message -
> 
> 
> El 04/08/16 a las 07:18, Arik Hadas escribió:
> > - Original Message -
> >> Hi,
> >>
> >> We're running oVirt 4.0.1 and today I found out that one of our hosts
> >> has all its VMs in an unknown state. I actually don't know how (and
> >> when) did this happen, but I'd like to restore service possibly without
> >> turning off these machines. The host is up, the VMs are up, 'qemu'
> >> process exists, no errors, it's just the VMs running on it that have a
> >> '?' where status is defined.
> >>
> >> Is it safe in this case to simply modify database and set those VM's
> >> status to 'up'? I remember having to do this a time ago when we faced
> >> storage issues, it didn't break anything back then. If not, is there a
> >> "safe" way to migrate those VMs to a different host and restart the host
> >> that marked them as unknown?
> > Hi Nicolás,
> >
> > I assume that the host these VMs are running on is empty in the webadmin,
> > right? if that is the case then you've probably hit [1]. Changing their
> > status to up is not the way to go since these VMs will not be monitored.
> 
> Hi Arik,
> 
> By "empty" you mean the webadmin reports the host being running 0 VMs?
> If so, that's not the case, actually the VM count seems to be correct in
> relation to "qemu-*" processes (about 32 VMs), I can even see the
> machines in the "Virtual machines" tab of the host, it's just they are
> all marked with the '?' mark.

No, I meant the 'Host' column in the Virtual Machines tab but if you see
the VMs in the "Virtual machines" sub-tab of the host then run_on_vds
points to the right host..

The host is up in the webadmin as well?
Can you share the engine log?

> 
> Thanks.
> 
> > Yes, there is no other way to resolve it other than changing the DB but
> > the change should be to update run_on_vds field of these VMs to the host
> > you know they are running on. Their status will then be updates in 15 sec.
> >
> > [1] https://bugzilla.redhat.com/show_bug.cgi?id=1354494
> >
> > Arik.
> >
> >> Thanks.
> >>
> >> Nicolás
> >>
> >> ___
> >> 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] VM Import from remote libvirt Server on web gui with Host key verification failed or permission denied error

[Arik Hadas]

Hi Rogério,

Note that your test using virsh was from hlg-rbs-ovirt-kvm01-poa while 
ovirt-engine chose hlg-rbs-ovirt-kvm02-poa.rbs.com.br as the proxy host.
You need to make sure that all your hosts are configured with ssh-keys or 
explicitly choose one that is configured properly as a proxy (in the import 
dialog).

- Original Message -
> Hi Ovirt Jedi´s !!!
> 
> First of all, congratulations for this amazing product. I am an Vmware and
> Hyper-V Engineer but i am very excited with oVirt.
> 
> Now, let´s go to work ... :-)
> 
> I am trying to Import vm from remote libvirt server on web gui but i was
> unable to solve the problem until now.
> 
> 
> 
> Node logs :
> 
> [root@hlg-rbs-ovirt-kvm01-poa ~]# tail -f /var/log/vdsm/vdsm.log | grep -i
> error | grep -v Host.getStats
> jsonrpc.Executor/0::ERROR::2016-10-06
> 10:24:52,432::v2v::151::root::(get_external_vms) error connection to
> hypervisor: 'Cannot recv data: Permission denied, please try
> again.\r\nPermission denied, please try again.\r\nPermission denied
> (publickey,gssapi-keyex,gssapi-with-mic,password).: Connection reset by
> peer'
> jsonrpc.Executor/0::INFO::2016-10-06
> 10:24:52,433::__init__::513::jsonrpc.JsonRpcServer::(_serveRequest) RPC call
> Host.getExternalVMs failed (error 65) in 10.05 seconds
> 
> [root@hlg-rbs-ovirt-kvm02-poa ~]# grep error /var/log/vdsm/vdsm.log | grep
> get_external_vms
> jsonrpc.Executor/7::ERROR::2016-10-06
> 10:25:37,344::v2v::151::root::(get_external_vms) error connection to
> hypervisor: 'Cannot recv data: Host key verification failed.: Connection
> reset by peer'
> [root@hlg-rbs-ovirt-kvm02-poa ~]#
> 
> Engine Logs :
> 
> [root@hlg-rbs-ovirt01-poa ~]# tail -f /var/log/ovirt-engine/engine.log
> 2016-10-06 10:24:42,377 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetVmsFromExternalProviderVDSCommand]
> (default task-97) [] START, GetVmsFromExternalProviderVDSCommand(HostName =
> hlg-rbs-ovirt-kvm01-poa.rbs.com.br ,
> GetVmsFromExternalProviderParameters:{runAsync='true',
> hostId='5feddfba-d7b2-423e-a946-ac2bf36906fa', url='qemu+ssh://
> r...@prd-openshift-kvm03-poa.rbs.com.br/system ', username='root',
> originType='KVM'}), log id: eb750c7
> 2016-10-06 10:24:53,435 WARN
> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetVmsFromExternalProviderVDSCommand]
> (default task-97) [] Unexpected return value: StatusForXmlRpc [code=65,
> message=Cannot recv data: Permission denied, please try again.
> Permission denied, please try again.
> Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password).:
> Connection reset by peer]
> 2016-10-06 10:24:53,435 ERROR
> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetVmsFromExternalProviderVDSCommand]
> (default task-97) [] Failed in 'GetVmsFromExternalProviderVDS' method
> 2016-10-06 10:24:53,435 WARN
> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetVmsFromExternalProviderVDSCommand]
> (default task-97) [] Unexpected return value: StatusForXmlRpc [code=65,
> message=Cannot recv data: Permission denied, please try again.
> Permission denied, please try again.
> Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password).:
> Connection reset by peer]
> 2016-10-06 10:24:53,454 ERROR
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (default task-97) [] Correlation ID: null, Call Stack: null, Custom Event
> ID: -1, Message: VDSM hlg-rbs-ovirt-kvm01-poa.rbs.com.br command failed:
> Cannot recv data: Permission denied, please try again.
> Permission denied, please try again.
> Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password).:
> Connection reset by peer
> 2016-10-06 10:24:53,454 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetVmsFromExternalProviderVDSCommand]
> (default task-97) [] Command
> 'org.ovirt.engine.core.vdsbroker.vdsbroker.GetVmsFromExternalProviderVDSCommand'
> return value
> 'org.ovirt.engine.core.vdsbroker.vdsbroker.VMListReturnForXmlRpc@6c6f696c'
> 2016-10-06 10:24:53,454 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetVmsFromExternalProviderVDSCommand]
> (default task-97) [] HostName = hlg-rbs-ovirt-kvm01-poa.rbs.com.br
> 2016-10-06 10:24:53,454 ERROR
> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetVmsFromExternalProviderVDSCommand]
> (default task-97) [] Command 'GetVmsFromExternalProviderVDSCommand(HostName
> = hlg-rbs-ovirt-kvm01-poa.rbs.com.br ,
> GetVmsFromExternalProviderParameters:{runAsync='true',
> hostId='5feddfba-d7b2-423e-a946-ac2bf36906fa', url='qemu+ssh://
> r...@prd-openshift-kvm03-poa.rbs.com.br/system ', username='root',
> originType='KVM'})' execution failed: VDSGenericException:
> VDSErrorException: Failed to GetVmsFromExternalProviderVDS, error = Cannot
> recv data: Permission denied, please try again.
> Permission denied, please try again.
> Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password).:
> Connection reset by peer, code = 65
> 2016-10-06 10:24:53,454 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetVmsFromExternalProviderVDSCommand]
> (defaul

Re: [ovirt-users] Can't shut down VM

[Arik Hadas]

Hi,
There was some connectivity problem with the host that prevented you from
shutting down this VM.
What is the status of the host 80bb6fbe-6479-4642-835d-83f729e97fbb now (in
the webadmin it is shown as the host that the VM runs on)?

On Sun, Dec 25, 2016 at 11:21 AM, Peter Calum  wrote:

> Hi,
>
> I have a VM hanging in powering down state, the same VM has at snapshot
> hanging in state locked. - How do i solve this ?
>
> vmId='6d820a57-efef-431d-b98f-99e8fe13b6ac',
>
> oVirt Engine Version: 4.0.5.5-1.el7.centos
>
> engine log attached.
>
> --
> Venlig hilsen / Kind regards
>
> Peter Calum
>
>
> ___
> 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] Can't shut down VM

[Arik Hadas]

On Sun, Dec 25, 2016 at 12:14 PM, Peter Calum  wrote:

> Hi Arik
>
> Thank you for answering.
>
> The host for the VM with problems are running normally with 17 oter VM's.
>

So currently the host is up, 17 other VMs are running and this VM is stuck
in Powering Down?
Could you create a VM and try to run it on that host (at the Host tab in
the VM dialog select this host) and see if it get stuck in WaitForLaunch
state?


>
> thanks,
> Peter
>
>
> 2016-12-25 10:56 GMT+01:00 Arik Hadas :
>
>> Hi,
>> There was some connectivity problem with the host that prevented you from
>> shutting down this VM.
>> What is the status of the host 80bb6fbe-6479-4642-835d-83f729e97fbb now
>> (in the webadmin it is shown as the host that the VM runs on)?
>>
>> On Sun, Dec 25, 2016 at 11:21 AM, Peter Calum 
>> wrote:
>>
>>> Hi,
>>>
>>> I have a VM hanging in powering down state, the same VM has at snapshot
>>> hanging in state locked. - How do i solve this ?
>>>
>>> vmId='6d820a57-efef-431d-b98f-99e8fe13b6ac',
>>>
>>> oVirt Engine Version: 4.0.5.5-1.el7.centos
>>>
>>> engine log attached.
>>>
>>> --
>>> Venlig hilsen / Kind regards
>>>
>>> Peter Calum
>>>
>>>
>>> ___
>>> Users mailing list
>>> Users@ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/users
>>>
>>>
>>
>
>
> --
> Venlig hilsen / Kind regards
>
> Peter Calum
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Exporting VM as ova

[Arik Hadas]

Hi Benjamin,

Unfortunately not.
We intend to make more use of the OVA format soon, we design this these
days.
May I ask what is the motivation in your case to export the VM as OVA?

Regards,
Arik



On Fri, Feb 10, 2017 at 11:41 AM, Benjamin Alfery <
benjamin.alf...@linforge.com> wrote:

> Hi,
>
> I'm using ovirt 4.0 and was wondering if it is possible to export an
> existing VM to ova format (via the gui). If it's not possible via GUI,
> is that possible at all?
>
>
> Best Regards
> Benjamin
> ___
> 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] Exporting VM as ova

[Arik Hadas]

On Sun, Feb 12, 2017 at 2:37 PM, Anantha Raghava <
rag...@exzatechconsulting.com> wrote:

> Hello Arik,
>
> Converting to an appliance (OVA) makes the VM portable. Works on multiple
> hypervisor. VM migration and interoperability becomes uncomplicated.
>

Thanks Anantha.
That's true only to some extent.
For example, without converting OVA that was generated by VMware using
virt-v2v oVirt cannot consume it since the VMDK disks format is not
supported in oVirt. Another example is the OVF representation that differs
among various virtualization management platforms.
So if you are trying to migrate a VM from oVirt to another platform and
assume you'll get this out-of-the-box by having an OVA that is generated by
oVirt, I'm afraid you'll be disappointed in case the target platform
doesn't support the format of the disks or doesn't know how to parse the
OVF that is generated by oVirt.
And there may be more use cases for exporting the VM as OVA, that's why I'm
interested to know what's the goal in this case :)


> --
>
> Thanks & Regards,
>
>
> Anantha Raghava eXzaTech Consulting And Services Pvt. Ltd.
>
> Do not print this e-mail unless required. Save Paper & trees.
> On Sunday 12 February 2017 06:04 PM, Arik Hadas wrote:
>
> Hi Benjamin,
>
> Unfortunately not.
> We intend to make more use of the OVA format soon, we design this these
> days.
> May I ask what is the motivation in your case to export the VM as OVA?
>
> Regards,
> Arik
>
>
>
> On Fri, Feb 10, 2017 at 11:41 AM, Benjamin Alfery <
> benjamin.alf...@linforge.com> wrote:
>
>> Hi,
>>
>> I'm using ovirt 4.0 and was wondering if it is possible to export an
>> existing VM to ova format (via the gui). If it's not possible via GUI,
>> is that possible at all?
>>
>>
>> Best Regards
>> Benjamin
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>
>
>
> ___
> Users mailing listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users
>
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] ovirt 4.1.0 - sparsify ireversibly destroys preallocated disks

[Arik Hadas]

Hi Nelson,

We are going to disable the sparsify operation on pre-allocated disks, see
https://bugzilla.redhat.com/show_bug.cgi?id=1414430.

Regards,
Arik

בתאריך 13 בפבר׳ 2017 11:18 AM,‏ "Nelson Lameiras" <
nelson.lamei...@lyra-network.com> כתב:

> Hello,
>
> Not sure if it's a bug or a limitation but, while playing with oVirt 4.1
> new possibilities, I tried to use the sparsity function on a preallocated
> disk, and this action irreversibly ruined the data on the disk. I have
> repeated this experiment multiple times and always same result.
> (Sparsifying a thin provisioned disk works great though)
>
> I understand that the "sparsify" function is relevant to thin provision
> disks only. Still I think there should be a warning before doing this
> action on a preallocated disk? or maybe even forbid this action on a
> preallocated disk since sparsify has no meaning on a preallocated disk? (I
> maybe wrong...)
>
> thanks
>
> 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.payzen.eu
> ___
> 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] Disable guest agent not installed warning

[Arik Hadas]

On Thu, Feb 23, 2017 at 7:48 PM, Karli Sjöberg  wrote:

>
> Den 23 feb. 2017 6:10 em skrev Nir Soffer :
> >
> > On Thu, Feb 23, 2017 at 6:47 PM, Karli Sjöberg 
> wrote:
> > >
> > > Den 23 feb. 2017 4:09 em skrev Nir Soffer :
> > >>
> > >> On Thu, Feb 23, 2017 at 4:38 PM, Karli Sjöberg 
> > >> wrote:
> > >> > On Thu, 2017-02-23 at 13:46 +, Misak Khachatryan wrote:
> > >> >> Hi there. Anybody knows how to suppress guest agent not installed
> > >> >> warning for VM? I have one VM based on FreeBSD, where i can't
> install
> > >> >> it and the warning is just annoying.
> > >>
> > >> I learned today that HA does not work properly if guest agent is not
> > >> installed,
> > >> so you should be careful about the warning.
> > >>
> > >> Nir
> > >
> > > Uhm, what makes you say that exactly? I've been running oVirt since god
> > > knows how long now, faced countless of times where HA worked perfectly
> fine.
> > > If this is a new "feature", you have my sincerest thumbs down on that
> one:)
> >
> > If the vm is terminated on the host, we will treat that as normal
> termination
> > (e.g. poweroff within the vm), and will not start the vm on another host.
> >
> > You probably do not notice this since nobody is killing your vms.
> >
> > Nir
>
> So a 'kill -9' or qemu bug, huh? Good to know, but I consider it a small
> risk.
>
Note that what Nir was referring to [1,2] is not something new, is
unrelated to the original question (the warning shown when connecting using
a spice console to a VM with no guest agent has nothing to do with its
high-availability) and is indeed minor.

Back to the original question, I'm afraid there is no way to prevent this
warning today.

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1384007
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1418927

BTW Misak, you should be able to get the guest agent running in FreeBSD 11,
> since they added VirtIO serial now, haven't tried it myself, a bit
> preoccupied at the moment.
>
> /K
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] oVirt 4.1: clone option of importing from VMware

[Arik Hadas]

On Mon, Feb 27, 2017 at 3:48 PM, Gianluca Cecchi 
wrote:

> On Mon, Feb 27, 2017 at 2:40 PM, Yaniv Kaul wrote:
>
>>
>>
>> On Mon, Feb 27, 2017 at 3:36 PM Gianluca Cecchi wrote:
>>
>>> Hello,
>>> I'm doing some tests to import VMs from VMware and verify functionality.
>>> Great newcomer in 4.1
>>>
>>
>> It was added in 4.0, I believe.
>>
>
> Ah, ok. Never tried before from web admin gui.
> I confused in release notes of 4.1.0 with the feature:
> BZ 1294629 Improve loading external VMs speed
>
>
>
>>
>>
>>> And after about 20 minutes (the original VM has only one thin
>>> provisioned disk 4Gb/8Gb) the lock goes away and the status of the VM
>>> becomes down and in events pane I get only now the sequence:
>>>
>>
>>> Feb 27, 2017 2:20:42 PM Vm T-RHEL6-64 was imported successfully to Data
>>> Center Default, Cluster Default
>>>
>>
>> And this is the end of the task.
>>
>
> Yes, I mean that during the 20 minutes elapsed time, it results that no
> tasks are in execution.
> Is this correct because it is considered a sort of external task or is it
> a bug?
>
>
>
>>
>>
>>> It seems to me not so clear experience for the user importing,
>>> especially I imagine in case of more than one import and with big disks.
>>>
>>
>> I guess as always, we could try to improve with progress bar...
>>
>
> I didn't refer to it (see above), but for sure it could be a nice add-on
> feature to provide.
>

Actually there is a progress bar for the phase of disks copying (after the
'initialization' phase) in the 'status' column of the virtual machines tab.


>
> And what about the "clone" option? In what is it different from no
> selection of it?
>

That means that the VM will be imported as a cloned VM - have different mac
addresses, different identifiers for the disks, different identifier for
the VM.


>
> Thanks,
> 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 4.1: clone option of importing from VMware

[Arik Hadas]

On Mon, Feb 27, 2017 at 5:18 PM, Gianluca Cecchi 
wrote:

> On Mon, Feb 27, 2017 at 2:51 PM, Arik Hadas  wrote:
>
>>
>>>
>>> I didn't refer to it (see above), but for sure it could be a nice add-on
>>> feature to provide.
>>>
>>
>> Actually there is a progress bar for the phase of disks copying (after
>> the 'initialization' phase) in the 'status' column of the virtual machines
>> tab.
>>
>
> Ah, ok... I retried with another VM, monitoring this time the behavior and
> I see at  15:45 the message
>
> Starting to convert Vm T-RHEL5-64
>
> Then up to 16:04 it remains in "Initializing"
> Only at 16:04 it begins the copying phase, with a "qemu-img convert"
> command at host side that starts copying from an image in /var/tmp to the
> chosen storage domain with an elapsed of about 3 minutes and final
> completion
> Previously I missed the final minutes of the process, so that I noticed
> only the "Initializing" Status step and the final "Down" Status of the
> VM
>
>
>>
>>>
>>> And what about the "clone" option? In what is it different from no
>>> selection of it?
>>>
>>
>> That means that the VM will be imported as a cloned VM - have different
>> mac addresses, different identifiers for the disks, different identifier
>> for the VM.
>>
>>
>>>
>>>
> Ah, ok.
> This explains why I get this message while importing a VM without
> selecting "clone":
>
> VM T-RHEL7 has MAC address(es) 00:50:56:b0:0c:7d, which is/are out of its
> MAC pool definitions.
> ?
> In this case to assign an oVirt MAC between the setup ones, only way is to
> remove and add a new one or what?
>

After you imported the VM, yes.
During import, you can use the 'clone' option as you did before - it should
be fine as long as you're willing to have different identifiers (in most
cases, these identifiers have no functional implications).


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

Re: [ovirt-users] failed to migrate Vm

[Arik Hadas]

On Sat, Mar 4, 2017 at 8:42 PM, Bill James  wrote:

> I have a hardware node that for whatever reason most of the VM status was
> "?", even though VM was up and running fine.
>

This indicates that the engine failed to monitor the host (thus switching
VMs it knew that were running on it to the 'unknown' state).


> node was running ovirt 3.6 so I decided to upgrade it to 4.1.0.4-1 like
> most of the rest of the cluster is, including engine.
> After upgrade some VMs I'm able to start up fine on the upgraded hosts,
> other fail to start on that host and migrate themselves to another host.
> If I try to manually migrate them to the recently upgraded host migration
> fails. I have yet to find in the logs where it says why they fail.
> I am able to "runonce" the VM and tell it to start on this host and it
> starts fine.
> Why is migration failing?
>

> ovirt-engine-4.1.0.4-1.el7.centos.noarch
> vdsm-4.19.4-1.el7.centos.x86_64
>
>
> 2017-03-04 10:16:51,716-08 ERROR [org.ovirt.engine.core.dal.
> dbbroker.auditloghandling.AuditLogDirector] 
> (org.ovirt.thread.pool-7-thread-48)
> [519095c3-83ed-4478-8dd4-f432db6db140] EVENT_ID:
> VM_MIGRATION_TO_SERVER_FAILED(120), Correlation ID: 2
> 6d1ecba-8711-408d-b9d5-6461a4aab4e5, Job ID: 
> 546e0e11-9b4b-48d4-bd50-2f525d049ae2,
> Call Stack: null, Custom Event ID: -1, Message: Migration failed  (VM: 
> *j2es2.test.j2noc.com
> *, Source: ovirt6.test.j2noc.com,
> Destination: *ovirt4.test.j2noc.com *)
>
>
> (engine.log attached)
>

The engine log doesn't contain the reason.
Please file a bug (https://bugzilla.redhat.com) and attach VDSM logs from
the mentioned source and destination hosts that cover the time of the
migration attempt.


>
> Thanks.
>
>
> ___
> 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 importing VM

[Arik Hadas]

On Thu, Mar 2, 2017 at 10:48 AM, rightkicktech.gmail.com <
rightkickt...@gmail.com> wrote:

> Hi,
>
> I am using Virt4.1 on top glusterfs.
> I have defined two data domains, one for engine and one for vms. Also
> export and iso domains are on separate dedicated gluster volumes.
>
> When I try to import a VM from the export domain the VM is imported in the
> engine data domain. I would expect to be able to select on which data
> domain to import it. Am I missing sth?
>

Yeah, you missed the disks subtab at the import dialog :)
When pressing on one of the VMs to be imported subtabs appear and you can
configure the destination data domain per-disk (see the screenshot
attached).


>
> Thanx,
> Alex
>
> --
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
> ___
> 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] VMs imported from libvirt have no cdrom device

[Arik Hadas]

On Sun, Mar 5, 2017 at 1:17 PM, Chris Boot  wrote:

> Hi,
>
> I've imported a number of VMs that I previously was running under a
> self-hosted libvirt configuration. Most of the VMs at the source did not
> have a cdrom device (but some did) because I just added one as I needed to.
>
> Now that the VMs have been imported into oVirt, none of them have a
> cdrom device. Even booting with the "Attach CD" option doesn't create a
> cdrom device. I can't see any way to get oVirt to re-create the missing
> device.
>
> Is there a way for me to add these missing devices to my VMs?
>

Unfortunately there is no supported way of doing that. In oVirt, we add a
cd-rom device for every VM during its creation and don't enable to add or
remove a cd-rom. If no cd-rom device is added by default during import from
libvirt then that's a bug, could you please file a bug on that (
https://bugzilla.redhat.com) ?

However, you can resolve it in a hacky way by modifying the database
directly:

insert into vm_device (device_id, vm_id, type, device, is_managed,
is_plugged, is_readonly, address) values (uuid_generate_v1(), (select
vm_guid from vm_static where vm_name='your-vm-name'), 'disk', 'cdrom', 't',
't', 't', '');


>
> I'm running oVirt 4.1 on CentOS 7.3.1611 with a hosted engine setup. VMs
> were migrated from a Debian Stretch machine running libvirt 3.0.0 with
> qemu 2.8.0.
>
> Thanks,
> Chris
>
> --
> Chris Boot
> bo...@bootc.net
> ___
> 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] Any simple way of migrating KVM machines to oVirt instances

[Arik Hadas]

On Mon, Mar 20, 2017 at 9:15 AM, Yedidyah Bar David  wrote:

> On Mon, Mar 20, 2017 at 9:07 AM, John Joseph  wrote:
> > Hi All,
> > Thanks to the mailing list support and advice, now I have finished
> > installing oVirt 4.1, I have created few virtual machines and it is
> working
> > fine. Now I am thinking about migrating some virtual machines from
> > vmware/KVM to ovirt.
> > I am  checking the docs at
> >
> > http://www.ovirt.org/develop/release-management/features/
> virt/virt-v2v-integration/
> > for KVM to oVirt installation.
> >
> > Like to know is there any other simple way of migrating from KVM
> machines to
> > oVirt instance, it will be great if I can get a url for the how to do
>
> Searching for: site:ovirt.org kvm dd
> I found e.g.: http://lists.ovirt.org/pipermail/users/2014-June/058827.html


It sounds far more complicated than the integrated process in oVirt for
importing kvm virtual machines using libvirt.
John, can you please share why do you seek for an alternative way?


>
>
> Best,
>
> >
> > Advice and support requested
> > Thanks
> > Joseph John
> >
> > ___
> > 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
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Migration downtime

[Arik Hadas]

On Mon, Mar 20, 2017 at 12:28 PM, Arsène Gschwind  wrote:

> Hi,
>
> Since I've upgraded to 4.1 I don't have "actual downtime" after VM
> migration displayed, it displays N/A
>
>  Duration: 1 minute 59 seconds, Total: 1 minute 59 seconds, Actual
> downtime: (N/A) .
>
> So far I remember this value was available in 3.6, does anybody else have
> the same situation where this value is missing?
> I've investigate the logs but could just find the same information (N/A)
>
> Where is this value calculated / measured?
>

This is a regression in 4.1 that we are aware of [1] and working on.

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1427566

> Regards,
> Arsène
>
>
>
> --
>
> *Arsène Gschwind*
> Fa. Sapify AG im Auftrag der Universität Basel
> IT Services
> Klingelbergstr. 70 |  CH-4056 Basel  |  Switzerland
> Tel. +41 79 449 25 63 <+41%2079%20449%2025%2063>  |  http://its.unibas.ch
> ITS-ServiceDesk: support-...@unibas.ch | +41 61 267 14 11
> <+41%2061%20267%2014%2011>
>
> ___
> 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] Upload/download disks through muCommander

[Arik Hadas]

Hi all,

I want to share with you that a new version of muCommander has been
released and this version includes integration with oVirt!

A demo of the provided functionality is available at [1]:
First, we connect to RHV (but the following process would work the same for
oVirt) and browse the content if its storage domain. Then, we take two
virtual disk images, one of format=raw and size=3G and second of
format=qcow2 and size=2G, and upload them to that storage domain. In the
meantime, we download an iso file from the storage domain and explore its
content. We check the format and size for the uploaded disks. Lastly, we
remove the first disk from within muCommander and see that it also
disappears from the storage domain.

That can be seen as a front-end of oVirt's Image I/O [2].
However, please be aware of the following limitations:
1. Snapshots are not supported.
2. There is no way to specify the virtual size of the disk. This means it
works nicely for preallocated disks and for uploading iso files to data
domains (note the filename must end with the '.iso' extension), but
thin-provisioned disks would probably need to be extended after the upload.
3. oVirt-specific things like disk description, host to upload the disk to,
wipe-after-delete, and others cannot be specified.

This version of muCommander (v0.9.4-2) can be downloaded from [3].
Please feel free to to file issues for bugs or possible enhancements at [4]

Note that muCommander is not under the oVirt umbrella.

Feedback is welcome!

[1] https://youtu.be/F2u3cDGfEU0
[2]
https://www.ovirt.org/develop/release-management/features/storage/image-upload.html
[3] https://github.com/mucommander/mucommander/releases/tag/0.9.4-2
[4] https://github.com/mucommander/mucommander/issues

Thanks,
Arik
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/EQLYGPE3MUZQ7M32XWJ7FNLNYKRCHSGR/

[ovirt-users] Re: VM's in status unknown

[Arik Hadas]

I would start by querying the database with:
select vm_name, status, run_on_vds from vms where vm_name in ('', '');

Their status should be '7' in that case.
The more interesting part though is their 'run_on_vds' field -
If it's non-empty and points to the host the VMs ran on, it probably means
there's an issue in the communication between the engine and that host, so
restarting the engine/vdsm can solve it.
Otherwise, it would require a deeper look at the log to see why the engine
lost track of the host they run on.

On Fri, Apr 17, 2020 at 12:12 PM Staniforth, Paul <
p.stanifo...@leedsbeckett.ac.uk> wrote:

> I don't think the status is reported via the agent but vdsm on the host.
>
> Try restarting the engine service.
>
> use vdsm-client  on the host to see if the VM running and shut it down if
> needed.
>
> https://www.ovirt.org/develop/developer-guide/vdsm/vdsm-client.html
>
> on the host restart vdsmd ( you may want to migrate other VMs first)
>
> systemctl restart vdsmd
>
> If this doesn't work alter the database
>
> Regards,
> Paul S.
>
> --
> *From:* Jayme 
> *Sent:* 16 April 2020 19:07
> *To:* eev...@digitaldatatechs.com 
> *Cc:* kim.karga...@noroff.no ; users <
> users@ovirt.org>
> *Subject:* [ovirt-users] Re: VM's in status unknown
>
>
> *Caution External Mail:* Do not click any links or open any attachments
> unless you trust the sender and know that the content is safe.
> Do you have the guest agent installed on the VMs?
>
> On Thu, Apr 16, 2020 at 2:55 PM  wrote:
>
> Are you getting any errors in the engine log or
> /var/log/libvirt/qemu/.log?
> I have Windows 10 and haven't experienced that. You can't shut it down in
> the UI? Even after you try to shut it down inside Windows?
> I will assume you have the latest guest tools installed.
>
> Eric Evans
> Digital Data Services LLC.
> 304.660.9080
>
>
> -Original Message-
> From: kim.karga...@noroff.no 
> Sent: Thursday, April 16, 2020 8:23 AM
> To: users@ovirt.org
> Subject: [ovirt-users] VM's in status unknown
>
> Hi,
>
> We have a few Windows 10 VM's running on our ovirt 4.3, where when you
> shutdown the VM from within Windows, that VM does not shut down but gets a
> status of unknown in ovirt and one cannot do anything to the machines
> within the web gui. This seems to specfically be related to that Windows 10
> template that we have created. Any ideas? Also, any ideas on how one can
> shut these machines down?
>
> Thanks
>
> Kim
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org Privacy Statement:
> https://www.ovirt.org/privacy-policy.html
> 
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> 
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/UM26TABUTG373QVXEI4UJN3EAKANLWHL/
> 
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> 
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> 
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/messa

Re: [ovirt-users] Exporting/Copying VM to another oVirt server

[Arik Hadas]

בתאריך 28 בדצמ׳ 2017 10:38 PM,‏ "Alex Bartonek"  כתב:

After the success of getting my VM's working on my test server, I decided
to wipe out another server I had and wanted to move my VMs to it.   I tried
the "Export" as ova and it seems to work but in the Tasks its red:

"Exporting VM CentOS7 as an OVA to /ovirt_data/CentOS7.ova on Host
junkHost".

The .ova is never created.   Is there another way to do this?  Both servers
are running 4.2.

Googling hasnt helped me find a solution yet...


Can you please share engine.log?



___
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] Exporting/Copying VM to another oVirt server

[Arik Hadas]

On Thu, Dec 28, 2017 at 10:46 PM, Alex Bartonek  wrote:

> Log uploaded to:
>
> http://textuploader.com/dc2be
>
>
Thanks!
Exporting and importing as OVA files is the new shiny way of doing that as
from 4.2 but unfortunately, there seems to be an error while generating OVF
for the VM you're trying to export.
I see NullPointerException in the log and an empty line afterwards, can you
please check if there is a stacktrace right below in the engine.log that
was not copied? It should be below:
2017-12-28 14:45:03,728-06 ERROR
[org.ovirt.engine.core.bll.CreateOvaCommand]
(EE-ManagedThreadFactory-engineScheduled-Thread-22) [38896e98] Exception:
java.lang.NullPointerException


>
>
>
>  Original Message 
> Subject: Re: [ovirt-users] Exporting/Copying VM to another oVirt server
> Local Time: December 28, 2017 2:41 PM
> UTC Time: December 28, 2017 8:41 PM
> From: aha...@redhat.com
> To: Alex Bartonek 
> users 
>
>
>
> בתאריך 28 בדצמ׳ 2017 10:38 PM,‏ "Alex Bartonek"  כתב:
>
> After the success of getting my VM's working on my test server, I decided
> to wipe out another server I had and wanted to move my VMs to it.   I tried
> the "Export" as ova and it seems to work but in the Tasks its red:
>
> "Exporting VM CentOS7 as an OVA to /ovirt_data/CentOS7.ova on Host
> junkHost".
>
> The .ova is never created.   Is there another way to do this?  Both
> servers are running 4.2.
>
> Googling hasnt helped me find a solution yet...
>
>
> Can you please share engine.log?
>
>
>
> ___
> 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] Exporting/Copying VM to another oVirt server

[Arik Hadas]

On Thu, Dec 28, 2017 at 11:28 PM, Alex Bartonek  wrote:

> That is the excerpt from the  engine log file.   There isnt any  more java
> stack dump in it other than what I captured.
>

Can you please attach the entire engine.log to this thread or to a new bug (
https://bugzilla.redhat.com)?


>
>
> Sent with ProtonMail  Secure Email.
>
>  Original Message 
> Subject: Re: [ovirt-users] Exporting/Copying VM to another oVirt server
> Local Time: December 28, 2017 3:18 PM
> UTC Time: December 28, 2017 9:18 PM
> From: aha...@redhat.com
> To: Alex Bartonek 
> users 
>
>
>
> On Thu, Dec 28, 2017 at 10:46 PM, Alex Bartonek  wrote:
>
>> Log uploaded to:
>>
>> http://textuploader.com/dc2be
>>
>>
> Thanks!
> Exporting and importing as OVA files is the new shiny way of doing that as
> from 4.2 but unfortunately, there seems to be an error while generating OVF
> for the VM you're trying to export.
> I see NullPointerException in the log and an empty line afterwards, can
> you please check if there is a stacktrace right below in the engine.log
> that was not copied? It should be below:
> 2017-12-28 14:45:03,728-06 ERROR [org.ovirt.engine.core.bll.CreateOvaCommand]
> (EE-ManagedThreadFactory-engineScheduled-Thread-22) [38896e98] Exception:
> java.lang.NullPointerException
>
>
>>
>>
>>
>>
>>  Original Message 
>> Subject: Re: [ovirt-users] Exporting/Copying VM to another oVirt server
>> Local Time: December 28, 2017 2:41 PM
>> UTC Time: December 28, 2017 8:41 PM
>> From: aha...@redhat.com
>> To: Alex Bartonek 
>> users 
>>
>>
>>
>> בתאריך 28 בדצמ׳ 2017 10:38 PM,‏ "Alex Bartonek"  כתב:
>>
>> After the success of getting my VM's working on my test server, I decided
>> to wipe out another server I had and wanted to move my VMs to it.   I tried
>> the "Export" as ova and it seems to work but in the Tasks its red:
>>
>> "Exporting VM CentOS7 as an OVA to /ovirt_data/CentOS7.ova on Host
>> junkHost".
>>
>> The .ova is never created.   Is there another way to do this?  Both
>> servers are running 4.2.
>>
>> Googling hasnt helped me find a solution yet...
>>
>>
>> Can you please share engine.log?
>>
>>
>>
>> ___
>> 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] Exporting/Copying VM to another oVirt server

[Arik Hadas]

Thanks.
Is the description of the disk of the VM empty?
If it is, please type some description and then try again.

On Fri, Dec 29, 2017 at 12:02 AM, Alex Bartonek  wrote:

> Attached.  Its 3.8 mb decompressed.
>
>
> Sent with ProtonMail  Secure Email.
>
>  Original Message 
> Subject: Re: [ovirt-users] Exporting/Copying VM to another oVirt server
> Local Time: December 28, 2017 3:56 PM
> UTC Time: December 28, 2017 9:56 PM
> From: aha...@redhat.com
> To: Alex Bartonek 
> users 
>
>
>
> On Thu, Dec 28, 2017 at 11:28 PM, Alex Bartonek  wrote:
>
>> That is the excerpt from the  engine log file.   There isnt any  more
>> java stack dump in it other than what I captured.
>>
>
> Can you please attach the entire engine.log to this thread or to a new bug
> (https://bugzilla.redhat.com)?
>
>
>>
>>
>>
>> Sent with ProtonMail  Secure Email.
>>
>>  Original Message 
>> Subject: Re: [ovirt-users] Exporting/Copying VM to another oVirt server
>> Local Time: December 28, 2017 3:18 PM
>> UTC Time: December 28, 2017 9:18 PM
>> From: aha...@redhat.com
>> To: Alex Bartonek 
>> users 
>>
>>
>>
>> On Thu, Dec 28, 2017 at 10:46 PM, Alex Bartonek 
>> wrote:
>>
>>> Log uploaded to:
>>>
>>> http://textuploader.com/dc2be
>>>
>>>
>> Thanks!
>> Exporting and importing as OVA files is the new shiny way of doing that
>> as from 4.2 but unfortunately, there seems to be an error while generating
>> OVF for the VM you're trying to export.
>> I see NullPointerException in the log and an empty line afterwards, can
>> you please check if there is a stacktrace right below in the engine.log
>> that was not copied? It should be below:
>> 2017-12-28 14:45:03,728-06 ERROR [org.ovirt.engine.core.bll.CreateOvaCommand]
>> (EE-ManagedThreadFactory-engineScheduled-Thread-22) [38896e98]
>> Exception: java.lang.NullPointerException
>>
>>
>>>
>>>
>>>
>>>
>>>  Original Message 
>>> Subject: Re: [ovirt-users] Exporting/Copying VM to another oVirt server
>>> Local Time: December 28, 2017 2:41 PM
>>> UTC Time: December 28, 2017 8:41 PM
>>> From: aha...@redhat.com
>>> To: Alex Bartonek 
>>> users 
>>>
>>>
>>>
>>> בתאריך 28 בדצמ׳ 2017 10:38 PM,‏ "Alex Bartonek"  כתב:
>>>
>>> After the success of getting my VM's working on my test server, I
>>> decided to wipe out another server I had and wanted to move my VMs to it.
>>> I tried the "Export" as ova and it seems to work but in the Tasks its red:
>>>
>>> "Exporting VM CentOS7 as an OVA to /ovirt_data/CentOS7.ova on Host
>>> junkHost".
>>>
>>> The .ova is never created.   Is there another way to do this?  Both
>>> servers are running 4.2.
>>>
>>> Googling hasnt helped me find a solution yet...
>>>
>>>
>>> Can you please share engine.log?
>>>
>>>
>>>
>>> ___
>>> 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] Exporting/Copying VM to another oVirt server

[Arik Hadas]

:/
Can you please attach the new log?

On Fri, Dec 29, 2017 at 12:18 AM, Alex Bartonek  wrote:

> Yes it was empty.  Tried again, same failure.
>
>
> Sent with ProtonMail  Secure Email.
>
>  Original Message 
> Subject: Re: [ovirt-users] Exporting/Copying VM to another oVirt server
> Local Time: December 28, 2017 4:11 PM
> UTC Time: December 28, 2017 10:11 PM
> From: aha...@redhat.com
> To: Alex Bartonek 
> users 
>
> Thanks.
> Is the description of the disk of the VM empty?
> If it is, please type some description and then try again.
>
> On Fri, Dec 29, 2017 at 12:02 AM, Alex Bartonek  wrote:
>
>> Attached.  Its 3.8 mb decompressed.
>>
>>
>> Sent with ProtonMail  Secure Email.
>>
>>  Original Message 
>> Subject: Re: [ovirt-users] Exporting/Copying VM to another oVirt server
>> Local Time: December 28, 2017 3:56 PM
>> UTC Time: December 28, 2017 9:56 PM
>> From: aha...@redhat.com
>> To: Alex Bartonek 
>> users 
>>
>>
>>
>> On Thu, Dec 28, 2017 at 11:28 PM, Alex Bartonek 
>> wrote:
>>
>>> That is the excerpt from the  engine log file.   There isnt any  more
>>> java stack dump in it other than what I captured.
>>>
>>
>> Can you please attach the entire engine.log to this thread or to a new
>> bug (https://bugzilla.redhat.com)?
>>
>>
>>>
>>>
>>>
>>> Sent with ProtonMail  Secure Email.
>>>
>>>  Original Message 
>>> Subject: Re: [ovirt-users] Exporting/Copying VM to another oVirt server
>>> Local Time: December 28, 2017 3:18 PM
>>> UTC Time: December 28, 2017 9:18 PM
>>> From: aha...@redhat.com
>>> To: Alex Bartonek 
>>> users 
>>>
>>>
>>>
>>> On Thu, Dec 28, 2017 at 10:46 PM, Alex Bartonek 
>>> wrote:
>>>
 Log uploaded to:

 http://textuploader.com/dc2be


>>> Thanks!
>>> Exporting and importing as OVA files is the new shiny way of doing that
>>> as from 4.2 but unfortunately, there seems to be an error while generating
>>> OVF for the VM you're trying to export.
>>> I see NullPointerException in the log and an empty line afterwards, can
>>> you please check if there is a stacktrace right below in the engine.log
>>> that was not copied? It should be below:
>>> 2017-12-28 14:45:03,728-06 ERROR 
>>> [org.ovirt.engine.core.bll.CreateOvaCommand]
>>> (EE-ManagedThreadFactory-engineScheduled-Thread-22) [38896e98]
>>> Exception: java.lang.NullPointerException
>>>
>>>




  Original Message 
 Subject: Re: [ovirt-users] Exporting/Copying VM to another oVirt server
 Local Time: December 28, 2017 2:41 PM
 UTC Time: December 28, 2017 8:41 PM
 From: aha...@redhat.com
 To: Alex Bartonek 
 users 



 בתאריך 28 בדצמ׳ 2017 10:38 PM,‏ "Alex Bartonek" 
 כתב:

 After the success of getting my VM's working on my test server, I
 decided to wipe out another server I had and wanted to move my VMs to it.
 I tried the "Export" as ova and it seems to work but in the Tasks its red:

 "Exporting VM CentOS7 as an OVA to /ovirt_data/CentOS7.ova on Host
 junkHost".

 The .ova is never created.   Is there another way to do this?  Both
 servers are running 4.2.

 Googling hasnt helped me find a solution yet...


 Can you please share engine.log?



 ___
 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] Exporting/Copying VM to another oVirt server

[Arik Hadas]

That's weird that we don't get the stacktrace for that NPE, I wonder if we
encounter the problem that was discussed in this old thread: [1]
Could you restart the engine and try again, hoping that then we'll get the
stacktrace (it was shown previously in the engine,log and was related to
that empty disk description)

[1]
https://stackoverflow.com/questions/2411487/nullpointerexception-in-java-with-no-stacktrace

On Fri, Dec 29, 2017 at 12:25 AM, Alex Bartonek  wrote:

> 2017-12-28 16:14:59,452-06 INFO  
> [org.ovirt.engine.core.bll.tasks.SPMAsyncTask]
> (EE-ManagedThreadFactory-engine-Thread-15462) [10f0e6a5] 
> BaseAsyncTask::removeTaskFromDB:
> Removed task '3e1cfaa1-07a5-49cb-a9bc-8937c7cc75b2' from DataBase
> 2017-12-28 16:14:59,452-06 INFO  
> [org.ovirt.engine.core.bll.tasks.CommandAsyncTask]
> (EE-ManagedThreadFactory-engine-Thread-15462) [10f0e6a5]
> CommandAsyncTask::HandleEndActionResult [within thread]: Removing
> CommandMultiAsyncTasks object for entity '84686e92-7ca6-4228-9d3c-
> 31289b2d1d57'
> 2017-12-28 16:15:48,805-06 INFO  
> [org.ovirt.engine.core.bll.tasks.AsyncTaskManager]
> (EE-ManagedThreadFactory-engineScheduled-Thread-45) [] Setting new tasks
> map. The map contains now 1 tasks
> 2017-12-28 16:16:18,805-06 INFO  
> [org.ovirt.engine.core.bll.tasks.AsyncTaskManager]
> (EE-ManagedThreadFactory-engineScheduled-Thread-5) [] Setting new tasks
> map. The map contains now 0 tasks
> 2017-12-28 16:16:18,805-06 INFO  
> [org.ovirt.engine.core.bll.tasks.AsyncTaskManager]
> (EE-ManagedThreadFactory-engineScheduled-Thread-5) [] Cleared all tasks
> of pool '3bb4edf8-be27-42e4-b860-a1f1f293b81c'.
> 2017-12-28 16:21:17,538-06 INFO  
> [org.ovirt.engine.core.bll.utils.ThreadPoolMonitoringService]
> (EE-ManagedThreadFactory-engineThreadMonitoring-Thread-1) [] Thread pool
> 'default' is using 0 threads out of 1 and 5 tasks are waiting in the queue.
> 2017-12-28 16:21:17,538-06 INFO  
> [org.ovirt.engine.core.bll.utils.ThreadPoolMonitoringService]
> (EE-ManagedThreadFactory-engineThreadMonitoring-Thread-1) [] Thread pool
> 'engine' is using 0 threads out of 500, 8 threads waiting for tasks and 0
> tasks in queue.
> 2017-12-28 16:21:17,538-06 INFO  
> [org.ovirt.engine.core.bll.utils.ThreadPoolMonitoringService]
> (EE-ManagedThreadFactory-engineThreadMonitoring-Thread-1) [] Thread pool
> 'engineScheduled' is using 0 threads out of 100 and 100 tasks are waiting
> in the queue.
> 2017-12-28 16:21:17,538-06 INFO  
> [org.ovirt.engine.core.bll.utils.ThreadPoolMonitoringService]
> (EE-ManagedThreadFactory-engineThreadMonitoring-Thread-1) [] Thread pool
> 'engineThreadMonitoring' is using 1 threads out of 1 and 0 tasks are
> waiting in the queue.
> 2017-12-28 16:21:17,538-06 INFO  
> [org.ovirt.engine.core.bll.utils.ThreadPoolMonitoringService]
> (EE-ManagedThreadFactory-engineThreadMonitoring-Thread-1) [] Thread pool
> 'hostUpdatesChecker' is using 0 threads out of 5 and 2 tasks are waiting in
> the queue.
> 2017-12-28 16:21:28,068-06 INFO  
> [org.ovirt.engine.core.bll.exportimport.ExportOvaCommand]
> (default task-39) [aa503a62-d439-4131-9b46-e161779847f4] Lock Acquired to
> object 
> 'EngineLock:{exclusiveLocks='[43c82580-6c7a-4319-97f6-6cfb17a4445a=VM]',
> sharedLocks=''}'
> 2017-12-28 16:21:28,082-06 INFO  
> [org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor]
> (default task-39) [aa503a62-d439-4131-9b46-e161779847f4] Executing
> Ansible command:  [/usr/bin/ansible-playbook, 
> --private-key=/etc/pki/ovirt-engine/keys/engine_id_rsa,
> --inventory=/tmp/ansible-inventory8939720115375947799,
> --extra-vars=target_directory=/media/primary/extra_space,
> --extra-vars=validate_only=True, /usr/share/ovirt-engine/
> playbooks/ovirt-ova-export.yml] [Logfile: /var/log/ovirt-engine/ova/
> ovirt-export-ova-validate-ansible-20171228162128-reindeer.themagicm.com-
> aa503a62-d439-4131-9b46-e161779847f4.log]
> 2017-12-28 16:21:32,496-06 INFO  
> [org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor]
> (default task-39) [aa503a62-d439-4131-9b46-e161779847f4] Ansible playbook
> command has exited with value: 0
> 2017-12-28 16:21:32,548-06 INFO  
> [org.ovirt.engine.core.bll.exportimport.ExportOvaCommand]
> (EE-ManagedThreadFactory-engine-Thread-15515) 
> [aa503a62-d439-4131-9b46-e161779847f4]
> Running command: ExportOvaCommand internal: false. Entities affected :  ID:
> 43c82580-6c7a-4319-97f6-6cfb17a4445a Type: VMAction group
> IMPORT_EXPORT_VM with role type ADMIN
> 2017-12-28 16:21:32,584-06 INFO  
> [org.ovirt.engine.core.bll.storage.disk.CreateAllOvaDisksCommand]
> (EE-ManagedThreadFactory-engine-Thread-15515) 
> [aa503a62-d439-4131-9b46-e161779847f4]
> Running command: CreateAllOvaDisksCommand internal: true.
> 2017-12-28 16:21:32,645-06 INFO  [org.ovirt.engine.core.bll.
> storage.disk.image.CopyImageGroupCommand] 
> (EE-ManagedThreadFactory-engine-Thread-15515)
> [aa503a62-d439-4131-9b46-e161779847f4] Running command:
> CopyImageGroupCommand internal: true. Entities affected :  ID:
> 4108dd94-7538-

Re: [ovirt-users] Exporting/Copying VM to another oVirt server

[Arik Hadas]

Thanks.
It seems that it fails at the same place it failed before [1]. The only
reason for this failure is that the disk's description is empty.
Are you sure that you set a description for the right disk? Can you attach
a screenshot of the VM's disk info?

[1]
https://github.com/oVirt/ovirt-engine/blob/ovirt-engine-4.2.0/backend/manager/modules/utils/src/main/java/org/ovirt/engine/core/utils/ovf/OvfOvaWriter.java#L55

On Fri, Dec 29, 2017 at 12:45 AM, Alex Bartonek  wrote:

> shut down the engine, deleted engine.log, started up and attached entire
> log.  It does contain a java stack dump.
>
>
>  Original Message 
> Subject: Re: [ovirt-users] Exporting/Copying VM to another oVirt server
> Local Time: December 28, 2017 4:36 PM
> UTC Time: December 28, 2017 10:36 PM
> From: aha...@redhat.com
> To: Alex Bartonek 
> users 
>
> That's weird that we don't get the stacktrace for that NPE, I wonder if we
> encounter the problem that was discussed in this old thread: [1]
> Could you restart the engine and try again, hoping that then we'll get the
> stacktrace (it was shown previously in the engine,log and was related to
> that empty disk description)
>
> [1] https://stackoverflow.com/questions/2411487/
> nullpointerexception-in-java-with-no-stacktrace
>
> On Fri, Dec 29, 2017 at 12:25 AM, Alex Bartonek  wrote:
>
>> 2017-12-28 16:14:59,452-06 INFO  
>> [org.ovirt.engine.core.bll.tasks.SPMAsyncTask]
>> (EE-ManagedThreadFactory-engine-Thread-15462) [10f0e6a5]
>> BaseAsyncTask::removeTaskFromDB: Removed task
>> '3e1cfaa1-07a5-49cb-a9bc-8937c7cc75b2' from DataBase
>> 2017-12-28 16:14:59,452-06 INFO  
>> [org.ovirt.engine.core.bll.tasks.CommandAsyncTask]
>> (EE-ManagedThreadFactory-engine-Thread-15462) [10f0e6a5]
>> CommandAsyncTask::HandleEndActionResult [within thread]: Removing
>> CommandMultiAsyncTasks object for entity '84686e92-7ca6-4228-9d3c-31289
>> b2d1d57'
>> 2017-12-28 16:15:48,805-06 INFO  
>> [org.ovirt.engine.core.bll.tasks.AsyncTaskManager]
>> (EE-ManagedThreadFactory-engineScheduled-Thread-45) [] Setting new tasks
>> map. The map contains now 1 tasks
>> 2017-12-28 16:16:18,805-06 INFO  
>> [org.ovirt.engine.core.bll.tasks.AsyncTaskManager]
>> (EE-ManagedThreadFactory-engineScheduled-Thread-5) [] Setting new tasks
>> map. The map contains now 0 tasks
>> 2017-12-28 16:16:18,805-06 INFO  
>> [org.ovirt.engine.core.bll.tasks.AsyncTaskManager]
>> (EE-ManagedThreadFactory-engineScheduled-Thread-5) [] Cleared all tasks
>> of pool '3bb4edf8-be27-42e4-b860-a1f1f293b81c'.
>> 2017-12-28 16:21:17,538-06 INFO  [org.ovirt.engine.core.bll.uti
>> ls.ThreadPoolMonitoringService] 
>> (EE-ManagedThreadFactory-engineThreadMonitoring-Thread-1)
>> [] Thread pool 'default' is using 0 threads out of 1 and 5 tasks are
>> waiting in the queue.
>> 2017-12-28 16:21:17,538-06 INFO  [org.ovirt.engine.core.bll.uti
>> ls.ThreadPoolMonitoringService] 
>> (EE-ManagedThreadFactory-engineThreadMonitoring-Thread-1)
>> [] Thread pool 'engine' is using 0 threads out of 500, 8 threads waiting
>> for tasks and 0 tasks in queue.
>> 2017-12-28 16:21:17,538-06 INFO  [org.ovirt.engine.core.bll.uti
>> ls.ThreadPoolMonitoringService] 
>> (EE-ManagedThreadFactory-engineThreadMonitoring-Thread-1)
>> [] Thread pool 'engineScheduled' is using 0 threads out of 100 and 100
>> tasks are waiting in the queue.
>> 2017-12-28 16:21:17,538-06 INFO  [org.ovirt.engine.core.bll.uti
>> ls.ThreadPoolMonitoringService] 
>> (EE-ManagedThreadFactory-engineThreadMonitoring-Thread-1)
>> [] Thread pool 'engineThreadMonitoring' is using 1 threads out of 1 and 0
>> tasks are waiting in the queue.
>> 2017-12-28 16:21:17,538-06 INFO  [org.ovirt.engine.core.bll.uti
>> ls.ThreadPoolMonitoringService] 
>> (EE-ManagedThreadFactory-engineThreadMonitoring-Thread-1)
>> [] Thread pool 'hostUpdatesChecker' is using 0 threads out of 5 and 2 tasks
>> are waiting in the queue.
>> 2017-12-28 16:21:28,068-06 INFO  
>> [org.ovirt.engine.core.bll.exportimport.ExportOvaCommand]
>> (default task-39) [aa503a62-d439-4131-9b46-e161779847f4] Lock Acquired
>> to object 
>> 'EngineLock:{exclusiveLocks='[43c82580-6c7a-4319-97f6-6cfb17a4445a=VM]',
>> sharedLocks=''}'
>> 2017-12-28 16:21:28,082-06 INFO  
>> [org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor]
>> (default task-39) [aa503a62-d439-4131-9b46-e161779847f4] Executing
>> Ansible command:  [/usr/bin/ansible-playbook, 
>> --private-key=/etc/pki/ovirt-engine/keys/engine_id_rsa,
>> --inventory=/tmp/ansible-inventory8939720115375947799,
>> --extra-vars=target_directory=/media/primary/extra_space,
>> --extra-vars=validate_only=True, 
>> /usr/share/ovirt-engine/playbooks/ovirt-ova-export.yml]
>> [Logfile: /var/log/ovirt-engine/ova/ovirt-export-ova-validate-ansible-
>> 20171228162128-reindeer.themagicm.com-aa503a62-d439-
>> 4131-9b46-e161779847f4.log]
>> 2017-12-28 16:21:32,496-06 INFO  
>> [org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor]
>> (default task-39) [aa503a62-d439-4131-9b46-e161779847f4] Ansible
>> playbook

Re: [ovirt-users] Exporting/Copying VM to another oVirt server

[Arik Hadas]

Cool, glad to hear that it works now :)
Filed a bug about that NPE [1]

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1529607

On Fri, Dec 29, 2017 at 1:09 AM, Alex Bartonek  wrote:

> geez... yes, you were correct. I added the description to the VM not the
> *disk*.  :-/
> Sorry about that.  That took care of it.  Simple.  Very cool!!  Thank you
> very  much!
>
>
> Sent with ProtonMail  Secure Email.
>
>  Original Message 
> Subject: Re: [ovirt-users] Exporting/Copying VM to another oVirt server
> Local Time: December 28, 2017 4:57 PM
> UTC Time: December 28, 2017 10:57 PM
> From: aha...@redhat.com
> To: Alex Bartonek 
> users 
>
> Thanks.
> It seems that it fails at the same place it failed before [1]. The only
> reason for this failure is that the disk's description is empty.
> Are you sure that you set a description for the right disk? Can you attach
> a screenshot of the VM's disk info?
>
> [1] https://github.com/oVirt/ovirt-engine/blob/ovirt-
> engine-4.2.0/backend/manager/modules/utils/src/main/java/
> org/ovirt/engine/core/utils/ovf/OvfOvaWriter.java#L55
>
> On Fri, Dec 29, 2017 at 12:45 AM, Alex Bartonek  wrote:
>
>> shut down the engine, deleted engine.log, started up and attached entire
>> log.  It does contain a java stack dump.
>>
>>
>>  Original Message 
>> Subject: Re: [ovirt-users] Exporting/Copying VM to another oVirt server
>> Local Time: December 28, 2017 4:36 PM
>> UTC Time: December 28, 2017 10:36 PM
>> From: aha...@redhat.com
>> To: Alex Bartonek 
>> users 
>>
>> That's weird that we don't get the stacktrace for that NPE, I wonder if
>> we encounter the problem that was discussed in this old thread: [1]
>> Could you restart the engine and try again, hoping that then we'll get
>> the stacktrace (it was shown previously in the engine,log and was related
>> to that empty disk description)
>>
>> [1] https://stackoverflow.com/questions/2411487/nullpointere
>> xception-in-java-with-no-stacktrace
>>
>> On Fri, Dec 29, 2017 at 12:25 AM, Alex Bartonek 
>> wrote:
>>
>>> 2017-12-28 16:14:59,452-06 INFO  
>>> [org.ovirt.engine.core.bll.tasks.SPMAsyncTask]
>>> (EE-ManagedThreadFactory-engine-Thread-15462) [10f0e6a5]
>>> BaseAsyncTask::removeTaskFromDB: Removed task
>>> '3e1cfaa1-07a5-49cb-a9bc-8937c7cc75b2' from DataBase
>>> 2017-12-28 16:14:59,452-06 INFO  
>>> [org.ovirt.engine.core.bll.tasks.CommandAsyncTask]
>>> (EE-ManagedThreadFactory-engine-Thread-15462) [10f0e6a5]
>>> CommandAsyncTask::HandleEndActionResult [within thread]: Removing
>>> CommandMultiAsyncTasks object for entity '84686e92-7ca6-4228-9d3c-31289
>>> b2d1d57'
>>> 2017-12-28 16:15:48,805-06 INFO  
>>> [org.ovirt.engine.core.bll.tasks.AsyncTaskManager]
>>> (EE-ManagedThreadFactory-engineScheduled-Thread-45) [] Setting new
>>> tasks map. The map contains now 1 tasks
>>> 2017-12-28 16:16:18,805-06 INFO  
>>> [org.ovirt.engine.core.bll.tasks.AsyncTaskManager]
>>> (EE-ManagedThreadFactory-engineScheduled-Thread-5) [] Setting new tasks
>>> map. The map contains now 0 tasks
>>> 2017-12-28 16:16:18,805-06 INFO  
>>> [org.ovirt.engine.core.bll.tasks.AsyncTaskManager]
>>> (EE-ManagedThreadFactory-engineScheduled-Thread-5) [] Cleared all tasks
>>> of pool '3bb4edf8-be27-42e4-b860-a1f1f293b81c'.
>>> 2017-12-28 16:21:17,538-06 INFO  [org.ovirt.engine.core.bll.uti
>>> ls.ThreadPoolMonitoringService] 
>>> (EE-ManagedThreadFactory-engineThreadMonitoring-Thread-1)
>>> [] Thread pool 'default' is using 0 threads out of 1 and 5 tasks are
>>> waiting in the queue.
>>> 2017-12-28 16:21:17,538-06 INFO  [org.ovirt.engine.core.bll.uti
>>> ls.ThreadPoolMonitoringService] 
>>> (EE-ManagedThreadFactory-engineThreadMonitoring-Thread-1)
>>> [] Thread pool 'engine' is using 0 threads out of 500, 8 threads waiting
>>> for tasks and 0 tasks in queue.
>>> 2017-12-28 16:21:17,538-06 INFO  [org.ovirt.engine.core.bll.uti
>>> ls.ThreadPoolMonitoringService] 
>>> (EE-ManagedThreadFactory-engineThreadMonitoring-Thread-1)
>>> [] Thread pool 'engineScheduled' is using 0 threads out of 100 and 100
>>> tasks are waiting in the queue.
>>> 2017-12-28 16:21:17,538-06 INFO  [org.ovirt.engine.core.bll.uti
>>> ls.ThreadPoolMonitoringService] 
>>> (EE-ManagedThreadFactory-engineThreadMonitoring-Thread-1)
>>> [] Thread pool 'engineThreadMonitoring' is using 1 threads out of 1 and 0
>>> tasks are waiting in the queue.
>>> 2017-12-28 16:21:17,538-06 INFO  [org.ovirt.engine.core.bll.uti
>>> ls.ThreadPoolMonitoringService] 
>>> (EE-ManagedThreadFactory-engineThreadMonitoring-Thread-1)
>>> [] Thread pool 'hostUpdatesChecker' is using 0 threads out of 5 and 2 tasks
>>> are waiting in the queue.
>>> 2017-12-28 16:21:28,068-06 INFO  
>>> [org.ovirt.engine.core.bll.exportimport.ExportOvaCommand]
>>> (default task-39) [aa503a62-d439-4131-9b46-e161779847f4] Lock Acquired
>>> to object 
>>> 'EngineLock:{exclusiveLocks='[43c82580-6c7a-4319-97f6-6cfb17a4445a=VM]',
>>> sharedLocks=''}'
>>> 2017-12-28 16:21:28,082-06 INFO  
>>> [org.ovirt

Re: [ovirt-users] How to import OVA from oVirt 4.2 to oVirt 4.2

[Arik Hadas]

On Sat, Dec 30, 2017 at 1:26 AM, Alex Bartonek  wrote:

> I used clonezilla and built the VM that way.  If you get the OVA thing
> working, cool..  but in the meantime, here's how I did it using Clonezilla.
>

The bad news is that unfortunately, this OVA-import functionality is indeed
broken on 4.2.0.2.
The good news is that not only that the fix for this, along with other
OVA-related improvements, is already available on the master branch where
4.2.1 will be generated from but also that there is a workaround for
importing an OVA **that was generated by oVirt** which may even be more
efficient:
The alternative way requires using the SDK.
An example that demonstrates how to do this can be found at [1] - you just
need to replace the path to the ova (#43), the name of the target cluster
(#45), the connection details (#51-#57) and the name of the target storage
domain (#115).

So you'll need to install the SDK on one of the hosts that are part of the
source data center and then:
1. Export the VM as OVA through the webadmin/rest-api to a specific path on
that host.
2. Execute the example-script that takes the OVA from that path and uploads
it to the target data center.

Note that the SDK example-script uses the upload-disk operation.
This requires several configuration settings - I highly suggest to execute
the example of upload-disk [2] and only once that works for you to upload
the OVA(s).

[1]
https://github.com/oVirt/ovirt-engine-sdk/blob/master/sdk/examples/upload_ova_as_vm.py
[2]
https://github.com/oVirt/ovirt-engine-sdk/blob/master/sdk/examples/upload_disk.py



>
> https://www.unix1337.com/cloning-a-virtualbox-vm-to-ovirt-4-2/
>
>
>
> Sent with ProtonMail  Secure Email.
>
>  Original Message 
> Subject: How to import OVA from oVirt 4.2 to oVirt 4.2
> Local Time: December 28, 2017 8:03 PM
> UTC Time: December 29, 2017 2:03 AM
> From: a...@unix1337.com
> To: users 
>
> Followed instructions here:
> https://www.ovirt.org/develop/release-management/features/
> virt/virt-v2v-integration/
> Section: Importing OVA Files from VMware
> Even though its not VMWare, its an ova file so I followed the steps
> there.  Ownership of the file is 777, wide open.
>
> Error after clicking load: Failed to load VM configuration from OVA file:
> /media/primary/extra_space/CentOS7.ova
>
>
> Error in engine.log:
> 2017-12-28 20:03:04,910-06 INFO  
> [org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor]
> (default task-38) [b596efbd-dc55-4ce4-b3b8-5e8ffac6e633] Executing
> Ansible command:  [/usr/bin/ansible-playbook, 
> --private-key=/etc/pki/ovirt-engine/keys/engine_id_rsa,
> --inventory=/tmp/ansible-inventory4892490524555390378,
> --extra-vars=ovirt_query_ova_path=/media/primary/extra_space/CentOS7.ova,
> /usr/share/ovirt-engine/playbooks/ovirt-ova-query.yml] [Logfile: null]
> 2017-12-28 20:03:09,045-06 INFO  
> [org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor]
> (default task-38) [b596efbd-dc55-4ce4-b3b8-5e8ffac6e633] Ansible playbook
> command has exited with value: 0
> 2017-12-28 20:03:09,046-06 ERROR [org.ovirt.engine.core.bll.GetVmFromOvaQuery]
> (default task-38) [b596efbd-dc55-4ce4-b3b8-5e8ffac6e633] Query
> 'GetVmFromOvaQuery' failed: null
> 2017-12-28 20:03:09,046-06 ERROR [org.ovirt.engine.core.bll.GetVmFromOvaQuery]
> (default task-38) [b596efbd-dc55-4ce4-b3b8-5e8ffac6e633] Exception:
> java.lang.NullPointerException
> at 
> org.ovirt.engine.core.bll.GetVmFromOvaQuery.executeQueryCommand(GetVmFromOvaQuery.java:47)
> [bll.jar:]
> at 
> org.ovirt.engine.core.bll.QueriesCommandBase.executeCommand(QueriesCommandBase.java:106)
> [bll.jar:]
> at org.ovirt.engine.core.dal.VdcCommandBase.execute(VdcCommandBase.java:33)
> [dal.jar:]
> at org.ovirt.engine.core.bll.executor.DefaultBackendQueryExecutor.execute(
> DefaultBackendQueryExecutor.java:14) [bll.jar:]
> at org.ovirt.engine.core.bll.Backend.runQueryImpl(Backend.java:579)
> [bll.jar:]
> at org.ovirt.engine.core.bll.Backend.runQuery(Backend.java:548) [bll.jar:]
> at sun.reflect.GeneratedMethodAccessor100.invoke(Unknown Source)
> [:1.8.0_151]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_151]
> at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_151]
> at org.jboss.as.ee.component.ManagedReferenceMethodIntercep
> tor.processInvocation(ManagedReferenceMethodInterceptor.java:52)
> at org.jboss.invocation.InterceptorContext.proceed(
> InterceptorContext.java:422)
> at org.jboss.invocation.InterceptorContext$Invocation.
> proceed(InterceptorContext.java:509)
> at org.jboss.as.weld.ejb.DelegatingInterceptorInvocationContext.proceed(
> DelegatingInterceptorInvocationContext.java:92) [wildfly-weld-ejb-11.0.0.
> Final.jar:11.0.0.Final]
> at org.jboss.weld.interceptor.proxy.WeldInvocationContext.
> interceptorChainCompleted(WeldInvocationContext.java:98)
> [weld-core-impl-2.4.3.Final.jar:2.4.3.Final]
> at org.jboss.weld.interceptor.proxy.WeldInvocati

Re: [ovirt-users] oVirt 4.2 , VM stuck in "Migrating from" state.

[Arik Hadas]

Hi,

The problem you had is fixed already by https://gerrit.ovirt.org/#/c/86367/.
I'm afraid you'll need to manually set the VM to Down in the database:
update vm_dynamic set status=0 where vm_guid in  (select vm_guid from
vm_static where vm_name='')

On Tue, Feb 6, 2018 at 11:20 AM, Eduardo Mayoral  wrote:

> Hi,
>
> Got a problem with oVirt 4.2
>
> While putting a Host in maintenance mode, an VM has failed to migrate.
> The end state is that the Web UI shows the VM as "Migrating from".
>
> The VM is not running in any Host in the cluster.
>
> This is the relevant message in the /var/log/ovirt-engine/engine.log
>
> 2018-02-06 09:09:05,379Z INFO
> [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer]
> (EE-ManagedThreadFactory-engineScheduled-Thread-14) [] VM
> 'ab158ff3-a716-4655-9269-11738cd53b05'(repositorionuget) is running in
> db and not running on VDS
> '82b49615-9c65-4d8e-80e0-f10089cb4225'(llkh456.arsyslan.es)
> 2018-02-06 09:09:05,381Z ERROR
> [org.ovirt.engine.core.vdsbroker.monitoring.VmsMonitoring]
> (EE-ManagedThreadFactory-engineScheduled-Thread-14) [] Failed during
> monitoring vm: ab158ff3-a716-4655-9269-11738cd53b05 , error is: {}:
> java.lang.NullPointerException
> at
> org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer.
> auditVmMigrationAbort(VmAnalyzer.java:440)
> [vdsbroker.jar:]
> at
> org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer.abortVmMigration(
> VmAnalyzer.java:432)
> [vdsbroker.jar:]
> at
> org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer.
> proceedDisappearedVm(VmAnalyzer.java:794)
> [vdsbroker.jar:]
> at
> org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer.analyze(VmAnalyzer.
> java:135)
> [vdsbroker.jar:]
> at
> org.ovirt.engine.core.vdsbroker.monitoring.VmsMonitoring.lambda$
> analyzeVms$1(VmsMonitoring.java:136)
> [vdsbroker.jar:]
> at java.util.ArrayList.forEach(ArrayList.java:1255)
> [rt.jar:1.8.0_151]
> at
> org.ovirt.engine.core.vdsbroker.monitoring.VmsMonitoring.analyzeVms(
> VmsMonitoring.java:131)
> [vdsbroker.jar:]
> at
> org.ovirt.engine.core.vdsbroker.monitoring.VmsMonitoring.perform(
> VmsMonitoring.java:94)
> [vdsbroker.jar:]
> at
> org.ovirt.engine.core.vdsbroker.monitoring.PollVmStatsRefresher.poll(
> PollVmStatsRefresher.java:43)
> [vdsbroker.jar:]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> [rt.jar:1.8.0_151]
> at
> java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> [rt.jar:1.8.0_151]
> at
> org.glassfish.enterprise.concurrent.internal.
> ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.access$201(
> ManagedScheduledThreadPoolExecutor.java:383)
> [javax.enterprise.concurrent-1.0.jar:]
> at
> org.glassfish.enterprise.concurrent.internal.
> ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.run(
> ManagedScheduledThreadPoolExecutor.java:534)
> [javax.enterprise.concurrent-1.0.jar:]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(
> ThreadPoolExecutor.java:1149)
> [rt.jar:1.8.0_151]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(
> ThreadPoolExecutor.java:624)
> [rt.jar:1.8.0_151]
> at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_151]
> at
> org.glassfish.enterprise.concurrent.ManagedThreadFactoryImpl$
> ManagedThread.run(ManagedThreadFactoryImpl.java:250)
> [javax.enterprise.concurrent-1.0.jar:]
> at
> org.jboss.as.ee.concurrent.service.ElytronManagedThreadFactory$
> ElytronManagedThread.run(ElytronManagedThreadFactory.java:78)
>
> 2018-02-06 09:09:05,381Z ERROR
> [org.ovirt.engine.core.vdsbroker.monitoring.VmsMonitoring]
> (EE-ManagedThreadFactory-engineScheduled-Thread-14) [] Exception::
> java.lang.NullPointerException
> at
> org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer.
> auditVmMigrationAbort(VmAnalyzer.java:440)
> [vdsbroker.jar:]
> at
> org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer.abortVmMigration(
> VmAnalyzer.java:432)
> [vdsbroker.jar:]
> at
> org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer.
> proceedDisappearedVm(VmAnalyzer.java:794)
> [vdsbroker.jar:]
> at
> org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer.analyze(VmAnalyzer.
> java:135)
> [vdsbroker.jar:]
> at
> org.ovirt.engine.core.vdsbroker.monitoring.VmsMonitoring.lambda$
> analyzeVms$1(VmsMonitoring.java:136)
> [vdsbroker.jar:]
> at java.util.ArrayList.forEach(ArrayList.java:1255)
> [rt.jar:1.8.0_151]
> at
> org.ovirt.engine.core.vdsbroker.monitoring.VmsMonitoring.analyzeVms(
> VmsMonitoring.java:131)
> [vdsbroker.jar:]
> at
> org.ovirt.engine.core.vdsbroker.monitoring.VmsMonitoring.perform(
> VmsMonitoring.java:94)
> [vdsbroker.jar:]
> at
> org.ovirt.engine.core.vdsbroker.monitoring.PollVmStatsRefresher.poll(
> PollVmStatsRefresher.java:43)
> [vdsbroker.jar:]
> at
> java.util.concurrent.Executors$RunnableAdapter.ca

Re: [ovirt-users] problem importing ova vm

[Arik Hadas]

On Tue, Feb 20, 2018 at 2:03 PM, Jiří Sléžka  wrote:

> Hi,
>

Hi Jiří,


>
> I would like to try import some ova files into our oVirt instance [1]
> [2] but I facing problems.
>
> I have downloaded all ova images into one of hosts (ovirt01) into
> direcory /ova
>
> ll /ova/
> total 6532872
> -rw-r--r--. 1 vdsm kvm 1160387072 Feb 16 16:21 HAAS-hpcowrie.ovf
> -rw-r--r--. 1 vdsm kvm 785984 Feb 16 16:22 HAAS-hpdio.ova
> -rw-r--r--. 1 vdsm kvm  846736896 Feb 16 16:22 HAAS-hpjdwpd.ova
> -rw-r--r--. 1 vdsm kvm  891043328 Feb 16 16:23 HAAS-hptelnetd.ova
> -rw-r--r--. 1 vdsm kvm  908222464 Feb 16 16:23 HAAS-hpuchotcp.ova
> -rw-r--r--. 1 vdsm kvm  880643072 Feb 16 16:24 HAAS-hpuchoudp.ova
> -rw-r--r--. 1 vdsm kvm  890833920 Feb 16 16:24 HAAS-hpuchoweb.ova
>
> Then I tried to import them - from host ovirt01 and directory /ova but
> spinner spins infinitly and nothing is happen.
>

And does it work when you provide a path to the actual ova file, i.e.,
/ova/HAAS-hpdio.ova, rather than to the directory?


>
> I cannot see anything relevant in vdsm log of host ovirt01.
>
> In the engine.log of our standalone ovirt manager is just this relevant
> line
>
> 2018-02-20 12:35:04,289+01 INFO
> [org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor] (default
> task-31) [458990a7-b054-491a-904e-5c4fe44892c4] Executing Ansible
> command: ANSIBLE_STDOUT_CALLBACK=ovaqueryplugin
> [/usr/bin/ansible-playbook,
> --private-key=/etc/pki/ovirt-engine/keys/engine_id_rsa,
> --inventory=/tmp/ansible-inventory8237874608161160784,
> --extra-vars=ovirt_query_ova_path=/ova,
> /usr/share/ovirt-engine/playbooks/ovirt-ova-query.yml] [Logfile:
> /var/log/ovirt-engine/ova/ovirt-query-ova-ansible-
> 20180220123504-ovirt01.net.slu.cz.log]
>
> also there are two ansible processes which are still running (and makes
> heavy load on system (load 9+ and growing, it looks like it eats all the
> memory and system starts swapping))
>
> ovirt32087  3.3  0.0 332252  5980 ?Sl   12:35   0:41
> /usr/bin/python2 /usr/bin/ansible-playbook
> --private-key=/etc/pki/ovirt-engine/keys/engine_id_rsa
> --inventory=/tmp/ansible-inventory8237874608161160784
> --extra-vars=ovirt_query_ova_path=/ova
> /usr/share/ovirt-engine/playbooks/ovirt-ova-query.yml
> ovirt32099 57.5 78.9 15972880 11215312 ?   R12:35  11:52
> /usr/bin/python2 /usr/bin/ansible-playbook
> --private-key=/etc/pki/ovirt-engine/keys/engine_id_rsa
> --inventory=/tmp/ansible-inventory8237874608161160784
> --extra-vars=ovirt_query_ova_path=/ova
> /usr/share/ovirt-engine/playbooks/ovirt-ova-query.yml
>
> playbook looks like
>
> - hosts: all
>   remote_user: root
>   gather_facts: no
>
>   roles:
> - ovirt-ova-query
>
> and it looks like it only runs query_ova.py but on all hosts?
>

No, the engine provides ansible the host to run on when it executes the
playbook.
It would only be executed on the selected host.


>
> How does this work? ...or should it work?
>

It should, especially that part of querying the OVA and is supposed to be
really quick.
Can you please share the engine log and /var/log/ovirt-engine/ova/
ovirt-query-ova-ansible-20180220123504-ovirt01.net.slu.cz.log ?


>
> I am using latest 4.2.1.7-1.el7.centos version
>
> Cheers,
> Jiri Slezka
>
>
> [1] https://haas.cesnet.cz/#!index.md - Cesnet HAAS
> [2] https://haas.cesnet.cz/downloads/release-01/ - Image repository
>
>
> ___
> 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] problem importing ova vm

[Arik Hadas]

On Tue, Feb 20, 2018 at 3:49 PM, Jiří Sléžka  wrote:

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


Note that the logic that is applied on a specified folder is "try fetching
an 'ova folder' out of the destination folder" rather than "list all the
ova files inside the specified folder". It seems that you expected the
former output since there are no disks in that folder, right?


>
> > I cannot see anything relevant in vdsm log of host ovirt01.
> >
> > In the engine.log of our standalone ovirt manager is just this
> > relevant line
> >
> > 2018-02-20 12:35:04,289+01 INFO
> > [org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor]
> (default
> > task-31) [458990a7-b054-491a-904e-5c4fe44892c4] Executing Ansible
> > command: ANSIBLE_STDOUT_CALLBACK=ovaqueryplugin
> > [/usr/bin/ansible-playbook,
> > --private-key=/etc/pki/ovirt-engine/keys/engine_id_rsa,
> > --inventory=/tmp/ansible-inventory8237874608161160784,
> > --extra-vars=ovirt_query_ova_path=/ova,
> > /usr/share/ovirt-engine/playbooks/ovirt-ova-query.yml] [Logfile:
> > /var/log/ovirt-engine/ova/ovirt-query-ova-ansible-
> 20180220123504-ovirt01.net
> > <http://20180220123504-ovirt01.net>.slu.cz.log]
> >
> > also there are two ansible processes which are still running (and
> makes
> > heavy load on system (load 9+ and growing, it looks like it eats all
> the
> > memory and system starts swapping))
> >
> > ovirt32087  3.3  0.0 332252  5980 ?Sl   12:35   0:41
> > /usr/bin/python2 /usr/bin/ansible-playbook
> > --private-key=/etc/pki/ovirt-engine/keys/engine_id_rsa
> > --inventory=/tmp/ansible-inventory8237874608161160784
> > --extra-vars=ovirt_query_ova_path=/ova
> > /usr/share/ovirt-engine/playbooks/ovirt-ova-query.yml
> > ovirt32099 57.5 78.9 15972880 11215312 ?   R12:35  11:52
> > /usr/bin/python2 /usr/bin/ansible-playbook
> > --private-key=/etc/pki/ovirt-engine/keys/engine_id_rsa
> > --inventory=/tmp/ansible-inventory8237874608161160784
> > --extra-vars=ovirt_query_ova_path=/ova
> > /usr/share/ovirt-engine/playbooks/ovirt-ova-query.yml
> >
> > playbook looks like
> >
> > - hosts: all
> >   remote_user: root
> >   gather_facts: no
> >
> >   roles:
> > - ovirt-ova-query
> >
> > and it looks like it only runs query_ova.py but on all hosts?
> >
> >
> > No, the engine provides ansible the host to run on when it executes the
> > playbook.
> > It would only be executed on the selected host.
> >
> >
> >
> > How does this work? ...or should it work?
> >
> >
> > It should, especially that part of querying the OVA and is supposed to
> > be really quick.
> > Can you please share the engine log and
> > /var/log/ovirt-engine/ova/ovirt-query-ova-ansible-
> 20180220123504-ovirt01.net
> > <http://20180220123504-ovirt01.net>.slu.cz.log ?
>
> engine log is here:
>
> https://pastebin.com/nWWM3UUq


Thanks.
Alright, so now the configuration is fetched bu

Re: [ovirt-users] problem importing ova vm

[Arik Hadas]

On Tue, Feb 20, 2018 at 6:37 PM, Jiří Sléžka  wrote:

> On 02/20/2018 03:48 PM, Arik Hadas wrote:
> >
> >
> > On Tue, Feb 20, 2018 at 3:49 PM, Jiří Sléžka  > <mailto:jiri.sle...@slu.cz>> wrote:
> >
> > Hi Arik,
> >
> > On 02/20/2018 01:22 PM, Arik Hadas wrote:
> > >
> > >
> > > On Tue, Feb 20, 2018 at 2:03 PM, Jiří Sléžka  <mailto:jiri.sle...@slu.cz>
> > > <mailto:jiri.sle...@slu.cz <mailto:jiri.sle...@slu.cz>>> wrote:
> > >
> > > Hi,
> > >
> > >
> > > Hi Jiří,
> > >
> > >
> > >
> > > I would like to try import some ova files into our oVirt
> instance [1]
> > > [2] but I facing problems.
> > >
> > > I have downloaded all ova images into one of hosts (ovirt01)
> into
> > > direcory /ova
> > >
> > > ll /ova/
> > > total 6532872
> > > -rw-r--r--. 1 vdsm kvm 1160387072 Feb 16 16:21
> HAAS-hpcowrie.ovf
> > > -rw-r--r--. 1 vdsm kvm 785984 Feb 16 16:22 HAAS-hpdio.ova
> > > -rw-r--r--. 1 vdsm kvm  846736896 Feb 16 16:22 HAAS-hpjdwpd.ova
> > > -rw-r--r--. 1 vdsm kvm  891043328 Feb 16 16:23
> HAAS-hptelnetd.ova
> > > -rw-r--r--. 1 vdsm kvm  908222464 Feb 16 16:23
> HAAS-hpuchotcp.ova
> > > -rw-r--r--. 1 vdsm kvm  880643072 Feb 16 16:24
> HAAS-hpuchoudp.ova
> > > -rw-r--r--. 1 vdsm kvm  890833920 Feb 16 16:24
> HAAS-hpuchoweb.ova
> > >
> > > Then I tried to import them - from host ovirt01 and directory
> /ova but
> > > spinner spins infinitly and nothing is happen.
> > >
> > >
> > > And does it work when you provide a path to the actual ova file,
> i.e.,
> > > /ova/HAAS-hpdio.ova, rather than to the directory?
> >
> > this time it ends with "Failed to load VM configuration from OVA
> file:
> > /ova/HAAS-hpdio.ova" error.
> >
> >
> > Note that the logic that is applied on a specified folder is "try
> > fetching an 'ova folder' out of the destination folder" rather than
> > "list all the ova files inside the specified folder". It seems that you
> > expected the former output since there are no disks in that folder,
> right?
>
> yes, It would be more user friendly to list all ova files and then
> select which one to import (like listing all vms in vmware import)
>
> Maybe description of path field in manager should be "Path to ova file"
> instead of "Path" :-)
>

Sorry, I obviously meant 'latter' rather than 'former' before..
Yeah, I agree that would be better, at least until listing the OVA files in
the folder is implemented (that was the original plan, btw) - could you
please file a bug?


>
> > > I cannot see anything relevant in vdsm log of host ovirt01.
> > >
> > > In the engine.log of our standalone ovirt manager is just this
> > > relevant line
> > >
> > > 2018-02-20 12:35:04,289+01 INFO
> > > [org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor]
> (default
> > > task-31) [458990a7-b054-491a-904e-5c4fe44892c4] Executing
> Ansible
> > > command: ANSIBLE_STDOUT_CALLBACK=ovaqueryplugin
> > > [/usr/bin/ansible-playbook,
> > > --private-key=/etc/pki/ovirt-engine/keys/engine_id_rsa,
> > > --inventory=/tmp/ansible-inventory8237874608161160784,
> > > --extra-vars=ovirt_query_ova_path=/ova,
> > > /usr/share/ovirt-engine/playbooks/ovirt-ova-query.yml]
> [Logfile:
> > > /var/log/ovirt-engine/ova/ovirt-query-ova-ansible-
> 20180220123504-ovirt01.net
> > <http://ovirt-query-ova-ansible-20180220123504-ovirt01.net>
> > > <http://20180220123504-ovirt01.net
> > <http://20180220123504-ovirt01.net>>.slu.cz.log]
> > >
> > > also there are two ansible processes which are still running
> > (and makes
> > > heavy load on system (load 9+ and growing, it looks like it
> > eats all the
> > > memory and system starts swapping))
> > >
> > > ovirt32087  3.3  0.0 332252  5980 ?Sl   12:35
>  0:41
> > > /usr/bin/python2 /usr/bin/ansible-playbook
> > > --private-key=/etc/pki/ovirt-engine/ke

Re: [ovirt-users] problem importing ova vm

[Arik Hadas]

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

> On 02/21/2018 03:43 PM, Jiří Sléžka wrote:
> > On 02/20/2018 11:09 PM, Arik Hadas wrote:
> >>
> >>
> >> On Tue, Feb 20, 2018 at 6:37 PM, Jiří Sléžka  >> <mailto:jiri.sle...@slu.cz>> wrote:
> >>
> >> On 02/20/2018 03:48 PM, Arik Hadas wrote:
> >> >
> >> >
> >> > On Tue, Feb 20, 2018 at 3:49 PM, Jiří Sléžka  <mailto:jiri.sle...@slu.cz>
> >> > <mailto:jiri.sle...@slu.cz <mailto:jiri.sle...@slu.cz>>> wrote:
> >> >
> >> > Hi Arik,
> >> >
> >> > On 02/20/2018 01:22 PM, Arik Hadas wrote:
> >> > >
> >> > >
> >> > > On Tue, Feb 20, 2018 at 2:03 PM, Jiří Sléžka <
> jiri.sle...@slu.cz <mailto:jiri.sle...@slu.cz>
> >> <mailto:jiri.sle...@slu.cz <mailto:jiri.sle...@slu.cz>>
> >> > > <mailto:jiri.sle...@slu.cz <mailto:jiri.sle...@slu.cz>
> >> <mailto:jiri.sle...@slu.cz <mailto:jiri.sle...@slu.cz>>>> wrote:
> >> > >
> >> > > Hi,
> >> > >
> >> > >
> >> > > Hi Jiří,
> >> > >
> >> > >
> >> > >
> >> > > I would like to try import some ova files into our oVirt
> >> instance [1]
> >> > > [2] but I facing problems.
> >> > >
> >> > > I have downloaded all ova images into one of hosts
> >> (ovirt01) into
> >> > > direcory /ova
> >> > >
> >> > > ll /ova/
> >> > > total 6532872
> >> > > -rw-r--r--. 1 vdsm kvm 1160387072 Feb 16 16:21
> >> HAAS-hpcowrie.ovf
> >> > > -rw-r--r--. 1 vdsm kvm 785984 Feb 16 16:22
> >> HAAS-hpdio.ova
> >> > > -rw-r--r--. 1 vdsm kvm  846736896 Feb 16 16:22
> >> HAAS-hpjdwpd.ova
> >> > > -rw-r--r--. 1 vdsm kvm  891043328 Feb 16 16:23
> >> HAAS-hptelnetd.ova
> >> > > -rw-r--r--. 1 vdsm kvm  908222464 Feb 16 16:23
> >> HAAS-hpuchotcp.ova
> >> > > -rw-r--r--. 1 vdsm kvm  880643072 Feb 16 16:24
> >> HAAS-hpuchoudp.ova
> >> > > -rw-r--r--. 1 vdsm kvm  890833920 Feb 16 16:24
> >> HAAS-hpuchoweb.ova
> >> > >
> >> > > Then I tried to import them - from host ovirt01 and
> >> directory /ova but
> >> > > spinner spins infinitly and nothing is happen.
> >> > >
> >> > >
> >> > > And does it work when you provide a path to the actual ova
> >> file, i.e.,
> >> > > /ova/HAAS-hpdio.ova, rather than to the directory?
> >> >
> >> > this time it ends with "Failed to load VM configuration from
> >> OVA file:
> >> > /ova/HAAS-hpdio.ova" error.
> >> >
> >> >
> >> > Note that the logic that is applied on a specified folder is "try
> >> > fetching an 'ova folder' out of the destination folder" rather
> than
> >> > "list all the ova files inside the specified folder". It seems
> >> that you
> >> > expected the former output since there are no disks in that
> >> folder, right?
> >>
> >> yes, It would be more user friendly to list all ova files and then
> >> select which one to import (like listing all vms in vmware import)
> >>
> >> Maybe description of path field in manager should be "Path to ova
> file"
> >> instead of "Path" :-)
> >>
> >>
> >> Sorry, I obviously meant 'latter' rather than 'former' before..
> >> Yeah, I agree that would be better, at least until listing the OVA files
> >> in the folder is implemented (that was the original plan, btw) - could
> >> you please file a bug?
> >
> > yes, sure
> >
> >
> >> > > I cannot see anything relevant in vdsm log of host
> ovirt01.
> >> > >
> >> > &

Re: [ovirt-users] problem importing ova vm

[Arik Hadas]

So I have some good news and some bad news.

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

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



  0

  usb

  USB Controller

  usb

  6

  23



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

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


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


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

installed, try installing a fullvirt kernel (only for

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

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


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

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

> On 02/21/2018 05:35 PM, Arik Hadas wrote:
> >
> >
> > On Wed, Feb 21, 2018 at 6:03 PM, Jiří Sléžka  > <mailto:jiri.sle...@slu.cz>> wrote:
> >
> >     On 02/21/2018 03:43 PM, Jiří Sléžka wrote:
> > > On 02/20/2018 11:09 PM, Arik Hadas wrote:
> > >>
> > >>
> > >> On Tue, Feb 20, 2018 at 6:37 PM, Jiří Sléžka  > <mailto:jiri.sle...@slu.cz>
> > >> <mailto:jiri.sle...@slu.cz <mailto:jiri.sle...@slu.cz>>> wrote:
> > >>
> > >> On 02/20/2018 03:48 PM, Arik Hadas wrote:
> > >> >
> > >> >
> > >> > On Tue, Feb 20, 2018 at 3:49 PM, Jiří Sléžka
> > mailto:jiri.sle...@slu.cz>
> > <mailto:jiri.sle...@slu.cz <mailto:jiri.sle...@slu.cz>>
> > >> > <mailto:jiri.sle...@slu.cz <mailto:jiri.sle...@slu.cz>
> > <mailto:jiri.sle...@slu.cz <mailto:jiri.sle...@slu.cz>>>> wrote:
> > >> >
> > >> > Hi Arik,
> > >> >
> > >> > On 02/20/2018 01:22 PM, Arik Hadas wrote:
> > >> > >
> > >> > >
> > >> > > On Tue, Feb 20, 2018 at 2:03 PM, Jiří Sléžka
> > mailto:jiri.sle...@slu.cz>
> > <mailto:jiri.sle...@slu.cz <mailto:jiri.sle...@slu.cz>>
> > >> <mailto:jiri.sle...@slu.cz <mailto:jiri.sle...@slu.cz>
> > <mailto:jiri.sle...@slu.cz <mailto:jiri.sle...@slu.cz>>>
> > >> > > <mailto:jiri.sle...@slu.cz
> > <mailto:jiri.sle...@slu.cz> <mailto:jiri.sle...@slu.cz
> > <mailto:jiri.sle...@slu.cz>>
> > >> <mailto:jiri.sle...@slu.cz <mailto:jiri.sle...@slu.cz>
> > <mailto:jiri.sle...@slu.cz <mailto:jiri.sle...@slu.cz>>>>> wrote:
> > >> > >
> > >> > > Hi,
> > >> > >
> > >> > >
> > >> > > Hi Jiří,
> > >> > >
> > >> > >
> > >> > >
> > >> > > I would like to try import some ova files into
> > our oVirt
> > >> instance [1]
> > >> > > [2] but I facing problems.
> > >> > >
> > >> > > I have downloaded all ova images into one of hosts
> > >> (ovirt01) into
> > >> > > direcory /ova
> > >> > >
> > >> > > ll /ova/
> > >> > > total 6532872
> > >> > > -rw-r--r--. 1 vdsm kvm 1160387072 Feb 16 16:21
> > >> HAAS-hpcowrie.ovf
> > >> > > -rw-r--r--. 1 vdsm kvm 785984 Feb 16 16:22
> > >> HAAS-hpdio.ova
> > >> > > -rw-r--r--. 1 vdsm kvm  846736896 Feb 16 16:22
> > >> HAAS-hpjd

Re: [ovirt-users] problem importing ova vm

[Arik Hadas]

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

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

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

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


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

Re: [ovirt-users] After upgrade to 4.2 some VM won't start

[Arik Hadas]

On Tue, Feb 27, 2018 at 11:04 AM, Arsène Gschwind  wrote:

> Hi,
>
> I would like investigate what went wrong during the Cluster Compatibility
> update on running VMs, for sure the workaround by creating new VM and
> attaching disk works great but i think it would be interesting to know what
> went wrong.
>
> I've tried to find a way to create a dump of the VM config to be able to
> make a diff between old and new one to see what is different but without
> any luck so far...
>
> Any idea how to create such a dump?
>
Can you please provide the output of the following query in your database:

select type, device, address, alias, is_managed, is_plugged from vm_device
where vm_id in (select vm_guid from vm_static where vm_name='');

where  is the name of one of the VMs you can't start because of
that NPE?


> Thanks for any help.
>
> rgds,
>
> Arsene
>
> On 02/24/2018 09:03 AM, Arsène Gschwind wrote:
>
> When creating an identical VM and attaching the one disk it will start and
> run perfectly. It seems that during the Cluster Compatibility Update
> something doesn't work right on running VM, this only happens on running
> VMs and I could reproduce it.
>
> Is there a way to do some kind of diff between the new and the old VM
> settings to find out what may be different?
>
> Thanks,
> Arsene
>
> On 02/23/2018 08:14 PM, Arsène Gschwind wrote:
>
> Hi,
>
> After upgrading cluster compatibility to 4.2 some VM won't start and I'm
> unable to figured out why, it throws a java exception.
>
> I've attached the engine log.
>
> Thanks for any help/hint.
>
> rgds,
> Arsene
> --
>
> *Arsène Gschwind*
> Fa. Sapify AG im Auftrag der Universität Basel
> IT Services
> Klingelbergstr. 70 |  CH-4056 Basel  |  Switzerland
> Tel. +41 79 449 25 63 <+41%2079%20449%2025%2063>  |  http://its.unibas.ch
> ITS-ServiceDesk: support-...@unibas.ch | +41 61 267 14 11
> <+41%2061%20267%2014%2011>
>
>
> ___
> Users mailing listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users
>
>
> --
>
> *Arsène Gschwind*
> Fa. Sapify AG im Auftrag der Universität Basel
> IT Services
> Klingelbergstr. 70 |  CH-4056 Basel  |  Switzerland
> Tel. +41 79 449 25 63 <+41%2079%20449%2025%2063>  |  http://its.unibas.ch
> ITS-ServiceDesk: support-...@unibas.ch | +41 61 267 14 11
> <+41%2061%20267%2014%2011>
>
>
> ___
> Users mailing listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users
>
>
> --
>
> *Arsène Gschwind*
> Fa. Sapify AG im Auftrag der Universität Basel
> IT Services
> Klingelbergstr. 70 |  CH-4056 Basel  |  Switzerland
> Tel. +41 79 449 25 63 <+41%2079%20449%2025%2063>  |  http://its.unibas.ch
> ITS-ServiceDesk: support-...@unibas.ch | +41 61 267 14 11
> <+41%2061%20267%2014%2011>
>
> ___
> 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 remove vm.

[Arik Hadas]

On Thu, Mar 1, 2018 at 6:01 PM, nicola gentile 
wrote:

> Hi,
> I have a problem. I try to remove a pool and than I remove every vm
> but one of this display the message "Cannot remove VM. Related
> operation is currently in progress. Please try again later."


> I try to unlock with this command
>
> PGPASSWORD=... /usr/share/ovirt-engine/setup/dbutils/unlock_entity.sh
> -t all -u engine
>
> but not working
>

Yeah, that wouldn't work since the VM is locked in-memory (as opposed to
being locked in the database).


>
> in /var/log/ovirt-engine/engine.log
>
> 2018-03-01 17:02:47,799+01 INFO
> [org.ovirt.engine.core.bll.RemoveVmCommand] (default task-33)
> [0217d710-afb6-4450-9897-02748d871aa1] Failed to Acquire Lock to
> object 'EngineLock:{exclusiveLocks='[d623ad44-a645-4fd0-9993-
> d21374e99eb5=VM]',
> sharedLocks=''}'
> 2018-03-01 17:02:47,799+01 WARN
> [org.ovirt.engine.core.bll.RemoveVmCommand] (default task-33)
> [0217d710-afb6-4450-9897-02748d871aa1] Validation of action 'RemoveVm'
> failed for user admin@internal-authz. Reasons:
> VAR__ACTION__REMOVE,VAR__TYPE__VM,ACTION_TYPE_FAILED_OBJECT_LOCKED
>
> please help
>

What's the status of the VMs that are attached to the pool? It may be that
some of those VMs cannot be stopped and so they remain locked by the
remove-pool operation, but hard to tell without a complete engine log.
Anyway, you can restart the engine - it would probably release that
in-memory lock that prevents you from removing the VM.


>
> thanks
>
> Nick
> ___
> 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] Export VM to OVA failed

[Arik Hadas]

On Mon, Mar 5, 2018 at 6:29 PM, Fabrice SOLER <
fabrice.so...@ac-guadeloupe.fr> wrote:

> Hello,
>
> I need to export my VM to OVA format from the administration portail
> Ovirt. It fails with this message :
>
> *Failed to export Vm CentOS as a Virtual Appliance to path
> /data/CentOS.ova on Host eple-rectorat-proto*
>
> My storage is local (not NFS or iSCSI), is there some particulars
> permissions to put to the destination directory ?
>
No, the script that packs the OVA is executed with root permissions.


> The path is the path to an export domain ?
>
Not necessarily.


> Sincerely,
>
> Fabrice SOLER
> --
>
> ___
> 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] Export VM to OVA failed

[Arik Hadas]

On Mon, Mar 5, 2018 at 6:48 PM, Arik Hadas  wrote:

>
>
> On Mon, Mar 5, 2018 at 6:29 PM, Fabrice SOLER <
> fabrice.so...@ac-guadeloupe.fr> wrote:
>
>> Hello,
>>
>> I need to export my VM to OVA format from the administration portail
>> Ovirt. It fails with this message :
>>
>> *Failed to export Vm CentOS as a Virtual Appliance to path
>> /data/CentOS.ova on Host eple-rectorat-proto*
>>
>> My storage is local (not NFS or iSCSI), is there some particulars
>> permissions to put to the destination directory ?
>>
> No, the script that packs the OVA is executed with root permissions.
>
>
>> The path is the path to an export domain ?
>>
> Not necessarily.
>

Oh, and please share the (engine, ansible) logs if you want more eyes
looking at that failure.


>
>
>> Sincerely,
>>
>> Fabrice SOLER
>> --
>>
>> ___
>> 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] Export VM to OVA failed

[Arik Hadas]

On Mon, Mar 5, 2018 at 7:13 PM, Fabrice SOLER <
fabrice.so...@ac-guadeloupe.fr> wrote:

> Hello,
>
> Thank for your answer, I have put all permissions for the directory and I
> always have errors.
>
> Here are the ERROR in logs on the engine :
>
> 2018-03-05 13:03:18,525-04 INFO  [org.ovirt.engine.core.
> vdsbroker.vdsbroker.GetVolumeInfoVDSCommand] 
> (EE-ManagedThreadFactory-engineScheduled-Thread-23)
> [7dcef072] FINISH, GetVolumeInfoVDSCommand, return:
> org.ovirt.engine.core.common.businessentities.storage.DiskImage@90e3c610,
> log id: 84f89c3
> 2018-03-05 13:03:18,529-04 ERROR [org.ovirt.engine.core.bll.CreateOvaCommand]
> (EE-ManagedThreadFactory-engineScheduled-Thread-23) [7dcef072] Command
> 'org.ovirt.engine.core.bll.CreateOvaCommand' failed: null
> 2018-03-05 13:03:18,529-04 ERROR [org.ovirt.engine.core.bll.CreateOvaCommand]
> (EE-ManagedThreadFactory-engineScheduled-Thread-23) [7dcef072] Exception:
> java.lang.NullPointerException
> ...
>

The skipped part above is the most interesting one that may enable us to
investigate the error, can you share it? it would be best to file a bug [1]
and add the full log as an attachment (that can be made private if needed,
btw).

[1] https://bugzilla.redhat.com/


> 2018-03-05 13:03:18,533-04 ERROR 
> [org.ovirt.engine.core.bll.exportimport.ExportOvaCommand]
> (EE-ManagedThreadFactory-engineScheduled-Thread-23) [7dcef072] Failed to
> create OVA file
> 2018-03-05 13:03:18,533-04 INFO  [org.ovirt.engine.core.bll.
> SerialChildCommandsExecutionCallback] 
> (EE-ManagedThreadFactory-engineScheduled-Thread-23)
> [7dcef072] Command 'ExportOva' id: 'c484392e-3540-4a11-97bf-3fecbc13e080'
> failed when attempting to perform the next operation, marking as FAILED
> '[d5d4381b-ec82-4927-91a4-74597cd2511d]'
> 2018-03-05 13:03:18,533-04 INFO  [org.ovirt.engine.core.bll.
> SerialChildCommandsExecutionCallback] 
> (EE-ManagedThreadFactory-engineScheduled-Thread-23)
> [7dcef072] Command 'ExportOva' id: 'c484392e-3540-4a11-97bf-3fecbc13e080'
> child commands '[d5d4381b-ec82-4927-91a4-74597cd2511d]' executions were
> completed, status 'FAILED'
> 2018-03-05 13:03:19,542-04 ERROR 
> [org.ovirt.engine.core.bll.exportimport.ExportOvaCommand]
> (EE-ManagedThreadFactory-engineScheduled-Thread-98)
> [c99e94b0-a9dd-486f-9274-9aa17c9590a0] Ending command
> 'org.ovirt.engine.core.bll.exportimport.ExportOvaCommand' with failure.
> 2018-03-05 13:03:19,543-04 INFO  
> [org.ovirt.engine.core.bll.exportimport.ExportOvaCommand]
> (EE-ManagedThreadFactory-engineScheduled-Thread-98)
> [c99e94b0-a9dd-486f-9274-9aa17c9590a0] Lock freed to object
> 'EngineLock:{exclusiveLocks='[3ae307cb-53d6-4d70-87b6-4e073c6f5eb6=VM]',
> sharedLocks=''}'
> 2018-03-05 13:03:19,550-04 ERROR [org.ovirt.engine.core.dal.
> dbbroker.auditloghandling.AuditLogDirector] 
> (EE-ManagedThreadFactory-engineScheduled-Thread-98)
> [c99e94b0-a9dd-486f-9274-9aa17c9590a0] EVENT_ID:
> IMPORTEXPORT_EXPORT_VM_TO_OVA_FAILED(1,225), Failed to export Vm pfSense
> as a Virtual Appliance to path /ova/pfSense.ova on Host eple-rectorat-proto
> ...
>
> Sincerely,
> Fabrice
>
>
> Le 05/03/2018 à 12:50, Arik Hadas a écrit :
>
>
>
> On Mon, Mar 5, 2018 at 6:48 PM, Arik Hadas  wrote:
>
>>
>>
>> On Mon, Mar 5, 2018 at 6:29 PM, Fabrice SOLER <
>> fabrice.so...@ac-guadeloupe.fr> wrote:
>>
>>> Hello,
>>>
>>> I need to export my VM to OVA format from the administration portail
>>> Ovirt. It fails with this message :
>>>
>>> *Failed to export Vm CentOS as a Virtual Appliance to path
>>> /data/CentOS.ova on Host eple-rectorat-proto*
>>>
>>> My storage is local (not NFS or iSCSI), is there some particulars
>>> permissions to put to the destination directory ?
>>>
>> No, the script that packs the OVA is executed with root permissions.
>>
>>
>>> The path is the path to an export domain ?
>>>
>> Not necessarily.
>>
>
> Oh, and please share the (engine, ansible) logs if you want more eyes
> looking at that failure.
>
>
>>
>>
>>> Sincerely,
>>>
>>> Fabrice SOLER
>>> --
>>>
>>> ___
>>> 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] After the export, the import OVA failed

[Arik Hadas]

On Mon, Mar 5, 2018 at 11:01 PM, Fabrice SOLER <
fabrice.so...@ac-guadeloupe.fr> wrote:

> Hello,
>
> I found this KB : https://bugzilla.redhat.com/show_bug.cgi?id=1529607
> and put a description to the VM disk and the OVA export works ! :-)
>
> Now, the import does not work :-(
>
> The error is :
>
> *Failed to load VM configuration from OVA file: /data/ova/amon *I have
> tried two ways.
> In first, I let the file ova.
> Secondely I did  : tar xvf file.ova and specifiy the directory where the
> ovf file is.
>
> In the engine log, I have found this :
>
> 2018-03-05 16:15:58,319-04 INFO  
> [org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor]
> (default task-6) [e2a953ca-1460-4899-a958-7dbe37e40a21] Ansible playbook
> command has exited with value: 2
> 2018-03-05 16:15:58,319-04 ERROR [org.ovirt.engine.core.bll.GetVmFromOvaQuery]
> (default task-6) [e2a953ca-1460-4899-a958-7dbe37e40a21] Failed to query
> OVA info
> 2018-03-05 16:15:58,319-04 ERROR [org.ovirt.engine.core.bll.GetVmFromOvaQuery]
> (default task-6) [e2a953ca-1460-4899-a958-7dbe37e40a21] Query
> 'GetVmFromOvaQuery' failed: EngineException: Failed to query OVA info
> (Failed with error GeneralException and code 100)
>
> I have found this KB : https://bugzilla.redhat.com/show_bug.cgi?id=1529965
> The unique solution is a update ?
>

I highly suggest updating to the latest version, various issues related to
OVA export/import were recently fixed.


>
> Sincerely
> Fabrice
>
>
> Le 05/03/2018 à 13:13, Fabrice SOLER a écrit :
>
> Hello,
>
> Thank for your answer, I have put all permissions for the directory and I
> always have errors.
>
> Here are the ERROR in logs on the engine :
>
> 2018-03-05 13:03:18,525-04 INFO  [org.ovirt.engine.core.
> vdsbroker.vdsbroker.GetVolumeInfoVDSCommand] 
> (EE-ManagedThreadFactory-engineScheduled-Thread-23)
> [7dcef072] FINISH, GetVolumeInfoVDSCommand, return:
> org.ovirt.engine.core.common.businessentities.storage.DiskImage@90e3c610,
> log id: 84f89c3
> 2018-03-05 13:03:18,529-04 ERROR [org.ovirt.engine.core.bll.CreateOvaCommand]
> (EE-ManagedThreadFactory-engineScheduled-Thread-23) [7dcef072] Command
> 'org.ovirt.engine.core.bll.CreateOvaCommand' failed: null
> 2018-03-05 13:03:18,529-04 ERROR [org.ovirt.engine.core.bll.CreateOvaCommand]
> (EE-ManagedThreadFactory-engineScheduled-Thread-23) [7dcef072] Exception:
> java.lang.NullPointerException
> ...
> 2018-03-05 13:03:18,533-04 ERROR 
> [org.ovirt.engine.core.bll.exportimport.ExportOvaCommand]
> (EE-ManagedThreadFactory-engineScheduled-Thread-23) [7dcef072] Failed to
> create OVA file
> 2018-03-05 13:03:18,533-04 INFO  [org.ovirt.engine.core.bll.
> SerialChildCommandsExecutionCallback] 
> (EE-ManagedThreadFactory-engineScheduled-Thread-23)
> [7dcef072] Command 'ExportOva' id: 'c484392e-3540-4a11-97bf-3fecbc13e080'
> failed when attempting to perform the next operation, marking as FAILED
> '[d5d4381b-ec82-4927-91a4-74597cd2511d]'
> 2018-03-05 13:03:18,533-04 INFO  [org.ovirt.engine.core.bll.
> SerialChildCommandsExecutionCallback] 
> (EE-ManagedThreadFactory-engineScheduled-Thread-23)
> [7dcef072] Command 'ExportOva' id: 'c484392e-3540-4a11-97bf-3fecbc13e080'
> child commands '[d5d4381b-ec82-4927-91a4-74597cd2511d]' executions were
> completed, status 'FAILED'
> 2018-03-05 13:03:19,542-04 ERROR 
> [org.ovirt.engine.core.bll.exportimport.ExportOvaCommand]
> (EE-ManagedThreadFactory-engineScheduled-Thread-98)
> [c99e94b0-a9dd-486f-9274-9aa17c9590a0] Ending command
> 'org.ovirt.engine.core.bll.exportimport.ExportOvaCommand' with failure.
> 2018-03-05 13:03:19,543-04 INFO  
> [org.ovirt.engine.core.bll.exportimport.ExportOvaCommand]
> (EE-ManagedThreadFactory-engineScheduled-Thread-98)
> [c99e94b0-a9dd-486f-9274-9aa17c9590a0] Lock freed to object
> 'EngineLock:{exclusiveLocks='[3ae307cb-53d6-4d70-87b6-4e073c6f5eb6=VM]',
> sharedLocks=''}'
> 2018-03-05 13:03:19,550-04 ERROR [org.ovirt.engine.core.dal.
> dbbroker.auditloghandling.AuditLogDirector] 
> (EE-ManagedThreadFactory-engineScheduled-Thread-98)
> [c99e94b0-a9dd-486f-9274-9aa17c9590a0] EVENT_ID:
> IMPORTEXPORT_EXPORT_VM_TO_OVA_FAILED(1,225), Failed to export Vm pfSense
> as a Virtual Appliance to path /ova/pfSense.ova on Host eple-rectorat-proto
> ...
>
> Sincerely,
> Fabrice
>
> Le 05/03/2018 à 12:50, Arik Hadas a écrit :
>
>
>
> On Mon, Mar 5, 2018 at 6:48 PM, Arik Hadas  wrote:
>
>>
>>
>> On Mon, Mar 5, 2018 at 6:29 PM, Fabrice SOLER <
>> fabrice.so...@ac-guadeloupe.fr> wrote:
>>
>>> Hello,
>>>
>>&g

Re: [ovirt-users] After the export, the import OVA failed

[Arik Hadas]

On Tue, Mar 6, 2018 at 10:23 PM, Fabrice SOLER  wrote:

> Hello,
>
> I have imported a VM with OVA created with VMware and it works !
>

That's great, but note that importing an OVA that was created by VMware is
totally different than importing an OVA that was created by oVirt
implementation-wise.


> So, the problem is in the export ! The vm.ovf has no line terminators,
> that why it does not work !
>
> * [root@ovirt-eple amon]# file vm.ovf*
> * vm.ovf: XML 1.0 document, ASCII text, with very long lines, with no line
> terminators*
>
> Is there somebody would know a solution ?
>

I'm afraid that's not the issue here - the OVF inside the OVA seems valid
(otherwise, the UI would have failed to "load" the configuration from the
OVA file).
You may be facing one of the various issues that were already resolved and
will be available in 4.2.2, but it's hard to tell without having the logs.
If you can share the engine+ansible logs, we will gladly look at them and
try to shed more light on the issue you're facing.
Otherwise, I would suggest to wait for 4.2.2 where the new OVA support is
much more mature.


>
> Sincerely,
> Fabrice SOLER
>
>
>
> Le 06/03/2018 à 14:25, Fabrice SOLER a écrit :
>
> Hi,
>
> I have deleted the VM amon and tried to import the OVA. It does not work.
> I think there is a problem in the ovf file (XML format) like I posted in
> the precedente mail :
>
> *I constated that the ovf format is not the same when I made the export
> ova with vmware and ovirt.*
>
> * Export ova with vmware :*
>
> * [root@eple-rectorat-proto AntiVirus]# file AntiVirus.ovf*
> * AntiVirus.ovf: XML 1.0 document, ASCII text, with very long lines, with
> CRLF line terminators*
>
> * Export ova with ovirt :*
> * [root@ovirt-eple amon]# file vm.ovf*
> * vm.ovf: XML 1.0 document, ASCII text, with very long lines, with no line
> terminators*
>
> * With Ovirt there is no line terminators.*
>
> * Is that normal ? Is that why the OVA import does not work ?*
>
>
>
>
>
>
>
> Le 06/03/2018 à 12:11, Oliver Riesener a écrit :
>
> Hi Fabrice,
> try to rename the already existing old VM to another name like amon-old.
> The import the OVA machine again.
>
> On 06.03.2018 15:33, Fabrice SOLER wrote:
>
> Hello,
>
> I have upgraded the engine and the node, so the version is :
> 4.2.1.1.1-1.el7
> To import, I made a "tar xvf file.ova".
> Then from the portal, I import the VM
>
>
> I saw that :
>
>
>
> After that the amon was removed as we can see in the events  :
>
>
>
> It seems it does not work. Maybe the VM is hide somewhere ?
>
> Sincerely,
>
>
>
>
> ___
> Users mailing listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users
>
>
>
> ___
> Users mailing listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users
>
>
> --
>
>
> ___
> 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] Unremovable disks created through the API

[Arik Hadas]

On Tue, Mar 6, 2018 at 9:18 PM, Richard W.M. Jones 
wrote:

>
> I've been playing with disk uploads through the API.  As a result
> I now have lots of disks in the states "Paused by System" and
> "Paused by User".  They are not attached to any VM, and I'm logged
> in as admin@internal, but there seems to be no way to use them.
> Even worse I've now run out of space so can't do anything else.
>
> How can I remove them?


> Screenshot: http://oirase.annexia.org/tmp/ovirt.png


Hi Richard,

Selecting Upload->Cancel at that tab will remove such a disk.
Note that it may take a minute or two.


>
>
> It's a pretty recent engine:
>
> ovirt-engine-4.2.2.2-0.0.master.20180225172203.
> gitd7cf125.el7.centos.noarch
>
> Rich.
>
> --
> Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~
> rjones
> Read my programming and virtualization blog: http://rwmj.wordpress.com
> virt-df lists disk usage of guests without needing to install any
> software inside the virtual machine.  Supports Linux and Windows.
> http://people.redhat.com/~rjones/virt-df/
> ___
> 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] After the export, the import OVA failed

[Arik Hadas]

On Wed, Mar 7, 2018 at 12:10 AM, Oliver Riesener <
oliver.riese...@hs-bremen.de> wrote:

> Hi Arik, Hi Fabrice,
>
> i have tried the same procedure with 4.2.1, with same results.
>
> After commands:
>
> # mkdir /var/log/ovirt-engine/ova
> # chown ovirt.ovirt /var/log/ovirt-engine/ova
>
> I can provide log files. See ansible script failed.
>
> /export/ovirt/export/xx is the correct directory where i have extracted
> the *.ova file because the UI search for *.ovf file and didn’t recognize
> *.ova files directly ?
>

Thanks for providing the logs.
We don't support OVA directory with content (OVF, disks) that was created
by oVirt yet (it only works with content that was created by VMware).
The OVA tar file should not be extracted and the path to the OVA should
include the filename, e.g., /export/ovirt/export/xx/my.ova

If you pack the directory's content into an OVA file, please note that the
OVF should be placed at the first entry.

There is a bug about changing 'path' to something like 'path to ova file'
in the import dialog [1], I may add a validation for that as well until
we'll also support the OVA directory format.

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1547636


>
> Please see attachments:
>
> Cheers
> Olri
>
>
>
>
>
> Am 06.03.2018 um 19:25 schrieb Fabrice SOLER  fr>:
>
> Hi,
>
> I have deleted the VM amon and tried to import the OVA. It does not work.
> I think there is a problem in the ovf file (XML format) like I posted in
> the precedente mail :
>
> *I constated that the ovf format is not the same when I made the export
> ova with vmware and ovirt.*
>
> * Export ova with vmware :*
>
> * [root@eple-rectorat-proto AntiVirus]# file AntiVirus.ovf*
> * AntiVirus.ovf: XML 1.0 document, ASCII text, with very long lines, with
> CRLF line terminators*
>
> * Export ova with ovirt :*
> * [root@ovirt-eple amon]# file vm.ovf*
> * vm.ovf: XML 1.0 document, ASCII text, with very long lines, with no line
> terminators*
>
> * With Ovirt there is no line terminators.*
>
> * Is that normal ? Is that why the OVA import does not work ?*
>
>
>
>
>
>
>
> Le 06/03/2018 à 12:11, Oliver Riesener a écrit :
>
> Hi Fabrice,
> try to rename the already existing old VM to another name like amon-old.
> The import the OVA machine again.
>
> On 06.03.2018 15:33, Fabrice SOLER wrote:
>
> Hello,
>
> I have upgraded the engine and the node, so the version is :
> 4.2.1.1.1-1.el7
> To import, I made a "tar xvf file.ova".
> Then from the portal, I import the VM
>
> 
> I saw that :
>
> 
>
> After that the amon was removed as we can see in the events  :
>
> 
>
> It seems it does not work. Maybe the VM is hide somewhere ?
>
> Sincerely,
>
>
> 
>
>
> ___
> Users mailing listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users
>
>
>
> ___
> 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] Unable to start VM after upgrade vom 4.1.9 to 4.2.1 - NPE

[Arik Hadas]

On Wed, Mar 7, 2018 at 4:11 PM, Jan Siml  wrote:

> Hello,
>
> we have upgrade one of our oVirt engines to 4.2.1 (from 4.1.9) and
> afterwards all nodes too. The cluster compatibility level has been set to
> 4.2.
>
> Now we can't start a VM after it has been powered off. The only hint we
> found in engine.log is:
>
> 2018-03-07 14:51:52,504+01 INFO [org.ovirt.engine.core.vdsbrok
> er.UpdateVmDynamicDataVDSCommand] (EE-ManagedThreadFactory-engine-Thread-25)
> [f855b54a-56d9-4708-8a67-5609438ddadb] START,
> UpdateVmDynamicDataVDSCommand( 
> UpdateVmDynamicDataVDSCommandParameters:{hostId='null',
> vmId='a7bc4124-06cb-4909-9389-bcf727df1304', vmDynamic='
> org.ovirt.engine.core.common.businessentities.VmDynamic@491983e9'}), log
> id: 7d49849e
> 2018-03-07 14:51:52,509+01 INFO [org.ovirt.engine.core.vdsbrok
> er.UpdateVmDynamicDataVDSCommand] (EE-ManagedThreadFactory-engine-Thread-25)
> [f855b54a-56d9-4708-8a67-5609438ddadb] FINISH,
> UpdateVmDynamicDataVDSCommand, log id: 7d49849e
> 2018-03-07 14:51:52,531+01 INFO 
> [org.ovirt.engine.core.vdsbroker.CreateVDSCommand]
> (EE-ManagedThreadFactory-engine-Thread-25) 
> [f855b54a-56d9-4708-8a67-5609438ddadb]
> START, CreateVDSCommand( CreateVDSCommandParameters:{ho
> stId='0add031e-c72f-473f-ab2f-4f7abd1f402b',
> vmId='a7bc4124-06cb-4909-9389-bcf727df1304', vm='VM [prod-hub-201]'}),
> log id: 4af1f227
> 2018-03-07 14:51:52,533+01 INFO [org.ovirt.engine.core.vdsbrok
> er.vdsbroker.CreateBrokerVDSCommand] 
> (EE-ManagedThreadFactory-engine-Thread-25)
> [f855b54a-56d9-4708-8a67-5609438ddadb] START,
> CreateBrokerVDSCommand(HostName = prod-node-210,
> CreateVDSCommandParameters:{hostId='0add031e-c72f-473f-ab2f-4f7abd1f402b',
> vmId='a7bc4124-06cb-4909-9389-bcf727df1304', vm='VM [prod-hub-201]'}),
> log id: 71dcc8e7
> 2018-03-07 14:51:52,545+01 ERROR [org.ovirt.engine.core.vdsbrok
> er.vdsbroker.CreateBrokerVDSCommand] 
> (EE-ManagedThreadFactory-engine-Thread-25)
> [f855b54a-56d9-4708-8a67-5609438ddadb] Failed in 'CreateBrokerVDS'
> method, for vds: 'prod-node-210'; host: 'prod-node-210': null
> 2018-03-07 14:51:52,546+01 ERROR [org.ovirt.engine.core.vdsbrok
> er.vdsbroker.CreateBrokerVDSCommand] 
> (EE-ManagedThreadFactory-engine-Thread-25)
> [f855b54a-56d9-4708-8a67-5609438ddadb] Command
> 'CreateBrokerVDSCommand(HostName = prod-node-210,
> CreateVDSCommandParameters:{hostId='0add031e-c72f-473f-ab2f-4f7abd1f402b',
> vmId='a7bc4124-06cb-4909-9389-bcf727df1304', vm='VM
> [prod-hub-201]'})' execution failed: null
> 2018-03-07 14:51:52,546+01 INFO [org.ovirt.engine.core.vdsbrok
> er.vdsbroker.CreateBrokerVDSCommand] 
> (EE-ManagedThreadFactory-engine-Thread-25)
> [f855b54a-56d9-4708-8a67-5609438ddadb] FINISH, CreateBrokerVDSCommand,
> log id: 71dcc8e7
> 2018-03-07 14:51:52,546+01 ERROR 
> [org.ovirt.engine.core.vdsbroker.CreateVDSCommand]
> (EE-ManagedThreadFactory-engine-Thread-25) [f855b5
> 4a-56d9-4708-8a67-5609438ddadb] Failed to create VM:
> java.lang.NullPointerException
> at org.ovirt.engine.core.vdsbroker.builder.vminfo.LibvirtVmXmlB
> uilder.lambda$writeInterfaces$23(LibvirtVmXmlBuilder.java:1066)
>  [vdsbroker.jar:]
>
> [...]
>
> But this doesn't lead us to the root cause. I haven't found any matching
> bug tickets in release notes for upcoming 4.2.1. Can anyone help here?
>

What's the mac address of that VM?
You can find it in the UI or with:

select mac_addr from vm_interface where vm_guid in (select vm_guid from
vm_static where vm_name='');


>
> Kind regards
>
> Jan Siml
> ___
> 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 start VM after upgrade vom 4.1.9 to 4.2.1 - NPE

[Arik Hadas]

On Wed, Mar 7, 2018 at 5:20 PM, Arik Hadas  wrote:

>
>
> On Wed, Mar 7, 2018 at 4:11 PM, Jan Siml  wrote:
>
>> Hello,
>>
>> we have upgrade one of our oVirt engines to 4.2.1 (from 4.1.9) and
>> afterwards all nodes too. The cluster compatibility level has been set to
>> 4.2.
>>
>> Now we can't start a VM after it has been powered off. The only hint we
>> found in engine.log is:
>>
>> 2018-03-07 14:51:52,504+01 INFO [org.ovirt.engine.core.vdsbrok
>> er.UpdateVmDynamicDataVDSCommand] (EE-ManagedThreadFactory-engine-Thread-25)
>> [f855b54a-56d9-4708-8a67-5609438ddadb] START,
>> UpdateVmDynamicDataVDSCommand( 
>> UpdateVmDynamicDataVDSCommandParameters:{hostId='null',
>> vmId='a7bc4124-06cb-4909-9389-bcf727df1304', vmDynamic='
>> org.ovirt.engine.core.common.businessentities.VmDynamic@491983e9'}), log
>> id: 7d49849e
>> 2018-03-07 14:51:52,509+01 INFO [org.ovirt.engine.core.vdsbrok
>> er.UpdateVmDynamicDataVDSCommand] (EE-ManagedThreadFactory-engine-Thread-25)
>> [f855b54a-56d9-4708-8a67-5609438ddadb] FINISH,
>> UpdateVmDynamicDataVDSCommand, log id: 7d49849e
>> 2018-03-07 14:51:52,531+01 INFO 
>> [org.ovirt.engine.core.vdsbroker.CreateVDSCommand]
>> (EE-ManagedThreadFactory-engine-Thread-25) 
>> [f855b54a-56d9-4708-8a67-5609438ddadb]
>> START, CreateVDSCommand( CreateVDSCommandParameters:{ho
>> stId='0add031e-c72f-473f-ab2f-4f7abd1f402b',
>> vmId='a7bc4124-06cb-4909-9389-bcf727df1304', vm='VM [prod-hub-201]'}),
>> log id: 4af1f227
>> 2018-03-07 14:51:52,533+01 INFO [org.ovirt.engine.core.vdsbrok
>> er.vdsbroker.CreateBrokerVDSCommand] 
>> (EE-ManagedThreadFactory-engine-Thread-25)
>> [f855b54a-56d9-4708-8a67-5609438ddadb] START,
>> CreateBrokerVDSCommand(HostName = prod-node-210,
>> CreateVDSCommandParameters:{hostId='0add031e-c72f-473f-ab2f-4f7abd1f402b',
>> vmId='a7bc4124-06cb-4909-9389-bcf727df1304', vm='VM [prod-hub-201]'}),
>> log id: 71dcc8e7
>> 2018-03-07 14:51:52,545+01 ERROR [org.ovirt.engine.core.vdsbrok
>> er.vdsbroker.CreateBrokerVDSCommand] 
>> (EE-ManagedThreadFactory-engine-Thread-25)
>> [f855b54a-56d9-4708-8a67-5609438ddadb] Failed in 'CreateBrokerVDS'
>> method, for vds: 'prod-node-210'; host: 'prod-node-210': null
>> 2018-03-07 14:51:52,546+01 ERROR [org.ovirt.engine.core.vdsbrok
>> er.vdsbroker.CreateBrokerVDSCommand] 
>> (EE-ManagedThreadFactory-engine-Thread-25)
>> [f855b54a-56d9-4708-8a67-5609438ddadb] Command
>> 'CreateBrokerVDSCommand(HostName = prod-node-210,
>> CreateVDSCommandParameters:{hostId='0add031e-c72f-473f-ab2f-4f7abd1f402b',
>> vmId='a7bc4124-06cb-4909-9389-bcf727df1304', vm='VM
>> [prod-hub-201]'})' execution failed: null
>> 2018-03-07 14:51:52,546+01 INFO [org.ovirt.engine.core.vdsbrok
>> er.vdsbroker.CreateBrokerVDSCommand] 
>> (EE-ManagedThreadFactory-engine-Thread-25)
>> [f855b54a-56d9-4708-8a67-5609438ddadb] FINISH, CreateBrokerVDSCommand,
>> log id: 71dcc8e7
>> 2018-03-07 14:51:52,546+01 ERROR 
>> [org.ovirt.engine.core.vdsbroker.CreateVDSCommand]
>> (EE-ManagedThreadFactory-engine-Thread-25) [f855b5
>> 4a-56d9-4708-8a67-5609438ddadb] Failed to create VM:
>> java.lang.NullPointerException
>> at org.ovirt.engine.core.vdsbroker.builder.vminfo.LibvirtVmXmlB
>> uilder.lambda$writeInterfaces$23(LibvirtVmXmlBuilder.java:1066)
>>  [vdsbroker.jar:]
>>
>> [...]
>>
>> But this doesn't lead us to the root cause. I haven't found any matching
>> bug tickets in release notes for upcoming 4.2.1. Can anyone help here?
>>
>
> What's the mac address of that VM?
> You can find it in the UI or with:
>
> select mac_addr from vm_interface where vm_guid in (select vm_guid from
> vm_static where vm_name='');
>

Actually, different question - does this VM has unplugged network interface?


>
>
>>
>> Kind regards
>>
>> Jan Siml
>> ___
>> 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 start VM after upgrade vom 4.1.9 to 4.2.1 - NPE

[Arik Hadas]

On Wed, Mar 7, 2018 at 5:32 PM, Jan Siml  wrote:

> Hello Arik,
>
>
> we have upgrade one of our oVirt engines to 4.2.1 (from 4.1.9)
>> and afterwards all nodes too. The cluster compatibility level
>> has been set to 4.2.
>>
>> Now we can't start a VM after it has been powered off. The only
>> hint we found in engine.log is:
>>
>> 2018-03-07 14:51:52,504+01 INFO
>> [org.ovirt.engine.core.vdsbroker.UpdateVmDynamicDataVDSCommand]
>> (EE-ManagedThreadFactory-engine-Thread-25)
>> [f855b54a-56d9-4708-8a67-5609438ddadb] START,
>> UpdateVmDynamicDataVDSCommand(
>> UpdateVmDynamicDataVDSCommandParameters:{hostId='null',
>> vmId='a7bc4124-06cb-4909-9389-bcf727df1304',
>> vmDynamic='org.ovirt.engine.co
>> re.common.businessentities.VmDyn
>> amic@491983e9'}),
>>
>> log id: 7d49849e
>> 2018-03-07 14:51:52,509+01 INFO
>> [org.ovirt.engine.core.vdsbroker.UpdateVmDynamicDataVDSCommand]
>> (EE-ManagedThreadFactory-engine-Thread-25)
>> [f855b54a-56d9-4708-8a67-5609438ddadb] FINISH,
>> UpdateVmDynamicDataVDSCommand, log id: 7d49849e
>> 2018-03-07 14:51:52,531+01 INFO
>> [org.ovirt.engine.core.vdsbroker.CreateVDSCommand]
>> (EE-ManagedThreadFactory-engine-Thread-25)
>> [f855b54a-56d9-4708-8a67-5609438ddadb] START, CreateVDSCommand(
>> CreateVDSCommandParameters:{hostId='0add031e-c72f-473f-ab2f-
>> 4f7abd1f402b',
>> vmId='a7bc4124-06cb-4909-9389-bcf727df1304', vm='VM
>> [prod-hub-201]'}), log id: 4af1f227
>> 2018-03-07 14:51:52,533+01 INFO
>> [org.ovirt.engine.core.vdsbroker.vdsbroker.CreateBrokerVDSCo
>> mmand]
>> (EE-ManagedThreadFactory-engine-Thread-25)
>> [f855b54a-56d9-4708-8a67-5609438ddadb] START,
>> CreateBrokerVDSCommand(HostName = prod-node-210,
>> CreateVDSCommandParameters:{hostId='0add031e-c72f-473f-ab2f-
>> 4f7abd1f402b',
>> vmId='a7bc4124-06cb-4909-9389-bcf727df1304', vm='VM
>> [prod-hub-201]'}), log id: 71dcc8e7
>> 2018-03-07 14:51:52,545+01 ERROR
>> [org.ovirt.engine.core.vdsbroker.vdsbroker.CreateBrokerVDSCo
>> mmand]
>> (EE-ManagedThreadFactory-engine-Thread-25)
>> [f855b54a-56d9-4708-8a67-5609438ddadb] Failed in
>> 'CreateBrokerVDS' method, for vds: 'prod-node-210'; host:
>> 'prod-node-210': null
>> 2018-03-07 14:51:52,546+01 ERROR
>> [org.ovirt.engine.core.vdsbroker.vdsbroker.CreateBrokerVDSCo
>> mmand]
>> (EE-ManagedThreadFactory-engine-Thread-25)
>> [f855b54a-56d9-4708-8a67-5609438ddadb] Command
>> 'CreateBrokerVDSCommand(HostName = prod-node-210,
>> CreateVDSCommandParameters:{hostId='0add031e-c72f-473f-ab2f-
>> 4f7abd1f402b',
>> vmId='a7bc4124-06cb-4909-9389-bcf727df1304', vm='VM
>> [prod-hub-201]'})' execution failed: null
>> 2018-03-07 14:51:52,546+01 INFO
>> [org.ovirt.engine.core.vdsbroker.vdsbroker.CreateBrokerVDSCo
>> mmand]
>> (EE-ManagedThreadFactory-engine-Thread-25)
>> [f855b54a-56d9-4708-8a67-5609438ddadb] FINISH,
>> CreateBrokerVDSCommand, log id: 71dcc8e7
>> 2018-03-07 14:51:52,546+01 ERROR
>> [org.ovirt.engine.core.vdsbroker.CreateVDSCommand]
>> (EE-ManagedThreadFactory-engine-Thread-25) [f855b5
>> 4a-56d9-4708-8a67-5609438ddadb] Failed to create VM:
>> java.lang.NullPointerException
>> at
>> org.ovirt.engine.core.vdsbroker.builder.vminfo.LibvirtVmXmlB
>> uilder.lambda$writeInterfaces$23(LibvirtVmXmlBuilder.java:1066)
>>   [vdsbroker.jar:]
>>
>> [...]
>>
>> But this doesn't lead us to the root cause. I haven't found any
>> matching bug tickets in release notes for upcoming 4.2.1. Can
>> anyone help here?
>>
>>
>> What's the mac address of that VM?
>> You can find it in the UI or with:
>>
>> select mac_addr from vm_interface where vm_guid in (select vm_guid
>> from vm_static where vm_name='');
>>
>>
>> Actually, different question - does this VM has unplugged network
>> interface?
>>
>
> The VM has two NICs. Both are plugged.
>
> The MAC addresses are 00:1a:4a:18:01:52 for nic1 and 00:1a:4a:36:01:67 for
> nic2.
>

OK, those seem like two valid mac addresses so maybe something is wrong
with the vm devices.
Could you please provide the output of:

select type, device, address, is_managed, is_plugged, alias from vm_device
where vm_id in (select vm_guid from vm_static where vm_name='');


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

Re: [ovirt-users] Unable to start VM after upgrade vom 4.1.9 to 4.2.1 - NPE

[Arik Hadas]

On Wed, Mar 7, 2018 at 6:15 PM, Jan Siml  wrote:

> Hello,
>
> Enable network and disks on your VM than do:
>>> Run -> ONCE Ok Ignore errors. Ok
>>> Run
>>> Cheeers
>>>
>>
>> WTF! That worked.
>>
>> Did you know, why this works and what happens in the background? Is there
>> a Bugzilla bug ID for this issue?
>>
>
> BTW, here is the list of devices before:
>
> engine=# select type, device, address, is_managed, is_plugged, alias from
> vm_device where vm_id in (select vm_guid from vm_static where
> vm_name='prod-hub-201');
> type|device |   address
> | is_managed | is_plugged | alias
> +---+---
> ---+++
>  video  | qxl   || t  | t
> |
>  controller | virtio-scsi   || t  | t
> |
>  balloon| memballoon|| t  | f
> | balloon0
>  graphics   | spice || t  | t
> |
>  controller | virtio-serial | {slot=0x06, bus=0x00, domain=0x,
> type=pci, function=0x0} | t  | t  | virtio-serial0
>  disk   | disk  | {slot=0x07, bus=0x00, domain=0x,
> type=pci, function=0x0} | f  | t  | virtio-disk0
>  memballoon | memballoon| {slot=0x08, bus=0x00, domain=0x,
> type=pci, function=0x0} | f  | t  | balloon0
>  interface  | bridge| {slot=0x03, bus=0x00, domain=0x,
> type=pci, function=0x0} | f  | t  | net0
>  interface  | bridge| {slot=0x09, bus=0x00, domain=0x,
> type=pci, function=0x0} | f  | t  | net1
>  controller | scsi  | {slot=0x05, bus=0x00, domain=0x,
> type=pci, function=0x0} | f  | t  | scsi0
>  controller | ide   | {slot=0x01, bus=0x00, domain=0x,
> type=pci, function=0x1} | f  | t  | ide
>  controller | usb   | {slot=0x01, bus=0x00, domain=0x,
> type=pci, function=0x2} | t  | t  | usb
>  channel| unix  | {bus=0, controller=0, type=virtio-serial,
> port=1}| f  | t  | channel0
>  channel| unix  | {bus=0, controller=0, type=virtio-serial,
> port=2}| f  | t  | channel1
>  channel| spicevmc  | {bus=0, controller=0, type=virtio-serial,
> port=3}| f  | t  | channel2
>  interface  | bridge|| t  | t
> | net1
>  interface  | bridge|| t  | t
> | net0
>  disk   | cdrom || t  | f
> | ide0-1-0
>  disk   | cdrom | {bus=1, controller=0, type=drive, target=0,
> unit=0}  | f  | t  | ide0-1-0
>  disk   | disk  || t  | t
> | virtio-disk0
> (20 rows)
>
> and afterwards:
>
> engine=# select type, device, address, is_managed, is_plugged, alias from
> vm_device where vm_id in (select vm_guid from vm_static where
> vm_name='prod-hub-201');
> type|device |   address
> | is_managed | is_plugged | alias
> +---+---
> ---+++
>  channel| spicevmc  | {type=virtio-serial, bus=0, controller=0,
> port=3}| f  | t  | channel2
>  channel| unix  | {type=virtio-serial, bus=0, controller=0,
> port=1}| f  | t  | channel0
>  interface  | bridge| {type=pci, slot=0x04, bus=0x00,
> domain=0x, function=0x0} | t  | t  | net1
>  controller | usb   | {type=pci, slot=0x01, bus=0x00,
> domain=0x, function=0x2} | t  | t  | usb
>  controller | virtio-serial | {type=pci, slot=0x06, bus=0x00,
> domain=0x, function=0x0} | t  | t  | virtio-serial0
>  interface  | bridge| {type=pci, slot=0x03, bus=0x00,
> domain=0x, function=0x0} | t  | t  | net0
>  controller | virtio-scsi   | {type=pci, slot=0x05, bus=0x00,
> domain=0x, function=0x0} | t  | t  | scsi0
>  video  | qxl   | {type=pci, slot=0x02, bus=0x00,
> domain=0x, function=0x0} | t  | t  | video0
>  channel| unix  | {type=virtio-serial, bus=0, controller=0,
> port=2}| f  | t  | channel1
>  balloon| memballoon|| t  | t
> | balloon0
>  graphics   | spice || t  | t
> |
>  disk   | cdrom || t  | f
> | ide0-1-0
>  disk   | disk  | {type=pci, slot=0x07, bus=0x00,
> domain=0x, function=0x0} | t  | t  | virtio-disk0
> (13 rows)
>
>
Thanks.
The

[ovirt-users] Fwd: question about importing VMware-produced OVA

[Arik Hadas]

Sharing the thread below with the list.

-- Forwarded message --
From: Shao-Da Huang 
Date: Tue, Mar 13, 2018 at 11:23 AM
Subject: Re: question about importing VMware-produced OVA
To: Arik Hadas 


2018-03-13 15:51 GMT+08:00 Arik Hadas :

>
> On Tue, Mar 13, 2018 at 6:10 AM, Shao-Da Huang 
> wrote:
>
>> Hi Arik,
>>
>> I'm Michael, an oVirt user from Taiwan, and I'm trying to import OVAs
>> produced by VMware into my data center.
>> I've tried the functionality in the 'Virtual Machine' tab -> Import ->
>> Source 'VMware Virtual Appliance (OVA)', but I wanna know that is there a
>> corresponding REST API so I can use it to automate this procedure?
>>
>> I found the
>> POST /externalvmimports API,
>> but it seems not to be used for OVA.
>>
>
> Hi Michael,
>
> You can import an OVA via REST-API using that post command. Let's say that
> you would like to import an OVA that is located in /home/user/vm.ova on
> host 'myhost' then you should set the host to 'myhost', the URL to
> 'ova:///home/user/vm.ova' and the provider to VMware.
>
> Please let me know if that did the trick.
>

Thank you very much! It works!


> Btw, any reason not to send this to the users-list?
>
If no such REST API exists, how to use CLI commands combinations to achieve
>> the same goal as in the engine UI?
>>
>> Could you give me some advices?
>>
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] VM stuck in Locked mode after failed migration

[Arik Hadas]

On Tue, Mar 13, 2018 at 4:15 PM, John Nguyen  wrote:

> Hi Guys,
>
> My environment is running Ovirt 3.6 and due to power fluctuation caused by
> recent weather.  I have a handful of VMs stuck in a locked state as they
> failed to migrate between panicked host.
>
> I have purged zombie tasks and ran the unlocked utility as documented in
> https://www.ovirt.org/develop/developer-guide/db-issues/helperutilities/
> unlock_entity.sh completed successfully, however the vms are stilled in a
> locked state.
>
> Unfortunately I'm unable to attach logs because of my companies security
> posture.
>
> Any help would be really appreciated
>

Did you restart the engine?


>
> Thanks,
> John
>
> ___
> 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] Failed to run VM

[Arik Hadas]

On Sun, Mar 18, 2018 at 3:43 PM, maoz zadok  wrote:

> Hello All,
> I'm receiving this message every time that I try to start VM,
> any idea?
>

Seems you enounter [1] that is solved in 4.2.2.
I assume you're using 4.2.1, right? By just looking at the code, it seems
that restarting the engine could be a possible workaround for this.

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1532884


>
>
>
> 2018-03-18 09:39:51,479-04 ERROR [org.ovirt.engine.core.
> vdsbroker.monitoring.VmsMonitoring] 
> (EE-ManagedThreadFactory-engineScheduled-Thread-11)
> [] Failed during monitoring vm: 2445a47e-b102-11e6-ad11-1866da511add ,
> error is: {}: java.lang.NullPointerException
>
> 2018-03-18 09:39:51,480-04 ERROR [org.ovirt.engine.core.
> vdsbroker.monitoring.VmsMonitoring] 
> (EE-ManagedThreadFactory-engineScheduled-Thread-11)
> [] Exception:: java.lang.NullPointerException
>
> 2018-03-18 09:39:57,802-04 INFO  [org.ovirt.engine.core.bll.RunVmCommand]
> (default task-79) [b3b98e2c-6176-413d-9d75-315626918150] Lock Acquired to
> object 
> 'EngineLock:{exclusiveLocks='[fccee2da-92a3-4187-8aad-d6c1f9d5a3fb=VM]',
> sharedLocks=''}'
> 2018-03-18 09:39:57,822-04 INFO  [org.ovirt.engine.core.vdsbroker.
> IsVmDuringInitiatingVDSCommand] (default task-79)
> [b3b98e2c-6176-413d-9d75-315626918150] START,
> IsVmDuringInitiatingVDSCommand( IsVmDuringInitiatingVDSCommand
> Parameters:{vmId='fccee2da-92a3-4187-8aad-d6c1f9d5a3fb'}), log id:
> 2217c887
> 2018-03-18 09:39:57,822-04 INFO  [org.ovirt.engine.core.vdsbroker.
> IsVmDuringInitiatingVDSCommand] (default task-79)
> [b3b98e2c-6176-413d-9d75-315626918150] FINISH,
> IsVmDuringInitiatingVDSCommand, return: false, log id: 2217c887
> 2018-03-18 09:39:57,927-04 INFO  [org.ovirt.engine.core.bll.RunVmCommand]
> (EE-ManagedThreadFactory-engine-Thread-929544) 
> [b3b98e2c-6176-413d-9d75-315626918150]
> Running command: RunVmCommand internal: false. Entities affected :  ID:
> fccee2da-92a3-4187-8aad-d6c1f9d5a3fb Type: VMAction group RUN_VM with
> role type USER
> 2018-03-18 09:39:57,944-04 INFO  [org.ovirt.engine.core.bll.
> scheduling.policyunits.PreferredHostsWeightPolicyUnit]
> (EE-ManagedThreadFactory-engine-Thread-929544) 
> [b3b98e2c-6176-413d-9d75-315626918150]
> Penalizing host 'kvm5' because it is not preferred.
> 2018-03-18 09:39:57,944-04 INFO  [org.ovirt.engine.core.bll.
> scheduling.policyunits.PreferredHostsWeightPolicyUnit]
> (EE-ManagedThreadFactory-engine-Thread-929544) 
> [b3b98e2c-6176-413d-9d75-315626918150]
> Penalizing host 'kvm6' because it is not preferred.
> 2018-03-18 09:39:57,944-04 INFO  [org.ovirt.engine.core.bll.
> scheduling.policyunits.PreferredHostsWeightPolicyUnit]
> (EE-ManagedThreadFactory-engine-Thread-929544) 
> [b3b98e2c-6176-413d-9d75-315626918150]
> Penalizing host 'kvm7' because it is not preferred.
> 2018-03-18 09:39:57,945-04 WARN  [org.ovirt.engine.core.bll.
> scheduling.pending.PendingResourceManager] 
> (EE-ManagedThreadFactory-engine-Thread-929544)
> [b3b98e2c-6176-413d-9d75-315626918150] Clearing stale pending resource
> org.ovirt.engine.core.bll.scheduling.pending.PendingCpuCores@1d15d667
> (host: e044db3f-c49b-467f-9f04-21b44ffe78c4, vm: fccee2da-92a3-4187-8aad-
> d6c1f9d5a3fb)
> 2018-03-18 09:39:57,945-04 WARN  [org.ovirt.engine.core.bll.
> scheduling.pending.PendingResourceManager] 
> (EE-ManagedThreadFactory-engine-Thread-929544)
> [b3b98e2c-6176-413d-9d75-315626918150] Clearing stale pending resource
> org.ovirt.engine.core.bll.scheduling.pending.PendingMemory@1d15d667
> (host: e044db3f-c49b-467f-9f04-21b44ffe78c4, vm: fccee2da-92a3-4187-8aad-
> d6c1f9d5a3fb)
> 2018-03-18 09:39:57,946-04 WARN  [org.ovirt.engine.core.bll.
> scheduling.pending.PendingResourceManager] 
> (EE-ManagedThreadFactory-engine-Thread-929544)
> [b3b98e2c-6176-413d-9d75-315626918150] Clearing stale pending resource
> org.ovirt.engine.core.bll.scheduling.pending.PendingOvercommitMemory@1d15d667
> (host: e044db3f-c49b-467f-9f04-21b44ffe78c4, vm: fccee2da-92a3-4187-8aad-
> d6c1f9d5a3fb)
> 2018-03-18 09:39:57,946-04 WARN  [org.ovirt.engine.core.bll.
> scheduling.pending.PendingResourceManager] 
> (EE-ManagedThreadFactory-engine-Thread-929544)
> [b3b98e2c-6176-413d-9d75-315626918150] Clearing stale pending resource
> org.ovirt.engine.core.bll.scheduling.pending.PendingVM@1d15d667 (host:
> e044db3f-c49b-467f-9f04-21b44ffe78c4, vm: fccee2da-92a3-4187-8aad-
> d6c1f9d5a3fb)
> 2018-03-18 09:39:57,946-04 ERROR [org.ovirt.engine.core.bll.RunVmCommand]
> (EE-ManagedThreadFactory-engine-Thread-929544) 
> [b3b98e2c-6176-413d-9d75-315626918150]
> Command 'org.ovirt.engine.core.bll.RunVmCommand' failed: null
> 2018-03-18 09:39:57,946-04 ERROR [org.ovirt.engine.core.bll.RunVmCommand]
> (EE-ManagedThreadFactory-engine-Thread-929544) 
> [b3b98e2c-6176-413d-9d75-315626918150]
> Exception: java.lang.NullPointerException
> at org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring.
> refreshCommitedMemory(HostMonitoring.java:687) [vdsbroker.jar:]
> at org.ovirt.engine.core.vdsbr

Re: [ovirt-users] Problem to upgrade level cluster to 4.1

[Arik Hadas]

On Fri, Mar 23, 2018 at 9:09 PM, Marcelo Leandro 
wrote:

> Hello,
>  I am try update the cluster level but i had this menssage erro:
>
> Erro durante a execução da ação: Update of cluster compatibility version
> failed because there are VMs/Templates [VPS-NAME01, VPS-NAME02, VPS-NAME03]
> with incorrect configuration. To fix the issue, please go to each of them,
> edit and press OK. If the save does not pass, fix the dialog validation.
>
>
> 23/03/2018 15:03:07
> Cannot update compatibility version of Vm/Template: [VPS-NAME01], Message:
> [No Message]
> 23/03/2018 15:03:07
> Cannot update compatibility version of Vm/Template: [VPS-NAME02],
> Message: [No Message]
> 23/03/2018 15:03:07
> Cannot update compatibility version of Vm/Template: [VPS-NAME03],
> Message: [No Message]
>
>
> I am already open the edit box vm and close with ok button how show in the
> erro menssagem:
> To fix the issue, please go to each of them, edit and press OK. If the
> save does not pass, fix the dialog validation.
>
> But not return error when save.
>
> Anyone can help me ?
>

Can you please share the engine.log?


>
> ___
> 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 remove VM

[Arik Hadas]

On Wed, Mar 21, 2018 at 11:54 AM, Angel R. Gonzalez 
wrote:

> Hi,
>
> I can't edit/remove/modify a VM. Always show a message:
> "Cannot remove VM. Related operation is currently in progress. Please
> try again later"
>

That means that the VM is locked using an in-memory lock (rather than in
the database, so the script for unlocking entities would not help here).
The message you get was deprecated, when a lock is taken before executing a
long operation we generate a more informative message.
So that is almost certainly caused by a bug, we have fixed various bugs
that could have lead to that.
What version of oVirt do you use? Could you share the engine.log that
covers the latest operation that was made on this VM?
Anyway, restarting the engine would most probably release the lock of that
VM and allow removing it.


>
> I also used REST API
> curl -k -u admin@internal:passwd -X DELETE https://engine/ovirt-engine/ap
> i/vms/
> and the output message is the same.
>

Yeah, it doesn't matter what client you use since this error is generated
on the back-end side.


>
> How to can execute actions over the VM, or how to remove it from Cluster?
>
> Thanks in advance.
>
> Ángel González.
> ___
> 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] Fwd: Can't add/remove usb device to VM

[Arik Hadas]

On Mon, Feb 12, 2018 at 6:57 PM, Jon bae  wrote:

> A little update:
> I found out that I have to activate *Hostdev Passthrough* (is this really
> necessary for USB devices?). Now I see all the devices and I can add also
> an USB device.
>

Theoretically, no, it is not needed.
Practically, it is needed in previous versions of 4.2 due to a bug that
would be solved in the upcoming version of 4.2 [1].


> But I'm still not able to disconnect the USB from the old VM.
>

Yep, that's another bug that would be solved in the upcoming version of 4.2
[2].

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1548344
[2] https://bugzilla.redhat.com/show_bug.cgi?id=155


>
> -- Forwarded message --
> From: Jon bae 
> Date: 2018-02-12 16:14 GMT+01:00
> Subject: Can't add/remove usb device to VM
> To: users 
>
>
> Hello,
> I run oVirt 4.2.1, in 4.1 I added a USB device to a VM and now I wanted to
> change this device to a different VM.
> But I found out, that I'm not able to remove this device nor I'm able to
> add any device to any VM. The device list is empty.
>
> I found a bug report, what describe this error:
> https://bugzilla.redhat.com/show_bug.cgi?id=1531847
>
> Is there a solution for that?
>
> The USB device is a hardware dongle and it is very impotent for us to
> change this.
>

> Any workaround is welcome!
>

If you can't wait for the upcoming version of 4.2 you can try removing it
manually by manipulating the database (assuming there is only one host
device attached to the VM):

(1) delete from vm_device where vm_id in (select vm_guid from vm_static
where vm_name='') and type='hostdev';
(2) update host_device set vm_id = NULL where vm_id in (select vm_guid from
vm_static where vm_name='');


>
> Regards
>
> Jonathan
>
>
> ___
> 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] Problem to upgrade level cluster to 4.1

[Arik Hadas]

On Sun, Mar 25, 2018 at 3:06 PM, Marcelo Leandro 
wrote:

> Good morning,
> follow the log:
>
>  The real name of vms :
> VPS-Jarauto
> VPS-Jarauto-Firewall
> VPS-Varejo-Mais
>
> Thanks,
>

Thanks for sharing the log.

Two of these VMs are configured with the custom-property 'macspoof'. That
property is not supposed to be used since 4.0 (IIRC).
Nevertheless, defining this property for version 4.1 should solve this
problem, see [1].

The third VM is in a weird state - it cannot be updated because the host it
runs on doesn't support the number of CPUs defined for this VM.
You can either shut this VM down during the cluster upgrade or try to
migrate it to another host with more CPUs available.

Unfortunately, I can't correlate those issues with the VMs you mentioned,
but if you'll start with with the first issue you'll find which one
of them is that 'third VM'.

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1373573


>
> 2018-03-25 3:29 GMT-03:00 Arik Hadas :
>
>>
>>
>> On Fri, Mar 23, 2018 at 9:09 PM, Marcelo Leandro 
>> wrote:
>>
>>> Hello,
>>>  I am try update the cluster level but i had this menssage erro:
>>>
>>> Erro durante a execução da ação: Update of cluster compatibility version
>>> failed because there are VMs/Templates [VPS-NAME01, VPS-NAME02,
>>> VPS-NAME03] with incorrect configuration. To fix the issue, please go
>>> to each of them, edit and press OK. If the save does not pass, fix the
>>> dialog validation.
>>>
>>>
>>> 23/03/2018 15:03:07
>>> Cannot update compatibility version of Vm/Template: [VPS-NAME01],
>>> Message: [No Message]
>>> 23/03/2018 15:03:07
>>> Cannot update compatibility version of Vm/Template: [VPS-NAME02],
>>> Message: [No Message]
>>> 23/03/2018 15:03:07
>>> Cannot update compatibility version of Vm/Template: [VPS-NAME03],
>>> Message: [No Message]
>>>
>>>
>>> I am already open the edit box vm and close with ok button how show in
>>> the erro menssagem:
>>> To fix the issue, please go to each of them, edit and press OK. If the
>>> save does not pass, fix the dialog validation.
>>>
>>> But not return error when save.
>>>
>>> Anyone can help me ?
>>>
>>
>> Can you please share the engine.log?
>>
>>
>>>
>>> ___
>>> 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] Issue adding network interface to VM failed with HotPlugNicVDS

[Arik Hadas]

On Fri, Mar 30, 2018 at 10:06 PM, Oliver Riesener <
oliver.riese...@hs-bremen.de> wrote:

> Hi,
>
> running ovirt 4.2.2-6 with firewalld enabled.
>
> Failed to HotPlugNicVDS, error = The name org.fedoraproject.FirewallD1 was
> not provided by any .service files, code = 49
>

I have seen this error when trying to run a VM after starting/stoping
firewalld without restarting libvirtd.
Try restarting libvirtd.


>
> Can’t hot plug any new network interfaces.
>
> 30d6c2ab', vmId='20abce62-a558-4aee-b3e3-3fa70f1d1918'}',
> device='bridge', type='INTERFACE', specParams='[inbound={}, outbound={}]',
> address='', managed='true', plugged='true', readOnly='false',
> deviceAlias='', customProperties='[]', snapshotId='null',
> logicalName='null', hostDevice='null'}'})' execution failed:
> VDSGenericException: VDSErrorException: Failed to HotPlugNicVDS, error =
> The name org.fedoraproject.FirewallD1 was not provided by any .service
> files, code = 49
> 2018-03-30 20:56:08,620+02 INFO  [org.ovirt.engine.core.
> vdsbroker.vdsbroker.HotPlugNicVDSCommand] (default task-106) [e732710]
> FINISH, HotPlugNicVDSCommand, log id: 210cb07
> 2018-03-30 20:56:08,620+02 ERROR [org.ovirt.engine.core.bll.network.vm.
> ActivateDeactivateVmNicCommand] (default task-106) [e732710] Command
> 'org.ovirt.engine.core.bll.network.vm.ActivateDeactivateVmNicCommand'
> failed: EngineException: 
> org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException:
> VDSGenericException: VDSErrorException: Failed to HotPlugNicVDS, error =
> The name org.fedoraproject.FirewallD1 was not provided by any .service
> files, code = 49 (Failed with error ACTIVATE_NIC_FAILED and code 49)
> 2018-03-30 20:56:08,627+02 ERROR [org.ovirt.engine.core.dal.
> dbbroker.auditloghandling.AuditLogDirector] (default task-106) [e732710]
> EVENT_ID: NETWORK_ACTIVATE_VM_INTERFACE_FAILURE(1,013), Failed to plug
> Network Interface nic3 (VirtIO) to VM v-srv-opt. (User: admin@internal)
> 2018-03-30 20:56:08,629+02 INFO  
> [org.ovirt.engine.core.bll.CommandCompensator]
> (default task-106) [e732710] Command 
> [id=0db21508-1eeb-40f5-912e-58af9bb3fa9b]:
> Compensating NEW_ENTITY_ID of 
> org.ovirt.engine.core.common.businessentities.VmDevice;
> snapshot: VmDeviceId:{deviceId='6d7a5b68-0eb3-4531-bc06-3aff30d6c2ab',
> vmId='20abce62-a558-4aee-b3e3-3fa70f1d1918'}.
> 2018-03-30 20:56:08,630+02 INFO  
> [org.ovirt.engine.core.bll.CommandCompensator]
> (default task-106) [e732710] Command 
> [id=0db21508-1eeb-40f5-912e-58af9bb3fa9b]:
> Compensating NEW_ENTITY_ID of org.ovirt.engine.core.common.
> businessentities.network.VmNetworkStatistics; snapshot:
> 6d7a5b68-0eb3-4531-bc06-3aff30d6c2ab.
> 2018-03-30 20:56:08,631+02 INFO  
> [org.ovirt.engine.core.bll.CommandCompensator]
> (default task-106) [e732710] Command 
> [id=0db21508-1eeb-40f5-912e-58af9bb3fa9b]:
> Compensating NEW_ENTITY_ID of org.ovirt.engine.core.common.
> businessentities.network.VmNetworkInterface; snapshot:
> 6d7a5b68-0eb3-4531-bc06-3aff30d6c2ab.
> 2018-03-30 20:56:08,638+02 INFO  
> [org.ovirt.engine.core.bll.CommandCompensator]
> (default task-106) [e732710] Command 
> [id=0db21508-1eeb-40f5-912e-58af9bb3fa9b]:
> Compensating DELETED_OR_UPDATED_ENTITY of 
> org.ovirt.engine.core.common.businessentities.VmStatic;
> snapshot: id=20abce62-a558-4aee-b3e3-3fa70f1d1918.
> 2018-03-30 20:56:08,642+02 INFO  
> [org.ovirt.engine.core.bll.CommandCompensator]
> (default task-106) [e732710] Command 
> [id=0db21508-1eeb-40f5-912e-58af9bb3fa9b]:
> Compensating TRANSIENT_ENTITY of org.ovirt.engine.core.common.
> businessentities.ReleaseMacsTransientCompensation; snapshot:
> org.ovirt.engine.core.common.businessentities.
> ReleaseMacsTransientCompensation@581c941c.
> 2018-03-30 20:56:08,720+02 ERROR [org.ovirt.engine.core.dal.
> dbbroker.auditloghandling.AuditLogDirector] (default task-106) [e732710]
> EVENT_ID: NETWORK_ADD_VM_INTERFACE_FAILED(933), Failed to add Interface
> nic3 (VirtIO) to VM v-srv-opt. (User: admin@internal)
> ___
> 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] Is compatibility level change required for upgrading from 4.0 to 4.2?

[Arik Hadas]

On Fri, Apr 6, 2018 at 12:28 PM, Luca 'remix_tj' Lorenzetto <
lorenzetto.l...@gmail.com> wrote:

> On Fri, Apr 6, 2018 at 11:05 AM, Michal Skrivanek
>  wrote:
> >
> > you just need to keep the supported versions in mind. Version 4.2
> supports
> > Cluster levels 3.6, 4.0, 4.1(same as version 4.1) - so any of them is ok
> >
>
> Perfect, thank you for the confirmation.
>
> To change the compatibility level of DC, i've seen that all clusters
> require has to be upgraded.
> Does the upgrade of the DC requires the restart of all the VMs to have
> the cluster completely upgraded or restarting the VMs is an activity
> indipendent from this?
>

You won't have to restart the running VMs.
You'll see that VMs that were running at the time of the cluster upgrade
are set with custom-compatibility-version that matches the previous
compatibilty-level of the cluster. So obviously, VM-specific features that
were added in 4.2 won't be applicable to those VMs until they are restarted
(and then their custom-compatibility version is cleared so their effective
compability-level would change to 4.2).
But even when some VMs are set with custom-compatibility-version, the
cluster is upgraded and so it should be possible to upgrade the DC.


>
> Luca
>
>
>
> --
> "E' assurdo impiegare gli uomini di intelligenza eccellente per fare
> calcoli che potrebbero essere affidati a chiunque se si usassero delle
> macchine"
> Gottfried Wilhelm von Leibnitz, Filosofo e Matematico (1646-1716)
>
> "Internet è la più grande biblioteca del mondo.
> Ma il problema è che i libri sono tutti sparsi sul pavimento"
> John Allen Paulos, Matematico (1945-vivente)
>
> Luca 'remix_tj' Lorenzetto, http://www.remixtj.net , <
> lorenzetto.l...@gmail.com>
> ___
> 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] ?==?utf-8?q? vdsClient is removed and replaced by vdsm-client

[Arik Hadas]

On Fri, Apr 13, 2018 at 11:14 AM, fsoyer  wrote:

> Hi all,
> I can't find any exhaustive doc for new vdsm-client. My problem actually
> is a task (export a vm to OVA) blocked.
>

I'm afraid you won't find any task in VDSM for 'export a VM to OVA'.
Expoting a VM to OVA is comprised of three steps:
1. Creating temporary cloned disks - you'll find a task of copy-image-group
for each disk.
2. Creating the OVA file - that's done by a python script executed by
ansible, there is no task for that in VDSM.
3. Removing the temporary cloned disks - you'll find a task of remove-image
for each disk.

Can you please elaborate on the problem you're having - where do you see
that task and how can you see that it's blocked?


> I found that I can interact with
> vdsm-client Task getInfo taskID=, and replace getInfo by "stop", BUT
> : how can I find this UUID ???
> Old "vdsClient -s 0 getAllTasksStatuses" has no equivalent ??
>
> Does someone knows if a complete doc exists dot vdsm-client ?
> Thanks
> Frank
>
>
>
>
>
> Le Mercredi, Janvier 25, 2017 12:30 CET, Irit Goihman 
> a écrit:
>
>
> Hi All,
>
> vdsClient will be removed from master branch today.
> It is using XMLRPC protocol which has been deprecated and replaced by
> JSON-RPC.
>
> A new client for vdsm was introduced in 4.1: vdsm-client.
> This is a simple client that uses JSON-RPC protocol which was introduced
> in ovirt 3.5.
>
> The client is not aware of the available methods and parameters, and you
> should consult
> the schema [1] in order to construct the desired command.
>
> Future version should parse the schema and provide online help.
>
>
> If you're using vdsClient, we will be happy to assist you in migrating to
> the new vdsm client.
>
>
>
> *vdsm-client usage:*
>
> vdsm-client [-h] [-a ADDRESS] [-p PORT] [--unsecure] [--timeout TIMEOUT]
>[-f FILE] namespace method [name=value [name=value] ...]
>
>
> Invoking simple methods:
>
> # vdsm-client Host getVMList
> ['b3f6fa00-b315-4ad4-8108-f73da817b5c5']
>
> For invoking methods with many or complex parameters, you can read
> the parameters from a JSON format file:
>
> # vdsm-client Lease info -f lease.json
>
> where lease.json file content is:
>
> {
>
>   "lease": {
>
>   "sd_id": "75ab40e3-06b1-4a54-a825-2df7a40b93b2",
>
>   "lease_id": "b3f6fa00-b315-4ad4-8108-f73da817b5c5"
>
>   }
>
>   }
>
> It is also possible to read parameters from standard input, creating
> complex parameters interactively:
>
> # cat <
>  {
>
>  "lease": {
>
>  "sd_id": "75ab40e3-06b1-4a54-a825-2df7a40b93b2",
>
>  "lease_id": "b3f6fa00-b315-4ad4-8108-f73da817b5c5"
>
>  }
>
>  }
>
> EOF
>
>
> *Constructing a command from vdsm schema:*
>
> Let's take VM.getStats as an example.
> This is the entry in the schema:
>
> VM.getStats:
>
> added: '3.1'
>
> description: Get statistics about a running virtual machine.
>
> params:
>
> -   description: The UUID of the VM
>
> name: vmID
>
> type: *UUID
>
> return:
>
> description: An array containing a single VmStats record
>
> type:
>
> - *VmStats
>
>
> namespace: VM
> method name: getStats
> params: vmID
>
> The vdsm-client command is:
>
> # vdsm-client VM getStats vmID=b3f6fa00-b315-4ad4-8108-f73da817b5c5
>
>
> *Invoking getVdsCaps command:*
>
> # vdsm-client Host getCapabilities
>
>
>
> Please consult vdsm-client help and man page for further details and
> options.
>
>
>
> [1] https://github.com/oVirt/vdsm/blob/master/lib/api/vdsm-api.yml
>
> --
> Irit Goihman
> Software Engineer
> Red Hat Israel Ltd.
>
>
>
>
> ___
> 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] ?= vdsClient is removed and replaced by vdsm-clien

[Arik Hadas]

On Fri, Apr 13, 2018 at 6:54 PM, fsoyer  wrote:

> Hi,
> This task is listed (since 2 days) in the GUI / up right "tasks" icon. It
> is visibly freezed as no OVA file has been created, but no errors in GUI,
> just... it runs. Or : it loops :)
> This (test) vm is one on which I have extended the disk (50 -> 100G).
> Before being stopped and trying to export it to OVA, it works fine. All
> other vms around can be well exported but not this one. I've tried to
> restart engine, change SPM, restart one by one each node, but the task is
> always here. I could even restart the vm today without error and it works
> fine ! But... the task runs...
> Today also, I tried to clone the vm : same thing, now I have 2 tasks
> running indefinitly :(


> Strange bug, where no timeout stopped the tasks in error. I can't see any
> revelant things in engine.log or vdsm.log, but probably I've not seen them
> in all the messages.
> No problem to remove this (test) vm and try on another (test) one (extend
> disk to see if this is the reason of the problem). But before I want to
> kill this tasks !
>

Please don't remove that VM yet.
It would be appreciated if you could file a bug and share the engine log
that covers the attempt to export this VM to OVA + the ansible log of that
operation.


>
> Thanks.
> Frank
>
>
>
> Le Vendredi, Avril 13, 2018 16:24 CEST, Arik Hadas  a
> écrit:
>
>
>
>
> On Fri, Apr 13, 2018 at 11:14 AM, fsoyer  wrote:
>>
>> Hi all,
>> I can't find any exhaustive doc for new vdsm-client. My problem actually
>> is a task (export a vm to OVA) blocked.
>
>
> I'm afraid you won't find any task in VDSM for 'export a VM to OVA'.
> Expoting a VM to OVA is comprised of three steps:
> 1. Creating temporary cloned disks - you'll find a task of
> copy-image-group for each disk.
> 2. Creating the OVA file - that's done by a python script executed by
> ansible, there is no task for that in VDSM.
> 3. Removing the temporary cloned disks - you'll find a task of
> remove-image for each disk.
>
> Can you please elaborate on the problem you're having - where do you see
> that task and how can you see that it's blocked?
>
>
>> I found that I can interact with
>> vdsm-client Task getInfo taskID=, and replace getInfo by "stop",
>> BUT : how can I find this UUID ???
>> Old "vdsClient -s 0 getAllTasksStatuses" has no equivalent ??
>>
>> Does someone knows if a complete doc exists dot vdsm-client ?
>> Thanks
>> Frank
>>
>>
>>
>>
>>
>> Le Mercredi, Janvier 25, 2017 12:30 CET, Irit Goihman <
>> igoih...@redhat.com> a écrit:
>>
>>
>> Hi All,
>>
>> vdsClient will be removed from master branch today.
>> It is using XMLRPC protocol which has been deprecated and replaced by
>> JSON-RPC.
>>
>> A new client for vdsm was introduced in 4.1: vdsm-client.
>> This is a simple client that uses JSON-RPC protocol which was introduced
>> in ovirt 3.5.
>>
>> The client is not aware of the available methods and parameters, and you
>> should consult
>> the schema [1] in order to construct the desired command.
>>
>> Future version should parse the schema and provide online help.
>>
>>
>> If you're using vdsClient, we will be happy to assist you in migrating to
>> the new vdsm client.
>>
>>
>>
>> *vdsm-client usage:*
>>
>> vdsm-client [-h] [-a ADDRESS] [-p PORT] [--unsecure] [--timeout TIMEOUT]
>>[-f FILE] namespace method [name=value [name=value]
>> ...]
>>
>>
>> Invoking simple methods:
>>
>> # vdsm-client Host getVMList
>> ['b3f6fa00-b315-4ad4-8108-f73da817b5c5']
>>
>> For invoking methods with many or complex parameters, you can read
>> the parameters from a JSON format file:
>>
>> # vdsm-client Lease info -f lease.json
>>
>> where lease.json file content is:
>>
>> {
>>
>>   "lease": {
>>
>>   "sd_id": "75ab40e3-06b1-4a54-a825-2df7a40b93b2",
>>
>>   "lease_id": "b3f6fa00-b315-4ad4-8108-f73da817b5c5"
>>
>>   }
>>
>>   }
>>
>> It is also possible to read parameters from standard input, creating
>> complex parameters interactively:
>>
>> # cat <>
>>  {
>>
>>  "lease": {
>>
>>  "sd_id": "75ab40e3-06b1-4a54-a825-2df7a40b93b2",
>>
&g