
This is a multi-part message in MIME format. --------------080701070002030103070807 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: quoted-printable Le 10/12/2015 10:41, Michal Skrivanek a =E9crit :
On 10 Dec 2015, at 00:11, Gianluca Cecchi <gianluca.cecchi@gmail.com=20 <mailto:gianluca.cecchi@gmail.com>> wrote:
On Wed, Dec 9, 2015 at 10:21 PM, Sandro Bonazzola wrote:
No idea. If it's libvirt issue, can you test http://cbs.centos.org/koji/buildinfo?buildID=3D4726 ? it's from centos virt sig, introduced for Xen but should work on kvm as well. or the 7.2 libvirt from http://mirror.centos.org/centos/7/cr/x86_64/Packages/.
Hello, tried on a test environment where I have 3.6.0 on single CentOS 7.1=20 hypervisor configured with SelfHostedEngine I have a CentOS 7.1 vm running.
On hypervisor I shutdown VM, put maintenance global and shutdown=20 engine VM. Then [root@ractor ~]# yum --enablerepo=3Dcr update libvirt* Loaded plugins: fastestmirror, langpacks cr | 3.4 kB 00:00:00 cr/7/x86_64/primary_db | 3.7 MB 00:00:02 Loading mirror speeds from cached hostfile * base: centos.fastbull.org <http://centos.fastbull.org/> * extras: centos.fastbull.org <http://centos.fastbull.org/> * ovirt-3.6: ftp.nluug.nl <http://ftp.nluug.nl/> * ovirt-3.6-epel: epel.besthosting.ua <http://epel.besthosting.ua/> * updates: centos.copahost.com <http://centos.copahost.com/> Resolving Dependencies --> Running transaction check ---> Package libvirt-client.x86_64 0:1.2.8-16.el7_1.5 will be updated ---> Package libvirt-client.x86_64 0:1.2.17-13.el7_2.2 will be an upda=
te
--> Processing Dependency: libsystemd.so.0(LIBSYSTEMD_209)(64bit) for=20 package: libvirt-client-1.2.17-13.el7_2.2.x86_64 --> Processing Dependency: libsystemd.so.0()(64bit) for package:=20 libvirt-client-1.2.17-13.el7_2.2.x86_64 ---> Package libvirt-daemon.x86_64 0:1.2.8-16.el7_1.5 will be updated ---> Package libvirt-daemon.x86_64 0:1.2.17-13.el7_2.2 will be an upda= te ---> Package libvirt-daemon-config-nwfilter.x86_64 0:1.2.8-16.el7_1.5=20 will be updated ---> Package libvirt-daemon-config-nwfilter.x86_64=20 0:1.2.17-13.el7_2.2 will be an update ---> Package libvirt-daemon-driver-interface.x86_64=20 0:1.2.8-16.el7_1.5 will be updated ---> Package libvirt-daemon-driver-interface.x86_64=20 0:1.2.17-13.el7_2.2 will be an update ---> Package libvirt-daemon-driver-network.x86_64 0:1.2.8-16.el7_1.5=20 will be updated ---> Package libvirt-daemon-driver-network.x86_64 0:1.2.17-13.el7_2.2=20 will be an update ---> Package libvirt-daemon-driver-nodedev.x86_64 0:1.2.8-16.el7_1.5=20 will be updated ---> Package libvirt-daemon-driver-nodedev.x86_64 0:1.2.17-13.el7_2.2=20 will be an update ---> Package libvirt-daemon-driver-nwfilter.x86_64 0:1.2.8-16.el7_1.5=20 will be updated ---> Package libvirt-daemon-driver-nwfilter.x86_64=20 0:1.2.17-13.el7_2.2 will be an update ---> Package libvirt-daemon-driver-qemu.x86_64 0:1.2.8-16.el7_1.5=20 will be updated ---> Package libvirt-daemon-driver-qemu.x86_64 0:1.2.17-13.el7_2.2=20 will be an update ---> Package libvirt-daemon-driver-secret.x86_64 0:1.2.8-16.el7_1.5=20 will be updated ---> Package libvirt-daemon-driver-secret.x86_64 0:1.2.17-13.el7_2.2=20 will be an update ---> Package libvirt-daemon-driver-storage.x86_64 0:1.2.8-16.el7_1.5=20 will be updated ---> Package libvirt-daemon-driver-storage.x86_64 0:1.2.17-13.el7_2.2=20 will be an update --> Processing Dependency: libdevmapper.so.1.02(DM_1_02_97)(64bit)=20 for package: libvirt-daemon-driver-storage-1.2.17-13.el7_2.2.x86_64 ---> Package libvirt-daemon-kvm.x86_64 0:1.2.8-16.el7_1.5 will be upda= ted ---> Package libvirt-daemon-kvm.x86_64 0:1.2.17-13.el7_2.2 will be an=20 update ---> Package libvirt-lock-sanlock.x86_64 0:1.2.8-16.el7_1.5 will be=20 updated ---> Package libvirt-lock-sanlock.x86_64 0:1.2.17-13.el7_2.2 will be=20 an update ---> Package libvirt-python.x86_64 0:1.2.8-7.el7_1.1 will be updated ---> Package libvirt-python.x86_64 0:1.2.17-2.el7 will be an update --> Running transaction check ---> Package device-mapper-libs.x86_64 7:1.02.93-3.el7_1.1 will be=20 updated --> Processing Dependency: device-mapper-libs =3D 7:1.02.93-3.el7_1.1=20 for package: 7:device-mapper-1.02.93-3.el7_1.1.x86_64 ---> Package device-mapper-libs.x86_64 7:1.02.107-5.el7 will be an upd= ate ---> Package systemd-libs.x86_64 0:208-20.el7_1.6 will be updated --> Processing Dependency: systemd-libs =3D 208-20.el7_1.6 for package= :=20 systemd-208-20.el7_1.6.x86_64 ---> Package systemd-libs.x86_64 0:219-19.el7 will be an update --> Running transaction check ---> Package device-mapper.x86_64 7:1.02.93-3.el7_1.1 will be updated --> Processing Dependency: device-mapper =3D 7:1.02.93-3.el7_1.1 for=20 package: 7:device-mapper-event-1.02.93-3.el7_1.1.x86_64 ---> Package device-mapper.x86_64 7:1.02.107-5.el7 will be an update ---> Package systemd.x86_64 0:208-20.el7_1.6 will be updated --> Processing Dependency: systemd =3D 208-20.el7_1.6 for package:=20 systemd-sysv-208-20.el7_1.6.x86_64 --> Processing Dependency: systemd =3D 208-20.el7_1.6 for package:=20 systemd-python-208-20.el7_1.6.x86_64 --> Processing Dependency: systemd =3D 208-20.el7_1.6 for package:=20 libgudev1-208-20.el7_1.6.x86_64 ---> Package systemd.x86_64 0:219-19.el7 will be an update --> Processing Dependency: kmod >=3D 18-4 for package:=20 systemd-219-19.el7.x86_64 --> Running transaction check ---> Package device-mapper-event.x86_64 7:1.02.93-3.el7_1.1 will be=20 updated --> Processing Dependency: device-mapper-event =3D 7:1.02.93-3.el7_1.1= =20 for package: 7:lvm2-libs-2.02.115-3.el7_1.1.x86_64 ---> Package device-mapper-event.x86_64 7:1.02.107-5.el7 will be an=20 update --> Processing Dependency: device-mapper-event-libs =3D=20 7:1.02.107-5.el7 for package: 7:device-mapper-event-1.02.107-5.el7.x86= _64 ---> Package kmod.x86_64 0:14-10.el7 will be updated ---> Package kmod.x86_64 0:20-5.el7 will be an update ---> Package libgudev1.x86_64 0:208-20.el7_1.6 will be updated ---> Package libgudev1.x86_64 0:219-19.el7 will be an update ---> Package systemd-python.x86_64 0:208-20.el7_1.6 will be updated ---> Package systemd-python.x86_64 0:219-19.el7 will be an update ---> Package systemd-sysv.x86_64 0:208-20.el7_1.6 will be updated ---> Package systemd-sysv.x86_64 0:219-19.el7 will be an update --> Running transaction check ---> Package device-mapper-event-libs.x86_64 7:1.02.93-3.el7_1.1 will=20 be updated ---> Package device-mapper-event-libs.x86_64 7:1.02.107-5.el7 will be=20 an update ---> Package lvm2-libs.x86_64 7:2.02.115-3.el7_1.1 will be updated --> Processing Dependency: lvm2-libs =3D 7:2.02.115-3.el7_1.1 for=20 package: 7:lvm2-2.02.115-3.el7_1.1.x86_64 ---> Package lvm2-libs.x86_64 7:2.02.130-5.el7 will be an update --> Running transaction check ---> Package lvm2.x86_64 7:2.02.115-3.el7_1.1 will be updated ---> Package lvm2.x86_64 7:2.02.130-5.el7 will be an update --> Processing Dependency: device-mapper-persistent-data >=3D 0.5.5-1=20 for package: 7:lvm2-2.02.130-5.el7.x86_64 --> Running transaction check ---> Package device-mapper-persistent-data.x86_64 0:0.4.1-2.el7 will=20 be updated ---> Package device-mapper-persistent-data.x86_64 0:0.5.5-1.el7 will=20 be an update --> Processing Conflict: systemd-219-19.el7.x86_64 conflicts=20 initscripts < 9.49.28-1 --> Restarting Dependency Resolution with new changes. --> Running transaction check ---> Package initscripts.x86_64 0:9.49.24-1.el7 will be updated ---> Package initscripts.x86_64 0:9.49.30-1.el7 will be an update --> Processing Conflict: systemd-219-19.el7.x86_64 conflicts dracut <=20 033-243 --> Restarting Dependency Resolution with new changes. --> Running transaction check ---> Package dracut.x86_64 0:033-241.el7_1.5 will be updated --> Processing Dependency: dracut =3D 033-241.el7_1.5 for package:=20 dracut-config-rescue-033-241.el7_1.5.x86_64 --> Processing Dependency: dracut =3D 033-241.el7_1.5 for package:=20 dracut-network-033-241.el7_1.5.x86_64 ---> Package dracut.x86_64 0:033-360.el7_2 will be an update --> Running transaction check ---> Package dracut-config-rescue.x86_64 0:033-241.el7_1.5 will be=20 updated ---> Package dracut-config-rescue.x86_64 0:033-360.el7_2 will be an=20 update ---> Package dracut-network.x86_64 0:033-241.el7_1.5 will be updated ---> Package dracut-network.x86_64 0:033-360.el7_2 will be an update --> Finished Dependency Resolution
Dependencies Resolved
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D Package Arch=20 Version Repository Size =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D Updating: dracut x86_64=20 033-360.el7_2 cr 311 k initscripts x86_64=20 9.49.30-1.el7 cr 429 k libvirt-client x86_64=20 1.2.17-13.el7_2.2 cr 4.3 M libvirt-daemon x86_64=20 1.2.17-13.el7_2.2 cr 584 k libvirt-daemon-config-nwfilter x86_64=20 1.2.17-13.el7_2.2 cr 121 k libvirt-daemon-driver-interface x86_64=20 1.2.17-13.el7_2.2 cr 161 k libvirt-daemon-driver-network x86_64=20 1.2.17-13.el7_2.2 cr 301 k libvirt-daemon-driver-nodedev x86_64=20 1.2.17-13.el7_2.2 cr 160 k libvirt-daemon-driver-nwfilter x86_64=20 1.2.17-13.el7_2.2 cr 184 k libvirt-daemon-driver-qemu x86_64=20 1.2.17-13.el7_2.2 cr 569 k libvirt-daemon-driver-secret x86_64=20 1.2.17-13.el7_2.2 cr 154 k libvirt-daemon-driver-storage x86_64=20 1.2.17-13.el7_2.2 cr 327 k libvirt-daemon-kvm x86_64=20 1.2.17-13.el7_2.2 cr 117 k libvirt-lock-sanlock x86_64=20 1.2.17-13.el7_2.2 cr 166 k libvirt-python x86_64=20 1.2.17-2.el7 cr 309 k Updating for dependencies: device-mapper x86_64=20 7:1.02.107-5.el7 cr 251 k device-mapper-event x86_64=20 7:1.02.107-5.el7 cr 167 k device-mapper-event-libs x86_64=20 7:1.02.107-5.el7 cr 169 k device-mapper-libs x86_64=20 7:1.02.107-5.el7 cr 304 k device-mapper-persistent-data x86_64=20 0.5.5-1.el7 cr 350 k dracut-config-rescue x86_64=20 033-360.el7_2 cr 49 k dracut-network x86_64=20 033-360.el7_2 cr 90 k kmod x86_64=20 20-5.el7 cr 114 k libgudev1 x86_64=20 219-19.el7 cr 64 k lvm2 x86_64=20 7:2.02.130-5.el7 cr 1.0 M lvm2-libs x86_64=20 7:2.02.130-5.el7 cr 872 k systemd x86_64=20 219-19.el7 cr 5.1 M systemd-libs x86_64=20 219-19.el7 cr 356 k systemd-python x86_64=20 219-19.el7 cr 97 k systemd-sysv x86_64=20 219-19.el7 cr 52 k
Transaction Summary =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D Upgrade 15 Packages (+15 Dependent packages)
Total download size: 17 M Is this ok [y/d/N]:
Then I reboot my HV, exit from maintenance, connect to engine and=20 start VM. VM situation $ free total used free shared buff/cache =20 available Mem: 8172900 147356 7875692 8480 149852 78472= 48 Swap: 839676 0 839676
I set memory from 8192Mb to 10240Mb I get the same window I got with previous libvirt version. I select OK (I don't select "Apply later" checkbox)
Inside guest there is no changed memory, but I can see this in=20 /var/log/messages:
could it be perhaps the guest has troubles recognizing hotplug? Is it=20 also a CentOS 7.1 guest?
Dec 9 23:56:18 racclient1 kernel: init_memory_mapping: [mem=20 0x240000000-0x2bfffffff]
ANd output of dmesg contains:
[ 219.363640] ACPI: \_SB_.MP00: ACPI_NOTIFY_DEVICE_CHECK event [ 219.364248] init_memory_mapping: [mem 0x240000000-0x2bfffffff] [ 219.364253] [mem 0x240000000-0x2bfffffff] page 2M [ 219.366773] [ffffea0009000000-ffffea00091fffff] PMD ->=20 [ffff8800b7e00000-ffff8800b7ffffff] on node 0 [ 219.368433] [ffffea0009200000-ffffea00093fffff] PMD ->=20 [ffff880231400000-ffff8802315fffff] on node 0 [ 219.369838] [ffffea0009400000-ffffea00095fffff] PMD ->=20 [ffff880233600000-ffff8802337fffff] on node 0 [ 219.371226] [ffffea0009600000-ffffea00097fffff] PMD ->=20 [ffff880233000000-ffff8802331fffff] on node 0 [ 219.372790] [ffffea0009800000-ffffea00099fffff] PMD ->=20 [ffff880232c00000-ffff880232dfffff] on node 0 [ 219.374185] [ffffea0009a00000-ffffea0009bfffff] PMD ->=20 [ffff880232200000-ffff8802323fffff] on node 0 [ 219.377349] [ffffea0009c00000-ffffea0009ffffff] PMD ->=20 [ffff8800b7400000-ffff8800b77fffff] on node 0 [ 219.378716] [ffffea000a000000-ffffea000a1fffff] PMD ->=20 [ffff8800b7000000-ffff8800b71fffff] on node 0 [ 219.380115] [ffffea000a200000-ffffea000a3fffff] PMD ->=20 [ffff880230c00000-ffff880230dfffff] on node 0 [ 219.388147] [ffffea000a400000-ffffea000abfffff] PMD ->=20 [ffff880227c00000-ffff8802283fffff] on node 0 [ 219.389687] [ffffea000ac00000-ffffea000adfffff] PMD ->=20 [ffff8800b7200000-ffff8800b73fffff] on node 0
but =93free=94 sstill shows the same value as before hotplug?
I then shutdown the VM and power on it again and I get the changed=20 memory:
well, yeah, but that doesn=92t count since you=92ve shut it down, so th= e=20 next run is initialized with 10GB
$ free total used free shared buff/cache =20 available Mem: 10237276 167872 9919656 8480 149748 98912= 80 Swap: 839676 0 839676
BTW: When I press ok in the gui for memory increase I get these=20 events in webadmin: Dec 9, 2015 11:56:22 PM VM racclient1 c71_Disk1_newtemplate disk was updated by admin@internal= .
hm..doesn=92t sound right. Did the confirmation window show any more=20 fields as changed other than memory?
Dec 9, 2015 11:56:19 PM VM racclient1 configuration was updated by admin@internal.
that=92s correct - the new base for the next run
Dec 9, 2015 11:56:18 PM Hotset memory: changed the amount of memory on VM racclient1 from=20 8192 to 10240
that=92s the actual hotplug
It doesn't seem as expected, does it?
I think we=92re almost there. Just need to figure out what happened in=20 the guest. I would suspect a problem there I did the same test, I obtain the same result but here is what I get=20 into the /var/log/messages guest (7.1) logs and not mentionned there: unsupported configuration: maxMemory has to be specified when using=20 memory devices What can't I do with this error, is it a known issue?
Thanks, michal
Gianluca
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
gianluca.cecchi@gmail.com</a></a>> wrote:</div> <br class=3D"Apple-interchange-newline"> <div class=3D""> <div dir=3D"ltr" class=3D""> <div class=3D"gmail_extra"> <div class=3D"gmail_quote">On Wed, Dec 9, 2015 at 10:21 PM, Sandro Bonazzola=A0<span dir=3D"ltr" class=3D""></s=
--=20 Nathana=EBl Blanchet Supervision r=E9seau P=F4le Infrastrutures Informatiques 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 =09 T=E9l. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanchet@abes.fr --------------080701070002030103070807 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable <html> <head> <meta content=3D"text/html; charset=3Dwindows-1252" http-equiv=3D"Content-Type"> </head> <body bgcolor=3D"#FFFFFF" text=3D"#000000"> <br> <br> <div class=3D"moz-cite-prefix">Le 10/12/2015 10:41, Michal Skrivanek = a =E9crit=A0:<br> </div> <blockquote cite=3D"mid:F8823B97-23FD-4125-B374-EE3918F3A383@redhat.com" type=3D"cite"> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dwindows-1252"> <br class=3D""> <div> <blockquote type=3D"cite" class=3D""> <div class=3D"">On 10 Dec 2015, at 00:11, Gianluca Cecchi <<= a moz-do-not-send=3D"true" href=3D"mailto:gianluca.cecchi@gmail.com" class=3D""><a cla= ss=3D"moz-txt-link-abbreviated" href=3D"mailto:gianluca.cecchi@gmail.com"= pan> wrote:<br class=3D""> <blockquote class=3D"gmail_quote" style=3D"margin:0px 0= px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> <div dir=3D"ltr" class=3D""><br class=3D""> <div class=3D"gmail_extra"> <div class=3D"gmail_quote"><span class=3D""> <div class=3D""><br class=3D""> </div> </span> <div class=3D"">No idea. If it's libvirt issue, can you test=A0<a moz-do-not-send=3D"true" href=3D"http://cbs.centos.org/koji/buildinf= o?buildID=3D4726" target=3D"_blank" class=3D"">http://cbs.cen= tos.org/koji/buildinfo?buildID=3D4726</a> ? it's from centos virt sig, introduced for Xen but should work on kvm as well. or the 7.2 libvirt from=A0<a moz-do-not-send=3D"true= " href=3D"http://mirror.centos.org/centos/7/c= r/x86_64/Packages/" target=3D"_blank" class=3D"">http://mirror.= centos.org/centos/7/cr/x86_64/Packages/</a>.</div> <div class=3D""> <div class=3D"h5"> <div class=3D""><br class=3D""> </div> <div class=3D""><br class=3D""> </div> </div> </div> </div> </div> </div> </blockquote> </div> <br class=3D""> Hello,<br class=3D""> tried on a test environment where I have 3.6.0 on single CentOS 7.1 hypervisor configured with SelfHostedEngine<br class=3D""> I have a CentOS 7.1 vm running.<br class=3D""> <br class=3D""> On hypervisor I shutdown VM, put maintenance global and shutdown engine VM.<br class=3D""> Then<br class=3D""> [root@ractor ~]# yum --enablerepo=3Dcr update libvirt*<br class=3D""> Loaded plugins: fastestmirror, langpacks<br class=3D""> cr=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0 | 3.4 kB=A0 00:00:00=A0=A0=A0=A0 <br class=3D""> cr/7/x86_64/primary_db=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 | 3.7 MB=A0 00:00:02=A0=A0=A0=A0 <br class=3D""> Loading mirror speeds from cached hostfile<br class=3D""> =A0* base: <a moz-do-not-send=3D"true" href=3D"http://centos.fastbull.org/" class=3D"">centos.= fastbull.org</a><br class=3D""> =A0* extras: <a moz-do-not-send=3D"true" href=3D"http://centos.fastbull.org/" class=3D"">centos.= fastbull.org</a><br class=3D""> =A0* ovirt-3.6: <a moz-do-not-send=3D"true" href=3D"http://ftp.nluug.nl/" class=3D"">ftp.nluug.nl</= a><br class=3D""> =A0* ovirt-3.6-epel: <a moz-do-not-send=3D"true" href=3D"http://epel.besthosting.ua/" class=3D"">epel.be= sthosting.ua</a><br class=3D""> =A0* updates: <a moz-do-not-send=3D"true" href=3D"http://centos.copahost.com/" class=3D"">centos.= copahost.com</a><br class=3D""> Resolving Dependencies<br class=3D""> --> Running transaction check<br class=3D""> ---> Package libvirt-client.x86_64 0:1.2.8-16.el7_1.5 will be updated<br class=3D""> ---> Package libvirt-client.x86_64 0:1.2.17-13.el7_2.2 will be an update<br class=3D""> --> Processing Dependency: libsystemd.so.0(LIBSYSTEMD_209)(64bit) for package: libvirt-client-1.2.17-13.el7_2.2.x86_64<br class=3D""> --> Processing Dependency: libsystemd.so.0()(64bit) for package: libvirt-client-1.2.17-13.el7_2.2.x86_64<br class=3D""> ---> Package libvirt-daemon.x86_64 0:1.2.8-16.el7_1.5 will be updated<br class=3D""> ---> Package libvirt-daemon.x86_64 0:1.2.17-13.el7_2.2 will be an update<br class=3D""> ---> Package libvirt-daemon-config-nwfilter.x86_64 0:1.2.8-16.el7_1.5 will be updated<br class=3D""> ---> Package libvirt-daemon-config-nwfilter.x86_64 0:1.2.17-13.el7_2.2 will be an update<br class=3D""> ---> Package libvirt-daemon-driver-interface.x86_64 0:1.2.8-16.el7_1.5 will be updated<br class=3D""> ---> Package libvirt-daemon-driver-interface.x86_64 0:1.2.17-13.el7_2.2 will be an update<br class=3D""> ---> Package libvirt-daemon-driver-network.x86_64 0:1.2.8-16.el7_1.5 will be updated<br class=3D""> ---> Package libvirt-daemon-driver-network.x86_64 0:1.2.17-13.el7_2.2 will be an update<br class=3D""> ---> Package libvirt-daemon-driver-nodedev.x86_64 0:1.2.8-16.el7_1.5 will be updated<br class=3D""> ---> Package libvirt-daemon-driver-nodedev.x86_64 0:1.2.17-13.el7_2.2 will be an update<br class=3D""> ---> Package libvirt-daemon-driver-nwfilter.x86_64 0:1.2.8-16.el7_1.5 will be updated<br class=3D""> ---> Package libvirt-daemon-driver-nwfilter.x86_64 0:1.2.17-13.el7_2.2 will be an update<br class=3D""> ---> Package libvirt-daemon-driver-qemu.x86_64 0:1.2.8-16.el7_1.5 will be updated<br class=3D""> ---> Package libvirt-daemon-driver-qemu.x86_64 0:1.2.17-13.el7_2.2 will be an update<br class=3D""> ---> Package libvirt-daemon-driver-secret.x86_64 0:1.2.8-16.el7_1.5 will be updated<br class=3D""> ---> Package libvirt-daemon-driver-secret.x86_64 0:1.2.17-13.el7_2.2 will be an update<br class=3D""> ---> Package libvirt-daemon-driver-storage.x86_64 0:1.2.8-16.el7_1.5 will be updated<br class=3D""> ---> Package libvirt-daemon-driver-storage.x86_64 0:1.2.17-13.el7_2.2 will be an update<br class=3D""> --> Processing Dependency: libdevmapper.so.1.02(DM_1_02_97)(64bit) for package: libvirt-daemon-driver-storage-1.2.17-13.el7_2.2.x86_64<br class=3D""> ---> Package libvirt-daemon-kvm.x86_64 0:1.2.8-16.el7_1.5 will be updated<br class=3D""> ---> Package libvirt-daemon-kvm.x86_64 0:1.2.17-13.el7_2.2 will be an update<br class=3D""> ---> Package libvirt-lock-sanlock.x86_64 0:1.2.8-16.el7_1.5 will be updated<br class=3D""> ---> Package libvirt-lock-sanlock.x86_64 0:1.2.17-13.el7_2.2 will be an update<br class=3D""> ---> Package libvirt-python.x86_64 0:1.2.8-7.el7_1.1 will be updated<br class=3D""> ---> Package libvirt-python.x86_64 0:1.2.17-2.el7 will be an update<br class=3D""> --> Running transaction check<br class=3D""> ---> Package device-mapper-libs.x86_64 7:1.02.93-3.el7_1.1 will be updated<br class=3D""> --> Processing Dependency: device-mapper-libs =3D 7:1.02.93-3.el7_1.1 for package: 7:device-mapper-1.02.93-3.el7_1.1.x86_64<br class=3D""> ---> Package device-mapper-libs.x86_64 7:1.02.107-5.el7 will be an update<br class=3D""> ---> Package systemd-libs.x86_64 0:208-20.el7_1.6 will be updated<br class=3D""> --> Processing Dependency: systemd-libs =3D 208-20.el7_1.6 for package: systemd-208-20.el7_1.6.x86_64<br class=3D""> ---> Package systemd-libs.x86_64 0:219-19.el7 will be an update<br class=3D""> --> Running transaction check<br class=3D""> ---> Package device-mapper.x86_64 7:1.02.93-3.el7_1.1 will be updated<br class=3D""> --> Processing Dependency: device-mapper =3D 7:1.02.93-3.el7_1.1 for package: 7:device-mapper-event-1.02.93-3.el7_1.1.x86_64<br class=3D""> ---> Package device-mapper.x86_64 7:1.02.107-5.el7 will be an update<br class=3D""> ---> Package systemd.x86_64 0:208-20.el7_1.6 will be updated<br class=3D""> --> Processing Dependency: systemd =3D 208-20.el7_1.6 for package: systemd-sysv-208-20.el7_1.6.x86_64<br class=3D""> --> Processing Dependency: systemd =3D 208-20.el7_1.6 for package: systemd-python-208-20.el7_1.6.x86_64<br class=3D""> --> Processing Dependency: systemd =3D 208-20.el7_1.6 for package: libgudev1-208-20.el7_1.6.x86_64<br class=3D"= "> ---> Package systemd.x86_64 0:219-19.el7 will be an update<br class=3D""> --> Processing Dependency: kmod >=3D 18-4 for package: systemd-219-19.el7.x86_64<br class=3D""> --> Running transaction check<br class=3D""> ---> Package device-mapper-event.x86_64 7:1.02.93-3.el7_1.1 will be updated<br class=3D""> --> Processing Dependency: device-mapper-event =3D 7:1.02.93-3.el7_1.1 for package: 7:lvm2-libs-2.02.115-3.el7_1.1.x86_64<br class=3D""> ---> Package device-mapper-event.x86_64 7:1.02.107-5.el7 will be an update<br class=3D""> --> Processing Dependency: device-mapper-event-libs =3D 7:1.02.107-5.el7 for package: 7:device-mapper-event-1.02.107-5.el7.x86_64<br class=3D""=
---> Package kmod.x86_64 0:14-10.el7 will be updated<b= r class=3D""> ---> Package kmod.x86_64 0:20-5.el7 will be an update<= br class=3D""> ---> Package libgudev1.x86_64 0:208-20.el7_1.6 will be updated<br class=3D""> ---> Package libgudev1.x86_64 0:219-19.el7 will be an update<br class=3D""> ---> Package systemd-python.x86_64 0:208-20.el7_1.6 will be updated<br class=3D""> ---> Package systemd-python.x86_64 0:219-19.el7 will be an update<br class=3D""> ---> Package systemd-sysv.x86_64 0:208-20.el7_1.6 will be updated<br class=3D""> ---> Package systemd-sysv.x86_64 0:219-19.el7 will be an update<br class=3D""> --> Running transaction check<br class=3D""> ---> Package device-mapper-event-libs.x86_64 7:1.02.93-3.el7_1.1 will be updated<br class=3D""> ---> Package device-mapper-event-libs.x86_64 7:1.02.107-5.el7 will be an update<br class=3D""> ---> Package lvm2-libs.x86_64 7:2.02.115-3.el7_1.1 will be updated<br class=3D""> --> Processing Dependency: lvm2-libs =3D 7:2.02.115-3.el7_1.1 for package: 7:lvm2-2.02.115-3.el7_1.1.x86_64<br class=3D""> ---> Package lvm2-libs.x86_64 7:2.02.130-5.el7 will be an update<br class=3D""> --> Running transaction check<br class=3D""> ---> Package lvm2.x86_64 7:2.02.115-3.el7_1.1 will be updated<br class=3D""> ---> Package lvm2.x86_64 7:2.02.130-5.el7 will be an update<br class=3D""> --> Processing Dependency: device-mapper-persistent-data >=3D 0.5.5-1 for package= : 7:lvm2-2.02.130-5.el7.x86_64<br class=3D""> --> Running transaction check<br class=3D""> ---> Package device-mapper-persistent-data.x86_64 0:0.4.1-2.el7 will be updated<br class=3D""> ---> Package device-mapper-persistent-data.x86_64 0:0.5.5-1.el7 will be an update<br class=3D""> --> Processing Conflict: systemd-219-19.el7.x86_64 conflicts initscripts < 9.49.28-1<br class=3D""> --> Restarting Dependency Resolution with new changes.<br class=3D""> --> Running transaction check<br class=3D""> ---> Package initscripts.x86_64 0:9.49.24-1.el7 will be updated<br class=3D""> ---> Package initscripts.x86_64 0:9.49.30-1.el7 will be an update<br class=3D""> --> Processing Conflict: systemd-219-19.el7.x86_64 conflicts dracut < 033-243<br class=3D""> --> Restarting Dependency Resolution with new changes.<br class=3D""> --> Running transaction check<br class=3D""> ---> Package dracut.x86_64 0:033-241.el7_1.5 will be updated<br class=3D""> --> Processing Dependency: dracut =3D 033-241.el7_1.5 for package: dracut-config-rescue-033-241.el7_1.5.x86_64<= br class=3D""> --> Processing Dependency: dracut =3D 033-241.el7_1.5 for package: dracut-network-033-241.el7_1.5.x86_64<br class=3D""> ---> Package dracut.x86_64 0:033-360.el7_2 will be an update<br class=3D""> --> Running transaction check<br class=3D""> ---> Package dracut-config-rescue.x86_64 0:033-241.el7_1.5 will be updated<br class=3D""> ---> Package dracut-config-rescue.x86_64 0:033-360.el7_2 will be an update<br class=3D""> ---> Package dracut-network.x86_64 0:033-241.el7_1.5 will be updated<br class=3D""> ---> Package dracut-network.x86_64 0:033-360.el7_2 will be an update<br class=3D""> --> Finished Dependency Resolution<br class=3D""> <br class=3D""> Dependencies Resolved<br class=3D""> <br class=3D""> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= <br class=3D""> =A0Package=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 Arch=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0 Version=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0 Repository=A0 Size<br class=3D""> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= <br class=3D""> Updating:<br class=3D""> =A0dracut=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 x86_64=A0=A0=A0=A0=A0= =A0=A0=A0 033-360.el7_2=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 cr=A0= =A0=A0=A0=A0=A0=A0=A0 311 k<br class=3D""> =A0initscripts=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 x86_64=A0=A0=A0=A0=A0=A0=A0=A0 9.49.30-1.el7=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 cr=A0= =A0=A0=A0=A0=A0=A0=A0 429 k<br class=3D""> =A0libvirt-client=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 x86_64=A0=A0=A0=A0=A0=A0=A0=A0 1.2.17-13.el7_2.2=A0=A0=A0=A0=A0=A0=A0=A0=A0 cr=A0=A0=A0=A0= =A0=A0=A0=A0 4.3 M<br class=3D""> =A0libvirt-daemon=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 x86_64=A0=A0=A0=A0=A0=A0=A0=A0 1.2.17-13.el7_2.2=A0=A0=A0=A0=A0=A0=A0=A0=A0 cr=A0=A0=A0=A0= =A0=A0=A0=A0 584 k<br class=3D""> =A0libvirt-daemon-config-nwfilter=A0=A0=A0=A0=A0=A0=A0=A0= =A0 x86_64=A0=A0=A0=A0=A0=A0=A0=A0 1.2.17-13.el7_2.2=A0=A0=A0=A0=A0=A0=A0=A0=A0 cr=A0=A0=A0=A0= =A0=A0=A0=A0 121 k<br class=3D""> =A0libvirt-daemon-driver-interface=A0=A0=A0=A0=A0=A0=A0=A0= x86_64=A0=A0=A0=A0=A0=A0=A0=A0 1.2.17-13.el7_2.2=A0=A0=A0=A0=A0=A0=A0=A0=A0 cr=A0=A0=A0=A0= =A0=A0=A0=A0 161 k<br class=3D""> =A0libvirt-daemon-driver-network=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0 x86_64=A0=A0=A0=A0=A0=A0=A0=A0 1.2.17-13.el7_2.2=A0=A0=A0=A0=A0=A0=A0=A0=A0 cr=A0=A0=A0=A0= =A0=A0=A0=A0 301 k<br class=3D""> =A0libvirt-daemon-driver-nodedev=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0 x86_64=A0=A0=A0=A0=A0=A0=A0=A0 1.2.17-13.el7_2.2=A0=A0=A0=A0=A0=A0=A0=A0=A0 cr=A0=A0=A0=A0= =A0=A0=A0=A0 160 k<br class=3D""> =A0libvirt-daemon-driver-nwfilter=A0=A0=A0=A0=A0=A0=A0=A0= =A0 x86_64=A0=A0=A0=A0=A0=A0=A0=A0 1.2.17-13.el7_2.2=A0=A0=A0=A0=A0=A0=A0=A0=A0 cr=A0=A0=A0=A0= =A0=A0=A0=A0 184 k<br class=3D""> =A0libvirt-daemon-driver-qemu=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0 x86_64=A0=A0=A0=A0=A0=A0=A0=A0 1.2.17-13.el7_2.2=A0=A0=A0=A0=A0=A0=A0=A0=A0 cr=A0=A0=A0=A0= =A0=A0=A0=A0 569 k<br class=3D""> =A0libvirt-daemon-driver-secret=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0 x86_64=A0=A0=A0=A0=A0=A0=A0=A0 1.2.17-13.el7_2.2=A0=A0=A0=A0=A0=A0=A0=A0=A0 cr=A0=A0=A0=A0= =A0=A0=A0=A0 154 k<br class=3D""> =A0libvirt-daemon-driver-storage=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0 x86_64=A0=A0=A0=A0=A0=A0=A0=A0 1.2.17-13.el7_2.2=A0=A0=A0=A0=A0=A0=A0=A0=A0 cr=A0=A0=A0=A0= =A0=A0=A0=A0 327 k<br class=3D""> =A0libvirt-daemon-kvm=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0 x86_64=A0=A0=A0=A0=A0=A0=A0=A0 1.2.17-13.el7_2.2=A0=A0=A0=A0=A0=A0=A0=A0=A0 cr=A0=A0=A0=A0= =A0=A0=A0=A0 117 k<br class=3D""> =A0libvirt-lock-sanlock=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0 x86_64=A0=A0=A0=A0=A0=A0=A0=A0 1.2.17-13.el7_2.2=A0=A0=A0=A0=A0=A0=A0=A0=A0 cr=A0=A0=A0=A0= =A0=A0=A0=A0 166 k<br class=3D""> =A0libvirt-python=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 x86_64=A0=A0=A0=A0=A0=A0=A0=A0 1.2.17-2.el7=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 cr= =A0=A0=A0=A0=A0=A0=A0=A0 309 k<br class=3D""> Updating for dependencies:<br class=3D""> =A0device-mapper=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 x86_64=A0=A0=A0=A0=A0=A0=A0=A0 7:1.02.107-5.el7=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 cr=A0=A0=A0= =A0=A0=A0=A0=A0 251 k<br class=3D""> =A0device-mapper-event=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0 x86_64=A0=A0=A0=A0=A0=A0=A0=A0 7:1.02.107-5.el7=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 cr=A0=A0=A0= =A0=A0=A0=A0=A0 167 k<br class=3D""> =A0device-mapper-event-libs=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0 x86_64=A0=A0=A0=A0=A0=A0=A0=A0 7:1.02.107-5.el7=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 cr=A0=A0=A0= =A0=A0=A0=A0=A0 169 k<br class=3D""> =A0device-mapper-libs=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0 x86_64=A0=A0=A0=A0=A0=A0=A0=A0 7:1.02.107-5.el7=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 cr=A0=A0=A0= =A0=A0=A0=A0=A0 304 k<br class=3D""> =A0device-mapper-persistent-data=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0 x86_64=A0=A0=A0=A0=A0=A0=A0=A0 0.5.5-1.el7=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 = cr=A0=A0=A0=A0=A0=A0=A0=A0 350 k<br class=3D""> =A0dracut-config-rescue=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0 x86_64=A0=A0=A0=A0=A0=A0=A0=A0 033-360.el7_2=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 cr=A0= =A0=A0=A0=A0=A0=A0=A0=A0 49 k<br class=3D""> =A0dracut-network=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 x86_64=A0=A0=A0=A0=A0=A0=A0=A0 033-360.el7_2=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 cr=A0= =A0=A0=A0=A0=A0=A0=A0=A0 90 k<br class=3D""> =A0kmod=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 x86_64=A0=A0=A0=A0= =A0=A0=A0=A0 20-5.el7=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0 cr=A0=A0=A0=A0=A0=A0=A0=A0 114 k<br class=3D""> =A0libgudev1=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 x86_64=A0=A0=A0=A0=A0=A0=A0= =A0 219-19.el7=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= cr=A0=A0=A0=A0=A0=A0=A0=A0=A0 64 k<br class=3D""> =A0lvm2=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 x86_64=A0=A0=A0=A0= =A0=A0=A0=A0 7:2.02.130-5.el7=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 cr=A0=A0=A0= =A0=A0=A0=A0=A0 1.0 M<br class=3D""> =A0lvm2-libs=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 x86_64=A0=A0=A0=A0=A0=A0=A0= =A0 7:2.02.130-5.el7=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 cr=A0=A0=A0= =A0=A0=A0=A0=A0 872 k<br class=3D""> =A0systemd=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 x86_64=A0=A0=A0=A0=A0=A0= =A0=A0 219-19.el7=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= cr=A0=A0=A0=A0=A0=A0=A0=A0 5.1 M<br class=3D""> =A0systemd-libs=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 x86_64=A0=A0=A0=A0=A0=A0=A0=A0 219-19.el7=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= cr=A0=A0=A0=A0=A0=A0=A0=A0 356 k<br class=3D""> =A0systemd-python=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 x86_64=A0=A0=A0=A0=A0=A0=A0=A0 219-19.el7=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= cr=A0=A0=A0=A0=A0=A0=A0=A0=A0 97 k<br class=3D""> =A0systemd-sysv=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 x86_64=A0=A0=A0=A0=A0=A0=A0=A0 219-19.el7=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= cr=A0=A0=A0=A0=A0=A0=A0=A0=A0 52 k<br class=3D""> <br class=3D""> Transaction Summary<br class=3D""> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= <br class=3D""> Upgrade=A0 15 Packages (+15 Dependent packages)<br class=3D""> <br class=3D""> Total download size: 17 M<br class=3D""> Is this ok [y/d/N]: <br class=3D""> <br class=3D""> Then I reboot my HV, exit from maintenance, connect to engine and start VM.<br class=3D""> VM situation<br class=3D""> $ free<br class=3D""> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 total=A0=A0=A0=A0= =A0=A0=A0 used=A0=A0=A0=A0=A0=A0=A0 free=A0=A0=A0=A0=A0 shared=A0 buff/cache=A0=A0 available<br class=3D""> Mem:=A0=A0=A0=A0=A0=A0=A0 8172900=A0=A0=A0=A0=A0 147356=A0= =A0=A0=A0 7875692=A0=A0=A0=A0=A0=A0=A0 8480=A0=A0=A0=A0=A0 149852=A0=A0=A0=A0 7847248<br class=3D= ""> Swap:=A0=A0=A0=A0=A0=A0=A0 839676=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0 0=A0=A0=A0=A0=A0 839676<br class=3D""> <br class=3D""> </div> <div class=3D"gmail_extra">I set memory from 8192Mb to 10240Mb<br class=3D""> </div> <div class=3D"gmail_extra">I get the same window I got with previous libvirt version.<br class=3D""> </div> <div class=3D"gmail_extra">I select OK (I don't select "Apply later" checkbox)<br class=3D""> </div> <div class=3D"gmail_extra"><br class=3D""> </div> <div class=3D"gmail_extra">Inside guest there is no changed memory, but I can see this in /var/log/messages:<br class=3D""> </div> </div> </div> </blockquote> <div><br class=3D""> </div> could it be perhaps the guest has troubles recognizing hotplug? Is it also a CentOS 7.1 guest?</div> <div><br class=3D""> <blockquote type=3D"cite" class=3D""> <div class=3D""> <div dir=3D"ltr" class=3D""> <div class=3D"gmail_extra"><br class=3D""> Dec=A0 9 23:56:18 racclient1 kernel: init_memory_mapping: [mem 0x240000000-0x2bfffffff]<br class=3D""> <br class=3D""> </div> <div class=3D"gmail_extra">ANd output of dmesg contains:<br class=3D""> </div> <div class=3D"gmail_extra"><br class=3D""> [=A0 219.363640] ACPI: \_SB_.MP00: ACPI_NOTIFY_DEVICE_CHECK event<br class=3D""> [=A0 219.364248] init_memory_mapping: [mem 0x240000000-0x2bfffffff]<br class=3D""> [=A0 219.364253]=A0 [mem 0x240000000-0x2bfffffff] page 2M= <br class=3D""> [=A0 219.366773]=A0 [ffffea0009000000-ffffea00091fffff] P= MD -> [ffff8800b7e00000-ffff8800b7ffffff] on node 0<br class=3D""> [=A0 219.368433]=A0 [ffffea0009200000-ffffea00093fffff] P= MD -> [ffff880231400000-ffff8802315fffff] on node 0<br class=3D""> [=A0 219.369838]=A0 [ffffea0009400000-ffffea00095fffff] P= MD -> [ffff880233600000-ffff8802337fffff] on node 0<br class=3D""> [=A0 219.371226]=A0 [ffffea0009600000-ffffea00097fffff] P= MD -> [ffff880233000000-ffff8802331fffff] on node 0<br class=3D""> [=A0 219.372790]=A0 [ffffea0009800000-ffffea00099fffff] P= MD -> [ffff880232c00000-ffff880232dfffff] on node 0<br class=3D""> [=A0 219.374185]=A0 [ffffea0009a00000-ffffea0009bfffff] P= MD -> [ffff880232200000-ffff8802323fffff] on node 0<br class=3D""> [=A0 219.377349]=A0 [ffffea0009c00000-ffffea0009ffffff] P= MD -> [ffff8800b7400000-ffff8800b77fffff] on node 0<br class=3D""> [=A0 219.378716]=A0 [ffffea000a000000-ffffea000a1fffff] P= MD -> [ffff8800b7000000-ffff8800b71fffff] on node 0<br class=3D""> [=A0 219.380115]=A0 [ffffea000a200000-ffffea000a3fffff] P= MD -> [ffff880230c00000-ffff880230dfffff] on node 0<br class=3D""> [=A0 219.388147]=A0 [ffffea000a400000-ffffea000abfffff] P= MD -> [ffff880227c00000-ffff8802283fffff] on node 0<br class=3D""> [=A0 219.389687]=A0 [ffffea000ac00000-ffffea000adfffff] P= MD -> [ffff8800b7200000-ffff8800b73fffff] on node 0<br class=3D""> </div> </div> </div> </blockquote> <div><br class=3D""> </div> but =93free=94 sstill shows the same value as before hotplug?</di= v> <div><br class=3D""> <blockquote type=3D"cite" class=3D""> <div class=3D""> <div dir=3D"ltr" class=3D""> <div class=3D"gmail_extra"><br class=3D""> I then shutdown the VM and power on it again and I get the changed memory:<br class=3D""> </div> </div> </div> </blockquote> <div><br class=3D""> </div> well, yeah, but that doesn=92t count since you=92ve shut it down,= so the next run is initialized with 10GB</div> <div><br class=3D""> <blockquote type=3D"cite" class=3D""> <div class=3D""> <div dir=3D"ltr" class=3D""> <div class=3D"gmail_extra">$ free<br class=3D""> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 total=A0=A0=A0=A0= =A0=A0=A0 used=A0=A0=A0=A0=A0=A0=A0 free=A0=A0=A0=A0=A0 shared=A0 buff/cache=A0=A0 available<br class=3D""> Mem:=A0=A0=A0=A0=A0=A0 10237276=A0=A0=A0=A0=A0 167872=A0=A0= =A0=A0 9919656=A0=A0=A0=A0=A0=A0=A0 8480=A0=A0=A0=A0=A0 149748=A0=A0=A0=A0 9891280<br class=3D= ""> Swap:=A0=A0=A0=A0=A0=A0=A0 839676=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0 0=A0=A0=A0=A0=A0 839676<br class=3D""> <br class=3D""> </div> <div class=3D"gmail_extra">BTW: When I press ok in the gui for memory increase I get these events in webadmin:<br class=3D""> Dec 9, 2015 11:56:22 PM<br class=3D""> VM racclient1 c71_Disk1_newtemplate disk was updated by admin@internal.<br class=3D""> </div> </div> </div> </blockquote> <div><br class=3D""> </div> hm..doesn=92t sound right. Did the confirmation window show any more fields as changed other than memory?</div> <div><br class=3D""> <blockquote type=3D"cite" class=3D""> <div class=3D""> <div dir=3D"ltr" class=3D""> <div class=3D"gmail_extra">=A0=A0=A0 <br class=3D""> Dec 9, 2015 11:56:19 PM<br class=3D""> VM racclient1 configuration was updated by admin@internal.<br class=3D""> </div> </div> </div> </blockquote> <div><br class=3D""> </div> that=92s correct - the new base for the next run</div> <div><br class=3D""> <blockquote type=3D"cite" class=3D""> <div class=3D""> <div dir=3D"ltr" class=3D""> <div class=3D"gmail_extra">=A0=A0=A0 <br class=3D""> Dec 9, 2015 11:56:18 PM=A0 <br class=3D""> Hotset memory: changed the amount of memory on VM racclient1 from 8192 to 10240<br class=3D""> </div> </div> </div> </blockquote> <div><br class=3D""> </div> that=92s the actual hotplug</div> <div><br class=3D""> <blockquote type=3D"cite" class=3D""> <div class=3D""> <div dir=3D"ltr" class=3D""> <div class=3D"gmail_extra"><br class=3D""> </div> <div class=3D"gmail_extra">It doesn't seem as expected, doe= s it?<br class=3D""> </div> </div> </div> </blockquote> <div><br class=3D""> </div> I think we=92re almost there. Just need to figure out what happened in the guest. I would suspect a problem there</div> </blockquote> I did the same test, I obtain the same result but here is what I get into the /var/log/messages guest (7.1) logs and not mentionned there:<br> unsupported configuration: maxMemory has to be specified when using memory devices<br> What can't I do with this error, is it a known issue?<br> <blockquote cite=3D"mid:F8823B97-23FD-4125-B374-EE3918F3A383@redhat.com" type=3D"cite"> <div><br class=3D""> </div> <div>Thanks,</div> <div>michal</div> <div><br class=3D""> <blockquote type=3D"cite" class=3D""> <div class=3D""> <div dir=3D"ltr" class=3D""> <div class=3D"gmail_extra">Gianluca<br class=3D""> </div> <div class=3D"gmail_extra"><br class=3D""> </div> </div> </div> </blockquote> </div> <br class=3D""> <br> <fieldset class=3D"mimeAttachmentHeader"></fieldset> <br> <pre wrap=3D"">_______________________________________________ Users mailing list <a class=3D"moz-txt-link-abbreviated" href=3D"mailto:Users@ovirt.org">Use= rs@ovirt.org</a> <a class=3D"moz-txt-link-freetext" href=3D"http://lists.ovirt.org/mailman= /listinfo/users">http://lists.ovirt.org/mailman/listinfo/users</a> </pre> </blockquote> <br> <pre class=3D"moz-signature" cols=3D"72">--=20 Nathana=EBl Blanchet Supervision r=E9seau P=F4le Infrastrutures Informatiques 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 =09 T=E9l. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 <a class=3D"moz-txt-link-abbreviated" href=3D"mailto:blanchet@abes.fr">bl= anchet@abes.fr</a> </pre> </body> </html> --------------080701070002030103070807--