AppErrors cleanup
by Allon Mureinik
Hi all,
A recent bug [1] reported as part of the translation effort alerted me to the fact that we have a lot (and I mean a LOT - over 100 per file) of deprecated, unused keys in the various AppErrors files that serve no purpose and just take up space and waste translators time when they examine them.
To make a long story short - I've just merged a patch to remove all these useless messages, and enforce via unit tests that EVERY key there should have a corresponding constant in the EngineMessage or EngineError enums.
Many thanks to my reviewers!
I know this was an tedious patch that couldn't have been too fun to review.
-Allon
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1244766
8 years, 11 months
Running oVirt 3.5 on fc21 with open jdk 1.8 (dev)
by Eli Mesika
Hi
I upgraded my workstation from fc20 to fc21 and had troubles running engine-setup on a 3.5 application.
The following instructions did the trick to me (Thanks to Alon Bar Lev)
1) Download jboss-eap-x.y from http://www.jboss.org/products/eap/overview/ (zip)
2) Extract it to /opt (insure that it has the right permissions)
3) set the following environment variables :
a) export OVIRT_ENGINE_JAVA_HOME=/usr/lib/jvm/jre
b) export OVIRT_ENGINE_JAVA_HOME_FORCE=1
4) run engine-setup as follows :
engine-setup --jboss-home=/opt/jboss-eap-x.y
Thanks
Eli Mesika
9 years
VDSM on Debian
by Samuel Barton
What is the status of VDSM for Debian hosts at this time? Is it planned to
be released with 3.6 as a stable feature?
Samuel Barton
9 years, 3 months
Re: [ovirt-devel] [CentOS-virt] qemu-kvm SLIC acpitable workaround of Windows bug
by Sandro Bonazzola
On Thu, Jul 30, 2015 at 9:04 PM, Gena Makhomed <gmm(a)csdoc.com> wrote:
> On 30.07.2015 10:49, Nux! wrote:
>
> Then you should definitely submit a bug with redhat about this, seems like
>> a serious one.
>>
>
> Ok, done:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1248758
>
> P.S.
>
> As I can see - bugzilla.redhat.com for oVirt Product
> does not contain qemu-kvm-ev Component at all - looks
> like this is yet another bug - in the bugzilla settings.
>
Adding oVirt devel mailing list.
>
> But I can't find how to report this bugzilla misconfiguration,
> so I just report this oVirt bugreport as bugreport for package
> qemu-kvm-rhev from Red Hat Enterprise Virtualization Manager Product.
>
> I hope this help.
>
Have you checked 3.5.4 RC or CentOS Virt SIG[2] to see if the bug has been
fixed in latest qemu-kvm-ev ?
[1] http://resources.ovirt.org/pub/ovirt-3.5-pre/
[2] http://cbs.centos.org/repos/virt7-kvm-common-testing/x86_64/os/
>
> ----- Original Message -----
>>
>
> On 29.07.2015 21:34, Nux! wrote:
>>>
>>> Yes, you can.
>>>> In fact you can use the binaries from the ovirt repo itself, no need to
>>>> rebuild.
>>>>
>>>
>>> Thank you!
>>>
>>> In fact - I can't use raw binaries from the ovirt repo itself,
>>> because these qemu-kvm binaries contains one bug,
>>> which is already fixed in Debian:
>>>
>>> If you want to migrate Windows from hardware node
>>> to VM using CentOS 7.1 on hardware node and libvirt xml config:
>>>
>>> <domain type='kvm' xmlns:qemu='
>>> http://libvirt.org/schemas/domain/qemu/1.0'>
>>> .....
>>> <qemu:commandline>
>>> <qemu:arg value='-acpitable'/>
>>> <qemu:arg value='file=/sys/firmware/acpi/tables/SLIC'/>
>>> </qemu:commandline>
>>> </domain>
>>>
>>> Winodws not working correctly in this case, because Windows requires,
>>> what oem_id and oem_table_id from SLIC must be also placed
>>> into oem_id and oem_table_id of RSDT.
>>>
>>> Debian version of qemu-kvm contains workaround for this windows bug,
>>> and using Debian - Windows VM will works fine. But CentOS packages
>>> does not contain such workaround, so qemu-kvm-ev now must be patched
>>> manually with each new release.
>>>
>>> Patch already was created by Michael Tokarev in 2014:
>>> this is file mjt-set-oem-in-rsdt-like-slic.diff
>>> from https://packages.debian.org/jessie/qemu-kvm
>>>
>>> This patch cleanly applies also to qemu-kvm-ev-2.1.2-23.el7_1.3.1
>>>
>>> See mjt-set-oem-in-rsdt-like-slic.diff
>>> and qemu-kvm.spec.patch in attach for details.
>>>
>>> After executing rpmbuild -ba qemu-kvm.spec
>>> you can place new qemu-kvm binaries into
>>> /srv/download/centos/7/privat/x86_64/Packages
>>> create local repo and use it for upgrading rpm packages,
>>> for example, see privat.repo and privat-createrepo-7-x86_64
>>> in attach.
>>>
>>> ==============================================================
>>>
>>> Better if this workaround of Windows bug will be included
>>> into RHEL/CentOS ovirt repo binaries, and this will allow
>>> to anybody easy migrate Windows from hardware nodes
>>> to VMs and easy run CentOS/RHEL at hardware nodes.
>>>
>>>
>>> P.S.
>>> After patching qemu-kvm - option
>>> acpitable works without any bugs:
>>>
>>> # man qemu-kvm
>>>
>>> -acpitable [sig=str][...]
>>> If a SLIC table is supplied to qemu,
>>> then the oem_id from the SLIC table
>>> will be copied into the RSDT table
>>> (this is a Debian addition).
>>>
>>> ----- Original Message -----
>>>>
>>>
>>> Is it possible to use binary packages build from
>>>>>
>>>>> http://resources.ovirt.org/pub/ovirt-3.5/rpm/el7/SRPMS/qemu-kvm-ev-2.1.2-...
>>>>> with plain CentOS 7.1 and use all other packages from CentOS
>>>>> (libvirt, virt-manager, etc)
>>>>>
>>>>> Is it have reasons, if I not use live migrations and qcow2 snapshots?
>>>>> (instead use zfs, zvols and zfs snapshots for VM disks online backups)
>>>>>
>>>>> Is using qemu-kvm-ev with CentOS 7.1 have any disadvantages?
>>>>>
>>>>
> --
> Best regards,
> Gena
> _______________________________________________
> CentOS-virt mailing list
> CentOS-virt(a)centos.org
> http://lists.centos.org/mailman/listinfo/centos-virt
>
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
9 years, 3 months
ovirt-engine-extension-aaa-ldap-setup broken dep on 3.5
by Sandro Bonazzola
Hi,
looks like a recent change in ovirt-engine-extension-aaa-ldap-setup is
now requiring engine 3.6 and otopi 1.4. Please branch
ovirt-engine-extension-aaa-ldap-setup to keep 3.5 support or make it
still compatible with 3.5.
*07:40:20* package:
ovirt-engine-extension-aaa-ldap-setup-1.1.0-0.0.master.20150729115014.git1b0203a.el7.noarch
from check-custom-el7*07:40:20* unresolved deps: *07:40:20*
ovirt-engine >= 0:3.6*07:40:20* otopi >= 0:1.4.0
Thanks,
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
9 years, 3 months
Hello devel@ovirt.org
by zhukaijie
Hello,
Hello, I am a freshman in the Ovirt Development.Now I'm using Ovirt UI Plugin developping a dialog, which can get the input frome administrator and pass the value to a VM Customer Property called "test".Using Ovirt UI Plugin can create a dialog and get the value from administrator easily.But I don't know how to pass the value to the VM Customer Property "test".Could you please teach me how to do it? Thank you
9 years, 3 months
cloud-init network interface alias
by Dobó László
Hi,
I found a few strange things around the cloud-init network setup.
On the network interface field the validation form looks like this:
"A-Za-z0-9_-", while the api validation almost the same except you can
use the "." (dot) character also.
So if I like to define a network interface alias, like "eth0:1" I can't,
however the cloud-init application handle it well.
Is there any reason why the ":" character need to be forbidden?
Regards,
enax
9 years, 3 months
Dropping Fedora 21 engine builds on master / 3.6 on July 31
by Sandro Bonazzola
Hi,
since Fedora 21 is not going to be officially supported in 3.6 / master, in order to save resources for our CI systems we're going to drop builds for
engine related packages starting from July 31.
You may still continue developing engine on Fedora 21 by manually building required dependencies or you may upgrade to Fedora 22 and receive nightly
builds by CI system.
Note that VDSM related projects will still continue to be built in CI as long as VDSM team supports it.
Thanks
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
9 years, 3 months
