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