From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Peter Lieven <pl@kamp.de>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: qemu-4.0.1: vhost_region_add_section:Section rounded to 0 prior to previous a0000
Date: Thu, 9 Jan 2020 18:44:40 +0000 [thread overview]
Message-ID: <20200109184440.GR6795@work-vm> (raw)
In-Reply-To: <ca222a5f-1ec6-477c-ed83-6ef52ea9e97f@kamp.de>
* Peter Lieven (pl@kamp.de) wrote:
> Am 08.01.20 um 16:04 schrieb Dr. David Alan Gilbert:
> > * Peter Lieven (pl@kamp.de) wrote:
> > > Hi,
> > >
> > >
> > > I have a Qemu 4.0.1 machine with vhost-net network adapter, thats polluting the log with the above message.
> > >
> > > Is this something known? Googling revealed the following patch in Nemu (with seems to be a Qemu fork from Intel):
> > >
> > > https://github.com/intel/nemu/commit/03940ded7f5370ce7492c619dccced114ef7f56e
> > >
> > >
> > > The network stopped functioning. After a live-migration the vServer is reachable again.
> > >
> > >
> > > Any ideas?
> > What guest are you running and what does your qemu commandline look
> > like?
>
>
> Its running debian9. We have hundreds of other VMs with identical setup. Do not know why this one makes trouble.
Could you extract an 'info mtree' from it - particularly the
'address-space: memory' near the top.
> Here is the cmdline:
>
>
> /usr/bin/qemu-4.0.0 -enable-kvm -M pc-i440fx-2.9 -nodefaults -netdev
> type=tap,id=guest0,script=no,downscript=no,ifname=tap0,vhost=on,vnet_hdr=on
> -device virtio-net-pci,netdev=guest0,mac=52:54:00:80:07:bc -iscsi
> initiator-name=iqn.2005-03.org.virtual-core:0025b51f006c,timeout=30 -object
> rng-random,filename=/dev/urandom,id=rng0 -device
> virtio-rng-pci,rng=rng0,max-bytes=65536,period=1000 -drive format=raw,discard=on,detect-zeroes=off,file=XXX,if=none,cache=writeback,aio=native,id=disk0
> -device virtio-scsi-pci -device scsi-hd,drive=disk0 -serial null
> -parallel null -m 1024,slots=16,maxmem=393216M -smp
> 1,sockets=64,cores=1,threads=1,maxcpus=64 -monitor
> tcp:0:4001,server,nowait,nodelay -vnc :1 -qmp
> tcp:0:3001,server,nowait,nodelay -name 'debian9' -drive
> index=2,media=cdrom,if=ide,aio=native,readonly=on -boot order=c,menu=off
> -k de -pidfile /var/run/qemu/vm-5182.pid -mem-path /hugepages
> -mem-prealloc -cpu Westmere,+pcid,enforce -rtc base=utc -usb -device
> usb-tablet -no-hpet -vga vmware -chardev
> socket,host=127.0.0.1,port=2001,id=qga0,server,nowait,nodelay -device
> virtio-serial -device
> virtserialport,chardev=qga0,name=org.qemu.guest_agent.0
All pretty boring stuff. hmm.
Dave
>
> Thanks,
>
> Peter
>
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2020-01-09 18:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-08 13:45 qemu-4.0.1: vhost_region_add_section:Section rounded to 0 prior to previous a0000 Peter Lieven
2020-01-08 15:04 ` Dr. David Alan Gilbert
2020-01-09 18:19 ` Peter Lieven
2020-01-09 18:44 ` Dr. David Alan Gilbert [this message]
2020-01-13 16:25 ` Peter Lieven
2020-01-16 12:47 ` Peter Lieven
2020-01-16 16:44 ` Peter Lieven
2020-01-16 20:26 ` Dr. David Alan Gilbert
2020-01-16 21:10 ` Peter Lieven
2020-01-17 12:18 ` Peter Lieven
2020-01-17 15:59 ` Dr. David Alan Gilbert
2020-01-20 9:32 ` Peter Lieven
2020-01-20 9:42 ` Dr. David Alan Gilbert
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=20200109184440.GR6795@work-vm \
--to=dgilbert@redhat.com \
--cc=pl@kamp.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).