- Devel - oVirt List Archives

Postponing oVirt 3.6.0 beta
by Sandro Bonazzola 03 Aug '15

03 Aug '15

Hi, in order to solve an issue[1] discovered while testing the candidate build for the beta release we need to postpone beta release at least by one day for getting the fix in. Thanks, [1] https://bugzilla.redhat.com/show_bug.cgi?id=1249671 -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

(no subject)
by czg sai 03 Aug '15

03 Aug '15

I have one server with cpu power8e. I configure it as a host on ovirt engine. Vm running on host can be booted by CD, but os can not been intstalled.

3 2

[oVirt 3.6 Localization Question #25] "Concurrent with"
by Yuko Katabami 03 Aug '15

03 Aug '15

This is a multi-part message in MIME format. --------------060709050108010505080602 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Hello again, This will be my last question for today: *File:***UIConstants* Resource ID:** * concurrentFenceAgent *String: *Concurrent with *Question: *Is this string used to add concurrent fencing agents as described in http://www.ovirt.org/Features/Design/DetailedHostPMMultipleAgents? Does it appear on the Power Management window? Since I do not have any power management device, I am not able to check it in the test environment. Would it be possible to have a screenshot, if anyone has the setup? Many thanks in advance, Yuko Katabami --------------060709050108010505080602 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=utf-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> Hello again, This will be my last question for today: File: UIConstants Resource ID: concurrentFenceAgent String: Concurrent with Question: Is this string used to add concurrent fencing agents as described in <a class="moz-txt-link-freetext" href="http://www.ovirt.org/Features/Design/DetailedHostPMMultipleAgents">http://www.ovirt.org/Features/Design/DetailedHostPMMultipleAgents</a>? Does it appear on the Power Management window? Since I do not have any power management device, I am not able to check it in the test environment. Would it be possible to have a screenshot, if anyone has the setup? Many thanks in advance, Yuko Katabami </body> </html> --------------060709050108010505080602--

2 2

[oVirt 3.6 Localization Question #24] "Provided NetworkAttachments contains duplicates."
by Yuko Katabami 03 Aug '15

03 Aug '15

This is a multi-part message in MIME format. --------------030002020209030706030801 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Hi all, Another question to post * File:***AppErrors* Resource ID:*** ACTION_TYPE_FAILED_NETWORK_ATTACHMENT_CONTAINS_DUPLICATES *String: *Provided NetworkAttachments contains duplicates. *Question: *Does this mean it contains duplicated setting, or the Network Attachment itself is duplicated?* *There is also a grammatical error with plural "NetworkAttachments" and the verb with "s" for the third person singular present form. It should be either "Network Attachment contains" or "Network Attachments contain". Kind regards, Yuko --------------030002020209030706030801 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=utf-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> Hi all, <div class="moz-signature"> Another question to post File: AppErrors Resource ID: ACTION_TYPE_FAILED_NETWORK_ATTACHMENT_CONTAINS_DUPLICATES String: Provided NetworkAttachments contains duplicates. Question: Does this mean it contains duplicated setting, or the Network Attachment itself is duplicated? There is also a grammatical error with plural "NetworkAttachments" and the verb with "s" for the third person singular present form. It should be either "Network Attachment contains" or "Network Attachments contain". Kind regards, Yuko <meta http-equiv="content-type" content="text/html; charset=utf-8"> </div> </body> </html> --------------030002020209030706030801--

2 2

[oVirt 3.6 Localization Question #23] "NetworkAttachment" vs "Network Attachment"
by Yuko Katabami 03 Aug '15

03 Aug '15

This is a multi-part message in MIME format. --------------030808040506060700030406 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Hi all, We have another question which need your help. *File:***AppErrors* Resource IDs:*** NETWORK_ATTACHMENT_REFERENCES_NETWORK_INCOHERENTLY NETWORK_ATTACHMENT_REFERENCES_NICS_INCOHERENTLY ACTION_TYPE_FAILED_NETWORK_ATTACHMENT_CONTAINS_DUPLICATES * Strings: * Cannot ${action} ${type}. *NetworkAttachment* (id ${referrerId}) does not reference network coherently. Network name and id reference different networks: networkId ${referringId} networkName ${referringName}. Cannot ${action} ${type}. *NetworkAttachment* (id ${ENTITY_ID}) does not reference nic coherently. Nic name and id references different nic: nicId ${referringId} nicName ${referringName}. Provided *NetworkAttachments* contains duplicates. *Question: *Those three strings contain the term "NetworkAttachment" instead of "Network Attachment". Could I confirm these do not have to be literal and we can translate them as "Network Attachment"? Kind regards, Yuko Katabami --------------030808040506060700030406 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=utf-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> Hi all, We have another question which need your help. <div class="moz-signature">File: AppErrors Resource IDs: <meta http-equiv="content-type" content="text/html; charset=utf-8"> NETWORK_ATTACHMENT_REFERENCES_NETWORK_INCOHERENTLY NETWORK_ATTACHMENT_REFERENCES_NICS_INCOHERENTLY ACTION_TYPE_FAILED_NETWORK_ATTACHMENT_CONTAINS_DUPLICATES Strings: <meta http-equiv="content-type" content="text/html; charset=utf-8"> Cannot ${action} ${type}. NetworkAttachment (id ${referrerId}) does not reference network coherently. Network name and id reference different networks: networkId ${referringId} networkName ${referringName}. Cannot ${action} ${type}. NetworkAttachment (id ${ENTITY_ID}) does not reference nic coherently. Nic name and id references different nic: nicId ${referringId} nicName ${referringName}. Provided NetworkAttachments contains duplicates. Question: Those three strings contain the term "NetworkAttachment" instead of "Network Attachment". Could I confirm these do not have to be literal and we can translate them as "Network Attachment"? Kind regards, Yuko Katabami <meta http-equiv="content-type" content="text/html; charset=utf-8"> </div> </body> </html> --------------030808040506060700030406--

2 2

[oVirt 3.6 Localization Question #22] "Monitor"
by Yuko Katabami 03 Aug '15

03 Aug '15

This is a multi-part message in MIME format. --------------040901030209000303030708 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Hi all, The following question has been raised by a translator. Could anyone help us? * File:***LocalizedEnums* Resource ID:*** VdcActionType___Monitor *String: *Monitor *Question: *Is it noun or verb? Where does it appear in GUI?* *Thanks in advance, Yuko Katabami --------------040901030209000303030708 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=utf-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> Hi all, The following question has been raised by a translator. Could anyone help us? <div class="moz-signature"> File: <a class="GOKOG0LCMM active_link"> </a> <meta http-equiv="content-type" content="text/html; charset=utf-8"> LocalizedEnums Resource ID: VdcActionType___Monitor String: Monitor Question: Is it noun or verb? Where does it appear in GUI? Thanks in advance, Yuko Katabami <meta http-equiv="content-type" content="text/html; charset=utf-8"> </div> </body> </html> --------------040901030209000303030708--

2 2

[ANN] JMX control using CLI for ovirt-engine
by Roy Golan 02 Aug '15

02 Aug '15

Hi all, We can now have JMX control over the backend, from the command line, using ovirt authentication [1] It's is now very easy to: 1. raise logging level to DEBUG 2. get threading info 3. get transaction stats 4. interact with whatever we exposed as JMX beans (like LockManager) 5. shutdown, redeploy context and so on... $JBOSS_HOME/bin/jboss-cli.sh \ --controller=127.0.0.1:8706 --connect --user=admin@internal \ /subsystem=logging/logger=org.ovirt.engine.core.bll:write-attribute(name=level,value=DEBUG) See more examples in the commit message. Currently only admin@internal would be allow to perform such actions. We may consider to extend that to a dedicated system role. [1] https://gerrit.ovirt.org/#/c/29693/ (included in version 3.6) Thanks, Roy

1 0

vdsm from 3.5 branch is currently failing to build on Fedora
by Sandro Bonazzola 31 Jul '15

31 Jul '15

Hi, vdsm from 3.5 branch is currently failing to build on Fedora, failing pep8. Please fix ASAP. Fedora 20: http://jenkins.ovirt.org/view/Stable%20branches%20per%20project/view/vdsm/j… Fedora 21: http://jenkins.ovirt.org/view/Stable%20branches%20per%20project/view/vdsm/j… -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

3 4

Re: [ovirt-devel] [CentOS-virt] qemu-kvm SLIC acpitable workaround of Windows bug
by Sandro Bonazzola 31 Jul '15

31 Jul '15

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

1 0

ovirt-engine-extension-aaa-ldap-setup broken dep on 3.5
by Sandro Bonazzola 31 Jul '15

31 Jul '15

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

2 1