Re: [Qemu-devel] where can I find the latest memory hot plugging patch for Qemu?

[Igor Mammedov]

On Thu, 19 Jun 2014 10:28:41 +0000
"Kolk, G. van der" <address@hidden> wrote:

> This is probably more helpful:
>
> Hotplug Mem Device
> init_memory_mapping: 0000000100000000-0000000140000000
>  0100000000 - 0140000000 page 2M
>  [ffffea0003800000-ffffea00039fffff] PMD -> 
> [ffff88000cc00000-ffff88000cdfffff] on node 0
>  [ffffea0003a00000-ffffea0003bfffff] PMD -> 
> [ffff88000c800000-ffff88000c9fffff] on node 0
>  [ffffea0003c00000-ffffea0003dfffff] PMD -> 
> [ffff88000c600000-ffff88000c7fffff] on node 0
>  [ffffea0003e00000-ffffea0003ffffff] PMD -> 
> [ffff88000c000000-ffff88000c1fffff] on node 0
>  [ffffea0004000000-ffffea00041fffff] PMD -> 
> [ffff88000be00000-ffff88000bffffff] on node 0
>  [ffffea0004200000-ffffea00043fffff] PMD -> 
> [ffff88000ba00000-ffff88000bbfffff] on node 0
> Built 1 zonelists in Node order, mobility grouping on.  Total pages: 96442
> Policy zone: Normal
> nommu_map_sg: overflow 13fc02000+4096 of device mask ffffffff
> ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> ata1.00: failed command: WRITE DMA
> ata1.00: cmd ca/00:10:f0:b3:53/00:00:00:00:00/e0 tag 0 dma 8192 out
>          res 50/00:00:f0:b3:53/00:00:00:00:00/a0 Emask 0x40 (internal error)
> ata1.00: status: { DRDY }
> ata1.00: configured for MWDMA2
> ata1: EH complete

it's know linux guest issue, see for workaround RHBZ 987871

alternatively you can start guest with 4Gb or more initial memory which also
makes linux kernel work properly or switch disk to virtio driver.

[...]
-- 
Regards,
  Igor