search for: mem0

...size. /home/gavin/sandbox/qemu.main/build/qemu-system-aarch64 \ -accel kvm -machine virt,gic-version=host -cpu host \ -smp maxcpus=8,cpus=8,sockets=2,clusters=2,cores=2,threads=1 \ -m 1024M,slots=16,maxmem=64G \ -object memory-backend-ram,id=mem0,size=512M \ -object memory-backend-ram,id=mem1,size=512M \ -numa node,nodeid=0,memdev=mem0,cpus=0-3 \ -numa node,nodeid=1,memdev=mem1,cpus=4-7 \ : \ -device v...

...t of memory right now for e.g. > dirty bitmaps and memory slot tracking data) > > Start QEMU with two virtio-mem devices that provide little memory inititally. > $ qemu-system-x86_64 -m 4G,maxmem=504G \ > -smp sockets=2,cores=2 \ > [...] > -object memory-backend-ram,id=mem0,size=256G \ > -device virtio-mem-pci,id=vm0,memdev=mem0,node=0,size=4160M \ > -object memory-backend-ram,id=mem1,size=256G \ > -device virtio-mem-pci,id=vm1,memdev=mem1,node=1,size=3G > > Query the configuration ('size' tells us the guest driver is active): > (qemu...

On 14.05.20 12:02, teawater wrote: > > >> 2020?5?14? 16:48?David Hildenbrand <david at redhat.com> ??? >> >> On 14.05.20 08:44, teawater wrote: >>> Hi David, >>> >>> I got a kernel warning with v2 and v3. >> >> Hi Hui, >> >> thanks for playing with the latest versions. Surprisingly, I can >> reproduce even by

On 14.05.20 12:02, teawater wrote: > > >> 2020?5?14? 16:48?David Hildenbrand <david at redhat.com> ??? >> >> On 14.05.20 08:44, teawater wrote: >>> Hi David, >>> >>> I got a kernel warning with v2 and v3. >> >> Hi Hui, >> >> thanks for playing with the latest versions. Surprisingly, I can >> reproduce even by

...size. /home/gavin/sandbox/qemu.main/build/qemu-system-aarch64 \ -accel kvm -machine virt,gic-version=host -cpu host \ -smp maxcpus=8,cpus=8,sockets=2,clusters=2,cores=2,threads=1 \ -m 1024M,slots=16,maxmem=64G \ -object memory-backend-ram,id=mem0,size=512M \ -object memory-backend-ram,id=mem1,size=512M \ -numa node,nodeid=0,memdev=mem0,cpus=0-3 \ -numa node,nodeid=1,memdev=mem1,cpus=4-7 \ : \ -device v...

...> -cpu host \ > -no-reboot \ > -nographic \ > -device ide-hd,drive=hd \ > -drive if=none,id=hd,file=/home/dhildenb/git/Fedora-Cloud-Base-31-1.9.x86_64.qcow2,format=qcow2 \ > -m 1g,slots=10,maxmem=2G \ > -smp 1 \ > -object memory-backend-ram,id=mem0,size=256m \ > -device pc-dimm,id=dimm0,memdev=mem0 \ > -s \ > -monitor unix:/var/tmp/monitor,server,nowait > > > Without the DIMM it seems to work just fine. > And another correction. Using QEMU v5.0.0, Linux 5.7-rc5, untouched Fedora-Cloud-Base-32-1.6.x86_64....

...ndbox/qemu.main/build/qemu-system-aarch64 \ > -accel kvm -machine virt,gic-version=host -cpu host \ > -smp maxcpus=8,cpus=8,sockets=2,clusters=2,cores=2,threads=1 \ > -m 1024M,slots=16,maxmem=64G \ > -object memory-backend-ram,id=mem0,size=512M \ > -object memory-backend-ram,id=mem1,size=512M \ > -numa node,nodeid=0,memdev=mem0,cpus=0-3 \ > -numa node,nodeid=1,memdev=mem1,cpus=4-7 \ > :...

...m=16G -kernel /root/linux-next/$1/arch/x86/boot/bzImage \ -smp 4 \ -append "earlyprintk=ttyS0 root=/dev/sda1 console=ttyS0 debug psi=1 nokaslr ignore_loglevel" \ -hda /root/CentOS-7-x86_64-Azure-1703.qcow2 \ -net user,hostfwd=tcp::2222-:22 -net nic -s \ -object memory-backend-ram,id=mem0,size=3G \ -device virtio-mem-pci,id=vm0,memdev=mem0,node=0,requested-size=0M \ --nographic

...m=16G -kernel /root/linux-next/$1/arch/x86/boot/bzImage \ -smp 4 \ -append "earlyprintk=ttyS0 root=/dev/sda1 console=ttyS0 debug psi=1 nokaslr ignore_loglevel" \ -hda /root/CentOS-7-x86_64-Azure-1703.qcow2 \ -net user,hostfwd=tcp::2222-:22 -net nic -s \ -object memory-backend-ram,id=mem0,size=3G \ -device virtio-mem-pci,id=vm0,memdev=mem0,node=0,requested-size=0M \ --nographic

...chine pc-i440fx-5.0,accel=kvm,usb=off \ -cpu host \ -no-reboot \ -nographic \ -device ide-hd,drive=hd \ -drive if=none,id=hd,file=/home/dhildenb/git/Fedora-Cloud-Base-31-1.9.x86_64.qcow2,format=qcow2 \ -m 1g,slots=10,maxmem=2G \ -smp 1 \ -object memory-backend-ram,id=mem0,size=256m \ -device pc-dimm,id=dimm0,memdev=mem0 \ -s \ -monitor unix:/var/tmp/monitor,server,nowait Without the DIMM it seems to work just fine. -- Thanks, David / dhildenb

...-next/$1/arch/x86/boot/bzImage \ > -smp 4 \ > -append "earlyprintk=ttyS0 root=/dev/sda1 console=ttyS0 debug psi=1 nokaslr ignore_loglevel" \ > -hda /root/CentOS-7-x86_64-Azure-1703.qcow2 \ > -net user,hostfwd=tcp::2222-:22 -net nic -s \ > -object memory-backend-ram,id=mem0,size=3G \ > -device virtio-mem-pci,id=vm0,memdev=mem0,node=0,requested-size=0M \ > --nographic > > -- Thanks, David / dhildenb

...dhildenbrand/qemu.git virtio-mem > > Start QEMU with two virtio-mem devices (one per NUMA node): > $ qemu-system-x86_64 -m 4G,maxmem=204G \ > -smp sockets=2,cores=2 \ > -numa node,nodeid=0,cpus=0-1 -numa node,nodeid=1,cpus=2-3 \ > [...] > -object memory-backend-ram,id=mem0,size=100G,managed-size=on \ > -device virtio-mem-pci,id=vm0,memdev=mem0,node=0,requested-size=0M \ > -object memory-backend-ram,id=mem1,size=100G,managed-size=on \ > -device virtio-mem-pci,id=vm1,memdev=mem1,node=1,requested-size=1G > > Query the configuration: > QEMU 4.2....

...B ) created by SPDK): > /home/wuzhouhui/qemu-2.12.1/x86_64-softmmu/qemu-system-x86_64 \ > -name guest=wzh,debug-threads=on \ > -machine pc-i440fx-2.12,accel=kvm,usb=off \ > -cpu host \ > -m 4096 \ > -object memory-backend-file,id=mem0,size=4096M,mem-path=/dev/hugepages,share=on \ > -numa node,memdev=mem0 \ > -realtime mlock=off \ > -smp 2,sockets=2,cores=1,threads=1 \ > -uuid a84e96e6-2c53-408d-986b-c709bc6a0e51 \ > -no-user-config \ > -nodefaults \ &g...

...gt;smp); } - ADD_CMDLINE ("-m"); - ADD_CMDLINE_PRINTF ("%d", g->memsize); + if (guestfs_int_has_spdk_drive(g)) { + ADD_CMDLINE ("-m"); + ADD_CMDLINE ("1G"); + ADD_CMDLINE ("-object"); + ADD_CMDLINE ("memory-backend-file,id=mem0,size=1G,mem-path=/dev/hugepages,share=on"); + ADD_CMDLINE ("-numa"); + ADD_CMDLINE ("node,memdev=mem0"); + } else { + ADD_CMDLINE ("-m"); + ADD_CMDLINE_PRINTF ("%d", g->memsize); + } /* Force exit instead of reboot on panic */ ADD...

...nsible, but as you pointed out, that information might not be very useful. > I am not sure how it is handled today in QEMU in terms of guest-host > NUMA proximity domain mapping. It looks like the user can specify this guest-host mapping on the command-line: -object memory-backend-ram,id=mem0,size=4G,host-nodes=3,policy=bind -object memory-backend-ram,id=mem1,size=4G,host-nodes=4,policy=bind -numa node,memdev=mem0,nodeid=numa0 -numa node,memdev=mem1,nodeid=numa1 -numa cpu,node-id=numa0,socket-id=0 -numa cpu,node-id=numa1,socket-id=1 numa0 and numa1 would get proximity domains...

Considering that the technic of SPDK + QEMU is making progress toward maturity. Personally I'd like to do the integration work. Not sure somebody would mind to give me some clue on that? Because I'm not familiar with libguestfs code structures. Thanks, Bob

...eproduce this warning with set file as nvdimm with following command. > sudo /home/teawater/qemu/qemu/x86_64-softmmu/qemu-system-x86_64 -machine pc,accel=kvm,kernel_irqchip,nvdimm -no-reboot -nographic -kernel /home/teawater/kernel/bk2/arch/x86/boot/bzImage -append "console=ttyS0 root=/dev/pmem0 swiotlb=noforce" -m 1g,slots=1,maxmem=2G -smp 1 -device nvdimm,id=nv0,memdev=mem0 -object memory-backend-file,id=mem0,mem-path=/home/teawater/old.img,size=268435456 -monitor unix:/home/teawater/qemu/m,server,nowait > > Best, > Hui -- Thanks, David / dhildenb

...serial \ -device isa-serial,chardev=serial \ -append "console=ttyS0 rd.shell rd.luks=0 rd.lvm=0" \ -initrd /boot/initramfs-4.10.8-200.fc25.x86_64.img \ -chardev socket,id=monitor,path=/var/tmp/monitor,server,nowait \ -mon chardev=monitor,mode=readline \ -object memory-backend-ram,id=mem0,size=4G,max-size=8G \ -device virtio-mem-pci,id=reg0,memdev=mem0,node=0 \ -object memory-backend-ram,id=mem1,size=3G,max-size=8G \ -device virtio-mem-pci,id=reg1,memdev=mem1,node=1 2. Listing current memory assignment: --> (qemu) info memory-devices Memory device [virtio-mem]: "reg0&q...

...serial \ -device isa-serial,chardev=serial \ -append "console=ttyS0 rd.shell rd.luks=0 rd.lvm=0" \ -initrd /boot/initramfs-4.10.8-200.fc25.x86_64.img \ -chardev socket,id=monitor,path=/var/tmp/monitor,server,nowait \ -mon chardev=monitor,mode=readline \ -object memory-backend-ram,id=mem0,size=4G,max-size=8G \ -device virtio-mem-pci,id=reg0,memdev=mem0,node=0 \ -object memory-backend-ram,id=mem1,size=3G,max-size=8G \ -device virtio-mem-pci,id=reg1,memdev=mem1,node=1 2. Listing current memory assignment: --> (qemu) info memory-devices Memory device [virtio-mem]: "reg0&q...

...ial,chardev=serial \ > -append "console=ttyS0 rd.shell rd.luks=0 rd.lvm=0" \ > -initrd /boot/initramfs-4.10.8-200.fc25.x86_64.img \ > -chardev socket,id=monitor,path=/var/tmp/monitor,server,nowait \ > -mon chardev=monitor,mode=readline \ > -object memory-backend-ram,id=mem0,size=4G,max-size=8G \ > -device virtio-mem-pci,id=reg0,memdev=mem0,node=0 \ > -object memory-backend-ram,id=mem1,size=3G,max-size=8G \ > -device virtio-mem-pci,id=reg1,memdev=mem1,node=1 > > 2. Listing current memory assignment: > > --> (qemu) info memory-devices >...