qemu-4.0.1: vhost_region_add_section:Section rounded to 0 prior to previous a0000

qemu-4.0.1: vhost_region_add_section:Section rounded to 0 prior to previous a0000

[Peter Lieven]

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?


Thanks,

Peter

Re: qemu-4.0.1: vhost_region_add_section:Section rounded to 0 prior to previous a0000

[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?

I've just posted a fix for a similar case that only affected windows
guests with hyperv synic; but the 'previous a0000' looks different.

Dave

> 
> Thanks,
> 
> Peter
> 
> 
> 
> 
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK

Re: qemu-4.0.1: vhost_region_add_section:Section rounded to 0 prior to previous a0000

[Peter Lieven]

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.

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


Thanks,

Peter

Re: qemu-4.0.1: vhost_region_add_section:Section rounded to 0 prior to previous a0000

[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 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

Re: qemu-4.0.1: vhost_region_add_section:Section rounded to 0 prior to previous a0000

[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
       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

Re: qemu-4.0.1: vhost_region_add_section:Section rounded to 0 prior to previous a0000

[Peter Lieven]

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

Re: qemu-4.0.1: vhost_region_add_section:Section rounded to 0 prior to previous a0000

[Peter Lieven]

Am 16.01.20 um 13:47 schrieb Peter Lieven:
> 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?


Update from my side. This happens when I have Debian 10 with XFCE when the Graphical User Interface is initialized.

I see the log message when I specify -M pc-i440fx-2.9. If I obmit the machine type the error does not appear.


Peter

Re: qemu-4.0.1: vhost_region_add_section:Section rounded to 0 prior to previous a0000

[Dr. David Alan Gilbert]

* Peter Lieven (pl@kamp.de) wrote:
> Am 16.01.20 um 13:47 schrieb Peter Lieven:
> > 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?
> 
> 
> Update from my side. This happens when I have Debian 10 with XFCE when the Graphical User Interface is initialized.
> 
> I see the log message when I specify -M pc-i440fx-2.9. If I obmit the machine type the error does not appear.

I can't persuade this to reproduce here on the images I currently have;
but if you can rebuild, can you try the v3 of 'Fix hyperv synic on
vhost' I've just posted?  It turns off the alignment code that's
spitting that error in vhost-kernel cases, so should go away.

Dave

> 
> Peter
> 
> 
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK

Re: qemu-4.0.1: vhost_region_add_section:Section rounded to 0 prior to previous a0000

[Peter Lieven]

> Am 16.01.2020 um 21:26 schrieb Dr. David Alan Gilbert <dgilbert@redhat.com>:
> 
> * Peter Lieven (pl@kamp.de) wrote:
>> Am 16.01.20 um 13:47 schrieb Peter Lieven:
>>> 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?
>> 
>> 
>> Update from my side. This happens when I have Debian 10 with XFCE when the Graphical User Interface is initialized.
>> 
>> I see the log message when I specify -M pc-i440fx-2.9. If I obmit the machine type the error does not appear.
> 
> I can't persuade this to reproduce here on the images I currently have;
> but if you can rebuild, can you try the v3 of 'Fix hyperv synic on
> vhost' I've just posted?  It turns off the alignment code that's
> spitting that error in vhost-kernel cases, so should go away.


I will definitely give it a try tomorrow. The fix to change the machine type was not working. I was too fast with my assumption.

What I see is the following:

Machine boots up (cold start), has network connectivity. As soon as the Graphics are initialized, the vhost_region_add_section error pops up and
Networking is interrupted. When I then migrate the vServer to another host Networking works again. It even seems to keep working when I do a
soft reset (shutdown -r). The only thing that breaks networking again when the graphic is initialized is a hard reset (system reset via hmp or amp).

Thank you,
Peter

Re: qemu-4.0.1: vhost_region_add_section:Section rounded to 0 prior to previous a0000

[Peter Lieven]

Am 16.01.20 um 21:26 schrieb Dr. David Alan Gilbert:
> * Peter Lieven (pl@kamp.de) wrote:
>> Am 16.01.20 um 13:47 schrieb Peter Lieven:
>>> 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?
>>
>> Update from my side. This happens when I have Debian 10 with XFCE when the Graphical User Interface is initialized.
>>
>> I see the log message when I specify -M pc-i440fx-2.9. If I obmit the machine type the error does not appear.
> I can't persuade this to reproduce here on the images I currently have;
> but if you can rebuild, can you try the v3 of 'Fix hyperv synic on
> vhost' I've just posted?  It turns off the alignment code that's
> spitting that error in vhost-kernel cases, so should go away.

Your patch also seems to fix also my issue. No more errors and the network keeps responding.


Thanks

Peter

Re: qemu-4.0.1: vhost_region_add_section:Section rounded to 0 prior to previous a0000

[Dr. David Alan Gilbert]

* Peter Lieven (pl@kamp.de) wrote:
> Am 16.01.20 um 21:26 schrieb Dr. David Alan Gilbert:
> > * Peter Lieven (pl@kamp.de) wrote:
> >> Am 16.01.20 um 13:47 schrieb Peter Lieven:
> >>> 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?
> >>
> >> Update from my side. This happens when I have Debian 10 with XFCE when the Graphical User Interface is initialized.
> >>
> >> I see the log message when I specify -M pc-i440fx-2.9. If I obmit the machine type the error does not appear.
> > I can't persuade this to reproduce here on the images I currently have;
> > but if you can rebuild, can you try the v3 of 'Fix hyperv synic on
> > vhost' I've just posted?  It turns off the alignment code that's
> > spitting that error in vhost-kernel cases, so should go away.
> 
> Your patch also seems to fix also my issue. No more errors and the network keeps responding.

Great, can you reply to that post with a Tested-by ?

Dave

> 
> Thanks
> 
> Peter
> 
> 
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK

Re: qemu-4.0.1: vhost_region_add_section:Section rounded to 0 prior to previous a0000

[Peter Lieven]

Am 17.01.20 um 16:59 schrieb Dr. David Alan Gilbert:
> * Peter Lieven (pl@kamp.de) wrote:
>> Am 16.01.20 um 21:26 schrieb Dr. David Alan Gilbert:
>>> * Peter Lieven (pl@kamp.de) wrote:
>>>> Am 16.01.20 um 13:47 schrieb Peter Lieven:
>>>>> 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?
>>>> Update from my side. This happens when I have Debian 10 with XFCE when the Graphical User Interface is initialized.
>>>>
>>>> I see the log message when I specify -M pc-i440fx-2.9. If I obmit the machine type the error does not appear.
>>> I can't persuade this to reproduce here on the images I currently have;
>>> but if you can rebuild, can you try the v3 of 'Fix hyperv synic on
>>> vhost' I've just posted?  It turns off the alignment code that's
>>> spitting that error in vhost-kernel cases, so should go away.
>> Your patch also seems to fix also my issue. No more errors and the network keeps responding.
> Great, can you reply to that post with a Tested-by ?


I was not sure if I should reply since the patch is for a total different issue.

Anyway, please feel free to add a


Tested-by: Peter Lieven <pl@kamp.de>


I am currently not subscribed to qemu-devel so I can't reply directly.


Best,

Peter

Re: qemu-4.0.1: vhost_region_add_section:Section rounded to 0 prior to previous a0000

[Dr. David Alan Gilbert]

* Peter Lieven (pl@kamp.de) wrote:
> Am 17.01.20 um 16:59 schrieb Dr. David Alan Gilbert:
> > * Peter Lieven (pl@kamp.de) wrote:
> > > Am 16.01.20 um 21:26 schrieb Dr. David Alan Gilbert:
> > > > * Peter Lieven (pl@kamp.de) wrote:
> > > > > Am 16.01.20 um 13:47 schrieb Peter Lieven:
> > > > > > 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?
> > > > > Update from my side. This happens when I have Debian 10 with XFCE when the Graphical User Interface is initialized.
> > > > > 
> > > > > I see the log message when I specify -M pc-i440fx-2.9. If I obmit the machine type the error does not appear.
> > > > I can't persuade this to reproduce here on the images I currently have;
> > > > but if you can rebuild, can you try the v3 of 'Fix hyperv synic on
> > > > vhost' I've just posted?  It turns off the alignment code that's
> > > > spitting that error in vhost-kernel cases, so should go away.
> > > Your patch also seems to fix also my issue. No more errors and the network keeps responding.
> > Great, can you reply to that post with a Tested-by ?
> 
> 
> I was not sure if I should reply since the patch is for a total different issue.
> 
> Anyway, please feel free to add a
> 
> 
> Tested-by: Peter Lieven <pl@kamp.de>
> 
> 
> I am currently not subscribed to qemu-devel so I can't reply directly.
> 

OK, thanks!

Dave

> Best,
> 
> Peter
> 
> 
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK