[ovirt-users] Re: Q35: disk type view not consistent in edit vm and new disk pages

2021-02-24 Thread Arik Hadas
On Fri, Feb 19, 2021 at 11:55 AM Gianluca Cecchi 
wrote:

> Hello,
> if I create a VM and select Q35 machine type, still the General --> create
> image option in edit phase doesn't show sata as an option.
> Even if I create the VM without disks and then go to edit General -->
> create, I only see IDE, VirtIO-SCSI and VirtIO.
> Instead if I click VM name, DIsks --> New, I can select VirtIO-SCSI,
> VirtIO and SATA
> After the first disk (SATA in my case) has been created, now if I go and
> edit VM --> General --> Instance Images + --> Create, I see consistent
> options.
>
> I think GUI experience could be improved.
>

Definitely, the lists should be the same and include [sata, virtio,
virtio-scsi], we have a bug on that:
https://bugzilla.redhat.com/show_bug.cgi?id=1925079


> Also because I can reproduce this workflow converging to an error (even if
> IDE disks are not so common nowadays...):
> New VM
> In  general I create an IDE disk
> In System I select in Advanced parameters, Custom Chipset/Firmware Type
> Q35 (EFI or BIOS based)
> go ahead
>
> At the final OK I get the error:
>
> Cannot add Virtual Disk: The disk interface is not supported by the VM OS:
> Other OS.
>
> The result is VM created but without the IDE disk as not supported in Q35
> type.
>

I have only virtio and virtio-scsi in the list of interfaces so it's not
trivial for me to reproduce so can you please file a bug and attach the
engine.log - I wonder how come that the whole add-vm operation didn't fail
because of that.


>
> Tested in 4.4.4
> Gianluca
> ___
> 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/WRRI7FD2RTSLBR5KHIX6JNVEPTCOFJED/
>
___
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/CQVC4SMAYCNUABLIK7FJPWTD6JU6ICLE/


[ovirt-users] Re: Cannot add VM. Maximum number of threads per cpu exceeded

2021-02-23 Thread Arik Hadas
On Tue, Feb 23, 2021 at 4:10 PM Lavi.Buchnik--- via Users 
wrote:

> Hi,
>
> We have a strange thing, which not clear to us.
> When provisioning a new VM via REST API, if the number of vCPU for that VM
> is more than 16, I'm getting this error:
>
> Fault reason is "Operation Failed". Fault detail is "[Cannot add VM.
> Maximum number of threads per cpu exceeded]". HTTP response code is 409.
>
> Our version is: Version 4.3.6.6-1.0.9.el7
>
> Note that manual provisioning from the UI do not produce any error when
> using vCPU > 16.
> It seems like the issue is related to this setting (from the engine):
>
> [root@olvmengine01 ~]# engine-config -g MaxNumOfThreadsPerCpu
> MaxNumOfThreadsPerCpu: 8 version: 4.1
> MaxNumOfThreadsPerCpu: 8 version: 4.2
> MaxNumOfThreadsPerCpu: 8 version: 4.3
> [root@olvmengine01 ~]#
>
> But when trying to set it to another number, I'm always get this error,
> for example:
>
> [root@olvmengine01 ~]# engine-config -s MaxNumOfThreadsPerCpu=10
> Please select a version:
> 1. 4.1
> 2. 4.2
> 3. 4.3
> 3
> Cannot set value 10 to key MaxNumOfThreadsPerCpu.
>
> Questions:
> 1. Can you please explain why we getting this error: "Cannot add VM.
> Maximum number of threads per cpu exceeded"?
>

You've specified a value for threads-per-core that exceeds the
MaxNumOfThreadsPerCpu limit.

2. Is it related to engine-config -g MaxNumOfThreadsPerCpu?
>

Yes


> 3. Why it is working manually via the UI?
>

The UI sets the CPU topology for you when you specify the number of vCPUs
(for 16, it produces #sockets = 16, #cores=1, #threads=1).


> 4. if its related to engine-config, why we can't set it to another number?
>

You can change the values that engine-config accepts for
MaxNumOfThreadsPerCpu by changing MaxNumOfThreadsPerCpu.validValues in
/etc/ovirt-engine/engine-config/engine-config.properties but I think it
would be better to specify a better CPU topology in the request..


>
> Thanks in advance,
> Lavi
> ___
> 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/CRKRVCWPUIN6HGU4OBTAC7Z4TNUACP6U/
>
___
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/PUAMEB76VRCTAPAM2FRJ6T2LZVBTEQY5/


[ovirt-users] Re: VM stuck in reboot

2021-02-14 Thread Arik Hadas
On Fri, Feb 12, 2021 at 7:51 PM Michael Schmid 
wrote:

> Arik,
>
> Thank you so much, that solved it.
>
> that was my updates/maintenance weekend, so I would have probably updated
> the cluster at the same time. I'm not sure of the order I was trying to go
> home.
>
> I am so sorry I didn't find the previous post before asking
>
> Thank you again
>
I'm glad to see it helped :)
I tried to reproduce it by invoking shutdown and reboot simultaneously but
it didn't happen to me with 4.4.4 so I tend to think you've encountered
https://bugzilla.redhat.com/show_bug.cgi?id=1880251 with the previous
version. If it happens again, please let us know.

> Mike
>
> On 2/12/2021 11:52 AM, Arik Hadas wrote:
>
>
>
> On Fri, Feb 12, 2021 at 4:44 PM Michael Schmid 
> wrote:
>
>> Hi All,
>>
>> I am running on 4.4.4.7-1.el8
>>
>> I messed up. I was doing some weekend maintenance on VMs and some VMs
>> needed to be stopped and some rebooted and I stopped one, thought I
>> clicked on the next one and clicked shutdown. But... I clicked reboot
>> and shutdown on the same VM, now it is stuck. The Overview in the engine
>> shows the VM "Reboot In Progress" and it has for two weeks at this
>> point, it was a fresh VM so I just created a new one until I had this
>> figured out, but here I am. Clicking "Shutdown" does nothing but
>> generate an error, same with "Power Off" the error I get is
>>
>> ---
>>
>> 2021-02-10 12:04:03,460-05 INFO
>> [org.ovirt.engine.core.bll.StopVmCommand]
>> (EE-ManagedThreadFactory-engine-Thread-244169)
>> [c3ce0a41-3f53-4f3e-993f-0d75f62cc8e6] Running command: StopVmCommand
>> internal: false. Entities affected :  ID:
>> d4e90edd-0598-4ac1-b814-2cae8d29e216 Type: VMAction group STOP_VM with
>> role type USER
>> 2021-02-10 12:04:03,464-05 WARN
>> [org.ovirt.engine.core.bll.StopVmCommand]
>> (EE-ManagedThreadFactory-engine-Thread-244169)
>> [c3ce0a41-3f53-4f3e-993f-0d75f62cc8e6] Strange, according to the status
>> 'RebootInProgress' virtual machine
>> 'd4e90edd-0598-4ac1-b814-2cae8d29e216' should be running in a host but
>> it isn't.
>> 2021-02-10 12:04:03,485-05 ERROR
>> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
>> (EE-ManagedThreadFactory-engine-Thread-244169)
>> [c3ce0a41-3f53-4f3e-993f-0d75f62cc8e6] EVENT_ID:
>> USER_FAILED_STOP_VM(56), Failed to power off VM snipeit
>>
>> ---
>>
>> I have shut down the entire system. all VMs the hosts, the engine, and
>> nothing changes. still stuck in reboot in progress
>>
>> I would greatly appreciate any help
>>
>
> You'll need to make a change in the database, see [1].
>
> This really shouldn't happen with 4.4.4.7 though.
> You say the VM is in this state for two weeks, right? Can it be that it
> got to that state before you've upgraded to 4.4.4?
>
> [1] https://www.mail-archive.com/users@ovirt.org/msg62928.html
>
>
>>
>> Thanks
>>
>> Mike
>>
>>
>> ___
>> 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/IQ2YNJSNWANRUFIJHC5O2JD63M7FSBEW/
>>
>
___
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/PZPRTQXHU4WAZSWKXHMFCUYVUOGFNACG/


[ovirt-users] Re: VM stuck in reboot

2021-02-12 Thread Arik Hadas
On Fri, Feb 12, 2021 at 4:44 PM Michael Schmid 
wrote:

> Hi All,
>
> I am running on 4.4.4.7-1.el8
>
> I messed up. I was doing some weekend maintenance on VMs and some VMs
> needed to be stopped and some rebooted and I stopped one, thought I
> clicked on the next one and clicked shutdown. But... I clicked reboot
> and shutdown on the same VM, now it is stuck. The Overview in the engine
> shows the VM "Reboot In Progress" and it has for two weeks at this
> point, it was a fresh VM so I just created a new one until I had this
> figured out, but here I am. Clicking "Shutdown" does nothing but
> generate an error, same with "Power Off" the error I get is
>
> ---
>
> 2021-02-10 12:04:03,460-05 INFO
> [org.ovirt.engine.core.bll.StopVmCommand]
> (EE-ManagedThreadFactory-engine-Thread-244169)
> [c3ce0a41-3f53-4f3e-993f-0d75f62cc8e6] Running command: StopVmCommand
> internal: false. Entities affected :  ID:
> d4e90edd-0598-4ac1-b814-2cae8d29e216 Type: VMAction group STOP_VM with
> role type USER
> 2021-02-10 12:04:03,464-05 WARN
> [org.ovirt.engine.core.bll.StopVmCommand]
> (EE-ManagedThreadFactory-engine-Thread-244169)
> [c3ce0a41-3f53-4f3e-993f-0d75f62cc8e6] Strange, according to the status
> 'RebootInProgress' virtual machine
> 'd4e90edd-0598-4ac1-b814-2cae8d29e216' should be running in a host but
> it isn't.
> 2021-02-10 12:04:03,485-05 ERROR
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (EE-ManagedThreadFactory-engine-Thread-244169)
> [c3ce0a41-3f53-4f3e-993f-0d75f62cc8e6] EVENT_ID:
> USER_FAILED_STOP_VM(56), Failed to power off VM snipeit
>
> ---
>
> I have shut down the entire system. all VMs the hosts, the engine, and
> nothing changes. still stuck in reboot in progress
>
> I would greatly appreciate any help
>

You'll need to make a change in the database, see [1].

This really shouldn't happen with 4.4.4.7 though.
You say the VM is in this state for two weeks, right? Can it be that it got
to that state before you've upgraded to 4.4.4?

[1] https://www.mail-archive.com/users@ovirt.org/msg62928.html


>
> Thanks
>
> Mike
>
>
> ___
> 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/IQ2YNJSNWANRUFIJHC5O2JD63M7FSBEW/
>
___
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/3JOSMTLBZVMSOXCGMK4NCVKXEVQFQLKH/


[ovirt-users] Re: uploading ang .OVA image

2021-02-04 Thread Arik Hadas
On Thu, Feb 4, 2021 at 3:49 PM Gianluca Cecchi 
wrote:

> On Thu, Feb 4, 2021 at 2:12 PM Ariez Ahito 
> wrote:
>
>> hi guys, i just want to ask if you can just upload an .OVA file to ovirt
>> just like uploading ISO?
>> without setting up virt-v2v and export domain?
>>
> thanks
>>
>>
> Put the OVA file on one of your hypervisors in a certain path
> Go to Web Admin Gui --> Compute --> Virtual Machines
> Select the three vertical dots at top right (near the "Migrate" button)
> and "Import"
> Select "Virtual Appliance (OVA)" as source and choose the host and File
> Path where you previously put the OVA
> select the VMs to import using the horizontal arrows
>
> In theory it should be supported oVirt as internal format and only vSphere
> as external format of OVA.
> But as far as your OVA complies with what oVirt expects, it could work
> too.
>

Yeah.
I'd say that with vSphere-compliant OVAs one needs to do the above
mentioned steps because we have to invoke virt-v2v (btw, there's no need
for an export domain).
But if you have an OVA that was produced by oVirt at hand, you can
alternatively upload it as the following script does:
https://github.com/oVirt/ovirt-engine-sdk/blob/master/sdk/examples/upload_ova_as_vm_or_template.py


>
> Gianluca
>
>
> ___
> 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/IUA6QJGTZYHVAHIDUBEEGCTHCIR3CI2R/
>
___
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/7SD2ARW5IAWHIO47QHUIVCT3CSAEKBXK/


[ovirt-users] Re: Achieving high availability

2021-02-02 Thread Arik Hadas
On Tue, Feb 2, 2021 at 1:57 PM Vojtech Juranek  wrote:

> On Tuesday, 2 February 2021 11:37:01 CET Andrea Chierici wrote:
> > Hi,
> > I am trying to configure high availability on a critical VM. My ovirt
> > version is 4.3.10.4-1.el7.
> > My question is about the best settings to specify, since it's not
> > completely clear to me how they influence the availability.
> >
> > What I want is simply to have a specific machine ALWAYS running, or at
> > least, to be available as much as possible. I have no special
> > requirements on the VM, if it goes down, simply restarting it is fine.
> >
> > Here is my current setting. Is it good or I'd better chage anything?
>
> you may want to configure VM lease. If you don't do so, in case of split
> brain, there can be two VMs running and accessing the same storage,
> leading to
> the data corruption. With VM leases this cannot happen - only one VM can
> access the storage. To speed up the switch, you may want to configure also
> watchdog. But there can be use cases (e.g. stateless server which just
> forwards received packet somewhere) where leases are not needed or not
> using
> them won't cause any harm. See [1] for more details.
>
> [1] https://www.ovirt.org/develop/ha-vms.html


Indeed, configuring a VM lease and a watchdog device can be useful.
Not only that a VM lease can generally prevent split brains but in case the
host that the VM runs on becomes non-responsive, the system would
automatically try to restart the VM elsewhere (otherwise, the system waits
for a confirmation from the admin that the host is down which can take
time, and yes, if the VM still runs on the non-responsive host can lead to
a split-brain).
The watchdog device identifies problems from within the guest that are
otherwise hard to identify from outside of the virtual machine. Richard
Jones wrote a nice post about the watchdog device few years ago [2]

[2] https://rwmj.wordpress.com/2010/03/03/what-is-a-watchdog/


>
>
> >
> >
> > Thanks,
> > Andrea
>
> ___
> 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/IYHLDVK7UNFBHAT7ZQ3J7LIJSS24AZ5B/
>
___
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/7BD7LJVNUX2EGUHLDMQ4ZANAOI5AVAMI/


[ovirt-users] Re: Hosted Engine stuck in bios

2021-01-22 Thread Arik Hadas
On Thu, Jan 21, 2021 at 9:27 PM Joseph Gelinas  wrote:

> I found `engine-setup
> --otopi-environment=OVESETUP_CONFIG/continueSetupOnHEVM=bool:True` from [1]
> and now have the ovirt-engine web interface reachable again. But do have
> one more question; when I try to change the Custom Chipset/Firmware Type to
> Q35 Chipset with BIOS, I get the error; HostedEngine: There was an attempt
> to change the Hosted Engine VM values that are locked.
>
> How do I make the removal of the loader/nvram lines permanent?
>

Can you please check the output of:
select custom_bios_type from vm_static where origin=6;

If it returns 0 then you can change the custom bios type to Q35 + BIOS with:
update vm_static set custom_bios_type = 2,  db_generation = db_generation +
1 where origin = 6;

If it returns 2 as it is supposed to, you can change any field of the
hosted engine VM (e.g., "comment") via the UI to trigger an update of the
OVF_STORE.



>
> [1]
> https://lists.ovirt.org/archives/list/users@ovirt.org/thread/2AC57LTHFKJBU6OYZPYSCMTBF6NE3QO2/
>
> > On Jan 21, 2021, at 10:15, Joseph Gelinas  wrote:
> >
> > Removing those two lines got the hosted engine vm booting again, so that
> is a great help. Thank you.
> >
> > Now I just need the web interface of ovirt-engine to work again. I feel
> like I might have run things out of order and forgot to do `engine-setup`
> as part of the update of hosted engine. Though when I try to do that now it
> bails out claiming the cluster isn't in global maintenance yet it is.
> >
> > [ INFO  ] Stage: Setup validation
> > [ ERROR ] It seems that you are running your engine inside of the
> hosted-engine VM and are not in "Global Maintenance" mode.
> > In that case you should put the system into the "Global
> Maintenance" mode before running engine-setup, or the hosted-engine HA
> agent might kill the machine, which might corrupt your data.
> >
> > [ ERROR ] Failed to execute stage 'Setup validation': Hosted Engine
> setup detected, but Global Maintenance is not set.
> >
> >
> > I see engine.log says it can't contact the database but I certainly see
> Postgres processes running.
> >
> > /var/log/ovirt-engine/engine.log
> >
> > 2021-01-21 14:47:31,502Z ERROR
> [org.ovirt.engine.core.services.HealthStatus] (default task-15) [] Failed
> to run Health Status.
> > 2021-01-21 14:47:31,502Z ERROR
> [org.ovirt.engine.core.services.HealthStatus] (default task-14) [] Unable
> to contact Database!: java.lang.InterruptedException
> >
> >
> >
> >
> >> On Jan 21, 2021, at 03:19, Arik Hadas  wrote:
> >>
> >>
> >>
> >> On Thu, Jan 21, 2021 at 8:57 AM Joseph Gelinas 
> wrote:
> >> Hi,
> >>
> >> I recently did some updates of ovirt from 4.4.1 or 4.4.3 to 4.4.4, also
> setting the default datacenter from 4.4 to 4.5 and making the default bios
> q35+eufi. Unfortunately quite a few things. Now however hosted engine
> doesn't boot up anymore and `hosted-engine --console`  just shows the below
> bios/firmware output:
> >>
> >> RHEL
>
> >> RHEL-8.1.0 PC (Q35 + ICH9, 2009)2.00 GHz
>
> >> 0.0.0   16384 MB RAM
>
> >>
> >>
> >>
> >>   Select Language This is the
> option
> >> one adjusts to
> change
> >>> Device Managerthe language for
> the
> >>> Boot Manager  current system
>
> >>> Boot Maintenance Manager
>
> >>
> >>   Continue
>
> >>   Reset
>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>  ^v=Move Highlight   =Select Entry
>
> >>
> >>
> >> When in this state `hosted-engine --vm-status` says it is up but failed
> liveliness check
> >>
> >> hosted-engine --vm-status | grep -i engine\ status
> >> Engine status  : {"vm": "down", "health": "bad",
> "detail": "unknown", "reason": "vm not running on this host"}
> >> Engine status  : {"vm": "up", "health": "bad",
> "detail": "Up", "reason": "failed liveliness check"}
> >> Engine status  : {"vm": "down", "health": "bad",
> "detail": &q

[ovirt-users] Re: Hosted Engine stuck in bios

2021-01-21 Thread Arik Hadas
On Thu, Jan 21, 2021 at 8:57 AM Joseph Gelinas  wrote:

> Hi,
>
> I recently did some updates of ovirt from 4.4.1 or 4.4.3 to 4.4.4, also
> setting the default datacenter from 4.4 to 4.5 and making the default bios
> q35+eufi. Unfortunately quite a few things. Now however hosted engine
> doesn't boot up anymore and `hosted-engine --console`  just shows the below
> bios/firmware output:
>
>  RHEL
>
>  RHEL-8.1.0 PC (Q35 + ICH9, 2009)2.00 GHz
>
>  0.0.0   16384 MB RAM
>
>
>
>
>Select Language This is the
> option
>  one adjusts to
> change
>  > Device Managerthe language for
> the
>  > Boot Manager  current system
>
>  > Boot Maintenance Manager
>
>
>Continue
>
>Reset
>
>
>
>
>
>
>
>
>   ^v=Move Highlight   =Select Entry
>
>
>
> When in this state `hosted-engine --vm-status` says it is up but failed
> liveliness check
>
> hosted-engine --vm-status | grep -i engine\ status
> Engine status  : {"vm": "down", "health": "bad",
> "detail": "unknown", "reason": "vm not running on this host"}
> Engine status  : {"vm": "up", "health": "bad",
> "detail": "Up", "reason": "failed liveliness check"}
> Engine status  : {"vm": "down", "health": "bad",
> "detail": "Down", "reason": "bad vm status"}
>
> I assume I am running into https://access.redhat.com/solutions/5341561
> (RHV: Hosted-Engine VM fails to start after changing the cluster to
> Q35/UEFI) however how to fix that isn't really described. I have tried
> starting hosted engine paused (`hosted-engine --vm-start-paused`) and
> editing the config (`virsh -c
> qemu:///system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf edit
> HostedEngine`) to have pc-i440fx instead and removing a bunch of pcie lines
> etc until it will accept the config and then resuming hosted engine (`virsh
> -c qemu:///system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf resume
> HostedEngine`) but haven't come up with something that is able to start.
>
> Anyone know how to resolve this? Am I even chasing the right path?
>

Let's start with the negative - this should have been prevented by [1].
Can it be that the custom bios type that the hosted engine VM was set with
was manually dropped in this environment?

The positive is that the VM starts. This means that from the chipset
perspective, the configuration is valid.
So I wouldn't try to change it to i440fx, but only to switch the firmware
to BIOS.
I think that removing the following lines from the domain xml should do it:
/usr/share/OVMF/OVMF_CODE.secboot.fd
/var/lib/libvirt/qemu/nvram/81816cd3-5816-4185-b553-b5a636156fbd.fd
Can you give this a try?

[1] https://gerrit.ovirt.org/#/c/ovirt-engine/+/59/


>
>
> /var/log/libvirt/qemu/HostedEngine.log
>
> 2021-01-20 15:31:56.500+: starting up libvirt version: 6.6.0, package:
> 7.1.el8 (CBS , 2020-12-10-14:05:40, ), qemu version:
> 5.1.0qemu-kvm-5.1.0-14.el8.1, kernel: 4.18.0-240.1.1.el8_3.x86_64,
> hostname: ovirt-3
> LC_ALL=C \
> PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin \
> HOME=/var/lib/libvirt/qemu/domain-25-HostedEngine \
> XDG_DATA_HOME=/var/lib/libvirt/qemu/domain-25-HostedEngine/.local/share \
> XDG_CACHE_HOME=/var/lib/libvirt/qemu/domain-25-HostedEngine/.cache \
> XDG_CONFIG_HOME=/var/lib/libvirt/qemu/domain-25-HostedEngine/.config \
> QEMU_AUDIO_DRV=spice \
> /usr/libexec/qemu-kvm \
> -name guest=HostedEngine,debug-threads=on \
> -S \
> -object
> secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-25-HostedEngine/master-key.aes
> \
> -blockdev
> '{"driver":"file","filename":"/usr/share/OVMF/OVMF_CODE.secboot.fd","node-name":"libvirt-pflash0-storage","auto-read-only":true,"discard":"unmap"}'
> \
> -blockdev
> '{"node-name":"libvirt-pflash0-format","read-only":true,"driver":"raw","file":"libvirt-pflash0-storage"}'
> \
> -blockdev
> '{"driver":"file","filename":"/var/lib/libvirt/qemu/nvram/81816cd3-5816-4185-b553-b5a636156fbd.fd","node-name":"libvirt-pflash1-storage","auto-read-only":true,"discard":"unmap"}'
> \
> -blockdev
> '{"node-name":"libvirt-pflash1-format","read-only":false,"driver":"raw","file":"libvirt-pflash1-storage"}'
> \
> -machine
> pc-q35-rhel8.1.0,accel=kvm,usb=off,dump-guest-core=off,pflash0=libvirt-pflash0-format,pflash1=libvirt-pflash1-format
> \
> -cpu Cascadelake-Server-noTSX,mpx=off \
> -m size=16777216k,slots=16,maxmem=67108864k \
> -overcommit mem-lock=off \
> -smp 4,maxcpus=64,sockets=16,dies=1,cores=4,threads=1 \
> -object iothread,id=iothread1 \
> -numa node,nodeid=0,cpus=0-63,mem=16384 \
> -uuid 81816cd3-5816-4185-b553-b5a636156fbd \
> -smbios
> type=1,manufacturer=oVirt,product=RHEL,version=8-1.2011.el8,serial=4c4c4544-0051-3710-8032-c8c04f483633,uuid=81816cd3-5816-4185-b553-b5a636156fbd,family=oVirt
> \
> -no-user-config \
> 

[ovirt-users] Re: VM Disks order

2021-01-19 Thread Arik Hadas
On Mon, Jan 18, 2021 at 1:12 PM Erez Zarum  wrote:

> When attaching a disk it is not possible to set the disk order nor modify
> the order later.
> Example:
> A new VM is provisioned with 5 disks, Disk0 is the OS and then later
> attached disks by order up to Disk4.
> Removing Disk3 and then later attaching does not promise it will be
> attached back as Disk3.
> In most other platforms it is possible to set the order.
>
> Am i missing something? if not, is there a plan to add this feature?
>

What version of oVirt do you use?
The scenario you describe is likely to be fixed in 4.4.3 by [1] for SCSI
disks and assuming the VM keeps running between the detach and attach
operations

[1] https://gerrit.ovirt.org/#/c/ovirt-engine/+/28/


> ___
> 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/7TPSXUQ4WKVAHUP4QV5GITAXFF2BJBYY/
>
___
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/WUVWLT4373P4TVSZ3KLGGQIRJAATLQMY/


[ovirt-users] Re: Q35: BIOS type changed to "Default" when creating new VM from template with Q35 chipset.

2021-01-10 Thread Arik Hadas
On Sat, Jan 9, 2021 at 9:27 PM Tarun Kushwaha 
wrote:

> Hi,
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1678262
>
> this bug is still exist i am facing same issue when create VM from REST
> API and Ansible
> Please give me solutions
>

Hi,
Indeed - the custom bios type field is not copied from the template when
it's not specified in REST-API
Filed [1] on this.
You can explicitly set the custom bios type in the request (see [2]) as a
workaround.

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1914648
[1]
https://github.com/oVirt/ovirt-ansible-collection/blob/master/roles/hosted_engine_setup/tasks/create_target_vm/01_create_target_hosted_engine_vm.yml#L187


> ___
> 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/ORNGEKPETYTRIXXHGU4MC3VGOTJJSVKH/
>
___
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/JEVB6WK5A5K2KM4QKULH76TAWO777XRX/


[ovirt-users] Re: what these providers can do in ovirt envirment such as KVM or XEN ?

2020-12-23 Thread Arik Hadas
On Mon, Dec 21, 2020 at 11:30 AM tommy  wrote:

> If I add such providers like KVM and XEN, what can I do using oVirt?
>
>
>
>
>
>
>
> To manage XEN or KVM usning oVirt?
>

You can then import VMs from those environments to your data center that is
managed by oVirt.


>
> ___
> 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/JRF32YJP5RBUHCRFW7URQ3LTLIJ6XTKL/
>
___
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/TTREWTX3YXY5WM33TYIDIOSQH557EEND/


[ovirt-users] Re: Bad CPU TYPE after Centos 8.3

2020-12-15 Thread Arik Hadas
On Tue, Dec 15, 2020 at 4:41 PM Lionel Caignec  wrote:

> Hi Arik,
>
> Yes, my problem about cpu type, seems linked to the fact i've upgraded a
> host in 8.3 before ugprade ovirt in 4.3...
>
> I've done another test, for my problem of vm migration.
> I start a guest directly on the 8.3 nodes then it can be migrate from/to
> 8.2/83.
> I've also tried to force it to start on a 8.2 nodes then migrate to 8.3
> nodes, and it also work.
>

> So it seems a full power cycle on guest resolve issue.
>

Thanks for checking this - it makes sense that when the VM starts with CPU
type and flags that are derived from the new cluster configuration, the
issue doesn't happen anymore.


>
> Ok for opening a bug on vdsm, could you please let me know where?
>

Sure - https://bugzilla.redhat.com/enter_bug.cgi?product=vdsm


>
>
> Thank you.
>
> --
> *De: *"Arik Hadas" 
> *À: *"Lionel Caignec" 
> *Cc: *"Lucia Jelinkova" , "thomas" ,
> "users" 
> *Envoyé: *Mardi 15 Décembre 2020 15:21:22
> *Objet: *Re: [ovirt-users] Re: Bad CPU TYPE after Centos 8.3
>
>
> On Tue, Dec 15, 2020 at 3:29 PM Lionel Caignec  wrote:
>
>> Hi
>>
>> thank you it's work now. All my host 8.2/8.3 are up and running. During
>> reactivation of 8.2 host i saw the log line "updating cluster CPU..."
>>
>
> Good to see that it works for you now (the credit to Lucia).
> So the cluster configuration didn't change because not all hosts were UP
> when starting the 4.4.3 engine?
>
>
>>
>> I tried to move guest from 8.2 host to 8.3 one but it failed.
>>
>>
>> Engine.log :
>> ERROR [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer]
>> (ForkJoinPool-1-worker-27) [] Migration of VM 'pc115dev' to host '
>> bombur-adm.cines.fr' failed: VM destroyed during the startup.
>> ERROR [org.ovirt.engine.core.vdsbroker.monitoring.VmsMonitoring]
>> (ForkJoinPool-1-worker-19) [] Rerun VM
>> '4fd61e41-ea48-4ba8-b78f-dba5acb87c9e'. Called from VDS 'dis-adm.cines.fr
>> '
>> ERROR
>> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
>> (EE-ManagedThreadFactory-engine-Thread-4) [] EVENT_ID:
>> VM_MIGRATION_TO_SERVER_FAILED(120), Migration failed  (VM: pc115dev,
>> Source: dis-adm.cines.fr, Destination: bombur-adm.cines.fr).
>> ERROR [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer]
>> (ForkJoinPool-1-worker-13) [] Migration of VM 'pc115dev' to host '
>> bombur-adm.cines.fr' failed: VM destroyed during the startup.
>> ERROR [org.ovirt.engine.core.vdsbroker.monitoring.VmsMonitoring]
>> (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-39) []
>> Rerun VM '4fd61e41-ea48-4ba8-b78f-dba5acb87c9e'. Called from VDS '
>> dis-adm.cines.fr'
>> ERROR
>> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
>> (EE-ManagedThreadFactory-engine-Thread-38) [] EVENT_ID:
>> VM_MIGRATION_TO_SERVER_FAILED(120), Migration failed  (VM: pc115dev,
>> Source: dis-adm.cines.fr, Destination: bombur-adm.cines.fr).
>>
>>
>> vdsm.log (target host) :
>> WARN  (Reactor thread) [vds.dispatcher] unhandled write event
>> (betterAsyncore:184)
>> WARN  (jsonrpc/7) [root] ping was deprecated in favor of ping2 and
>> confirmConnectivity (API:1349)
>> WARN  (vm/4fd61e41) [virt.vm]
>> (vmId='4fd61e41-ea48-4ba8-b78f-dba5acb87c9e') Couldn't destroy incoming VM:
>> Domaine non trouvé : aucun domaine ne correspond à l'UUID
>> '4fd61e41-ea48-4ba8-b78f-dba5acb87c9e' (vm:3738)
>>
>
> The migration probably fails due to incompatible CPU flags - please file a
> bug and attach VDSM and libvirt logs from both source and destination hosts.
>
>
>>
>> Another think i've noticed on event log of 8.3 host :
>> VDSM bombur-adm.cines.fr command SpmStatusVDS failed: Cannot inquire
>> Lease(name='SDM', path='/dev/7586152d-338c-415d-93f4-74efd09c02fa/leases',
>> offset=1048576): (2, 'Sanlock get hosts failure', 'No such file or
>> directory')
>>
>>
>> But file seems to exist on host :
>> ls -l /dev/7586152d-338c-415d-93f4-74efd09c02fa/leases
>> lrwxrwxrwx. 1 root root 7 Dec 15 14:14
>> /dev/7586152d-338c-415d-93f4-74efd09c02fa/leases -> ../dm-7
>>
>>
>> I tried to reboot host  & restart engine, set my 8.3 host as SPM ... same
>> error.
>>
>>
>> Lionel.
>>
>
>
___
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/EDCFMNH33MK2I5H2EZSLU2DPZHDHVY7F/


[ovirt-users] Re: Bad CPU TYPE after Centos 8.3

2020-12-15 Thread Arik Hadas
On Tue, Dec 15, 2020 at 3:29 PM Lionel Caignec  wrote:

> Hi
>
> thank you it's work now. All my host 8.2/8.3 are up and running. During
> reactivation of 8.2 host i saw the log line "updating cluster CPU..."
>

Good to see that it works for you now (the credit to Lucia).
So the cluster configuration didn't change because not all hosts were UP
when starting the 4.4.3 engine?


>
> I tried to move guest from 8.2 host to 8.3 one but it failed.
>
>
> Engine.log :
> ERROR [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer]
> (ForkJoinPool-1-worker-27) [] Migration of VM 'pc115dev' to host '
> bombur-adm.cines.fr' failed: VM destroyed during the startup.
> ERROR [org.ovirt.engine.core.vdsbroker.monitoring.VmsMonitoring]
> (ForkJoinPool-1-worker-19) [] Rerun VM
> '4fd61e41-ea48-4ba8-b78f-dba5acb87c9e'. Called from VDS 'dis-adm.cines.fr'
> ERROR
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (EE-ManagedThreadFactory-engine-Thread-4) [] EVENT_ID:
> VM_MIGRATION_TO_SERVER_FAILED(120), Migration failed  (VM: pc115dev,
> Source: dis-adm.cines.fr, Destination: bombur-adm.cines.fr).
> ERROR [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer]
> (ForkJoinPool-1-worker-13) [] Migration of VM 'pc115dev' to host '
> bombur-adm.cines.fr' failed: VM destroyed during the startup.
> ERROR [org.ovirt.engine.core.vdsbroker.monitoring.VmsMonitoring]
> (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-39) []
> Rerun VM '4fd61e41-ea48-4ba8-b78f-dba5acb87c9e'. Called from VDS '
> dis-adm.cines.fr'
> ERROR
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (EE-ManagedThreadFactory-engine-Thread-38) [] EVENT_ID:
> VM_MIGRATION_TO_SERVER_FAILED(120), Migration failed  (VM: pc115dev,
> Source: dis-adm.cines.fr, Destination: bombur-adm.cines.fr).
>
>
> vdsm.log (target host) :
> WARN  (Reactor thread) [vds.dispatcher] unhandled write event
> (betterAsyncore:184)
> WARN  (jsonrpc/7) [root] ping was deprecated in favor of ping2 and
> confirmConnectivity (API:1349)
> WARN  (vm/4fd61e41) [virt.vm]
> (vmId='4fd61e41-ea48-4ba8-b78f-dba5acb87c9e') Couldn't destroy incoming VM:
> Domaine non trouvé : aucun domaine ne correspond à l'UUID
> '4fd61e41-ea48-4ba8-b78f-dba5acb87c9e' (vm:3738)
>

The migration probably fails due to incompatible CPU flags - please file a
bug and attach VDSM and libvirt logs from both source and destination hosts.


>
> Another think i've noticed on event log of 8.3 host :
> VDSM bombur-adm.cines.fr command SpmStatusVDS failed: Cannot inquire
> Lease(name='SDM', path='/dev/7586152d-338c-415d-93f4-74efd09c02fa/leases',
> offset=1048576): (2, 'Sanlock get hosts failure', 'No such file or
> directory')
>
>
> But file seems to exist on host :
> ls -l /dev/7586152d-338c-415d-93f4-74efd09c02fa/leases
> lrwxrwxrwx. 1 root root 7 Dec 15 14:14
> /dev/7586152d-338c-415d-93f4-74efd09c02fa/leases -> ../dm-7
>
>
> I tried to reboot host  & restart engine, set my 8.3 host as SPM ... same
> error.
>
>
> Lionel.
>
> --
> *De: *"Lucia Jelinkova" 
> *À: *"Lionel Caignec" 
> *Cc: *"thomas" , "users" 
> *Envoyé: *Mardi 15 Décembre 2020 13:46:11
> *Objet: *Re: [ovirt-users] Re: Bad CPU TYPE after Centos 8.3
>
> Hi Lionel,
>
> if you managed to remove the host (or move it to a different cluster) so
> that all hosts in your cluster are UP - you could try to put one of your
> running hosts to the maintenance and then back to active - the cluster
> settings should be updated on the host activation. You can look for the log
> "Updating cluster CPU flags and verb according to the configuration of the
> [cluster name]".
>
> If that does not help, you can try to restart the engine.
>
> Please let me know if that helps.
>
> Lucia
>
> ___
> 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/YCL3UBDQWSHXKUDYXXUOBIUUFHQPM3LK/
>
___
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/HBC4HRTGGOTZ7ZL2XW46SIP7322J4ZCD/


[ovirt-users] Re: BUG: after upgrading 4.4.2 to 4.4.3 ISO Domain show empty list

2020-12-08 Thread Arik Hadas
On Tue, Dec 8, 2020 at 10:44 AM Adam Xu  wrote:

> Hi ovirt
>
> This is a big bug. I can not install any OS now because both iso domain
> and iso file in Data Domain can not be visible for VM.
> 在 2020/11/27 20:51, Dmitry Kharlamov 写道:
>
> Recreated ISO domain, but ISO images are still not displayed.
> When loading the ISO files in the Data Domain, is also not visible for VM.
>
>
Could you please follow [1] and see if it solves the problem with the ISO
domain?

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1904947#c3


> ___
> 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/NQWS5L4EAZHUBAYKXDQWRP65QKRRCUAU/
>
> ___
> 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/L7AZDJURVSETJ22GIVDM3G3GFNV7J26I/
>
___
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/X63NACVDEC4JPQIRZWOHZIQEKBHHTTKD/


[ovirt-users] Re: unable to edit vm properties created from pool

2020-12-08 Thread Arik Hadas
On Tue, Dec 8, 2020 at 10:21 AM Lucie Leistnerova 
wrote:

> Hello,
> On 12/4/20 2:46 PM, mhu...@gmail.com wrote:
>
> Hi all,
>
> Is there any way how to edit cpu/memory/boot and stuff like that once the VM 
> has been created by the pool? All option when trying to edit VM are greyed 
> out. We are unable to edit any option for vm in pool.
>
> No, it is intended behaviour. You cannot edit specific VM in the pool. VM
> pool is a bunch of identical VMs that user can randomly take and run.
>

+1


> When you want to change all the pool VMs, you need to remove the pool,
> update the template and create new pool.
>
Or alternatively, if you set the pool to the latest version of a template,
you can create a new version for the template and the VMs would be upgraded
"automatically" when they restart.


> (oVirt Open Virtualization Manager, Software Version:4.4.3.12-1.el8)
>
> Thanks
> ___
> 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/QDFR6DOEKFJBYUR3BXSDOKKTHRFJ2HB4/
>
> Best regards,
> --
>
> Lucie Leistnerova
> Associate Manager, Quality Engineering, RHV - QE Core & Tools
> GChat: lleistne @ Virtualization
> 
> [image: Red Hat EMEA] 
> ___
> 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/K5AOCXIYNI2NPOQM26SK5WDXTV6H6YCM/
>
___
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/NMHW4MXFIEOUYOTDTSOW5Z6MZKUXNYEY/


[ovirt-users] Re: OVIRT and KUBEVIRT

2020-11-19 Thread Arik Hadas
On Wed, Nov 18, 2020 at 10:36 AM Roman Mohr  wrote:

> Hi Andre,
>
> On Wed, Nov 18, 2020 at 7:04 AM Andre Meyer Pflug 
> wrote:
>
>> Is there someone who has done an NON PERSISTANT VDI over oVirt using
>> kubevirt (on OKD) as the infraestructure for vm's?
>>
>> We plan to do a 1.000.000 concurrent users deployment...
>>
>
> I am working on KubeVirt. I can't tell you how the integration in oVirt
> works in detail and which capabilities you inherit from normal RHV flows,
> but I can tell you a little bit about this from the kubevirt and openshift
> perspective.
> I think that you will need a bunch of openshift clusters (10+) to cope
> with that number of VMs/Pods. Also keep in mind that you will have to use
> for VDI something like citrix, windows remote desktop or so on. KubeVirt
> does not support spice, just in case that this was your target.
>
> Others can probably tell you more.
>

In terms of the oVirt-KubeVirt integration, please note that there's no
mapping to VM pools.
I imagine that in oVirt you would probably create VM pool(s) for this - but
doing that won't result in having a corresponding entity in KubeVirt. And
it wouldn't work the other way around - having ReplicateSet/StatefulSet in
KubeVirt will not result in a VM pool on the oVirt side but rather in
individual VMs.

So while the integration may allow you to do user management related things
from within oVirt, it won't allow you to do those that are VM pool related
like defining "Maximum number of VMs per user". Other VM pool related
features may also not be available - either basic ones like assigning a VM
to a user and starting the VM when user "takes" a VM from the VM pool or
more advanced ones like template versions (automatic update of VMs in the
pool to the latest version of the template that the pool is based on).

There are other aspects in KubeVirt that may be relevant in this
context like (Roman/Fabian, please keep me honest as these may have
changed):
* The lack of thin-provisioning of VMs on top of template - pool VMs are
not just set with qcow volumes on top of the template's volumes but rather
each VM has its own isolated volumes. So with that number of VMs, you may
want to make sure the storage device(s) you use provides decent
deduplication capabilities.
* The lack of memory overcommit management - without a tool like MOM that
controls KSM and ballooning you may need more hardware (memory) than you
would have probably needed with oVirt for this.
* The lack of console features - it's not just about SPICE not being
supported but also the 'console-disconnect-action' setting. So the console
you get from oVirt to VMs that are running in KubeVirt may not be
sufficient.

So in terms of the oVirt-KubeVirt integration I'd say that in this context
you may get user management capabilities to some degree and the ability to
manage VMs that spread across various KubeVirt/OKD clusters from a single
place, but there may be other aspects (depending on your needs) that you
may need to consider.


>
> Best Regards,
> Roman
>
>
>
>>
>> Any help is welcome!
>>
>> Kind regards,
>>
>>
>> Andre Meyer Pflug
>> DDESK LLC
>>
>>
>> ___
>> 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/Y3SYDD7IECRVNRPFOJOJMIZ36KHYRIPR/
>>
> ___
> 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/2XATWOFBPPZWCUUYFG2QTJ25VDV6WGOW/
>
___
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/ZTJINF7AXPXVI7C3OPN4UXJZ6U5YDMJW/


[ovirt-users] Re: Clone a VM in the User Portal

2020-11-10 Thread Arik Hadas
On Tue, Nov 10, 2020 at 10:10 PM tfe...@swissonline.ch <
tfe...@swissonline.ch> wrote:

> Cloning VM's is a core feature of virtualization.
>
> I remember having cloned VM's back in the 90's with the free VMware
> version 0.9.
>
> My main use case ever since is cloning fully configured production servers
> into a testservers, for isolated testing.
>
> Why would a hypervisor not offer cloning, when it is possible and useful?
>
> regards, Toni
>

(Added users@ovirt.org back)

Sure, it can be handy in some cases - that's why we've implemented it in
oVirt and enhance it in 4.4.3 (for running VMs).
But I wouldn't expect it to be commonly used via the user portal, that's
why I am interested in the use-case.


>
> On 10.11.20 16:22, Arik Hadas wrote:
>
>
>
> On Tue, Nov 10, 2020 at 4:37 PM Nicolás  wrote:
>
>> Hi Arik,
>>
>> El 10/11/20 a las 13:21, Arik Hadas escribió:
>>
>>
>>
>> On Tue, Nov 10, 2020 at 3:08 PM Nicolás  wrote:
>>
>>> Hi Sharon,
>>>
>>> Thanks for the reply! I've opened [1], so hopefully someone will be able
>>> to implement it.
>>>
>>> Regards,
>>>
>>> Nico
>>>
>>>   [1]: https://github.com/oVirt/ovirt-site/issues/2389
>>>
>>> El 10/11/20 a las 11:38, Sharon Gratch escribió:
>>>
>>> Hi,
>>>
>>> This feature of cloning a VM was indeed part of the old User Portal and
>>> you are right that it's not supported by the newer VM Portal (since oVirt
>>> 4.3).
>>> It seemed that this wasn't required by VM Portal users (no user
>>> complained up till now) and that's why we omitted it and it's not part of
>>> our current roadmap to implement it as well.
>>>
>>> Nevertheless, there is no real reason not to include that ability as
>>> part of VM Portal, so you are most welcome to open an issue on
>>> https://github.com/oVirt/ovirt-web-ui/issues
>>> <https://github.com/oVirt/ovirt-site/issues>
>>> and you can push a fix yourself if you have time (or someone else from
>>> the community) :-)
>>>
>>> Thanks!
>>> Sharon
>>>
>>> On Fri, Nov 6, 2020 at 11:06 AM Nicolás  wrote:
>>>
>>>> Hi,
>>>>
>>>> We're using oVirt 4.3.8, having an organization that intensively uses
>>>> the User Portal. After upgrading from 4.2, we've noticed that cloning a
>>>> VM from within the User Portal is not possible anymore. In our case,
>>>> this feature was heavily used by hundreds of students deploying their
>>>> VMs.
>>>>
>>>
>> Out of curiosity, why cloning a VM and not provisioning the VMs from
>> template(s)?
>>
>>
>>
>> Most of our students are IT-related, and their professors want to teach
>> them the procedure to deploy a VM from scratch. Some other courses surely
>> deploy their VMs from a template as they are not that IT oriented and they
>> just want to have a working VM instead of building it from scratch. We have
>> a lot of casuistry, but in our case about 400~500 students would very
>> welcome having back the clone option.
>>
>
> Thanks Nicolás.
> I'd say that even for the IT-related students it may make more sense to
> provision VMs from templates instead of cloning VMs -
> so you want them to deploy VMs from scratch, which means starting with a
> VM that is based on the blank template, add disk(s) and other devices,
> install and configure the guest and such; and then the students would use
> clone-VM to duplicate the VM they just prepared, right?
> Why would you want them to clone the VM rather than creating a template
> out of this VM and provision further VMs from that template with
> thin-provisioned disks?
>
>
>>
>> Regards,
>>
>> Nico
>>
>>
>>>> Is this feature in the roadmap yet? If not, do you consider it useful
>>>> to
>>>> open a RFE?
>>>>
>>>> Thank you.
>>>>
>>>> Regards,
>>>>
>>>> Nico
>>>> ___
>>>> 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/HFMFJRV3AC3G

[ovirt-users] Re: Clone a VM in the User Portal

2020-11-10 Thread Arik Hadas
On Tue, Nov 10, 2020 at 4:37 PM Nicolás  wrote:

> Hi Arik,
>
> El 10/11/20 a las 13:21, Arik Hadas escribió:
>
>
>
> On Tue, Nov 10, 2020 at 3:08 PM Nicolás  wrote:
>
>> Hi Sharon,
>>
>> Thanks for the reply! I've opened [1], so hopefully someone will be able
>> to implement it.
>>
>> Regards,
>>
>> Nico
>>
>>   [1]: https://github.com/oVirt/ovirt-site/issues/2389
>>
>> El 10/11/20 a las 11:38, Sharon Gratch escribió:
>>
>> Hi,
>>
>> This feature of cloning a VM was indeed part of the old User Portal and
>> you are right that it's not supported by the newer VM Portal (since oVirt
>> 4.3).
>> It seemed that this wasn't required by VM Portal users (no user
>> complained up till now) and that's why we omitted it and it's not part of
>> our current roadmap to implement it as well.
>>
>> Nevertheless, there is no real reason not to include that ability as part
>> of VM Portal, so you are most welcome to open an issue on
>> https://github.com/oVirt/ovirt-web-ui/issues
>> <https://github.com/oVirt/ovirt-site/issues>
>> and you can push a fix yourself if you have time (or someone else from
>> the community) :-)
>>
>> Thanks!
>> Sharon
>>
>> On Fri, Nov 6, 2020 at 11:06 AM Nicolás  wrote:
>>
>>> Hi,
>>>
>>> We're using oVirt 4.3.8, having an organization that intensively uses
>>> the User Portal. After upgrading from 4.2, we've noticed that cloning a
>>> VM from within the User Portal is not possible anymore. In our case,
>>> this feature was heavily used by hundreds of students deploying their
>>> VMs.
>>>
>>
> Out of curiosity, why cloning a VM and not provisioning the VMs from
> template(s)?
>
>
>
> Most of our students are IT-related, and their professors want to teach
> them the procedure to deploy a VM from scratch. Some other courses surely
> deploy their VMs from a template as they are not that IT oriented and they
> just want to have a working VM instead of building it from scratch. We have
> a lot of casuistry, but in our case about 400~500 students would very
> welcome having back the clone option.
>

Thanks Nicolás.
I'd say that even for the IT-related students it may make more sense to
provision VMs from templates instead of cloning VMs -
so you want them to deploy VMs from scratch, which means starting with a VM
that is based on the blank template, add disk(s) and other devices, install
and configure the guest and such; and then the students would use clone-VM
to duplicate the VM they just prepared, right?
Why would you want them to clone the VM rather than creating a template out
of this VM and provision further VMs from that template with
thin-provisioned disks?


>
> Regards,
>
> Nico
>
>
>>> Is this feature in the roadmap yet? If not, do you consider it useful to
>>> open a RFE?
>>>
>>> Thank you.
>>>
>>> Regards,
>>>
>>> Nico
>>> ___
>>> 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/HFMFJRV3AC3GVLYZJ32KAZCIAO25P3X3/
>>>
>>
>> ___
>> 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/RUEW52WZUD27INREQXQ2OPLBLQW2RMK4/
>>
>
>
___
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/QXPS6FCRT66HFI47OXTHTKFS3NONX5MB/


[ovirt-users] Re: Clone a VM in the User Portal

2020-11-10 Thread Arik Hadas
On Tue, Nov 10, 2020 at 3:08 PM Nicolás  wrote:

> Hi Sharon,
>
> Thanks for the reply! I've opened [1], so hopefully someone will be able
> to implement it.
>
> Regards,
>
> Nico
>
>   [1]: https://github.com/oVirt/ovirt-site/issues/2389
>
> El 10/11/20 a las 11:38, Sharon Gratch escribió:
>
> Hi,
>
> This feature of cloning a VM was indeed part of the old User Portal and
> you are right that it's not supported by the newer VM Portal (since oVirt
> 4.3).
> It seemed that this wasn't required by VM Portal users (no user complained
> up till now) and that's why we omitted it and it's not part of our current
> roadmap to implement it as well.
>
> Nevertheless, there is no real reason not to include that ability as part
> of VM Portal, so you are most welcome to open an issue on
> https://github.com/oVirt/ovirt-web-ui/issues
> 
> and you can push a fix yourself if you have time (or someone else from
> the community) :-)
>
> Thanks!
> Sharon
>
> On Fri, Nov 6, 2020 at 11:06 AM Nicolás  wrote:
>
>> Hi,
>>
>> We're using oVirt 4.3.8, having an organization that intensively uses
>> the User Portal. After upgrading from 4.2, we've noticed that cloning a
>> VM from within the User Portal is not possible anymore. In our case,
>> this feature was heavily used by hundreds of students deploying their VMs.
>>
>
Out of curiosity, why cloning a VM and not provisioning the VMs from
template(s)?


>
>> Is this feature in the roadmap yet? If not, do you consider it useful to
>> open a RFE?
>>
>> Thank you.
>>
>> Regards,
>>
>> Nico
>> ___
>> 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/HFMFJRV3AC3GVLYZJ32KAZCIAO25P3X3/
>>
>
> ___
> 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/RUEW52WZUD27INREQXQ2OPLBLQW2RMK4/
>
___
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/GDXLV4DXINPMXJFNZIJOCZWEGML3MLTW/


[ovirt-users] Re: VM Struck in Shutdown Mode

2020-11-05 Thread Arik Hadas
On Thu, Nov 5, 2020 at 12:51 PM Andrei Verovski 
wrote:

> H,
>
> Select query wen succesfull, unfortunately (vm_guid copied from VM
> profile, rest copied from [1]):
>
> engine=# update vm_dynamic set
> run_on_vds='82f92946-9130-4dbd-8663-1ac0b50668a1' where
> vm_guid='d168bbeb-0532-44e4-93da-fdfcd7cc7f20';
>
> ERROR:  insert or update on table "vm_dynamic" violates foreign key
> constraint "vds_static_vm_dynamic_r"
> DETAIL:  Key (run_on_vds)=(82f92946-9130-4dbd-8663-1ac0b50668a1) is not
> present in table "vds_static".
>
> How to properly determine value “ run_on_vds” ? Is this node UUID?
>

Take one of the results of:
select vds_id from vds where status=3;


>
> Thanks.
>
>
> On 3 Nov 2020, at 18:21, Arik Hadas  wrote:
>
>
>
> On Tue, Nov 3, 2020 at 5:36 PM Andrei Verovski 
> wrote:
>
>> Hi,
>>
>> I have oVirt 4.4 engine and v4.2 nodes.
>>
>> On one node newly created VM struck in shutdown mode (with green round
>> recycle icon) - I can’t anything, neither power off neither shutdown, both
>> operation fail (with no explanation). This VM have no value whatsoever, but
>> I can’t delete it either.
>>
>> Restarted oVirt engine, all same.
>>
>> Process list (on node) clearly shows absence of this VM as KVM process.
>> VM is down.
>>
>> How to reset its status in oVirt?
>>
>
> Hi,
>
> Please try the steps described in [1]
>
> [1] https://www.mail-archive.com/users@ovirt.org/msg62928.html
>
>
>>
>> Thanks in advance.
>> Andrei
>> ___
>> 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/VVQT4YDC5JKGSVXBXSXXZONUNQBVLXJQ/
>>
>
>
___
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/2LBVXZIXUP4X4G45LI3RY4VUVZFMM77O/


[ovirt-users] Re: VM Struck in Shutdown Mode

2020-11-03 Thread Arik Hadas
On Tue, Nov 3, 2020 at 5:36 PM Andrei Verovski  wrote:

> Hi,
>
> I have oVirt 4.4 engine and v4.2 nodes.
>
> On one node newly created VM struck in shutdown mode (with green round
> recycle icon) - I can’t anything, neither power off neither shutdown, both
> operation fail (with no explanation). This VM have no value whatsoever, but
> I can’t delete it either.
>
> Restarted oVirt engine, all same.
>
> Process list (on node) clearly shows absence of this VM as KVM process. VM
> is down.
>
> How to reset its status in oVirt?
>

Hi,

Please try the steps described in [1]

[1] https://www.mail-archive.com/users@ovirt.org/msg62928.html


>
> Thanks in advance.
> Andrei
> ___
> 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/VVQT4YDC5JKGSVXBXSXXZONUNQBVLXJQ/
>
___
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/S2DN2BIMWARAGJO6UPFI3ZSKX32S5JAB/


[ovirt-users] Re: Problem with Cluster-wise BIOS Settings in oVirt 4.4

2020-09-30 Thread Arik Hadas
On Wed, Sep 30, 2020 at 1:29 PM Rodrigo G. López 
wrote:

> Hi Arik,
>
> Ok, we'll try with that one.
>

That's just to prevent your hosted engine from being corrupted


>
> The oVirt version we use is 4.4.1.
>

We made several fixes in that area since then, however I see this still
happens on latest version -
so please file a bug and we'll look into it


>
>
> On 9/30/20 11:55 AM, Arik Hadas wrote:
>
>
>
> On Wed, Sep 30, 2020 at 12:30 PM Rodrigo G. López 
> wrote:
>
>> Hi all,
>>
>> We are running an oVirt 4.4 Hosted Engine as a VM, and after changing the
>> Cluster's BIOS type from Q35 with Legacy BIOS (the default one after
>> installation) to Preexistent, the VM fails with the following error:
>>
>> XML error: The device at PCI address :00:02.0 cannot be plugged into
>> the PCI controller with index='0'. It requires a controller that accepts a
>> pcie-root-port.
>>
>>
>> We need it so that we can run imported VMs from a previous version of
>> oVirt, namely 4.0.
>> Applying the BIOS settings individually works but as an attempt to
>> generalize the settings we decided to apply it to the full cluster.
>>
>> Tell me if you need more data.
>>
>>
> Hi,
>
> First, I'd recommend to set the hosted-engine VM with custom bios type set
> to q35+seabios (that's going to be automatically set as of 4.4.3).
> Second, what version of oVirt 4.4 do you use?
>
>
>>
>>
>> Cheers,
>>
>> -rodri
>>
>> ___
>> 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/6RH6UTWUGIS35U74EYDX26AV763PLESM/
>>
>
> ___
> 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/UAMJVONNN236KPRSR5OJYIW6UJJSKHSU/
>
>
> --
> *Rodrigo* González López
> Dpto. Ingeniería
> [image: No parecemos diferentes, LO SOMOS] <http://telfy.com/>
> *Aviso de protección de datos*:
> En cumplimiento del Reglamento (UE) 2016/679 del Parlamento Europeo y del
> Consejo de 27 de abril de 2016, TELFY TELECOM S.L.U. con CIF número
> B54076708 domicilio social en Catral Avd. constitución 9 (Alicante), como
> responsable del tratamiento, le informa que los datos personales que nos
> facilite por este u otro medio serán tratados con la finalidad de prestar y
> ofrecer nuestros servicios de comunicaciones. Le informamos, igualmente,
> que sus datos no serán cedidos a terceros más que en los supuestos en que
> nos hallemos obligados en cumplimiento de la normativa vigente o como
> consecuencia de la ejecución de un contrato. Asimismo le informamos que
> podrá ejercitar de forma gratuita los derechos de acceso, rectificación,
> portabilidad, limitación, supresión, oposición y revocación del
> consentimiento, enviando una solicitud a través del e-mail: i...@telfy.com.
> En caso de que así lo haya consentido previamente a la empresa, sus datos
> podrán ser utilizados para realizarle comunicaciones comerciales y de
> promoción de los productos ofrecidos por TELFY. Podrá obtener toda la
> información necesaria acerca de nuestra política de privacidad y protección
> de datos visitando nuestra web a través del siguiente enlace:
> https://www.telfy.com/es/politica-de-privacidad
> *Confidencialidad:*
> El contenido de esta comunicación, así como el de toda la documentación
> anexa, es confidencial y va dirigido únicamente al destinatario del mismo.
> En el supuesto de que usted no fuera el destinatario, le solicitamos que
> nos lo indique y no comunique su contenido a terceros, procediendo a su
> destrucción.
>
> ___
> 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/GVBEUMY4U6Y73BKYMGB5XC6W73LKYN7Q/
>
___
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/4YSAL65KX7MYEQ4QN3XHSROOCXCF4ZFL/


[ovirt-users] Re: Problem with Cluster-wise BIOS Settings in oVirt 4.4

2020-09-30 Thread Arik Hadas
On Wed, Sep 30, 2020 at 12:30 PM Rodrigo G. López 
wrote:

> Hi all,
>
> We are running an oVirt 4.4 Hosted Engine as a VM, and after changing the
> Cluster's BIOS type from Q35 with Legacy BIOS (the default one after
> installation) to Preexistent, the VM fails with the following error:
>
> XML error: The device at PCI address :00:02.0 cannot be plugged into
> the PCI controller with index='0'. It requires a controller that accepts a
> pcie-root-port.
>
>
> We need it so that we can run imported VMs from a previous version of
> oVirt, namely 4.0.
> Applying the BIOS settings individually works but as an attempt to
> generalize the settings we decided to apply it to the full cluster.
>
> Tell me if you need more data.
>
>
Hi,

First, I'd recommend to set the hosted-engine VM with custom bios type set
to q35+seabios (that's going to be automatically set as of 4.4.3).
Second, what version of oVirt 4.4 do you use?


>
>
> Cheers,
>
> -rodri
>
> ___
> 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/6RH6UTWUGIS35U74EYDX26AV763PLESM/
>
___
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/UAMJVONNN236KPRSR5OJYIW6UJJSKHSU/


[ovirt-users] Re: VM without Host stuck in "Rebooting" State

2020-09-29 Thread Arik Hadas
On Tue, Sep 29, 2020 at 11:46 AM Raphael Höser  wrote:

> I have a VM which was send a "Reboot" and "Shutdown" command in short
> succession (two admins who were not thinking the same way) and now the VM
> is Stuck in "Rebooting".
> It has no Host assigned and when trying to turn it of (via Shutdown or
> Power Off) it gives this error:
>
> Sep 29, 2020, 10:27:10 AM
> Failed to power off VM  (Host: , User:
> admin@internal-authz).
>
> The engine logs don't provide more info either:
> 2020-09-29 10:42:18,628+02 INFO  [org.ovirt.engine.core.bll.StopVmCommand]
> (EE-ManagedThreadFactory-engine-Thread-68681)
> [d4c6547e-c326-4907-8c34-36fd5ab81dfa] Running command: StopVmCommand
> internal: false. Entities affected :  ID:
> 55edef7a-7a0b-42f0-a98f-9150103fa0b1 Type: VMAction group STOP_VM with role
> type USER
> 2020-09-29 10:42:18,628+02 WARN  [org.ovirt.engine.core.bll.StopVmCommand]
> (EE-ManagedThreadFactory-engine-Thread-68681)
> [d4c6547e-c326-4907-8c34-36fd5ab81dfa] Strange, according to the status
> 'RebootInProgress' virtual machine '55edef7a-7a0b-42f0-a98f-9150103fa0b1'
> should be running in a host but it isn't.
> 2020-09-29 10:42:18,635+02 ERROR
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (EE-ManagedThreadFactory-engine-Thread-68681)
> [d4c6547e-c326-4907-8c34-36fd5ab81dfa] EVENT_ID: USER_FAILED_STOP_VM(56),
> Failed to power off VM degum-ci-windows3 (Host: , User:
> admin@internal-authz).
>
> What steps can I do to resolve this?
> I do not need to restore this machine, I'm totally fine with just deleting
> it, but it may not impact other running machines.
>

The steps to overcome this situation were summarized in [1]
The discussion on a proper fix for that takes place in [2]

[1] https://www.mail-archive.com/users@ovirt.org/msg62928.html
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1880251


> ___
> 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/KGWETDMWLPWW62AUBPYF2REH6SITTICZ/
>
___
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/ULFTSQVRLYZGGLDZOKXMPMGPP5LNBWZA/


[ovirt-users] Re: VM stuck in "reboot in progress" ("virtual machine XXX should be running in a host but it isn't.").

2020-09-21 Thread Arik Hadas
On Sun, Sep 20, 2020 at 11:21 AM Gilboa Davara  wrote:

> On Sat, Sep 19, 2020 at 7:44 PM Arik Hadas  wrote:
> >
> >
> >
> > On Fri, Sep 18, 2020 at 8:27 AM Gilboa Davara  wrote:
> >>
> >> Hello all (and happy new year),
> >>
> >> (Note: Also reported as
> https://bugzilla.redhat.com/show_bug.cgi?id=1880251)
> >>
> >> Self hosted engine, single node, NFS.
> >> Attempted to install CentOS over an existing Fedora VM with one host
> >> device (USB printer).
> >> Reboot failed, trying to boot from a non-existent CDROM.
> >> Tried shutting the VM down, failed.
> >> Tried powering off the VM, failed.
> >> Dropped cluster to global maintenance, reboot host + engine (was
> >> planning to upgrade it anyhow...), VM still stuck.
> >>
> >> When trying to power off the VM, the following message can be found
> >> the in engine.log:
> >> 2020-09-18 07:58:51,439+03 INFO
> >> [org.ovirt.engine.core.bll.StopVmCommand]
> >> (EE-ManagedThreadFactory-engine-Thread-42)
> >> [7bc4ac71-f0b2-4af7-b081-100dc99b6123] Running command: StopVmCommand
> >> internal: false. Entities affected :  ID:
> >> b411e573-bcda-4689-b61f-1811c6f03ad5 Type: VMAction group STOP_VM with
> >> role type USER
> >> 2020-09-18 07:58:51,441+03 WARN
> >> [org.ovirt.engine.core.bll.StopVmCommand]
> >> (EE-ManagedThreadFactory-engine-Thread-42)
> >> [7bc4ac71-f0b2-4af7-b081-100dc99b6123] Strange, according to the
> >> status 'RebootInProgress' virtual machine
> >> 'b411e573-bcda-4689-b61f-1811c6f03ad5' should be running in a host but
> >> it isn't.
> >> 2020-09-18 07:58:51,594+03 ERROR
> >> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> >> (EE-ManagedThreadFactory-engine-Thread-42)
> >> [7bc4ac71-f0b2-4af7-b081-100dc99b6123] EVENT_ID:
> >> USER_FAILED_STOP_VM(56), Failed to power off VM kids-home-srv (Host:
> >> , User: gilboa@internal-authz).
> >>
> >> My question is simple: Pending a solution to the bug, can I somehow
> >> drop the state of the VM? It's currently holding a sizable disk image
> >> and a USB device I need (printer).
> >
> >
> > It would be best to modify the VM as if it should still be running on
> the host and let the system discover that it's not running there and update
> the VM accordingly.
> >
> > You can do it by changing the database with:
> > update vm_dynamic set run_on_vds='82f92946-9130-4dbd-8663-1ac0b50668a1'
> where vm_guid='b411e573-bcda-4689-b61f-1811c6f03ad5';
> >
> >
> >>
> >>
> >> As it's my private VM cluster, I have no problem dropping the site
> >> completely for maintenance.
> >>
> >> Thanks,
> >>
> >> Gilboa
>
>
> Hello,
>
> Thanks for the prompt answer.
>
> Edward,
>
> Full reboot of both engine and host didn't help.
> Most likely there's a consistency problem in the oVirt DB.
>
> Arik,
>
> To which DB I should connect and as which user?
> E.g. psql -U user db_name
>

To the 'engine' database.
I usually connect to it by switching to the 'postgres' user as Strahil
described.


>
> Thanks again,
> - Gilboa
>
>
___
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/Z3NF7BKSZFBPZ6ZIN6PICTXJVO3A4Q3A/


[ovirt-users] Re: VM stuck in "reboot in progress" ("virtual machine XXX should be running in a host but it isn't.").

2020-09-19 Thread Arik Hadas
On Fri, Sep 18, 2020 at 8:27 AM Gilboa Davara  wrote:

> Hello all (and happy new year),
>
> (Note: Also reported as
> https://bugzilla.redhat.com/show_bug.cgi?id=1880251)
>
> Self hosted engine, single node, NFS.
> Attempted to install CentOS over an existing Fedora VM with one host
> device (USB printer).
> Reboot failed, trying to boot from a non-existent CDROM.
> Tried shutting the VM down, failed.
> Tried powering off the VM, failed.
> Dropped cluster to global maintenance, reboot host + engine (was
> planning to upgrade it anyhow...), VM still stuck.
>
> When trying to power off the VM, the following message can be found
> the in engine.log:
> 2020-09-18 07:58:51,439+03 INFO
> [org.ovirt.engine.core.bll.StopVmCommand]
> (EE-ManagedThreadFactory-engine-Thread-42)
> [7bc4ac71-f0b2-4af7-b081-100dc99b6123] Running command: StopVmCommand
> internal: false. Entities affected :  ID:
> b411e573-bcda-4689-b61f-1811c6f03ad5 Type: VMAction group STOP_VM with
> role type USER
> 2020-09-18 07:58:51,441+03 WARN
> [org.ovirt.engine.core.bll.StopVmCommand]
> (EE-ManagedThreadFactory-engine-Thread-42)
> [7bc4ac71-f0b2-4af7-b081-100dc99b6123] Strange, according to the
> status 'RebootInProgress' virtual machine
> 'b411e573-bcda-4689-b61f-1811c6f03ad5' should be running in a host but
> it isn't.
> 2020-09-18 07:58:51,594+03 ERROR
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (EE-ManagedThreadFactory-engine-Thread-42)
> [7bc4ac71-f0b2-4af7-b081-100dc99b6123] EVENT_ID:
> USER_FAILED_STOP_VM(56), Failed to power off VM kids-home-srv (Host:
> , User: gilboa@internal-authz).
>
> My question is simple: Pending a solution to the bug, can I somehow
> drop the state of the VM? It's currently holding a sizable disk image
> and a USB device I need (printer).
>

It would be best to modify the VM as if it should still be running on the
host and let the system discover that it's not running there and update the
VM accordingly.

You can do it by changing the database with:
update vm_dynamic set run_on_vds='82f92946-9130-4dbd-8663-1ac0b50668a1'
where vm_guid='b411e573-bcda-4689-b61f-1811c6f03ad5';



>
> As it's my private VM cluster, I have no problem dropping the site
> completely for maintenance.
>
> Thanks,
>
> Gilboa
> ___
> 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/CD536K6HHE5JX7QY2DA6LYNTFABLYR2K/
>
___
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/7JR22MIXFN7FCLOCZB3AW5DQXGHUZASK/


[ovirt-users] Re: cpu QoS doesn't work

2020-09-16 Thread Arik Hadas
On Tue, Sep 15, 2020 at 10:01 AM  wrote:

> Hello,
>
> I set cpu QoS as 10 and applied it to VM on oVirt 4.2, but it doesn't seem
> to work.
> compared to VM without QoS, there wasn't any difference in cpu usage.
> Also, there wasn't any ... or ... field
> related to QoS in libvirt file.
>
> is it right result??
>

well, it depends on the specific properties of your environment - it could
be that with certain values the cpu usage wouldn't change.
as for the last part, yeah - we don't set it in the cputune part of the
domain xml but rather in the metadata section.
you should look for it within the  section - mom is
supposed to detect this and make the changes in libvirt [1]

[1]
https://github.com/oVirt/mom/blob/2438f74cb9fd67f3cc5ab4fb32479b62f08001cf/mom/HypervisorInterfaces/libvirtInterface.py#L300


>
> Thanks,
> ___
> 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:
>
___
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/NHH4PXCIGB7LKGK3SRYVITSHYUB7QMLB/


[ovirt-users] Re: Problem installing Windows VM on 4.4.1

2020-09-01 Thread Arik Hadas
Facundo, can you please provide the output of
virsh -r dumpxml 
on the host that the VM runs on when you start it with an IDE disk and
Windows installer doesn't detect it?

On Tue, Sep 1, 2020 at 9:29 AM Sandro Bonazzola  wrote:

> +Arik Hadas  can you help debugging this?
>
> Il giorno gio 27 ago 2020 alle ore 14:21  ha scritto:
>
>> Hi,
>>  I'm having problem after I upgraded to 4.4.1 with Windows machines.
>>
>>  The installation sees no disk. Even IDE disk doesn't get detected and
>> installation won't move forward no matter what driver i use for the disk.
>>
>>   Any one else having this issue?.
>>
>> Regards,
>> Facundo
>> ___
>> 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/NWECE32ZPJKUCN7CZK45A3MXCHZPI5CX/
>>
>
>
> --
>
> Sandro Bonazzola
>
> MANAGER, SOFTWARE ENGINEERING, EMEA R RHV
>
> Red Hat EMEA <https://www.redhat.com/>
>
> sbona...@redhat.com
> <https://www.redhat.com/>
>
> *Red Hat respects your work life balance. Therefore there is no need to
> answer this email out of your office hours.
> <https://mojo.redhat.com/docs/DOC-1199578>*
>
___
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/7ERGUEODXAGULQ3KP3U4N4IMT57MOJ3T/


[ovirt-users] Re: How can you avoid breaking 4.3.11 legacy VMs imported in 4.4.1 during a migration?

2020-09-01 Thread Arik Hadas
On Tue, Sep 1, 2020 at 1:22 AM  wrote:

> Thanks for the suggestion, I tried that, but I didn't get very far on a
> single node HCI cluster...
> And I'm afraid it won't be much better on HCI in general, which is really
> the use case I am most interested in.
>

Yes, that requires at least one more host for the second cluster


>
> Silently converting VMs is something rather unexpected from a hypervisor,
> doing it twice my result in the same machine here only by accident.
>
> That type of design decision needs highlighting in the documentation,
> because users just won't be expecting it.
> ___
> 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/MUGBA2TBEEIHIJJLBYVQTYQKUTOJ2MWK/
>
___
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/6GZIVEFL6MJLUSSHRHMUIYPXDZPOFKER/


[ovirt-users] Re: How can you avoid breaking 4.3.11 legacy VMs imported in 4.4.1 during a migration?

2020-08-31 Thread Arik Hadas
On Mon, Aug 31, 2020 at 8:41 PM  wrote:

> Testing the 4.3 to 4.4 migration... what I describe here is facts is
> mostly observations and conjecture, could be wrong, just makes writing
> easier...
>
> While 4.3 seems to maintain a default emulated machine type
> (pc-i440fx-rhel7.6.0 by default), it doesn't actually allow setting it in
> the cluster settings: Could be built-in, could be inherited from the
> default template... Most of my VMs were created with the default on 4.3.
>
> oVirt 4.4 presets that to pc-q35-rhel8.1.0 and that has implications:
> 1. Any VM imported from an export on a 4.3 farm, will get upgraded to Q35,
> which unfortunately breaks things, e.g. network adapters getting renamed as
> the first issue I stumbled on some Debian machines
>
2. If you try to compensate by lowering the cluster default from Q35 to
> pc-i44fx the hosted-engine will fail, because it was either built or came
> as Q35 and can no longer find critical devices: It evidently doesn't
> take/use the VM configuration data it had at the last shutdown, but seems
> to re-generate it according to some obscure logic, which fails here.
>
> I've tried creating a bit of backward compatibility by creating another
> template based on pc-i440fx, but at the time of the import, I cannot switch
> the template.
> If I try to downgrade the cluster, the hosted-engine will fail to start
> and I can't change the template of the hosted-engine to something Q35.
>
> Currently this leaves me in a position where I can't separate the move of
> VMs from 4.3 to 4.4 and the upgrade of the virtual hardware, which is a
> different mess for every OS in the mix of VMs.
>
> Recommendations, tips anyone?
>

If you have to preserve the i440fx chipset, you can create another cluster
that is set with legacy bios and import the VMs to that cluster.
The drawback in the alternative you tested (importing it to a q35 cluster
and override the chipset/emulated machine before launching the VM) is that
on import we
convert the VM to q35 (changing devices, clearing PCI addresses) and later
the VM is converted back to i440fx - so it's less recommended.


>
> P.S. A hypervisor reconstructing the virtual hardware from anywhere but
> storage at every launch, is difficult to trust IMHO.
> ___
> 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/36WNCP6YMRM3MG44WIVHLVOUD2MACDQ5/
>
___
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/PAJJNL44JIIY3RAQTWB456EMQALV4SHM/


[ovirt-users] Re: shutdown virtual machine did not display in the list when using virsh list --all and virsh list --state-shutoff

2020-08-30 Thread Arik Hadas
On Sun, Aug 30, 2020 at 10:26 AM Yedidyah Bar David  wrote:

> Hi,
>
> On Sun, Aug 30, 2020 at 9:55 AM Kyre  wrote:
> >
> > Hello, I am using ovirt 4.3.8. I want to use the virsh command to boot
> the shutdown virtual machine, but when using virsh list --all and virsh
> list --state-shutoff, the shutdown virtual machine did not display in the
> list. What is the cause of this, and how can I display the shutdown virtual
> machine.
>
> You can't.
>
> All oVirt-managed VMs are, in libvirt terms, transient. The meta-data
> about them is kept in the engine's database, not in libvirt.
>

This is no longer the case - in 2017 we switched to persistent domains (
https://gerrit.ovirt.org/c/78046)
When the engine issues a 'destroy' call, VDSM undefines the VM


>
> If you want this to plan for (or already are in) a case where the
> engine is dead/unavailable, then you should make sure you keep regular
> engine backups, so that you can restore it, and/or check about DR.
>
> Best regards,
>
> >
> > virsh # list --all
> > Please enter your authentication name: root
> > Please enter your password:
> >  IdName   State
> > 
> >  4 win10E2  running
> >
> > virsh # list --state-shutoff
> >  IdName   State
> > 
> >
> >
> > ___
> > 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/JGFSRX5YF3GK5DBI6EVQBSEJ34VUM66E/
>
>
>
> --
> Didi
> ___
> 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/PD6Y4LWKVVNI4NPQBBJEPQEWROF7ZPYQ/
>
___
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/KXV3XVLZZQ7627VWPA2VAUA4S5YSPG3M/


[ovirt-users] Re: POWER9 (ppc64le) Support on oVirt 4.4.1

2020-08-27 Thread Arik Hadas
On Thu, Aug 27, 2020 at 10:23 PM Arik Hadas  wrote:

>
>
> On Thu, Aug 27, 2020 at 10:13 PM Vinícius Ferrão <
> fer...@versatushpc.com.br> wrote:
>
>>
>>
>> On 27 Aug 2020, at 16:03, Arik Hadas  wrote:
>>
>>
>>
>> On Thu, Aug 27, 2020 at 8:40 PM Vinícius Ferrão via Users <
>> users@ovirt.org> wrote:
>>
>>> Hi Michal,
>>>
>>> On 27 Aug 2020, at 05:08, Michal Skrivanek 
>>> wrote:
>>>
>>>
>>>
>>> On 26 Aug 2020, at 20:50, Vinícius Ferrão via Users 
>>> wrote:
>>>
>>> Okay here we go Arik.
>>>
>>> With your insight I’ve done the following:
>>>
>>> # rpm -Va
>>>
>>> This showed what’s zeroed on the machine, since it was a lot of things,
>>> I’ve just gone crazy and done:
>>>
>>>
>>> you should still have host deploy logs on the engine machine. it’s weird
>>> it succeeded, unless it somehow happened afterwards?
>>>
>>>
>>> It only succeeded my yum reinstall rampage.
>>>
>>> yum list installed | cut -f 1 -d " " > file
>>> yum -y reinstall `cat file | xargs`
>>>
>>> Reinstalled everything.
>>>
>>> Everything worked as expected and I finally added the machine back to
>>> the cluster. It’s operational.
>>>
>>>
>>> eh, I wouldn’t trust it much. did you run redeploy at least?
>>>
>>>
>>> I’ve done reinstall on the web interface of the engine. I can reinstall
>>> the host, there’s nothing running on it… gonna try a third format.
>>>
>>>
>>>
>>> Now I’ve another issue, I have 3 VM’s that are ppc64le, when trying to
>>> import them, the Hosted Engine identifies them as x86_64:
>>>
>>> 
>>>
>>> So…
>>>
>>> This appears to be a bug. Any ideia on how to force it back to ppc64? I
>>> can’t manually force the import on the Hosted Engine since there’s no
>>> buttons to do this…
>>>
>>>
>>> how exactly did you import them? could be a bug indeed.
>>> we don’t support changing it as it doesn’t make sense, the guest can’t
>>> be converted
>>>
>>>
>>> Yeah. I done the normal procedure, added the storage domain to the
>>> engine and clicked on “Import VM”. Immediately it was detected as x86_64.
>>>
>>> Since I wasn’t able to upgrade my environment from 4.3.10 to 4.4.1 due
>>> to random errors when redeploying the engine with the backup from 4.3.10, I
>>> just reinstalled it, reconfigured everything and them imported the storage
>>> domains.
>>>
>>> I don’t know where the information about architecture is stored in the
>>> storage domain, I tried to search for some metadata files inside the domain
>>> but nothing come up. Is there a way to force this change? It must be a way.
>>>
>>> I even tried to import the machine as x86_64. So I can delete the VM and
>>> just reattach the disks in a new only, effectively not losing the data, but…
>>>
>>> 
>>>
>>> Yeah, so something is broken. The check during the import appears to be
>>> OK, but the interface does not me allow to import it to the ppc64le
>>> machine, since it’s read as x86_64.
>>>
>>
>> Could you please provide the output of the following query from the
>> database:
>> select * from unregistered_ovf_of_entities where entity_name='
>> energy.versatushpc.com.br';
>>
>>
>> Sure, there you go:
>>
>>  46ad1d80-2649-48f5-92e6-e5489d11d30c | energy.versatushpc.com.br | VM
>>|1 | |
>> d19456e4-0051-456e-b33c-57348a78c2e0 |
>>  http://schemas.dmtf.org/ovf/envelope/1/; xmlns:rasd="
>> http://schemas.dmtf.org/wbem/wscim/1/cim
>> -schema/2/CIM_ResourceAllocationSettingData" xmlns:vssd="
>> http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_VirtualSystemSettingData;
>> xmlns:xsi="http://ww
>> w.w3.org/2001/XMLSchema-instance"
>> ovf:version="4.1.0.0">> ovf:href="775b24a9-6a32-431a-831f-4ac9b3b31152/b1d9832e-076f-48f3-a300-0b5cdf0949af
>> " ovf:id="b1d9832e-076f-48f3-a300-0b5cdf0949af" ovf:size="512"
>> ovf:description="Active VM" ovf:disk_storage_type="IMAGE"
>> ovf:cinder_volume_type="">> eferences>List of networks> ovf:name="legacyservers">> xsi:type="ovf:DiskSection_Type&qu

[ovirt-users] Re: POWER9 (ppc64le) Support on oVirt 4.4.1

2020-08-27 Thread Arik Hadas
On Thu, Aug 27, 2020 at 10:13 PM Vinícius Ferrão 
wrote:

>
>
> On 27 Aug 2020, at 16:03, Arik Hadas  wrote:
>
>
>
> On Thu, Aug 27, 2020 at 8:40 PM Vinícius Ferrão via Users 
> wrote:
>
>> Hi Michal,
>>
>> On 27 Aug 2020, at 05:08, Michal Skrivanek 
>> wrote:
>>
>>
>>
>> On 26 Aug 2020, at 20:50, Vinícius Ferrão via Users 
>> wrote:
>>
>> Okay here we go Arik.
>>
>> With your insight I’ve done the following:
>>
>> # rpm -Va
>>
>> This showed what’s zeroed on the machine, since it was a lot of things,
>> I’ve just gone crazy and done:
>>
>>
>> you should still have host deploy logs on the engine machine. it’s weird
>> it succeeded, unless it somehow happened afterwards?
>>
>>
>> It only succeeded my yum reinstall rampage.
>>
>> yum list installed | cut -f 1 -d " " > file
>> yum -y reinstall `cat file | xargs`
>>
>> Reinstalled everything.
>>
>> Everything worked as expected and I finally added the machine back to the
>> cluster. It’s operational.
>>
>>
>> eh, I wouldn’t trust it much. did you run redeploy at least?
>>
>>
>> I’ve done reinstall on the web interface of the engine. I can reinstall
>> the host, there’s nothing running on it… gonna try a third format.
>>
>>
>>
>> Now I’ve another issue, I have 3 VM’s that are ppc64le, when trying to
>> import them, the Hosted Engine identifies them as x86_64:
>>
>> 
>>
>> So…
>>
>> This appears to be a bug. Any ideia on how to force it back to ppc64? I
>> can’t manually force the import on the Hosted Engine since there’s no
>> buttons to do this…
>>
>>
>> how exactly did you import them? could be a bug indeed.
>> we don’t support changing it as it doesn’t make sense, the guest can’t be
>> converted
>>
>>
>> Yeah. I done the normal procedure, added the storage domain to the engine
>> and clicked on “Import VM”. Immediately it was detected as x86_64.
>>
>> Since I wasn’t able to upgrade my environment from 4.3.10 to 4.4.1 due to
>> random errors when redeploying the engine with the backup from 4.3.10, I
>> just reinstalled it, reconfigured everything and them imported the storage
>> domains.
>>
>> I don’t know where the information about architecture is stored in the
>> storage domain, I tried to search for some metadata files inside the domain
>> but nothing come up. Is there a way to force this change? It must be a way.
>>
>> I even tried to import the machine as x86_64. So I can delete the VM and
>> just reattach the disks in a new only, effectively not losing the data, but…
>>
>> 
>>
>> Yeah, so something is broken. The check during the import appears to be
>> OK, but the interface does not me allow to import it to the ppc64le
>> machine, since it’s read as x86_64.
>>
>
> Could you please provide the output of the following query from the
> database:
> select * from unregistered_ovf_of_entities where entity_name='
> energy.versatushpc.com.br';
>
>
> Sure, there you go:
>
>  46ad1d80-2649-48f5-92e6-e5489d11d30c | energy.versatushpc.com.br | VM
>|1 | |
> d19456e4-0051-456e-b33c-57348a78c2e0 |
>  http://schemas.dmtf.org/ovf/envelope/1/; xmlns:rasd="
> http://schemas.dmtf.org/wbem/wscim/1/cim
> -schema/2/CIM_ResourceAllocationSettingData" xmlns:vssd="
> http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_VirtualSystemSettingData;
> xmlns:xsi="http://ww
> w.w3.org/2001/XMLSchema-instance" ovf:version="4.1.0.0"> ovf:href="775b24a9-6a32-431a-831f-4ac9b3b31152/b1d9832e-076f-48f3-a300-0b5cdf0949af
> " ovf:id="b1d9832e-076f-48f3-a300-0b5cdf0949af" ovf:size="512"
> ovf:description="Active VM" ovf:disk_storage_type="IMAGE"
> ovf:cinder_volume_type=""> eferences>List of networks ovf:name="legacyservers"> xsi:type="ovf:DiskSection_Type">
> List of Virtual Disks ovf:diskId="b1d9832e-076f-48f3-a300-0b5cdf0949af" ovf:size="40"
> ovf:actual_size="1" ovf:vm_snapshot_id="6de58683-c586
> -4e97-b0e8-ee7ee3baf754" ovf:parentRef=""
> ovf:fileRef="775b24a9-6a32-431a-831f-4ac9b3b31152/b1d9832e-076f-48f3-a300-0b5cdf0949af"
> ovf:format="http://www.vmwa
> re.com/specifications/vmdk.html#sparse" ovf:volume-format="RAW"
> ovf:volume-type="Sparse" ovf:disk-interface="VirtIO_SCSI"
> ovf:read-only="false&qu

[ovirt-users] Re: POWER9 (ppc64le) Support on oVirt 4.4.1

2020-08-27 Thread Arik Hadas
is empty, not checked.
> /sbin/ldconfig: File /lib64/libvirt.so.0.6000.0 is empty, not checked.
> /sbin/ldconfig: File /lib64/libisns.so.0 is empty, not checked.
> /sbin/ldconfig: File /lib64/libiscsi.so.0 is empty, not checked.
> /sbin/ldconfig: File /lib64/libopeniscsiusr.so.0 is empty, not checked.
> /sbin/ldconfig: File /lib64/libopeniscsiusr.so.0.2.0 is empty, not checked.
>
> /sbin/ldconfig: File /lib64/libkadm5clnt.so is empty, not checked.
> /sbin/ldconfig: File /lib64/libkadm5clnt_mit.so is empty, not checked.
> /sbin/ldconfig: File /lib64/libkadm5clnt_mit.so.11 is empty, not checked.
> /sbin/ldconfig: File /lib64/libkadm5clnt_mit.so.11.0 is empty, not checked.
> /sbin/ldconfig: File /lib64/libkadm5srv.so is empty, not checked.
> /sbin/ldconfig: File /lib64/libkadm5srv_mit.so is empty, not checked.
> /sbin/ldconfig: File /lib64/libkadm5srv_mit.so.11 is empty, not checked.
> /sbin/ldconfig: File /lib64/libkadm5srv_mit.so.11.0 is empty, not checked.
> /sbin/ldconfig: File /lib64/libsensors.so.4 is empty, not checked.
> /sbin/ldconfig: File /lib64/libsensors.so.4.4.0 is empty, not checked.
> /sbin/ldconfig: File /lib64/libvirt-admin.so.0 is empty, not checked.
> /sbin/ldconfig: File /lib64/libvirt-admin.so.0.6000.0 is empty, not
> checked.
> /sbin/ldconfig: File /lib64/libvirt-lxc.so.0 is empty, not checked.
> /sbin/ldconfig: File /lib64/libvirt-lxc.so.0.6000.0 is empty, not checked.
> /sbin/ldconfig: File /lib64/libvirt-qemu.so.0 is empty, not checked.
> /sbin/ldconfig: File /lib64/libvirt-qemu.so.0.6000.0 is empty, not checked.
> /sbin/ldconfig: File /lib64/libvirt.so.0 is empty, not checked.
> /sbin/ldconfig: File /lib64/libvirt.so.0.6000.0 is empty, not checked.
> /sbin/ldconfig: File /lib64/libisns.so.0 is empty, not checked.
> /sbin/ldconfig: File /lib64/libiscsi.so.0 is empty, not checked.
> /sbin/ldconfig: File /lib64/libopeniscsiusr.so.0 is empty, not checked.
> /sbin/ldconfig: File /lib64/libopeniscsiusr.so.0.2.0 is empty, not checked.
>
>   Verifying: vdsm-client-4.40.22-1.el8ev.noarch
>
>   1/2
>   Verifying: vdsm-client-4.40.22-1.el8ev.noarch
>
>   2/2
> Installed products updated.
>
> Reinstalled:
>   vdsm-client-4.40.22-1.el8ev.noarch
>
>
>
> I’ve never seen something like this.
>
> I’ve already reinstalled the host from the ground and the same thing
> happens.
>
>
> On 26 Aug 2020, at 14:28, Vinícius Ferrão via Users 
> wrote:
>
> Hello Arik,
> This is probably the issue. Output totally empty:
>
> [root@power ~]# vdsm-client Host getCapabilities
> [root@power ~]#
>
> Here are the packages installed on the machine: (grepped ovirt and vdsm on
> rpm -qa)
> ovirt-imageio-daemon-2.0.8-1.el8ev.ppc64le
> ovirt-imageio-client-2.0.8-1.el8ev.ppc64le
> ovirt-host-4.4.1-4.el8ev.ppc64le
> ovirt-vmconsole-host-1.0.8-1.el8ev.noarch
> ovirt-host-dependencies-4.4.1-4.el8ev.ppc64le
> ovirt-imageio-common-2.0.8-1.el8ev.ppc64le
> ovirt-vmconsole-1.0.8-1.el8ev.noarch
> vdsm-hook-vmfex-dev-4.40.22-1.el8ev.noarch
> vdsm-hook-fcoe-4.40.22-1.el8ev.noarch
> vdsm-hook-ethtool-options-4.40.22-1.el8ev.noarch
> vdsm-hook-openstacknet-4.40.22-1.el8ev.noarch
> vdsm-common-4.40.22-1.el8ev.noarch
> vdsm-python-4.40.22-1.el8ev.noarch
> vdsm-jsonrpc-4.40.22-1.el8ev.noarch
> vdsm-api-4.40.22-1.el8ev.noarch
> vdsm-yajsonrpc-4.40.22-1.el8ev.noarch
> vdsm-4.40.22-1.el8ev.ppc64le
> vdsm-network-4.40.22-1.el8ev.ppc64le
> vdsm-http-4.40.22-1.el8ev.noarch
> vdsm-client-4.40.22-1.el8ev.noarch
> vdsm-hook-vhostmd-4.40.22-1.el8ev.noarch
>
> Any ideias to try?
>
> Thanks.
>
> On 26 Aug 2020, at 05:09, Arik Hadas  wrote:
>
>
>
> On Mon, Aug 24, 2020 at 1:30 AM Vinícius Ferrão via Users 
> wrote:
>
>> Hello, I was using oVirt 4.3.10 with IBM AC922 (POWER9 / ppc64le) without
>> any issues.
>>
>> Since I’ve moved to 4.4.1 I can’t add the AC922 machine to the engine
>> anymore, it complains with the following error:
>> The host CPU does not match the Cluster CPU type and is running in
>> degraded mode. It is missing the following CPU flags: model_POWER9, powernv.
>>
>> Any ideia of what’s may be happening? The engine runs on x86_64, and I
>> was using this way on 4.3.10.
>
>
>> Machine info:
>> timebase: 51200
>> platform: PowerNV
>> model   : 8335-GTH
>> machine : PowerNV 8335-GTH
>> firmware: OPAL
>> MMU : Radix
>>
>
> Can you please provide the output of 'vdsm-client Host getCapabilities' on
> that host?
>
>
>>
>> Thanks,
>>
>>
>> ___
>> Users mailing list -- users@ovirt.org
>> To 

[ovirt-users] Re: POWER9 (ppc64le) Support on oVirt 4.4.1

2020-08-26 Thread Arik Hadas
On Mon, Aug 24, 2020 at 1:30 AM Vinícius Ferrão via Users 
wrote:

> Hello, I was using oVirt 4.3.10 with IBM AC922 (POWER9 / ppc64le) without
> any issues.
>
> Since I’ve moved to 4.4.1 I can’t add the AC922 machine to the engine
> anymore, it complains with the following error:
> The host CPU does not match the Cluster CPU type and is running in
> degraded mode. It is missing the following CPU flags: model_POWER9, powernv.
>
> Any ideia of what’s may be happening? The engine runs on x86_64, and I was
> using this way on 4.3.10.


> Machine info:
> timebase: 51200
> platform: PowerNV
> model   : 8335-GTH
> machine : PowerNV 8335-GTH
> firmware: OPAL
> MMU : Radix
>

Can you please provide the output of 'vdsm-client Host getCapabilities' on
that host?


>
> Thanks,
>
>
> ___
> 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/RV6FHRGKGPPZHVR36WKUHBFDMCQHEJHP/
>
___
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/FRKCP33JX4OHY2NHUHVIAWCCHG52SA6L/


[ovirt-users] Re: Max running ansible-playbook

2020-08-20 Thread Arik Hadas
On Tue, Aug 18, 2020 at 10:49 AM Tommaso - Shellrent via Users <
users@ovirt.org> wrote:

> No one have this kind of problem?
>
> We use OVA export to make some backup, but the whole task takes a lot of
> time because only one ansible-playbook
> "/usr/share/ovirt-engine/playbooks/ovirt-ova-export.yml" run at the same
> time.
>

How do you trigger the export operations?
Do you select multiple VMs/templates in the webadmin and call export to OVA?


> Il 13/08/2020 10:14, Tommaso - Shellrent via Users ha scritto:
>
> Hi to all.
>
> on our angine we always see max 1 ansible-playbook running on the same
> time.
>
> How can we ingrease this value?
>
>
> Regards.
> --
> --
> [image: Shellrent - Il primo hosting italiano Security First]
> *Tommaso De Marchi*
> *COO - Chief Operating Officer*
> Shellrent Srl
> Via dell'Edilizia, 19 - 36100 Vicenza
> Tel. 0444321155 <+390444321155> | Fax 04441492177
>
> ___
> 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/HGST4GFRRAKWZTJ5FJGBO3MGTL233WWK/
>
> --
> --
> [image: Shellrent - Il primo hosting italiano Security First]
> *Tommaso De Marchi*
> *COO - Chief Operating Officer*
> Shellrent Srl
> Via dell'Edilizia, 19 - 36100 Vicenza
> Tel. 0444321155 <+390444321155> | Fax 04441492177
> ___
> 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/KKKLWCHKCHZNJVKUEBGP4JVABREJ7NK4/
>
___
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/JW7MYWZJ352UPOKWFX32Y76SCB5V2IA5/


[ovirt-users] Re: Windows TimeZone UTC

2020-07-26 Thread Arik Hadas
On Sun, Jul 26, 2020 at 4:39 PM Liran Rotenberg  wrote:

>
>
> On Sun, Jul 26, 2020 at 11:52 AM Erez Zarum  wrote:
>
>> Hey Liran,
>> I still don't understand from those resources how can i add an "extra"
>> timezone that is not "compiled" into Engine?
>> Is there a possibility you can write one here? I fear to mess up the
>> Engine.
>>
> Hi, I'm afraid not. There is no option to add a new one.
> The only options you have for windows are:
>
> https://docs.microsoft.com/en-us/previous-versions/windows/embedded/ms912391(v=winembedded.11)?redirectedfrom=MSDN
> As can be seen in:
>
> https://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=blob;f=backend/manager/modules/common/src/main/java/org/ovirt/engine/core/common/TimeZoneType.java
>

(GMT) Greenwich Standard Time should result in offset=0 which will give you
UTC time inside the guest


>
> ___
>> 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/4TJBJEW5QF74EKOBEX5TBH2VHSYRSISR/
>>
> ___
> 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/OT2BQH3TJ5Y7IPGFNEE2C4UPMECISUZC/
>
___
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/K75CTJ5RBEIMAZMAZ7USFVGTK42GLH67/


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

2020-04-19 Thread 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/message/M4LITHLIZXJDTZACENZX4NLO7LSB6VAM/
> 

[ovirt-users] Upload/download disks through muCommander

2020-03-09 Thread 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: Export as OVA fails

2019-08-20 Thread Arik Hadas
On Tue, Aug 20, 2019 at 2:10 AM  wrote:

> Hi.
>
> We are running oVirt 4.3.4 with each of the hosts configured to use local
> storage.
>
> When I attempt to export a large virtual machine as an OVA the process
> begins but fails about half an hour later.
>
> On the oVirt Events page the following entries appear:
>
> Starting to export Vm Jessica as a Virtual Appliance
> Failed to export Vm Jessica as a Virtual Appliance to path
> /storage/Jessica.ova on Host Trueblood
>
> When I log onto the host Trueblood I see that a file called
> Jessica.ova.tmp has been created.
>
> The engine.log file contains the following errors:
>
> 2019-08-16 16:40:27,141+10 ERROR
> [org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor]
> (EE-ManagedThreadFactory-engineScheduled-Thread-37) [80ae4c6] Ansible
> playbook execution failed: Timeout occurred while executing Ansible
> playbook.
> 2019-08-16 16:40:27,142+10 ERROR
> [org.ovirt.engine.core.bll.CreateOvaCommand]
> (EE-ManagedThreadFactory-engineScheduled-Thread-37) [80ae4c6] Failed to
> create OVA. Please check logs for more details:
> /var/log/ovirt-engine/ova/ovirt-export-ova-ansible-20190816161027-trueblood.alfatron.com.au-80ae4c6.log
> 2019-08-16 16:40:27,161+10 ERROR
> [org.ovirt.engine.core.bll.exportimport.ExportVmToOvaCommand]
> (EE-ManagedThreadFactory-engineScheduled-Thread-37) [80ae4c6] Failed to
> create OVA file
> 2019-08-16 16:40:27,162+10 ERROR
> [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback]
> (EE-ManagedThreadFactory-engineScheduled-Thread-37) [80ae4c6] Command
> 'ExportVmToOva' id: '12e98544-67ea-45b0-adb8-c50c8c190ecf' with children
> [a6c04b63-fe81-4d13-a69f-87b8ac55ceaa] failed when attempting to perform
> the next operation, marking as 'ACTIVE'
> 2019-08-16 16:40:27,162+10 ERROR
> [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback]
> (EE-ManagedThreadFactory-engineScheduled-Thread-37) [80ae4c6]
> EngineException: ENGINE (Failed with error ENGINE and code 5001):
> org.ovirt.engine.core.common.errors.EngineException: EngineException:
> ENGINE (Failed with error ENGINE and code 5001)
> at
> org.ovirt.engine.core.bll.exportimport.ExportOvaCommand.createOva(ExportOvaCommand.java:117)
> [bll.jar:]
> at
> org.ovirt.engine.core.bll.exportimport.ExportVmToOvaCommand.executeNextOperation(ExportVmToOvaCommand.java:224)
> [bll.jar:]
> at
> org.ovirt.engine.core.bll.exportimport.ExportVmToOvaCommand.performNextOperation(ExportVmToOvaCommand.java:216)
> [bll.jar:]
> at
> org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback.childCommandsExecutionEnded(SerialChildCommandsExecutionCallback.java:32)
> [bll.jar:]
> at
> org.ovirt.engine.core.bll.ChildCommandsCallbackBase.doPolling(ChildCommandsCallbackBase.java:77)
> [bll.jar:]
> at
> org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller.invokeCallbackMethodsImpl(CommandCallbacksPoller.java:175)
> [bll.jar:]
> at
> org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller.invokeCallbackMethods(CommandCallbacksPoller.java:109)
> [bll.jar:]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> [rt.jar:1.8.0_212]
> at
> java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> [rt.jar:1.8.0_212]
> 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_212]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> [rt.jar:1.8.0_212]
> at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_212]
> 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)
>
> 2019-08-16 16:40:28,304+10 ERROR
> [org.ovirt.engine.core.bll.exportimport.ExportVmToOvaCommand]
> (EE-ManagedThreadFactory-engineScheduled-Thread-10)
> [3f52073f-b7d2-4238-8ac1-4634678b11b4] Ending command
> 'org.ovirt.engine.core.bll.exportimport.ExportVmToOvaCommand' with failure.
> 2019-08-16 16:40:28,745+10 ERROR
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (EE-ManagedThreadFactory-engineScheduled-Thread-10) [41e553bf] EVENT_ID:
> IMPORTEXPORT_EXPORT_VM_TO_OVA_FAILED(1,225), Failed to export Vm Jessica as
> a Virtual Appliance to path /storage/Jessica.ova on Host Trueblood
>
> Any suggestions/help on solving this would 

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

2019-07-08 Thread Arik Hadas
On Mon, Jul 8, 2019 at 8:05 AM Richard Chan 
wrote:

> There was a NIC that was Up + Unplugged. I have removed all NICs and
> recreated them. The NPE remains.
>

Can you please provide the output of the following query:

*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='');*



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

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

2019-07-06 Thread Arik Hadas
On Fri, Jul 5, 2019 at 7:44 PM Richard Chan 
wrote:

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

[1] https://lists.ovirt.org/pipermail/users/2018-March/087481.html


>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> Thanks
>>> Richard Chan
>>> ___
>>> Users mailing list -- users@ovirt.org
>>> To unsubscribe send an email to users-le...@ovirt.org
>>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>>> oVirt Code of Conduct:
>>> 

[ovirt-users] Re: Uploading disk images (oVirt 4.3.3.1)

2019-06-02 Thread Arik Hadas
On Fri, May 31, 2019 at 11:57 PM  wrote:

> Hi,
> I have an issue while trying to upload disk images thru the Web UI.
> "Connection to ovirt-imageio-proxy service has failed. Make sure the
> service is installed, configured, and ovirt-engine certificate is
> registered as a valid CA in the browser."
>
> My ovirt engine's fqdn is ovirt-engine.mydomain.com however due to
> network restrictions I had to set rules in order to reach our ovirt-engine
> ovirt-engine.mydomain.com = 192.168.0.45
>
> For example ovirt-engine.mydomain.otherstuff.com - 192.168.10.109:80,
> 192.168.10.109:443, 192.168.0.45:80
> So as you can see I need to hit the ovirt-engine using
> ovirt-engine.mydomain.otherstuff.com which I am able to by modifyting the
> 11-setup-sso.conf file and adding "SSO_ENGINE_URL="
> https://ovirt-engine.mydomain.otherstuff.com:443/ovirt-engine/;
>
> I am able to upload disk images when using
> http://ovirt-engine.mydomain.com  but not able to
> http://ovirt-engine.mydomain.otherstuff.com
> I know it might be related to the certificates but I need to be able to
> upload disk images using both URLs.
>
> any ideas?
>

Hi,

While it doesn't address your issue directly, you may want to use
muCommander for this - a demo is available in [1].
Note that this is not part of the oVirt project and still under development
but the upload functionality works well, without needing to mess with
credentials in the browser and it also supports uploading ISO files to data
domains (as ISO images). muCommander is not packaged yet with this plugin
for oVirt, so if you're interested in that you'll need to clone the code
from [2] and build it as shown in [1] (All you need is git and the Java
compiler installed. Note it's cross-platform).

[1] https://www.youtube.com/watch?v=pJSTjixYOnU
[2] g...@github.com:mucommander/mucommander.git


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


[ovirt-users] Re: VM Import from remote libvirt Server on web gui with Host key verification failed or permission denied error

2019-05-15 Thread 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]
> 

[ovirt-users] Re: Backup VMs to external USB Disk

2019-04-02 Thread Arik Hadas
On Tue, Apr 2, 2019 at 7:56 PM  wrote:

> Thanks Arik Hadas for your reply.
>
> And how can i do this regulary and automaticly every day?
>

oVirt does not provide an integrated way to define periodic tasks like that.
So you need, e.g., to set up a cron job that executes a script that
triggers the export_to_path_on_host API call - the script can do that via
the python-sdk as you can find at [1]

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


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


[ovirt-users] Re: Backup VMs to external USB Disk

2019-04-01 Thread Arik Hadas
On Mon, Apr 1, 2019 at 10:09 AM  wrote:

> Hi all,
> I'm new in Ovirt and have tested a lot of things how to backup my VMS to a
> external USB Disk.
>
> How have you solved this Problem - have anybody a Tutorial or something
> similar for me?
>

If you can plug the external USB disk to one of the hosts in the cluster,
then you can export your VMs to OVAs and specify the mount point of that
disk on that host as target.


>
> Thanks for your helps.
>
> Daniel
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/UWRIZGJHQULNV47Y6DQ2CHFL2PGP2423/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/VBIW4BNZVPG4ICN2I2IMUYIQBWYF325M/


[ovirt-users] Re: How to import from another oVirt / RHV environment

2019-01-20 Thread Arik Hadas
On Fri, Jan 18, 2019 at 12:17 PM Gianluca Cecchi 
wrote:

> On Thu, Jan 17, 2019 at 6:57 PM Arik Hadas  wrote:
>
>>
>>
>> On Thu, Jan 17, 2019 at 7:54 PM Arik Hadas  wrote:
>>
>>>
>>>
>>> On Thu, Jan 17, 2019 at 6:54 PM Gianluca Cecchi <
>>> gianluca.cec...@gmail.com> wrote:
>>>
>>>> On Thu, Jan 17, 2019 at 5:42 PM Gianluca Cecchi <
>>>> gianluca.cec...@gmail.com> wrote:
>>>>
>>>>> On Thu, Jan 17, 2019 at 4:47 PM Gianluca Cecchi <
>>>>> gianluca.cec...@gmail.com> wrote:
>>>>>
>>>>>> On Thu, Jan 17, 2019 at 4:24 PM Arik Hadas  wrote:
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Thu, Jan 17, 2019 at 4:53 PM Gianluca Cecchi <
>>>>>>> gianluca.cec...@gmail.com> wrote:
>>>>>>>
>>>>>>>> Hello,
>>>>>>>> I have two different oVirt 4.2 environments and I want to migrate
>>>>>>>> some big VMs from one to another.
>>>>>>>> I'm not able to detach and attach the block based domain where are
>>>>>>>> the disks of source.
>>>>>>>> And I cannot use export domain functionality.
>>>>>>>>
>>>>>>>
>>>>>>> you can export them to ova on some device that can later be mounted
>>>>>>> to the destination environment.
>>>>>>> this is similar to the export domain functionality - but you didn't
>>>>>>> specify why the export domain functionality is not applicable for you.
>>>>>>>
>>>>>>
>>>>>>
> Tried by I got error.
> The VM from which I try to create OVA is composed by 3 disks: 15 + 60 +
> 440 Gb
>
> This is the sequence of events seen in engine:
>
> Starting to export Vm dbatest5 as a Virtual Appliance 1/17/19 5:33:35 PM
> VDSM ov200 command TeardownImageVDS failed: Cannot deactivate Logical
> Volume: ('General Storage Exception: ("5 [] [\' Logical volume
> fa33df49-b09d-4f86-9719-ede649542c21/08abaac5-ef82-4755-adc5-7341ce1cde33
> in
> use.\']\\nfa33df49-b09d-4f86-9719-ede649542c21/[\'08abaac5-ef82-4755-adc5-7341ce1cde33\']",)',)
> 1/17/19 9:48:02 PM
>
> Failed to export Vm dbatest5 as a Virtual Appliance to path
> /export/ovirt/dbatest5.ova on Host ov200 1/17/19 9:48:03 PM
>
> Disk dbatest5_Disk1 was successfully removed from domain ovsd3750 (User
> admin@internal-authz). 1/17/19 9:48:04 PM
>
> Disk dbatest5_Disk2 was successfully removed from domain ovsd3750 (User
> admin@internal-authz). 1/17/19 9:48:05 PM
>
> Disk dbatest5_Disk3 was successfully removed from domain ovsd3750 (User
> admin@internal-authz). 1/17/1 99:48:05 PM
>
> And this left this file
> [root@ov200 ~]# ll /export/ovirt/dbatest5.ova.tmp
> -rw-r--r--. 1 root root 552574404608 Jan 17 22:47
> /export/ovirt/dbatest5.ova.tmp
> [root@ov200 ~]#
>
> The ".tmp" extension worried me about possibly not completed ova... is
> this the case... anyway I tried then to import it, see below
>
> I have not understtod which LV it tries to deactivate...
>

Hard to tell from the above anlysis - can you please file a bug and attach
the full engine log?


>
>
>
>> Ah, ok, thanks.
>>>>>> I think you are referring to this feature page and I see in my 4.2.7
>>>>>> env I can do it for a powered off VM:
>>>>>>
>>>>>> https://ovirt.org/develop/release-management/features/virt/enhance-import-export-with-ova.html
>>>>>>
>>>>>
>>> Right
>>>
>>
> On destination host I get this, but I don't know if it depends on ova not
> exactly completed in its part; from the "Broken pipe" error I suspect so...:
>
> ./upload_ova_as_vm.py /export/ovirt/dbatest5.ova.tmp RHVDBA rhvsd3720
>
> Uploaded 69.46%
>
> Uploaded 69.70%
>
> Uploaded 69.95%
>
> Uploaded 70.21%
>
> Uploaded 70.45%
>
> Uploaded 70.71%
> Uploaded 70.72%
>
> Traceback (most recent call last):
>
>   File "./upload_ova_as_vm.py", line 227, in 
>
>proxy_connection.send(chunk)
>   File "/usr/lib64/python2.7/httplib.py", line 857, in send
>
> self.sock.sendall(data)
>
>   File "/usr/lib64/python2.7/ssl.py", line 744, in sendall
>
> v = self.send(data[count:])
>
>   File "/usr/lib64/python2.7/ssl.py", line 710, in send
>
> v = self._sslobj.write(data)
>
> socket.error: [Errno 32] B

[ovirt-users] Re: How to import from another oVirt / RHV environment

2019-01-17 Thread Arik Hadas
On Thu, Jan 17, 2019 at 7:54 PM Arik Hadas  wrote:

>
>
> On Thu, Jan 17, 2019 at 6:54 PM Gianluca Cecchi 
> wrote:
>
>> On Thu, Jan 17, 2019 at 5:42 PM Gianluca Cecchi <
>> gianluca.cec...@gmail.com> wrote:
>>
>>> On Thu, Jan 17, 2019 at 4:47 PM Gianluca Cecchi <
>>> gianluca.cec...@gmail.com> wrote:
>>>
>>>> On Thu, Jan 17, 2019 at 4:24 PM Arik Hadas  wrote:
>>>>
>>>>>
>>>>>
>>>>> On Thu, Jan 17, 2019 at 4:53 PM Gianluca Cecchi <
>>>>> gianluca.cec...@gmail.com> wrote:
>>>>>
>>>>>> Hello,
>>>>>> I have two different oVirt 4.2 environments and I want to migrate
>>>>>> some big VMs from one to another.
>>>>>> I'm not able to detach and attach the block based domain where are
>>>>>> the disks of source.
>>>>>> And I cannot use export domain functionality.
>>>>>>
>>>>>
>>>>> you can export them to ova on some device that can later be mounted to
>>>>> the destination environment.
>>>>> this is similar to the export domain functionality - but you didn't
>>>>> specify why the export domain functionality is not applicable for you.
>>>>>
>>>>
>>>> Ah, ok, thanks.
>>>> I think you are referring to this feature page and I see in my 4.2.7
>>>> env I can do it for a powered off VM:
>>>>
>>>> https://ovirt.org/develop/release-management/features/virt/enhance-import-export-with-ova.html
>>>>
>>>
> Right
>
>
>>
>>>> I will try
>>>> Are the two described TBD features:
>>>> - export as ova also a running VM
>>>> - stream to export to ovirt-imageio daemon
>>>> supposed to be included in 4.3, or is there already a planned target
>>>> release for them?
>>>>
>>>
> The first one is included in 4.3 already (in general, the ova handling is
> better in 4.3 compared to 4.2 in terms of speed).
>

I meant to say: in general, the ova handling is better in 4.3 compared to
4.2.


> The second is unlikely to happen as we found there's no real need for it.
>
>
>>
>>>> Gianluca
>>>>
>>>
>>> BTW: would it be possible to export as ova on a path on host that is an
>>> NFS share, bypassing export domain setup, or does it require local storage?
>>>
>>
> Yes, but note that you need to mount the NFS share in a way that the root
> user on host can write to the specified path.
>
>
>>
>>> Gianluca
>>>
>>
>>
>>  Strange: I tried from the GUI with a vm with 3 disks and specifying a
>> directory but it seems that it has started 3 processes of type "qemu-img
>> convert" where destination is on the storage domain itself???
>> Does it need this step before writing to the destination I chose? I hope
>> no...
>>
>
> Unfortunately, it is indeed done that way in 4.2 :/
> Let me explain:
> We wanted disks within the ova to be of type qcow (for several reasons,
> like thin-provisioning, compression).
> In 4.2 we create temporary disks on the storage that are then copied into
> the OVA (and then removed).
> In 4.3 qemu-img converts the images directly into the place they should be
> within the OVA. That's the reason for the export process being faster in
> 4.3.
>

>
>>
>> vdsm 14380 14269  2 17:33 ?00:00:14 /usr/bin/qemu-img convert
>> -p -t none -T none -f raw
>> /rhev/data-center/mnt/blockSD/fa33df49-b09d-4f86-9719-ede649542c21/images/8cf79957-1b89-42c6-a7af-8031b22f3771/8846e584-190d-403e-a06a-792cebe3b1b1
>> -O qcow2 -o compat=1.1
>> /rhev/data-center/mnt/blockSD/fa33df49-b09d-4f86-9719-ede649542c21/images/8ab058e1-19fd-440a-aa91-c137a79a870e/335c5fdb-025b-4e3e-82a8-06ec9d808d60
>>
>>
>> Gianluca
>>
>>
>>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/G3E7BSCWE67H5SWJZR7RIEYYR4UFZOY4/


[ovirt-users] Re: How to import from another oVirt / RHV environment

2019-01-17 Thread Arik Hadas
On Thu, Jan 17, 2019 at 6:54 PM Gianluca Cecchi 
wrote:

> On Thu, Jan 17, 2019 at 5:42 PM Gianluca Cecchi 
> wrote:
>
>> On Thu, Jan 17, 2019 at 4:47 PM Gianluca Cecchi <
>> gianluca.cec...@gmail.com> wrote:
>>
>>> On Thu, Jan 17, 2019 at 4:24 PM Arik Hadas  wrote:
>>>
>>>>
>>>>
>>>> On Thu, Jan 17, 2019 at 4:53 PM Gianluca Cecchi <
>>>> gianluca.cec...@gmail.com> wrote:
>>>>
>>>>> Hello,
>>>>> I have two different oVirt 4.2 environments and I want to migrate some
>>>>> big VMs from one to another.
>>>>> I'm not able to detach and attach the block based domain where are the
>>>>> disks of source.
>>>>> And I cannot use export domain functionality.
>>>>>
>>>>
>>>> you can export them to ova on some device that can later be mounted to
>>>> the destination environment.
>>>> this is similar to the export domain functionality - but you didn't
>>>> specify why the export domain functionality is not applicable for you.
>>>>
>>>
>>> Ah, ok, thanks.
>>> I think you are referring to this feature page and I see in my 4.2.7 env
>>> I can do it for a powered off VM:
>>>
>>> https://ovirt.org/develop/release-management/features/virt/enhance-import-export-with-ova.html
>>>
>>
Right


>
>>> I will try
>>> Are the two described TBD features:
>>> - export as ova also a running VM
>>> - stream to export to ovirt-imageio daemon
>>> supposed to be included in 4.3, or is there already a planned target
>>> release for them?
>>>
>>
The first one is included in 4.3 already (in general, the ova handling is
better in 4.3 compared to 4.2 in terms of speed).
The second is unlikely to happen as we found there's no real need for it.


>
>>> Gianluca
>>>
>>
>> BTW: would it be possible to export as ova on a path on host that is an
>> NFS share, bypassing export domain setup, or does it require local storage?
>>
>
Yes, but note that you need to mount the NFS share in a way that the root
user on host can write to the specified path.


>
>> Gianluca
>>
>
>
>  Strange: I tried from the GUI with a vm with 3 disks and specifying a
> directory but it seems that it has started 3 processes of type "qemu-img
> convert" where destination is on the storage domain itself???
> Does it need this step before writing to the destination I chose? I hope
> no...
>

Unfortunately, it is indeed done that way in 4.2 :/
Let me explain:
We wanted disks within the ova to be of type qcow (for several reasons,
like thin-provisioning, compression).
In 4.2 we create temporary disks on the storage that are then copied into
the OVA (and then removed).
In 4.3 qemu-img converts the images directly into the place they should be
within the OVA. That's the reason for the export process being faster in
4.3.


>
> vdsm 14380 14269  2 17:33 ?00:00:14 /usr/bin/qemu-img convert
> -p -t none -T none -f raw
> /rhev/data-center/mnt/blockSD/fa33df49-b09d-4f86-9719-ede649542c21/images/8cf79957-1b89-42c6-a7af-8031b22f3771/8846e584-190d-403e-a06a-792cebe3b1b1
> -O qcow2 -o compat=1.1
> /rhev/data-center/mnt/blockSD/fa33df49-b09d-4f86-9719-ede649542c21/images/8ab058e1-19fd-440a-aa91-c137a79a870e/335c5fdb-025b-4e3e-82a8-06ec9d808d60
>
>
> Gianluca
>
>
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/NVFB273MO55MYR3P3JXUSR5Z5R4GMKVM/


[ovirt-users] Re: How to import from another oVirt / RHV environment

2019-01-17 Thread Arik Hadas
On Thu, Jan 17, 2019 at 4:53 PM Gianluca Cecchi 
wrote:

> Hello,
> I have two different oVirt 4.2 environments and I want to migrate some big
> VMs from one to another.
> I'm not able to detach and attach the block based domain where are the
> disks of source.
> And I cannot use export domain functionality.
>

you can export them to ova on some device that can later be mounted to the
destination environment.
this is similar to the export domain functionality - but you didn't specify
why the export domain functionality is not applicable for you.


> But the 2 environments, both hosts and engines, are able to communicate.
>

in this case, you can optimize the above with [1] - export the vm as ova on
one of the hosts that is installed with the ovirt-sdk and upload the ova
from that host to the destination environment.


> Can I use in some way the import Virtual Machine functionality with the
> "KVM(via Libvirt)" source type?
>

I don't think it is possible - you'll need the VM to be configured but not
running on the host (in this case, the engine asks vdsm to destroy the vm).
and anyway I wouldn't do that - it is targeted for importing from foreign
environments. one of the side effects is that you'll lose the
oVirt-specific configuration of the vm.

Or is there (eventually via command line) a way to use virt-v2v in this
> case?
>

virt-v2v is just an overkill for this scenario.

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


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


[ovirt-users] Re: Acquire an XML dump of a VM oVirt?

2018-12-23 Thread Arik Hadas
On Thu, Dec 20, 2018 at 6:28 PM Jacob Green  wrote:

> What if you cannot run the VM, so its not running on any specific host.
> But you want the XML to identify the  information.
>
>
> Thank you.
>
> On 12/20/2018 09:10 AM, Benny Zlotnik wrote:
>
> You can run `virsh -r dumpxml  `  on the relevant host
>
> On Thu, Dec 20, 2018, 16:17 Jacob Green 
>>  How does one get an XML dump of a VM from ovirt? I have seen ovirt
>> do it in the engine.log, but not sure how to force it to generate one
>> when I need it.
>>
>
oVirt doesn't store the domain xml internally.
The domain xml is generated only when trying to start the vm (that's the
output you've seen in engine.log).
I'm afraid there is no other trigger to force generating that xml at the
moment.
But the generation of the xml is mostly 1:1 mapping of some configuration
that is stored differently in oVirt and can be found via the ui/rest-api.
What do you look for exactly?


>
>>
>> Thank you.
>>
>> --
>> Jacob Green
>>
>> Systems Admin
>>
>> American Alloy Steel
>>
>> 713-300-5690
>> ___
>> Users mailing list -- users@ovirt.org
>> To unsubscribe send an email to users-le...@ovirt.org
>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>> oVirt Code of Conduct:
>> https://www.ovirt.org/community/about/community-guidelines/
>> List Archives:
>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/YV7K4GQZID2UC2SPS3PNDEKQUDZ5HLGV/
>>
>
>
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct: 
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives: 
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/LNQTWNT3HLXPXOPZOUMBYTV4HOORAQ75/
>
>
> --
> Jacob Green
>
> Systems Admin
>
> American Alloy Steel
>
> 713-300-5690
>
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/JH4K6SH2DB7EB52KKE2CTD43PJFUMMVX/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/CTN4U5QJUU2LFXO7E3UYHGDIP2K3ZEFJ/


[ovirt-users] Re: Unable to export vm as ova

2018-10-26 Thread Arik Hadas
On Fri, Oct 26, 2018 at 8:58 PM  wrote:

> When I try to export a vm to ova, get this below error in engine log
>
> 2018-10-26 12:11:36,657-04 ERROR
> [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback]
> (EE-ManagedThreadFactory-engineScheduled-Thread-37) [484d3716]
> EngineException: ENGINE (Failed with error ENGINE and code 5001):
> org.ovirt.engine.core.common.errors.EngineException: EngineException:
> ENGINE (Failed with error ENGINE and code 5001)
> at
> org.ovirt.engine.core.bll.exportimport.ExportOvaCommand.createOva(ExportOvaCommand.java:301)
> [bll.jar:]
> at
> org.ovirt.engine.core.bll.exportimport.ExportOvaCommand.executeNextOperation(ExportOvaCommand.java:285)
> [bll.jar:]
> at
> org.ovirt.engine.core.bll.exportimport.ExportOvaCommand.performNextOperation(ExportOvaCommand.java:277)
> [bll.jar:]
> at
> org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback.childCommandsExecutionEnded(SerialChildCommandsExecutionCallback.java:32)
> [bll.jar:]
> at
> org.ovirt.engine.core.bll.ChildCommandsCallbackBase.doPolling(ChildCommandsCallbackBase.java:68)
> [bll.jar:]
> at
> org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller.invokeCallbackMethodsImpl(CommandCallbacksPoller.java:146)
> [bll.jar:]
> at
> org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller.invokeCallbackMethods(CommandCallbacksPoller.java:107)
> [bll.jar:]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> [rt.jar:1.8.0_181]
>
>
> In Ansible log
>
> writing disk:
> path=/rhev/data-center/mnt/ca-ovmstor101:_export_sanrathi_brml11g04-oVirt-nfs-01/aec73d1f-ea3d-4228-a151-a41b20b6b67b/images/e1186fdb-3fc3-46ae-945c-dd19bb6d434c/d95c52e3-35d1-493e-ab2d-42577bdb0391
> size=196848
> Traceback (most recent call last):
>   File
> "/root/.ansible/tmp/ansible-tmp-1540570288.02-200413742597669/pack_ova.py",
> line 96, in 
> write_disks(ova_path, disks_info.split('+'))
>   File
> "/root/.ansible/tmp/ansible-tmp-1540570288.02-200413742597669/pack_ova.py",
> line 79, in write_disks
> write_disk(ova_path, disk_path, disk_size)
>   File
> "/root/.ansible/tmp/ansible-tmp-1540570288.02-200413742597669/pack_ova.py",
> line 59, in write_disk
> fd = os.open(disk_path, os.O_RDONLY | os.O_DIRECT)
> OSError: [Errno 13] Permission denied:
> '/rhev/data-center/mnt/ca-ovmstor101:_export_sanrathi_brml11g04-oVirt-nfs-01/aec73d1f-ea3d-4228-a151-a41b20b6b67b/images/e1186fdb-3fc3-46ae-945c-dd19bb6d434c/d95c52e3-35d1-493e-ab2d-42577bdb0391'
>

Can you please provide more information about image
d95c52e3-35d1-493e-ab2d-42577bdb0391 of disk
e1186fdb-3fc3-46ae-945c-dd19bb6d434c?
1. Its file permissions
2. What's its format (qemu-img info )
3. Whether or not it has a backing file

In light of the size of this image not being a multiply of 512, I suspect
this is an empty qcow2 file.
If that's the case, removing the O_DIRECT flag from pack_ova.py script
might solve this (although if that's the problem I would expect the error
to be "invalid argument" rather than "permission denied").

I see, according to your email, that you're from Oracle so if you're doing
that to test something or as part of an integration of oVirt with some
tool, I would propose doing that with the nightly build of 4.3 - the
process of exporting & importing OVAs was almost completely rewritten and
the new version is faster and more stable (the output of the process, the
OVA, remains the same as that in 4.2).


>
> I have my storage in NFS .
>
> Note: Export to Domain works fine.
> Thanks in advance .
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/75YC2O3RC3G5XZC57ANP7HSOAQYODZAU/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/3DXIRSHSYDGBYIBZUZPZEGM6LSTQZXJB/


[ovirt-users] Re: Can't start the VM ... There are no hosts to use. Check that the cluster contains at least one host in Up state.

2018-08-22 Thread Arik Hadas
On Wed, Aug 22, 2018 at 5:28 PM Daniel Renaud 
wrote:

> No more VM in problem since I remove the CPU type , etc.  Theses values
> came back the same as they was but no more problem starting the VMs after
>

I see.
That's a pity because we cannot figure out what actually lead to that NPE
that I saw in the engine log.
But glad to see that it works for you now. Thanks.


>
> 2018-08-22 9:58 GMT-04:00 Arik Hadas :
>
>>
>>
>> On Wed, Aug 22, 2018 at 4:51 PM Daniel Renaud 
>> wrote:
>>
>>> I checked for the unmanaged interface and they was all ok in the 3 vm
>>>
>>
>> And do you still have a VM that experieces such failures?
>>
>>
>>>
>>> --
>>> Daniel Renaud
>>> Analyste Sécurité & Système
>>> DJJ Consultants, http://www.djj-consultants.com
>>> Téléphone : 418-907-9530, poste 200
>>> GPG key : 0x7189C9D0
>>>
>>> Le 22 août 2018 à 09:43, Arik Hadas  a écrit :
>>>
>>>
>>>
>>> On Wed, Aug 22, 2018 at 3:07 PM Daniel Renaud <
>>> dan...@djj-consultants.com> wrote:
>>>
>>>> Hi
>>>>
>>>> I didn't upgrade and the run once didn't solve the issue but . When
>>>> I use run once again, I remove (in the system tab) Custom emulate machine
>>>> and Custom CPU type (leave it blank) and the run once worked.  After that,
>>>> I can shutdown and but without any problem.  If I go back to look the
>>>> emulate machine and CPU type, it is back to the same value but now I can
>>>> boot.
>>>>
>>>
>>> Please reply to the list.
>>> You said that you have 3 VMs in that state - could you please check if
>>> you have unmanaged interfaces for the other 2 before fixing them that way?
>>>
>>>
>>>>
>>>> 2018-08-22 7:44 GMT-04:00 Arik Hadas :
>>>>
>>>>> Do you remember to what version of oVirt you upgraded the 4.1/4.0/3.6
>>>>> cluster?
>>>>> It sounds like a bug we had (relatively long time ago) that lead to
>>>>> having duplicated unmanaged devices.
>>>>> Can you please check in the VM devices tab if you have unmanaged
>>>>> network interfaces? if you do, it was reported that running the VM in
>>>>> run-once mode would clear those devices (but you can also remove them from
>>>>> the database as well).
>>>>>
>>>>> On Wed, Aug 22, 2018 at 1:38 PM  wrote:
>>>>>
>>>>>> I also tried to export (work) and re-import(work) the same VM and try
>>>>>> to start the imported one with the same result that it didn't start
>>>>>> ___
>>>>>> Users mailing list -- users@ovirt.org
>>>>>> To unsubscribe send an email to users-le...@ovirt.org
>>>>>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>>>>>> oVirt Code of Conduct:
>>>>>> https://www.ovirt.org/community/about/community-guidelines/
>>>>>> List Archives:
>>>>>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/SVE77SQAO5BUC2YQSBWRL54DKYB5FE62/
>>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Daniel Renaud
>>>> Analyste Sécurité & Système
>>>> DJJ Consultants, http://www.djj-consultants.com
>>>> Téléphone : 418-907-9530, poste 200
>>>> GPG key : 0x7189C9D0
>>>>
>>>
>
>
> --
> Daniel Renaud
> Analyste Sécurité & Système
> DJJ Consultants, http://www.djj-consultants.com
> Téléphone : 418-907-9530, poste 200
> GPG key : 0x7189C9D0
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/ERUUO7X3PHEIDRVKX55U5P5FDADMQSNA/


[ovirt-users] Re: Can't start the VM ... There are no hosts to use. Check that the cluster contains at least one host in Up state.

2018-08-22 Thread Arik Hadas
On Wed, Aug 22, 2018 at 4:51 PM Daniel Renaud 
wrote:

> I checked for the unmanaged interface and they was all ok in the 3 vm
>

And do you still have a VM that experieces such failures?


>
> --
> Daniel Renaud
> Analyste Sécurité & Système
> DJJ Consultants, http://www.djj-consultants.com
> Téléphone : 418-907-9530, poste 200
> GPG key : 0x7189C9D0
>
> Le 22 août 2018 à 09:43, Arik Hadas  a écrit :
>
>
>
> On Wed, Aug 22, 2018 at 3:07 PM Daniel Renaud 
> wrote:
>
>> Hi
>>
>> I didn't upgrade and the run once didn't solve the issue but . When I
>> use run once again, I remove (in the system tab) Custom emulate machine and
>> Custom CPU type (leave it blank) and the run once worked.  After that, I
>> can shutdown and but without any problem.  If I go back to look the emulate
>> machine and CPU type, it is back to the same value but now I can boot.
>>
>
> Please reply to the list.
> You said that you have 3 VMs in that state - could you please check if you
> have unmanaged interfaces for the other 2 before fixing them that way?
>
>
>>
>> 2018-08-22 7:44 GMT-04:00 Arik Hadas :
>>
>>> Do you remember to what version of oVirt you upgraded the 4.1/4.0/3.6
>>> cluster?
>>> It sounds like a bug we had (relatively long time ago) that lead to
>>> having duplicated unmanaged devices.
>>> Can you please check in the VM devices tab if you have unmanaged network
>>> interfaces? if you do, it was reported that running the VM in run-once mode
>>> would clear those devices (but you can also remove them from the database
>>> as well).
>>>
>>> On Wed, Aug 22, 2018 at 1:38 PM  wrote:
>>>
>>>> I also tried to export (work) and re-import(work) the same VM and try
>>>> to start the imported one with the same result that it didn't start
>>>> ___
>>>> Users mailing list -- users@ovirt.org
>>>> To unsubscribe send an email to users-le...@ovirt.org
>>>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>>>> oVirt Code of Conduct:
>>>> https://www.ovirt.org/community/about/community-guidelines/
>>>> List Archives:
>>>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/SVE77SQAO5BUC2YQSBWRL54DKYB5FE62/
>>>>
>>>
>>
>>
>> --
>> Daniel Renaud
>> Analyste Sécurité & Système
>> DJJ Consultants, http://www.djj-consultants.com
>> Téléphone : 418-907-9530, poste 200
>> GPG key : 0x7189C9D0
>>
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/BQ4P7SEQXPDNW2GCSXD72L6IBQIJRSM5/


[ovirt-users] Re: Can't start the VM ... There are no hosts to use. Check that the cluster contains at least one host in Up state.

2018-08-22 Thread Arik Hadas
On Wed, Aug 22, 2018 at 3:07 PM Daniel Renaud 
wrote:

> Hi
>
> I didn't upgrade and the run once didn't solve the issue but . When I
> use run once again, I remove (in the system tab) Custom emulate machine and
> Custom CPU type (leave it blank) and the run once worked.  After that, I
> can shutdown and but without any problem.  If I go back to look the emulate
> machine and CPU type, it is back to the same value but now I can boot.
>

Please reply to the list.
You said that you have 3 VMs in that state - could you please check if you
have unmanaged interfaces for the other 2 before fixing them that way?


>
> 2018-08-22 7:44 GMT-04:00 Arik Hadas :
>
>> Do you remember to what version of oVirt you upgraded the 4.1/4.0/3.6
>> cluster?
>> It sounds like a bug we had (relatively long time ago) that lead to
>> having duplicated unmanaged devices.
>> Can you please check in the VM devices tab if you have unmanaged network
>> interfaces? if you do, it was reported that running the VM in run-once mode
>> would clear those devices (but you can also remove them from the database
>> as well).
>>
>> On Wed, Aug 22, 2018 at 1:38 PM  wrote:
>>
>>> I also tried to export (work) and re-import(work) the same VM and try to
>>> start the imported one with the same result that it didn't start
>>> ___
>>> Users mailing list -- users@ovirt.org
>>> To unsubscribe send an email to users-le...@ovirt.org
>>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>>> oVirt Code of Conduct:
>>> https://www.ovirt.org/community/about/community-guidelines/
>>> List Archives:
>>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/SVE77SQAO5BUC2YQSBWRL54DKYB5FE62/
>>>
>>
>
>
> --
> Daniel Renaud
> Analyste Sécurité & Système
> DJJ Consultants, http://www.djj-consultants.com
> Téléphone : 418-907-9530, poste 200
> GPG key : 0x7189C9D0
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/PL7MRJO4T7KQ3BX5PSVUVCHIPSGRTC2C/


[ovirt-users] Re: Can't start the VM ... There are no hosts to use. Check that the cluster contains at least one host in Up state.

2018-08-22 Thread Arik Hadas
Do you remember to what version of oVirt you upgraded the 4.1/4.0/3.6
cluster?
It sounds like a bug we had (relatively long time ago) that lead to having
duplicated unmanaged devices.
Can you please check in the VM devices tab if you have unmanaged network
interfaces? if you do, it was reported that running the VM in run-once mode
would clear those devices (but you can also remove them from the database
as well).

On Wed, Aug 22, 2018 at 1:38 PM  wrote:

> I also tried to export (work) and re-import(work) the same VM and try to
> start the imported one with the same result that it didn't start
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/SVE77SQAO5BUC2YQSBWRL54DKYB5FE62/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/AQQRRT6AS75XZASZZOFQQCGDQF3GMVI4/


[ovirt-users] Re: cannot activate host

2018-08-12 Thread Arik Hadas
On Fri, Aug 10, 2018 at 4:23 PM Jiří Sléžka  wrote:

> Well, issue was solved by installing latest async update 4.2.5...
> Probably helped this part of upgrade process...
>
> ...
> [ INFO  ] Cleaning async tasks and compensations
> [ INFO  ] Unlocking existing entities
>

Right, that was an in-memory lock that blocked you so you probably had to
remove the relevant command that acquired the lock from the
command_entities table.


> ...
>
>
> Cheers,
>
> Jiri
>
>
> On 08/10/2018 11:03 AM, Jiří Sléžka wrote:
> > On 08/10/2018 10:52 AM, Raz Tamir wrote:
> >>
> >>
> >> On Fri, Aug 10, 2018 at 11:30 AM, Jiří Sléžka  >> > wrote:
> >>
> >> Hi,
> >>
> >> On 08/09/2018 11:25 PM, Raz Tamir wrote:
> >> > You can try using vdsm-client to check if there are running tasks
> on the
> >> > host using this command:
> >> >
> >> > vdsm-client Host getAllTasksInfo
> >>
> >> thanks for support, I tried this on affected host
> >>
> >> [root@blade01 ~]# vdsm-client Host getAllTasksInfo
> >> vdsm-client: Command Host.getAllTasksInfo with args {} failed:
> >> (code=654, message=Not SPM: ())
> >>
> >> so I moved into SPM host (blade03 at this time)
> >>
> >> [root@blade03 ~]# vdsm-client Host getAllTasksInfo
> >> {}
> >>
> >> I tried also
> >>
> >> [root@blade01 ~]# vdsm-client Host getAllTasks
> >> {}
> >> [root@blade01 ~]# vdsm-client Host getJobs
> >> {}
> >>
> >> [root@blade03 ~]# vdsm-client Host getAllTasks
> >> {}
> >> [root@blade03 ~]# vdsm-client Host getJobs
> >> {}
> >>
> >> It looks like there are no tasks/jobs running on hosts. It looks
> like
> >> something is stucked in engine db.
> >>
> >> At the beginning of this issue, there were some race condition where
> >> blade01 had two running tasks/jobs which cannot be finished (network
> >> configuration and activating of host). I deleted this jobs manually
> in
> >> db via
> >>
> >> SELECT * FROM job ORDER BY start_time DESC;
> >> SELECT DeleteJob('...job_id...');
> >> SELECT DeleteJob('...job_id...');
> >>
> >> Maybe it was not wise... but what can I do now to solve this? :-)
> >>
> >> Yes it can be bad to mess with the DB.
> >> My best suugestion at the momet is to try and re-add this host.
> >
> > I would like to but I cannot even remove this host (Cannot remove Host.
> > Related operation is currently in progress. Please try again later.) :-(
> > But maybe I can try to add it as brand new one?
> >
> > But I am curious what checks do manager and why we cannot see the
> > tasks/jobs/locks/anything in db...
> >
> > Cheers, Jiri
> >
> >
> >
> >>
> >>
> >>
> >> Cheers, Jiri
> >>
> >>
> >> >
> >> > If there are running tasks, you can stop them:
> >> >
> >> > vdsm-client Task stop taskID=xxx-yyy
> >> >
> >> > If there are finished tasks, you can clear them:
> >> >
> >> > vdsm-client Task clear taskID=xxx-yyy
> >> >
> >> >
> >> > On Thu, Aug 9, 2018, 16:15 Jiří Sléžka  
> >> > >> wrote:
> >> >
> >> > Hello,
> >> >
> >> > still no luck with solving this issue.
> >> >
> >> > I cannot even remove this host.
> >> >
> >> > engine log is now spammed with this messages
> >> >
> >> > 2018-08-09 15:03:08,410+02 INFO
> >> > [org.ovirt.engine.core.bll.lock.InMemoryLockManager]
> >> > (EE-ManagedThreadFactory-engine-Thread-1057)
> >> > [cb8aa091-70ce-419a-b45b-3ffad6f2529b] Failed to acquire lock
> >> and wait
> >> > lock
> >> >
> >>
>   
> 'HostEngineLock:{exclusiveLocks='[786646cd-c9ef-49a8-8aea-56e858dcf202=VDS_INIT]',
> >> > sharedLocks=''}'
> >> > 2018-08-09 15:03:08,446+02 INFO
> >> > [org.ovirt.engine.core.bll.lock.InMemoryLockManager]
> >> > (EE-ManagedThreadFactory-engine-Thread-1057)
> >> > [cb8aa091-70ce-419a-b45b-3ffad6f2529b] Failed to acquire lock
> >> and wait
> >> > lock
> >> >
> >>
>   
> 'HostEngineLock:{exclusiveLocks='[786646cd-c9ef-49a8-8aea-56e858dcf202=VDS_INIT]',
> >> > sharedLocks=''}'
> >> > 2018-08-09 15:03:08,451+02 INFO
> >> > [org.ovirt.engine.core.bll.lock.InMemoryLockManager]
> >> > (EE-ManagedThreadFactory-engine-Thread-1057)
> >> > [cb8aa091-70ce-419a-b45b-3ffad6f2529b] Failed to acquire lock
> >> and wait
> >> > lock
> >> >
> >>
>   
> 'HostEngineLock:{exclusiveLocks='[786646cd-c9ef-49a8-8aea-56e858dcf202=VDS_INIT]',
> >> > sharedLocks=''}'
> >> > 2018-08-09 15:03:08,486+02 INFO
> >> > [org.ovirt.engine.core.bll.lock.InMemoryLockManager]
> >> > (EE-ManagedThreadFactory-engine-Thread-1057)
> >> > [cb8aa091-70ce-419a-b45b-3ffad6f2529b] Failed to acquire lock
> >> and wait
> >> > lock
> >> >
> >>
> 

[ovirt-users] Re: Windows 10 & 2016 snapshot error

2018-08-08 Thread Arik Hadas
On Wed, Aug 8, 2018 at 9:28 PM femi adegoke  wrote:

> Yes the guest agent is running. I have guest control, IP address & fqdn
> show up in the console.
>

Does the gust agent report the applications list inside the VM? (you can
check that in the webadmin)
If it does + this list contains the qemu-guest-agent then you can set the
config value "AgentAppName" accordingly (by default the engine determines
whether the guest agent is installed by checking whether this list contains
either ovirt-guest-agent-common or ovirt-guest-agent).


> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/6RYY52BDCQYUIPV7D7SQPFQZ3DULNYZ7/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/LIJE4I4PQR5MO2G66PQSQJUE2SKIFTMH/


[ovirt-users] Re: More USB device redirection

2018-07-21 Thread Arik Hadas
בתאריך שבת, 21 ביולי 2018, 01:21, מאת Shi Qilin ‏:

> Thanks,this is successful
>

Sure


> 在 2018年7月20日 at 16:21:36, Arik Hadas (aha...@redhat.com) 写到:
>
>>
>>
>> On Fri, Jul 20, 2018 at 5:28 AM  wrote:
>>
>>> We have more USB devices redir (There are 8),But oVirt supports only 6.
>>> How should I configure it.
>>>
>>> /etc/engine-config/engine-config.properties
>>> NumberOfUSBSlots.validValues=0..6
>>>
>>> This 0..6 modify 0..8
>>>
>>> engine-config -s NumberOfUSBSlots=8
>>> engine-config -g NumberOfUSBSlots
>>> NumberOfUSBSlots: 8 version: general
>>>
>>> But No entry into force
>>> Should I do?
>>>
>>
>> To apply this change you'll need to restart the engine, then disable the
>> USB support for that VM, and then enable the USB support again.
>>
>>
>>> Thanks
>>> ___
>>> Users mailing list -- users@ovirt.org
>>> To unsubscribe send an email to users-le...@ovirt.org
>>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>>> oVirt Code of Conduct:
>>> https://www.ovirt.org/community/about/community-guidelines/
>>> List Archives:
>>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/WMBJJAD5H7IAQRQPBWQX5D3LDCETK2SY/
>>>
>>
> --
> shiqi...@outlook.com
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/JKTSASOTLIPF3FWBH34XO32DR2X75RHY/


[ovirt-users] Re: More USB device redirection

2018-07-20 Thread Arik Hadas
On Fri, Jul 20, 2018 at 5:28 AM  wrote:

> We have more USB devices redir (There are 8),But oVirt supports only 6.
> How should I configure it.
>
> /etc/engine-config/engine-config.properties
> NumberOfUSBSlots.validValues=0..6
>
> This 0..6 modify 0..8
>
> engine-config -s NumberOfUSBSlots=8
> engine-config -g NumberOfUSBSlots
> NumberOfUSBSlots: 8 version: general
>
> But No entry into force
> Should I do?
>

To apply this change you'll need to restart the engine, then disable the
USB support for that VM, and then enable the USB support again.


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


[ovirt-users] Re: [Qemu-block] Libvirt ERROR cannot access backing file after importing VM from OpenStack

2018-07-11 Thread Arik Hadas
Better late than never - thank you all for the input, it was very useful!
With the ability to measure the collapsed form of a volume chain in
the qcow2 format, we managed to simplify and improve the process of
creating an OVA significantly. What we do now is:
1. Measure the collapsed qcow2 volumes that would be written to the OVA
2. Create the OVA file accordingly
3. Write the "metadata" of the OVA - headers and OVF, while skipping the
reserved places for disks
4. Mount each reserved place for a disk as a loopback device and convert
the volume-chain directly to it [1]

This saves us from allocating temporary disks and extra copies.
That change would hopefully land in one of the next updates of oVirt 4.2.

[1]
https://github.com/oVirt/ovirt-engine/commit/23230a131af33bfa55a3fe828660c32f7fff04d7

On Wed, May 30, 2018 at 7:39 PM Kevin Wolf  wrote:

> Am 30.05.2018 um 18:14 hat Arik Hadas geschrieben:
> > On Wed, May 30, 2018 at 6:33 PM, Kevin Wolf  wrote:
> > > I think the problem is that we're talking about two different things in
> > > one thread. If I understand correctly, what oVirt does today is:
> > >
> > > 1. qemu-img convert to create a temporary qcow2 image that merges the
> > >whole backing chain in a single file
> > >
> > > 2. tar to create an temporary OVA archive that contains, amongst
> others,
> > >the temporary qcow2 image. This is a second temporary file.
> > >
> > > 3. Stream this temporary OVA archive over HTTP
> > >
> >
> > Well, today we suggest users to mount a shared storage to multiple hosts
> > that reside in different oVirt/RHV deployments so they could export
> > VMs/templates as OVAs to that shared storage and import these OVAs from
> the
> > shared storage to a destination deployment. This process involves only #1
> > and #2.
> >
> > The technique you proposed earlier for writing disks directly into an
> OVA,
> > assuming that the target size can be retrieved with 'qemu-img measure',
> > sounds like a nice approach to accelerate this process. I think we should
> > really consider doing that if that's as easy as it sounds.
>
> Writing the image to a given offset in a file is the example that I gave
> further down in the mail:
>
> > > You added another host into the mix, which just receives the image
> > > content via NBD and then re-exports it as HTTP. Does this host actually
> > > exist or is it the same host where the original images are located?
> > >
> > > Because if you stay local for this step, there is no need to use NBD at
> > > all:
> > >
> > > $ ./qemu-img measure -O qcow2 ~/images/hd.img
> > > required size: 67436544
> > > fully allocated size: 67436544
> > > $ ./qemu-img create -f file /tmp/test.qcow2 67436544
> > > Formatting '/tmp/test.qcow2', fmt=file size=67436544
> > > $ ./qemu-img convert -n --target-image-opts ~/images/hd.img
> > > driver=raw,file.driver=file,file.filename=/tmp/test.qcow2,offset=65536
> > >
> > > hexdump verifies that this does the expected thing.
>
> > But #3 is definitely something we are interested in because we expect the
> > next step to be exporting the OVAs to a remote instance of Glance that
> > serves as a shared repository for the different deployments. Being able
> to
> > stream the collapsed form of a volume chain without writing anything to
> the
> > storage device would be fantastic. I think that even at the expense of
> > iterating the chain twice - once to map the structure of the jump tables
> > (right?) and once to stream the whole data.
>
> If the target is not a stupid web browser, but something actually
> virt-related like Glance, I'm sure it can offer a more suitable protocol
> than HTTP? If you could talk NBD to Glance, you'd get rid of the
> streaming requirement. I think it would make more sense to invest the
> effort there.
>
> Kevin
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/FNTUC4PPI4VKYYFL5OH3ALOJWYMGEI2Z/


[ovirt-users] Re: engine

2018-06-25 Thread Arik Hadas
On Mon, Jun 25, 2018 at 2:16 PM du_hon...@yeah.net 
wrote:

> I have deployed ovirt-engine-4.2.0 in my cluster, I only wan to fix this
> bug, if update ovirt-engine, I am afraid to it has other issue.
>

I see. Well, there were quite a few patches that solved a variety of bugs
in that area, not to mention a big change in the infrastructure that this
feature was implemented with, and therefore finding the relevant patches
and cherry-picking them would not be trivial.
So I would suggest you not to use the OVA export/import until you are able
to update to a more recent version.


>
> --
>
> Regards
>
> Hongyu Du
>
>
> *From:* Arik Hadas 
> *Date:* 2018-06-25 18:03
> *To:* du_hongyu 
> *CC:* users 
> *Subject:* Re: Re: [ovirt-users] engine
>
>
> On Mon, Jun 25, 2018 at 12:39 PM du_hon...@yeah.net 
> wrote:
>
>> I can't to try latest oVirt,  I want to find a patch for this bug. can
>> you give me a patch url for this bug. thanks.
>>
>
> Why can't you update to latest 4.2?
>
>
>>
>> --
>>
>> Regards
>>
>> Hongyu Du
>>
>>
>> *From:* Arik Hadas 
>> *Date:* 2018-06-25 17:28
>> *To:* du_hongyu 
>> *CC:* users 
>> *Subject:* Re: Re: [ovirt-users] engine
>>
>>
>> On Mon, Jun 25, 2018 at 12:15 PM du_hon...@yeah.net 
>> wrote:
>>
>>> my two ovirt version are the same, version is 4.2.0
>>>
>>
>>  Ok, thanks. Yeah, we had a bug that caused our own OVAs to be identified
>> as external OVAs and thus invoking virt-v2v. Please try with latest oVirt,
>> there's a good chance that is resolved already.
>>
>>
>>>
>>> --
>>>
>>> Regards
>>>
>>> Hongyu Du
>>>
>>>
>>> *From:* Arik Hadas 
>>> *Date:* 2018-06-25 17:05
>>> *To:* du_hongyu 
>>> *CC:* users 
>>> *Subject:* Re: Re: [ovirt-users] engine
>>>
>>>
>>> On Mon, Jun 25, 2018 at 11:55 AM du_hon...@yeah.net 
>>> wrote:
>>>
>>>> I get OVA from "Export as OVA" in my another ovirt  cluster.
>>>>
>>>
>>> I see, and what's the version of oVirt that you try to import the OVA to?
>>>
>>>
>>>>
>>>> --
>>>>
>>>> Regards
>>>>
>>>> Hongyu Du
>>>>
>>>>
>>>> *From:* Arik Hadas 
>>>> *Date:* 2018-06-25 16:42
>>>> *To:* du_hongyu 
>>>> *CC:* users 
>>>> *Subject:* Re: Re: [ovirt-users] engine
>>>>
>>>>
>>>> On Mon, Jun 25, 2018 at 11:19 AM du_hon...@yeah.net 
>>>> wrote:
>>>>
>>>>>
>>>>> Hi
>>>>> I find error in /var/log/vdsm/import/
>>>>>
>>>>
>>>> Seems like the OVA is problematic, where did you get it from?
>>>>
>>>>
>>>>>
>>>>> libguestfs: trace: set_verbose true
>>>>> libguestfs: trace: set_verbose = 0
>>>>> libguestfs: trace: get_cachedir
>>>>> libguestfs: trace: get_cachedir = "/var/tmp"
>>>>> virt-v2v: libguestfs 1.32.7 (x86_64)
>>>>> [   0.0] Opening the source -i ova
>>>>> /rhev/data-center/mnt/import-ova/backup_server.ova
>>>>> tar '-xf' '/rhev/data-center/mnt/import-ova/backup_server.ova' '-C'
>>>>> '/var/tmp/ova.z1kmYX'
>>>>> virt-v2v: error: expecting XML expression to return an integer
>>>>> (expression:
>>>>> rasd:Parent/text(), matching string:
>>>>> ----)
>>>>> rm -rf '/var/tmp/ova.z1kmYX'
>>>>> rm -rf '/var/tmp/null.qCXaVl'
>>>>> libguestfs: trace: close
>>>>> libguestfs: closing guestfs handle 0x18cdb60 (state 0)
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>> Regards
>>>>>
>>>>> Hongyu Du
>>>>>
>>>>>
>>>>> *From:* Arik Hadas 
>>>>> *Date:* 2018-06-25 15:44
>>>>> *To:* du_hongyu 
>>>>> *CC:* users 
>>>>> *Subject:* Re: Re: [ovirt-users] engine
>>>>>
>>>>>
>>>>> On Mon, Jun 25, 2018 at 10:37 AM du_hon...@yeah.net <
>>>>> du_hon...@yeah.net> wrote:
>>>>>
>>

[ovirt-users] Re: engine

2018-06-25 Thread Arik Hadas
On Mon, Jun 25, 2018 at 12:39 PM du_hon...@yeah.net 
wrote:

> I can't to try latest oVirt,  I want to find a patch for this bug. can you
> give me a patch url for this bug. thanks.
>

Why can't you update to latest 4.2?


>
> --
>
> Regards
>
> Hongyu Du
>
>
> *From:* Arik Hadas 
> *Date:* 2018-06-25 17:28
> *To:* du_hongyu 
> *CC:* users 
> *Subject:* Re: Re: [ovirt-users] engine
>
>
> On Mon, Jun 25, 2018 at 12:15 PM du_hon...@yeah.net 
> wrote:
>
>> my two ovirt version are the same, version is 4.2.0
>>
>
>  Ok, thanks. Yeah, we had a bug that caused our own OVAs to be identified
> as external OVAs and thus invoking virt-v2v. Please try with latest oVirt,
> there's a good chance that is resolved already.
>
>
>>
>> --
>>
>> Regards
>>
>> Hongyu Du
>>
>>
>> *From:* Arik Hadas 
>> *Date:* 2018-06-25 17:05
>> *To:* du_hongyu 
>> *CC:* users 
>> *Subject:* Re: Re: [ovirt-users] engine
>>
>>
>> On Mon, Jun 25, 2018 at 11:55 AM du_hon...@yeah.net 
>> wrote:
>>
>>> I get OVA from "Export as OVA" in my another ovirt  cluster.
>>>
>>
>> I see, and what's the version of oVirt that you try to import the OVA to?
>>
>>
>>>
>>> --
>>>
>>> Regards
>>>
>>> Hongyu Du
>>>
>>>
>>> *From:* Arik Hadas 
>>> *Date:* 2018-06-25 16:42
>>> *To:* du_hongyu 
>>> *CC:* users 
>>> *Subject:* Re: Re: [ovirt-users] engine
>>>
>>>
>>> On Mon, Jun 25, 2018 at 11:19 AM du_hon...@yeah.net 
>>> wrote:
>>>
>>>>
>>>> Hi
>>>> I find error in /var/log/vdsm/import/
>>>>
>>>
>>> Seems like the OVA is problematic, where did you get it from?
>>>
>>>
>>>>
>>>> libguestfs: trace: set_verbose true
>>>> libguestfs: trace: set_verbose = 0
>>>> libguestfs: trace: get_cachedir
>>>> libguestfs: trace: get_cachedir = "/var/tmp"
>>>> virt-v2v: libguestfs 1.32.7 (x86_64)
>>>> [   0.0] Opening the source -i ova
>>>> /rhev/data-center/mnt/import-ova/backup_server.ova
>>>> tar '-xf' '/rhev/data-center/mnt/import-ova/backup_server.ova' '-C'
>>>> '/var/tmp/ova.z1kmYX'
>>>> virt-v2v: error: expecting XML expression to return an integer
>>>> (expression:
>>>> rasd:Parent/text(), matching string:
>>>> ----)
>>>> rm -rf '/var/tmp/ova.z1kmYX'
>>>> rm -rf '/var/tmp/null.qCXaVl'
>>>> libguestfs: trace: close
>>>> libguestfs: closing guestfs handle 0x18cdb60 (state 0)
>>>>
>>>>
>>>> --
>>>>
>>>> Regards
>>>>
>>>> Hongyu Du
>>>>
>>>>
>>>> *From:* Arik Hadas 
>>>> *Date:* 2018-06-25 15:44
>>>> *To:* du_hongyu 
>>>> *CC:* users 
>>>> *Subject:* Re: Re: [ovirt-users] engine
>>>>
>>>>
>>>> On Mon, Jun 25, 2018 at 10:37 AM du_hon...@yeah.net 
>>>> wrote:
>>>>
>>>>> hi
>>>>> thanks ,  I used full path:
>>>>> /rhev/data-center/mnt/import-ova/backup_server.ova.
>>>>>
>>>>
>>>> Oh, sorry, I looked at a previous attempt.
>>>> Yeah, the conversion failed - we'll need the vdsm log and more
>>>> importantly the import log from the host.
>>>>
>>>>
>>>>>
>>>>> --
>>>>>
>>>>> Regards
>>>>>
>>>>> Hongyu Du
>>>>>
>>>>>
>>>>> *From:* Arik Hadas 
>>>>> *Date:* 2018-06-25 14:49
>>>>> *To:* du_hongyu 
>>>>> *CC:* users 
>>>>> *Subject:* Re: [ovirt-users] engine
>>>>>
>>>>>
>>>>> On Mon, Jun 25, 2018 at 9:12 AM du_hon...@yeah.net 
>>>>> wrote:
>>>>>
>>>>>>
>>>>>> Hi
>>>>>>
>>>>>> I export OVA from my ovirt , then want to import the OVA to anther
>>>>>> ovirt, but this is failed
>>>>>> 2018-06-25 13:52:03,836+08 INFO
>>>>>>  [org.ovirt.en

[ovirt-users] Re: engine

2018-06-25 Thread Arik Hadas
On Mon, Jun 25, 2018 at 12:15 PM du_hon...@yeah.net 
wrote:

> my two ovirt version are the same, version is 4.2.0
>

 Ok, thanks. Yeah, we had a bug that caused our own OVAs to be identified
as external OVAs and thus invoking virt-v2v. Please try with latest oVirt,
there's a good chance that is resolved already.


>
> --
>
> Regards
>
> Hongyu Du
>
>
> *From:* Arik Hadas 
> *Date:* 2018-06-25 17:05
> *To:* du_hongyu 
> *CC:* users 
> *Subject:* Re: Re: [ovirt-users] engine
>
>
> On Mon, Jun 25, 2018 at 11:55 AM du_hon...@yeah.net 
> wrote:
>
>> I get OVA from "Export as OVA" in my another ovirt  cluster.
>>
>
> I see, and what's the version of oVirt that you try to import the OVA to?
>
>
>>
>> --
>>
>> Regards
>>
>> Hongyu Du
>>
>>
>> *From:* Arik Hadas 
>> *Date:* 2018-06-25 16:42
>> *To:* du_hongyu 
>> *CC:* users 
>> *Subject:* Re: Re: [ovirt-users] engine
>>
>>
>> On Mon, Jun 25, 2018 at 11:19 AM du_hon...@yeah.net 
>> wrote:
>>
>>>
>>> Hi
>>> I find error in /var/log/vdsm/import/
>>>
>>
>> Seems like the OVA is problematic, where did you get it from?
>>
>>
>>>
>>> libguestfs: trace: set_verbose true
>>> libguestfs: trace: set_verbose = 0
>>> libguestfs: trace: get_cachedir
>>> libguestfs: trace: get_cachedir = "/var/tmp"
>>> virt-v2v: libguestfs 1.32.7 (x86_64)
>>> [   0.0] Opening the source -i ova
>>> /rhev/data-center/mnt/import-ova/backup_server.ova
>>> tar '-xf' '/rhev/data-center/mnt/import-ova/backup_server.ova' '-C'
>>> '/var/tmp/ova.z1kmYX'
>>> virt-v2v: error: expecting XML expression to return an integer
>>> (expression:
>>> rasd:Parent/text(), matching string:
>>> ----)
>>> rm -rf '/var/tmp/ova.z1kmYX'
>>> rm -rf '/var/tmp/null.qCXaVl'
>>> libguestfs: trace: close
>>> libguestfs: closing guestfs handle 0x18cdb60 (state 0)
>>>
>>>
>>> --
>>>
>>> Regards
>>>
>>> Hongyu Du
>>>
>>>
>>> *From:* Arik Hadas 
>>> *Date:* 2018-06-25 15:44
>>> *To:* du_hongyu 
>>> *CC:* users 
>>> *Subject:* Re: Re: [ovirt-users] engine
>>>
>>>
>>> On Mon, Jun 25, 2018 at 10:37 AM du_hon...@yeah.net 
>>> wrote:
>>>
>>>> hi
>>>> thanks ,  I used full path:
>>>> /rhev/data-center/mnt/import-ova/backup_server.ova.
>>>>
>>>
>>> Oh, sorry, I looked at a previous attempt.
>>> Yeah, the conversion failed - we'll need the vdsm log and more
>>> importantly the import log from the host.
>>>
>>>
>>>>
>>>> --
>>>>
>>>> Regards
>>>>
>>>> Hongyu Du
>>>>
>>>>
>>>> *From:* Arik Hadas 
>>>> *Date:* 2018-06-25 14:49
>>>> *To:* du_hongyu 
>>>> *CC:* users 
>>>> *Subject:* Re: [ovirt-users] engine
>>>>
>>>>
>>>> On Mon, Jun 25, 2018 at 9:12 AM du_hon...@yeah.net 
>>>> wrote:
>>>>
>>>>>
>>>>> Hi
>>>>>
>>>>> I export OVA from my ovirt , then want to import the OVA to anther
>>>>> ovirt, but this is failed
>>>>> 2018-06-25 13:52:03,836+08 INFO
>>>>>  [org.ovirt.engine.core.bll.exportimport.ConvertVmCallback]
>>>>> (EE-ManagedThreadFactory-engineScheduled-Thread-94) [5c66b700] Conversion
>>>>> of VM from external environment failed: Job
>>>>> u'7ef7bff2-5766-4f38-ac28-cdd9da4c407c' process failed exit-code: 1
>>>>>
>>>>
>>>> Seems you're trying to import the OVA file backup_server.ova but you
>>>> provide only the the directory in the "Path" field, right?
>>>> It doesn't work so well at the moment so better specifying the full
>>>> path: /rhev/data-center/mnt/import-ova/backup_server.ova
>>>>
>>>>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>> Regards
>>>>>
>>>>> Hongyu Du
>>>>> ___
>>>>> Users mailing list -- users@ovirt.org
>>>>> To unsubscribe send an email to users-le...@ovirt.org
>>>>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>>>>> oVirt Code of Conduct:
>>>>> https://www.ovirt.org/community/about/community-guidelines/
>>>>> List Archives:
>>>>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/WJZOLVOQT2PDEAVUR3TYCY7AHVR7SKOC/
>>>>>
>>>>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/75YO6URAPD5XJIRWF7R7JP3AK5CAUCUG/


[ovirt-users] Re: engine

2018-06-25 Thread Arik Hadas
On Mon, Jun 25, 2018 at 11:55 AM du_hon...@yeah.net 
wrote:

> I get OVA from "Export as OVA" in my another ovirt  cluster.
>

I see, and what's the version of oVirt that you try to import the OVA to?


>
> --
>
> Regards
>
> Hongyu Du
>
>
> *From:* Arik Hadas 
> *Date:* 2018-06-25 16:42
> *To:* du_hongyu 
> *CC:* users 
> *Subject:* Re: Re: [ovirt-users] engine
>
>
> On Mon, Jun 25, 2018 at 11:19 AM du_hon...@yeah.net 
> wrote:
>
>>
>> Hi
>> I find error in /var/log/vdsm/import/
>>
>
> Seems like the OVA is problematic, where did you get it from?
>
>
>>
>> libguestfs: trace: set_verbose true
>> libguestfs: trace: set_verbose = 0
>> libguestfs: trace: get_cachedir
>> libguestfs: trace: get_cachedir = "/var/tmp"
>> virt-v2v: libguestfs 1.32.7 (x86_64)
>> [   0.0] Opening the source -i ova
>> /rhev/data-center/mnt/import-ova/backup_server.ova
>> tar '-xf' '/rhev/data-center/mnt/import-ova/backup_server.ova' '-C'
>> '/var/tmp/ova.z1kmYX'
>> virt-v2v: error: expecting XML expression to return an integer
>> (expression:
>> rasd:Parent/text(), matching string: ----)
>> rm -rf '/var/tmp/ova.z1kmYX'
>> rm -rf '/var/tmp/null.qCXaVl'
>> libguestfs: trace: close
>> libguestfs: closing guestfs handle 0x18cdb60 (state 0)
>>
>>
>> --
>>
>> Regards
>>
>> Hongyu Du
>>
>>
>> *From:* Arik Hadas 
>> *Date:* 2018-06-25 15:44
>> *To:* du_hongyu 
>> *CC:* users 
>> *Subject:* Re: Re: [ovirt-users] engine
>>
>>
>> On Mon, Jun 25, 2018 at 10:37 AM du_hon...@yeah.net 
>> wrote:
>>
>>> hi
>>> thanks ,  I used full path:
>>> /rhev/data-center/mnt/import-ova/backup_server.ova.
>>>
>>
>> Oh, sorry, I looked at a previous attempt.
>> Yeah, the conversion failed - we'll need the vdsm log and more
>> importantly the import log from the host.
>>
>>
>>>
>>> --
>>>
>>> Regards
>>>
>>> Hongyu Du
>>>
>>>
>>> *From:* Arik Hadas 
>>> *Date:* 2018-06-25 14:49
>>> *To:* du_hongyu 
>>> *CC:* users 
>>> *Subject:* Re: [ovirt-users] engine
>>>
>>>
>>> On Mon, Jun 25, 2018 at 9:12 AM du_hon...@yeah.net 
>>> wrote:
>>>
>>>>
>>>> Hi
>>>>
>>>> I export OVA from my ovirt , then want to import the OVA to anther
>>>> ovirt, but this is failed
>>>> 2018-06-25 13:52:03,836+08 INFO
>>>>  [org.ovirt.engine.core.bll.exportimport.ConvertVmCallback]
>>>> (EE-ManagedThreadFactory-engineScheduled-Thread-94) [5c66b700] Conversion
>>>> of VM from external environment failed: Job
>>>> u'7ef7bff2-5766-4f38-ac28-cdd9da4c407c' process failed exit-code: 1
>>>>
>>>
>>> Seems you're trying to import the OVA file backup_server.ova but you
>>> provide only the the directory in the "Path" field, right?
>>> It doesn't work so well at the moment so better specifying the full
>>> path: /rhev/data-center/mnt/import-ova/backup_server.ova
>>>
>>>
>>>>
>>>>
>>>> --
>>>>
>>>> Regards
>>>>
>>>> Hongyu Du
>>>> ___
>>>> Users mailing list -- users@ovirt.org
>>>> To unsubscribe send an email to users-le...@ovirt.org
>>>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>>>> oVirt Code of Conduct:
>>>> https://www.ovirt.org/community/about/community-guidelines/
>>>> List Archives:
>>>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/WJZOLVOQT2PDEAVUR3TYCY7AHVR7SKOC/
>>>>
>>>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/LG5I2Z2P5FCIWD2XGOIRYHFS6ONB7GHA/


[ovirt-users] Re: engine

2018-06-25 Thread Arik Hadas
On Mon, Jun 25, 2018 at 11:19 AM du_hon...@yeah.net 
wrote:

>
> Hi
> I find error in /var/log/vdsm/import/
>

Seems like the OVA is problematic, where did you get it from?


>
> libguestfs: trace: set_verbose true
> libguestfs: trace: set_verbose = 0
> libguestfs: trace: get_cachedir
> libguestfs: trace: get_cachedir = "/var/tmp"
> virt-v2v: libguestfs 1.32.7 (x86_64)
> [   0.0] Opening the source -i ova
> /rhev/data-center/mnt/import-ova/backup_server.ova
> tar '-xf' '/rhev/data-center/mnt/import-ova/backup_server.ova' '-C'
> '/var/tmp/ova.z1kmYX'
> virt-v2v: error: expecting XML expression to return an integer (expression:
> rasd:Parent/text(), matching string: ----)
> rm -rf '/var/tmp/ova.z1kmYX'
> rm -rf '/var/tmp/null.qCXaVl'
> libguestfs: trace: close
> libguestfs: closing guestfs handle 0x18cdb60 (state 0)
>
>
> --
>
> Regards
>
> Hongyu Du
>
>
> *From:* Arik Hadas 
> *Date:* 2018-06-25 15:44
> *To:* du_hongyu 
> *CC:* users 
> *Subject:* Re: Re: [ovirt-users] engine
>
>
> On Mon, Jun 25, 2018 at 10:37 AM du_hon...@yeah.net 
> wrote:
>
>> hi
>> thanks ,  I used full path:
>> /rhev/data-center/mnt/import-ova/backup_server.ova.
>>
>
> Oh, sorry, I looked at a previous attempt.
> Yeah, the conversion failed - we'll need the vdsm log and more importantly
> the import log from the host.
>
>
>>
>> --
>>
>> Regards
>>
>> Hongyu Du
>>
>>
>> *From:* Arik Hadas 
>> *Date:* 2018-06-25 14:49
>> *To:* du_hongyu 
>> *CC:* users 
>> *Subject:* Re: [ovirt-users] engine
>>
>>
>> On Mon, Jun 25, 2018 at 9:12 AM du_hon...@yeah.net 
>> wrote:
>>
>>>
>>> Hi
>>>
>>> I export OVA from my ovirt , then want to import the OVA to anther
>>> ovirt, but this is failed
>>> 2018-06-25 13:52:03,836+08 INFO
>>>  [org.ovirt.engine.core.bll.exportimport.ConvertVmCallback]
>>> (EE-ManagedThreadFactory-engineScheduled-Thread-94) [5c66b700] Conversion
>>> of VM from external environment failed: Job
>>> u'7ef7bff2-5766-4f38-ac28-cdd9da4c407c' process failed exit-code: 1
>>>
>>
>> Seems you're trying to import the OVA file backup_server.ova but you
>> provide only the the directory in the "Path" field, right?
>> It doesn't work so well at the moment so better specifying the full path:
>> /rhev/data-center/mnt/import-ova/backup_server.ova
>>
>>
>>>
>>>
>>> --
>>>
>>> Regards
>>>
>>> Hongyu Du
>>> ___
>>> Users mailing list -- users@ovirt.org
>>> To unsubscribe send an email to users-le...@ovirt.org
>>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>>> oVirt Code of Conduct:
>>> https://www.ovirt.org/community/about/community-guidelines/
>>> List Archives:
>>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/WJZOLVOQT2PDEAVUR3TYCY7AHVR7SKOC/
>>>
>>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/ILTCPXQG6TXZ3WMZXYL7PYWUVUHTYPI6/


[ovirt-users] Re: engine

2018-06-25 Thread Arik Hadas
On Mon, Jun 25, 2018 at 11:09 AM du_hon...@yeah.net 
wrote:

> Hi
> thanks, this is my vdsm log.
>

The interesting log is rather
/var/log/vdsm/import/import-e832a5ea-a05d-4888-8a73-102aca0c7c0d-20180625T160105.log


> 2018-06-25 16:01:22,028+0800 INFO  (v2v/e832a5ea) [vdsm.api] START
> teardownImage(sdUUID=u'02d60c3b-26e4-463a-a396-0e157228dda9',
> spUUID=u'5b2878b9-024a-0281-007f-00bc',
> imgUUID=u'40264bed-6841-4e25-b230-f6f67c453e7c', volUUID=None)
> from=internal, task_id=21caf93b-c793-46eb-a6fc-529c463f2e86 (api:46)
> 2018-06-25 16:01:22,029+0800 INFO  (v2v/e832a5ea) [vdsm.api] FINISH
> teardownImage return=None from=internal,
> task_id=21caf93b-c793-46eb-a6fc-529c463f2e86 (api:52)
> 2018-06-25 16:01:22,030+0800 ERROR (v2v/e832a5ea) [root] Job
> u'e832a5ea-a05d-4888-8a73-102aca0c7c0d' failed (v2v:871)
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/site-packages/vdsm/v2v.py", line 866, in _run
> self._import()
>   File "/usr/lib/python2.7/site-packages/vdsm/v2v.py", line 891, in _import
> self._proc.returncode))
> V2VProcessError: Job u'e832a5ea-a05d-4888-8a73-102aca0c7c0d' process
> failed exit-code: 1
> 2018-06-25 16:01:22,578+0800 INFO  (jsonrpc/2) [jsonrpc.JsonRpcServer] RPC
> call Host.ping2 succeeded in 0.00 seconds (__init__:573)
> 2018-06-25 16:01:22,583+0800 INFO  (jsonrpc/1) [vdsm.api] START
> repoStats(domains=[u'1dbf48c9-ef23-4830-9f16-fb929624bf26'])
> from=::1,48430, task_id=e98ed4cb-b6cc-4980-ae41-1520a82da5c3 (api:46)
> 2018-06-25 16:01:22,583+0800 INFO  (jsonrpc/1) [vdsm.api] FINISH repoStats
> return={u'1dbf48c9-ef23-4830-9f16-fb929624bf26': {'code': 0, 'actual':
> True, 'version': 4, 'acquired': True, 'delay': '0.00220638', 'lastCheck':
> '3.3', 'valid': True}} from=::1,48430,
> task_id=e98ed4cb-b6cc-4980-ae41-1520a82da5c3 (api:52)
> 2018-06-25 16:01:22,584+0800 INFO  (jsonrpc/1) [jsonrpc.JsonRpcServer] RPC
> call Host.getStorageRepoStats succeeded in 0.00 seconds (__init__:573)
> 2018-06-25 16:01:23,426+0800 INFO  (periodic/43) [vdsm.api] START
> repoStats(domains=()) from=internal,
> task_id=3a5ca5a4-4908-4193-8eb8-de0d010f10eb (api:46)
>
>
> --
>
> Regards
>
> Hongyu Du
>
>
> *From:* Arik Hadas 
> *Date:* 2018-06-25 15:44
> *To:* du_hongyu 
> *CC:* users 
> *Subject:* Re: Re: [ovirt-users] engine
>
>
> On Mon, Jun 25, 2018 at 10:37 AM du_hon...@yeah.net 
> wrote:
>
>> hi
>> thanks ,  I used full path:
>> /rhev/data-center/mnt/import-ova/backup_server.ova.
>>
>
> Oh, sorry, I looked at a previous attempt.
> Yeah, the conversion failed - we'll need the vdsm log and more importantly
> the import log from the host.
>
>
>>
>> --
>>
>> Regards
>>
>> Hongyu Du
>>
>>
>> *From:* Arik Hadas 
>> *Date:* 2018-06-25 14:49
>> *To:* du_hongyu 
>> *CC:* users 
>> *Subject:* Re: [ovirt-users] engine
>>
>>
>> On Mon, Jun 25, 2018 at 9:12 AM du_hon...@yeah.net 
>> wrote:
>>
>>>
>>> Hi
>>>
>>> I export OVA from my ovirt , then want to import the OVA to anther
>>> ovirt, but this is failed
>>> 2018-06-25 13:52:03,836+08 INFO
>>>  [org.ovirt.engine.core.bll.exportimport.ConvertVmCallback]
>>> (EE-ManagedThreadFactory-engineScheduled-Thread-94) [5c66b700] Conversion
>>> of VM from external environment failed: Job
>>> u'7ef7bff2-5766-4f38-ac28-cdd9da4c407c' process failed exit-code: 1
>>>
>>
>> Seems you're trying to import the OVA file backup_server.ova but you
>> provide only the the directory in the "Path" field, right?
>> It doesn't work so well at the moment so better specifying the full path:
>> /rhev/data-center/mnt/import-ova/backup_server.ova
>>
>>
>>>
>>>
>>> --
>>>
>>> Regards
>>>
>>> Hongyu Du
>>> ___
>>> Users mailing list -- users@ovirt.org
>>> To unsubscribe send an email to users-le...@ovirt.org
>>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>>> oVirt Code of Conduct:
>>> https://www.ovirt.org/community/about/community-guidelines/
>>> List Archives:
>>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/WJZOLVOQT2PDEAVUR3TYCY7AHVR7SKOC/
>>>
>>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/TOJ74FJ73CTPOO3UK4OJXNFGQ753HWNI/


[ovirt-users] Re: engine

2018-06-25 Thread Arik Hadas
On Mon, Jun 25, 2018 at 10:37 AM du_hon...@yeah.net 
wrote:

> hi
> thanks ,  I used full path:
> /rhev/data-center/mnt/import-ova/backup_server.ova.
>

Oh, sorry, I looked at a previous attempt.
Yeah, the conversion failed - we'll need the vdsm log and more importantly
the import log from the host.


>
> --
>
> Regards
>
> Hongyu Du
>
>
> *From:* Arik Hadas 
> *Date:* 2018-06-25 14:49
> *To:* du_hongyu 
> *CC:* users 
> *Subject:* Re: [ovirt-users] engine
>
>
> On Mon, Jun 25, 2018 at 9:12 AM du_hon...@yeah.net 
> wrote:
>
>>
>> Hi
>>
>> I export OVA from my ovirt , then want to import the OVA to anther ovirt,
>> but this is failed
>> 2018-06-25 13:52:03,836+08 INFO
>>  [org.ovirt.engine.core.bll.exportimport.ConvertVmCallback]
>> (EE-ManagedThreadFactory-engineScheduled-Thread-94) [5c66b700] Conversion
>> of VM from external environment failed: Job
>> u'7ef7bff2-5766-4f38-ac28-cdd9da4c407c' process failed exit-code: 1
>>
>
> Seems you're trying to import the OVA file backup_server.ova but you
> provide only the the directory in the "Path" field, right?
> It doesn't work so well at the moment so better specifying the full path:
> /rhev/data-center/mnt/import-ova/backup_server.ova
>
>
>>
>>
>> --
>>
>> Regards
>>
>> Hongyu Du
>> ___
>> Users mailing list -- users@ovirt.org
>> To unsubscribe send an email to users-le...@ovirt.org
>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>> oVirt Code of Conduct:
>> https://www.ovirt.org/community/about/community-guidelines/
>> List Archives:
>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/WJZOLVOQT2PDEAVUR3TYCY7AHVR7SKOC/
>>
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/76ZY43FJSGJVDI4QHY5UG5E7CJVVDYA5/


[ovirt-users] Re: engine

2018-06-25 Thread Arik Hadas
On Mon, Jun 25, 2018 at 9:12 AM du_hon...@yeah.net 
wrote:

>
> Hi
>
> I export OVA from my ovirt , then want to import the OVA to anther ovirt,
> but this is failed
> 2018-06-25 13:52:03,836+08 INFO
>  [org.ovirt.engine.core.bll.exportimport.ConvertVmCallback]
> (EE-ManagedThreadFactory-engineScheduled-Thread-94) [5c66b700] Conversion
> of VM from external environment failed: Job
> u'7ef7bff2-5766-4f38-ac28-cdd9da4c407c' process failed exit-code: 1
>

Seems you're trying to import the OVA file backup_server.ova but you
provide only the the directory in the "Path" field, right?
It doesn't work so well at the moment so better specifying the full path:
/rhev/data-center/mnt/import-ova/backup_server.ova


>
>
> --
>
> Regards
>
> Hongyu Du
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/WJZOLVOQT2PDEAVUR3TYCY7AHVR7SKOC/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/D3HICZXCYUO466MYFAPLWBH6IPEKUIJJ/


[ovirt-users] Re: Export as OVA failed

2018-06-22 Thread Arik Hadas
בתאריך יום ו׳, 22 ביוני 2018, 11:20, מאת du_hon...@yeah.net ‏<
du_hon...@yeah.net>:

>
> thanks, I  face another trouble.
> fatal: [192.168.122.211]: FAILED! => {"changed": true, "msg": "non-zero
> return code", "rc": 1, "stderr": "Shared connection to 192.168.122.211
> closed.\r\n", "stdout": "opening for write:
> /rhev/data-center/mnt/192.168.122.26:_exports_vm__exports/backup_server.ova.tmp\r\nwriting
> ovf:  ...
>

Please update to a more recent version, there is a good chance that the
issue you're facing is already resolved.

--
>
> Regards
>
> Hongyu Du
>
>
> *From:* Arik Hadas 
> *Date:* 2018-06-22 15:45
> *To:* du_hongyu 
> *CC:* users 
> *Subject:* Re: Re: [ovirt-users] Export as OVA failed
>
>
> On Fri, Jun 22, 2018 at 10:10 AM du_hon...@yeah.net 
> wrote:
>
>> Hi
>> my ovirt-engine is 4.2.0, how to set a description for each of the VM's
>> disks?
>>
>
> From the webadmin, choose the VM you want to export, browse its disks, for
> each open the edit dialog and set some string in the description field. See
> [1].
>
> [1] https://ibb.co/b5cvS8
>
>
>>
>> --
>>
>> Regards
>>
>> Hongyu Du
>>
>>
>> *From:* Arik Hadas 
>> *Date:* 2018-06-22 14:50
>> *To:* du_hongyu 
>> *CC:* users 
>> *Subject:* Re: [ovirt-users] Export as OVA failed
>>
>>
>> On Fri, Jun 22, 2018 at 9:43 AM du_hon...@yeah.net 
>> wrote:
>>
>>> Hi
>>> I want to export my vm,  I shutdown my vm, then from the three-dot
>>> dropdown select "Export as OVA"
>>> but /var/log/ovirt-engine/engine.log has Exception fail.
>>>
>>
>> You're probably using 4.2.0, right?
>> I would suggest to upgrade to a more recent version of 4.2.
>> Alternatively, you'll need to set a description for each of the VM's disks.
>>
>>
>>>
>>> --
>>>
>>> Regards
>>>
>>> Hongyu Du
>>> ___
>>> Users mailing list -- users@ovirt.org
>>> To unsubscribe send an email to users-le...@ovirt.org
>>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>>> oVirt Code of Conduct:
>>> https://www.ovirt.org/community/about/community-guidelines/
>>> List Archives:
>>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/QOJVXER5YAZN5ANQMCP5V7QC3XBECJFL/
>>>
>>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/JNIVU3AOYZVZ7XDSFXTEWIYGMUFB7GUH/


[ovirt-users] Re: Export as OVA failed

2018-06-22 Thread Arik Hadas
On Fri, Jun 22, 2018 at 10:10 AM du_hon...@yeah.net 
wrote:

> Hi
> my ovirt-engine is 4.2.0, how to set a description for each of the VM's
> disks?
>

>From the webadmin, choose the VM you want to export, browse its disks, for
each open the edit dialog and set some string in the description field. See
[1].

[1] https://ibb.co/b5cvS8


>
> --
>
> Regards
>
> Hongyu Du
>
>
> *From:* Arik Hadas 
> *Date:* 2018-06-22 14:50
> *To:* du_hongyu 
> *CC:* users 
> *Subject:* Re: [ovirt-users] Export as OVA failed
>
>
> On Fri, Jun 22, 2018 at 9:43 AM du_hon...@yeah.net 
> wrote:
>
>> Hi
>> I want to export my vm,  I shutdown my vm, then from the three-dot
>> dropdown select "Export as OVA"
>> but /var/log/ovirt-engine/engine.log has Exception fail.
>>
>
> You're probably using 4.2.0, right?
> I would suggest to upgrade to a more recent version of 4.2. Alternatively,
> you'll need to set a description for each of the VM's disks.
>
>
>>
>> --
>>
>> Regards
>>
>> Hongyu Du
>> ___
>> Users mailing list -- users@ovirt.org
>> To unsubscribe send an email to users-le...@ovirt.org
>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>> oVirt Code of Conduct:
>> https://www.ovirt.org/community/about/community-guidelines/
>> List Archives:
>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/QOJVXER5YAZN5ANQMCP5V7QC3XBECJFL/
>>
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/NADUKEAWD6WPKS46VMTDSNCUANXAF7AS/


[ovirt-users] Re: Export as OVA failed

2018-06-22 Thread Arik Hadas
On Fri, Jun 22, 2018 at 9:43 AM du_hon...@yeah.net 
wrote:

> Hi
> I want to export my vm,  I shutdown my vm, then from the three-dot
> dropdown select "Export as OVA"
> but /var/log/ovirt-engine/engine.log has Exception fail.
>

You're probably using 4.2.0, right?
I would suggest to upgrade to a more recent version of 4.2. Alternatively,
you'll need to set a description for each of the VM's disks.


>
> --
>
> Regards
>
> Hongyu Du
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/QOJVXER5YAZN5ANQMCP5V7QC3XBECJFL/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/3EVT6OGRBGYV4LZ4RJRXDLFM6SGDAKML/


[ovirt-users] Re: oVirt export VM as OVA

2018-06-22 Thread Arik Hadas
On Fri, Jun 22, 2018 at 6:22 AM du_hon...@yeah.net 
wrote:

>
> Hi
> I want to export my vm by "Eports as OVA", but i don't know what to write
> in Directory?
>

That should be the absolute path on the host where you want the OVA file to
be created.
This is mainly intended for a scenario in which you have a shared storage
mounted to some of the hosts in the data center and then you pick one of
those hosts and the directory indicates the mountpoint, e.g., host A and
directory /mnt/export. But the 'directory' can point to a local directory
as well.


> --
>
> Regards
>
> Hongyu Du
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/LSKLCVN3CMCKS3CRI3ITDTPUBZXGA436/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/UJSKZXV6HHP4RY2DIK2JUMVSKZUKWRXI/


[ovirt-users] Re: OVA export/import

2018-06-13 Thread Arik Hadas
On Wed, Jun 13, 2018 at 8:36 PM, RabidCicada  wrote:

> Arik,
> I've opened a bug here with all my information:
> https://bugzilla.redhat.com/show_bug.cgi?id=1590948


Thanks


>
>
> ~Kyle
>
> On Wed, Jun 13, 2018 at 10:04 AM, Arik Hadas  wrote:
> >
> >
> > On Wed, Jun 13, 2018 at 4:58 PM, RabidCicada 
> wrote:
> >>
> >> Thanks for the quick reply,
> >>
> >> I am using 4.2.3 and Ovirt cannot import it's own generated OVA.  That
> >> is why my whole investigation started.  Is it known to work for anyone
> >> else?  Based on your statement it seems like it should be capable of
> >> importing it's own;  But my install, perhaps JUST my install and
> >> no-one elses :), cannot do so.  Can anyone verify import of ovirt
> >> generated OVA's works on ovirt 4.2.3?
> >
> >
> > I would suggest to file a bug and attach the engine and ansible logs so
> we
> > can investigate why it fails for you.
> > It generally works in 4.2.3 but there were some fixes we've made in this
> > area - you may have encountered some of those issues or discovered a new
> one
> > :)
> >
> >>
> >>
> >> ~Kyle
> >>
> >> On Wed, Jun 13, 2018 at 9:54 AM, Arik Hadas  wrote:
> >> >
> >> >
> >> > On Wed, Jun 13, 2018 at 4:04 PM, RabidCicada 
> >> > wrote:
> >> >>
> >> >> All,
> >> >> I recently tried to used the OVA export/import functionality.  It
> >> >> seems I misunderstood the intentions.  I expected OVA export/import
> to
> >> >> be reciprocal functionalities.  I expected what we export as OVA to
> be
> >> >> importable as OVA in ovirt.
> >> >>
> >> >> What I have found is the following:
> >> >>
> >> >> * It seems OVA export does export an OVA, though the format is not
> >> >> spec compliant
> >> >>   * We use 'disk/' in the HostResource xml field instead of '/disk/'
> >> >> for example in the ovf.
> >> >> * It seems OVA import is intended specifically for VMWare OVA's?
> >> >> * I thought I read about export domains being deprecated, and
> >> >> incorrectly assumed the recently added OVA export/import was to make
> >> >> things better for one off import/export.
> >> >>
> >> >>
> >> >> Can anyone clarify the following:
> >> >> * Is OVA import really just VMWare OVA's?
> >> >
> >> >
> >> > No, you can provide OVAs that were generated by oVirt as an input as
> >> > well.
> >> > See examples [1] and [2] for doing this via the python-sdk. Doing that
> >> > from
> >> > the webadmin is trivial is exactly like importing OVA that was
> generated
> >> > by
> >> > VMware.
> >> >
> >> > [1]
> >> >
> >> > https://github.com/oVirt/ovirt-engine-sdk/blob/master/
> sdk/examples/import_vm_from_ova.py
> >> > [2]
> >> >
> >> > https://github.com/oVirt/ovirt-engine-sdk/blob/master/
> sdk/examples/upload_ova_as_vm.py
> >> >
> >> >>
> >> >> * Are we really not spec compliant with the OVA/OVF format as my
> >> >> example above shows?  OR do I misunderstand something?
> >> >
> >> >
> >> > Well, we now use the same code for parsing OVFs that were generated by
> >> > oVirt
> >> > and ones that were generated by VMware. So that's an evidence for
> being
> >> > compliant with the specification to some degree.
> >> >
> >> > Indeed, there may be things that we don't use when reading the OVF,
> like
> >> > the
> >> > field you mentioned, and therefore there may be some gaps here and
> >> > there.
> >> >
> >> > Is this the only gap you found so far? if so then I would say we are
> in
> >> > a
> >> > really good place since fixing that should be trivial, see [3]. You
> are
> >> > more
> >> > than welcome to send a patch!
> >> >
> >> > [3]
> >> >
> >> > https://github.com/oVirt/ovirt-engine/blob/master/
> backend/manager/modules/utils/src/main/java/org/ovirt/
> engine/core/utils/ovf/OvfOvaWriter.java#L179
> >> >
> >> >
> >> >>
> >> >> * After spending my time yesterday,

[ovirt-users] Re: OVA export/import

2018-06-13 Thread Arik Hadas
On Wed, Jun 13, 2018 at 4:58 PM, RabidCicada  wrote:

> Thanks for the quick reply,
>
> I am using 4.2.3 and Ovirt cannot import it's own generated OVA.  That
> is why my whole investigation started.  Is it known to work for anyone
> else?  Based on your statement it seems like it should be capable of
> importing it's own;  But my install, perhaps JUST my install and
> no-one elses :), cannot do so.  Can anyone verify import of ovirt
> generated OVA's works on ovirt 4.2.3?
>

I would suggest to file a bug and attach the engine and ansible logs so we
can investigate why it fails for you.
It generally works in 4.2.3 but there were some fixes we've made in this
area - you may have encountered some of those issues or discovered a new
one :)


>
> ~Kyle
>
> On Wed, Jun 13, 2018 at 9:54 AM, Arik Hadas  wrote:
> >
> >
> > On Wed, Jun 13, 2018 at 4:04 PM, RabidCicada 
> wrote:
> >>
> >> All,
> >> I recently tried to used the OVA export/import functionality.  It
> >> seems I misunderstood the intentions.  I expected OVA export/import to
> >> be reciprocal functionalities.  I expected what we export as OVA to be
> >> importable as OVA in ovirt.
> >>
> >> What I have found is the following:
> >>
> >> * It seems OVA export does export an OVA, though the format is not
> >> spec compliant
> >>   * We use 'disk/' in the HostResource xml field instead of '/disk/'
> >> for example in the ovf.
> >> * It seems OVA import is intended specifically for VMWare OVA's?
> >> * I thought I read about export domains being deprecated, and
> >> incorrectly assumed the recently added OVA export/import was to make
> >> things better for one off import/export.
> >>
> >>
> >> Can anyone clarify the following:
> >> * Is OVA import really just VMWare OVA's?
> >
> >
> > No, you can provide OVAs that were generated by oVirt as an input as
> well.
> > See examples [1] and [2] for doing this via the python-sdk. Doing that
> from
> > the webadmin is trivial is exactly like importing OVA that was generated
> by
> > VMware.
> >
> > [1]
> > https://github.com/oVirt/ovirt-engine-sdk/blob/master/
> sdk/examples/import_vm_from_ova.py
> > [2]
> > https://github.com/oVirt/ovirt-engine-sdk/blob/master/
> sdk/examples/upload_ova_as_vm.py
> >
> >>
> >> * Are we really not spec compliant with the OVA/OVF format as my
> >> example above shows?  OR do I misunderstand something?
> >
> >
> > Well, we now use the same code for parsing OVFs that were generated by
> oVirt
> > and ones that were generated by VMware. So that's an evidence for being
> > compliant with the specification to some degree.
> >
> > Indeed, there may be things that we don't use when reading the OVF, like
> the
> > field you mentioned, and therefore there may be some gaps here and there.
> >
> > Is this the only gap you found so far? if so then I would say we are in a
> > really good place since fixing that should be trivial, see [3]. You are
> more
> > than welcome to send a patch!
> >
> > [3]
> > https://github.com/oVirt/ovirt-engine/blob/master/
> backend/manager/modules/utils/src/main/java/org/ovirt/
> engine/core/utils/ovf/OvfOvaWriter.java#L179
> >
> >
> >>
> >> * After spending my time yesterday, I recall now that the deprecation
> >> of export domain is in favor of detaching and re-attaching ANY data
> >> domain.
> >
> >
> > Depending what you're looking for.
> > If you want to *move* your entities (VMs/templates) from one deployment
> to
> > another then sure, detach the domain (that will cause those entities to
> be
> > deleted from the source environment), attach the domain to the new
> > deployment and register the entities you want. That is relatively quick
> > operation since no copy is needed.
> >
> > Export domains/OVAs are targeted for different scenario - when you want
> to
> > *copy* you entities from one deployment to another. You export them
> > somewhere and than import them from that place.
> >
> >>
> >> * What is the purpose of our OVA export if we ourselves indeed cannot
> >> import our own OVA?  Or can you tell me how we import our own if I'm
> >> wrong.
> >
> >
> > Already answered.
> >
> >>
> >>
> >> Please feel free to overshare details :), as any context will help
> >> prevent more confusion on my part.
> >>
> >> ~Kyle
> >> _

[ovirt-users] Re: OVA export/import

2018-06-13 Thread Arik Hadas
On Wed, Jun 13, 2018 at 4:04 PM, RabidCicada  wrote:

> All,
> I recently tried to used the OVA export/import functionality.  It
> seems I misunderstood the intentions.  I expected OVA export/import to
> be reciprocal functionalities.  I expected what we export as OVA to be
> importable as OVA in ovirt.
>
> What I have found is the following:
>
> * It seems OVA export does export an OVA, though the format is not
> spec compliant
>   * We use 'disk/' in the HostResource xml field instead of '/disk/'
> for example in the ovf.
> * It seems OVA import is intended specifically for VMWare OVA's?
> * I thought I read about export domains being deprecated, and
> incorrectly assumed the recently added OVA export/import was to make
> things better for one off import/export.
>
>
> Can anyone clarify the following:
> * Is OVA import really just VMWare OVA's?
>

No, you can provide OVAs that were generated by oVirt as an input as well.
See examples [1] and [2] for doing this via the python-sdk. Doing that from
the webadmin is trivial is exactly like importing OVA that was generated by
VMware.

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


> * Are we really not spec compliant with the OVA/OVF format as my
> example above shows?  OR do I misunderstand something?
>

Well, we now use the same code for parsing OVFs that were generated by
oVirt and ones that were generated by VMware. So that's an evidence for
being compliant with the specification to some degree.

Indeed, there may be things that we don't use when reading the OVF, like
the field you mentioned, and therefore there may be some gaps here and
there.

Is this the only gap you found so far? if so then I would say we are in a
really good place since fixing that should be trivial, see [3]. You are
more than welcome to send a patch!

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



> * After spending my time yesterday, I recall now that the deprecation
> of export domain is in favor of detaching and re-attaching ANY data
> domain.
>

Depending what you're looking for.
If you want to *move* your entities (VMs/templates) from one deployment to
another then sure, detach the domain (that will cause those entities to be
deleted from the source environment), attach the domain to the new
deployment and register the entities you want. That is relatively quick
operation since no copy is needed.

Export domains/OVAs are targeted for different scenario - when you want to
*copy* you entities from one deployment to another. You export them
somewhere and than import them from that place.


> * What is the purpose of our OVA export if we ourselves indeed cannot
> import our own OVA?  Or can you tell me how we import our own if I'm
> wrong.
>

Already answered.


>
> Please feel free to overshare details :), as any context will help
> prevent more confusion on my part.
>
> ~Kyle
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-
> guidelines/
> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/
> message/MYWHJF4ZJS4VSJ2RWBSYDPPOWTI6VWW5/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/X5QRB74Z7WMEEWSPBOTVNN45RMJT3J4F/


[ovirt-users] Re: Failure to import a VM

2018-06-01 Thread Arik Hadas
36a1e4cd] Command
> [id=ba2a1ec9-36b3-451b-b6b9-2b2d698ed900]: Compensating TRANSIENT_ENTITY
> of org.ovirt.engine.core.common.businessentities.
> ReleaseMacsTransientCompensation; snapshot: org.ovirt.engine.core.common.
> businessentities.ReleaseMacsTransientCompensation@3306fa7b.
> 2018-06-01 13:00:43,649Z INFO  [org.ovirt.engine.core.bll.CommandCompensator]
> (EE-ManagedThreadFactory-engineScheduled-Thread-87) [36a1e4cd] Command
> [id=ba2a1ec9-36b3-451b-b6b9-2b2d698ed900]: Compensating NEW_ENTITY_ID of
> org.ovirt.engine.core.common.businessentities.network.VmNetworkStatistics;
> snapshot: afafda74-57f4-4f79-83a4-d875461ab557.
> 2018-06-01 13:00:43,649Z INFO  [org.ovirt.engine.core.bll.CommandCompensator]
> (EE-ManagedThreadFactory-engineScheduled-Thread-87) [36a1e4cd] Command
> [id=ba2a1ec9-36b3-451b-b6b9-2b2d698ed900]: Compensating NEW_ENTITY_ID of
> org.ovirt.engine.core.common.businessentities.network.VmNetworkInterface;
> snapshot: afafda74-57f4-4f79-83a4-d875461ab557.
> 2018-06-01 13:00:43,650Z INFO  [org.ovirt.engine.core.bll.CommandCompensator]
> (EE-ManagedThreadFactory-engineScheduled-Thread-87) [36a1e4cd] Command
> [id=ba2a1ec9-36b3-451b-b6b9-2b2d698ed900]: Compensating TRANSIENT_ENTITY
> of org.ovirt.engine.core.common.businessentities.
> ReleaseMacsTransientCompensation; snapshot: org.ovirt.engine.core.common.
> businessentities.ReleaseMacsTransientCompensation@53a4230e.
> 2018-06-01 13:00:43,651Z INFO  [org.ovirt.engine.core.bll.CommandCompensator]
> (EE-ManagedThreadFactory-engineScheduled-Thread-87) [36a1e4cd] Command
> [id=ba2a1ec9-36b3-451b-b6b9-2b2d698ed900]: Compensating NEW_ENTITY_ID of
> org.ovirt.engine.core.common.businessentities.VmStatistics; snapshot:
> 632fec81-6271-4ae7-866e-2aad43530594.
> 2018-06-01 13:00:43,651Z INFO  [org.ovirt.engine.core.bll.CommandCompensator]
> (EE-ManagedThreadFactory-engineScheduled-Thread-87) [36a1e4cd] Command
> [id=ba2a1ec9-36b3-451b-b6b9-2b2d698ed900]: Compensating NEW_ENTITY_ID of
> org.ovirt.engine.core.common.businessentities.VmDynamic; snapshot:
> 632fec81-6271-4ae7-866e-2aad43530594.
> 2018-06-01 13:00:43,652Z INFO  [org.ovirt.engine.core.bll.CommandCompensator]
> (EE-ManagedThreadFactory-engineScheduled-Thread-87) [36a1e4cd] Command
> [id=ba2a1ec9-36b3-451b-b6b9-2b2d698ed900]: Compensating NEW_ENTITY_ID of
> org.ovirt.engine.core.common.businessentities.Snapshot; snapshot:
> bf4518c0-1624-49f7-82be-2b079bfe0111.
> 2018-06-01 13:00:43,653Z INFO  [org.ovirt.engine.core.bll.CommandCompensator]
> (EE-ManagedThreadFactory-engineScheduled-Thread-87) [36a1e4cd] Command
> [id=ba2a1ec9-36b3-451b-b6b9-2b2d698ed900]: Compensating NEW_ENTITY_ID of
> org.ovirt.engine.core.common.businessentities.VmStatic; snapshot:
> 632fec81-6271-4ae7-866e-2aad43530594.
> 2018-06-01 13:00:43,677Z INFO  
> [org.ovirt.engine.core.bll.exportimport.ImportVmFromOvaCommand]
> (EE-ManagedThreadFactory-engineScheduled-Thread-87) [36a1e4cd] Lock freed
> to object 'EngineLock:{exclusiveLocks='[PA-VM-8.0.0=VM_NAME,
> 632fec81-6271-4ae7-866e-2aad43530594=VM]', sharedLocks=''}'
> 2018-06-01 13:00:43,702Z ERROR [org.ovirt.engine.core.dal.
> dbbroker.auditloghandling.AuditLogDirector] 
> (EE-ManagedThreadFactory-engineScheduled-Thread-87)
> [36a1e4cd] *EVENT_ID: IMPORTEXPORT_IMPORT_VM_FAILED(1,153), Failed to
> import Vm PA-VM-8.0.0 to Data Center DC2, Cluster Cluster2*
> 2018-06-01 13:00:46,438Z INFO  [org.ovirt.engine.core.bll.tasks.SPMAsyncTask]
> (EE-ManagedThreadFactory-engineScheduled-Thread-80) [] Task id
> '0eee4fa8-16eb-4211-9ef1-9a8081952028' is in pre-polling  period and
> should not be polled. Pre-polling period is 6 millis.
> 2018-06-01 13:00:56,439Z INFO  [org.ovirt.engine.core.bll.tasks.SPMAsyncTask]
> (EE-ManagedThreadFactory-engineScheduled-Thread-33) [] Task id
> '0eee4fa8-16eb-4211-9ef1-9a8081952028' is in pre-polling  period and
> should not be polled. Pre-polling period is 6 millis.
> 2018-06-01 13:01:06,440Z INFO  [org.ovirt.engine.core.bll.tasks.SPMAsyncTask]
> (EE-ManagedThreadFactory-engineScheduled-Thread-95) [] Task id
> '0eee4fa8-16eb-4211-9ef1-9a8081952028' is in pre-polling  period and
> should not be polled. Pre-polling period is 6 millis.
> 2018-06-01 13:01:16,274Z INFO  
> [org.ovirt.engine.core.bll.tasks.AsyncTaskManager]
> (EE-ManagedThreadFactory-engineScheduled-Thread-5) [] Setting new tasks
> map. The map contains now 1 tasks
>
> 
> -
>
>
> Best regards
>
> On Mon, May 28, 2018 at 5:57 PM, Arik Hadas  wrote:
>
>>
>>
>> On Mon, May 28, 2018 at 7:55 PM, Aziz  wrote:
>>
>>> Hi All,
>>>
>>> I'm getting an error when trying to import an OVA file to my oVirt. It
>>> seems 

[ovirt-users] Re: VM status and issue with cloud_init

2018-05-31 Thread Arik Hadas
On Thu, May 31, 2018 at 10:08 AM, 03CE 007 <03ce...@gmail.com> wrote:

> Ok thanks, when you say guest agent, could you please provide the full
> name and how to have it installed, and I am assuming it should be installed
> on the the engineVM or the new VM I want to spin and boot up.
>

Generally speaking, we are transitioning from ovirt-guest-agent to
qemu-guest-agent.
I don't know what's the status of this transition with respect to centos as
I typically use latest-fedora.
Tomas, can you please advice what needs to be installed in centos 7.4?

And it should be installed in the new VM.


>
> On Thu, 31 May 2018, 7:57 am Arik Hadas,  wrote:
>
>>
>>
>> On Wed, May 30, 2018 at 7:30 PM, <03ce...@gmail.com> wrote:
>>
>>> Some what new to the VM and Ovirt world here and need some help
>>> understanding terminologies and get the VM to work as per requirement.
>>>
>>> I have a self-hosted-engine (4.2) running on centos (7.4). The engine is
>>> in good health and I have deployed a test VM using below playbook
>>> successfully. It is currently in "up" state.
>>>
>>>
>>> - name: oVirt Self-Hosted-Engine - Manage VMs
>>>   hosts: hypervisor_ovirt
>>>   gather_facts: false
>>>
>>>   vars_files:
>>> # Contains encrypted `engine_password` varibale using ansible-vault
>>> - ovirt-secrets.yml
>>>
>>>   vars:
>>> engine_url: https://engine-ovirt.dw/ovirt-engine/api
>>> engine_user: admin@internal
>>> engine_cafile: /etc/pki/ovirt-engine/ca.pem
>>>
>>> mytest_vm:
>>>   cluster: Default
>>>   memory: 64GiB
>>>   memory_guaranteed: 1GiB
>>>   cores: 2
>>>   nics:
>>> - name: vnet0
>>>   network: ovirtmgmt
>>>   profile: ovirtmgmt
>>>   interface: virtio
>>>   wait: true
>>>   domain: node.dev.dw
>>>   os_type: rhel_7x64
>>>   ssh_key: ssh-rsa AAA...LGx user01@mytestvm
>>>   root_password: super_password
>>>   disks:
>>> - size: 20GiB
>>>   name: data
>>>   storage_domain: hosted_storage
>>>   interface: virtio
>>>   bootable: true
>>>   nics:
>>> - name: vnet0
>>>   network: ovirtmgmt
>>>   profile: ovirtmgmt
>>>   interface: virtio
>>>
>>> vms:
>>>   - name: mytest_vm
>>> tag: mytest_vm
>>> profile: "{{ mytest_vm }}"
>>> cloud_init:
>>>   dns_servers:
>>> - 10.90.x.1
>>> - 10.90.x.1
>>>   nic_boot_protocol: static
>>>   nic_ip_address: 10.90.x.y
>>>   nic_netmask: 255.255.255.0
>>>   nic_gateway: 10.90.x.z
>>>   nic_name: eth0
>>>   nic_on_boot: true
>>>   host_name: mytestvm.test.dw
>>>   custom_script: |
>>> write_files:
>>>  - content: |
>>>  Hello, world!
>>>path: /tmp/greeting.txt
>>>permissions: '0644'
>>>   user_name: root
>>>   root_password: super_password
>>> cloud_init_persist: true
>>>
>>>   roles:
>>> - oVirt.vm-infra
>>>
>>>
>>> Above playbook runs fine, but when i see summary using ovirt4.py, i do
>>> not see ipaddr for this test vm.
>>>
>>> - I do not see the ipaddr for this VM despite specifying it using
>>> cloud_init
>>>
>>
>> You need to install a guest agent in order to be provided with ip
>> addresses.
>>
>>
>>> - does the "up" status mean it has "booted" or I need to do something
>>> else to boot it with centos 7.4 minimal
>>>
>>
>> Without a guest agent installed we know nothing about the state of the
>> guest so in this case the UP status only means that the VM process is
>> running for more than 1 minute.
>>
>>
>>>
>>> Thank you in advance.
>>> ___
>>> Users mailing list -- users@ovirt.org
>>> To unsubscribe send an email to users-le...@ovirt.org
>>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>>> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-
>>> guidelines/
>>> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/
>>> message/YF635QVUMPZTMVX3CMPSNUORXK527OFA/
>>>
>>
>>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/RNDG6JSHOCRPT2OX4OJZFGK4CVTEH4LB/


[ovirt-users] Re: VM status and issue with cloud_init

2018-05-31 Thread Arik Hadas
On Wed, May 30, 2018 at 7:30 PM, <03ce...@gmail.com> wrote:

> Some what new to the VM and Ovirt world here and need some help
> understanding terminologies and get the VM to work as per requirement.
>
> I have a self-hosted-engine (4.2) running on centos (7.4). The engine is
> in good health and I have deployed a test VM using below playbook
> successfully. It is currently in "up" state.
>
>
> - name: oVirt Self-Hosted-Engine - Manage VMs
>   hosts: hypervisor_ovirt
>   gather_facts: false
>
>   vars_files:
> # Contains encrypted `engine_password` varibale using ansible-vault
> - ovirt-secrets.yml
>
>   vars:
> engine_url: https://engine-ovirt.dw/ovirt-engine/api
> engine_user: admin@internal
> engine_cafile: /etc/pki/ovirt-engine/ca.pem
>
> mytest_vm:
>   cluster: Default
>   memory: 64GiB
>   memory_guaranteed: 1GiB
>   cores: 2
>   nics:
> - name: vnet0
>   network: ovirtmgmt
>   profile: ovirtmgmt
>   interface: virtio
>   wait: true
>   domain: node.dev.dw
>   os_type: rhel_7x64
>   ssh_key: ssh-rsa AAA...LGx user01@mytestvm
>   root_password: super_password
>   disks:
> - size: 20GiB
>   name: data
>   storage_domain: hosted_storage
>   interface: virtio
>   bootable: true
>   nics:
> - name: vnet0
>   network: ovirtmgmt
>   profile: ovirtmgmt
>   interface: virtio
>
> vms:
>   - name: mytest_vm
> tag: mytest_vm
> profile: "{{ mytest_vm }}"
> cloud_init:
>   dns_servers:
> - 10.90.x.1
> - 10.90.x.1
>   nic_boot_protocol: static
>   nic_ip_address: 10.90.x.y
>   nic_netmask: 255.255.255.0
>   nic_gateway: 10.90.x.z
>   nic_name: eth0
>   nic_on_boot: true
>   host_name: mytestvm.test.dw
>   custom_script: |
> write_files:
>  - content: |
>  Hello, world!
>path: /tmp/greeting.txt
>permissions: '0644'
>   user_name: root
>   root_password: super_password
> cloud_init_persist: true
>
>   roles:
> - oVirt.vm-infra
>
>
> Above playbook runs fine, but when i see summary using ovirt4.py, i do not
> see ipaddr for this test vm.
>
> - I do not see the ipaddr for this VM despite specifying it using
> cloud_init
>

You need to install a guest agent in order to be provided with ip addresses.


> - does the "up" status mean it has "booted" or I need to do something else
> to boot it with centos 7.4 minimal
>

Without a guest agent installed we know nothing about the state of the
guest so in this case the UP status only means that the VM process is
running for more than 1 minute.


>
> Thank you in advance.
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-
> guidelines/
> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/
> message/YF635QVUMPZTMVX3CMPSNUORXK527OFA/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/V2EKYKSS3C2PKZ7LG5CQDAREHONMK6PR/


[ovirt-users] Re: [Qemu-block] Libvirt ERROR cannot access backing file after importing VM from OpenStack

2018-05-30 Thread Arik Hadas
On Wed, May 30, 2018 at 6:33 PM, Kevin Wolf  wrote:

> Am 30.05.2018 um 17:05 hat Eric Blake geschrieben:
> > If I understood the question, we start with a local:
> >
> > T (any format) <- S (qcow2) <- V (qcow2)
> >
> > and want to create a remote tar file:
> >
> > dest.tar == | header ... | qcow2 image |
> >
> > where we write a single collapsed view of the T<-S<-V chain as a qcow2
> image
> > in the subset of the remote tar file.
>
> I think the problem is that we're talking about two different things in
> one thread. If I understand correctly, what oVirt does today is:
>
> 1. qemu-img convert to create a temporary qcow2 image that merges the
>whole backing chain in a single file
>
> 2. tar to create an temporary OVA archive that contains, amongst others,
>the temporary qcow2 image. This is a second temporary file.
>
> 3. Stream this temporary OVA archive over HTTP
>

Well, today we suggest users to mount a shared storage to multiple hosts
that reside in different oVirt/RHV deployments so they could export
VMs/templates as OVAs to that shared storage and import these OVAs from the
shared storage to a destination deployment. This process involves only #1
and #2.

The technique you proposed earlier for writing disks directly into an OVA,
assuming that the target size can be retrieved with 'qemu-img measure',
sounds like a nice approach to accelerate this process. I think we should
really consider doing that if that's as easy as it sounds.

But #3 is definitely something we are interested in because we expect the
next step to be exporting the OVAs to a remote instance of Glance that
serves as a shared repository for the different deployments. Being able to
stream the collapsed form of a volume chain without writing anything to the
storage device would be fantastic. I think that even at the expense of
iterating the chain twice - once to map the structure of the jump tables
(right?) and once to stream the whole data.


>
> Your proposal is about getting rid of the temporary file from step 1,
> but keeping the temporary file from step 2. I was kind of ignoring
> step 2 and answering how you can avoid a temporary file by creating and
> streaming a qcow2 file in a single step, but if you already have the
> code to create a qcow2 image as a stream, adding a tar header as well
> shouldn't be that hard...
>
> I think Nir was talking about both.
>
> Ideally, we'd somehow get rid of HTTP, which introduces the requirement
> of a non-seekable stream.
>
> > So, first use qemu-img to learn how big to size the collapsed qcow2
> image,
> > and by extension, the overall tar image
> > $ qemu-img measure -f qcow2 -O qcow2 V
> >
> > then pre-create a large enough tar file on the destination
> > $ create header
> > $ truncate --size=XXX dest.qcow2
> > $ tar cf dest.tar header dest.qcow2
> >
> > (note that I explicitly did NOT use tar --sparse; dest.qcow2 is sparse
> and
> > occupies practically no disk space, but dest.tar must NOT be sparse
> because
> > neither tar nor NBD work well with after-the-fact resizing)
> >
> > then set up an NBD server on the destination that can write to the
> subset of
> > the tar file:
> >
> > $ learn the offset of dest.qcow2 within dest.tar (probably a multiple of
> > 10240, given default GNU tar options)
> > $ qemu-nbd --image-opts
> > driver=raw,offset=YYY,size=XXX,file.driver=file,file.filename=dest.tar
> >
> > (I'm not sure if I got the --image-opts syntax exactly correct.  nbdkit
> has
> > more examples of learning offsets within a tar file, and may be a better
> > option as a server than qemu-nbd - but the point remains: serve up the
> > subset of the dest.tar file as raw bytes)
> >
> > finally set up qemu as an NBD client on the source:
> > $ qemu-img convert -f qcow2 V -O qcow2 nbd://remote
> >
> > (now the client collapses the qcow2 chain onto the source, and writes
> that
> > into a qcow2 subset of the tar file on the destination, where the
> > destination was already sized large enough to hold the qcow2 image, and
> > where no other temporary storage was needed other than the sparse
> dest.qcow2
> > used in creating a large enough tar file)
>
> You added another host into the mix, which just receives the image
> content via NBD and then re-exports it as HTTP. Does this host actually
> exist or is it the same host where the original images are located?
>
> Because if you stay local for this step, there is no need to use NBD at
> all:
>
> $ ./qemu-img measure -O qcow2 ~/images/hd.img
> required size: 67436544
> fully allocated size: 67436544
> $ ./qemu-img create -f file /tmp/test.qcow2 67436544
> Formatting '/tmp/test.qcow2', fmt=file size=67436544
> $ ./qemu-img convert -n --target-image-opts ~/images/hd.img
> driver=raw,file.driver=file,file.filename=/tmp/test.qcow2,offset=65536
>
> hexdump verifies that this does the expected thing.
>
> > > Exporting to a stream is possible if we're allowed to make two passes
> > > over the source, but the existing QEMU code is useless for 

[ovirt-users] Re: Failure to import a VM

2018-05-28 Thread Arik Hadas
On Mon, May 28, 2018 at 7:55 PM, Aziz  wrote:

> Hi All,
>
> I'm getting an error when trying to import an OVA file to my oVirt. It
> seems that a JAVA command is failing with an exception :
>
> Here are the logs from the engine.log file, while importing the OVA file.
>
> 2018-05-28 16:47:09,491Z ERROR 
> [org.ovirt.engine.core.bll.exportimport.ImportVmFromOvaCommand]
> (EE-ManagedThreadFactory-engine-Thread-19767) 
> [e0306ff3-db73-4030-924b-57d86023db28]
> Command 'org.ovirt.engine.core.bll.exportimport.ImportVmFromOvaCommand'
> failed: For input string: ""
> 2018-05-28 16:47:09,491Z ERROR 
> [org.ovirt.engine.core.bll.exportimport.ImportVmFromOvaCommand]
> (EE-ManagedThreadFactory-engine-Thread-19767) 
> [e0306ff3-db73-4030-924b-57d86023db28]
> Exception: java.lang.NumberFormatException: For input string: ""
> at 
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> [rt.jar:1.8.0_171]
> at java.lang.Long.parseLong(Long.java:601) [rt.jar:1.8.0_171]
> at 
> org.ovirt.engine.core.utils.MacAddressRangeUtils.macToLong(MacAddressRangeUtils.java:124)
> [utils.jar:]
> at org.ovirt.engine.core.bll.network.macpool.MacPoolUsingRanges.
> isMacInRange(MacPoolUsingRanges.java:193) [bll.jar:]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [rt.jar:1.8.0_171]
> at sun.reflect.NativeMethodAccessorImpl.invoke(
> NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_171]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_171]
> at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_171]
> at org.ovirt.engine.core.utils.lock.LockedObjectFactory$
> LockingInvocationHandler.invoke(LockedObjectFactory.java:66) [utils.jar:]
> at com.sun.proxy.$Proxy187.isMacInRange(Unknown Source)
> at java.util.function.Predicate.lambda$negate$1(Predicate.java:80)
> [rt.jar:1.8.0_171]
> at 
> java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:174)
> [rt.jar:1.8.0_171]
> at 
> java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175)
> [rt.jar:1.8.0_171]
> at 
> java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193)
> [rt.jar:1.8.0_171]
> at java.util.ArrayList$ArrayListSpliterator.
> forEachRemaining(ArrayList.java:1382) [rt.jar:1.8.0_171]
> at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
> [rt.jar:1.8.0_171]
> at 
> java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
> [rt.jar:1.8.0_171]
> at 
> java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708)
> [rt.jar:1.8.0_171]
> at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> [rt.jar:1.8.0_171]
> at java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:499)
> [rt.jar:1.8.0_171]
> at org.ovirt.engine.core.bll.network.vm.ExternalVmMacsFinder.
> findExternalMacAddresses(ExternalVmMacsFinder.java:37) [bll.jar:]
> at org.ovirt.engine.core.bll.exportimport.ImportVmCommandBase.
> reportExternalMacs(ImportVmCommandBase.java:512) [bll.jar:]
> at org.ovirt.engine.core.bll.exportimport.ImportVmCommandBase.
> addVmInterfaces(ImportVmCommandBase.java:640) [bll.jar:]
> at org.ovirt.engine.core.bll.exportimport.ImportVmCommandBase.lambda$
> addVmToDb$2(ImportVmCommandBase.java:533) [bll.jar:]
> at org.ovirt.engine.core.utils.transaction.TransactionSupport.
> executeInNewTransaction(TransactionSupport.java:202) [utils.jar:]
> at org.ovirt.engine.core.bll.exportimport.
> ImportVmCommandBase.addVmToDb(ImportVmCommandBase.java:529) [bll.jar:]
> at org.ovirt.engine.core.bll.exportimport.
> ImportVmFromExternalProviderCommand.addVmToDb(
> ImportVmFromExternalProviderCommand.java:364) [bll.jar:]
> at org.ovirt.engine.core.bll.exportimport.ImportVmCommandBase.
> executeVmCommand(ImportVmCommandBase.java:474) [bll.jar:]
> at org.ovirt.engine.core.bll.VmCommand.executeCommand(VmCommand.java:161)
> [bll.jar:]
> at 
> org.ovirt.engine.core.bll.CommandBase.executeWithoutTransaction(CommandBase.java:1133)
> [bll.jar:]
> at org.ovirt.engine.core.bll.CommandBase.
> executeActionInTransactionScope(CommandBase.java:1285) [bll.jar:]
> at 
> org.ovirt.engine.core.bll.CommandBase.runInTransaction(CommandBase.java:1934)
> [bll.jar:]
> at org.ovirt.engine.core.utils.transaction.TransactionSupport.
> executeInSuppressed(TransactionSupport.java:164) [utils.jar:]
> at org.ovirt.engine.core.utils.transaction.TransactionSupport.
> executeInScope(TransactionSupport.java:103) [utils.jar:]
> at org.ovirt.engine.core.bll.CommandBase.execute(CommandBase.java:1345)
> [bll.jar:]
> at 
> org.ovirt.engine.core.bll.CommandBase.executeAction(CommandBase.java:400)
> [bll.jar:]
> at org.ovirt.engine.core.bll.PrevalidatingMultipleActionsRu
> nner.executeValidatedCommand(PrevalidatingMultipleActionsRunner.java:204)
> [bll.jar:]
> at 

[ovirt-users] Re: Libvirt ERROR cannot access backing file after importing VM from OpenStack

2018-05-28 Thread Arik Hadas
On Mon, May 28, 2018 at 11:25 AM, Kevin Wolf <kw...@redhat.com> wrote:

> [ Adding qemu-block ]
>
> Am 27.05.2018 um 10:36 hat Arik Hadas geschrieben:
> > On Thu, May 24, 2018 at 6:13 PM, Nir Soffer <nsof...@redhat.com> wrote:
> >
> > > On Thu, May 24, 2018 at 6:06 PM Vrgotic, Marko <
> m.vrgo...@activevideo.com>
> > > wrote:
> > >
> > >> Dear Nir,
> > >>
> > >> Thank you for quick reply.
> > >>
> > >> Ok, why it will not work?
> > >>
> > >
> > > Because the image has a backing file which is not accessible to oVirt.
> > >
> > >
> > >> I used qemu+tcp connection, via import method through engine admin UI.
> > >>
> > >> Images was imported and converted according logs, still “backing file”
> > >> invalid entry remained.
> > >>
> > >> Also, I did use same method before, connecting to plain “libvirt kvm”
> > >> host, import and conversion went smooth, no backend file.
> > >>
> > >> Image format is qcow(2) which is supported by oVirt.
> > >>
> > >> What am I missing? Should I use different method?
> > >>
> > >
> > > I guess this is not a problem on your side, but a bug in our side.
> > >
> > > Either we should block the operation that cannot work, or fix the
> process
> > > so we don't refer to non-existing image.
> > >
> > > When importing we have 2 options:
> > >
> > > - import the entire chain,  importing all images in the chain,
> converting
> > >  each image to oVirt volume, and updating the backing file of each
> layer
> > > to point to the oVirt image.
> > >
> > > - import the current state of the image into a new image, using either
> raw
> > > or qcow2, but without any backing file.
> > >
> > > Arik, do you know why we create qcow2 file with invalid backing file?
> > >
> >
> > It seems to be a result of a bit naive behavior of the kvm2ovirt module
> > that tries to download only the top-level volume the VM uses, assuming
> each
> > of the disks to be imported is comprised of a single volume.
> >
> > Maybe it's time to finally asking QEMU guys to provide a way to consume
> the
> > 'collapsed' form of a chain of volumes as a stream if that's not
> available
> > yet? ;) It can also boost the recently added process of exporting VMs as
> > OVAs...
>
> Not sure which operation we're talking about on the QEMU level, but
> generally the "collapsed" view is the normal thing because that's what
> guests see.
>
> For example, if you use 'qemu-img convert', you have to pass options to
> specifically disable it and convert only a single layer if you want to
> keep using backing files instead of getting a standalone image that
> contains everything.
>

Yeah, some context was missing. Sorry about that.

Let me demonstrate briefly the flow for OVA:
Let's say that we have a VM that is based on a template and has one disk
and one snapshot, so its volume-chain would be:
T -> S -> V
(V is the volume the VM writes to, S is the backing file of V and T is the
backing file of S).
When exporting that VM to an OVA file we want the produced tar file to be
comprised of:
(1) OVF configuration
(2) single disk volume (preferably qcow).

So we need to collapse T, S, V into a single volume.
Sure, we can do 'qemu-img convert'. That's what we do now in oVirt 4.2:
(a) qemu-img convert produces a 'temporary' collapsed volume
(b) make a tar file of the OVf configuration and that 'temporary' volume
(c) delete the temporary volume

But the fact that we produce that 'temporary' volume obviously slows down
the entire operation.
It would be much better if we could "open" a stream that we can read from
the 'collapsed' form of that chain and stream it directly into the
appropriate tar file entry, without extra writes to the storage device.

Few months ago people from the oVirt-storage team checked the qemu toolset
and replied that this capability is not yet provided, therefore we
implemented the workaround described above. Apparently, the desired ability
can also be useful for the flow discussed in this thread so it worth asking
for it again :)


>
> Kevin
>
> >
> > >
> > > Nir
> > >
> > >
> > >>
> > >> Kindly awaiting your reply.
> > >>
> > >> — — —
> > >> Met vriendelijke groet / Best regards,
> > >>
> > >> Marko Vrgotic
> > >> Sr. System Engineer
> > >> ActiveVideo
> > >

[ovirt-users] Re: Libvirt ERROR cannot access backing file after importing VM from OpenStack

2018-05-27 Thread Arik Hadas
On Thu, May 24, 2018 at 6:13 PM, Nir Soffer <nsof...@redhat.com> wrote:

> On Thu, May 24, 2018 at 6:06 PM Vrgotic, Marko <m.vrgo...@activevideo.com>
> wrote:
>
>> Dear Nir,
>>
>> Thank you for quick reply.
>>
>> Ok, why it will not work?
>>
>
> Because the image has a backing file which is not accessible to oVirt.
>
>
>> I used qemu+tcp connection, via import method through engine admin UI.
>>
>> Images was imported and converted according logs, still “backing file”
>> invalid entry remained.
>>
>> Also, I did use same method before, connecting to plain “libvirt kvm”
>> host, import and conversion went smooth, no backend file.
>>
>> Image format is qcow(2) which is supported by oVirt.
>>
>> What am I missing? Should I use different method?
>>
>
> I guess this is not a problem on your side, but a bug in our side.
>
> Either we should block the operation that cannot work, or fix the process
> so we don't refer to non-existing image.
>
> When importing we have 2 options:
>
> - import the entire chain,  importing all images in the chain, converting
>  each image to oVirt volume, and updating the backing file of each layer
> to point to the oVirt image.
>
> - import the current state of the image into a new image, using either raw
> or qcow2, but without any backing file.
>
> Arik, do you know why we create qcow2 file with invalid backing file?
>

It seems to be a result of a bit naive behavior of the kvm2ovirt module
that tries to download only the top-level volume the VM uses, assuming each
of the disks to be imported is comprised of a single volume.

Maybe it's time to finally asking QEMU guys to provide a way to consume the
'collapsed' form of a chain of volumes as a stream if that's not available
yet? ;) It can also boost the recently added process of exporting VMs as
OVAs...


>
> Nir
>
>
>>
>> Kindly awaiting your reply.
>>
>> — — —
>> Met vriendelijke groet / Best regards,
>>
>> Marko Vrgotic
>> Sr. System Engineer
>> ActiveVideo
>>
>> Tel. +31 (0)35 677 4131 <+31%2035%20677%204131>
>> email: m.vrgo...@activevideo.com
>> skype: av.mvrgotic.se
>> www.activevideo.com
>> --
>> *From:* Nir Soffer <nsof...@redhat.com>
>> *Sent:* Thursday, May 24, 2018 4:09:40 PM
>> *To:* Vrgotic, Marko
>> *Cc:* users@ovirt.org; Richard W.M. Jones; Arik Hadas
>> *Subject:* Re: [ovirt-users] Libvirt ERROR cannot access backing file
>> after importing VM from OpenStack
>>
>>
>>
>> On Thu, May 24, 2018 at 5:05 PM Vrgotic, Marko <m.vrgo...@activevideo.com>
>> wrote:
>>
>> Dear oVirt team,
>>
>>
>>
>> When trying to start imported VM, it fails with following message:
>>
>>
>>
>> ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
>> (ForkJoinPool-1-worker-2) [] EVENT_ID: VM_DOWN_ERROR(119), VM
>> instance-0673 is down with error. Exit message: Cannot access backing
>> file '/var/lib/nova/instances/_base/2f4f8c5fc11bb83bcab03f4c829ddda4da8c0bce'
>> of storage file '/rhev/data-center/mnt/glusterSD/aws-gfs-01.awesome.
>> lan:_gv0__he/2607c265-248c-40ad-b020-f3756454839e/images/
>> 816ac00f-ba98-4827-b5c8-42a8ba496089/8ecfcd5b-db67-4c23-9869-0e20d7553aba'
>> (as uid:107, gid:107): No such file or directory.
>>
>>
>>
>> Platform details:
>>
>> Ovirt SHE
>>
>> Version 4.2.2.6-1.el7.centos
>>
>> GlusterFS, unmanaged by oVirt.
>>
>>
>>
>> VM is imported & converted from OpenStack, according to log files,
>> successfully (one WARN, related to different MAC address):
>>
>> 2018-05-24 12:03:31,028+02 INFO  [org.ovirt.engine.core.
>> vdsbroker.vdsbroker.GetVmsNamesFromExternalProviderVDSCommand] (default
>> task-29) [cc5931a2-1af5-4d65-b0b3-362588db9d3f] FINISH,
>> GetVmsNamesFromExternalProviderVDSCommand, return: [VM
>> [instance-0001f94c], VM [instance-00078f6a], VM [instance-0814], VM
>> [instance-0001f9ac], VM [instance-01ff], VM [instance-0001f718], VM
>> [instance-0673], VM [instance-0001ecf2], VM [instance-00078d38]], log
>> id: 7f178a5e
>>
>> 2018-05-24 12:48:33,722+02 INFO  [org.ovirt.engine.core.
>> vdsbroker.vdsbroker.GetVmsNamesFromExternalProviderVDSCommand] (default
>> task-8) [103d56e1-7449-4853-ae50-48ee94d43d77] FINISH,
>> GetVmsNamesFromExternalProviderVDSCommand, return: [VM
>> [instance-0001f94c], VM [instance-00078f6a], VM [instance-0814], VM
>> [instance-0001f9ac], VM [in

[ovirt-users] Re: Copying/Cloning a VM to another server

2018-05-16 Thread Arik Hadas
On Mon, May 14, 2018 at 8:57 PM, Alex Bartonek <a...@unix1337.com> wrote:

> Is there an ETA on a release?
>

Hopefully in some future subversion of 4.2.


>
>
> Sent with ProtonMail <https://protonmail.com> Secure Email.
>
> ‐‐‐ Original Message ‐‐‐
> On May 13, 2018 2:22 PM, Arik Hadas <aha...@redhat.com> wrote:
>
>
>
> On Sun, May 13, 2018 at 8:04 PM, Alex Bartonek <a...@unix1337.com> wrote:
>
>> Strange..   None of my VMs have the option of Exporting to either OVA or
>> Export Domain.  It is grey'd out.  It would be awesome if I could do that
>> with them running.
>>
>
> Yeah, that capability of exporting running VMs was discussed (and I even
> started implementing it half a year ago [1]) but is not yet available.
>
> [1] https://gerrit.ovirt.org/#/c/85806/
>
>
>>
>>
>> oVirt has proven itself a very very valuable product in my homelab.
>> Tickled to death to run this thing with a few forward facing sites, hosting
>> my own cloud etc.
>>
>>
>> Sent with ProtonMail <https://protonmail.com> Secure Email.
>>
>> ‐‐‐ Original Message ‐‐‐
>> On May 13, 2018 7:00 AM, Jayme <jay...@gmail.com> wrote:
>>
>> You should be able to do this without having to shut vm down
>>
>> On Sun, May 13, 2018, 7:04 AM Alex Bartonek, <a...@unix1337.com> wrote:
>>
>>> Just trying to make sure there isnt an easier way to do what I'm doing.
>>> I dont have an HA environment in my homelab.  I have 3 VM's and I wanted
>>> to copy them to my backup r710 which runs oVirt 4.2.  I basically shut down
>>> my VM, exported it to an export domain on my primary r710.  Then detached
>>> the export domain on the primary.  On my "standby" r710 I imported the
>>> export domain from the primary r710, attached, activated and imported the
>>> VM.  Worked as expected.
>>>
>>> I'm assuming this is the correct way to do so.  I've tried Export to OVA
>>> but that didnt work like I wanted and I didnt care to keep messing with
>>> that option.
>>>
>> Can you please elaborate on the issue you had with exporting to OVA?
>
>>
>>>
>>> Thanks
>>> -Alex
>>>
>>>
>>> Sent with ProtonMail <https://protonmail.com> Secure Email.
>>>
>>> ___
>>> Users mailing list -- users@ovirt.org
>>> To unsubscribe send an email to users-le...@ovirt.org
>>>
>>
>>
>> ___
>> Users mailing list -- users@ovirt.org
>> To unsubscribe send an email to users-le...@ovirt.org
>>
>>
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org


[ovirt-users] Re: What is "Active VM" snapshot

2018-05-15 Thread Arik Hadas
On Tue, May 15, 2018 at 12:21 PM,  wrote:

> Hi!
>
> Can anybody explain what is "Active VM" snapshot that present on each VM
> and does it contain VM memory snapshot?
>

"Active VM" snapshot is an entity that:
(1) Top-level volume of each disk image that the VM uses when it starts is
attached to.
(2) Memory that needs to be restored when the VM starts is attached to.

So yeah, it may contain memory - this happens when the VM is either
suspended or a snapshot with memory is restored.


>
> I need it for PCI assessment and did not found answer in documentation or
> any other public sources.
>
> Thanks!
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> oVirt Code of Conduct: https://www.ovirt.org/communit
> y/about/community-guidelines/
> List Archives:
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives:


[ovirt-users] Re: how to attach an export domain to a new datacenter with an export domain not very well unattached from an obsolete datacenter

2018-05-14 Thread Arik Hadas
On Mon, May 14, 2018 at 9:14 AM, Arik Hadas <aha...@redhat.com> wrote:

>
>
> On Sun, May 13, 2018 at 11:36 PM, <n.v...@free.fr> wrote:
>
>> Hi Ovirt Team,
>>
>> how to attach an export domain to a new datacenter with an export domain
>> not very well unattached from an obsolete datacenter ?
>>
>> My old platform with ovirt 4.1 was deleted ans reinstalled with ovirt
>> 4.2.3.
>> It's ok but i have a problem with an export domain which has not been
>> unattached before the extinction of the old platform.
>>
>> When i try to attach this export domain, i have the error message in the
>> gui :
>>
>> Failed to attach Storage Domain oVirtNFS_EXPORT to Data Center xxx.
>>
>>
>> How can i reinitialize the export domain without erase the data ? just
>> the manager who own the domain.
>>
>
> I haven't don't it for a long time, but the following procedure used to
> work:
>

I haven't done*


> 1. Browse the export domain and find a file called 'metadata' in the
> dom_md folder.
> 2. Back it up.
> 3. Remove the lines with POOL_UUID and _SHA_CKSUM in that file.
>
>
>>
>>
>> Thanks for all.
>>
>> Nicolas VAYE
>> ___
>> Users mailing list -- users@ovirt.org
>> To unsubscribe send an email to users-le...@ovirt.org
>>
>
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org


[ovirt-users] Re: how to attach an export domain to a new datacenter with an export domain not very well unattached from an obsolete datacenter

2018-05-14 Thread Arik Hadas
On Sun, May 13, 2018 at 11:36 PM,  wrote:

> Hi Ovirt Team,
>
> how to attach an export domain to a new datacenter with an export domain
> not very well unattached from an obsolete datacenter ?
>
> My old platform with ovirt 4.1 was deleted ans reinstalled with ovirt
> 4.2.3.
> It's ok but i have a problem with an export domain which has not been
> unattached before the extinction of the old platform.
>
> When i try to attach this export domain, i have the error message in the
> gui :
>
> Failed to attach Storage Domain oVirtNFS_EXPORT to Data Center xxx.
>
>
> How can i reinitialize the export domain without erase the data ? just the
> manager who own the domain.
>

I haven't don't it for a long time, but the following procedure used to
work:
1. Browse the export domain and find a file called 'metadata' in the dom_md
folder.
2. Back it up.
3. Remove the lines with POOL_UUID and _SHA_CKSUM in that file.


>
>
> Thanks for all.
>
> Nicolas VAYE
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org


[ovirt-users] Re: Copying/Cloning a VM to another server

2018-05-13 Thread Arik Hadas
On Sun, May 13, 2018 at 8:04 PM, Alex Bartonek  wrote:

> Strange..   None of my VMs have the option of Exporting to either OVA or
> Export Domain.  It is grey'd out.  It would be awesome if I could do that
> with them running.
>

Yeah, that capability of exporting running VMs was discussed (and I even
started implementing it half a year ago [1]) but is not yet available.

[1] https://gerrit.ovirt.org/#/c/85806/


>
> oVirt has proven itself a very very valuable product in my homelab.
> Tickled to death to run this thing with a few forward facing sites, hosting
> my own cloud etc.
>
>
> Sent with ProtonMail  Secure Email.
>
> ‐‐‐ Original Message ‐‐‐
> On May 13, 2018 7:00 AM, Jayme  wrote:
>
> You should be able to do this without having to shut vm down
>
> On Sun, May 13, 2018, 7:04 AM Alex Bartonek,  wrote:
>
>> Just trying to make sure there isnt an easier way to do what I'm doing.
>> I dont have an HA environment in my homelab.  I have 3 VM's and I wanted
>> to copy them to my backup r710 which runs oVirt 4.2.  I basically shut down
>> my VM, exported it to an export domain on my primary r710.  Then detached
>> the export domain on the primary.  On my "standby" r710 I imported the
>> export domain from the primary r710, attached, activated and imported the
>> VM.  Worked as expected.
>>
>> I'm assuming this is the correct way to do so.  I've tried Export to OVA
>> but that didnt work like I wanted and I didnt care to keep messing with
>> that option.
>>
> Can you please elaborate on the issue you had with exporting to OVA?

>
>> Thanks
>> -Alex
>>
>>
>> Sent with ProtonMail  Secure Email.
>>
>> ___
>> Users mailing list -- users@ovirt.org
>> To unsubscribe send an email to users-le...@ovirt.org
>>
>
>
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
>
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org


Re: [ovirt-users] Pass through disk can't R/W

2018-05-03 Thread Arik Hadas
On Thu, May 3, 2018 at 11:45 AM, gss...@pku.edu.cn 
wrote:

> Hi,
>
> I found my VM libvirt create xml as:
>
> 
>   
> 
> 
>   
> 
>
> I found https://libvirt.org/formatdomain.html#elementsHostDevSubsys like
> blow:
>
> ...
> 
>   
> 
>   
>   
> 
> 
> 
>   
> 
> ...
>
> Is  mandatory?
>
> No, it is not mandatory.
If not set, it would be determined by libvirt. See [1].

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

>
>
> ___
> 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] Help debugging VM import error

2018-04-26 Thread Arik Hadas
On Mon, Apr 23, 2018 at 10:02 PM, Roy Golan  wrote:

> I suspect
>
> List guids = Guid.createGuidListFromString(
> snap.getMemoryVolume());
>
> where guids is empty because there is not memory volume. which fails this
>
> StorageDomain sd = getStorageDomainDao().
> getForStoragePool(guids.get(0), params.getStoragePoolId());
>

Note that this analysis is based on an incorrect version of the code since
it happened with version 4.2.2.6. So it may still happen with the
up-to-date code on the master branch as well. (Also note that had 'guids'
be empty the exception would have been IndexOutOfBoundsException rather
than NPE).


>
>
> On Mon, 23 Apr 2018 at 22:01 Benny Zlotnik  wrote:
>
>> Looks like a bug. Can you please file a report:
>> https://bugzilla.redhat.com/enter_bug.cgi?product=ovirt-engine
>>
>> On Mon, Apr 23, 2018 at 9:38 PM, ~Stack~  wrote:
>>
>>> Greetings,
>>>
>>> After my rebuild, I have imported my VM's. Everything went smooth and
>>> all of them came back, except one. One VM gives me the error "General
>>> command validation failure." which isn't helping me when I search for
>>> the problem.
>>>
>>> The oVirt engine logs aren't much better at pointing to what the failure
>>> is (posted below).
>>>
>>> Can someone help me figure out why this VM isn't importing, please?
>>>
>>> Thanks!
>>> ~Stack~
>>>
>>>
>>> 2018-04-23 13:31:44,313-05 INFO
>>> [org.ovirt.engine.core.bll.exportimport.ImportVmFromConfigurationComma
>>> nd]
>>> (default task-72) [6793fe73-7cda-4cb5-a806-7104a05c3c1b] Lock Acquired
>>> to object 'EngineLock:{exclusiveLocks='[infra01=VM_NAME,
>>> 0b64ced5-7e4b-48cd-9d0d-24e8b905758c=VM]',
>>> sharedLocks='[0b64ced5-7e4b-48cd-9d0d-24e8b905758c=REMOTE_VM]'}'
>>> 2018-04-23 13:31:44,349-05 ERROR
>>> [org.ovirt.engine.core.bll.exportimport.ImportVmFromConfigurationComma
>>> nd]
>>> (default task-72) [6793fe73-7cda-4cb5-a806-7104a05c3c1b] Error during
>>> ValidateFailure.: java.lang.NullPointerException
>>> at
>>> org.ovirt.engine.core.bll.validator.ImportValidator.
>>> validateStorageExistsForMemoryDisks(ImportValidator.java:140)
>>> [bll.jar:]
>>> at
>>> org.ovirt.engine.core.bll.exportimport.ImportVmFromConfigurationComma
>>> nd.isValidDisks(ImportVmFromConfigurationCommand.java:151)
>>> [bll.jar:]
>>> at
>>> org.ovirt.engine.core.bll.exportimport.ImportVmFromConfigurationComma
>>> nd.validate(ImportVmFromConfigurationCommand.java:103)
>>> [bll.jar:]
>>> at
>>> org.ovirt.engine.core.bll.CommandBase.internalValidate(
>>> CommandBase.java:779)
>>> [bll.jar:]
>>> at
>>> org.ovirt.engine.core.bll.CommandBase.validateOnly(CommandBase.java:368)
>>> [bll.jar:]
>>> at
>>> org.ovirt.engine.core.bll.PrevalidatingMultipleActionsRu
>>> nner.canRunActions(PrevalidatingMultipleActionsRunner.java:113)
>>> [bll.jar:]
>>> at
>>> org.ovirt.engine.core.bll.PrevalidatingMultipleActionsRu
>>> nner.invokeCommands(PrevalidatingMultipleActionsRunner.java:99)
>>> [bll.jar:]
>>> at
>>> org.ovirt.engine.core.bll.PrevalidatingMultipleActionsRunner.execute(
>>> PrevalidatingMultipleActionsRunner.java:76)
>>> [bll.jar:]
>>> at
>>> org.ovirt.engine.core.bll.Backend.runMultipleActionsImpl(
>>> Backend.java:596)
>>> [bll.jar:]
>>> at
>>> org.ovirt.engine.core.bll.Backend.runMultipleActions(Backend.java:566)
>>> [bll.jar:]
>>> at sun.reflect.GeneratedMethodAccessor914.invoke(Unknown Source)
>>> [:1.8.0_161]
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(
>>> DelegatingMethodAccessorImpl.java:43)
>>> [rt.jar:1.8.0_161]
>>> at java.lang.reflect.Method.invoke(Method.java:498)
>>> [rt.jar:1.8.0_161]
>>> 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.interceptors.Jsr299BindingsInterceptor.
>>> delegateInterception(Jsr299BindingsInterceptor.java:78)
>>> at
>>> org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.
>>> doMethodInterception(Jsr299BindingsInterceptor.java:88)
>>> at
>>> org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.
>>> processInvocation(Jsr299BindingsInterceptor.java:101)
>>> at
>>> org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.
>>> processInvocation(UserInterceptorFactory.java:63)
>>> at
>>> org.jboss.invocation.InterceptorContext.proceed(
>>> InterceptorContext.java:422)
>>> at
>>> org.jboss.invocation.InterceptorContext$Invocation.
>>> proceed(InterceptorContext.java:509)
>>> at
>>> org.ovirt.engine.core.bll.interceptors.CorrelationIdTrackerIntercepto
>>> 

Re: [ovirt-users] ?= vdsClient is removed and replaced by vdsm-clien

2018-04-13 Thread Arik Hadas
On Fri, Apr 13, 2018 at 6:54 PM, fsoyer <fso...@systea.fr> 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 <aha...@redhat.com> a
> écrit:
>
>
>
>
> On Fri, Apr 13, 2018 at 11:14 AM, fsoyer <fso...@systea.fr> 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",
>>
>>  

Re: [ovirt-users] ?==?utf-8?q? vdsClient is removed and replaced by vdsm-client

2018-04-13 Thread 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] Is compatibility level change required for upgrading from 4.0 to 4.2?

2018-04-08 Thread 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] Issue adding network interface to VM failed with HotPlugNicVDS

2018-04-01 Thread 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] Fwd: Can't add/remove usb device to VM

2018-03-25 Thread 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] Cannot remove VM

2018-03-25 Thread 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] Failed to run VM

2018-03-18 Thread 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 

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

2018-03-13 Thread 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


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

2018-03-13 Thread Arik Hadas
Sharing the thread below with the list.

-- Forwarded message --
From: Shao-Da Huang <sdhuan...@gmail.com>
Date: Tue, Mar 13, 2018 at 11:23 AM
Subject: Re: question about importing VMware-produced OVA
To: Arik Hadas <aha...@redhat.com>


2018-03-13 15:51 GMT+08:00 Arik Hadas <aha...@redhat.com>:

>
> On Tue, Mar 13, 2018 at 6:10 AM, Shao-Da Huang <sdhuan...@gmail.com>
> 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] Unable to start VM after upgrade vom 4.1.9 to 4.2.1 - NPE

2018-03-07 Thread 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 

  1   2   >