[ovirt-users] Re: OVA Export from Snapshot?

2022-05-08 Thread Arik Hadas
On Fri, May 6, 2022 at 3:00 PM Alan G  wrote:
>
> Hi,
>
> Is there a way to export an OVA from a snapshot? Or only from the "Active VM" 
> image?

The fact you're asking specifically about the image makes me wonder
what's the reason for asking that
If you look for a way to create an OVA directly from an existing
snapshot then no, it's not possible. You'd need to provision a
VM/template from the snapshot and export it to an OVA.
If you don't want the export operation to operate on the active
volume(s) of the VM then unless the VM is configured with MBS (managed
block storage) disk, the system creates a snapshot first and exports
the volumes that are associate with the snapshot to the OVA (so it
doesn't use the active volumes)

>
> Thanks,
>
> Alan
>
> ___
> 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/QIJM6R3GS2HQYIM2VYPTIBVPJXC2D5GN/
___
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/HL626RQUSPO5OXPXRH2D6WNLUCEA6UNC/


[ovirt-users] Re: [Ext.] Re: convert disk image to thin-provisioned - Ovirt 4.1

2022-04-28 Thread Arik Hadas
On Thu, Apr 28, 2022 at 11:11 AM Mohamed Roushdy
 wrote:
>
> Thanks for responding.
>
> So, this feature isn't available in 4.4.10 as we are intending to move to 
> that version?

It's not available in 4.4.10
See https://bugzilla.redhat.com/show_bug.cgi?id=98 (introduced in 4.5)

> Storage used for that VM is NFS.
>
> Thanks,
>
> -Original Message-
> From: Nir Soffer 
> Sent: Wednesday, April 27, 2022 10:53 PM
> To: Mohamed Roushdy 
> Cc: users@ovirt.org; Benny Zlotnik 
> Subject: [Ext.] Re: [ovirt-users] convert disk image to thin-provisioned - 
> Ovirt 4.1
>
> [CAUTION: This email originated from outside of the organization. Do not 
> click links or open attachments unless you recognize the sender and know the 
> content is safe]
>
> On Wed, Apr 27, 2022 at 1:02 PM Mohamed Roushdy 
>  wrote:
> >
> > Hello,
> >
> > I’ve researched a bit on how to convert a disk image from pre-allocated to 
> > thin in Ovirt 4.1, but nothing worked. Is there a way to achieve this 
> > please?
>
> Yes!
>
> 1. Install ovirt 4.5.0
> 2.  Use the new convert disk feature
>
> With oVirt 4.1 you can do this manually. What kind storage are you using?
> (NFS, iSCSI?)
>
> Nir
>
> ___
> 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/KNYUTOLPAUZOXKCQY63JML6XUGVF5XIR/
___
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/TQK4ID5OHF4TF6KRAPL6D4B5F4A2RKTY/


[ovirt-users] Re: NVIDIA vgpu mdev/mediated devices are getting deleted/removed after VM shutdown with ovirt

2022-04-20 Thread Arik Hadas
On Tue, Apr 19, 2022 at 11:00 PM Sandip Thorat  wrote:
>
> Thanks Arik for reply.
>
> I want to add enable_large_sys_mem=1 vGPU plugin parameter . How can I do 
> that with oVirt? Could you please share steps?

Go to the "Manage vGPU" (Virtual Machine -> Host Devices -> Manage
vGPU) and add it to "Optional driver parameters" (see attached
screenshot)

>
> -Original Message-
> From: Arik Hadas 
> Sent: Tuesday, April 19, 2022 6:49 PM
> To: Sandip Thorat 
> Cc: users 
> Subject: Re: [ovirt-users] NVIDIA vgpu mdev/mediated devices are getting 
> deleted/removed after VM shutdown with ovirt
>
>
>
> External email: Use caution opening links or attachments
>
>
>
>
>
> On Tue, Apr 19, 2022 at 3:47 PM sandipt--- via Users  wrote:
>
> >
>
> > Hi Team,
>
> > NVIDIA vgpu mdev/mediated devices are getting deleted/removed after VM 
> > shutdown with ovirt. How I can make them persistent even after VM 
> > shutdown/poweroff ? I want to set some vgpu parameter in file 
> > /sys/bus/mdev/devices/vgpu-id/nvidia/vgpu_params for testing to mdev. But 
> > can't do as uuid of mdev are not persistent.  mdev are not there in 
> > /sys/bus/mdev/devices/ after VM shutdown. We were using RHV/Red Hat 
> > Virtualization Host 4.4.10 host with NVIDIA vGPU.  virsh commands are 
> > helping. Can you please help?
>
>
>
> As from oVirt 4.5, you can set such parameters via oVirt's UI/API, see:
>
> https://bugzilla.redhat.com/1987121
>
> (The mdev devices were also changed to managed devices in order to have them 
> persisted)
>
>
>
>
>
> > ___
>
> > 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/YAZ5I5LT
>
> > FZ3WXBPVNIPH2HQWVEDSQW6K/
>
>
___
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/73FOONPBRKLKDKNG5NC723522YBUYUI3/


[ovirt-users] Re: NVIDIA vgpu mdev/mediated devices are getting deleted/removed after VM shutdown with ovirt

2022-04-19 Thread Arik Hadas
On Tue, Apr 19, 2022 at 3:47 PM sandipt--- via Users  wrote:
>
> Hi Team,
> NVIDIA vgpu mdev/mediated devices are getting deleted/removed after VM 
> shutdown with ovirt. How I can make them persistent even after VM 
> shutdown/poweroff ? I want to set some vgpu parameter in file 
> /sys/bus/mdev/devices/vgpu-id/nvidia/vgpu_params for testing to mdev. But 
> can't do as uuid of mdev are not persistent.  mdev are not there in 
> /sys/bus/mdev/devices/ after VM shutdown. We were using RHV/Red Hat 
> Virtualization Host 4.4.10 host with NVIDIA vGPU.  virsh commands are 
> helping. Can you please help?

As from oVirt 4.5, you can set such parameters via oVirt's UI/API, see:
https://bugzilla.redhat.com/1987121
(The mdev devices were also changed to managed devices in order to
have them persisted)


> ___
> 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/YAZ5I5LTFZ3WXBPVNIPH2HQWVEDSQW6K/
___
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/JKIR6GV6KV3OX45NI6VQFJOUHTMFZMQN/


[ovirt-users] Re: VM hangs after migration

2022-03-31 Thread Arik Hadas
Moshe, this sounds similar to what we've seen in your environment, no?
Did you manage to resolve it?

On Thu, Mar 31, 2022 at 12:57 PM Giorgio Biacchi 
wrote:

> Hi,
> I have a fresh Ovirt installation (4.4.10.7-1.el8 engine and oVirt Node
> 4.4.10) on a Dell VRTX chassis. There are 3 blades, two of them are
> identical hardware (PowerEdge M630) and the third is a little newer
> (PowerEdge M640). The third has different CPUs, more RAM, and slower
> NICs. I also have a bunch of data domains some on the shared PERC
> internal storage and others on an external iSCSI storage, all seems
> configured correctly and all the hosts are operational.
>
> I can migrate a VM back and forth from the first two blades without any
> problem, I can migrate a VM to the third blade but when I migrate a VM
> from the third blade to any of the other two the task terminate
> successfully, the VM is marked as up on the target host but the VM
> hangs, the console is frozen and the VM stops to respond to ping.
>
> I have no clues about why this is happening and I'm looking for
> suggestions about how to debug and hopefully fix this issue.
>
> Thanks in advance
> --
> gb
>
> PGP Key: http://pgp.mit.edu/
> Primary key fingerprint: C510 0765 943E EBED A4F2 69D3 16CC DC90 B9CB 0F34
> ___
> 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/HYHAVG3KDHMNVWNYROIIX2CTHSLFPVU3/
>
___
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/NZF4LY7PTQAIQLIZCXPHCMHHFGUHPV6H/


[ovirt-users] Re: Upgrade oVirt 4.3 -> 4.4 Cluster "Emulated maschine" - Error

2022-03-28 Thread Arik Hadas
On Mon, Mar 28, 2022 at 9:02 AM  wrote:

> Hi,
>
> ++ Setup: 1 Selfhosted oVirt with EL- Hosts (one ol7, second ol8)
>
> we 've updated the ovirt-engine from 4.3 to 4.4 - works, after this, we
> updated the first host (test-host2) to Oracle Linux 8.5.0
> After this we install /add (over the oVirt GUI) the new Host to the
> Cluster.
> oVirt install all. We can see the Host and Configure the Host Networks ...
> but the Status is "NonOperational".
>
> At the Host we can see this error message:
> Host test-host2 does not comply with the cluster Test-Cluster emulated
> machine. The cluster emulated machine is pc-i440fx-2.12 and the host
> emulated machines are
> q35,pc-q35-rhel8.3.0,pc,pc-i440fx-2.11,pc-q35-rhel7.3.0,pc-q35-rhel7.6.0,pc-q35-rhel8.1.0,pc-q35-rhel7.4.0,pc-q35-rhel8.0.0,pc-i440fx-rhel7.3.0,pc-q35-rhel7.5.0,pc-i440fx-4.2,pc-i440fx-rhel7.0.0,pc-i440fx-rhel7.6.0,pc-i440fx-rhel7.4.0,pc-q35-rhel8.4.0,pc-q35-rhel8.5.0,pc-q35-rhel8.2.0,pc-i440fx-rhel7.1.0,pc-i440fx-rhel7.2.0,pc-i440fx-rhel7.5.0.
>
> The Host Version:
>  /usr/libexec/qemu-kvm -M ? |grep pc-i440fx-2
> >> pc-i440fx-2.11   Standard PC (i440FX + PIIX, 1996) (deprecated)
>
> The Cluster has the Compatibility Version "4.3" - if i change to 4.4 he
> complains that is a old (OL-7) Host in the Cluster (right ;))
>
> How can i update the emulated machines for the new Host?
> "yum update" allready done :)
>

The following might work:
1. In the webadmin -> clusters view, select the cluster and trigger "Reset
Emulated Machine" from the kebab menu
2. Activate the 8.5 host


>
> Best Regards,
> Fabian
> ___
> 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/AZZRS47ZJ4AJZCOBA74NWKQXZDMTB4L5/
>
___
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/U5MXNONA4SRVAU5BD2U6B6VUFFWYPZTL/


[ovirt-users] Re: No bootable device

2022-03-27 Thread Arik Hadas
On Sun, Mar 27, 2022 at 12:24 PM Nir Soffer  wrote:

> On Wed, Mar 23, 2022 at 3:09 PM  wrote:
> > We're running oVirt 4.4.8.6. We have uploaded a qcow2 image (metasploit
> > v.3, FWIW)
>
> Is it Metasploitable3-0.1.4.ova from the github releases page?
> https://github.com/brimstone/metasploitable3/releases
>
> If not, can you share the image? It will help if we can reproduce this
> problem
> locally with the same image you are using.
>
> > using the GUI (Storage -> Disks -> Upload -> Start). The
> > image is in qcow2 format.
>
> Did you convert the vmdk file from the ova to qcow2?
>
> > No options on the right side were checked. The
> > upload went smoothly, so we now tried to attach the disk to a VM.
> >
> > To do that, we opened the VM -> Disks -> Attach and selected the disk.
> > As interface, VirtIO-iSCSI was chosen, and the disk was marked as OS, so
> > the "bootable" checkbox was selected.
> >
> > The VM was later powered on, but when accessing the console the message
> > "No bootable device." appears. We're pretty sure this is a bootable
> > image, because it was tested on other virtualization infrastructure and
> > it boots well. We also tried to upload the image in RAW format but the
> > result is the same.
> >
> > What are we missing here? Is anything else needed to do so the disk is
> > bootable?
>
> It sounds like you converted an image from another virtualization
> system (virtualbox)
> to qcow2 format, which may not be good enough to use the virtual machine.
>
> oVirt supports importing OVA, but based on the UI, it supports only OVA
> created
> by oVirt.
>

That information message is incorrect, both OVAs that are created by
oVirt/RHV and OVAs that are created by VMware are supported
It could work for OVAs that are VMware-compatible though
Posted https://github.com/oVirt/ovirt-engine/pull/191 to emphasis that



>
> You can try virt-v2v - this is an example command, you need
> to fill in the {} parts:
>
> virt-v2v \
> -i ova {path-to-ova-file} \
> -o rhv-upload \
> -oc https://{engine-address}/ovirt-engine/api \
> -op {engine-password-file} \
> -on {vm-name} \
> -os {storrage-domain-name} \
> -of qcow2 \
> -oo rhv-cafile={engine-ca-file} \
> -oo rhv-cluster={cluster-name}
>
> I tried to import the Metasploitable3-0.1.4.ova, and virt-v2 fails
> with this error:
>
> virt-v2v: error: inspection could not detect the source guest (or
> physical machine).
>
> attached virt-v2v log.
>
> Nir
>
___
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/XLRNVGUB43YPAYOBSGA6BZZD6ULUMC5H/


[ovirt-users] Re: Cloning VM selecting part of the disks

2022-03-22 Thread Arik Hadas
On Tue, Mar 22, 2022 at 12:16 PM Gianluca Cecchi 
wrote:

> Hello,
> in recent versions of oVirt (eg my last 4.4.10) there is the feature to
> make a clone of a running  VM.
> This operation passes through a temporary VM snapshot (then automatically
> deleted) and cloning of this snapshot.
>

For the most part, yes (we now skip the creation of the snapshot when the
VM uses MBS disks)


> Sometimes there is a need to clone a VM but only a subset of its disks is
> required (eg in my case I want to retain boot disk, 20Gb, and dedicated sw
> disk, 20Gb, but not data disk, that usually is big... in my case 200Gb).
> In this scenario I have to go the old path where I explicitly create a
> snapshot of the VM, where I can select a subset of the disks, then I clone
> the snapshot and last I delete the snapshot.
>
Do you think it is interesting to have the option of selecting disks when
> you clone a running VM and go automatic..?
>
If I want to open a bugzilla as RFE, what components and options I have to
> select?
>

The initial idea behind clone-VM was to have a simple operation for getting
an exact-clone (sure, with different ID, different MAC addresses and so on)
of an existing VM without going through the cycle you mentioned of:
creating a snapshot, cloning a VM from the snapshot and removing the
snapshot

While external contributions for adding the ability to filter the disks of
the cloned VM would be welcome, it's unlikely to be something we would get
to since there is an alternative way to achieve this and it's not
considered to be a common scenario


>
> Thanks,
> 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/CO34RAB2EOA3IYA4LDSLTZYY4MR4UQJA/
>
___
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/W5E6R53EYFUFDTCTAF5TMFJC4FF5TBCK/


[ovirt-users] Re: Import ova Thin provisioned disk conversion to pre allocated disks fails

2022-03-13 Thread Arik Hadas
On Sat, Mar 12, 2022 at 9:06 AM Simon Scott  wrote:

> Hi Arik,
>
> I don’t see an option to select ‘allocation-policy=clone and specifying
> that the VM disk(s) should be preallocated’ when creating a VM from the
> template.
>

>From the API you need to specify clone=True as in [1] and the volume
type+format as in [2]
In the webadmin, it is part of the Resource Allocation tab (specifically
its 'Storage Allocation' section) in the add-vm dialog

[1]
https://github.com/oVirt/python-ovirt-engine-sdk4/blob/c5ea821acc80da12a30b68647dd76370b9f54e4e/examples/add_independet_vm.py#L56
[2]
https://github.com/oVirt/python-ovirt-engine-sdk4/blob/c5ea821acc80da12a30b68647dd76370b9f54e4e/examples/add_template.py#L73-L74


> Regard
>
> Simon
> ___
> 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/PM2YIHRODYWHKS56YDQZVAZHZAYS7DAB/
>
___
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/7WRZJ67J7EYLKIYT3PY7PQEJOTMKATUG/


[ovirt-users] Re: Import ova Thin provisioned disk conversion to pre allocated disks fails

2022-03-11 Thread Arik Hadas
Another one might be to import the OVA as a template and then provision a
VM from that template with allocation-policy=clone and specifying that the
VM disk(s) should be preallocated

On Fri, Mar 11, 2022 at 7:56 AM Strahil Nikolov via Users 
wrote:

> One workaround that comes to my mind is to power up the VM, write a large
> file and delete it and run fstrim -av.
> Another approach is to create an additional LV inside the guest, use dd to
> fill it in and then blkdiscard and delete the LV .
>
> It will force the fisk to be fully allocated
>
> Best Regards,
> Strahil Nikolov
>
> Thanks Arik,
>
> Is there a fix that can be applied to current versions as 4.5 release and
> subsequent testing/approval is some way off/
>
> ___
> 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/HXTHUA5QFBBCLMQPKM25ACANVVNL7XKC/
>
> ___
> 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/4WUBMHETRW6O3PN3YNEFJAEW5SNCO3XX/
>
___
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/7B5GX4XLLDSJG5FAOQCCRBPMI6UNNRWC/


[ovirt-users] Re: Import ova Thin provisioned disk conversion to pre allocated disks fails

2022-03-10 Thread Arik Hadas
On Thu, Mar 10, 2022 at 1:13 PM  wrote:

> Hi All,
>
> During the ova import process, preallocated disk policy is selected and
> the VM is imported successfully.
> Unfortunately the disks remain as Thin Provisioned - is this a known bug
> and is there a workaround?
>

This should be fixed in oVirt 4.5:
https://bugzilla.redhat.com/show_bug.cgi?id=1986726


>
> Kind Regards
>
> Simon...
> ___
> 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/6ONULHQQQOTJKJLSY2E7MRPPPOSJT4DE/
>
___
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/3EQMR2WPJTEUB6X53SMW3V33GH4FEYJT/


[ovirt-users] Re: vm seal

2022-02-15 Thread Arik Hadas
On Tue, Feb 15, 2022 at 12:26 PM Nathanaël Blanchet 
wrote:

>
> Le 15/02/2022 à 10:32, Arik Hadas a écrit :
>
>
>
> On Mon, Feb 14, 2022 at 11:29 PM Nathanaël Blanchet 
> wrote:
>
>>
>>
>> Le 14 févr. 2022 21:09, Arik Hadas  a écrit :
>>
>>
>>
>> On Mon, Feb 14, 2022 at 8:44 PM Nathanaël Blanchet 
>> wrote:
>>
>>
>> Le 14/02/2022 à 17:45, Arik Hadas a écrit :
>>
>>
>>
>> On Mon, Feb 14, 2022 at 4:52 PM Nathanaël Blanchet 
>> wrote:
>>
>> Hello,
>>
>> I noticed that a vm created from a "sealed" template is initially mount
>> on one host with libguestfs, with a virt-sysprep process, before getting
>> ready to be used.
>>
>> This should be unuseful given that the template is already sealed. Is
>> there a reason to that?
>>
>>
>> Yes, we do this in order to produce different LVM IDs and machine IDs for
>> the provisioned VMs, see:
>> https://gerrit.ovirt.org/c/ovirt-engine/+/115009
>>
>> okay, but, I modified  the
>> /usr/lib/python3.6/site-packages/vdsm/virtsysprep.py file like following:
>>
>> args = ['--hostname', 'localhost', ''--selinux-relabel', '--update',
>> '--network']"
>>
>> in order to update packages on  template creation.
>>
>> The template creation still works and the template is checked as sealed
>> and os is updated, but now the vm creation never ends up and I have to
>> manually kill the virt-sysprep process to stop the infinite process
>> creation.
>>
>> I believed it was a good workaround to get updated templates, but I had
>> to rollback to default virt-sysprep args configuration, unless there is
>> trick do to so?
>>
>> If you create the VM from the webadmin, you can uncheck the 'sealed'
>> option in the new-vm dialog to skip the second execution of virt-sysprep on
>> the VM
>> If you create it from REST-API (or the VM portal), you might want to
>> change the configuration of the template in the database:
>> update vm_static set is_template_sealed='f' where vm_name='> template's name>';
>>
>> Thanks for this useful tip, but as you said if second seal has been
>> designed it is to produce different VM IDs... So what will happen if I skip
>> this process?
>>
>
> It was that way (i.e., without sysprep-ing the vm volumes) for years - if
> that worked well for you, you shouldn't notice a difference
>
>
>> Secondly I'd like to know if there is a way to skip the second seal from
>> the template with oVirt VM ansible module( don't seem to be), it is safer
>> than modifying the DB.
>>
>
> Ansible is in the second category (since it is based on oVirt's REST-API)
> so yeah, I don't see a different way you can achieve this at the moment
> And you're right, it's not recommended to modify the DB directly but the
> same goes for changing the VDSM source files ;)
> Anyway, that is_template_sealed field only affects the UI (presenting
> whether the template is sealed) and this functionality (deciding whether
> virt-sysprep should be executed on the vm volumes) - so changing it should
> be safe.
>
> Thank you it works as expected now.
>
> But giving that my templates are auto-created, is there a way to set
> is_template_sealed to false at template creation rather than manually doing
> it in a second time?
>
We change the database via Ansible during the deployment of hosted engine
[1], maybe you can do it in a similar way..

Filed https://bugzilla.redhat.com/show_bug.cgi?id=2054681 for adding the
configuration we have at the webadmin to the API

[1]
https://github.com/oVirt/ovirt-ansible-collection/blob/1.6.6-1/roles/hosted_engine_setup/tasks/create_target_vm/02_engine_vm_configuration.yml#L11-L15


>
>
>>
>> --
>> Nathanaël Blanchet
>>
>> Supervision réseau
>> SIRE
>> 227 avenue Professeur-Jean-Louis-Viala
>> 34193 MONTPELLIER CEDEX 5
>> Tél. 33 (0)4 67 54 84 55
>> Fax  33 (0)4 67 54 84 14
>> blanc...@abes.fr
>> ___
>> Users mailing list -- users@ovirt.org
>> 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/7VSOFV3TFSMKPEZBI2ERRVUCTFGJALQT/
>>
>> --
>> Nathanaël Blanchet
>>
>> Supervision réseau
>> SIRE
>> 227 avenue Professeur-Jean-Louis-Viala
>> 34193 MONTPELLIER CED

[ovirt-users] Re: vm seal

2022-02-15 Thread Arik Hadas
On Mon, Feb 14, 2022 at 11:29 PM Nathanaël Blanchet 
wrote:

>
>
> Le 14 févr. 2022 21:09, Arik Hadas  a écrit :
>
>
>
> On Mon, Feb 14, 2022 at 8:44 PM Nathanaël Blanchet 
> wrote:
>
>
> Le 14/02/2022 à 17:45, Arik Hadas a écrit :
>
>
>
> On Mon, Feb 14, 2022 at 4:52 PM Nathanaël Blanchet 
> wrote:
>
> Hello,
>
> I noticed that a vm created from a "sealed" template is initially mount
> on one host with libguestfs, with a virt-sysprep process, before getting
> ready to be used.
>
> This should be unuseful given that the template is already sealed. Is
> there a reason to that?
>
>
> Yes, we do this in order to produce different LVM IDs and machine IDs for
> the provisioned VMs, see: https://gerrit.ovirt.org/c/ovirt-engine/+/115009
>
> okay, but, I modified  the
> /usr/lib/python3.6/site-packages/vdsm/virtsysprep.py file like following:
>
> args = ['--hostname', 'localhost', ''--selinux-relabel', '--update',
> '--network']"
>
> in order to update packages on  template creation.
>
> The template creation still works and the template is checked as sealed
> and os is updated, but now the vm creation never ends up and I have to
> manually kill the virt-sysprep process to stop the infinite process
> creation.
>
> I believed it was a good workaround to get updated templates, but I had to
> rollback to default virt-sysprep args configuration, unless there is trick
> do to so?
>
> If you create the VM from the webadmin, you can uncheck the 'sealed'
> option in the new-vm dialog to skip the second execution of virt-sysprep on
> the VM
> If you create it from REST-API (or the VM portal), you might want to
> change the configuration of the template in the database:
> update vm_static set is_template_sealed='f' where vm_name=' template's name>';
>
> Thanks for this useful tip, but as you said if second seal has been
> designed it is to produce different VM IDs... So what will happen if I skip
> this process?
>

It was that way (i.e., without sysprep-ing the vm volumes) for years - if
that worked well for you, you shouldn't notice a difference


> Secondly I'd like to know if there is a way to skip the second seal from
> the template with oVirt VM ansible module( don't seem to be), it is safer
> than modifying the DB.
>

Ansible is in the second category (since it is based on oVirt's REST-API)
so yeah, I don't see a different way you can achieve this at the moment
And you're right, it's not recommended to modify the DB directly but the
same goes for changing the VDSM source files ;)
Anyway, that is_template_sealed field only affects the UI (presenting
whether the template is sealed) and this functionality (deciding whether
virt-sysprep should be executed on the vm volumes) - so changing it should
be safe.


>
> --
> Nathanaël Blanchet
>
> Supervision réseau
> SIRE
> 227 avenue Professeur-Jean-Louis-Viala
> 34193 MONTPELLIER CEDEX 5
> Tél. 33 (0)4 67 54 84 55
> Fax  33 (0)4 67 54 84 14
> blanc...@abes.fr
> ___
> Users mailing list -- users@ovirt.org
> 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/7VSOFV3TFSMKPEZBI2ERRVUCTFGJALQT/
>
> --
> Nathanaël Blanchet
>
> Supervision réseau
> SIRE
> 227 avenue Professeur-Jean-Louis-Viala
> 34193 MONTPELLIER CEDEX 5 
> Tél. 33 (0)4 67 54 84 55
> Fax  33 (0)4 67 54 84 14blanc...@abes.fr
>
>
>
___
Users mailing list -- users@ovirt.org
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/PXOQI5UDF3TF2A4E6RJOQXOGUDZS6UZW/


[ovirt-users] Re: vm seal

2022-02-14 Thread Arik Hadas
On Mon, Feb 14, 2022 at 8:44 PM Nathanaël Blanchet  wrote:

>
> Le 14/02/2022 à 17:45, Arik Hadas a écrit :
>
>
>
> On Mon, Feb 14, 2022 at 4:52 PM Nathanaël Blanchet 
> wrote:
>
>> Hello,
>>
>> I noticed that a vm created from a "sealed" template is initially mount
>> on one host with libguestfs, with a virt-sysprep process, before getting
>> ready to be used.
>>
>> This should be unuseful given that the template is already sealed. Is
>> there a reason to that?
>>
>
> Yes, we do this in order to produce different LVM IDs and machine IDs for
> the provisioned VMs, see: https://gerrit.ovirt.org/c/ovirt-engine/+/115009
>
> okay, but, I modified  the
> /usr/lib/python3.6/site-packages/vdsm/virtsysprep.py file like following:
>
> args = ['--hostname', 'localhost', ''--selinux-relabel', '--update',
> '--network']"
>
> in order to update packages on  template creation.
>
> The template creation still works and the template is checked as sealed
> and os is updated, but now the vm creation never ends up and I have to
> manually kill the virt-sysprep process to stop the infinite process
> creation.
>
> I believed it was a good workaround to get updated templates, but I had to
> rollback to default virt-sysprep args configuration, unless there is trick
> do to so?
>
If you create the VM from the webadmin, you can uncheck the 'sealed' option
in the new-vm dialog to skip the second execution of virt-sysprep on the VM
If you create it from REST-API (or the VM portal), you might want to change
the configuration of the template in the database:
update vm_static set is_template_sealed='f' where vm_name='';

>
>
>> --
>> Nathanaël Blanchet
>>
>> Supervision réseau
>> SIRE
>> 227 avenue Professeur-Jean-Louis-Viala
>> 34193 MONTPELLIER CEDEX 5
>> Tél. 33 (0)4 67 54 84 55
>> Fax  33 (0)4 67 54 84 14
>> blanc...@abes.fr
>> ___
>> Users mailing list -- users@ovirt.org
>> 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/7VSOFV3TFSMKPEZBI2ERRVUCTFGJALQT/
>>
> --
> Nathanaël Blanchet
>
> Supervision réseau
> SIRE
> 227 avenue Professeur-Jean-Louis-Viala
> 34193 MONTPELLIER CEDEX 5 
> Tél. 33 (0)4 67 54 84 55
> Fax  33 (0)4 67 54 84 14blanc...@abes.fr
>
>
___
Users mailing list -- users@ovirt.org
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/A5CNQHASI3DHJQ5JJBJUKLCXRSUK3VCJ/


[ovirt-users] Re: vm seal

2022-02-14 Thread Arik Hadas
On Mon, Feb 14, 2022 at 4:52 PM Nathanaël Blanchet  wrote:

> Hello,
>
> I noticed that a vm created from a "sealed" template is initially mount
> on one host with libguestfs, with a virt-sysprep process, before getting
> ready to be used.
>
> This should be unuseful given that the template is already sealed. Is
> there a reason to that?
>

Yes, we do this in order to produce different LVM IDs and machine IDs for
the provisioned VMs, see: https://gerrit.ovirt.org/c/ovirt-engine/+/115009


> --
> Nathanaël Blanchet
>
> Supervision réseau
> SIRE
> 227 avenue Professeur-Jean-Louis-Viala
> 34193 MONTPELLIER CEDEX 5
> Tél. 33 (0)4 67 54 84 55
> Fax  33 (0)4 67 54 84 14
> blanc...@abes.fr
> ___
> Users mailing list -- users@ovirt.org
> 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/7VSOFV3TFSMKPEZBI2ERRVUCTFGJALQT/
>
___
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/BPLB4DXKM4L7CYWU4UG47JHKI6BRV35P/


[ovirt-users] Re: VM Image is Locked after cleaning up of problematic snapshot.

2022-02-06 Thread Arik Hadas
On Sat, Feb 5, 2022 at 9:00 AM Muhammad Aidilfitri Bin Saleh <
darketemp...@outlook.sg> wrote:

> Hello Everyone,
>
> I requires your input as the VM that is currently Hosted on Ovirt 4.4.4.5
> is showing a locked Icon in the status column. I am unable to perform any
> actions on this particular VM as it shows that the "Snapshot is currently
> being created for VM 
>
> There was a failed snapshot attempt executed earlier but I have gone
> through the steps to identified and unlock the said images and snapshot
> using the build tools /usr/share/ovirt-engine/setup/dbutils. I even went
> into the DB to identified the failed snapshot but still no luck.
>
> I have restarted the ovirt-engine service and also the Standalone VM
> hosting this Ovirt-Engine but still not able to release the VM. I have also
> performed the ovirt-setup but still no luck on this portion.
>

This means that the tasks of the snapshot command are still in the database
and lead to restoring the VM lock (which is an in-memory lock) when the
ovirt-engine service starts.
You can try to identify the relevant rows and removes them from the
'command_entities' table in the database and then restart ovirt-engine


>
> Any assistance is appreciated.
> ___
> 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/J27TETBLQKRWVWFJ5W6YUAA2T34DICOE/
>
___
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/MQH2K5JSHM34N3MYEYIGK3DWNK7KLQTO/


[ovirt-users] Re: support of AMD EPYC 3rd Genneration Milan

2022-01-20 Thread Arik Hadas
On Thu, Jan 20, 2022 at 6:16 PM Sandro Bonazzola 
wrote:

>
>
> Il giorno sab 8 gen 2022 alle ore 18:47 samuel@horebdata.cn <
> samuel@horebdata.cn> ha scritto:
>
>> Helllo, Ovirt experts,
>>
>> Does Ovirt now support the use of AMD EPYC 3rd Genneration Milan CPU? and
>> if yes, from which version?
>>
>>
> AMD EPYC Milan CPU should be supported by Advanced Virtualization since
> June 2021, included in oVirt Node 4.4.6.1 and newer.
> Within oVirt I think it's recognized as "EPYC" without real distinction
> between Milan, Rome or others.
> +Arik Hadas  ?
>

Right, there's no distinction, they are all compared against the two
variants we have for AMD EPYC (insecure/secure) that you can find in:
https://github.com/oVirt/ovirt-engine/blob/ovirt-engine-4.4.10.4/packaging/dbscripts/upgrade/pre_upgrade/_config.sql#L1248-L1249


>
> --
>
> 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.*
>
>
>
___
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/FC6FJVDHDQSXE4F4T32KHBIPFYZKJCLL/


[ovirt-users] Re: Lack of attribute "decode" in v2v module

2021-12-30 Thread Arik Hadas
On Thu, Dec 30, 2021 at 7:40 PM Diego Ercolani 
wrote:

> Hello,
>
> As asked by Stefano Stagnaro I'm currently writing about an issue I'm
> experiencing during vm import from external VMWARE farm:
>
> I have the system log full of error:
>
> Dec 30 13:23:42 ovirt-node2.ovirt vdsm[3420]: *ERROR Internal server
> error*
>
>  *Traceback (most recent call last):*
>
>  *  File "/usr/lib/python3.6/site-packages/yajsonrpc/__init__.py", line
> 349, in _handle_request*
>
>  *res = method(**params)*
>
>  *  File "/usr/lib/python3.6/site-packages/vdsm/rpc/Bridge.py", line 194,
> in _dynamicMethod*
>
>  *result = fn(*methodArgs)*
>
>  *  File "", line 2, in getStats*
>
>  *  File "/usr/lib/python3.6/site-packages/vdsm/common/api.py", line 50,
> in method*
>
>  *ret = func(*args, **kwargs)*
>
>  *  File "/usr/lib/python3.6/site-packages/vdsm/API.py", line 1456, in
> getStats*
>
>  *multipath=True)*
>
>  *  File "/usr/lib/python3.6/site-packages/vdsm/host/api.py", line 49, in
> get_stats*
>
>  *decStats = stats.produce(first_sample, last_sample)*
>
>  *  File "/usr/lib/python3.6/site-packages/vdsm/host/stats.py", line 108,
> in produce*
>
>  *stats['v2vJobs'] = v2v.get_jobs_status()*
>
>  *  File "/usr/lib/python3.6/site-packages/vdsm/v2v.py", line 290, in
> get_jobs_status*
>
>  *'description': job.description,*
>
>  *AttributeError: 'str' object has no attribute 'decode'*
>
> As stated in the error: line 290 of
> */usr/lib/python3.6/site-packages/vdsm/v2v.py*
>
> Uses the method "decode" that it doesn't seem to be enabled:
>
>'description': job.description.decode('utf-8'),
>
>  [root@ovirt-node2 ~]# rpm -qf
> /usr/lib/python3.6/site-packages/vdsm/v2v.py
>

Hi, this will be fixed in 4.4.10 (see
https://bugzilla.redhat.com/show_bug.cgi?id=2026809)


>
>
>
>
> --
>
> Ing. Diego Ercolani
>
> S.S.I.S. s.p.a.
>
> T. 0549-875910
>
> ___
> 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/CJBISCMAOZYJHJJLL6PSDSLWYRTXZNOY/
>
___
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/WJKOOPYJCE5ZLRVZG6SFKWXA3EWDDYCZ/


[ovirt-users] Re: virsh list --all only shows running on host

2021-12-22 Thread Arik Hadas
On Wed, Dec 22, 2021 at 8:04 AM Yedidyah Bar David  wrote:

> On Tue, Dec 21, 2021 at 5:21 PM richmoch--- via Users 
> wrote:
>
>> Which engine are you referring to ?
>
>
> Perhaps search the net for something like 'ovirt architecture' to get an
> overview.
>
>
>>   The engine is up but the VM ( or domain )  is only down.
>>
>> So for this link :
>>
>>
>> https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.0/html/virtual_machine_management_guide/sect-exporting_and_importing_virtual_machines_and_templates
>>
>> Under the section Procedure 6.27. Importing a Virtual Machine from KVM, I
>> am able to connect to the KVM and it gives me a list of only the running
>> VMs . The caveat is the VM needs to be down  to import ( understandably ),
>> so if I go and shutdown the VM  on the remote KVM host, it no longer
>> appears in the list .
>>
>> So how does one go about selecting the VM ( which is down ) from the list
>> when it is not seen ?
>>
>
> I am not sure exactly what you are trying to do, nor whether the above
> document is relevant to this. Please clarify exactly what you want to do,
> or what your question/issue is.
>

Right, the above mentioned section doesn't refer to hosts that are part of
an oVirt cluster but "external" hosts that hold persistent domains you want
to import to an oVirt cluster


>
> If you are experienced with libvirt/virsh and expected the oVirt is just a
> (shallow) wrapper around that, and that you can continue using
> libvirt/virsh as you are/were used to, well, it's not like that. Indeed in
> certain cases your knowledge will be relevant for
> debugging/troubleshooting, perhaps supplying custom hooks if needed, but
> not more than that.
>
> Best regards,
> --
> 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/VZJU55YHQHQ4BK3NG3CZZAFHQ3VIT5PQ/
>
___
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/CVK6JDMG7EVIN63SFT2SKY7QVBU3QNTX/


[ovirt-users] Re: import vm from iscsi storage domain fails with "Cannot import VM. Invalid time zone for given OS type. Attribute: vm.vmStatic"

2021-12-15 Thread Arik Hadas
On Wed, Dec 15, 2021 at 11:25 AM Saif Abu Saleh  wrote:

> In addition to what Liran said
>
> This time-zones lines is what we had issue with before 4.4.9:
>

Right so another alternative is to upgrade to 4.4.9 that contains a fix for
the following bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1999651


>
> America/Indianapolis=US Eastern Standard Time
> Europe/Warsaw=Central European Standard Time
>
> If you don't know really the time-zone of the VM, you can try to add them
>
> To add them, there is also new provided documentation here:
> https://www.ovirt.org/documentation/virtual_machine_management_guide/index.html#Configuring_timezones
>
> Thanks,
> Saif
>
> On Wed, Dec 15, 2021 at 11:18 AM Liran Rotenberg 
> wrote:
>
>>
>>
>> On Wed, Dec 15, 2021 at 8:26 AM  wrote:
>>
>>> Dear ovirt users,
>>> we are running RHV 4.4.8.6-0.1.el8ev on the manager and Red Hat
>>> Virtualization Host 4.4.6 (el8.4) on the hypervisors. Normally I would open
>>> a case at Red Hat but our subscriptions expired. We are currently in the
>>> process of purchasing new ones but this problem is really urgent so I
>>> thought I'd give it a try here. Sorry for that if its misplaced.
>>> We have a problem importing some VMs from a iscsi storage domain. We had
>>> an outage of the iscsi san volume but managed to recover the data and bring
>>> them back online. We imported the volume into a new data center and were
>>> able to import most of the vms which were on that volume. But now there are
>>> still some importand ones left and we do get the upper mentioned error.
>>> I searched the web and found a solution which proposes to alter the
>>> "operating system type" in the import dialog and change it to "linux". Oh,
>>> while writing "linux" I forgot to mention all of the problematic vms are
>>> windows ones. But the import dialog doesn't let me change the operation
>>> system type. I can only change the name.
>>> I found another solution here in the archive of this mailing list. Its
>>> pretty new I think. Topic was "How to re-import a VM with an invalid
>>> timezone?" in August. The solution was to add the missing timezone in a
>>> file (
>>> https://github.com/oVirt/ovirt-engine/blob/master/packaging/conf/timezones-defaults.properties#L18-L22)
>>> on the manager and restart ovirt-engine. I would love to try that but I
>>> really don't know what to put there. I can't open an ova file because the
>>> vm is on the iscsi domain in some lvs or metadata or .. I don't know where
>>> RHV reads that from.
>>>
>>
>> Hi Timo,
>> As written in the documentation of the timezones properties, you need to
>> create a new file: 10-timezones.properties in the same directory.
>> Then you need to add the timezone like this example - if the VM set
>> with Eastern Standard Time (-5:00):
>> America/Indianapolis=US Eastern Standard Time
>> But, you need to add the time zone you miss (the time zone the imported
>> VM is set with).
>>
>> Regards,
>> Liran
>>
>>>
>>> Hope I am not missing some important info. Any help would be greatly
>>> appreciated
>>> Cheers
>>> Timo
>>> ___
>>> 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/VTTD2OUROCHTV4R6ORIJ6PUDB56MR7DF/
>>>
>> ___
> 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/7C7TMSUX4CCOFEASK6IXAHDNPYVDKPGH/
>
___
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/K6RL3OQTXG62SPWUNB4FXSYL5XJ6ZY4X/


[ovirt-users] Re: Migrated a VM from VMware to Ovirt using import ova option. Task stuck and running for day 2 now.

2021-12-08 Thread Arik Hadas
On Wed, Dec 8, 2021 at 8:44 AM  wrote:

> 1. First node that was upgraded now continuously logs this error:
> VDSM  command Get Host Statistics failed: Internal JSON-RPC
> error:
> {'reason': "'str' object has no attribute 'decode'"}
> 2. During import of two virtual machines from VMware (has done multible
> before upgrade)
> the import seems to never finish - currently running on day 2-3... any
> clues how to fix
> this?
>
> Events VDSM  command Get Host Statistics failed: Internal
> JSON-RPC error:
> {'reason': "'str' object has no attribute 'decode'"} running for 2 days
> every 20 seconds. Please suggest
>

Looks like [1], however in that report the import process succeeded despite
those errors.
Can you please share the import logs?

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


> ___
> 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/37YK2JLWZQX6654X46UQ7QNDQYINAHFM/
>
___
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/IXXX2OZVCJEPUEXSU5V5MXBL2FQXRTKH/


[ovirt-users] Re: no QXL ?

2021-12-07 Thread Arik Hadas
On Wed, Dec 8, 2021 at 3:53 AM Colin Coe  wrote:

> For us, SPICE lets us present VMs in secure networks to unsecure
> locations.  RDP and VNC will not work for us.
>
> I didn't want to rant but why Red Hat drops useful features is beyond me.
> First Satellite 5 (Spacewalk), GlusterFS, not RHV.  Yep, we've been a RHV
> customer since RHEV v2.2 days.  SPICE was the compelling feature then and
> remains so.
>
> My 2 cents
>
> On Wed, 8 Dec 2021 at 03:42, Alex McWhirter  wrote:
>
>> It's being removed from RHEL 9, unsure of reasoning.
>>
>> So this mean that oVirt cannot offer SPICE/QXL on RHEL9, there is no
>> spice package, qemu is compiled without SPICE/QXL support, the kernel does
>> not support QXL video drivers.
>>
>> It's not that oVirt is killing off SPICE/QXL, but rather RHEL9 is and
>> oVirt cannot support a feature not available on the host OS unless 3rd
>> party packages or a SiG makes them available
>>
>
Right
The idea was to have a new cluster level on which we can provide the
latest-and-greatest fixes and capabilities and so to base it on CentOS
stream 9 where SPICE is not available
We anyway intend to keep SPICE in oVirt 4.5 on lower cluster levels, which
should work as long as the hosts are not upgraded to CentOS stream 9


> .
>>
>>
>> On 2021-12-07 14:14, Patrick Hibbs wrote:
>>
>> Hello,
>>
>> Can I ask why this is being removed?
>>
>> The linked bugzilla report doesn't give a reason, and at least two others
>> have expressed concerns over SPICE's deprecation.
>>
>> Personally, I would like to know why it's being removed entirely with no
>> recourse instead of becoming an option to enable in the VM config, or an
>> optional RPM that can be installed by the sysadmin.
>>
>> Thanks.
>>
>> On Tue, 2021-12-07 at 09:41 +0200, Arik Hadas wrote:
>>
>>
>>
>> On Tue, Dec 7, 2021 at 8:33 AM Patrick Hibbs 
>> wrote:
>>
>> Hello,
>>
>> Are we to assume that VNC mode is the only thing that will be supported
>> for the VM consoles moving forward then?
>> As the pure SPICE mode only works with QXL display as far as I can tell.
>>
>> I ask because the VNC or SPICE+VNC modes haven't worked in my environment
>> for over a year now, and that change
>> would effectively prevent the use of any VM console in my environment.
>>  (Use of VNC with remote viewer always gives
>> me an authentication error.) Not that it's a normal environment, but that
>> kind of thing should be advertised more. Just in case
>> simillar issues exist in other deployments.
>>
>>
>> Yes, one would need to make sure vnc/vga works well before upgrading to
>> the next cluster-level (in oVirt 4.5)
>> In general it is recommended to test the configuration in the new
>> cluster-level by setting some representative VMs in the environment with a
>> custom compatibility level  and check that they work properly before
>> upgrading to that cluster-level.
>>
>>
>>
>> Thanks.
>>
>> On Mon, 2021-12-06 at 22:03 +0200, Arik Hadas wrote:
>>
>>
>>
>> On Mon, Dec 6, 2021 at 8:45 PM lejeczek via Users 
>> wrote:
>>
>>
>>
>> On 06/12/2021 17:42, lejeczek via Users wrote:
>> > Hi.
>> >
>> > I've Qemu/Libvirt from
>> >
>> ovirt-release-master-4.5.0-0.0.master.20211206152702.gitebb0229.el9.noarch
>> > and it seems QXL is not there.
>> > Is that a fluke or intention?
>> > Do you have QXL working?
>> >
>> upss.. pardon me, these are from CentOS 9 Steam own repos
>> actually.
>>
>>
>>
>> Right, and that's the reason for the ongoing work on removing qxl on
>> cluster level 4.7:
>> https://bugzilla.redhat.com/show_bug.cgi?id=1976607
>>
>>
>> ___
>> 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/DZMAQQJMPHD2L4DPVHTET5N4KB4MZDUY/
>>
>> ___
>> 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:
>> htt

[ovirt-users] Re: no QXL ?

2021-12-06 Thread Arik Hadas
On Tue, Dec 7, 2021 at 8:33 AM Patrick Hibbs  wrote:

> Hello,
>
> Are we to assume that VNC mode is the only thing that will be supported
> for the VM consoles moving forward then?
> As the pure SPICE mode only works with QXL display as far as I can tell.
>
> I ask because the VNC or SPICE+VNC modes haven't worked in my environment
> for over a year now, and that change
> would effectively prevent the use of any VM console in my environment.
>  (Use of VNC with remote viewer always gives
> me an authentication error.) Not that it's a normal environment, but that
> kind of thing should be advertised more. Just in case
> simillar issues exist in other deployments.
>

Yes, one would need to make sure vnc/vga works well before upgrading to the
next cluster-level (in oVirt 4.5)
In general it is recommended to test the configuration in the new
cluster-level by setting some representative VMs in the environment with a
custom compatibility level  and check that they work properly before
upgrading to that cluster-level.


>
> Thanks.
>
> On Mon, 2021-12-06 at 22:03 +0200, Arik Hadas wrote:
>
>
>
> On Mon, Dec 6, 2021 at 8:45 PM lejeczek via Users  wrote:
>
>
>
> On 06/12/2021 17:42, lejeczek via Users wrote:
> > Hi.
> >
> > I've Qemu/Libvirt from
> >
> ovirt-release-master-4.5.0-0.0.master.20211206152702.gitebb0229.el9.noarch
> > and it seems QXL is not there.
> > Is that a fluke or intention?
> > Do you have QXL working?
> >
> upss.. pardon me, these are from CentOS 9 Steam own repos
> actually.
>
>
> Right, and that's the reason for the ongoing work on removing qxl on
> cluster level 4.7:
> https://bugzilla.redhat.com/show_bug.cgi?id=1976607
>
>
> ___
> 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/DZMAQQJMPHD2L4DPVHTET5N4KB4MZDUY/
>
> ___
> 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/22NZAQL46WMEFFKQ66EKZBHGE5KCX3MY/
>
>
> ___
> 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/GT5YYVAFM4P7AMCFFCJNYZO75Y6M3H4R/
>
___
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/A3SCN663TVNEKPK3O2SZXJGHVVBXTQ77/


[ovirt-users] Re: no QXL ?

2021-12-06 Thread Arik Hadas
On Mon, Dec 6, 2021 at 8:45 PM lejeczek via Users  wrote:

>
>
> On 06/12/2021 17:42, lejeczek via Users wrote:
> > Hi.
> >
> > I've Qemu/Libvirt from
> >
> ovirt-release-master-4.5.0-0.0.master.20211206152702.gitebb0229.el9.noarch
> > and it seems QXL is not there.
> > Is that a fluke or intention?
> > Do you have QXL working?
> >
> upss.. pardon me, these are from CentOS 9 Steam own repos
> actually.
>

Right, and that's the reason for the ongoing work on removing qxl on
cluster level 4.7:
https://bugzilla.redhat.com/show_bug.cgi?id=1976607


> ___
> 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/DZMAQQJMPHD2L4DPVHTET5N4KB4MZDUY/
>
___
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/22NZAQL46WMEFFKQ66EKZBHGE5KCX3MY/


[ovirt-users] Re: on-demand machine creation for VDI project

2021-12-05 Thread Arik Hadas
On Sun, Dec 5, 2021 at 12:33 PM Luca Contessa 
wrote:

> Hi List,
>
> I've made an oVirt node installation (oVirt ver. 4.4.9) for a VDI project
> and I'd like to ask if it is possible to create an empty pool with a
> maximum number of machine and as the machine are required by the end user
> (so when the users use the think client to request the provisioning of a
> machine of the pool in question) the pool will dynamically create the
> machine and link it to the end user.
>
> To specify once more the pool will be create with no machine in it, only a
> maximum limit on the number of machines, and as the user start connecting
> to the pool the VM will be created, started and provisioned to the user
> requesting them.
>
> Then when the user stop using the machine they would like the system to
> save the datas and stop the machine and from that point on when the user
> will connect the virtual machine connected to their account on the AD
> system should start.
>
> Do you know if this is possibile?
>

oVirt doesn't provide that exact behavior but maybe the existing behavior
could also fit your needs.
You can't create a pool that is initially empty and grows as users ask for
VMs - the VMs are rather created when creating the pool. From a storage
perspective, empty thin-provisioned volumes are created on top of the
template volumes so they don't consume much space. From a virtualization
perspective, no compute resources are consumed until the VMs are started.
Having the VMs created "in advance" enables users to take VMs faster -
there's no need to create them but just to assign and start them.
As for the second part, you can configure a console disconnect option to
shut-down/power-off so when a user disconnects, the VM would stop. If you
wish VMs to remain assigned to users also when they go down, you can set
the pool to "manual" mode and then VMs remain assigned until the admin
detaches their assigned users.



> Thanks a lot to everybody,
>
> Luca
> ___
> 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/WYA3BCC6CXBFG2WFRWKVSKFJMCTIA2NX/
>
___
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/EGDCZ2GGCGDTEPQ6KU4L2BATIEIWCXI4/


[ovirt-users] Re: How to turn off the state of tlbflush for Windows vm

2021-12-05 Thread Arik Hadas
On Sun, Dec 5, 2021 at 12:36 PM Hean-Seng Tan 
wrote:

> We encounter random Windows BSOD (blue screen of death) issues for vm's in
> environment running oVirt Engine 4.4.4. Upgrading the environment to 4.4.8
> does not fix the issue. There is a suggestion from
> https://bugzilla.redhat.com/show_bug.cgi?id=1868572 to turn off the state
> of tlbflush under hyperv section for the Windows vm. Does anyone know how
> to achieve that?
>

Didn't the alternatives that were specified in
https://bugzilla.redhat.com/show_bug.cgi?id=1868572#c130 work for you?


>
> Currently, vm description returned from api call includes the following
> section that has tlbflush 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/XRHQE3HHSVKHKC474FX5PFCJ7HKAL7ZU/
>
___
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/BJNJDK47EM32OXLOCRT3GN7BTMJACXGL/


[ovirt-users] Re: create custom scheduling policy

2021-11-16 Thread Arik Hadas
On Sun, Nov 14, 2021 at 12:40 AM Hadiyansyah Hadiyansyah 
wrote:

> hi all,
>
> i have 4 host in the cluster, i wanna create custom schedulin policy for
> this cluster with condition.
> - max vm guest on single host is 10 vms
>

For this you can check [1] (from slide 9 onward)


> - host with 70% cpu, vm guest cant migrate to this host
>

I'm not sure whether you can differentiate VMs that are migrating to a host
from VMs that start on a host

[1] https://resources.ovirt.org/old-site-files/Scheduler-Deep-Dive-oVirt.pdf


>
> anyone can help me for explained this condition to create custom
> scheduling policy ?


>
> thanks
>
> hadi
> ___
> 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/KNYQMS5BUMNHQWK6HEUWEBV2QBNIRLKB/
>
___
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/2P6BWCBWXQNW24ORG5I225ZQQL4WDQWE/


[ovirt-users] Re: Viewing and hopefully, modifying the VM's qemu command line

2021-11-09 Thread Arik Hadas
On Tue, Nov 9, 2021 at 11:57 AM Gilboa Davara  wrote:

> (Sorry: Pressed send too fast...)
> 3. I'm facing some odd memory allocation issues (only if the VM is Q35,
> all works well if the VM is configured as i440fx), which may require me to
> change additional VM parameters.
>
> BTW, ironically, the two other hosts in the same cluster, with older MBs,
> have zero issues with GPU/Audio/USB passthrough...)
>
> - Gilboa
>
> On Tue, Nov 9, 2021 at 11:52 AM Gilboa Davara  wrote:
>
>> Hello,
>>
>> Many thanks for the prompt reply.
>>
>> On Mon, Nov 8, 2021 at 8:52 PM Nir Soffer  wrote:
>>
>>> On Mon, Nov 8, 2021 at 5:47 PM Gilboa Davara  wrote:
>>> >
>>> > Hello all,
>>> >
>>> > I'm setting up a fairly (?) complex oVirt over Gluster setup built
>>> around 3 Xeon servers-turned-into-workstations, each doubling as oVirt node
>>> + one primary Fedora VM w/ a dedicated passthrough GPU (+audio and a couple
>>> of USB root devices).
>>> > One of the servers seems to have some weird issue w/ the passthrough
>>> nVidia GPU that seems to require me to edit the VM iommu (1) and
>>> passthrough device (2) command line.
>>> > I tried using the qemu-cmdline addon to add the missing parameters,
>>> but it seems that qemu treats the added parameters as an additional device
>>> / iommu instead of editing the existing parameters.
>>> >
>>> > So:
>>> > 1. How can I view the VM qemu command line?
>>>
>>> less /var/log/libvirt/qemu/vm-name.log
>>>
>>
>> Found it, thanks!
>>
>>
>>> > 2. Can I somehow manually edit the qemu command line, either directly
>>> or by somehow adding parameters in the HE XML file?
>>>
>>> I think this should be possible via vdsm hook, but hooks are bad.
>>> Can you explain what do you want to change?
>>>
>>> Nir
>>>
>>
>> 1. IOMMU:
>> -device intel-iommu,intremap=on,eim=on
>> To (Add: caching-mode=on, per qemu log message)
>> -device intel-iommu,intremap=on,eim=on,caching-mode=on
>> (2021-11-05T18:42:36.651191Z qemu-kvm: We need to set caching-mode=on for
>> intel-iommu to enable device assignment with IOMMU protection.)
>>
>
Note that this one should be fixed in the latest ovirt-engine
(ovirt-engine-4.4.9.4) -
https://bugzilla.redhat.com/show_bug.cgi?id=2013752


>
>> 2. Device:
>> -device
>> vfio-pci,host=:84:00.0,id=ua-c774115b-c0ee-43a5-97c8-12ac73cb6f3a,bus=pci.10,addr=0x0
>>
>> -device
>> vfio-pci,host=:84:00.1,id=ua-3c7d3b66-57aa-470b-afc8-78383ac9a025,bus=pci.8,addr=0x0
>> To (Attach hdmi sound as function of GPU, possibly add x-vga=on):
>> -device
>> vfio-pci,host=:84:00.0,id=ua-c774115b-c0ee-43a5-97c8-12ac73cb6f3a,bus=pci.8.0,x-vga=on,addr=0x0
>>
>> -device
>> vfio-pci,host=:84:00.1,id=ua-3c7d3b66-57aa-470b-afc8-78383ac9a025,bus=pci.8.1,addr=0x0
>>
>> 3. I'm facing some odd memory allocation issues (only if the VM is Q35,
>> all works well if the VM is configured as i440fx), which may req
>>
> ___
> 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/XKZLE6ZEU7ZNXSMYEMA65F6MJBSNZQVD/
>
___
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/Q6RIJCHHPJYNQEQNB73S22M5KYDUCRJC/


[ovirt-users] Re: importing an ovirt vm via the API for "Virtual Appliance OVA"

2021-10-03 Thread Arik Hadas
On Fri, Oct 1, 2021 at 10:08 AM Vojtech Juranek  wrote:

> On Friday, 1 October 2021 07:51:56 CEST di...@santanas.co.za wrote:
> > Hi oVirt Team,
> >
> > Reading the API docs
> >
> >
> http://ovirt.github.io/ovirt-engine-api-model/4.3/#services/external_vm_impo
> > rts
> >
> http://ovirt.github.io/ovirt-engine-api-model/4.3/#types/external_vm_provid
> > er_type
> > and ovirt_vm module
> >
> https://docs.ansible.com/ansible/latest/collections/ovirt/ovirt/ovirt_vm_mod
> > ule.html#ansible-collections-ovirt-ovirt-ovirt-vm-module
>
> > I see support for
> > - kvm
> > - vmware
> > - XEN
> >
> > In the oVirt web GUI (4.3) there is under compute -> VM -> import ->
> > source options for:
> > - kvm
> > - vmware
> > - XEN
> > - Virtual Appliance OVA
> >
> > I'm trying to import an OVA that sits on the file system on the oVirt
> > node.  Via the GUI selecting Virtual Appliance OVA does the job.
> >
> > Is the API missing this functionality or am I missing something?
>
> here is example how to import OVA file (for 4.4, not
> sure about 4.3, but probably should work as well):
>
>
> https://github.com/oVirt/python-ovirt-engine-sdk4/blob/main/examples/import_vm_from_ova.py


Yeah, and just to elaborate on that a bit - it doesn't matter which
provider is set there. Even though it is set to KVM in that example, we
don't look at it
For OVA, the important part is to have the URL in the form of "ova://" and oVirt will figure out if it's an OVA that was generated by
oVirt or by a different platform regardless of the provider you set


>
>
>
> > --
> > Divan Santana
> > ___
> > 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/2WWHXYKDSB2PG
> > QVEQEV3FUPDWNCQBUXY/
>
> ___
> 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/YWAC57VJL6MZX6K53QUWCGMJAMAYQH24/
>
___
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/3KNDYIVHZDGNKYNNOGNZQFWOIAXBEEQE/


[ovirt-users] Re: qemu-guest-agent not reporting IP address on boot?

2021-10-03 Thread Arik Hadas
On Fri, Oct 1, 2021 at 5:51 PM  wrote:

> Hi folks,
>
> Kali Linux repos (based on Debian) no longer ship ovirt-guest-agent, and
> instead package qemu-guest-agent. However, since this upgrade VMs based on
> Kali no longer report their IP address to oVirt (and therefore timeout
> during provisioning). If I interact with the VM console, the VM does have
> an IP address, and the agent is running, yet oVirt reports N/A IP address.
> I've tried restarting the agent, but that does not help. If I load the
> console and use the VM it seems to increase the chances the IP address will
> eventually makes it's way to oVirt, although I can't seem to reproduce an
> update, or get it to provide the IP address on boot so that provisioning
> works reliably.
>
> Any suggestions would be really appreciated.
>

Might be the same as/related to
https://bugzilla.redhat.com/show_bug.cgi?id=1981946 which is still being
investigated


>
> Thank you.
>
> Cheers,
> Cliffe.
> ___
> 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/FFINLLXPBRKYHNTBEI5GKZY53C3KX2OD/
>
___
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/74CM5T4SEC66H7KR3N6KWCVN3BJQ6WEI/


[ovirt-users] Re: Sparse VMs from Templates - Storage issues

2021-08-11 Thread Arik Hadas
On Wed, Aug 11, 2021 at 2:56 PM Benny Zlotnik  wrote:

> > If your vm is temporary and you like to drop the data written while
> > the vm is running, you
> > could use a temporary disk based on the template. This is called a
> > "transient disk" in vdsm.
> >
> > Arik, maybe you remember how transient disks are used in engine?
> > Do we have an API to run a VM once, dropping the changes to the disk
> > done while the VM was running?
>
> I think that's how stateless VMs work
>

+1
It doesn't work exactly like Nir wrote above - stateless VMs that are
thin-provisioned would have a qcow volume on top of each template's volume
and when they starts, their active volume would be a qcow volume on top of
the aforementioned qcow volume and that active volume will be removed when
the VM goes down
But yeah, stateless VMs are intended for such use case
___
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/6OALP5LAFBRYZ46ONUFPC2JV7UIOLMJF/


[ovirt-users] Re: Storage Domains for a VM from Template

2021-08-09 Thread Arik Hadas
On Mon, Aug 9, 2021 at 1:31 PM Shantur Rathore 
wrote:

> Thanks Arik,
>
> I am interested in the Thin approach.
> Is it not possible to create it on another storage domain ? Even with API ?
>
> I read here
> http://ovirt.github.io/ovirt-engine-api-model/4.4/#services/vms
>
> *When creating a virtual machine from a template or from a snapshot it is
> usually useful to explicitly indicate in what storage domain to create the
> disks for the virtual machine. If the virtual machine is created from a
> template then this is achieved passing a set of disk_attachment elements
> that indicate the mapping:*
>

It's not possible to create a thin-provisioned VM disk on a storage domain
that doesn't hold the corresponding template's disk, even from the api
But if you copy the template's disk(s) to the target storage domain
beforehand then you can create the thin-provisioned VM disks there using
the api as described above


>
>
> Thanks,
> Shantur
>
> On Mon, Aug 9, 2021 at 11:19 AM Arik Hadas  wrote:
>
>>
>>
>> On Mon, Aug 9, 2021 at 12:55 PM Shantur Rathore <
>> shantur.rath...@gmail.com> wrote:
>>
>>> Hi all,
>>>
>>> I have multiple storage domains in my DC. One is backed up that has
>>> templates and another one which isn't backed up and I want to use it for VM
>>> instances of the template.
>>>
>>> I cannot find an option to create the VM from a template and use a
>>> storage domain other than where the template is stored.
>>>
>>> Is it even possible?
>>>
>>
>> Assuming you're asking about the administration portal, it depends on the
>> selected allocation policy (which you can find in the Resource Allocation
>> tab of the add-VM dialog):
>> - If it is set to 'Clone' then you can select any other storage domain
>> that is available in the DC to clone the template's disk to
>> - If it is set to 'Thin' then a VM disk must reside on a storage domain
>> that contains the template's disk it is based on. You can copy the
>> template's disk(s) to another storage domain if you want a VM disk to be
>> created there
>>
>>
>>>
>>> Thanks,
>>> Shantur
>>> ___
>>> 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/SKR6URQN7IH5OYI4MEIVEY2QZZSX2XTY/
>>>
>>
___
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/LENONTKMHJUH7UG2ORIWW5R5CEKYGJYI/


[ovirt-users] Re: Storage Domains for a VM from Template

2021-08-09 Thread Arik Hadas
On Mon, Aug 9, 2021 at 12:55 PM Shantur Rathore 
wrote:

> Hi all,
>
> I have multiple storage domains in my DC. One is backed up that has
> templates and another one which isn't backed up and I want to use it for VM
> instances of the template.
>
> I cannot find an option to create the VM from a template and use a storage
> domain other than where the template is stored.
>
> Is it even possible?
>

Assuming you're asking about the administration portal, it depends on the
selected allocation policy (which you can find in the Resource Allocation
tab of the add-VM dialog):
- If it is set to 'Clone' then you can select any other storage domain that
is available in the DC to clone the template's disk to
- If it is set to 'Thin' then a VM disk must reside on a storage domain
that contains the template's disk it is based on. You can copy the
template's disk(s) to another storage domain if you want a VM disk to be
created there


>
> Thanks,
> Shantur
> ___
> 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/SKR6URQN7IH5OYI4MEIVEY2QZZSX2XTY/
>
___
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/KZFUFIPCZDWSOCHBIENKW4NGCZ7HFZY3/


[ovirt-users] Re: cloning a template using Rest Api

2021-07-29 Thread Arik Hadas
On Thu, Jul 22, 2021 at 4:29 AM Pascal D  wrote:

> What is the easiest way to clone a template using rest api. I know I can
> create a VM from a template then make a new template from this new VM but I
> would like to just clone a template directly so I can maintain different
> branches
>

I'm afraid there's no easier way than what you described
What do you mean by "maintain different branches?"


>
> TIA
> ___
> 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/5G72TQZIJXLXBNZGCERXD6Y7JN6PFQCS/
>
___
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/34ER4YDV7WTIQN3YKI4ICYWSHDKO4RD2/


[ovirt-users] Re: oVirt and ARM

2021-07-14 Thread Arik Hadas
On Wed, Jul 14, 2021 at 3:14 PM Milan Zamazal  wrote:

> Arik Hadas  writes:
>
> > On Wed, Jul 14, 2021 at 10:36 AM Milan Zamazal 
> wrote:
> >
> >> Marko Vrgotic  writes:
> >>
> >> > Dear Arik and Milan,
> >> >
> >> > In the meantime, I was asked to check if in current 4.4 version or
> >> > coming 4.5, are/will there any capabilities or options of emulating
> >> > aarch64 on x86_64 platform and if so, what would be the steps to
> >> > test/enable it.
> >> >
> >> > Can you provide some information?
> >>
> >> Hi Marko,
> >>
> >> I don't think there is a way to emulate a non-native architecture.
> >> Engine doesn't have ARM support and it cannot handle ARM (native or
> >> emulated) hosts.  You could try to run emulated ARM VMs presented as x86
> >> to Engine using Vdsm hooks but I doubt it would work.
> >>
> >
> > Oh I just sent a draft I had in my mailbox without noticing this comment
> > and I see we both mentioned Vdsm hook
> > What is the source of the doubts about Vdsm hooks to work for this?
>
> It's possible to override the domain XML obtained from Engine to change
> it from x86 to ARM but Engine will get back the non-x86 domain XML.
> Engine may not care about the emulator but perhaps it can be confused by
> the reported CPU etc.  There can be problems with devices and
> architecture specific settings in both the directions.  Engine will base
> assumptions about the VM capabilities based on x86, which won't exactly
> match ARM.
>

Yeah, it would be best to try and see what the misalignment between what
the engine thinks and what the VM runs with leads to
But from the top of my head I don't think a misalignment in regards to CPU
or capabilities could be problematic since the engine doesn't check what
the VM is actually set with, it just assumes that the VM is set with what
it wrote to its domain XML
The engine certainly looks at the devices but as long as they preserve
their user-alias, managed devices won't be unplugged. Other devices would
be added as unmanaged. So I think that should also be fine.


>
> Maybe it'd be possible to simply run and stop a VM with some effort and
> it would be enough for certain purposes.  But for more than that it's a
> question whether the effort would be better spent on implementing a
> proper architecture support.


> >> I'm afraid the only way is to add ARM support to oVirt.  My former
> >> colleague has played with running oVirt on Raspberry Pi hosts some years
> >> ago (there are traces of that effort in Vdsm) and I think adding ARM
> >> support should be, at least in theory, possible.  Particular features
> >> available would be mostly dependent on ARM support in QEMU and libvirt.
> >
> >
> >> Regards,
> >> Milan
> >>
> >> > -
> >> > kind regards/met vriendelijke groeten
> >> >
> >> > Marko Vrgotic
> >> > Sr. System Engineer @ System Administration
> >> >
> >> > ActiveVideo
> >> > o: +31 (35) 6774131
> >> > m: +31 (65) 5734174
> >> > e: m.vrgo...@activevideo.com<mailto:m.vrgo...@activevideo.com>
> >> > w: www.activevideo.com<http://www.activevideo.com>
> >> >
> >> > ActiveVideo Networks BV. Mediacentrum 3745 Joop van den Endeplein
> >> > 1.1217 WJ Hilversum, The Netherlands. The information contained in
> >> > this message may be legally privileged and confidential. It is
> >> > intended to be read only by the individual or entity to whom it is
> >> > addressed or by their designee. If the reader of this message is not
> >> > the intended recipient, you are on notice that any distribution of
> >> > this message, in any form, is strictly prohibited.  If you have
> >> > received this message in error, please immediately notify the sender
> >> > and/or ActiveVideo Networks, LLC by telephone at +1 408.931.9200 and
> >> > delete or destroy any copy of this message.
> >> >
> >> >
> >> >
> >> > From: Sandro Bonazzola 
> >> > Date: Friday, 9 July 2021 at 15:37
> >> > To: Marko Vrgotic , Arik Hadas
> >> > , Milan Zamazal 
> >> > Cc: Evgheni Dereveanchin , Zhenyu Zheng
> >> > , Joey Ma ,
> >> > users@ovirt.org 
> >> > Subject: Re: [ovirt-users] oVirt and ARM
> >> >
> >> > ***CAUTION: This email originated from outside of the organization. Do
> >> > not click links or open

[ovirt-users] Re: oVirt and ARM

2021-07-14 Thread Arik Hadas
On Wed, Jul 14, 2021 at 10:36 AM Milan Zamazal  wrote:

> Marko Vrgotic  writes:
>
> > Dear Arik and Milan,
> >
> > In the meantime, I was asked to check if in current 4.4 version or
> > coming 4.5, are/will there any capabilities or options of emulating
> > aarch64 on x86_64 platform and if so, what would be the steps to
> > test/enable it.
> >
> > Can you provide some information?
>
> Hi Marko,
>
> I don't think there is a way to emulate a non-native architecture.
> Engine doesn't have ARM support and it cannot handle ARM (native or
> emulated) hosts.  You could try to run emulated ARM VMs presented as x86
> to Engine using Vdsm hooks but I doubt it would work.
>

Oh I just sent a draft I had in my mailbox without noticing this comment
and I see we both mentioned Vdsm hook
What is the source of the doubts about Vdsm hooks to work for this?


>
> I'm afraid the only way is to add ARM support to oVirt.  My former
> colleague has played with running oVirt on Raspberry Pi hosts some years
> ago (there are traces of that effort in Vdsm) and I think adding ARM
> support should be, at least in theory, possible.  Particular features
> available would be mostly dependent on ARM support in QEMU and libvirt.


> Regards,
> Milan
>
> > -
> > kind regards/met vriendelijke groeten
> >
> > Marko Vrgotic
> > Sr. System Engineer @ System Administration
> >
> > ActiveVideo
> > o: +31 (35) 6774131
> > m: +31 (65) 5734174
> > e: m.vrgo...@activevideo.com<mailto:m.vrgo...@activevideo.com>
> > w: www.activevideo.com<http://www.activevideo.com>
> >
> > ActiveVideo Networks BV. Mediacentrum 3745 Joop van den Endeplein
> > 1.1217 WJ Hilversum, The Netherlands. The information contained in
> > this message may be legally privileged and confidential. It is
> > intended to be read only by the individual or entity to whom it is
> > addressed or by their designee. If the reader of this message is not
> > the intended recipient, you are on notice that any distribution of
> > this message, in any form, is strictly prohibited.  If you have
> > received this message in error, please immediately notify the sender
> > and/or ActiveVideo Networks, LLC by telephone at +1 408.931.9200 and
> > delete or destroy any copy of this message.
> >
> >
> >
> > From: Sandro Bonazzola 
> > Date: Friday, 9 July 2021 at 15:37
> > To: Marko Vrgotic , Arik Hadas
> > , Milan Zamazal 
> > Cc: Evgheni Dereveanchin , Zhenyu Zheng
> > , Joey Ma ,
> > users@ovirt.org 
> > Subject: Re: [ovirt-users] oVirt and ARM
> >
> > ***CAUTION: This email originated from outside of the organization. Do
> > not click links or open attachments unless you recognize the
> > sender!!!***
> >
> >
> > Il giorno ven 9 lug 2021 alle ore 11:00 Marko Vrgotic
> > mailto:m.vrgo...@activevideo.com>> ha
> > scritto:
> > Hi Sandro and the rest of oVirt gurus,
> >
> > My managers are positive regarding helping provide some ARM hardware,
> > but it would not happened earlier than three months from now, as we
> > are in process of establishing certain relationship with ARM HW
> > vendor.
> >
> > T news!
> >
> >
> > In the meantime, I was asked to check if in current 4.4 version or
> > coming 4.5, are/will there any capabilities or options of emulating
> > aarch64 on x86_64 platform and if so, what would be the steps to
> > test/enable it.
> >
> > +Arik Hadas<mailto:aha...@redhat.com> , +Milan Zamazal mzama...@redhat.com> ?
> >
> >
> > Kindly awaiting your reply.
> >
> > Marko Vrgotic
> >
> > From: Marko Vrgotic  m.vrgo...@activevideo.com>>
> > Date: Monday, 28 June 2021 at 15:38
> > To: Sandro Bonazzola
> > mailto:sbona...@redhat.com>>, Evgheni
> > Dereveanchin mailto:edere...@redhat.com>>
> > Cc: Zhenyu Zheng
> > mailto:zhengzhenyul...@gmail.com>>, Joey Ma
> > mailto:majunj...@gmail.com>>,
> > users@ovirt.org<mailto:users@ovirt.org>
> > mailto:users@ovirt.org>>
> > Subject: Re: [ovirt-users] oVirt and ARM
> > Hi Sandro,
> >
> > I will check with my managers if we have and could spare some hardware
> > to contribute developing for oVirt.
> >
> >
> > -
> > kind regards/met vriendelijke groeten
> >
> > Marko Vrgotic
> > Sr. System Engineer @ System Administration
> >
> > ActiveVideo
> > o: +31 (35) 6774131
> > m: +31 (65) 5734174
> > e: m.vrgo...@activevideo.com<ma

[ovirt-users] Re: oVirt and ARM

2021-07-14 Thread Arik Hadas
On Tue, Jul 13, 2021 at 10:45 PM Marko Vrgotic 
wrote:

> Dear Arik and Milan,
>
>
>
> In the meantime, I was asked to check if in current 4.4 version or coming
> 4.5, are/will there any capabilities or options of emulating aarch64 on
> x86_64 platform and if so, what would be the steps to test/enable it.
>
>
>
> Can you provide some information?
>

oVirt doesn't support fully emulated workloads out of the box.
The architecture of the guest is determined by that of the cluster [1] and
the latter is either set automatically based on the hosts in the cluster or
set explicitly by the user in which case we enforce the hosts to comply
with that setting.

It could be nice to see it picked up by someone in the community if fully
emulated workloads are desired.
We don't have anything about this in our backlog at this point.

In the meantime, the easiest way to have fully emulated AArch64 workloads
would probably be by using a VDSM hook that modifies the VM configuration
before it starts (e.g., changing the 'emulator' to
/usr/bin/qemu-system-aarch64, changing the 'os' tag, etc). See [2] for how
it was suggested to emulate ARM.

[1]
https://github.com/oVirt/ovirt-engine/blob/ovirt-engine-4.4.8/backend/manager/modules/vdsbroker/src/main/java/org/ovirt/engine/core/vdsbroker/builder/vminfo/LibvirtVmXmlBuilder.java#L661
[2]
https://fedoraproject.org/wiki/Architectures/ARM/HowToQemu#Installing_the_ARM_root_filesystem_and_XML


>
>
> -
>
> kind regards/met vriendelijke groeten
>
>
>
> Marko Vrgotic
> Sr. System Engineer @ System Administration
>
>
> ActiveVideo
>
> *o: *+31 (35) 6774131
>
> *m: +*31 (65) 5734174
>
> *e:* m.vrgo...@activevideo.com
> *w: *www.activevideo.com
>
>
>
> ActiveVideo Networks BV. Mediacentrum 3745 Joop van den Endeplein 1.1217
> WJ Hilversum, The Netherlands. The information contained in this message
> may be legally privileged and confidential. It is intended to be read only
> by the individual or entity to whom it is addressed or by their designee.
> If the reader of this message is not the intended recipient, you are on
> notice that any distribution of this message, in any form, is strictly
> prohibited.  If you have received this message in error, please immediately
> notify the sender and/or ActiveVideo Networks, LLC by telephone at +1
> 408.931.9200 and delete or destroy any copy of this message.
>
>
>
>
>
>
>
> *From: *Sandro Bonazzola 
> *Date: *Friday, 9 July 2021 at 15:37
> *To: *Marko Vrgotic , Arik Hadas <
> aha...@redhat.com>, Milan Zamazal 
> *Cc: *Evgheni Dereveanchin , Zhenyu Zheng <
> zhengzhenyul...@gmail.com>, Joey Ma , users@ovirt.org
> 
> *Subject: *Re: [ovirt-users] oVirt and ARM
>
> ***CAUTION: This email originated from outside of the organization. Do not
> click links or open attachments unless you recognize the sender!!!***
>
>
>
>
>
> Il giorno ven 9 lug 2021 alle ore 11:00 Marko Vrgotic <
> m.vrgo...@activevideo.com> ha scritto:
>
> Hi Sandro and the rest of oVirt gurus,
>
>
>
> My managers are positive regarding helping provide some ARM hardware, but
> it would not happened earlier than three months from now, as we are in
> process of establishing certain relationship with ARM HW vendor.
>
>
>
> T news!
>
>
>
>
>
> In the meantime, I was asked to check if in current 4.4 version or coming
> 4.5, are/will there any capabilities or options of emulating aarch64 on
> x86_64 platform and if so, what would be the steps to test/enable it.
>
>
>
> +Arik Hadas  , +Milan Zamazal  ?
>
>
>
>
>
> Kindly awaiting your reply.
>
>
>
> Marko Vrgotic
>
>
>
> *From: *Marko Vrgotic 
> *Date: *Monday, 28 June 2021 at 15:38
> *To: *Sandro Bonazzola , Evgheni Dereveanchin <
> edere...@redhat.com>
> *Cc: *Zhenyu Zheng , Joey Ma <
> majunj...@gmail.com>, users@ovirt.org 
> *Subject: *Re: [ovirt-users] oVirt and ARM
>
> Hi Sandro,
>
>
>
> I will check with my managers if we have and could spare some hardware to
> contribute developing for oVirt.
>
>
>
>
>
> -
>
> kind regards/met vriendelijke groeten
>
>
>
> Marko Vrgotic
> Sr. System Engineer @ System Administration
>
>
> ActiveVideo
>
> *o: *+31 (35) 6774131
>
> *m: +*31 (65) 5734174
>
> *e:* m.vrgo...@activevideo.com
> *w: *www.activevideo.com
>
>
>
> ActiveVideo Networks BV. Mediacentrum 3745 Joop van den Endeplein 1.1217
> WJ Hilversum, The Netherlands. The information contained in this message
> may be legally privileged and confidential. It is intended to be read only
> by the individual or entity to whom it is addressed or by their designee.
> I

[ovirt-users] Re: How to remove "VM is being cloned" flag in a failed clone VM operation

2021-07-13 Thread Arik Hadas
On Tue, Jul 13, 2021 at 3:56 PM Richard Chan 
wrote:

> Hello list,
>
> I had an unsuccessful zombie clone VM task  -
> 1. Target: was able to unlock the disks and delete the target VM
> 2. Source: able to unlock the disks.
>
> Now I cannot do anything with the source as it is flagged as "VM is being
> clone".
>
> Is there a way to remove this flag manually?
>

> vdms-client Host -> this does not show any tasks outstanding.
>

That's an in-memory lock - if the tasks were removed also on the engine
side, just restart ovirt-engine and the vm would be unlocked


>
> Thank you.
>
> Richard Chan
>
> ___
> 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/PJZMIIGTEKDM2EPKMQTXU7AEDWAUFFT2/
>
___
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/DVHFOZ5IDHMLF7SWMQRIVJHWOAKQ5VTZ/


[ovirt-users] Re: export VM from oVirt engine 3.5

2021-07-11 Thread Arik Hadas
On Fri, Jul 9, 2021 at 1:03 AM Alex K  wrote:

>
>
> On Thu, Jul 8, 2021, 20:19  wrote:
>
>> Hello,
>> I am trying to export a bunch o VM from  oVirt version 3.5
>> The problem is that there is no OVA support for exporting them. I also
>> tryed to export VMs into OVA format using ovirtsdk4 which anyway won't work
>> on oVirt 3.5.
>> I can successfully export to a NFS partition but for each VM there are
>> several qcow v2 files which I suppose to be the VM image and its snapshots.
>> How to identify the correct file to represent the current VM status ?
>>
> When exporting you should get only one image file with the current status
> of the vm.
>
> If you want to hack with the vm images, you can commit all the chain of
> the snapshot files to your own single qcow2 copy using qemu-img commands.
>
>> You can easily get the disk ID of the current active snapshot (vm ->
> snapshots) then you can view the full chain with:
> qemu-img info --backing-chain $FILENAME
> You need to know what you are doing though to avoid any data loss.
>
> If I delete all the snapshots, will I end up with only one valid qcow v2
>> image that I can use ?
>>
> Yes, you should. You can try if the snapshots are not needed.
>

You can alternatively ask to discard (collapse) snapshots during export in
order to get a single volume on the export domain [0]
There's an example for how to do that in the latest documentation of the
API [1]
This option seems to exist also in the API of oVirt 3.5 [2]

[0] It will not necessarily be a qcow2 volume - that depends on the format
of the base volume of the VM you export
[1]
https://github.com/oVirt/ovirt-engine-api-model/blob/4.4.31/src/main/java/services/VmService.java#L174-L189
[2]
https://github.com/oVirt/ovirt-engine/blob/ovirt-engine-3.5/backend/manager/modules/restapi/jaxrs/src/main/java/org/ovirt/engine/api/restapi/resource/BackendVmResource.java#L432-L434


> ___
>> 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/FCCK7HSIVMXAH2D7F2DWLHR4J2XSSTPP/
>>
> ___
> 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/4J3HIIWUCVHJBMCL5TP7VR46J42MO2ED/
>
___
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/AH5ASGPMDESX2XI37R5W27EKUW6YNULO/


[ovirt-users] Re: what happens to vms when a host shutdowns?

2021-07-06 Thread Arik Hadas
On Tue, Jul 6, 2021 at 7:02 PM Sandro Bonazzola  wrote:

>
>
> Il giorno mar 6 lug 2021 alle ore 17:33 Nir Soffer 
> ha scritto:
>
>> On Tue, Jul 6, 2021 at 5:58 PM Scott Worthington
>>  wrote:
>> >
>> >
>> >
>> > On Tue, Jul 6, 2021 at 8:13 AM Nir Soffer  wrote:
>> >>
>> >> On Tue, Jul 6, 2021 at 2:29 PM Sandro Bonazzola 
>> wrote:
>> >>>
>> >>>
>> >>>
>> >>> Il giorno mar 6 lug 2021 alle ore 13:03 Nir Soffer <
>> nsof...@redhat.com> ha scritto:
>> 
>>  On Tue, Jul 6, 2021 at 1:11 PM Nathanaël Blanchet 
>> wrote:
>>  > We are installing UPS powerchute client on hypervisors.
>>  >
>>  > What is the default vms behaviour of running vms when an
>> hypervisor is
>>  > ordered to shutdown: do the vms live migrate or do they shutdown
>>  > properly (even the restart on an other host because of HA) ?
>> 
>>  In general VMs are not restarted after an unexpected shutdown, but
>> HA VMs
>>  are restarted after failures.
>> 
>>  If the HA VM has a lease, it can restart safely on another host
>> regardless of
>>  the original host status. If the HA VM does not have a lease, the
>> system must
>>  wait until the original host is up again to check if the VM is still
>>  running on this
>>  host.
>> 
>>  Arik can add more details on this.
>> >>>
>> >>>
>> >>> I think the question is not related to what happens after the host is
>> back.
>> >>> I think the question is what happens when the host goes down.
>> >>> To me, the right way to shutdown a host is putting it first to
>> maintenance (VM evacuate to other hosts) and then shutdown.
>> >>
>> >>
>> >> Right, but the we don't have integration with the UPS, so engine
>> cannot put the host
>> >> to maintenance when the host lose power and the UPS will shut it down
>> after
>> >> few minutes.
>> >
>> >
>> > This is outside of the scope of oVirt team:
>> >
>> > Perhaps one could combine multiple applications ( NUT + Ansible +
>> Nagios/Zabbix ) to notify the oVirt engine to switch a host to maintenance?
>> >
>> > NUT[0] could be configured to alert a monitoring system ( like Nagios
>> or Zabbix) to trigger an Ansible playbook [1][2] to put the host in
>> maintenance mode, and the trigger should happen before the UPS battery is
>> depleted (you'll have to account for the time it takes to live migrate VMs).
>>
>> I would trigger this once power is lost. You never know how much time
>> migration will take, so best migrate all vms immediately.
>>
>> It would be nice to integrate this with engine, but we can start by
>> something
>> like you describe, that will use engine API/SDK to prepare the hosts for
>> graceful shutdown.
>>
>
There are pros and cons to this approach.
If the workloads manage to get evacuated quickly, before libvirt-guests
starts shutting them down, that's great.
But what happens if the VMs are still migrated after libvirt-guests
initiated shutdowns?
Think about the following case:
1. A highly available VM starts migrating
2. libvirt-guests tries to shut down the guest
3. The migration completed
4. The guest shuts down while it runs on the destination host
I'm not sure that we'll treat that case as a non-intentional shutdown since
we may lose the context of the shutdown while the VM runs to the
destination host and therefore won't try to restart the VM automatically.


>
> we already have a role for immediate shutdown of the whole datacenter:
> https://github.com/oVirt/ovirt-ansible-shutdown-env
> now integrated in ansible collection
> https://github.com/oVirt/ovirt-ansible-collection/tree/master/roles/shutdown_env
>
>
>
>>
>> > [0] Network UPS Tools
>> https://networkupstools.org/docs/user-manual.chunked/index.html
>> > [1]
>> https://www.ovirt.org/develop/release-management/features/infra/ansible_modules.html
>> > [2]
>> https://docs.ansible.com/ansible/latest/collections/ovirt/ovirt/ovirt_host_module.html
>>
>>
>
> --
>
> Sandro Bonazzola
>
> MANAGER, SOFTWARE ENGINEERING, EMEA R RHV
>
> Red Hat EMEA 
>
> sbona...@redhat.com
> 
>
> *Red Hat respects your work life balance. Therefore there is no need to
> answer this email out of your office hours.
> *
>
>
> ___
> 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/TYCMHTXMBD2KLGPYXVSB7CAUMBFWGLEP/
>
___
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: 

[ovirt-users] Re: what happens to vms when a host shutdowns?

2021-07-06 Thread Arik Hadas
On Tue, Jul 6, 2021 at 3:13 PM Nir Soffer  wrote:

> On Tue, Jul 6, 2021 at 2:29 PM Sandro Bonazzola 
> wrote:
>
>>
>>
>> Il giorno mar 6 lug 2021 alle ore 13:03 Nir Soffer 
>> ha scritto:
>>
>>> On Tue, Jul 6, 2021 at 1:11 PM Nathanaël Blanchet 
>>> wrote:
>>> > We are installing UPS powerchute client on hypervisors.
>>> >
>>> > What is the default vms behaviour of running vms when an hypervisor is
>>> > ordered to shutdown: do the vms live migrate or do they shutdown
>>> > properly (even the restart on an other host because of HA) ?
>>>
>>> In general VMs are not restarted after an unexpected shutdown, but HA VMs
>>> are restarted after failures.
>>>
>>> If the HA VM has a lease, it can restart safely on another host
>>> regardless of
>>> the original host status. If the HA VM does not have a lease, the system
>>> must
>>> wait until the original host is up again to check if the VM is still
>>> running on this
>>> host.
>>>
>>> Arik can add more details on this.
>>>
>>
>> I think the question is not related to what happens after the host is
>> back.
>> I think the question is what happens when the host goes down.
>> To me, the right way to shutdown a host is putting it first to
>> maintenance (VM evacuate to other hosts) and then shutdown.
>>
>
> Right, but the we don't have integration with the UPS, so engine cannot
> put the host
> to maintenance when the host lose power and the UPS will shut it down after
> few minutes.
>
>
>> On emergency shutdown without moving the host to maintenance first I
>> think libvirt is communicating the host is going down to the guests and
>> tries to cleanly shutdown vms while the host is going down.
>> Arik please confirm :-)
>>
>
Yes, that is correct.
If the host shuts down, libvirt-guests attempt to shut down the guests
gracefully.


>
>>
>>
>>>
>>> Nir
>>> ___
>>> 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/HXVXSLXQYZX6CQPJNXKWLOMY3LQU7XJ5/
>>>
>>
>>
>> --
>>
>> Sandro Bonazzola
>>
>> MANAGER, SOFTWARE ENGINEERING, EMEA R RHV
>>
>> Red Hat EMEA 
>>
>> sbona...@redhat.com
>> 
>>
>> *Red Hat respects your work life balance. Therefore there is no need to
>> answer this email out of your office hours.
>> *
>>
>>
>> ___
> 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/7Q7XXOL3JXL2L4MP6G2Q7OJLKLBEZFVP/
>
___
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/SESPV2OKLEOSRMDO6LTK6JZCKI63NINN/


[ovirt-users] Re: Failing to migrate hosted engine from 4.4.6 host to 4.4.7 host

2021-07-06 Thread Arik Hadas
On Tue, Jul 6, 2021 at 3:56 PM Nir Soffer  wrote:

> On Tue, Jul 6, 2021 at 3:36 PM Sandro Bonazzola 
> wrote:
>
>> Hi,
>> I update the hosted engine to 4.4.7 and one of the 2 nodes where the
>> engine is running.
>> Current status is:
>> - Hosted engine at 4.4.7 running on Node 0
>> - Node 0 at 4.4.6
>> - Node 1 at 4.4.7
>>
>> Now, moving Node 0 to maintenance successfully moved the SPM from Node 0
>> to Node 1 but while trying to migrate hosted engine I get on Node 0
>> vdsm.log:
>>
> ...
>
>>   File "/usr/lib64/python3.6/site-packages/libvirt.py", line 2119, in 
>> migrateToURI3
>> raise libvirtError('virDomainMigrateToURI3() failed')
>> libvirt.libvirtError: can't connect to virtlogd: Unable to open system token 
>> /run/libvirt/common/system.token: Permission denied
>>
>>
> This looks like the selinux issue we had in libvirt 7.4. Do we have the
> latest
> selinux-policy-target package on the host?
>

Yeah, seems like https://bugzilla.redhat.com/show_bug.cgi?id=1964317
___
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/IUMARKVV7KU3DNHS6YTN7EKO3NXVPIAZ/


[ovirt-users] Re: VM-Pool is already attached to a User

2021-07-05 Thread Arik Hadas
On Mon, Jul 5, 2021 at 10:42 AM Nicolás  wrote:

> Hi,
>
> It's possible that you bumped into:
>
> Original bug: https://bugzilla.redhat.com/show_bug.cgi?id=1462236
> Downstream clone: https://bugzilla.redhat.com/show_bug.cgi?id=1635337.
>
> It has been solved in 4.3.5.
>

> Regards,
>
> Nicolás
>
> El 2/7/21 a las 13:55, Dominique D escribió:
> > I created a VM pool (20 Windows) and the first 6 users took a virtual
> machine in the VM portal.
> >
> > the following other users have this message
> >
> > "Cannot attach VM to VM-Pool. VM-Pool is already attached to a User"
> >
> > I have 15 users and 20 VMs available, do you know why I have this
> message ?
> >
> > I have no user registered in the permissions tab of the vm available.
> >
> > ovirt 4.4.1
>

If it happens with oVirt 4.4.1 then it can be related to [1] that was fixed
in 4.4.2

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


> >
> > Thank you.
> > ___
> > 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/BBUPBG4X4TZ5NJC5ZAZO4OJ56MYGS436/
> ___
> 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/ZQS46LT4CTV5XCXC3L7OGFBJY3OLY2H2/
>
___
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/MSUYJZYI4I35HA5E3ZI6TIMMLA6HGNVZ/


[ovirt-users] Re: Question about Template and Storage Domain

2021-07-04 Thread Arik Hadas
On Mon, Jun 28, 2021 at 11:23 AM Eyal Shenitzky  wrote:

> Hi,
>
> You are probably creating the VM as a dependent on the template (thin VM),
> it means that the VM's disk should be created on the same storage domain as
> the template disk.
>
> In order to create the VM with a disk on a different storage domain, you
> can either create the VM as an independent (clone) or copy the template
> disk to the storage domain you want to create the VM disk on.
>

> On Sun, 27 Jun 2021 at 18:40, Nur Imam Febrianto 
> wrote:
>
>> Hi,
>>
>>
>> Want to ask about template. For example I have a several template (with
>> disk) stored in some Storage Domain. If I create a VM from the template,
>> and when I change the parameter of cloned disk into another storage domain
>> (different with where the template are stored). The VM always failed to be
>> created. This only occurs in VM creation phase, if I create the VM at same
>> storage domain where the templates are stored, it created successfully. Is
>> this are “normal” behavior ?
>>
>
No, you should be able to create cloned disks on a storage domain that is
different from the one(s) the template image(s) is on.

How did you try to do that?
If you tried to create thin-provisioned disks as Eyal mentioned above via
the API, the operation should fail with an error of
TEMPLATE_IMAGE_NOT_EXIST (it shouldn't be possible to select a storage
domain that doesn't hold the template image via the webadmin)

If you specified that the disks should be cloned to a different storage
domain correctly then the engine.log should reveal what is the problem.


>>
>> Thanks before.
>>
>>
>>
>> Regards,
>>
>> Nur Imam Febrianto
>> ___
>> 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/F6BCRDFJBCOGA6GLJWWLIBXMFFKCD75C/
>>
>
>
> --
> Regards,
> Eyal Shenitzky
> ___
> 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/3RPONNQIRSIO6CQPX3WWJXXSAFTRISFP/
>
___
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/XBC2JBI2ULYTAY5C7CNV52X5NQCZWBDP/


[ovirt-users] Re: Problems moving vm & templates between oVirt 4.3 & 4.4

2021-06-23 Thread Arik Hadas
On Wed, Jun 23, 2021 at 8:27 AM Guillaume Pavese <
guillaume.pav...@interactiv-group.com> wrote:

> I opened : https://bugzilla.redhat.com/show_bug.cgi?id=1975076
>

Thanks for filing it.
If you wish to transfer VMs from oVirt 4.4 to oVirt 4.3, you have to make
sure that the cluster you use in oVirt 4.4 is set with compatibility level
which is supported in oVirt 4.3 (that is, compatibility level 4.2 or 4.3),
as forward-compatibility is not supported.


>
>
>
> Guillaume Pavese
> Ingénieur Système et Réseau
> Interactiv-Group
>
>
> On Tue, Jun 22, 2021 at 12:26 PM Strahil Nikolov 
> wrote:
>
>> Error during ValidateFailure.: java.lang.IllegalArgumentExcepti
>> on: VM64BitMaxMemorySizeInMB has no value for version: 4.6
>>
>>
>> This one is quite interesting... Most probably is a bug.
>>
>> Best Regards,
>> Strahil Nikolov
>>
>> On Tue, Jun 22, 2021 at 0:59, Guillaume Pavese
>>  wrote:
>> ___
>> 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/XXFQFMUD76O53PSA3XZHSXTMHHPBOEE3/
>>
>>
> Ce message et toutes les pièces jointes (ci-après le “message”) sont
> établis à l’intention exclusive de ses destinataires et sont confidentiels.
> Si vous recevez ce message par erreur, merci de le détruire et d’en avertir
> immédiatement l’expéditeur. Toute utilisation de ce message non conforme a
> sa destination, toute diffusion ou toute publication, totale ou partielle,
> est interdite, sauf autorisation expresse. L’internet ne permettant pas
> d’assurer l’intégrité de ce message . Interactiv-group (et ses filiales)
> décline(nt) toute responsabilité au titre de ce message, dans l’hypothèse
> ou il aurait été modifié. IT, ES, UK.
> 
> ___
> 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/2UNL6ASMOTFMT5NIIIR2GGC25KMPIT3J/
>
___
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/DRL7EK3XS2ZZGMS3UDTLHLBWASIFRBK3/


[ovirt-users] Re: importing vm's from storage pool from 4.1.6.2-1 in to 4.4.6 fails due to lingering snapshot configuration in source

2021-06-22 Thread Arik Hadas
On Mon, Jun 21, 2021 at 11:45 PM Charles Kozler 
wrote:

> I know the subject is a bit wordy but let me try to explain
>
> I have a 4.1 installation that I am migrating to 4.4. I placed the storage
> domain into maintenance and then rsync'ed it to the storage I am using for
> 4.4. In 4.4 I import the domain and it comes in fine, however, when trying
> to import some VM's it fails because it says it cannot find a disk. The
> disk ID's I cannot find anywhere in 4.1 or 4.4 so I opened OVF_STORE after
> upgrading the pool in 4.4 and look at the ovf file for some of the VM's
> that are failing to import
>
> I see this in the ovf configuration file -
>
> 
>   
> ACTIVE
> Active VM
> 2019/12/19 16:47:48
>
> 07d3447c-c640-4163-9cf1-74ce126d702a,59b5cfdf-015b-0333-004b-0397,8c48ea33-dc34-403a-90d2-a3e78776404c,1757809b-9685-4315-a92e-3ea82dc6d8a8,94a2c2b3-e02e-4b05-80eb-6f4b7a9701e7,248a9fd1-61f0-4c5a-b6ab-4630d433c6fa
>   
> 
>   
> 
>
> These are the disk ID's I can see failing to import in engine.log
>
> I am aware that importing a VM cannot support snapshots and have found
> multiple mailing list posts around this, however, I do not have any
> snapshots visible in 4.1 UI.
>
> I also tried modifying OVF_STORE by untar'ing it and editing the ovf files
> directly, however, this does not work as it ends up overwritten by ovirt
> with the previous configuration
>
> Any ideas? As noted, I cannot see any snapshots listed in 4.1 source pool
> so I therefore cannot remove this stale configuration from the source and
> upon importing in to 4.4 it fails because it cannot find the disks
>

I think the only possible explanation to having a VM with no snapshots
besides the ACTIVE one and memory attached to the ACTIVE snapshot is that
the VM is suspended. In that case, and if the error you get is related to
the memory (dump/metadta) disks, shutting down the VM in the source (4.1)
env first can solve this


>
> I tried import partial and that still fails which to me seems like a bug
> because the idea of the import partial is to still register the VM even if
> it cant find disks
>
> I also tried scanning domain for disks and update OVF's in the UI and it
> does not help anything
>
>
> *Notice to Recipient*: https://www.fixflyer.com/disclaimer
> ___
> 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/O4EAECZSGR33FABPEV4FB6E3ZTKMZQKM/
>
___
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/BJVH226VRE3IVLFGXA6PDHDO5YLJBJY2/


[ovirt-users] Re: Ovirt 4.4.6.8-1 upload ova as template to multiple hosts

2021-05-27 Thread Arik Hadas
On Thu, May 27, 2021 at 6:19 PM Don Dupuis  wrote:

> It is the same script, I just renamed it. Now what I did works but it
> isn't the proper way to do it. I want to improve it before contributing it
> as I write the ovf data back out to a file and use pythons sed like
> functionality to modify the file and then read in the updated one to give
> to the engine. I just wanted to get something to work to get my project
> done.
>

Ack, yeah, it makes sense to change that.
I don't know if you've added an argument to the script that determines
whether or not the entity is imported as a clone, but it can also be handy
to import as a clone automatically when a VM/template with the same ID
already exists. That's something we used to do when importing from export
domains and we miss it for uploading from OVA.


>
> Don
>
> On Thu, May 27, 2021 at 9:35 AM Arik Hadas  wrote:
>
>>
>>
>> On Thu, May 27, 2021 at 4:24 PM Don Dupuis  wrote:
>>
>>> Arik
>>> Just to say thank you again for the pointers on what was needed to be
>>> done. I was able to modify that script to do what was needed and now it
>>> works like a champ.
>>>
>>
>> Awesome, glad to hear that.
>> Looking again at what you wrote below, you've mentioned the script is
>> named upload_ova_as_template.py. We've made some changes to that script and
>> renamed it to upload_ova_as_vm_or_template.py [1]. It would be great if you
>> could contribute your changes to it
>>
>> [1]
>> https://gerrit.ovirt.org/gitweb?p=ovirt-engine-sdk.git;a=blob;f=sdk/examples/upload_ova_as_vm_or_template.py;h=d6f40548b912577dc18a24d564f37d117a084d28;hb=HEAD
>>
>>
>>>
>>> Thanks
>>> Don
>>>
>>> On Mon, May 24, 2021 at 3:56 PM Don Dupuis  wrote:
>>>
>>>> Arik
>>>> Thanks for the info. My simple setup is just a base for bigger clusters
>>>> that I have to do and there will be multiple templates that I need to
>>>> install. I have python programming skills but just needed some simple
>>>> pointing in the right direction on where to make the addition changes to
>>>> the code. It takes a little bit of time to get the services and types
>>>> correct for what you want to accomplish and how it is implemented.
>>>>
>>>> Don
>>>>
>>>> On Mon, May 24, 2021 at 2:51 PM Arik Hadas  wrote:
>>>>
>>>>>
>>>>>
>>>>> On Mon, May 24, 2021 at 6:49 PM Don Dupuis  wrote:
>>>>>
>>>>>> Nudging to see if anyone has experience with this?
>>>>>>
>>>>>> Don
>>>>>>
>>>>>> On Wed, May 19, 2021 at 11:18 PM Don Dupuis 
>>>>>> wrote:
>>>>>>
>>>>>>> I have a single ovirt manager and 2 ovirt hosts, each has a local
>>>>>>> storage domain. I am using the upload_ova_as_template.py and my template
>>>>>>> upload works on a single host but not both. If I use the gui method, 
>>>>>>> there
>>>>>>> is the option of "clone" and putting in a new name for the template. 
>>>>>>> This
>>>>>>> seems to work most of the time, but it has failed a couple of times 
>>>>>>> also. I
>>>>>>> would like to add the same "clone" and "name" option to the
>>>>>>> upload_ova_as_temple.py. What is the best way to do this since I need to
>>>>>>> have unique UUIDs for the template disks? This is a unique setup in the
>>>>>>> fact that I can't use shared storage and this should be doable as I was
>>>>>>> able to do it in the ovirt gui.
>>>>>>>
>>>>>>
>>>>> If it's just a one-time operation, I'd rather try to create a VM out
>>>>> of the template that was imported successfully (with disk-provisioning =
>>>>> clone), create a second template out of it, remove the original template
>>>>> and then upload the template from the OVA to the other storage domain.
>>>>>
>>>>> Changing the script to obtain import as clone is also possible but it
>>>>> requires some programming skills - you'd need to either generate or 
>>>>> provide
>>>>> the script with different name for the template and UUIDs for the disks 
>>>>> and
>>>>> then (1) use the new UUIDs when uploading the disks and (2) change the OVF
>>>>> that is loaded from the OVA to have the new name and UUIDs before 
>>>>> providing
>>>>> the OVF to the engine.
>>>>>
>>>>>
>>>>>>
>>>>>>> Thanks
>>>>>>> Don
>>>>>>>
>>>>>> ___
>>>>>> 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/U6Q5P7YKDBJARPPNFJOXAMP2AMKEJDNK/
>>>>>>
>>>>>
___
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/UK6ASJ4NHZY7IUEYOCQPVSSIUTVFIVE2/


[ovirt-users] Re: Ovirt 4.4.6.8-1 upload ova as template to multiple hosts

2021-05-27 Thread Arik Hadas
On Thu, May 27, 2021 at 4:24 PM Don Dupuis  wrote:

> Arik
> Just to say thank you again for the pointers on what was needed to be
> done. I was able to modify that script to do what was needed and now it
> works like a champ.
>

Awesome, glad to hear that.
Looking again at what you wrote below, you've mentioned the script is named
upload_ova_as_template.py. We've made some changes to that script and
renamed it to upload_ova_as_vm_or_template.py [1]. It would be great if you
could contribute your changes to it

[1]
https://gerrit.ovirt.org/gitweb?p=ovirt-engine-sdk.git;a=blob;f=sdk/examples/upload_ova_as_vm_or_template.py;h=d6f40548b912577dc18a24d564f37d117a084d28;hb=HEAD


>
> Thanks
> Don
>
> On Mon, May 24, 2021 at 3:56 PM Don Dupuis  wrote:
>
>> Arik
>> Thanks for the info. My simple setup is just a base for bigger clusters
>> that I have to do and there will be multiple templates that I need to
>> install. I have python programming skills but just needed some simple
>> pointing in the right direction on where to make the addition changes to
>> the code. It takes a little bit of time to get the services and types
>> correct for what you want to accomplish and how it is implemented.
>>
>> Don
>>
>> On Mon, May 24, 2021 at 2:51 PM Arik Hadas  wrote:
>>
>>>
>>>
>>> On Mon, May 24, 2021 at 6:49 PM Don Dupuis  wrote:
>>>
>>>> Nudging to see if anyone has experience with this?
>>>>
>>>> Don
>>>>
>>>> On Wed, May 19, 2021 at 11:18 PM Don Dupuis  wrote:
>>>>
>>>>> I have a single ovirt manager and 2 ovirt hosts, each has a local
>>>>> storage domain. I am using the upload_ova_as_template.py and my template
>>>>> upload works on a single host but not both. If I use the gui method, there
>>>>> is the option of "clone" and putting in a new name for the template. This
>>>>> seems to work most of the time, but it has failed a couple of times also. 
>>>>> I
>>>>> would like to add the same "clone" and "name" option to the
>>>>> upload_ova_as_temple.py. What is the best way to do this since I need to
>>>>> have unique UUIDs for the template disks? This is a unique setup in the
>>>>> fact that I can't use shared storage and this should be doable as I was
>>>>> able to do it in the ovirt gui.
>>>>>
>>>>
>>> If it's just a one-time operation, I'd rather try to create a VM out of
>>> the template that was imported successfully (with disk-provisioning =
>>> clone), create a second template out of it, remove the original template
>>> and then upload the template from the OVA to the other storage domain.
>>>
>>> Changing the script to obtain import as clone is also possible but it
>>> requires some programming skills - you'd need to either generate or provide
>>> the script with different name for the template and UUIDs for the disks and
>>> then (1) use the new UUIDs when uploading the disks and (2) change the OVF
>>> that is loaded from the OVA to have the new name and UUIDs before providing
>>> the OVF to the engine.
>>>
>>>
>>>>
>>>>> Thanks
>>>>> Don
>>>>>
>>>> ___
>>>> 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/U6Q5P7YKDBJARPPNFJOXAMP2AMKEJDNK/
>>>>
>>>
___
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/M2ORTP6NNIU5ZB25WP3Q6KF2ITHTLGXM/


[ovirt-users] Re: Ovirt 4.4.6.8-1 upload ova as template to multiple hosts

2021-05-24 Thread Arik Hadas
On Mon, May 24, 2021 at 6:49 PM Don Dupuis  wrote:

> Nudging to see if anyone has experience with this?
>
> Don
>
> On Wed, May 19, 2021 at 11:18 PM Don Dupuis  wrote:
>
>> I have a single ovirt manager and 2 ovirt hosts, each has a local storage
>> domain. I am using the upload_ova_as_template.py and my template upload
>> works on a single host but not both. If I use the gui method, there is the
>> option of "clone" and putting in a new name for the template. This seems to
>> work most of the time, but it has failed a couple of times also. I would
>> like to add the same "clone" and "name" option to the
>> upload_ova_as_temple.py. What is the best way to do this since I need to
>> have unique UUIDs for the template disks? This is a unique setup in the
>> fact that I can't use shared storage and this should be doable as I was
>> able to do it in the ovirt gui.
>>
>
If it's just a one-time operation, I'd rather try to create a VM out of the
template that was imported successfully (with disk-provisioning = clone),
create a second template out of it, remove the original template and then
upload the template from the OVA to the other storage domain.

Changing the script to obtain import as clone is also possible but it
requires some programming skills - you'd need to either generate or provide
the script with different name for the template and UUIDs for the disks and
then (1) use the new UUIDs when uploading the disks and (2) change the OVF
that is loaded from the OVA to have the new name and UUIDs before providing
the OVF to the engine.


>
>> Thanks
>> Don
>>
> ___
> 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/U6Q5P7YKDBJARPPNFJOXAMP2AMKEJDNK/
>
___
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/WUY6XZ5SICUFQKWGJ4AZEMDIZZVLIFHV/


[ovirt-users] Re: How to reduce load during create VM

2021-04-25 Thread Arik Hadas
On Wed, Apr 21, 2021 at 10:07 AM  wrote:

> Hi everyone, please, can you limit the "Create VM" process somewhere so
> that setting up quota does not load the server so much, especially storage
> when duplicating the template disk?
>

I assume you refer to the process (qemu-img) that clones the disks, right?
Did you consider changing the storage allocation to "thin" instead of
"clone"?


> ___
> 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/2PO6CSPZN6N4E2VHNDOSS2VHMP2ZFH7J/
>
___
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/DT7NQM273AOBX77ZDVWEUW3E5R3IJXBT/


[ovirt-users] Re: pool list vm assign user

2021-04-25 Thread Arik Hadas
On Wed, Apr 21, 2021 at 8:17 PM Dominique D <
dominique.desche...@gcgenicom.com> wrote:

> I found this a "select command" on this link
> https://bugzilla.redhat.com/show_bug.cgi?id=1462236
>
> I use ovirt 4.4
>
> But where I execute this command :
>
> engine=# select s.vm_name, d.status, u.name from vm_static s, vm_dynamic
> d, permissions p, users u
> where
> s.vm_guid = d.vm_guid and
> u.user_id = p.ad_element_id and
> p.object_type_id = 2 and
> p.object_id = s.vm_guid and
> s.vm_name ilike '%VMPOOL%' ORDER BY vm_name;
>vm_name| status | name
> --++--
>  VMPOOL-1   |  1 | ADRIAN
>  VMPOOL-10  |  1 | ADRIAN
>

That SQL command can be executed via a PostgreSQL client.
Alternatively, you can look at the virtual machine's permissions (sub-)tab
in the webadmin.


> ___
> 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/DPCDBK4LNEKJTKG6HFT4GXBHUV3TYDE2/
>
___
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/AUM7HTWSTPZ5OMKN53YP5DX5XJZX3SK7/


[ovirt-users] Re: ova import

2021-04-08 Thread Arik Hadas
On Thu, Apr 8, 2021 at 12:04 PM Gianluca Cecchi 
wrote:

> On Thu, Apr 8, 2021 at 10:49 AM Arik Hadas  wrote:
>
>>
>> On Thu, Apr 8, 2021 at 3:50 AM  wrote:
>>
>>> I am running Ovirt 4.3 and exported machines as ova which includes
>>> disks. When I re import them. the disks are thin provisioned and the vm
>>> will not boot.
>>> Any idea how to get the import to  preallocate disks?  I have vms that
>>> will not boot.
>>>
>> It states no bootable disk is available.
>>> It seems the virt2vm isn't working correctly.
>>> ANy help would be appreciated.
>>>
>>
>> There's no option to change the format of the imported disks at the
>> moment so they'd keep being thin-provisioned as they are within the OVA.
>> I doubt that's the reason for the failure of those VMs to boot though -
>> can you please share the engine.log that shows the configuration that a VM
>> that didn't manage to boot started with?
>>
>>
>>> Eric
>>>
>>
> There were some threads in July 2020 about ova export zero size disks, and
> so unusable import.
> See these bugzillas for more information and also see suggestions about
> how to put a single line fix to your 4.3 install as there was no backport
> but solution only on 4.4
> https://bugzilla.redhat.com/show_bug.cgi?id=1862115
> https://bugzilla.redhat.com/show_bug.cgi?id=1813028
>

Good point.
It's indeed more likely to be the reason than what I had in mind :)


>
> HIH,
> 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/GV3DTJ5UNE5Z2IRC5PEEE2B7W24CL36O/


[ovirt-users] Re: ova import

2021-04-08 Thread Arik Hadas
On Thu, Apr 8, 2021 at 3:50 AM  wrote:

> I am running Ovirt 4.3 and exported machines as ova which includes disks.
> When I re import them. the disks are thin provisioned and the vm will not
> boot.
> Any idea how to get the import to  preallocate disks?  I have vms that
> will not boot.
>
It states no bootable disk is available.
> It seems the virt2vm isn't working correctly.
> ANy help would be appreciated.
>

There's no option to change the format of the imported disks at the moment
so they'd keep being thin-provisioned as they are within the OVA.
I doubt that's the reason for the failure of those VMs to boot though - can
you please share the engine.log that shows the configuration that a VM that
didn't manage to boot started with?


> Eric
> ___
> 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/GYGBNMSMEZZJA6GZPVRSMLTBRCXCAILK/
>
___
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/6XD5J6II2BOD2TENFLYRFV3R7NHZPCAS/


[ovirt-users] Re: VM CPU Pinning

2021-03-11 Thread Arik Hadas
On Thu, Mar 11, 2021 at 5:20 PM lavi.buchnik--- via Users 
wrote:

> Hi Arik,
>
> I'm using this tool to pin the VM cpu's:
> olvm-vmcontrol -m  -u api_cpu_pin@internal -v  -c setvcpu -s
> 0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55
> -e
>

So there's probably a bug in that olvm-vmcontrol thingie, I don't know how
it generates the pinning string
You can write your own script to generate a shorter one :) or update to 4.4
and use the auto-pinning feature


>
> Thanks,
> 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/NLZX6QLZ4IWUPG4G6TWHYRYLYXVYQMSV/
>
___
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/LYL7NDWPGXI5HX2BYSQAKBOMI4NECDE5/


[ovirt-users] Re: VM CPU Pinning

2021-03-11 Thread Arik Hadas
On Thu, Mar 11, 2021 at 4:27 PM lavi.buchnik--- via Users 
wrote:

> Hi,
>
> When trying to pin a VM CPU's to Physical CPU's, I'm getting this error in
> case the number of physical CPU slots are > 35 (e.g. 40):
>
> Error attempting to pin CPUs.
> Full error: Fault reason is "Operation Failed". Fault detail is "[size
> must be between 0 and 4000, Attribute: vmStatic.cpuPinning]". HTTP response
> code is "400". HTTP response message is "Bad Request".
>
> It is working for me up to 35 physical CPU's. but above it, I get that
> error.
>
> Can you please tell what this error means and how to overcome it?
> Version we are using is: 4.3.6.6-1.0.9.el7
>

You've specified a pinning-string that is longer than 4K characters - the
pinning string shouldn't be that long..


>
> Thanks,
> 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/TBC5WUEKU7Y4KGKFG4JFU7IGSXJL6K7R/
>
___
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/HTBQ4Y6QF2W6H3YSV4ITXREG25NAUKQM/


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


  1   2   3   >