From: Linhaifeng <haifeng.lin@huawei.com>
To: qemu-devel@nongnu.org
Cc: Damjan Marion <damarion@cisco.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
lilijun <jerry.lilijun@huawei.com>,
n.nikolaev@virtualopensystems.com, liuyongan@huawei.com,
huangzhichao@huawei.com, pbonzini@redhat.com
Subject: [Qemu-devel] vhost-user:Bad ram offset
Date: Sat, 1 Nov 2014 17:21:32 +0800 [thread overview]
Message-ID: <5454A61C.5050505@huawei.com> (raw)
Hi,all
VM use vhost-user backend cannot startup when memory bigger than 3.5G.The log print "Bad ram offset 100000000" .Is this a bug?
log：
[2014-11-01T08:39:07.245324Z] virtio_set_status:524 virtio-net device status is 1 that means ACKNOWLEDGE
[2014-11-01T08:39:07.247225Z] virtio_set_status:524 virtio-balloon device status is 1 that means ACKNOWLEDGE
[2014-11-01T08:39:07.320191Z] virtio_set_status:524 virtio-net device status is 3 that means DRIVER
Bad ram offset 100000000
[2014-11-01 08:39:07]: shutting down
command：
/usr/bin/qemu-system-x86_64 -name vm1
-smp 4
-drive file=/mnt/sdb/linhf/imgs/vm1.img,if=none,id=drive-ide0-0-0,format=raw,cache=none,aio=native -device ide-hd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1 \
-chardev socket,id=charnet0,path=/var/run/vhost-user/port1 -netdev type=vhost-user,id=hostnet0,chardev=charnet0 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=00:00:00:00:00:01,bus=pci.0,addr=0x3 \
-enable-kvm -mem-prealloc -object memory-backend-file,id=mem,size=3968M,mem-path=/dev/hugepages,share=on -numa node,memdev=mem
when memory is smaller than 3.5G VM would run well.
--
Regards,
Haifeng
next reply other threads:[~2014-11-01 9:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-01 9:21 Linhaifeng [this message]
2014-11-02 16:46 ` [Qemu-devel] vhost-user:Bad ram offset Michael S. Tsirkin
2014-11-02 18:54 ` Michael S. Tsirkin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5454A61C.5050505@huawei.com \
--to=haifeng.lin@huawei.com \
--cc=damarion@cisco.com \
--cc=huangzhichao@huawei.com \
--cc=jerry.lilijun@huawei.com \
--cc=liuyongan@huawei.com \
--cc=mst@redhat.com \
--cc=n.nikolaev@virtualopensystems.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.