I would leave out the second -m option. It just add confusion. It does
override the first -m option; in this case, they are the same number, 512,
so the second option does not change anything.
Here is something peculiar I found in the qemu-system man page:
-m [size=]megs[,slots=n,maxmem=size]
Sets guest startup RAM size to megs megabytes. Default is 128
MiB.
Optionally, a suffix of "M" or "G" can be used to signify a value
in megabytes or gigabytes respectively. Optional pair slots,
maxmem
could be used to set amount of hotpluggable memory slots and
maximum amount of memory. Note that maxmem must be aligned to the
page size.
For example, the following command-line sets the guest startup
RAM
size to 1GB, creates 3 slots to hotplug additional memory and
sets
the maximum memory the guest can reach to 4GB:
qemu-system-x86_64 -m 1G,slots=3,maxmem=4G
In one place they use the Mebibytes abbreviation, MiB. Presumably they mean
mebibytes (2**20) and gibibytes (2**30) everywhere, that's my guess, but
they switch back and forth in the written form. Usually we use the wrong
term but use it consistently. Very weird. Blame it on Microsoft.
Burt
On Tue, Jul 11, 2017 at 2:01 PM, Steven Luong (sluong) <[email protected]>
wrote:
> Divya,
>
>
>
> Please try this. I highlighted the difference.
>
>
>
> ./qemu-system-x86_64 -enable-kvm -m 512 -bios
> /home/cavium/Downloads/OVMF.fd -smp 4 -cpu host -vga none -nographic -drive
> file="/home/cavium/Downloads/clear-16300-kvm.img",if=virtio,aio=threads
> -chardev socket,id=char1,path=/tmp/sock1.sock -netdev
> type=vhost-user,id=mynet1,chardev=char1,vhostforce -device
> virtio-net-pci,mac=00:00:00:00:00:01,netdev=mynet1 -object
> memory-backend-file,id=mem,size=512M,mem-path=/dev/hugepages,share=on
> -numa node,memdev=mem –m 512 -mem-prealloc -debugcon file:debug.log
> -global isa-debugcon.iobase=0x402
>
>
>
> Steven
>
>
>
> *From: *<[email protected]> on behalf of Divya Vyas <
> [email protected]>
> *Date: *Saturday, July 8, 2017 at 10:46 AM
> *To: *"[email protected]" <[email protected]>
> *Subject: *[vpp-dev] Qemu error vhost-user Failed initializing vhost-user
> memory map
>
>
>
> I am using below command for launching qemu
>
> ./qemu-system-x86_64 -enable-kvm -m 1024 -bios
> /home/cavium/Downloads/OVMF.fd -smp 4 -cpu host -vga none -nographic -drive
> file="/home/cavium/Downloads/clear-16300-kvm.img",if=virtio,aio=threads
> -chardev socket,id=char1,path=/tmp/sock1.sock -netdev
> type=vhost-user,id=mynet1,chardev=char1,vhostforce -device
> virtio-net-pci,mac=00:00:00:00:00:01,netdev=mynet1 -object
> memory-backend-file,id=mem,size=512M,mem-path=/dev/hugepages,share=on
> -numa node,mem=1024M -mem-prealloc -debugcon file:debug.log -global
> isa-debugcon.iobase=0x402
>
> and it is giving error :
>
> qemu-system-x86_64: Failed initializing vhost-user memory map, consider
> using -object memory-backend-file share=on
> qemu-system-x86_64: vhost_set_mem_table failed: Resource temporarily
> unavailable (11)
> qemu-system-x86_64: unable to start vhost net: 11: falling back on
> userspace virtio
>
> Any ideas?
>
> Thanks,
>
> Divya
>
>
> _______________________________________________
> vpp-dev mailing list
> [email protected]
> https://lists.fd.io/mailman/listinfo/vpp-dev
>
_______________________________________________
vpp-dev mailing list
[email protected]
https://lists.fd.io/mailman/listinfo/vpp-dev
