Re: [ovirt-users] Balloon driver unavailable
On Wed, 2014-11-12 at 08:35 +0100, Demeter Tibor wrote: > Hi, > > > I have a lot of centos 6 based vms and I have install "ovirt guest > agent" for those vms. > But two vm always say "The balloon driver on xxxvm on hostX is > requested but unavailable" > I did check the virtio_balloon module are loaded on vms. > > > Anybody can me help? > > > Thanks in advance > > > Tibor I see that too, but only on Windows 2008 R2 guests... No one else ever said anything about it, so I thought it was just me:) -- Med Vänliga Hälsningar --- Karli Sjöberg Swedish University of Agricultural Sciences Box 7079 (Visiting Address Kronåsvägen 8) S-750 07 Uppsala, Sweden Phone: +46-(0)18-67 15 66 karli.sjob...@slu.se ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] Balloon driver unavailable
Hi, I have a lot of centos 6 based vms and I have install "ovirt guest agent" for those vms. But two vm always say "The balloon driver on xxxvm on hostX is requested but unavailable" I did check the virtio_balloon module are loaded on vms. Anybody can me help? Thanks in advance Tibor ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] upgrade glusterfs under ovirt
Hi, I see that glusterfs 3.6 has released. What is the official way to upgrade this under a production ovirt cluster? Can I use the "yum update" command or I need to switch to the host to maintenance and select "reinstall" button? Thanks Tibor ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] Can you update the wiki about how to setup ovirt reports development?
hi all , I am trying to view the ovirt-reports code based on the version of 3.5. And it's necessary that setting up the reports development. But the wiki of http://www.ovirt.org/How_to_setup_a_oVirt_Reports_development_environment had become obsolete. So would you share the right method of how to setup a ovirt reports development environment based on 3.5 version? Thank u for consideration.[?] ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] Problem installing windows 2008 sp2 and windows 2012 server standard
Hi, Ovirt 3.5 on Fedora 20; all updates latest virtio-win 0.1-81 In the process of testing ovirt: testing Windows installation with virtio-win drivers A) I've tried to install Windows 2008 SP2 using Virtio disk, the installation succeeded, the problem was with: - the Virtio Network, the was driver installed, the NIC card detected, but no trafic after configuration, I switched to e1000 and it works. - I had an unknow SCSI device, so I installed the driver and I got a nice BSOD and I had to use a previous snaphot to re-use the VM. - Finally the ovirt agent did not seem to work, no information on Ovirt GUI. B) With Windows 2012, only the IDE disk worked for installation, the Virtio and Virtio-SCSI helped detecting the disk, but Windows installer won't install "Error: windows can't install on disk0 partition 2 error 0x8031" using the IDE option, windows is still installing after 1h, it's very slow... ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] qemu version
- Original Message - > From: "John H. Thompson (GSFC-606.2)[Computer Sciences Corporation]" > > To: users@ovirt.org > Sent: Tuesday, November 11, 2014 8:33:17 PM > Subject: [ovirt-users] qemu version > > oVirt seems to want to install a very old version of qemu, version 0.12.1 in > fact. Version 2.1.2 is now available. Is there any way to make oVirt use a > newer version or use/leave what’s already installed? > Hi John, oVirt does not choose the qemu version. It uses the one available in centos[1] or the other relevant distro repo. Having that said, you need to bare in mind there's a whole stack build on top of qemu (libvirt, vdsm, etc) and jumping forward may destabilize the setup you're using. Doron [1] http://mirror.centos.org/centos/6.6/updates/x86_64/Packages/ ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] qemu version
oVirt seems to want to install a very old version of qemu, version 0.12.1 in fact. Version 2.1.2 is now available. Is there any way to make oVirt use a newer version or use/leave what¹s already installed? ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] Cannot find suitable CPU model for given data
When trying to launch a Centos6.5 VM (pulled from ovirt-image-repository) onto a Westmere (Dell 6100) host through oVirt, the following error occurs from libvirt: 3312: warning : x86Decode:1517 : Preferred CPU model Westmere not allowed by hypervisor; closest supported model will be used 3312: error : x86Decode:1573 : internal error: Cannot find suitable CPU model for given data Googling the issue yeilds: https://bugzilla.redhat.com/show_bug.cgi?id=804224 System info as Virsh sees it. $virsh capabilities 6622b24b-5019-4644-af20-289533f0a7bc x86_64 Westmere Intel CPUs qemu-kvm supports. $/usr/libexec/qemu-kvm -cpu "?" -nodefconfig x86 Opteron_G5 AMD Opteron 63xx class CPU x86 Opteron_G4 AMD Opteron 62xx class CPU x86 Opteron_G3 AMD Opteron 23xx (Gen 3 Class Opteron) x86 Opteron_G2 AMD Opteron 22xx (Gen 2 Class Opteron) x86 Opteron_G1 AMD Opteron 240 (Gen 1 Class Opteron) x86 Haswell Intel Core Processor (Haswell) x86 SandyBridge Intel Xeon E312xx (Sandy Bridge) x86 Westmere Westmere E56xx/L56xx/X56xx (Nehalem-C) x86 Nehalem Intel Core i7 9xx (Nehalem Class Core i7) x86 Penryn Intel Core 2 Duo P9xxx (Penryn Class Core 2) x86 Conroe Intel Celeron_4x0 (Conroe/Merom Class Core 2) x86 cpu64-rhel5 QEMU Virtual CPU version (cpu64-rhel5) x86 cpu64-rhel6 QEMU Virtual CPU version (cpu64-rhel6) x86 n270 Intel(R) Atom(TM) CPU N270 @ 1.60GHz x86 athlon QEMU Virtual CPU version 0.12.1 x86 pentium3 x86 pentium2 x86 pentium x86 486 x86 coreduo Genuine Intel(R) CPU T2600 @ 2.16GHz x86 qemu32 QEMU Virtual CPU version 0.12.1 x86kvm64 Common KVM processor x86 core2duo Intel(R) Core(TM)2 Duo CPU T7700 @ 2.40GHz x86 phenom AMD Phenom(tm) 9550 Quad-Core Processor x86 qemu64 QEMU Virtual CPU version 0.12.1 CPU model name from /proc/cpu Intel(R) Xeon(R) CPU X5660 @ 2.80GHz ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] replace ovirt engine host
I dunno why this is all so simple for you.
I just replaced the ovirt-engine like described in the docs.
I ejected the CD ISOs on every vm so i was able to delete the ISO_DOMAIN.
But i have still problems with my storage. Its a replicated glusterfs.
It looks healthy on the nodes itself. But somehow my ovirt-engine gets
confused. Can someone explain me what the actual error is?
Note: i only replaced the ovirt-engine host and delete the ISO_DOMAIN:
2014-11-11 18:32:37,832 ERROR
[org.ovirt.engine.core.vdsbroker.vdsbroker.HSMGetTaskStatusVDSCommand]
(org.ovirt.thread.pool-6-thread-39) [71891fe3] Failed in
HSMGetTaskStatusVDS method
2014-11-11 18:32:37,833 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.SpmStartVDSCommand]
(org.ovirt.thread.pool-6-thread-39) [71891fe3] spmStart polling ended:
taskId = 8c5fae2c-0ddb-41cd-ac54-c404c943e00f task status = finished
2014-11-11 18:32:37,834 ERROR
[org.ovirt.engine.core.vdsbroker.vdsbroker.SpmStartVDSCommand]
(org.ovirt.thread.pool-6-thread-39) [71891fe3] Start SPM Task failed -
result: cleanSuccess, message: VDSGenericException: VDSErrorException:
Failed to HSMGetTaskStatusVDS, error = Storage domain does not exist,
code = 358
2014-11-11 18:32:37,888 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.SpmStartVDSCommand]
(org.ovirt.thread.pool-6-thread-39) [71891fe3] spmStart polling ended,
spm status: Free
2014-11-11 18:32:37,889 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.HSMClearTaskVDSCommand]
(org.ovirt.thread.pool-6-thread-39) [71891fe3] START,
HSMClearTaskVDSCommand(HostName = ovirt-node01.foobar.net, HostId =
2e8cec66-23d7-4a5c-b6f3-9758d1d87f5c,
taskId=8c5fae2c-0ddb-41cd-ac54-c404c943e00f), log id: 547e26fd
2014-11-11 18:32:37,937 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.HSMClearTaskVDSCommand]
(org.ovirt.thread.pool-6-thread-39) [71891fe3] FINISH,
HSMClearTaskVDSCommand, log id: 547e26fd
2014-11-11 18:32:37,938 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.SpmStartVDSCommand]
(org.ovirt.thread.pool-6-thread-39) [71891fe3] FINISH,
SpmStartVDSCommand, return:
org.ovirt.engine.core.common.businessentities.SpmStatusResult@5027ed97,
log id: 461eb5b5
2014-11-11 18:32:37,941 INFO
[org.ovirt.engine.core.bll.storage.SetStoragePoolStatusCommand]
(org.ovirt.thread.pool-6-thread-39) [6d5f7d9d] Running command:
SetStoragePoolStatusCommand internal: true. Entities affected : ID:
b384b3da-02a6-44f3-a3f6-56751ce8c26d Type: StoragePool
2014-11-11 18:32:37,948 ERROR
[org.ovirt.engine.core.vdsbroker.irsbroker.IrsBrokerCommand]
(org.ovirt.thread.pool-6-thread-39) [6d5f7d9d]
IrsBroker::Failed::ActivateStorageDomainVDS due to:
IrsSpmStartFailedException: IRSGenericException: IRSErrorException:
SpmStart failed
2014-11-11 18:32:38,006 INFO
[org.ovirt.engine.core.vdsbroker.irsbroker.IrsBrokerCommand]
(org.ovirt.thread.pool-6-thread-39) [6d5f7d9d] Irs placed on server
2e8cec66-23d7-4a5c-b6f3-9758d1d87f5c failed. Proceed Failover
2014-11-11 18:32:38,044 INFO
[org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListVDSCommand]
(DefaultQuartzScheduler_Worker-29) START,
GlusterVolumesListVDSCommand(HostName = ovirt-node01.foobar.net,
HostId = 2e8cec66-23d7-4a5c-b6f3-9758d1d87f5c), log id: 7a110756
2014-11-11 18:32:38,045 INFO
[org.ovirt.engine.core.vdsbroker.irsbroker.IrsBrokerCommand]
(org.ovirt.thread.pool-6-thread-39) [6d5f7d9d]
hostFromVds::selectedVds - ovirt-node02.foobar.net, spmStatus Free,
storage pool HP_Proliant_DL180G6
2014-11-11 18:32:38,048 INFO
[org.ovirt.engine.core.vdsbroker.irsbroker.IrsBrokerCommand]
(org.ovirt.thread.pool-6-thread-39) [6d5f7d9d] starting spm on vds
ovirt-node02.foobar.net, storage pool HP_Proliant_DL180G6, prevId -1,
LVER -1
2014-11-11 18:32:38,050 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.SpmStartVDSCommand]
(org.ovirt.thread.pool-6-thread-39) [6d5f7d9d] START,
SpmStartVDSCommand(HostName = ovirt-node02.foobar.net, HostId =
6948da12-0b8a-4b6d-a9af-162e6c25dad3, storagePoolId =
b384b3da-02a6-44f3-a3f6-56751ce8c26d, prevId=-1, prevLVER=-1,
storagePoolFormatType=V3, recoveryMode=Manual, SCSIFencing=false), log
id: 1a6ccb9c
2014-11-11 18:32:38,108 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.SpmStartVDSCommand]
(org.ovirt.thread.pool-6-thread-39) [6d5f7d9d] spmStart polling
started: taskId = 78d31638-70a5-46aa-89e7-1d1e8126bdba
2014-11-11 18:32:38,193 INFO
[org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListVDSCommand]
(DefaultQuartzScheduler_Worker-29) FINISH,
GlusterVolumesListVDSCommand, return:
{d46619e9-9368-4e82-bf3a-a2377b6e85e4=org.ovirt.engine.core.common.businessentities.gluster.GlusterVolumeEntity@9746ef53},
log id: 7a110756
2014-11-11 18:32:38,352 INFO
[org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListVDSCommand]
(DefaultQuartzScheduler_Worker-29) START,
GlusterVolumesListVDSCommand(HostName = ovirt-node04.foobar.net,
HostId = 073c24e1-003f-412a-be56-0c41a435829a), log id: 2f25d56e
2014-11-11 18:32:38,433 INFO
[org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListVDSCommand]
(DefaultQuartzSchedule
[ovirt-users] Get involved in oVirt integration! November edition
Hi, have you got some free time and do you want to get involved in oVirt integration? Here are a couple of bugs you can hopefully fix in less that one day or you can just try to reproduce providing info: Bug 1080823 - [RFE] make override of iptables configurable when using hosted-engine Bug 1065350 - hosted-engine should prompt a question at the user when the host was already a host in the engine Bug 1059952 - hosted-engine --deploy (additional host) will fail if the engine is not using the default self-signed CA Bug 1073421 - [RFE] allow additional parameter for engine-backup to omit audit_log data You don't have programming skills but you want to contribute? Here are some bugs you can take care of, also without writing a line of code: Bug ID Status Whiteboard Summary 1118354 NEW integration [RFE] Automated testing should prevent leaking sensitive data 1120585 NEW integration update image uploader documentation 1120586 NEW integration update iso uploader documentation 1120588 NEW integration update log collector documentation 1083104 NEW integration engine-setup --offline does not update versionlock 1074301 NEW infra [RFE] ovirt-shell has no man page Do you prefer to write on the wiki? Bug ID Status Summary 108 NEW Hosted Engine documentation has several errors 105 NEW Migrate to Hosted Engine How-To does not state all pre-reqs 1054303 NEW Dead links in "Quick Start Guide" 1125933 NEW Provide a way to change /ca.crt for non-self-signed certs 918 NEW Suggest a repository for installing hosts with an external network provider 1127123 ASSIGNEDcannot figure out how to use show statistic 1142623 NEW Feature page: AAA 3.5 needs to be updated 1142649 POSTFeature page: AdvancedForemanIntegration needs to be updated 1142671 POSTFeature page: CommandCoordinator needs to be updated 1142616 NEW Feature page: Gluster Volume Capacity needs to be updated 1142803 NEW Feature page: Generic Node Registration needs to be updated 1142639 NEW Feature page: Features/Design/JsonRpc needs to be updated 1142822 NEW Feature page: Support blkio SLA features needs to be updated 1142846 NEW Feature page: oVirt Scheduler API needs to be updated 1142806 NEW Feature page: Node Hosted Engine needs to be updated 1142814 NEW Feature page: oVirt Appliance needs to be updated 1142662 NEW Feature page: PMHealthCheck needs to be updated 1142665 NEW Feature page: Custom Fencing needs to be updated 1142652 NEW Feature page: DetailedHostPMProxyPreferences needs to be updated 1142783 NEW Feature page: Separate DWH Host needs to be updated 066 NEW oVirt Hardening Guide 1074545 NEW Error in API documentation: Create API object in python sdk Is this the first time you try to contribute to oVirt project? You can start from here [1][2]! Don't know gerrit very well? You can find some more docs here [3]. Any other question about development? Feel free to ask on de...@ovirt.org or on irc channel[4]. [1] http://www.ovirt.org/Develop [2] http://www.ovirt.org/Working_with_oVirt_Gerrit [3] https://gerrit-review.googlesource.com/Documentation [4] http://www.ovirt.org/Community -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] http://www.ovirt.org/Features/ForemanIntegration
On 11.11.2014 16:09, ybronhei wrote: > On 11/11/2014 03:25 PM, Daniel Helgenberger wrote: >> >> >> On 11.11.2014 13:46, ybronhei wrote: >>> Hey Daniel, >>> Thanks for your comments. >>> First, I do mention the requirement for having ovirt_provision_plugin >>> installed in bullet 2: >>> """Add oVirt Provision Plugin: "yum install >>> ruby193-rubygem-ovirt_provision_plugin" \ "foreman-installer >>> --enable-foreman-plugin-ovirt-provision" (Not available yet) >>> """ >> Indeed, I read that. My reasoning at this point it might be too late in >> the text. Users (me included) already have tried this at this point >> using the pictured guide and failing because of the missing provider. >> >> This is the point witch was entirely unclear for me in my first attempt >> and it took me a while to find out. >> >> While the discovery plugin is needed (only) for Bare-Metal Provisioning, >> the ovirt provider is always needed for the integration to succeed. >> >> I did think about a hint early on describing the workflow briefly in the >> detailed description section: >> - Make sure Foreman is running at version X >> - Install RPMs in Foreman (see Bare-Metal Provisioning) >> - Go to engine, "Adding foreman provider" > I don't see why the current way we arrange the page is misleading. Sorry if this is unclear. But: For the "Test" button in "Add external provider" in Engine GUI to work, one *needs* do this on the Foreman host: # yum install ruby193-rubygem-ovirt_provision_plugin If this this assumption is true (it was for me reproducible) Foreman/oVirt communication will fail. Therefore I am still convinced it is reasonable to put this as the first step before ever trying to add the provider in oVirt.* The other things, like bare metal prov. and so on are optional. Installing the oVirt - provider on the Foreman host is not. > > We have under "Detailed Description" 3 levels which have different > prerequisites - > Adding installed Foreman hosts as oVirt hosts - which just requires > foreman setup, To make this clear, this is not correct since the default foreman setup does not have the oVirt provider module installed. There are some use cases where Foreman is added because of oVirt, and some will have Foreman already runningin their infra. In this case, foreman-installer was already run. * At least I was struggling with this requirement. Truth be told, Foreman was one point on a (very long) check list of mine; so I might not have paid proper attention to the details. OTOH the document suggested a strait forward approach with nice details and icons on how to do it oVirt. For instance, when I got to the section "Bare Metal Provisioning" I looked briefly over the requirements and decided to do this later on. Wrong here, since there is what I need to get it running in the first place! The other issue, having two different (one obsolete) ForemanIntegration docs, is solved now. > Bare-Metal Provisioning - which requires many things. starts with the > ovirt plugin, discovery plugin, configuration of hostgroups > computeresource medias and ends with setting the provisioning templates > accordingly for node installation. > > and last - Future Plans: VM provisioning which still in declaration phase. >> >> >>> >>> next foreman build foreman-installer will include the >>> --enable-foreman-plugin-ovirt-provision option which will make it >>> easier. its already merged. >> This is great to know! >> >>> >>> Second, about the openjdk issue, I don't think it worth to mention. I'll >>> add to the "Current Status" section that the integration is supported >>> over rhel6.6 and above. >> This will do here. >> >>> >>> Yaniv Bronhaim. >>> >>> On 11/11/2014 02:38 PM, Daniel Helgenberger wrote: Hello Yaniv, thank you! On 10.11.2014 10:04, ybronhei wrote: > For those who interested, I merged the pages ForemanIntegration and > AdvancedForemanIntegration to ease the search. > > The page includes full description about the current integration we have > with foreman [aka satellite\katello], the future plans, how to setup > environment for testing and production and more illustrations to make it > easier to follow > > feel free to comment about that (directly to me or to the list) and you > more than welcome to try that at home :) I think there might be still the issue I ran into: A prerequisite to adding Foreman external provider in oVirt is (at least for me) that Foreman has *ruby193-rubygem-ovirt_provision_plugin* rpm installed. Otherwise the test will fail with: "Failed with error PROVIDER_FAILURE and code 5050" Sp, on the foreman host one needs to do: yum install ruby193-rubygem-ovirt_provision_plugin Also, please note there is an issue users might run into at this step, so it may be worth noting. Foreman integration will fail altogether on Engines running =< El6.5 because of an too old jdk versi
Re: [ovirt-users] http://www.ovirt.org/Features/ForemanIntegration
On 11/11/2014 03:25 PM, Daniel Helgenberger wrote: On 11.11.2014 13:46, ybronhei wrote: Hey Daniel, Thanks for your comments. First, I do mention the requirement for having ovirt_provision_plugin installed in bullet 2: """Add oVirt Provision Plugin: "yum install ruby193-rubygem-ovirt_provision_plugin" \ "foreman-installer --enable-foreman-plugin-ovirt-provision" (Not available yet) """ Indeed, I read that. My reasoning at this point it might be too late in the text. Users (me included) already have tried this at this point using the pictured guide and failing because of the missing provider. This is the point witch was entirely unclear for me in my first attempt and it took me a while to find out. While the discovery plugin is needed (only) for Bare-Metal Provisioning, the ovirt provider is always needed for the integration to succeed. I did think about a hint early on describing the workflow briefly in the detailed description section: - Make sure Foreman is running at version X - Install RPMs in Foreman (see Bare-Metal Provisioning) - Go to engine, "Adding foreman provider" I don't see why the current way we arrange the page is misleading. We have under "Detailed Description" 3 levels which have different prerequisites - Adding installed Foreman hosts as oVirt hosts - which just requires foreman setup, Bare-Metal Provisioning - which requires many things. starts with the ovirt plugin, discovery plugin, configuration of hostgroups computeresource medias and ends with setting the provisioning templates accordingly for node installation. and last - Future Plans: VM provisioning which still in declaration phase. next foreman build foreman-installer will include the --enable-foreman-plugin-ovirt-provision option which will make it easier. its already merged. This is great to know! Second, about the openjdk issue, I don't think it worth to mention. I'll add to the "Current Status" section that the integration is supported over rhel6.6 and above. This will do here. Yaniv Bronhaim. On 11/11/2014 02:38 PM, Daniel Helgenberger wrote: Hello Yaniv, thank you! On 10.11.2014 10:04, ybronhei wrote: For those who interested, I merged the pages ForemanIntegration and AdvancedForemanIntegration to ease the search. The page includes full description about the current integration we have with foreman [aka satellite\katello], the future plans, how to setup environment for testing and production and more illustrations to make it easier to follow feel free to comment about that (directly to me or to the list) and you more than welcome to try that at home :) I think there might be still the issue I ran into: A prerequisite to adding Foreman external provider in oVirt is (at least for me) that Foreman has *ruby193-rubygem-ovirt_provision_plugin* rpm installed. Otherwise the test will fail with: "Failed with error PROVIDER_FAILURE and code 5050" Sp, on the foreman host one needs to do: yum install ruby193-rubygem-ovirt_provision_plugin Also, please note there is an issue users might run into at this step, so it may be worth noting. Foreman integration will fail altogether on Engines running =< El6.5 because of an too old jdk version not supporting DH keys larger then 1024 byte [1]. This is not an issue in oVirt and will never be resolved. Luckily, upgrading to the latest openjdk (java-1.7.0-openjdk-1.7.0.71-2.5.3.1.el6.x86_64) solves the issue (on the ENGINE!) [1] https://bugzilla.redhat.com/show_bug.cgi?id=1157749 Thanks -- Yaniv Bronhaim. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Ovirt VM Performance abd CPU times
Ok, so we found a "solution" that I thought I'll share in case this thread pops up in a future search. The problem was that our Redhat 5.x guests still run with a kernel that lacks the "tickeless" feature, meaning that they are poking the host a 1000 times per second even if they haven't anything to do. Disabling hyperthreading and most importantly, adding the parameter "divider=10" to the kernel boot line in grub does indeed lower the cpu utilization in the hosts almost to 0% when idling. In our case we use the command sudo /sbin/grubby --update-kernel=ALL --args="divider=10" To upgrade the /boot/grub/grub.conf file and then we restart the vm. Thank you everyone for the help. Xavier On Mon, Nov 10, 2014 at 8:32 AM, Xavier Naveira wrote: > We tried a minimal installation from CD of RedHat 5.10 and it is the same. > > This should be fairly easy to reproduce: > > - Install a RedHat 6.5 hypervisor > - Install a RedHat 5.10 guest in it > - Enjoy your overused CPU > > Is there someone with a similar setup out there? > > Xavier > > On Fri, Nov 7, 2014 at 12:30 PM, Gianluca Cecchi < > gianluca.cec...@gmail.com> wrote: > >> On Fri, Nov 7, 2014 at 10:48 AM, Xavier Naveira >> wrote: >> >>> Hi, >>> >>> We have installed and added a new hypervisor into the ovirt cluster but >>> this time with disabled HT. >>> >>> I migrated a RedHat 5.10 machine to it and immediately the qemu-kvm >>> process running the vm (freshly installed, just basic packages) began to >>> consume 20-40% CPU as showed running top on the hypervisor. >>> >>> Now that I have a hypervisor to run tests in, what would you suggest the >>> next step is? >>> >>> Thank you. >>> >>> Xavier >>> >>> >>> >> If I remember correctly you had to test plain Qemu/KVM on CentOS 6.5 and >> see if the difference is made by oVirt itself or by the OS changed from 5.x >> to 6.y... >> And also compare command line (eventually both in 5.x and 6.x) between >> plain Qemu/KVM and oVirt spawned VMs >> Gianluca >> > > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] http://www.ovirt.org/Features/ForemanIntegration
On 11.11.2014 13:46, ybronhei wrote: > Hey Daniel, > Thanks for your comments. > First, I do mention the requirement for having ovirt_provision_plugin > installed in bullet 2: > """Add oVirt Provision Plugin: "yum install > ruby193-rubygem-ovirt_provision_plugin" \ "foreman-installer > --enable-foreman-plugin-ovirt-provision" (Not available yet) > """ Indeed, I read that. My reasoning at this point it might be too late in the text. Users (me included) already have tried this at this point using the pictured guide and failing because of the missing provider. This is the point witch was entirely unclear for me in my first attempt and it took me a while to find out. While the discovery plugin is needed (only) for Bare-Metal Provisioning, the ovirt provider is always needed for the integration to succeed. I did think about a hint early on describing the workflow briefly in the detailed description section: - Make sure Foreman is running at version X - Install RPMs in Foreman (see Bare-Metal Provisioning) - Go to engine, "Adding foreman provider" > > next foreman build foreman-installer will include the > --enable-foreman-plugin-ovirt-provision option which will make it > easier. its already merged. This is great to know! > > Second, about the openjdk issue, I don't think it worth to mention. I'll > add to the "Current Status" section that the integration is supported > over rhel6.6 and above. This will do here. > > Yaniv Bronhaim. > > On 11/11/2014 02:38 PM, Daniel Helgenberger wrote: >> Hello Yaniv, >> >> thank you! >> >> On 10.11.2014 10:04, ybronhei wrote: >>> For those who interested, I merged the pages ForemanIntegration and >>> AdvancedForemanIntegration to ease the search. >>> >>> The page includes full description about the current integration we have >>> with foreman [aka satellite\katello], the future plans, how to setup >>> environment for testing and production and more illustrations to make it >>> easier to follow >>> >>> feel free to comment about that (directly to me or to the list) and you >>> more than welcome to try that at home :) >> I think there might be still the issue I ran into: >> >> A prerequisite to adding Foreman external provider in oVirt is (at least >> for me) that Foreman has *ruby193-rubygem-ovirt_provision_plugin* rpm >> installed. Otherwise the test will fail with: >> "Failed with error PROVIDER_FAILURE and code 5050" >> >> Sp, on the foreman host one needs to do: >> yum install ruby193-rubygem-ovirt_provision_plugin >> >> Also, please note there is an issue users might run into at this step, >> so it may be worth noting. >> Foreman integration will fail altogether on Engines running =< El6.5 >> because of an too old jdk version not supporting DH keys larger then >> 1024 byte [1]. >> This is not an issue in oVirt and will never be resolved. Luckily, >> upgrading to the latest openjdk >> (java-1.7.0-openjdk-1.7.0.71-2.5.3.1.el6.x86_64) solves the issue (on >> the ENGINE!) >> >> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1157749 >>> >>> Thanks >>> >> > > -- Daniel Helgenberger m box bewegtbild GmbH P: +49/30/2408781-22 F: +49/30/2408781-10 ACKERSTR. 19 D-10115 BERLIN www.m-box.de www.monkeymen.tv Geschäftsführer: Martin Retschitzegger / Michaela Göllner Handeslregister: Amtsgericht Charlottenburg / HRB 112767 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] http://www.ovirt.org/Features/ForemanIntegration
Hey Daniel, Thanks for your comments. First, I do mention the requirement for having ovirt_provision_plugin installed in bullet 2: """Add oVirt Provision Plugin: "yum install ruby193-rubygem-ovirt_provision_plugin" \ "foreman-installer --enable-foreman-plugin-ovirt-provision" (Not available yet) """ next foreman build foreman-installer will include the --enable-foreman-plugin-ovirt-provision option which will make it easier. its already merged. Second, about the openjdk issue, I don't think it worth to mention. I'll add to the "Current Status" section that the integration is supported over rhel6.6 and above. Yaniv Bronhaim. On 11/11/2014 02:38 PM, Daniel Helgenberger wrote: Hello Yaniv, thank you! On 10.11.2014 10:04, ybronhei wrote: For those who interested, I merged the pages ForemanIntegration and AdvancedForemanIntegration to ease the search. The page includes full description about the current integration we have with foreman [aka satellite\katello], the future plans, how to setup environment for testing and production and more illustrations to make it easier to follow feel free to comment about that (directly to me or to the list) and you more than welcome to try that at home :) I think there might be still the issue I ran into: A prerequisite to adding Foreman external provider in oVirt is (at least for me) that Foreman has *ruby193-rubygem-ovirt_provision_plugin* rpm installed. Otherwise the test will fail with: "Failed with error PROVIDER_FAILURE and code 5050" Sp, on the foreman host one needs to do: yum install ruby193-rubygem-ovirt_provision_plugin Also, please note there is an issue users might run into at this step, so it may be worth noting. Foreman integration will fail altogether on Engines running =< El6.5 because of an too old jdk version not supporting DH keys larger then 1024 byte [1]. This is not an issue in oVirt and will never be resolved. Luckily, upgrading to the latest openjdk (java-1.7.0-openjdk-1.7.0.71-2.5.3.1.el6.x86_64) solves the issue (on the ENGINE!) [1] https://bugzilla.redhat.com/show_bug.cgi?id=1157749 Thanks -- Yaniv Bronhaim. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] http://www.ovirt.org/Features/ForemanIntegration
Hello Yaniv, thank you! On 10.11.2014 10:04, ybronhei wrote: > For those who interested, I merged the pages ForemanIntegration and > AdvancedForemanIntegration to ease the search. > > The page includes full description about the current integration we have > with foreman [aka satellite\katello], the future plans, how to setup > environment for testing and production and more illustrations to make it > easier to follow > > feel free to comment about that (directly to me or to the list) and you > more than welcome to try that at home :) I think there might be still the issue I ran into: A prerequisite to adding Foreman external provider in oVirt is (at least for me) that Foreman has *ruby193-rubygem-ovirt_provision_plugin* rpm installed. Otherwise the test will fail with: "Failed with error PROVIDER_FAILURE and code 5050" Sp, on the foreman host one needs to do: yum install ruby193-rubygem-ovirt_provision_plugin Also, please note there is an issue users might run into at this step, so it may be worth noting. Foreman integration will fail altogether on Engines running =< El6.5 because of an too old jdk version not supporting DH keys larger then 1024 byte [1]. This is not an issue in oVirt and will never be resolved. Luckily, upgrading to the latest openjdk (java-1.7.0-openjdk-1.7.0.71-2.5.3.1.el6.x86_64) solves the issue (on the ENGINE!) [1] https://bugzilla.redhat.com/show_bug.cgi?id=1157749 > > Thanks > -- Daniel Helgenberger m box bewegtbild GmbH P: +49/30/2408781-22 F: +49/30/2408781-10 ACKERSTR. 19 D-10115 BERLIN www.m-box.de www.monkeymen.tv Geschäftsführer: Martin Retschitzegger / Michaela Göllner Handeslregister: Amtsgericht Charlottenburg / HRB 112767 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Upgrade to 3.5 issues, vm cannot be started
On 11/11/14 12:37, Gianluca Cecchi wrote: > Gilad, > from your latest answer to the same referred thread, here: > http://lists.ovirt.org/pipermail/users/2014-September/027891.html > I sorted out that it was a problem of mine, coming from a 3.5-rc2 to > 3.5-rc3 now it actually seems that it is indeed a regression from 3.4 > to 3.5. > So I propose to consider something managing this for 3.5.1 so that a user > upgrading from 3.4.x to 3.5.1 will not get this kind of nasty problem. this is already targeted for 3.5.1 and marked as a blocker: https://bugzilla.redhat.com/show_bug.cgi?id=1157149 But it's still not backported to 3.5 branch HTH -- Mit freundlichen Grüßen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Upgrade to 3.5 issues, vm cannot be started
On Tue, Nov 11, 2014 at 11:30 AM, James James wrote: > It 's a NUMA problem. > > It 's like : > http://lists.ovirt.org/pipermail/users/2014-September/027787.html > > http://lists.ovirt.org/pipermail/users/2014-September/027891.html > > Is it possible to change the default NUMA mode to interleave in GUI ? > > Gilad, from your latest answer to the same referred thread, here: http://lists.ovirt.org/pipermail/users/2014-September/027891.html I sorted out that it was a problem of mine, coming from a 3.5-rc2 to 3.5-rc3 now it actually seems that it is indeed a regression from 3.4 to 3.5. So I propose to consider something managing this for 3.5.1 so that a user upgrading from 3.4.x to 3.5.1 will not get this kind of nasty problem. Gianluca ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] USB redirect
On Nov 11, 2014, at 11:08 , Juan Jose wrote: > Thank you very much Michal, If I have checked Device administrator in my > Windows 7 VM and as you can see in the attached image, the USB device is > correctly installed. But when I click "File" in remote-viewer "USB device > selection" appears in grey and I can't select any USB device. > > Is there any other requirement to be able redirect USB devices?, Is it > necessary to install usbclerk in Windows clients to redirect USB to the > Windows guest? usbredir drivers yes, you need them, they should be on the guest tools iso Thanks, michal > > Many thanks in advanced, > > Juanjo. > > On Tue, Nov 11, 2014 at 8:23 AM, Michal Skrivanek > wrote: > > On Nov 10, 2014, at 17:54 , Juan Jose wrote: > > > Hello everybody, > > > > I have an oVirt 3.4 deployment and I have some Windows 7 Enterprise 32 > > bits guests. I can't redirect USB from a Windows 7 client. I'm using remote > > - viewer as console. Also I have observed something wrong in my > > administration portal. The oVirt documentation says that I have to select > > Native USB mode in console properties in VM configuration > > yes, that's the only supported way > you should see the USB controller in devices > > > but after select this mode, it doesn't remain. If I check this value in > > console configuration again I can see disabled, native mode value have been > > changed. > > there used to be such issue in 3.4..it is fixed in 3.5 already. > It should be a UI problem only… > > Thanks, > michal > > > > > Is there someone have had this problem?, and how I can solve it?, is it > > necessary to install in Windows clients us clerk software? > > > > Many thanks in advanced. > > > > Juanjo. > > ___ > > Users mailing list > > Users@ovirt.org > > http://lists.ovirt.org/mailman/listinfo/users > > > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Upgrade to 3.5 issues, vm cannot be started
It 's a NUMA problem. It 's like : http://lists.ovirt.org/pipermail/users/2014-September/027787.html http://lists.ovirt.org/pipermail/users/2014-September/027891.html Is it possible to change the default NUMA mode to interleave in GUI ? 2014-11-11 10:58 GMT+01:00 James James : > Hi, > > today I've decided to upgrade my 3.4 Ovirt cluster to 3.5/ > > The engine migration was OK. Everything was good .. after I want upgraded > the node .. I've installed the rpm on the node and follow : > http://www.ovirt.org/OVirt_3.5_Release_Notes#Install_.2F_Upgrade_from_Previous_Versions > . > > Now my vms cannot be started. I've got this error message : > > 2014-11-11 10:49:37,305 WARN [org.ovirt.engine.core.bll.RunVmCommand] > (org.ovirt.thread.pool-8-thread-13) CanDoAction of action RunVm failed. > Reasons:VAR__ACTION__RUN,VAR__TYPE__VM,VAR__ACTION__RUN,VAR__TYPE__VM,VAR__ACTION__RUN,VAR__TYPE__VM,VAR__ACTION__RUN,VAR__TYPE__VM,SCHEDULING_NO_HOSTS > 2014-11-11 10:49:37,307 INFO [org.ovirt.engine.core.bll.RunVmCommand] > (org.ovirt.thread.pool-8-thread-13) Lock freed to object EngineLock > [exclusiveLocks= key: 0fdea856-9aec-4300-8d88-4cfd330cf4ff value: VM > , sharedLocks= ] > > There is a full log in attachment .. > > Any help will be appreciated ... > > James > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] Jiří Moskovčák změnil čas události Ovirt - Hosted Engine iSCSI support (deep dive)
Jiří Moskovčák změnil čas události na st 12. listopadu, 14:00 SEČ Toto oznámení bylo odesláno na adresu users@ovirt.org; Chcete-li aktualizovat svou adresu, přejděte na nastavení doručování oznámení: https://plus.google.com/_/notifications/ngemlink?&emid=COCoq96I8sECFRKW3Aod_xYAjA&path=%2Fsettings%2Fplus&dt=1415692285625&uob=14 Ve správě odběrů můžete nastavit, jaké e-maily z Google+ chcete dostávat: https://plus.google.com/_/notifications/ngemlink?&emid=COCoq96I8sECFRKW3Aod_xYAjA&path=%2Fsettings%2Fplus&dt=1415692285625&uob=14 Google Inc., 1600 Amphitheatre Pkwy, Mountain View, CA 94043 USA ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] USB redirect
Thank you very much Michal, If I have checked Device administrator in my Windows 7 VM and as you can see in the attached image, the USB device is correctly installed. But when I click "File" in remote-viewer "USB device selection" appears in grey and I can't select any USB device. Is there any other requirement to be able redirect USB devices?, Is it necessary to install usbclerk in Windows clients to redirect USB to the Windows guest? Many thanks in advanced, Juanjo. On Tue, Nov 11, 2014 at 8:23 AM, Michal Skrivanek < michal.skriva...@redhat.com> wrote: > > On Nov 10, 2014, at 17:54 , Juan Jose wrote: > > > Hello everybody, > > > > I have an oVirt 3.4 deployment and I have some Windows 7 Enterprise 32 > bits guests. I can't redirect USB from a Windows 7 client. I'm using remote > - viewer as console. Also I have observed something wrong in my > administration portal. The oVirt documentation says that I have to select > Native USB mode in console properties in VM configuration > > yes, that's the only supported way > you should see the USB controller in devices > > > but after select this mode, it doesn't remain. If I check this value in > console configuration again I can see disabled, native mode value have been > changed. > > there used to be such issue in 3.4..it is fixed in 3.5 already. > It should be a UI problem only… > > Thanks, > michal > > > > > Is there someone have had this problem?, and how I can solve it?, is it > necessary to install in Windows clients us clerk software? > > > > Many thanks in advanced. > > > > Juanjo. > > ___ > > Users mailing list > > Users@ovirt.org > > http://lists.ovirt.org/mailman/listinfo/users > > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] Cumulative VM network usage
Hello,
The need to monitor cumulative VM network usage has come up several
times in the past; while this should be handled as part of
(https://bugzilla.redhat.com/show_bug.cgi?id=1063343), in the mean time
I've written a small Python script that monitors those statistics,
attached here.
The script polls the engine via RESTful API periodically and dumps the
up-to-date total usage into a file. The output is a multi-level
map/dictionary in JSON format, where:
* The top level keys are VM names.
* Under each VM, the next level keys are vNIC names.
* Under each vNIC, there are keys for total 'rx' (received) and 'tx'
(transmitted), where the values are in Bytes.
The script is built to run forever. It may be stopped at any time, but
while it's not running VM network usage data will "be lost". When it's
re-run, it'll go back to accumulating data on top of its previous data.
A few disclaimers:
* I haven't tested this with any edge cases (engine service dies, etc.).
* Tested this with tens of VMs, not sure it'll work fine with hundreds.
* The PERIOD_TIME (polling interval) should be set so that it matches
both the engine's and vdsm's polling interval (see comments inside the
script), otherwise data will be either lost or counted multiple times.
>From 3.4 onwards, default configuration should be fine with 15 seconds.
* The precision of traffic measurement on a NIC is 0.1% of the
interface's speed over each PERIOD_TIME interval. For example, on a
1Gbps vNIC, when PERIOD_TIME = 15s, data will only be measured in 15Mb
(~2MB) quanta. Specifically what this means is, that in this example,
any traffic smaller than 2MB over a 15-second period would be negligible
and wouldn't be recorded.
Knock yourselves out :)
from json import load,dump
from genericpath import exists
from ovirtsdk.api import API
from threading import Thread
from time import sleep, time
PERIOD_TIME = 15 # time in seconds between measurements - for data integrity's sake, should match both the engine polling interval (determined by configuration values: NumberVmRefreshesBeforeSave * VdsRefreshRate) and the vdsm polling interval (vm_sample_net_interval in /etc/vdsm/vdsm.conf)
ENGINE_URL = 'http://localhost:8080/api'
USERNAME = 'admin@internal'
PASSWORD = 'foo'
PATHNAME = 'traffic.txt'
RX_ENTRY = 'rx'
TX_ENTRY = 'tx'
api = API(url=ENGINE_URL, username=USERNAME, password=PASSWORD)
def deserialize():
if exists(PATHNAME):
f = open(PATHNAME, 'r+')
traffic = load(f)
f.close()
else:
traffic = {}
return traffic
def serialize(traffic):
f = open(PATHNAME, 'w')
dump(traffic, f)
f.close()
# returns an up-to-date cumulative NIC network usage
# nicEntry := {'rx' : totalRxInBytes, 'tx' : totalTxInBytes}
def updateNic(nic, nicEntry):
rx = nicEntry[RX_ENTRY] if (RX_ENTRY in nicEntry) else 0
tx = nicEntry[TX_ENTRY] if (TX_ENTRY in nicEntry) else 0
for statistic in nic.statistics.list():
if statistic.get_name() == 'data.current.rx':
rx += PERIOD_TIME * statistic.get_values().get_value().pop().get_datum()
elif statistic.get_name() == 'data.current.tx':
tx += PERIOD_TIME * statistic.get_values().get_value().pop().get_datum()
nicEntry[RX_ENTRY] = rx
nicEntry[TX_ENTRY] = tx
# returns the up-to-date cumulative network usage for all the NICs of a VM
# vmEntry := {nicName1 : nicEntry, nicName2 : nicEntry, ...}
# see nicEntry format in updateNic()
def updateVm(vm, vmEntry):
for nic in vm.nics.list():
nicName = nic.get_name()
nicEntry = {}
if nicName in vmEntry:
nicEntry = vmEntry[nicName]
updateNic(nic, nicEntry)
vmEntry[nicName] = nicEntry
# returns the up-to-date cumulative network usage for all the NICs of all the VMs in the deployment
# traffic := {vmName1 : vmEntry, vmName2 : vmEntry, ...}
# see vmEntry format in updateVm
def updateAllVms():
traffic = deserialize()
for vm in api.vms.list():
vmName = vm.get_name()
vmEntry = {}
if vmName in traffic:
vmEntry = traffic[vmName]
updateVm(vm, vmEntry)
traffic[vmName] = vmEntry
serialize(traffic)
while True:
reference = time()
thread = Thread(target=updateAllVms)
thread.run()
overhead = time() - reference
sleep(PERIOD_TIME - overhead) # for some reason initializing the thread takes non-negligible amount of time in Python, correct for it
api.disconnect()
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] Upgrade to 3.5 issues, vm cannot be started
Hi,
today I've decided to upgrade my 3.4 Ovirt cluster to 3.5/
The engine migration was OK. Everything was good .. after I want upgraded
the node .. I've installed the rpm on the node and follow :
http://www.ovirt.org/OVirt_3.5_Release_Notes#Install_.2F_Upgrade_from_Previous_Versions
.
Now my vms cannot be started. I've got this error message :
2014-11-11 10:49:37,305 WARN [org.ovirt.engine.core.bll.RunVmCommand]
(org.ovirt.thread.pool-8-thread-13) CanDoAction of action RunVm failed.
Reasons:VAR__ACTION__RUN,VAR__TYPE__VM,VAR__ACTION__RUN,VAR__TYPE__VM,VAR__ACTION__RUN,VAR__TYPE__VM,VAR__ACTION__RUN,VAR__TYPE__VM,SCHEDULING_NO_HOSTS
2014-11-11 10:49:37,307 INFO [org.ovirt.engine.core.bll.RunVmCommand]
(org.ovirt.thread.pool-8-thread-13) Lock freed to object EngineLock
[exclusiveLocks= key: 0fdea856-9aec-4300-8d88-4cfd330cf4ff value: VM
, sharedLocks= ]
There is a full log in attachment ..
Any help will be appreciated ...
James
2014-11-11 10:55:21,095 INFO [org.ovirt.engine.core.bll.RunVmCommand]
(ajp--127.0.0.1-8702-2) [bab78b2] Lock Acquired to object EngineLock
[exclusiveLocks= key: 0fdea856-9aec-4300-8d88-4cfd330cf4ff value: VM
, sharedLocks= ]
2014-11-11 10:55:21,150 INFO
[org.ovirt.engine.core.vdsbroker.IsVmDuringInitiatingVDSCommand]
(ajp--127.0.0.1-8702-2) [bab78b2] START, IsVmDuringInitiatingVDSCommand( vmId =
0fdea856-9aec-4300-8d88-4cfd330cf4ff), log id: 37b8c678
2014-11-11 10:55:21,151 INFO
[org.ovirt.engine.core.vdsbroker.IsVmDuringInitiatingVDSCommand]
(ajp--127.0.0.1-8702-2) [bab78b2] FINISH, IsVmDuringInitiatingVDSCommand,
return: false, log id: 37b8c678
2014-11-11 10:55:21,254 INFO [org.ovirt.engine.core.bll.RunVmCommand]
(org.ovirt.thread.pool-8-thread-7) [bab78b2] Running command: RunVmCommand
internal: false. Entities affected : ID: 0fdea856-9aec-4300-8d88-4cfd330cf4ff
Type: VMAction group VM_BASIC_OPERATIONS with role type USER
2014-11-11 10:55:21,352 INFO
[org.ovirt.engine.core.bll.scheduling.policyunits.HaReservationWeightPolicyUnit]
(org.ovirt.thread.pool-8-thread-7) [bab78b2] Started HA reservation scoring
method
2014-11-11 10:55:21,404 INFO
[org.ovirt.engine.core.vdsbroker.UpdateVmDynamicDataVDSCommand]
(org.ovirt.thread.pool-8-thread-7) [bab78b2] START,
UpdateVmDynamicDataVDSCommand(HostName = ovirt-node2, HostId =
051acfd2-076f-498d-adf9-4c6692f65d50,
vmDynamic=org.ovirt.engine.core.common.businessentities.VmDynamic@51e309c6),
log id: 5186ff6
2014-11-11 10:55:21,407 INFO
[org.ovirt.engine.core.vdsbroker.UpdateVmDynamicDataVDSCommand]
(org.ovirt.thread.pool-8-thread-7) [bab78b2] FINISH,
UpdateVmDynamicDataVDSCommand, log id: 5186ff6
2014-11-11 10:55:21,438 INFO
[org.ovirt.engine.core.vdsbroker.CreateVmVDSCommand]
(org.ovirt.thread.pool-8-thread-7) [bab78b2] START, CreateVmVDSCommand(HostName
= ovirt-node2, HostId = 051acfd2-076f-498d-adf9-4c6692f65d50,
vmId=0fdea856-9aec-4300-8d88-4cfd330cf4ff, vm=VM [puppetdb]), log id: 3685dd2b
2014-11-11 10:55:21,467 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.CreateVDSCommand]
(org.ovirt.thread.pool-8-thread-7) [bab78b2] START, CreateVDSCommand(HostName =
ovirt-node2, HostId = 051acfd2-076f-498d-adf9-4c6692f65d50,
vmId=0fdea856-9aec-4300-8d88-4cfd330cf4ff, vm=VM [puppetdb]), log id: 5d3a82e5
2014-11-11 10:55:21,493 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.CreateVDSCommand]
(org.ovirt.thread.pool-8-thread-7) [bab78b2]
org.ovirt.engine.core.vdsbroker.vdsbroker.CreateVDSCommand
kvmEnable=true,keyboardLayout=en-us,nice=0,pitReinjection=false,displayNetwork=ovirtmgmt,copyPasteEnable=true,timeOffset=0,transparentHugePages=true,vmId=0fdea856-9aec-4300-8d88-4cfd330cf4ff,acpiEnable=true,custom={device_2837bb81-e830-4014-9cba-b95e76c8785bdevice_87f78a45-040c-4534-a19a-e7ba97f3721fdevice_b97a2abb-a9a7-4137-bc47-04ab5cb7a0b7=VmDevice
{vmId=0fdea856-9aec-4300-8d88-4cfd330cf4ff,
deviceId=b97a2abb-a9a7-4137-bc47-04ab5cb7a0b7, device=spicevmc, type=CHANNEL,
bootOrder=0, specParams={}, address={port=3, bus=0, controller=0,
type=virtio-serial}, managed=false, plugged=true, readOnly=false,
deviceAlias=channel2, customProperties={}, snapshotId=null},
device_2837bb81-e830-4014-9cba-b95e76c8785bdevice_87f78a45-040c-4534-a19a-e7ba97f3721f=VmDevice
{vmId=0fdea856-9aec-4300-8d88-4cfd330cf4ff,
deviceId=87f78a45-040c-4534-a19a-e7ba97f3721f, device=unix, type=CHANNEL,
bootOrder=0, specParams={}, address={port=2, bus=0, controller=0,
type=virtio-serial}, managed=false, plugged=true, readOnly=false,
deviceAlias=channel1, customProperties={}, snapshotId=null},
device_2837bb81-e830-4014-9cba-b95e76c8785b=VmDevice
{vmId=0fdea856-9aec-4300-8d88-4cfd330cf4ff,
deviceId=2837bb81-e830-4014-9cba-b95e76c8785b, device=unix, type=CHANNEL,
bootOrder=0, specParams={}, address={port=1, bus=0, controller=0,
type=virtio-serial}, managed=false, plugged=true, readOnly=false,
deviceAlias=channel0, customProperties={}, snapshotId=null},
device_2837bb81-e830-4014-9cba-b95e76c8785bdevice_87f78a45-040c-4534-a19a-
