subject:"\[ovirt\-users\] hot plug memory in el7"

Re: [ovirt-users] hot plug memory in el7

2015-12-10 Thread Michal Skrivanek


> On 10 Dec 2015, at 00:11, Gianluca Cecchi  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=4726 
>  ? 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 
> hypervisor configured with SelfHostedEngine
> I have a CentOS 7.1 vm running.
> 
> On hypervisor I shutdown VM, put maintenance global and shutdown engine VM.
> Then
> [root@ractor ~]# yum --enablerepo=cr 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 
>  * extras: centos.fastbull.org 
>  * ovirt-3.6: ftp.nluug.nl 
>  * ovirt-3.6-epel: epel.besthosting.ua 
>  * updates: 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 update
> --> Processing Dependency: libsystemd.so.0(LIBSYSTEMD_209)(64bit) for 
> package: libvirt-client-1.2.17-13.el7_2.2.x86_64
> --> Processing Dependency: libsystemd.so.0()(64bit) for package: 
> 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 update
> ---> Package libvirt-daemon-config-nwfilter.x86_64 0:1.2.8-16.el7_1.5 will be 
> updated
> ---> Package libvirt-daemon-config-nwfilter.x86_64 0:1.2.17-13.el7_2.2 will 
> be an update
> ---> Package libvirt-daemon-driver-interface.x86_64 0:1.2.8-16.el7_1.5 will 
> be updated
> ---> Package libvirt-daemon-driver-interface.x86_64 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 will be 
> updated
> ---> Package libvirt-daemon-driver-network.x86_64 0:1.2.17-13.el7_2.2 will be 
> an update
> ---> Package libvirt-daemon-driver-nodedev.x86_64 0:1.2.8-16.el7_1.5 will be 
> updated
> ---> Package libvirt-daemon-driver-nodedev.x86_64 0:1.2.17-13.el7_2.2 will be 
> an update
> ---> Package libvirt-daemon-driver-nwfilter.x86_64 0:1.2.8-16.el7_1.5 will be 
> updated
> ---> Package libvirt-daemon-driver-nwfilter.x86_64 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 will be 
> updated
> ---> Package libvirt-daemon-driver-qemu.x86_64 0:1.2.17-13.el7_2.2 will be an 
> update
> ---> Package libvirt-daemon-driver-secret.x86_64 0:1.2.8-16.el7_1.5 will be 
> updated
> ---> Package libvirt-daemon-driver-secret.x86_64 0:1.2.17-13.el7_2.2 will be 
> an update
> ---> Package libvirt-daemon-driver-storage.x86_64 0:1.2.8-16.el7_1.5 will be 
> updated
> ---> Package libvirt-daemon-driver-storage.x86_64 0:1.2.17-13.el7_2.2 will be 
> an update
> --> 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
> ---> Package libvirt-daemon-kvm.x86_64 0:1.2.8-16.el7_1.5 will be updated
> ---> Package libvirt-daemon-kvm.x86_64 0:1.2.17-13.el7_2.2 will be an update
> ---> Package libvirt-lock-sanlock.x86_64 0:1.2.8-16.el7_1.5 will be updated
> ---> Package libvirt-lock-sanlock.x86_64 0:1.2.17-13.el7_2.2 will be 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 updated
> --> 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
> ---> Package device-mapper-libs.x86_64 7:1.02.107-5.el7 will be an update
> ---> Package systemd-libs.x86_64 0:208-20.el7_1.6 will be updated
> --> Processing Dependency: systemd-libs = 208-20.el7_1.6 for package: 
> 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 = 7:1.02.93-3.el7_1.1 for 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

Re: [ovirt-users] hot plug memory in el7

2015-12-10 Thread Nathanaël Blanchet




Le 10/12/2015 10:41, Michal Skrivanek a écrit :


On 10 Dec 2015, at 00:11, Gianluca Cecchi > 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=4726 ? 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 
hypervisor configured with SelfHostedEngine

I have a CentOS 7.1 vm running.

On hypervisor I shutdown VM, put maintenance global and shutdown 
engine VM.

Then
[root@ractor ~]# yum --enablerepo=cr 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 
 * extras: centos.fastbull.org 
 * ovirt-3.6: ftp.nluug.nl 
 * ovirt-3.6-epel: epel.besthosting.ua 
 * updates: 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 update
--> Processing Dependency: libsystemd.so.0(LIBSYSTEMD_209)(64bit) for 
package: libvirt-client-1.2.17-13.el7_2.2.x86_64
--> Processing Dependency: libsystemd.so.0()(64bit) for package: 
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 update
---> Package libvirt-daemon-config-nwfilter.x86_64 0:1.2.8-16.el7_1.5 
will be updated
---> Package libvirt-daemon-config-nwfilter.x86_64 
0:1.2.17-13.el7_2.2 will be an update
---> Package libvirt-daemon-driver-interface.x86_64 
0:1.2.8-16.el7_1.5 will be updated
---> Package libvirt-daemon-driver-interface.x86_64 
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 
will be updated
---> Package libvirt-daemon-driver-network.x86_64 0:1.2.17-13.el7_2.2 
will be an update
---> Package libvirt-daemon-driver-nodedev.x86_64 0:1.2.8-16.el7_1.5 
will be updated
---> Package libvirt-daemon-driver-nodedev.x86_64 0:1.2.17-13.el7_2.2 
will be an update
---> Package libvirt-daemon-driver-nwfilter.x86_64 0:1.2.8-16.el7_1.5 
will be updated
---> Package libvirt-daemon-driver-nwfilter.x86_64 
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 
will be updated
---> Package libvirt-daemon-driver-qemu.x86_64 0:1.2.17-13.el7_2.2 
will be an update
---> Package libvirt-daemon-driver-secret.x86_64 0:1.2.8-16.el7_1.5 
will be updated
---> Package libvirt-daemon-driver-secret.x86_64 0:1.2.17-13.el7_2.2 
will be an update
---> Package libvirt-daemon-driver-storage.x86_64 0:1.2.8-16.el7_1.5 
will be updated
---> Package libvirt-daemon-driver-storage.x86_64 0:1.2.17-13.el7_2.2 
will be an update
--> 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

---> Package libvirt-daemon-kvm.x86_64 0:1.2.8-16.el7_1.5 will be updated
---> Package libvirt-daemon-kvm.x86_64 0:1.2.17-13.el7_2.2 will be an 
update
---> Package libvirt-lock-sanlock.x86_64 0:1.2.8-16.el7_1.5 will be 
updated
---> Package libvirt-lock-sanlock.x86_64 0:1.2.17-13.el7_2.2 will be 
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 
updated
--> 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

---> Package device-mapper-libs.x86_64 7:1.02.107-5.el7 will be an update
---> Package systemd-libs.x86_64 0:208-20.el7_1.6 will be updated
--> Processing Dependency: systemd-libs = 208-20.el7_1.6 for package: 
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 = 7:1.02.93-3.el7_1.1 for 
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 = 208-20.el7_1.6 for package: 
systemd-sysv-208-20.el7_1.6.x86_64
--> Processing Dependency: systemd = 208-20.el7_1.6 for package: 
systemd-python-208-20.el7_1.6.x86_64
--> Processing Dependency: systemd = 208-20.el7_1.6 for package: 
libgudev1-208-20.el7_1.6.x86_64

--->

Re: [ovirt-users] hot plug memory in el7

2015-12-10 Thread Michal Skrivanek


> On 10 Dec 2015, at 11:30, Gianluca Cecchi  wrote:
> 
> On Thu, Dec 10, 2015 at 10:41 AM, Michal Skrivanek  
> wrote:
> 
>> On 10 Dec 2015, at 00:11, Gianluca Cecchi  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=4726 ? 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/.
>> 
>> 
>> 
>> 
>> Then I reboot my HV, exit from maintenance, connect to engine and start VM.
>> VM situation
>> $ free
>>   totalusedfree  shared  buff/cache   
>> available
>> Mem:8172900  147356 78756928480  149852 
>> 7847248
>> 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 
>> /var/log/messages:
> 
> could it be perhaps the guest has troubles recognizing hotplug? Is it also a 
> CentOS 7.1 guest?
> 
> Yes, CentOS 7.1 updated up to a couple of days ago.

Can you try 7.2? I don’t remember exactly but it may be that in earlier guests 
it’s not automatic. Check some tips for onlining memory explicitly

5.2. How to online memory
 
Even if the memory is hot-added, it is not at ready-to-use state.
For using newly added memory, you have to "online" the memory block.
 
For onlining, you have to write "online" to the memory block's state file as:
 
% echo online > /sys/devices/system/memory/memoryXXX/state



> 
>   
> 
>> 
>> Dec  9 23:56:18 racclient1 kernel: init_memory_mapping: [mem 
>> 0x24000-0x2bfff]
>> 
>> ANd output of dmesg contains:
>> 
>> [  219.363640] ACPI: \_SB_.MP00: ACPI_NOTIFY_DEVICE_CHECK event
>> [  219.364248] init_memory_mapping: [mem 0x24000-0x2bfff]
>> [  219.364253]  [mem 0x24000-0x2bfff] page 2M
>> [  219.366773]  [ea000900-ea00091f] PMD -> 
>> [8800b7e0-8800b7ff] on node 0
>> [  219.368433]  [ea000920-ea00093f] PMD -> 
>> [88023140-8802315f] on node 0
>> [  219.369838]  [ea000940-ea00095f] PMD -> 
>> [88023360-8802337f] on node 0
>> [  219.371226]  [ea000960-ea00097f] PMD -> 
>> [88023300-8802331f] on node 0
>> [  219.372790]  [ea000980-ea00099f] PMD -> 
>> [880232c0-880232df] on node 0
>> [  219.374185]  [ea0009a0-ea0009bf] PMD -> 
>> [88023220-8802323f] on node 0
>> [  219.377349]  [ea0009c0-ea0009ff] PMD -> 
>> [8800b740-8800b77f] on node 0
>> [  219.378716]  [ea000a00-ea000a1f] PMD -> 
>> [8800b700-8800b71f] on node 0
>> [  219.380115]  [ea000a20-ea000a3f] PMD -> 
>> [880230c0-880230df] on node 0
>> [  219.388147]  [ea000a40-ea000abf] PMD -> 
>> [880227c0-8802283f] on node 0
>> [  219.389687]  [ea000ac0-ea000adf] PMD -> 
>> [8800b720-8800b73f] on node 0
> 
> but “free” sstill shows the same value as before hotplug?
> 
> 
> Yes, output of "free" command show the same amount of memory
> 
>   
> 
>> 
>> I then shutdown the VM and power on it again and I get the changed memory:
> 
> well, yeah, but that doesn’t count since you’ve shut it down, so the next run 
> is initialized with 10GB
> 
> 
> It was only to verify that after shutdown/power on the changed setting would 
> have been applied to the VM
>  
>> $ free
>>   totalusedfree  shared  buff/cache   
>> available
>> Mem:   10237276  167872 99196568480  149748 
>> 9891280
>> Swap:839676   0  839676
>> 
>> BTW: When I press ok in the gui for memory increase I get these events in 
>> webadmin:
>> Dec 9, 2015 11:56:22 PM
>> VM racclient1 c71_Disk1_newtemplate disk was updated by admin@internal.
> 
> hm..doesn’t sound right. Did the confirmation window show any more fields as 
> changed other than memory?
> 
> The window I got when I increased the amount of memory was the same as in a 
> previous test where I selected "Cancel", before libvirt update; see
> https://drive.google.com/file/d/0BwoPbcrMv8mvbUw2VnpCMTNNQlU/view?usp=sharing
> 
> And I also commented about misleading information inside it: I didn't clearly 
> understand what would have been changed and what not, because I see memory 
> information in both parts…..

I agree it’s confusing. Please do open a bug on that

Thanks,
michal

> 
>> 
>> It doesn't seem as expected, does it?
> 
> I think we’re almost there. Just need to figure out what

Re: [ovirt-users] hot plug memory in el7

2015-12-10 Thread Gianluca Cecchi

On Thu, Dec 10, 2015 at 11:31 AM, Nathanaël Blanchet 
wrote:

>
>
> 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:
> unsupported configuration: maxMemory has to be specified when using memory
> devices
> What can't I do with this error, is it a known issue?
>
>
In my case I only got the line I wrote in previous e-mail when I click ok
in web gui to increase memory:
Dec  9 23:56:18 racclient1 kernel: init_memory_mapping: [mem
0x24000-0x2bfff]

See here the messages boot related lines for my guest, just before I tried
to increase memory, in case they can be useful:

https://drive.google.com/file/d/0BwoPbcrMv8mvNnFmUDMybXpla1E/view?usp=sharing

BTW: Nathanaël did you increase by 256Mb multiples? I see this is a sort of
limitation... what was previous amount of ram of VM and the tried new
setting?
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] hot plug memory in el7

2015-12-10 Thread Gianluca Cecchi

On Thu, Dec 10, 2015 at 10:41 AM, Michal Skrivanek 
wrote:

>
> On 10 Dec 2015, at 00:11, Gianluca Cecchi 
> 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=4726 ? 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/.
>>
>>
>>
>
> Then I reboot my HV, exit from maintenance, connect to engine and start VM.
> VM situation
> $ free
>   totalusedfree  shared  buff/cache
> available
> Mem:8172900  147356 78756928480  149852
> 7847248
> 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
> /var/log/messages:
>
>
> could it be perhaps the guest has troubles recognizing hotplug? Is it also
> a CentOS 7.1 guest?
>

Yes, CentOS 7.1 updated up to a couple of days ago.



>
>
> Dec  9 23:56:18 racclient1 kernel: init_memory_mapping: [mem
> 0x24000-0x2bfff]
>
> ANd output of dmesg contains:
>
> [  219.363640] ACPI: \_SB_.MP00: ACPI_NOTIFY_DEVICE_CHECK event
> [  219.364248] init_memory_mapping: [mem 0x24000-0x2bfff]
> [  219.364253]  [mem 0x24000-0x2bfff] page 2M
> [  219.366773]  [ea000900-ea00091f] PMD ->
> [8800b7e0-8800b7ff] on node 0
> [  219.368433]  [ea000920-ea00093f] PMD ->
> [88023140-8802315f] on node 0
> [  219.369838]  [ea000940-ea00095f] PMD ->
> [88023360-8802337f] on node 0
> [  219.371226]  [ea000960-ea00097f] PMD ->
> [88023300-8802331f] on node 0
> [  219.372790]  [ea000980-ea00099f] PMD ->
> [880232c0-880232df] on node 0
> [  219.374185]  [ea0009a0-ea0009bf] PMD ->
> [88023220-8802323f] on node 0
> [  219.377349]  [ea0009c0-ea0009ff] PMD ->
> [8800b740-8800b77f] on node 0
> [  219.378716]  [ea000a00-ea000a1f] PMD ->
> [8800b700-8800b71f] on node 0
> [  219.380115]  [ea000a20-ea000a3f] PMD ->
> [880230c0-880230df] on node 0
> [  219.388147]  [ea000a40-ea000abf] PMD ->
> [880227c0-8802283f] on node 0
> [  219.389687]  [ea000ac0-ea000adf] PMD ->
> [8800b720-8800b73f] on node 0
>
>
> but “free” sstill shows the same value as before hotplug?
>


Yes, output of "free" command show the same amount of memory



>
>
> I then shutdown the VM and power on it again and I get the changed memory:
>
>
> well, yeah, but that doesn’t count since you’ve shut it down, so the next
> run is initialized with 10GB
>
>
It was only to verify that after shutdown/power on the changed setting
would have been applied to the VM


> $ free
>   totalusedfree  shared  buff/cache
> available
> Mem:   10237276  167872 99196568480  149748
> 9891280
> Swap:839676   0  839676
>
> BTW: When I press ok in the gui for memory increase I get these events in
> webadmin:
> Dec 9, 2015 11:56:22 PM
> VM racclient1 c71_Disk1_newtemplate disk was updated by admin@internal.
>
>
> hm..doesn’t sound right. Did the confirmation window show any more fields
> as changed other than memory?
>

The window I got when I increased the amount of memory was the same as in a
previous test where I selected "Cancel", before libvirt update; see
https://drive.google.com/file/d/0BwoPbcrMv8mvbUw2VnpCMTNNQlU/view?usp=sharing

And I also commented about misleading information inside it: I didn't
clearly understand what would have been changed and what not, because I see
memory information in both parts.

>
>
> It doesn't seem as expected, does it?
>
>
> I think we’re almost there. Just need to figure out what happened in the
> guest. I would suspect a problem there
>
> Thanks,
> michal
>
> Gianluca
>
>
>

The gui events have the same timestamp of the moment when I pressed ok.
After 2-3 minutes I did shutdown and power on of the VM and I only got the
down/up events...
I'm available to make further test you need.

GIanluca
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] hot plug memory in el7

2015-12-10 Thread Gianluca Cecchi

On Thu, Dec 10, 2015 at 12:24 PM, Michal Skrivanek 
wrote:

>
>
> >
> > Yes, CentOS 7.1 updated up to a couple of days ago.
>
> Can you try 7.2? I don’t remember exactly but it may be that in earlier
> guests it’s not automatic. Check some tips for onlining memory explicitly
>
> 5.2. How to online memory
>  
> Even if the memory is hot-added, it is not at ready-to-use state.
> For using newly added memory, you have to "online" the memory block.
>
> For onlining, you have to write "online" to the memory block's state file
> as:
>
> % echo online > /sys/devices/system/memory/memoryXXX/state
>
>

Hello,
with your suggestions it worked as expected, without updating any packages
in VM 7.1 guest (I seemed to remember that the forced online operation
should not be necessary any more...):

Starting state with 10Gb of ram inside the VM
[root@racclient1 ~]# ll -d  /sys/devices/system/memory/memory* | wc -l
80

slots defined:
0 --> 23
32 --> 87

Increase from web gui memory from 10240 to 12288

I see this in messages as expected

Dec 10 12:59:32 racclient1 kernel: init_memory_mapping: [mem
0x2c000-0x33fff]

In /sys/devices/system/memory I see 16 new memoryxx directories (probably
each one addressing 128Mb...)

88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103

They have indeed been added but are offline, eg

latest previous one:
[root@racclient1 ~]# cat /sys/devices/system/memory/memory87/state
online

first newly added one:
[root@racclient1 ~]# cat /sys/devices/system/memory/memory88/state
offline

[root@racclient1 ~]# cat /sys/devices/system/memory/memory87/online
1
[root@racclient1 ~]# cat /sys/devices/system/memory/memory88/online
0

put online the new segments:
[root@racclient1 ~]# for i in $(seq 88 103)
> do
> echo online > /sys/devices/system/memory/memory${i}/state
> done

Memory has been increased now, also from inside the OS.

[root@racclient1 ~]# free
  totalusedfree  shared  buff/cache
available
Mem:   12334428  222080119340448480  178304
 12019544

NOTE: no new entries after online memory, neither in messages file nor in
dmesg output.

Questions:
1) which component to bugzilla against for message confusing window of the
gui?
2) Initially I see that my VM (in webadmin gui) has 8Gb of defined memory
AND 8Gb of "Physical Memory Guaranteed".
After increasing memory, the second one remains the same and doesn't change
even after shutdown / Power on.
I think it could be an enhancement to ask the user if he/she wants to
change it too, instead of manually go through
Edit --> resource allocation --> memory allocation screen
If seen as a agreed enhancement, which components to bugzilla against for
RFE?
Gianluca
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] hot plug memory in el7

2015-12-10 Thread Nathanaël Blanchet

- Mail d'origine -
De: Gianluca Cecchi <gianluca.cec...@gmail.com>
À: Nathanaël Blanchet <blanc...@abes.fr>
Cc: users <users@ovirt.org>
Envoyé: Thu, 10 Dec 2015 11:49:58 +0100 (CET)
Objet: Re: [ovirt-users] hot plug memory in el7

On Thu, Dec 10, 2015 at 11:31 AM, Nathanaël Blanchet <blanc...@abes.fr>
wrote:

>
>
> 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:
> unsupported configuration: maxMemory has to be specified when using memory
> devices
> What can't I do with this error, is it a known issue?
>
>
In my case I only got the line I wrote in previous e-mail when I click ok
in web gui to increase memory:
Dec  9 23:56:18 racclient1 kernel: init_memory_mapping: [mem
0x24000-0x2bfff]

See here the messages boot related lines for my guest, just before I tried
to increase memory, in case they can be useful:

https://drive.google.com/file/d/0BwoPbcrMv8mvNnFmUDMybXpla1E/view?usp=sharing

BTW: Nathanaël did you increase by 256Mb multiples? I see this is a sort of
limitation... what was previous amount of ram of VM and the tried new
setting?

Yes the initial memory was set to 1024mb and I increased to 2048.

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] hot plug memory in el7

2015-12-10 Thread Michal Skrivanek


> On 10 Dec 2015, at 13:16, Gianluca Cecchi  wrote:
> 
> On Thu, Dec 10, 2015 at 12:24 PM, Michal Skrivanek  > wrote:
> 
> 
> >
> > Yes, CentOS 7.1 updated up to a couple of days ago.
> 
> Can you try 7.2? I don’t remember exactly but it may be that in earlier 
> guests it’s not automatic. Check some tips for onlining memory explicitly
> 
> 5.2. How to online memory
>  
> Even if the memory is hot-added, it is not at ready-to-use state.
> For using newly added memory, you have to "online" the memory block.
> 
> For onlining, you have to write "online" to the memory block's state file as:
> 
> % echo online > /sys/devices/system/memory/memoryXXX/state
> 
>  
> 
> Hello,
> with your suggestions it worked as expected, without updating any packages in 
> VM 7.1 guest (I seemed to remember that the forced online operation should 
> not be necessary any more…):

great!
with 7.2 it should be automatic. I think with Windows it works automatically as 
well.

> 
> Starting state with 10Gb of ram inside the VM
> [root@racclient1 ~]# ll -d  /sys/devices/system/memory/memory* | wc -l
> 80
> 
> slots defined:
> 0 --> 23
> 32 --> 87
> 
> Increase from web gui memory from 10240 to 12288
> 
> I see this in messages as expected
> 
> Dec 10 12:59:32 racclient1 kernel: init_memory_mapping: [mem 
> 0x2c000-0x33fff]
> 
> In /sys/devices/system/memory I see 16 new memoryxx directories (probably 
> each one addressing 128Mb...)
> 
> 88
> 89
> 90
> 91
> 92
> 93
> 94
> 95
> 96
> 97
> 98
> 99
> 100
> 101
> 102
> 103
> 
> They have indeed been added but are offline, eg
> 
> latest previous one:
> [root@racclient1 ~]# cat /sys/devices/system/memory/memory87/state 
> online
> 
> first newly added one:
> [root@racclient1 ~]# cat /sys/devices/system/memory/memory88/state 
> offline
> 
> [root@racclient1 ~]# cat /sys/devices/system/memory/memory87/online 
> 1
> [root@racclient1 ~]# cat /sys/devices/system/memory/memory88/online 
> 0
> 
> put online the new segments:
> [root@racclient1 ~]# for i in $(seq 88 103)
> > do
> > echo online > /sys/devices/system/memory/memory${i}/state
> > done
> 
> Memory has been increased now, also from inside the OS.
> 
> [root@racclient1 ~]# free
>   totalusedfree  shared  buff/cache   
> available
> Mem:   12334428  222080119340448480  178304
> 12019544
> 
> 
> NOTE: no new entries after online memory, neither in messages file nor in 
> dmesg output.
> 
> Questions:
> 1) which component to bugzilla against for message confusing window of the 
> gui?

doesn’t matter much, ovirt-engine, frontend.

> 2) Initially I see that my VM (in webadmin gui) has 8Gb of defined memory AND 
> 8Gb of "Physical Memory Guaranteed".
> After increasing memory, the second one remains the same and doesn't change 
> even after shutdown / Power on.

> I think it could be an enhancement to ask the user if he/she wants to change 
> it too, instead of manually go through 
> Edit --> resource allocation --> memory allocation screen
> If seen as a agreed enhancement, which components to bugzilla against for RFE?

yeah, these are two separate fields. The suggestion sounds reasonable to me, 
Roy, thoughts on that?

> Gianluca

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] hot plug memory in el7

2015-12-10 Thread Gianluca Cecchi

On Thu, Dec 10, 2015 at 2:35 PM, Michal Skrivanek 
wrote:

>
>
> great!
> with 7.2 it should be automatic. I think with Windows it works
> automatically as well.
>
>
In the mean time I tested how to make it automatic also in my CentOS 7.1
guest.

I temporarily added this rule
inside /lib/udev/rules.d/55-ovirt-guest-agent.rules (but it could have also
been a plain new file for that matter):

SUBSYSTEM=="memory", ACTION=="add", TEST=="state", ATTR{state}=="offline",
ATTR{state}="online"

With this row the addition is automatically intercepted and applied from
the OS too.
Tested changing from 8Gb to 10Gb of ram.

I'm not an udev guru I took inspiration form the already set up file
for cpu adition in 40-redhat.rules file.. ;-)

So perhaps the only change in 7.2 is an addition like mine in
40-redhat.rules?

>
>
> Questions:
> 1) which component to bugzilla against for message confusing window of the
> gui?
>
>
> doesn’t matter much, ovirt-engine, frontend.
>

Ok, I'll do

> Gianluca
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] hot plug memory in el7

2015-12-10 Thread Michal Skrivanek


> On 10 Dec 2015, at 15:12, Gianluca Cecchi  wrote:
> 
> On Thu, Dec 10, 2015 at 2:35 PM, Michal Skrivanek  > wrote:
> 
> 
> great!
> with 7.2 it should be automatic. I think with Windows it works automatically 
> as well.
> 
> 
> In the mean time I tested how to make it automatic also in my CentOS 7.1 
> guest.
> 
> I temporarily added this rule inside 
> /lib/udev/rules.d/55-ovirt-guest-agent.rules (but it could have also been a 
> plain new file for that matter):
> 
> SUBSYSTEM=="memory", ACTION=="add", TEST=="state", ATTR{state}=="offline", 
> ATTR{state}="online"
> 
> With this row the addition is automatically intercepted and applied from the 
> OS too.
> Tested changing from 8Gb to 10Gb of ram.
> 
> I'm not an udev guru I took inspiration form the already set up file for 
> cpu adition in 40-redhat.rules file.. ;-)

me neither, but yeah, it’s in 7.2 just like that:)

# cat /lib/udev/rules.d/40-redhat.rules
# do not edit this file, it will be overwritten on update

# CPU hotadd request
SUBSYSTEM=="cpu", ACTION=="add", TEST=="online", ATTR{online}=="0", 
ATTR{online}="1"

# Memory hotadd request
SUBSYSTEM=="memory", ACTION=="add", ATTR{state}=="offline", ATTR{state}="online"

# reload sysctl.conf / sysctl.conf.d settings when the bridge module is loaded
ACTION=="add", SUBSYSTEM=="module", KERNEL=="bridge", 
RUN+="/usr/lib/systemd/systemd-sysctl --prefix=/proc/sys/net/bridge"

# load SCSI generic (sg) driver
SUBSYSTEM=="scsi", ENV{DEVTYPE}=="scsi_device", TEST!="[module/sg]", 
RUN+="/sbin/modprobe -bv sg"

# Rule for prandom character device node permissions
KERNEL=="prandom", MODE=“0644"

> 
> So perhaps the only change in 7.2 is an addition like mine in 40-redhat.rules?
>  
>> 
>> 
>> Questions:
>> 1) which component to bugzilla against for message confusing window of the 
>> gui?
> 
> doesn’t matter much, ovirt-engine, frontend.
> 
> Ok, I'll do
> 
>  
> Gianluca

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] hot plug memory in el7

2015-12-09 Thread Nathanaël Blanchet




Le 08/12/2015 11:43, Michal Skrivanek a écrit :



On 08 Dec 2015, at 11:20, Yaniv Dary > wrote:





Yaniv Dary Technical Product Manager Red Hat Israel Ltd. 34 Jerusalem 
Road Building A, 4th floor Ra'anana, Israel 4350109 Tel : +972 (9) 
7692306 8272306 Email: yd...@redhat.com  IRC 
: ydary


On Tue, Dec 8, 2015 at 2:03 AM, Nathanaël Blanchet > wrote:


Hi all,

I may miss something but according to
http://www.ovirt.org/Features/Hot_Plug_Memory, ovirt 3.6 was
supposed to support the hot plug memory feature. Nothing happens
in reality when increasing memory on a running vm with centos7.
I found this :
http://lists.ovirt.orgpipermail/kimchi-devel/2015-June/010714.html,
and it seems that el7.1 can't support the feature because of its
libvirt version (1.2.8) while the required one is 1.2.14.
I didn't test, but I guess F22 supports it.
Is there any chance that el7.2 would support it with a backported
libvirtd?


It does support it, but only hot-plug not hot-unplug.

Or will a dedicated libvirt rhev package be released so as the
downstream to support it (like qemu-kvm for live snapshot some
time ago)?
Documentation and limitation of the libvirt version for hot plug
memory are difficult to find in the ovirt wiki and more generally
on the web.
Maybe the feature has been postponed to a 3.6.z release?


I works with fedora and you can use it currently with this feature.


It works on centos too, qemu-kvm-ev 2.3 we distribute in ovirt repo

Hello, no qemu-kvm-ev 2.3 is not enough:
[root@fuji ~]# qemu-img --version
qemu-img version 2.3.0 (qemu-kvm-ev-2.3.0-29.1.el7), Copyright (c) 
2004-2008 Fabrice Bellard

and
vdsm-4.17.10.1-0.el7.centos.noarch

I get this error message each time I try to hot add memory :
Dec  9 11:18:00 fuji journal: unsupported configuration: unknown device 
type 'memory'


I tried to restart vdsmd but it is the same, even on other hosts.

any help will be appreciated, thank you.



Thank you for your help
___
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


--
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
blanc...@abes.fr

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] hot plug memory in el7

2015-12-09 Thread Michal Skrivanek


> On 09 Dec 2015, at 14:54, Nathanaël Blanchet  wrote:
> 
> 
> 
> Le 08/12/2015 11:43, Michal Skrivanek a écrit :
>> 
>> 
>> On 08 Dec 2015, at 11:20, Yaniv Dary < 
>> yd...@redhat.com > wrote:
>> 
>>> 
>>> 
>>> Yaniv Dary
>>> Technical Product Manager
>>> Red Hat Israel Ltd.
>>> 34 Jerusalem Road
>>> Building A, 4th floor
>>> Ra'anana, Israel 4350109
>>> 
>>> Tel : +972 (9) 7692306
>>> 8272306
>>> Email: yd...@redhat.com 
>>> IRC : ydary
>>> 
>>> On Tue, Dec 8, 2015 at 2:03 AM, Nathanaël Blanchet < 
>>> blanc...@abes.fr > wrote:
>>> Hi all,
>>> 
>>> I may miss something but according to  
>>> http://www.ovirt.org/Features/Hot_Plug_Memory
>>>  , ovirt 3.6 was supposed to 
>>> support the hot plug memory feature. Nothing happens in reality when 
>>> increasing memory on a running vm with centos7.
>>> I found this : 
>>> http://lists.ovirt.orgpipermail/kimchi-devel/2015-June/010714.html 
>>> , and 
>>> it seems that el7.1 can't support the feature because of its libvirt 
>>> version (1.2.8) while the required one is 1.2.14.
>>> I didn't test, but I guess F22 supports it.
>>> Is there any chance that el7.2 would support it with a backported libvirtd?
>>> 
>>> It does support it, but only hot-plug not hot-unplug.
>>>  
>>> Or will a dedicated libvirt rhev package be released so as the downstream 
>>> to support it (like qemu-kvm for live snapshot some time ago)?
>>> Documentation and limitation of the libvirt version for hot plug memory are 
>>> difficult to find in the ovirt wiki and more generally on the web.
>>> Maybe the feature has been postponed to a 3.6.z release?
>>> 
>>> I works with fedora and you can use it currently with this feature.
>> 
>> It works on centos too, qemu-kvm-ev 2.3 we distribute in ovirt repo
> Hello, no qemu-kvm-ev 2.3 is not enough:
> [root@fuji ~]# qemu-img --version
> qemu-img version 2.3.0 (qemu-kvm-ev-2.3.0-29.1.el7), Copyright (c) 2004-2008 
> Fabrice Bellard
> and
> vdsm-4.17.10.1-0.el7.centos.noarch
> 
> I get this error message each time I try to hot add memory :
> Dec  9 11:18:00 fuji journal: unsupported configuration: unknown device type 
> ‘memory'

was the VM started in a 3.6 cluster? 
Or how/when did you create it?

Thanks,
michal

> 
> I tried to restart vdsmd but it is the same, even on other hosts.
> 
> any help will be appreciated, thank you.
>> 
>>>  
>>> Thank you for your help
>>> ___
>>> 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 
>>> 
> 
> -- 
> 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
> blanc...@abes.fr  

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] hot plug memory in el7

2015-12-09 Thread Nathanaël Blanchet




Le 09/12/2015 17:12, Michal Skrivanek a écrit :


On 09 Dec 2015, at 14:54, Nathanaël Blanchet > wrote:




Le 08/12/2015 11:43, Michal Skrivanek a écrit :



On 08 Dec 2015, at 11:20, Yaniv Dary  wrote:




Yaniv Dary Technical Product Manager Red Hat Israel Ltd. 34 
Jerusalem Road Building A, 4th floor Ra'anana, Israel 4350109 Tel : 
+972 (9) 7692306 8272306 Email: yd...@redhat.com 
 IRC : ydary


On Tue, Dec 8, 2015 at 2:03 AM, Nathanaël Blanchet 
 wrote:


Hi all,

I may miss something but according to
http://www.ovirt.org/Features/Hot_Plug_Memory, ovirt 3.6 was
supposed to support the hot plug memory feature. Nothing
happens in reality when increasing memory on a running vm with
centos7.
I found this :
http://lists.ovirt.orgpipermail/kimchi-devel/2015-June/010714.html,
and it seems that el7.1 can't support the feature because of
its libvirt version (1.2.8) while the required one is 1.2.14.
I didn't test, but I guess F22 supports it.
Is there any chance that el7.2 would support it with a
backported libvirtd?


It does support it, but only hot-plug not hot-unplug.

Or will a dedicated libvirt rhev package be released so as the
downstream to support it (like qemu-kvm for live snapshot some
time ago)?
Documentation and limitation of the libvirt version for hot
plug memory are difficult to find in the ovirt wiki and more
generally on the web.
Maybe the feature has been postponed to a 3.6.z release?


I works with fedora and you can use it currently with this feature.


It works on centos too, qemu-kvm-ev 2.3 we distribute in ovirt repo

Hello, no qemu-kvm-ev 2.3 is not enough:
[root@fuji ~]# qemu-img --version
qemu-img version 2.3.0 (qemu-kvm-ev-2.3.0-29.1.el7), Copyright (c) 
2004-2008 Fabrice Bellard

and
vdsm-4.17.10.1-0.el7.centos.noarch

I get this error message each time I try to hot add memory :
Dec  9 11:18:00 fuji journal: unsupported configuration: unknown 
device type ‘memory'


was the VM started in a 3.6 cluster?
sure, on a full 3.6 cluster. I stopped/restarted them. I restarted vdsmd 
and libvirtd

Or how/when did you create it?
those vms have been created before uprading to 3.6, some of them from a 
blank template, other one based on a el7 template.


Thanks,
michal



I tried to restart vdsmd but it is the same, even on other hosts.

any help will be appreciated, thank you.



Thank you for your help
___
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


--
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
blanc...@abes.fr  




--
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
blanc...@abes.fr

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] hot plug memory in el7

2015-12-09 Thread Nathanaël Blanchet




Le 09/12/2015 18:00, Michal Skrivanek a écrit :


On 09 Dec 2015, at 17:54, Nathanaël Blanchet > wrote:




Le 09/12/2015 17:12, Michal Skrivanek a écrit :


On 09 Dec 2015, at 14:54, Nathanaël Blanchet > wrote:




Le 08/12/2015 11:43, Michal Skrivanek a écrit :



On 08 Dec 2015, at 11:20, Yaniv Dary  wrote:




Yaniv Dary Technical Product Manager Red Hat Israel Ltd. 34 
Jerusalem Road Building A, 4th floor Ra'anana, Israel 4350109 Tel 
: +972 (9) 7692306 8272306 Email: yd...@redhat.com 
 IRC : ydary


On Tue, Dec 8, 2015 at 2:03 AM, Nathanaël Blanchet 
 wrote:


Hi all,

I may miss something but according to
http://www.ovirt.org/Features/Hot_Plug_Memory, ovirt 3.6 was
supposed to support the hot plug memory feature. Nothing
happens in reality when increasing memory on a running vm
with centos7.
I found this :
http://lists.ovirt.orgpipermail/kimchi-devel/2015-June/010714.html,
and it seems that el7.1 can't support the feature because of
its libvirt version (1.2.8) while the required one is 1.2.14.
I didn't test, but I guess F22 supports it.
Is there any chance that el7.2 would support it with a
backported libvirtd?


It does support it, but only hot-plug not hot-unplug.

Or will a dedicated libvirt rhev package be released so as
the downstream to support it (like qemu-kvm for live snapshot
some time ago)?
Documentation and limitation of the libvirt version for hot
plug memory are difficult to find in the ovirt wiki and more
generally on the web.
Maybe the feature has been postponed to a 3.6.z release?


I works with fedora and you can use it currently with this feature.


It works on centos too, qemu-kvm-ev 2.3 we distribute in ovirt repo

Hello, no qemu-kvm-ev 2.3 is not enough:
[root@fuji ~]# qemu-img --version
qemu-img version 2.3.0 (qemu-kvm-ev-2.3.0-29.1.el7), Copyright (c) 
2004-2008 Fabrice Bellard

and
vdsm-4.17.10.1-0.el7.centos.noarch

I get this error message each time I try to hot add memory :
Dec  9 11:18:00 fuji journal: unsupported configuration: unknown 
device type ‘memory'


was the VM started in a 3.6 cluster?
sure, on a full 3.6 cluster. I stopped/restarted them. I restarted 
vdsmd and libvirtd


ok..and just for the sake of completeness - what is libvirt version 
exactly? If you’re running <1.2.14 then your initial comment make a 
lot of sense….
Yes, el7.2 has the right one (1.2.17) but even on 7.1 it should 
support it and if it doesn’t it’s our problem we should fix in ovirt 
(similarly as we solve qemu by shipping it ourselves)

libvirt-daemon-1.2.8-16.el7_1.5.x86_64
I'm really surprised that such a waited feature has not been yet tested 
by the community users with el7, so that nobody has reported the issue yet.



Or how/when did you create it?
those vms have been created before uprading to 3.6, some of them from 
a blank template, other one based on a el7 template.


Thanks,
michal



I tried to restart vdsmd but it is the same, even on other hosts.

any help will be appreciated, thank you.



Thank you for your help
___
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


--
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
blanc...@abes.fr  




--
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
blanc...@abes.fr  




--
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
blanc...@abes.fr

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] hot plug memory in el7

2015-12-09 Thread Michal Skrivanek



> On 09 Dec 2015, at 18:07, Nathanaël Blanchet  wrote:
> 
> 
> 
> Le 09/12/2015 18:00, Michal Skrivanek a écrit :
>> 
>>> On 09 Dec 2015, at 17:54, Nathanaël Blanchet  wrote:
>>> 
>>> 
>>> 
>>> Le 09/12/2015 17:12, Michal Skrivanek a écrit :
 
> On 09 Dec 2015, at 14:54, Nathanaël Blanchet  wrote:
> 
> 
> 
> Le 08/12/2015 11:43, Michal Skrivanek a écrit :
>> 
>> 
>> On 08 Dec 2015, at 11:20, Yaniv Dary  wrote:
>> 
>>> 
>>> 
>>> Yaniv Dary
>>> Technical Product Manager
>>> Red Hat Israel Ltd.
>>> 34 Jerusalem Road
>>> Building A, 4th floor
>>> Ra'anana, Israel 4350109
>>> 
>>> Tel : +972 (9) 7692306
>>> 8272306
>>> Email: yd...@redhat.com
>>> IRC : ydary
>>> 
 On Tue, Dec 8, 2015 at 2:03 AM, Nathanaël Blanchet  
 wrote:
 Hi all,
 
 I may miss something but according to 
 http://www.ovirt.org/Features/Hot_Plug_Memory, ovirt 3.6 was supposed 
 to support the hot plug memory feature. Nothing happens in reality 
 when increasing memory on a running vm with centos7.
 I found this : 
 http://lists.ovirt.orgpipermail/kimchi-devel/2015-June/010714.html, 
 and it seems that el7.1 can't support the feature because of its 
 libvirt version (1.2.8) while the required one is 1.2.14.
 I didn't test, but I guess F22 supports it.
 Is there any chance that el7.2 would support it with a backported 
 libvirtd?
>>> 
>>> It does support it, but only hot-plug not hot-unplug.
>>>  
 Or will a dedicated libvirt rhev package be released so as the 
 downstream to support it (like qemu-kvm for live snapshot some time 
 ago)?
 Documentation and limitation of the libvirt version for hot plug 
 memory are difficult to find in the ovirt wiki and more generally on 
 the web.
 Maybe the feature has been postponed to a 3.6.z release?
>>> 
>>> I works with fedora and you can use it currently with this feature.
>> 
>> It works on centos too, qemu-kvm-ev 2.3 we distribute in ovirt repo
> Hello, no qemu-kvm-ev 2.3 is not enough:
> [root@fuji ~]# qemu-img --version
> qemu-img version 2.3.0 (qemu-kvm-ev-2.3.0-29.1.el7), Copyright (c) 
> 2004-2008 Fabrice Bellard
> and
> vdsm-4.17.10.1-0.el7.centos.noarch
> 
> I get this error message each time I try to hot add memory :
> Dec  9 11:18:00 fuji journal: unsupported configuration: unknown device 
> type ‘memory'
 
 was the VM started in a 3.6 cluster?
>>> sure, on a full 3.6 cluster. I stopped/restarted them. I restarted vdsmd 
>>> and libvirtd
>> 
>> ok..and just for the sake of completeness - what is libvirt version exactly? 
>> If you’re running <1.2.14 then your initial comment make a lot of sense….
>> Yes, el7.2 has the right one (1.2.17) but even on 7.1 it should support it 
>> and if it doesn’t it’s our problem we should fix in ovirt (similarly as we 
>> solve qemu by shipping it ourselves)
> libvirt-daemon-1.2.8-16.el7_1.5.x86_64
> I'm really surprised that such a waited feature has not been yet tested by 
> the community users with el7, so that nobody has reported the issue yet.

Weird indeed. Well, RHEL 7.2 is out for more than a month and there is centos 
7.2 beta and perhaps rc as well, it's due very soon
Sandro, we should think about it - since we push qemu-kvm-ev we do not really 
enforce anyone to run on el7.2. We want to do that for various reasons as soon 
as possible. Maybe updating qemu-kvm-ev to require new 7.2 libvirt?

>> 
 Or how/when did you create it?
>>> those vms have been created before uprading to 3.6, some of them from a 
>>> blank template, other one based on a el7 template.
 
 Thanks,
 michal
 
> 
> I tried to restart vdsmd but it is the same, even on other hosts.
> 
> any help will be appreciated, thank you.
>> 
>>>  
 Thank you for your help
 ___
 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
> 
> -- 
> 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
> blanc...@abes.fr 
>>> 
>>> -- 
>>> 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

Re: [ovirt-users] hot plug memory in el7

2015-12-09 Thread Gianluca Cecchi

I too verified the problem with CentOS 7.1 Hypervisor and CentOS 7.1 VM

BTW: I find the below window somehow misleading when you try te resize the
memory of the vm
https://drive.google.com/file/d/0BwoPbcrMv8mvbUw2VnpCMTNNQlU/view?usp=sharing

Gianluca
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] hot plug memory in el7

2015-12-09 Thread Sandro Bonazzola

On Wed, Dec 9, 2015 at 8:04 PM, Michal Skrivanek 
wrote:

>
>
> On 09 Dec 2015, at 18:07, Nathanaël Blanchet  wrote:
>
>
>
> Le 09/12/2015 18:00, Michal Skrivanek a écrit :
>
>
> On 09 Dec 2015, at 17:54, Nathanaël Blanchet  wrote:
>
>
>
> Le 09/12/2015 17:12, Michal Skrivanek a écrit :
>
>
> On 09 Dec 2015, at 14:54, Nathanaël Blanchet  wrote:
>
>
>
> Le 08/12/2015 11:43, Michal Skrivanek a écrit :
>
>
>
> On 08 Dec 2015, at 11:20, Yaniv Dary < yd...@redhat.com>
> wrote:
>
>
>
> Yaniv Dary
> Technical Product Manager
> Red Hat Israel Ltd.
> 34 Jerusalem Road
> Building A, 4th floor
> Ra'anana, Israel 4350109
>
> Tel : +972 (9) 7692306
> 8272306
> Email: yd...@redhat.com
> IRC : ydary
>
>
> On Tue, Dec 8, 2015 at 2:03 AM, Nathanaël Blanchet < 
> blanc...@abes.fr> wrote:
>
>> Hi all,
>>
>> I may miss something but according to
>> http://www.ovirt.org/Features/Hot_Plug_Memory, ovirt 3.6 was supposed to
>> support the hot plug memory feature. Nothing happens in reality when
>> increasing memory on a running vm with centos7.
>> I found this :
>> 
>> http://lists.ovirt.orgpipermail/kimchi-devel/2015-June/010714.html, and
>> it seems that el7.1 can't support the feature because of its libvirt
>> version (1.2.8) while the required one is 1.2.14.
>> I didn't test, but I guess F22 supports it.
>> Is there any chance that el7.2 would support it with a backported
>> libvirtd?
>>
>
> It does support it, but only hot-plug not hot-unplug.
>
>
>> Or will a dedicated libvirt rhev package be released so as the downstream
>> to support it (like qemu-kvm for live snapshot some time ago)?
>> Documentation and limitation of the libvirt version for hot plug memory
>> are difficult to find in the ovirt wiki and more generally on the web.
>> Maybe the feature has been postponed to a 3.6.z release?
>>
>
> I works with fedora and you can use it currently with this feature.
>
>
> It works on centos too, qemu-kvm-ev 2.3 we distribute in ovirt repo
>
> Hello, no qemu-kvm-ev 2.3 is not enough:
> [root@fuji ~]# qemu-img --version
> qemu-img version 2.3.0 (qemu-kvm-ev-2.3.0-29.1.el7), Copyright (c)
> 2004-2008 Fabrice Bellard
> and
> vdsm-4.17.10.1-0.el7.centos.noarch
>
> I get this error message each time I try to hot add memory :
> Dec  9 11:18:00 fuji journal: unsupported configuration: unknown device
> type ‘memory'
>
>
> was the VM started in a 3.6 cluster?
>
> sure, on a full 3.6 cluster. I stopped/restarted them. I restarted vdsmd
> and libvirtd
>
>
> ok..and just for the sake of completeness - what is libvirt version
> exactly? If you’re running <1.2.14 then your initial comment make a lot of
> sense….
> Yes, el7.2 has the right one (1.2.17) but even on 7.1 it should support it
> and if it doesn’t it’s our problem we should fix in ovirt (similarly as we
> solve qemu by shipping it ourselves)
>
> libvirt-daemon-1.2.8-16.el7_1.5.x86_64
> I'm really surprised that such a waited feature has not been yet tested by
> the community users with el7, so that nobody has reported the issue yet.
>
>
>
the feature has been tested (by me) and bug was already reported (here
https://bugzilla.redhat.com/show_bug.cgi?id=1287994 )


> Weird indeed. Well, RHEL 7.2 is out for more than a month and there is
> centos 7.2 beta and perhaps rc as well, it's due very soon
> Sandro, we should think about it - since we push qemu-kvm-ev we do not
> really enforce anyone to run on el7.2. We want to do that for various
> reasons as soon as possible. Maybe updating qemu-kvm-ev to require new 7.2
> libvirt?
>
>
>
No idea. If it's libvirt issue, can you test
http://cbs.centos.org/koji/buildinfo?buildID=4726 ? 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/.







> Or how/when did you create it?
>
> those vms have been created before uprading to 3.6, some of them from a
> blank template, other one based on a el7 template.
>
>
> Thanks,
> michal
>
>
> I tried to restart vdsmd but it is the same, even on other hosts.
>
> any help will be appreciated, thank you.
>
>
>
>
>> Thank you for your help
>> ___
>> 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
>
>
> --
> 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 14blanc...@abes.fr
>
>
>
> --
> Nathanaël Blanchet
>
> Supervision réseau
> Pôle Infrastrutures Informatiques
> 227 avenue Professeur-Jean-Louis-Viala
> 34193 MONTPELLIER CEDEX 5 
> Tél. 33

Re: [ovirt-users] hot plug memory in el7

2015-12-09 Thread Gianluca Cecchi

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=4726 ? 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
hypervisor configured with SelfHostedEngine
I have a CentOS 7.1 vm running.

On hypervisor I shutdown VM, put maintenance global and shutdown engine VM.
Then
[root@ractor ~]# yum --enablerepo=cr 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
 * extras: centos.fastbull.org
 * ovirt-3.6: ftp.nluug.nl
 * ovirt-3.6-epel: epel.besthosting.ua
 * updates: 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 update
--> Processing Dependency: libsystemd.so.0(LIBSYSTEMD_209)(64bit) for
package: libvirt-client-1.2.17-13.el7_2.2.x86_64
--> Processing Dependency: libsystemd.so.0()(64bit) for package:
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 update
---> Package libvirt-daemon-config-nwfilter.x86_64 0:1.2.8-16.el7_1.5 will
be updated
---> Package libvirt-daemon-config-nwfilter.x86_64 0:1.2.17-13.el7_2.2 will
be an update
---> Package libvirt-daemon-driver-interface.x86_64 0:1.2.8-16.el7_1.5 will
be updated
---> Package libvirt-daemon-driver-interface.x86_64 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 will
be updated
---> Package libvirt-daemon-driver-network.x86_64 0:1.2.17-13.el7_2.2 will
be an update
---> Package libvirt-daemon-driver-nodedev.x86_64 0:1.2.8-16.el7_1.5 will
be updated
---> Package libvirt-daemon-driver-nodedev.x86_64 0:1.2.17-13.el7_2.2 will
be an update
---> Package libvirt-daemon-driver-nwfilter.x86_64 0:1.2.8-16.el7_1.5 will
be updated
---> Package libvirt-daemon-driver-nwfilter.x86_64 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 will be
updated
---> Package libvirt-daemon-driver-qemu.x86_64 0:1.2.17-13.el7_2.2 will be
an update
---> Package libvirt-daemon-driver-secret.x86_64 0:1.2.8-16.el7_1.5 will be
updated
---> Package libvirt-daemon-driver-secret.x86_64 0:1.2.17-13.el7_2.2 will
be an update
---> Package libvirt-daemon-driver-storage.x86_64 0:1.2.8-16.el7_1.5 will
be updated
---> Package libvirt-daemon-driver-storage.x86_64 0:1.2.17-13.el7_2.2 will
be an update
--> 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
---> Package libvirt-daemon-kvm.x86_64 0:1.2.8-16.el7_1.5 will be updated
---> Package libvirt-daemon-kvm.x86_64 0:1.2.17-13.el7_2.2 will be an update
---> Package libvirt-lock-sanlock.x86_64 0:1.2.8-16.el7_1.5 will be updated
---> Package libvirt-lock-sanlock.x86_64 0:1.2.17-13.el7_2.2 will be 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 updated
--> 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
---> Package device-mapper-libs.x86_64 7:1.02.107-5.el7 will be an update
---> Package systemd-libs.x86_64 0:208-20.el7_1.6 will be updated
--> Processing Dependency: systemd-libs = 208-20.el7_1.6 for package:
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 = 7:1.02.93-3.el7_1.1 for 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 = 208-20.el7_1.6 for package:
systemd-sysv-208-20.el7_1.6.x86_64
--> Processing Dependency: systemd = 208-20.el7_1.6 for package:
systemd-python-208-20.el7_1.6.x86_64
--> Processing Dependency: systemd = 208-20.el7_1.6 for package:
libgudev1-208-20.el7_1.6.x86_64
---> Package systemd.x86_64 0:219-19.el7 will be an update
--> Processing Dependency: kmod >= 18-4 for package:
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 updated
--> 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

Re: [ovirt-users] hot plug memory in el7

2015-12-09 Thread Michal Skrivanek


> On 09 Dec 2015, at 17:54, Nathanaël Blanchet  wrote:
> 
> 
> 
> Le 09/12/2015 17:12, Michal Skrivanek a écrit :
>> 
>>> On 09 Dec 2015, at 14:54, Nathanaël Blanchet >> > wrote:
>>> 
>>> 
>>> 
>>> Le 08/12/2015 11:43, Michal Skrivanek a écrit :
 
 
 On 08 Dec 2015, at 11:20, Yaniv Dary < 
 yd...@redhat.com > wrote:
 
> 
> 
> Yaniv Dary
> Technical Product Manager
> Red Hat Israel Ltd.
> 34 Jerusalem Road
> Building A, 4th floor
> Ra'anana, Israel 4350109
> 
> Tel : +972 (9) 7692306
> 8272306
> Email: yd...@redhat.com 
> IRC : ydary
> 
> On Tue, Dec 8, 2015 at 2:03 AM, Nathanaël Blanchet  > wrote:
> Hi all,
> 
> I may miss something but according to  
> http://www.ovirt.org/Features/Hot_Plug_Memory
>  , ovirt 3.6 was supposed 
> to support the hot plug memory feature. Nothing happens in reality when 
> increasing memory on a running vm with centos7.
> I found this : 
> http://lists.ovirt.orgpipermail/kimchi-devel/2015-June/010714.html 
> , and 
> it seems that el7.1 can't support the feature because of its libvirt 
> version (1.2.8) while the required one is 1.2.14.
> I didn't test, but I guess F22 supports it.
> Is there any chance that el7.2 would support it with a backported 
> libvirtd?
> 
> It does support it, but only hot-plug not hot-unplug.
>  
> Or will a dedicated libvirt rhev package be released so as the downstream 
> to support it (like qemu-kvm for live snapshot some time ago)?
> Documentation and limitation of the libvirt version for hot plug memory 
> are difficult to find in the ovirt wiki and more generally on the web.
> Maybe the feature has been postponed to a 3.6.z release?
> 
> I works with fedora and you can use it currently with this feature.
 
 It works on centos too, qemu-kvm-ev 2.3 we distribute in ovirt repo
>>> Hello, no qemu-kvm-ev 2.3 is not enough:
>>> [root@fuji ~]# qemu-img --version
>>> qemu-img version 2.3.0 (qemu-kvm-ev-2.3.0-29.1.el7), Copyright (c) 
>>> 2004-2008 Fabrice Bellard
>>> and
>>> vdsm-4.17.10.1-0.el7.centos.noarch
>>> 
>>> I get this error message each time I try to hot add memory :
>>> Dec  9 11:18:00 fuji journal: unsupported configuration: unknown device 
>>> type ‘memory'
>> 
>> was the VM started in a 3.6 cluster? 
> sure, on a full 3.6 cluster. I stopped/restarted them. I restarted vdsmd and 
> libvirtd

ok..and just for the sake of completeness - what is libvirt version exactly? If 
you’re running <1.2.14 then your initial comment make a lot of sense….
Yes, el7.2 has the right one (1.2.17) but even on 7.1 it should support it and 
if it doesn’t it’s our problem we should fix in ovirt (similarly as we solve 
qemu by shipping it ourselves)

>> Or how/when did you create it?
> those vms have been created before uprading to 3.6, some of them from a blank 
> template, other one based on a el7 template.
>> 
>> Thanks,
>> michal
>> 
>>> 
>>> I tried to restart vdsmd but it is the same, even on other hosts.
>>> 
>>> any help will be appreciated, thank you.
 
>  
> Thank you for your help
> ___
> 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 
> 
>>> 
>>> -- 
>>> 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
>>> blanc...@abes.fr  
>> 
> 
> -- 
> 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
> blanc...@abes.fr  

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] hot plug memory in el7

2015-12-08 Thread Yaniv Dary

Yaniv Dary
Technical Product Manager
Red Hat Israel Ltd.
34 Jerusalem Road
Building A, 4th floor
Ra'anana, Israel 4350109

Tel : +972 (9) 7692306
8272306
Email: yd...@redhat.com
IRC : ydary


On Tue, Dec 8, 2015 at 2:03 AM, Nathanaël Blanchet  wrote:

> Hi all,
>
> I may miss something but according to
> http://www.ovirt.org/Features/Hot_Plug_Memory, ovirt 3.6 was supposed to
> support the hot plug memory feature. Nothing happens in reality when
> increasing memory on a running vm with centos7.
> I found this :
> http://lists.ovirt.orgpipermail/kimchi-devel/2015-June/010714.html, and
> it seems that el7.1 can't support the feature because of its libvirt
> version (1.2.8) while the required one is 1.2.14.
> I didn't test, but I guess F22 supports it.
> Is there any chance that el7.2 would support it with a backported libvirtd?
>

It does support it, but only hot-plug not hot-unplug.


> Or will a dedicated libvirt rhev package be released so as the downstream
> to support it (like qemu-kvm for live snapshot some time ago)?
> Documentation and limitation of the libvirt version for hot plug memory
> are difficult to find in the ovirt wiki and more generally on the web.
> Maybe the feature has been postponed to a 3.6.z release?
>

I works with fedora and you can use it currently with this feature.


> Thank you for your help
> ___
> 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] hot plug memory in el7

2015-12-08 Thread Michal Skrivanek



> On 08 Dec 2015, at 11:20, Yaniv Dary  wrote:
> 
> 
> 
> Yaniv Dary
> Technical Product Manager
> Red Hat Israel Ltd.
> 34 Jerusalem Road
> Building A, 4th floor
> Ra'anana, Israel 4350109
> 
> Tel : +972 (9) 7692306
> 8272306
> Email: yd...@redhat.com
> IRC : ydary
> 
>> On Tue, Dec 8, 2015 at 2:03 AM, Nathanaël Blanchet  wrote:
>> Hi all,
>> 
>> I may miss something but according to 
>> http://www.ovirt.org/Features/Hot_Plug_Memory, ovirt 3.6 was supposed to 
>> support the hot plug memory feature. Nothing happens in reality when 
>> increasing memory on a running vm with centos7.
>> I found this : 
>> http://lists.ovirt.orgpipermail/kimchi-devel/2015-June/010714.html, and it 
>> seems that el7.1 can't support the feature because of its libvirt version 
>> (1.2.8) while the required one is 1.2.14.
>> I didn't test, but I guess F22 supports it.
>> Is there any chance that el7.2 would support it with a backported libvirtd?
> 
> It does support it, but only hot-plug not hot-unplug.
>  
>> Or will a dedicated libvirt rhev package be released so as the downstream to 
>> support it (like qemu-kvm for live snapshot some time ago)?
>> Documentation and limitation of the libvirt version for hot plug memory are 
>> difficult to find in the ovirt wiki and more generally on the web.
>> Maybe the feature has been postponed to a 3.6.z release?
> 
> I works with fedora and you can use it currently with this feature.

It works on centos too, qemu-kvm-ev 2.3 we distribute in ovirt repo

>  
>> Thank you for your help
>> ___
>> 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
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] hot plug memory in el7

2015-12-07 Thread Nathanaël Blanchet


Hi all,

I may miss something but according to 
http://www.ovirt.org/Features/Hot_Plug_Memory, ovirt 3.6 was supposed to 
support the hot plug memory feature. Nothing happens in reality when 
increasing memory on a running vm with centos7.
I found this : 
http://lists.ovirt.orgpipermail/kimchi-devel/2015-June/010714.html, and 
it seems that el7.1 can't support the feature because of its libvirt 
version (1.2.8) while the required one is 1.2.14.

I didn't test, but I guess F22 supports it.
Is there any chance that el7.2 would support it with a backported libvirtd?
Or will a dedicated libvirt rhev package be released so as the 
downstream to support it (like qemu-kvm for live snapshot some time ago)?
Documentation and limitation of the libvirt version for hot plug memory 
are difficult to find in the ovirt wiki and more generally on the web.

Maybe the feature has been postponed to a 3.6.z release?
Thank you for your help
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] hot plug memory in el7

Re: [ovirt-users] hot plug memory in el7

Re: [ovirt-users] hot plug memory in el7

Re: [ovirt-users] hot plug memory in el7

Re: [ovirt-users] hot plug memory in el7

Re: [ovirt-users] hot plug memory in el7

Re: [ovirt-users] hot plug memory in el7

Re: [ovirt-users] hot plug memory in el7

Re: [ovirt-users] hot plug memory in el7

Re: [ovirt-users] hot plug memory in el7

Re: [ovirt-users] hot plug memory in el7

Re: [ovirt-users] hot plug memory in el7

Re: [ovirt-users] hot plug memory in el7

Re: [ovirt-users] hot plug memory in el7

Re: [ovirt-users] hot plug memory in el7

Re: [ovirt-users] hot plug memory in el7

Re: [ovirt-users] hot plug memory in el7

Re: [ovirt-users] hot plug memory in el7

Re: [ovirt-users] hot plug memory in el7

Re: [ovirt-users] hot plug memory in el7

Re: [ovirt-users] hot plug memory in el7

[ovirt-users] hot plug memory in el7

22 matches

Site Navigation

Mail list logo

Footer information