From: Peter Lieven <pl@kamp.de>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
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, 16 Jan 2020 13:47:32 +0100 [thread overview]
Message-ID: <cd316fb8-b56b-2913-8b57-f085ca4426d7@kamp.de> (raw)
In-Reply-To: <b89e8ba2-49e9-8c0d-1129-116afa76366a@kamp.de>
Am 13.01.20 um 17:25 schrieb Peter Lieven:
> Am 09.01.20 um 19:44 schrieb Dr. David Alan Gilbert:
>> * 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 we go:
>
>
> address-space: memory
> 0000000000000000-ffffffffffffffff (prio 0, i/o): system
> 0000000000000000-000000003fffffff (prio 0, i/o): alias ram-below-4g @pc.ram 0000000000000000-000000003fffffff
> 0000000000000000-ffffffffffffffff (prio -1, i/o): pci
> 00000000000a0000-00000000000affff (prio 2, i/o): alias vga.chain4 @vga.vram 0000000000000000-000000000000ffff
> 00000000000a0000-00000000000bffff (prio 1, i/o): vga-lowmem
What seems special is that the RAM area is prio2. Any idea if this makes trouble?
Peter
next prev parent reply other threads:[~2020-01-16 12:49 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
2020-01-13 16:25 ` Peter Lieven
2020-01-16 12:47 ` Peter Lieven [this message]
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=cd316fb8-b56b-2913-8b57-f085ca4426d7@kamp.de \
--to=pl@kamp.de \
--cc=dgilbert@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 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).