qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
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: Mon, 13 Jan 2020 17:25:19 +0100	[thread overview]
Message-ID: <b89e8ba2-49e9-8c0d-1129-116afa76366a@kamp.de> (raw)
In-Reply-To: <20200109184440.GR6795@work-vm>

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
       00000000000c0000-00000000000dffff (prio 1, rom): pc.rom
       00000000000e0000-00000000000fffff (prio 1, i/o): alias isa-bios @pc.bios 0000000000020000-000000000003ffff
       00000000fd000000-00000000fdffffff (prio 1, ram): vga.vram
       00000000fe000000-00000000fe00ffff (prio 1, ram): vmsvga.fifo
       00000000fe010000-00000000fe013fff (prio 1, i/o): virtio-pci
         00000000fe010000-00000000fe010fff (prio 0, i/o): virtio-pci-common
         00000000fe011000-00000000fe011fff (prio 0, i/o): virtio-pci-isr
         00000000fe012000-00000000fe012fff (prio 0, i/o): virtio-pci-device
         00000000fe013000-00000000fe013fff (prio 0, i/o): virtio-pci-notify
       00000000fe014000-00000000fe017fff (prio 1, i/o): virtio-pci
         00000000fe014000-00000000fe014fff (prio 0, i/o): virtio-pci-common
         00000000fe015000-00000000fe015fff (prio 0, i/o): virtio-pci-isr
         00000000fe016000-00000000fe016fff (prio 0, i/o): virtio-pci-device
         00000000fe017000-00000000fe017fff (prio 0, i/o): virtio-pci-notify
       00000000fe018000-00000000fe01bfff (prio 1, i/o): virtio-pci
         00000000fe018000-00000000fe018fff (prio 0, i/o): virtio-pci-common
         00000000fe019000-00000000fe019fff (prio 0, i/o): virtio-pci-isr
         00000000fe01a000-00000000fe01afff (prio 0, i/o): virtio-pci-device
         00000000fe01b000-00000000fe01bfff (prio 0, i/o): virtio-pci-notify
       00000000fe01c000-00000000fe01ffff (prio 1, i/o): virtio-pci
         00000000fe01c000-00000000fe01cfff (prio 0, i/o): virtio-pci-common
         00000000fe01d000-00000000fe01dfff (prio 0, i/o): virtio-pci-isr
         00000000fe01e000-00000000fe01efff (prio 0, i/o): virtio-pci-device
         00000000fe01f000-00000000fe01ffff (prio 0, i/o): virtio-pci-notify
       00000000febd0000-00000000febd0fff (prio 1, i/o): virtio-net-pci-msix
         00000000febd0000-00000000febd002f (prio 0, i/o): msix-table
         00000000febd0800-00000000febd0807 (prio 0, i/o): msix-pba
       00000000febd1000-00000000febd1fff (prio 1, i/o): virtio-scsi-pci-msix


Peter






  reply	other threads:[~2020-01-13 16:26 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 [this message]
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=b89e8ba2-49e9-8c0d-1129-116afa76366a@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).