April 2012 - Users - oVirt List Archives

[Users] can't get VM working (no ISO images, no Console)
by Frank Wall 24 Apr '12

24 Apr '12

Hi, I've setup a test instance of ovirt like this... - setup ovirt engine on Fedora 16 using yum (ovirt-engine-3.0.0_0001-1.6.fc16.x86_64) - setup ovirt node "ovirt-node1" using the ISO image ovirt-node-iso-2.3.0-1.0.fc16.iso - created a new datacenter with NFS storage ("datacenter2") - created a new cluster ("cluster2") - added ovirt node "ovirt-node1" to cluster "cluster2" - created an NFS storage for virtual machines ("nfs_storage1") - created an NFS storage for ISO images ("iso_images1") - created a new VM on "cluster2" with disk space provided by "nfs_storage1" ...but I fail to get any VM working. First of all, I've uploaded an ISO image with the iso-uploader. I can verify that it was uploaded successfully: [root@ovirt-engine ~]# engine-iso-uploader -v -i iso_images1 upload FreeBSD-8.2-RELEASE-amd64-disc1.iso Please provide the REST API password for the admin@internal oVirt Engine user (CTRL+D to abort): DEBUG: URL is https://ovirt-engine.EXAMPLE.COM:8443/api/storagedomains?search=name%3Diso_… DEBUG: Returned XML is <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <storage_domains> <storage_domain href="/api/storagedomains/b2d11688-84ce-40ef-b10f-f036ac806cf9" id="b2d11688-84ce-40ef-b10f-f036ac806cf9"> <name>iso_images1</name> <link href="/api/storagedomains/b2d11688-84ce-40ef-b10f-f036ac806cf9/permissions" rel="permissions"/> <link href="/api/storagedomains/b2d11688-84ce-40ef-b10f-f036ac806cf9/files" rel="files"/> <type>iso</type> <master>false</master> <storage> <type>nfs</type> <address>192.168.200.108</address> <path>/mnt/iso1</path> </storage> <available>15032385536</available> <used>3221225472</used> <committed>0</committed> <storage_format>v1</storage_format> </storage_domain> </storage_domains> DEBUG: id=b2d11688-84ce-40ef-b10f-f036ac806cf9 address=192.168.200.108 path=/mnt/iso1 DEBUG: local NFS mount point is /tmp/tmpxG6M3H DEBUG: NFS mount command (/bin/mount -t nfs -o rw,sync,soft 192.168.200.108:/mnt/iso1 /tmp/tmpxG6M3H) DEBUG: /bin/mount -t nfs -o rw,sync,soft 192.168.200.108:/mnt/iso1 /tmp/tmpxG6M3H DEBUG: _cmds(['/bin/mount', '-t', 'nfs', '-o', 'rw,sync,soft', '192.168.200.108:/mnt/iso1', '/tmp/tmpxG6M3H']) DEBUG: returncode(0) DEBUG: STDOUT() DEBUG: STDERR() ERROR: FreeBSD-8.2-RELEASE-amd64-disc1.iso exists on 192.168.200.108. Either remove it or supply the --force option to overwrite it. DEBUG: /bin/umount -t nfs -f /tmp/tmpxG6M3H DEBUG: /bin/umount -t nfs -f /tmp/tmpxG6M3H DEBUG: _cmds(['/bin/umount', '-t', 'nfs', '-f', '/tmp/tmpxG6M3H']) DEBUG: returncode(0) DEBUG: STDOUT() DEBUG: STDERR() Still I am unable to select the ISO image from the VM configuration menu, the "change CD" function doesn't show the ISO image either. Besides that my test VM is in status "Up", but I can't select the "console" option, it is grayed out. So maybe you can advise me how to get the first test VM working. I'd like to continue with further tests as soon as possible :-) Thanks - Frank

2 1

[Users] UPDATE: oVirt 3.1 release date changed
by Ofer Schreiber 24 Apr '12

24 Apr '12

Due to multiple integration issues (Java 7, Fedora 17 and JBoss official rpm support) we've decided to postpone the next release of oVirt [1] to June 27th. This one month delay will hopefully give us enough time to stabilize all the different layers of oVirt, and produce a better release. Stay tuned, -- Ofer Schreiber oVirt Release Manager [1] http://www.ovirt.org/wiki/Second_Release

1 0

[Users] oVirt Weekly Sync Meeting - 2012-04-24
by Mike Burns 24 Apr '12

24 Apr '12

Minutes: http://ovirt.org/meetings/ovirt/2012/ovirt.2012-04-24-14.00.html Minutes (text): http://ovirt.org/meetings/ovirt/2012/ovirt.2012-04-24-14.00.txt Log: http://ovirt.org/meetings/ovirt/2012/ovirt.2012-04-24-14.00.log.html ========================= #ovirt: oVirt Weekly Sync ========================= Meeting started by mburns at 14:00:30 UTC. The full logs are available at http://ovirt.org/meetings/ovirt/2012/ovirt.2012-04-24-14.00.log.html . Meeting summary --------------- * Agenda and Roll Call (mburns, 14:00:47) * LINK: http://www.ovirt.org/wiki/Meetings#Weekly_project_sync_meeting (mburns, 14:02:59) * Next Release Status (mburns, 14:03:47) * feature freeze is April 30 (mburns, 14:04:54) * AGREED: move release to 2012-06-30 and feature freeze to 2012-05-31 (mburns, 14:13:41) * test day will move out as well (mburns, 14:15:57) * AGREED: release date June 27, possible slip to Jul 2 (mburns, 14:20:26) * AGREED: target May 15 for alpha release (mburns, 14:23:51) * ACTION: oschreib to send notification of release date change to arch@ users@ board@ (mburns, 14:25:31) * AGREED: alpha testing is on F17 RC (mburns, 14:28:23) * java 7, f17 and jboss rpms (mburns, 14:32:11) * we're trying to use F17 with java 7 and distro specific jboss rpms where available (mburns, 14:32:39) * AGREED: Fedora 17 support is a blocker (mburns, 14:34:54) * AGREED: using distro jboss rpms is not a blocker, but is a goal (mburns, 14:38:37) * we should re-evaluate if we're going to miss using distro jboss rpms (mburns, 14:39:19) * if small delay, we may choose to slip the release to get it in (mburns, 14:39:39) * ACTION: mburns to add fedora jboss and java 7 to agenda to re-evaluate (mburns, 14:43:11) * AGREED: java 7 is a goal, will re-evaluate for blocker status on the next meeting (mburns, 14:44:08) * Upcoming workshops (mburns, 14:44:42) * one-day workshops added at LC Japan, NA, Europe (mburns, 14:45:49) * LINK: http://lists.ovirt.org/pipermail/arch/2012-April/000528.html (mburns, 14:47:51) * Signed-off-by (mburns, 15:04:11) * enabled in ovirt-node and ovirt-node-iso (mburns, 15:04:28) * AGREED: all projects will require signed-off-by starting may 1st (mburns, 15:06:31) * LINK: http://kerneltrap.org/files/Jeremy/DCO.txt (mburns, 15:09:28) * sub-project status (mburns, 15:10:38) * node should be good with new dates, only major tasks left are stability and f17 testing which are starting this week (mburns, 15:11:18) * Other Topics (mburns, 15:12:45) * Next Week's Meeting is Wednesday 2012-05-01 at 14:00 UTC (10:00 AM EDT) (mburns, 15:14:02) Meeting ended at 15:14:43 UTC. Action Items ------------ * oschreib to send notification of release date change to arch@ users@ board@ * mburns to add fedora jboss and java 7 to agenda to re-evaluate Action Items, by person ----------------------- * mburns * mburns to add fedora jboss and java 7 to agenda to re-evaluate * oschreib * oschreib to send notification of release date change to arch@ users@ board@ * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * mburns (138) * itamar (58) * oschreib (27) * lh (26) * lpeer (22) * doronf (22) * cctrieloff (21) * aglitke_ (8) * ovirtbot (6) * jb_netapp (5) * miki (4) * rharper (4) * quaid (4) * bazulay (3) * masayag (2) * sgordon (2) * aliguori (1) * jhernand (1) * ofrenkel (1) * dustins (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

[Users] Planning oVirt Workshops
by Leslie Hawthorn 24 Apr '12

24 Apr '12

(N.B.: This message was copied to users(a)ovirt.org but I am not clear if my subscription was approved. If you happen to note that this message did not get to that list, let me know.) Hello everyone, I am a new(ish) hire at Red Hat working on Carl Trieloff's team. I will be attending tomorrow's oVirt IRC meeting to provide an update on upcoming oVirt workshops, but in the interim wanted to circulate a proposed agenda. Please note that we're planning one day workshops at LinuxCon Japan, North America and Europe, as well as a 2 day workshop at NetApp HQ in California (target date 8 and 9th August 2012). As we're discussing workshop agendas for the one day events, it would be good to have an idea of what we'd like to present given the additional day. Here is a *very* preliminary agenda: - intro & arch - engine, vdsm deep dives - storage roadmap/discussion - network roadmap/discussion Open Questions: 1) What other topics should be covered during the workshop? 2) Who would like to volunteer to be an instructor? Cheers, LH -- Leslie Hawthorn Community Action and Impact Open Source and Standards @ Red Hat identi.ca/lh twitter.com/lhawthorn

4 3

[Users] rhev-guest for el5 and el5 derived
by Nathanaël Blanchet 24 Apr '12

24 Apr '12

This is a multi-part message in MIME format. --------------080809040709030500060800 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Hello, I need to make rhev-agent work mainly on centos 5. For centos 6 it's easy, because we can directly find SRPMS on redhat ftp. So I tried many ways to build it on my own: 1. git clone git://gerrit.ovirt.org/ovirt-guest-agent and ./autogen.sh. It claims "Autoconf version 2.63 or higher is required" but rhel 5 autoconf version is 2.59" 2. rpm -bb ovirt-guest-agent.spec.The issue is that I'm running i386 instead of an expected i686. If I change this required value in the SPEC file by doing "ExclusiveArch: i686 x86_64 i386 ", it complains then : "Group field must be present in the package: ovirt-guest-agent-pam-module". I'm stuck in any ways, It's a pity that rhel5x is the most used rhel system... -- Nathanaël Blanchet Supervision réseau Pôle exploitation et maintenance Département des systèmes d'information 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 blanchet(a)abes.fr --------------080809040709030500060800 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> </head> <body bgcolor="#FFFFFF" text="#000000"> Hello, I need to make rhev-agent work mainly on centos 5. For centos 6 it's easy, because we can directly find SRPMS on redhat ftp. So I tried many ways to build it on my own: <ol> <li> git clone git://gerrit.ovirt.org/ovirt-guest-agent and ./autogen.sh. It claims  "Autoconf version 2.63 or higher is required" but rhel 5 autoconf version is 2.59"</li> <li>rpm -bb ovirt-guest-agent.spec.The issue is that I'm running i386 instead of an expected i686. If I change this required value in the SPEC file by doing "ExclusiveArch: i686 x86_64 i386 ", it complains then : "Group field must be present in the package: ovirt-guest-agent-pam-module".</li> </ol> I'm stuck in any ways,  It's a pity that rhel5x is the most used rhel system... <pre class="moz-signature" cols="72">-- Nathanaël Blanchet Supervision réseau Pôle exploitation et maintenance Département des systèmes d'information 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 <a class="moz-txt-link-abbreviated" href="mailto:blanchet@abes.fr">blanchet(a)abes.fr</a> </pre> </body> </html> --------------080809040709030500060800--

2 1

[Users] Agenda for oVirt Weekly Sync 2012-04-24
by Mike Burns 24 Apr '12

24 Apr '12

The latest agenda will always be online[1]. * Status of Next Release * Sub-project reports (engine, vdsm, node) * Signed-off-by in commit tag check-up (rharper) * Java 7 in oVirt Engine (oschreib) * ovirt-engine-jbossas vs. Fedora17-jbossas (oschreib) * Moving to Fedora 17 (oschreib) * Do we need to re-evaluate release date based on above 3 items? (itamar) * Upcoming workshops * Topics * Dates/Events * Hardware availability for automated testing (mburns) * Would be good to have board members from sponsor companies available for this discussion [1] http://www.ovirt.org/wiki/Meetings#Weekly_project_sync_meeting

1 0

[Users] Call for agenda topics -- Weekly Sync 2012-04-24
by Mike Burns 23 Apr '12

23 Apr '12

Reminder: Meeting moved this week to Tuesday 2012-04-24 due to Israel Independence Day. This mail is a call for topics for the 2012-04-24 Weekly Sync meeting. Standing Agenda Topics: * Status of Next Release * Sub-project reports (engine, vdsm, node) Other topics that need to be covered this week: * Additional Hardware resources for Jenkins use If you have additional topics, please reply to this email with the topic(s) you want to cover. A final planned agenda will be sent out prior to the meeting. Thanks The oVirt Team

4 3

[Users] locale en_AU
by Jason Lawer 23 Apr '12

23 Apr '12

I just tried to run engine-setup and got the following error. [root@manager ~]# engine-setup Error: current locale (en_AU.UTF-8) is not supported. supported locales are: en_US.UTF-8,en_US.utf-8,en_US.utf8 Please check log file /var/log/ovirt-engine/engine-setup_2012_04_23_09_07_53.log for more information While I can easily change the locale settings on the box, I really think this is a bit of a crazy limitation as almost every other bit of software seems to assume en_AU = en_US as almost no software ends up creating an Australian localization for it. The character set is the same, the keyboards are the same, and I can't see any reason why en_AU (or say en_NZ) would cause a problem. The only differences I can think of are dates (DD/MM/YYYY vs MM/DD/YYYY) and the metric system. What would need to be the process to fix this? Is this just because no one has been willing to test or it is a policy? Jason

2 3

[Users] fedora qemu modern CPU recognition issues cause ovirt manged host to go non-operational
by Dead Horse 23 Apr '12

23 Apr '12

Seeing an issue wherein ovirt moves a managed host to non-operational state. This occurs with the currently released version of ovirt and the latest development builds. The ovirt host is loaded with Fedora core 16 and equipped with most current development version of the vdsm. *Editorial node* The latest vdsm to work on the FC16 host required building and adding newer versions of the sanlock, libvirt, lvm2 and device-mapper packages than what FC16 provides. Ultimately however none of the newer packages have any bearing on this failure mode. The failure mode is as follows. Upon successfully adding the host and setting the cluster CPU compatibility level oVirt will offline the host with the following message: --> Host ovirtnode moved to Non-Operational state as host does not meet the cluster's minimum CPU level. Missing CPU features : model_Nehalem Under the hood the actual cause of this failure is that qemu is not correctly able to identify the host CPU feature flags. This can be observed by doing: qemu-system-x86_64 -cpu Nehalem,check which fails with: warning: host cpuid 0000_0000 lacks requested flag 'fpu' [0x00000001] warning: host cpuid 0000_0000 lacks requested flag 'de' [0x00000004] and on and on... A simple check of "cat /proc/cpuinfo | grep flags" flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm dca sse4_1 sse4_2 popcnt lahf_lm ida dts tpr_shadow vnmi flexpriority ept vpid Thus the CPU is more than capable of everything being asked of it via the cpudef for "Nehalem" in /etc/qemu/target-x86_64.conf. This is only an issue on Fedora hosts. RHEL/CentOS/SL hosts work fine. This was recognized as an issue RHEL and fixed there but has not been fixed in Fedora. See: http://wiki.qemu.org/Features/CPUModels#Examples and this: https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=689665 and this related discussion in qemu-devel: http://www.mail-archive.com/qemu-devel@nongnu.org/msg101360.html Thus is appears that the changes were made to the RHEL qemu (eg: cpu type rhel6) AKA the change one needs to make to the ovirt engine database to have ovirt manage a EL based host. Fedora hosts--> psql -U postgres engine -c "update vdc_options set option_value='pc-0.14' where option_name='EmulatedMachine' and version='3.0';" EL hosts --> psql -U postgres engine -c "update vdc_options set option_value='rhel6.2.0' where option_name='EmulatedMachine' and version='3.0';" Thus at the moment any host loaded with Fedora and manged by oVirt utilizing a Sandy Bridge, Nehalem or Westmere processor will be dead in the water. -DHC

3 3

[Users] Problem with live migration.
by Martin Hovmöller 22 Apr '12

22 Apr '12

I can't live migrate the vm's in my cluster: 012-04-17 04:06:39,728 INFO [org.ovirt.engine.core.bll.MigrateVmCommand] (pool-5-thread-48) Running command: MigrateVmCommand internal: false. Entities affected : ID: ce9bb531-4d2a-4f5e-9935-3c8a4f5db94a Type: VM 2012-04-17 04:06:39,743 INFO [org.ovirt.engine.core.vdsbroker.MigrateVDSCommand] (pool-5-thread-48) START, MigrateVDSCommand(vdsId = f33ffc14-87ba-11e1-b610-e3aeca1e8008, vmId=ce9bb531-4d2a-4f5e-9935-3c8a4f5db94a, srcHost=10.23.30.130, dstVdsId=b4d329b4-87b6-11e1-ac0a-b70ec8cc50f0, dstHost=10.23.30.110:54321, migrationMethod=ONLINE), log id: 7c7201be 2012-04-17 04:06:39,748 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateBrokerVDSCommand] (pool-5-thread-48) VdsBroker::migrate::Entered (vm_guid=ce9bb531-4d2a-4f5e-9935-3c8a4f5db94a, srcHost=10.23.30.130, dstHost=10.23.30.110:54321, method=online 2012-04-17 04:06:39,749 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateBrokerVDSCommand] (pool-5-thread-48) START, MigrateBrokerVDSCommand(vdsId = f33ffc14-87ba-11e1-b610-e3aeca1e8008, vmId=ce9bb531-4d2a-4f5e-9935-3c8a4f5db94a, srcHost=10.23.30.130, dstVdsId=b4d329b4-87b6-11e1-ac0a-b70ec8cc50f0, dstHost=10.23.30.110:54321, migrationMethod=ONLINE), log id: 3c40c2de 2012-04-17 04:06:39,834 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateBrokerVDSCommand] (pool-5-thread-48) FINISH, MigrateBrokerVDSCommand, log id: 3c40c2de 2012-04-17 04:06:39,840 INFO [org.ovirt.engine.core.vdsbroker.MigrateVDSCommand] (pool-5-thread-48) FINISH, MigrateVDSCommand, return: MigratingFrom, log id: 7c7201be 2012-04-17 04:06:42,166 INFO [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] (QuartzScheduler_Worker-18) vds::refreshVmList vm id ce9bb531-4d2a-4f5e-9935-3c8a4f5db94a is migrating to vds rhevh1.<domain> ignoring it in the refresh till migration is done [...] 2012-04-17 04:07:33,852 INFO [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] (QuartzScheduler_Worker-34) vds::refreshVmList vm id ce9bb531-4d2a-4f5e-9935-3c8a4f5db94a status = Paused on vds rhevh1.<domain> ignoring it in the refresh till migration is done 2012-04-17 04:07:37,407 ERROR [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] (QuartzScheduler_Worker-71) Rerun vm ce9bb531-4d2a-4f5e-9935-3c8a4f5db94a. Called from vds rhevh2.<domain> 2012-04-17 04:07:37,414 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand] (pool-5-thread-47) START, MigrateStatusVDSCommand(vdsId = f33ffc14-87ba-11e1-b610-e3aeca1e8008, vmId=ce9bb531-4d2a-4f5e-9935-3c8a4f5db94a), log id: 8dfce1b 2012-04-17 04:07:37,496 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase] (pool-5-thread-47) Failed in MigrateStatusVDS method 2012-04-17 04:07:37,497 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase] (pool-5-thread-47) Error code createErr and error message VDSGenericException: VDSErrorException: Failed to MigrateStatusVDS, error = Error creating the requested virtual machine 2012-04-17 04:07:37,497 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase] (pool-5-thread-47) Command org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand return value Class Name: org.ovirt.engine.core.vdsbroker.vdsbroker.StatusOnlyReturnForXmlRpc mStatus Class Name: org.ovirt.engine.core.vdsbroker.vdsbroker.StatusForXmlRpc mCode 9 mMessage Error creating the requested virtual machine 2012-04-17 04:07:37,497 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase] (pool-5-thread-47) Vds: rhevh2.<domain> 2012-04-17 04:07:37,497 ERROR [org.ovirt.engine.core.vdsbroker.VDSCommandBase] (pool-5-thread-47) Command MigrateStatusVDS execution failed. Exception: VDSErrorException: VDSGenericException: VDSErrorException: Failed to MigrateStatusVDS, error = Error creating the requested virtual machine 2012-04-17 04:07:37,497 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand] (pool-5-thread-47) FINISH, MigrateStatusVDSCommand, log id: 8dfce1b 2012-04-17 04:07:37,528 WARN [org.ovirt.engine.core.bll.MigrateVmCommand] (pool-5-thread-47) CanDoAction of action MigrateVm failed. Reasons:ACTION_TYPE_FAILED_VDS_VM_CLUSTER,VAR__ACTION__MIGRATE,VAR__TYPE__VM There is no problem regarding storage or anything like that. If I shut down the vm I can start it on the other host without any problems whatsoever. Do I need to do something to make live migration work? Trying to dig in the logs on the hypervisors, but there's so much stuff being logged there...

3 9