lkml.org 
[lkml]   [2020]   [Mar]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCH v2 00/10] virtio-mem: paravirtualized memory
From
Date
On 27.03.20 18:03, David Hildenbrand wrote:
> On 27.03.20 17:58, Pankaj Gupta wrote:
>> Hi David,
>>
>> Trying to test the series with the Qemu branch(virtio-mem) mentioned.
>> Unfortunately,
>> not able to hotplug memory. Is anything changed from your previous posting
>> or I am doing something wrong?
>>
>> After giving value to "requested-size", I see size as zero.
>>
>> (qemu) qom-set vm0 requested-size 10G
>> (qemu) info memory-devices
>> Memory device [virtio-mem]: "vm0"
>> memaddr: 0x240000000
>> node: 0
>> requested-size: 10737418240
>> size: 0
>> max-size: 107374182400
>> block-size: 2097152
>> memdev: /objects/mem0
>>
>> Guest kernel: 5.6.0-rc4
>> Using same Qemu commandline arguments mentioned in cover-letter.
>
> Are you booting from an initrd? Are you compiling virtio-mem as a kernel
> module or into the kernel binary?
>
> Make sure that the virtio-mem driver will actually be loaded. (lsmod |
> grep virtio-mem).

"virtio_mem", of course :)

>
> Also, double check if there are any virtio-mem dmesg errors/warnings.
>


--
Thanks,

David / dhildenb

\
 
 \ /
  Last update: 2020-03-27 18:08    [W:0.053 / U:0.684 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site