On 2/5/21 9:34 AM, Jing Qi wrote:
Thanks Michal. I checked the virtio_mem module in the host last time.
I tried a new guest image with virtio_mem module and start the domain ,
then the value of actual can be set correctly.
Yeah, it's the guest that needs the module. Glad to hear it's working.
Thanks Michal. I checked the virtio_mem module in the host last time.
I tried a new guest image with virtio_mem module and start the domain ,
then the value of actual can be set correctly.
Jing Qi
On Thu, Feb 4, 2021 at 4:52 PM Michal Privoznik wrote:
> On 2/4/21 3:33 AM, Jing Qi wrote:
> > Mi
On 2/4/21 3:33 AM, Jing Qi wrote:
Michal,
I checked the virtio_mem module and it's loaded -
lsmod |grep virtio_mem
virtio_mem 32768 0
And I can't make the actual value change to non-zerio.
-> virsh update-memory pc --requested-size 256M
or
->virsh setmem pc 1000M
This is unrela
Michal,
I checked the virtio_mem module and it's loaded -
lsmod |grep virtio_mem
virtio_mem 32768 0
And I can't make the actual value change to non-zerio.
-> virsh update-memory pc --requested-size 256M
or
->virsh setmem pc 1000M
524288
0
2048
On 2/3/21 7:11 AM, Jing Qi wrote:
I did some test for virtio-mem with libvirt upstream version
v7.0.0-153-g5ea3ecd07d
& qemu-kvm-5.2.0-0.7.rc2.fc34.x86_64
S1. Start domain with memory device
1. Domain configuration-
10485760
1572864
1572864
...
...
I did some test for virtio-mem with libvirt upstream version
v7.0.0-153-g5ea3ecd07d
& qemu-kvm-5.2.0-0.7.rc2.fc34.x86_64
S1. Start domain with memory device
1. Domain configuration-
10485760
1572864
1572864
...
...
524288
0
2048
On Fri, Jan 22, 2021 at 13:50:21 +0100, Michal Privoznik wrote:
> Technically, this is another version of:
>
> https://www.redhat.com/archives/libvir-list/2020-December/msg00199.html
>
> But since virtio-pmem part is pushed now, I've reworked virtio-mem a bit
> and sending it as a new series.
>
On 22.01.21 23:03, Daniel Henrique Barboza wrote:
>
>
> On 1/22/21 6:19 PM, David Hildenbrand wrote:
>>
>>> Out of curiosity: are you aware of anyone working in enabling virtio-mem
>>> for pseries/ppc64? I'm wondering if there's some kind of architecture
>>> limitation in Power or if it's just a
On 1/22/21 6:19 PM, David Hildenbrand wrote:
Out of curiosity: are you aware of anyone working in enabling virtio-mem
for pseries/ppc64? I'm wondering if there's some kind of architecture
limitation in Power or if it's just a lack of interest.
I remember there is interest, however:
- arm6
> Out of curiosity: are you aware of anyone working in enabling virtio-mem
> for pseries/ppc64? I'm wondering if there's some kind of architecture
> limitation in Power or if it's just a lack of interest.
I remember there is interest, however:
- arm64 and x86-64 is used more frequently in appli
On 1/22/21 4:54 PM, David Hildenbrand wrote:
Am 22.01.2021 um 19:53 schrieb Daniel Henrique Barboza :
On 1/22/21 9:50 AM, Michal Privoznik wrote:
Technically, this is another version of:
https://www.redhat.com/archives/libvir-list/2020-December/msg00199.html
But since virtio-pmem part i
> Am 22.01.2021 um 19:53 schrieb Daniel Henrique Barboza
> :
>
>
>
>> On 1/22/21 9:50 AM, Michal Privoznik wrote:
>> Technically, this is another version of:
>> https://www.redhat.com/archives/libvir-list/2020-December/msg00199.html
>> But since virtio-pmem part is pushed now, I've reworked
On 1/22/21 9:50 AM, Michal Privoznik wrote:
Technically, this is another version of:
https://www.redhat.com/archives/libvir-list/2020-December/msg00199.html
But since virtio-pmem part is pushed now, I've reworked virtio-mem a bit
and sending it as a new series.
For curious ones, David summa
On 22.01.21 13:50, Michal Privoznik wrote:
> Technically, this is another version of:
>
> https://www.redhat.com/archives/libvir-list/2020-December/msg00199.html
>
> But since virtio-pmem part is pushed now, I've reworked virtio-mem a bit
> and sending it as a new series.
>
> For curious ones, D
Technically, this is another version of:
https://www.redhat.com/archives/libvir-list/2020-December/msg00199.html
But since virtio-pmem part is pushed now, I've reworked virtio-mem a bit
and sending it as a new series.
For curious ones, David summarized behaviour well when implementing
virtio-mem
15 matches
Mail list logo
