search for: memdev

...ent'/> <model type='virtio'/> </interface> when i create the VM the qemu command is like this without 'share=on' parameter: -object memory-backend-file,prealloc=yes,mem-path=/dev/hugepages/libvirt/qemu,size=1024M,id=ram-node0 -numa node,nodeid=0,cpus=0,memdev=ram-node0 -object memory-backend-file,prealloc=yes,mem-path=/dev/hugepages/libvirt/qemu,size=1024M,id=ram-node1 -numa node,nodeid=1,cpus=1,memdev=ram-node1

...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) info memory-devices > info memory-devices > Me...

...rtio'/> >> </interface> >> >> >> when i create the VM the qemu command is like this without 'share=on' parameter: >> -object memory-backend-file,prealloc=yes,mem-path=/dev/hugepages/libvirt/qemu,size=1024M,id=ram-node0 -numa node,nodeid=0,cpus=0,memdev=ram-node0 >> -object memory-backend-file,prealloc=yes,mem-path=/dev/hugepages/libvirt/qemu,size=1024M,id=ram-node1 -numa node,nodeid=1,cpus=1,memdev=ram-node1 >> >> _______________________________________________ >> libvirt-users mailing list >> libvirt-users@redhat.co...

...I have a list of successive package, and it occured that some package are not installed. exec { ''sudo gem update --system'': path => [''/usr/bin/''], alias => updateGem, } package { '' libmemcached-dev'': ensure => present, alias => memDev, require => Exec[updateGem], } package { '' libmemcached-dbg'': ensure => present, alias => memDbg, require => Package[memDev], } package { '' libsas2-dev'': ensure => present, alias => sasDev, require => Package[memDdg], } package { ...

...u 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 virtio-balloon-pci,id=balloon0,bus=pcie.10 { "execute" : "balloon", "arguments": { "v...

Hi, I want to use virsh to create a VM with the qemu parameter '-object memory-backend-file,id=mem,size=2048M,mem-path=/mnt/huge,share=on -numa node,memdev=mem'. How to write the XML file?

...u 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 virtio-balloon-pci,id=balloon0,bus=pcie.10 { "execute" : "balloon", "arguments": { "v...

...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 virtio-balloon-pci,id=balloon0,bus=pcie.10 > > { "execute" : "balloon", &qu...

...-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.50 monitor - type 'help' for more information > (qemu) info...

On 2014/9/25 2:05, Eric Blake wrote: > On 09/24/2014 02:05 AM, Linhaifeng wrote: >> Hi, >> >> I want to use virsh to create a VM with the qemu parameter '-object memory-backend-file,id=mem,size=2048M,mem-path=/mnt/huge,share=on -numa node,memdev=mem'. > > Looking at tests/qemuxml2argvdata/qemuxml2argv-hugepages-pages.args, I > see several instances of "-object memory-backend-file...", so look at > the counterpart .xml file for some examples: > > <memoryBacking> > <hugepages> >...

...<model type='virtio'/> > </interface> > > >when i create the VM the qemu command is like this without 'share=on' parameter: >-object memory-backend-file,prealloc=yes,mem-path=/dev/hugepages/libvirt/qemu,size=1024M,id=ram-node0 -numa node,nodeid=0,cpus=0,memdev=ram-node0 >-object memory-backend-file,prealloc=yes,mem-path=/dev/hugepages/libvirt/qemu,size=1024M,id=ram-node1 -numa node,nodeid=1,cpus=1,memdev=ram-node1 > >_______________________________________________ >libvirt-users mailing list >libvirt-users@redhat.com >https://www.redhat...

...like it would with virtio-balloon). Is this something virtio-mem is capable of? I've tried to run it, but it immediately took over 9GB of memory: virt-install --name test --cpu cell0.cpus=0,cell0.memory=4194304,cell1.cpus=1,cell1.memory=4194304 --memory maxMemory=65536,maxMemory.slots=8 --memdev model=virtio-mem,target.node=0,target.block=2048,target.size=1000 --disk size=400 --network network=ai --location=/tmp/debian-12.1.0-amd64-netinst.iso --os-variant=debian11 --graphics none --extra-args "console=ttyS0 Best wishes, Daniel -------------- next part -------------- A non-text...

...t can create a shared memory that guest device use, so we can use this memory to do something ourselves. First, I create host memory backend: -object memory-backend-file,size=1M,share,mem-path=/dev/shm/ivshmem,id=hostmem Twice, Bind a shared memory device to my guest: -device ivshmem-plain,memdev=hostmem Then I boot ivshmem servi ivshmem-server -p /var/run/ivshmem-server.pid -S /tmp/ivshmem_socket -M ivshmem -m /dev/shm -l 1M -n 2 Next time i get this error: *** Example code, do not use in production *** cannot bind And i search the problem on google, but nothing to get, hope...

...-balloon). Is this > something virtio-mem is capable of? I've tried to run it, but it immediately > took over 9GB of memory: > > virt-install --name test --cpu > cell0.cpus=0,cell0.memory=4194304,cell1.cpus=1,cell1.memory=4194304 --memory > maxMemory=65536,maxMemory.slots=8 --memdev > model=virtio-mem,target.node=0,target.block=2048,target.size=1000 --disk > size=400 --network network=ai > --location=/tmp/debian-12.1.0-amd64-netinst.iso --os-variant=debian11 > --graphics none --extra-args "console=ttyS0 When using PCI device assignment, the VFIO driver requir...

...<!-- [...] --> </devices> <ns0:commandline> <ns0:arg value="-object"/> <ns0:arg value="memory-backend-file,id=mem,size=2G,mem-path=/dev/hugepages,share=on"/> <ns0:arg value="-numa"/> <ns0:arg value="node,memdev=mem"/> <ns0:arg value="-mem-prealloc"/> </ns0:commandline> </domain> Now, if I try to start my VM, I get the following error and the VM is not started at all: $ virsh create vm.xml error: Failed to create domain from vm.xml error: unsupported configuratio...

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

...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 0 and 1, corresponding to host domains 3 and 4. It is also possible to specify the NUMA node of a PCI bus (via the PCI exp...

...t;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" addr: 0x140000000 node: 0 size: 4294967296 m...

...t;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" addr: 0x140000000 node: 0 size: 4294967296 m...