qemu-devel
[Top][All Lists]
Advanced
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: Kolk, G. van der
Subject: Re: [Qemu-devel] where can I find the latest memory hot plugging patch for Qemu?
Date: Thu, 19 Jun 2014 10:28:41 +0000
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
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:00:00:00/00:00:00:00:00/a0 Emask 0x40 (internal error)
ata1.00: status: { DRDY }
ata1.00: configured for MWDMA2
ata1: EH complete
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:00:00:00/00:00:00:00:00/a0 Emask 0x40 (internal error)
ata1.00: status: { DRDY }
ata1.00: configured for MWDMA2
ata1: EH complete
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:00:00:00/00:00:00:00:00/a0 Emask 0x40 (internal error)
ata1.00: status: { DRDY }
ata1.00: configured for MWDMA2
ata1: EH complete
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:00:00:00/00:00:00:00:00/a0 Emask 0x40 (internal error)
ata1.00: status: { DRDY }
ata1.00: configured for MWDMA2
ata1: EH complete
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:00:00:00/00:00:00:00:00/a0 Emask 0x40 (internal error)
ata1.00: status: { DRDY }
ata1.00: configured for MWDMA2
sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
sd 0:0:0:0: [sda] Sense Key : Aborted Command [current] [descriptor]
Descriptor sense data with sense descriptors (in hex):
        72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00 
        00 00 00 00 
sd 0:0:0:0: [sda] Add. Sense: No additional sense information
sd 0:0:0:0: [sda] CDB: Write(10): 2a 00 00 53 b3 f0 00 00 10 00
ata1: EH complete
Aborting journal on device dm-0-8.
EXT4-fs error (device dm-0) in ext4_reserve_inode_write: Journal has aborted
EXT4-fs error (device dm-0) in ext4_dirty_inode: Journal has aborted
EXT4-fs error (device dm-0): ext4_journal_start_sb: Detected aborted journal
EXT4-fs (dm-0): Remounting filesystem read-only
nommu_map_sg: overflow 13fc04000+4096 of device mask ffffffff
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:08:28:b1:90/00:00:00:00:00/e0 tag 0 dma 4096 in
         res 50/00:00:c0:dc:93/00:00:00:00:00/e0 Emask 0x40 (internal error)
ata1.00: status: { DRDY }
ata1.00: configured for MWDMA2
ata1: EH complete
nommu_map_sg: overflow 13fc04000+4096 of device mask ffffffff
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:08:28:b1:90/00:00:00:00:00/e0 tag 0 dma 4096 in
         res 50/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x40 (internal error)
ata1.00: status: { DRDY }
ata1.00: configured for MWDMA2
ata1: EH complete
nommu_map_sg: overflow 13fc04000+4096 of device mask ffffffff
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:08:28:b1:90/00:00:00:00:00/e0 tag 0 dma 4096 in
         res 50/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x40 (internal error)
ata1.00: status: { DRDY }
ata1.00: configured for MWDMA2
ata1: EH complete
nommu_map_sg: overflow 13fc04000+4096 of device mask ffffffff
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:08:28:b1:90/00:00:00:00:00/e0 tag 0 dma 4096 in
         res 50/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x40 (internal error)
ata1.00: status: { DRDY }
ata1.00: configured for MWDMA2
ata1: EH complete
nommu_map_sg: overflow 13fc04000+4096 of device mask ffffffff
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:08:28:b1:90/00:00:00:00:00/e0 tag 0 dma 4096 in
         res 50/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x40 (internal error)
ata1.00: status: { DRDY }
ata1.00: configured for MWDMA2
ata1: EH complete
nommu_map_sg: overflow 13fc04000+4096 of device mask ffffffff
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:08:28:b1:90/00:00:00:00:00/e0 tag 0 dma 4096 in
         res 50/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x40 (internal error)
ata1.00: status: { DRDY }
ata1.00: configured for MWDMA2
sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
sd 0:0:0:0: [sda] Sense Key : Aborted Command [current] [descriptor]
Descriptor sense data with sense descriptors (in hex):
        72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00 
        00 00 00 00 
sd 0:0:0:0: [sda] Add. Sense: No additional sense information
sd 0:0:0:0: [sda] CDB: Read(10): 28 00 00 90 b1 28 00 00 08 00
ata1: EH complete
EXT4-fs error (device dm-0): ext4_find_entry: reading directory #261395 offset 0

On 19 Jun 2014, at 11:21 ,  wrote:

Oops,

RTFM! :)
PS:
  Windows guest requires SRAT table for hotplug to work so add an extra option:
   -numa node
  to QEMU command line.
So status is, windows works. linux does not.

See attachment for more info

Regards,

Gerrit

On 19 Jun 2014, at 11:07 , Kolk, G. van der <address@hidden> wrote:

Hi Igor,

I’m trying the memory hot plug. But I have trouble getting it to work. This is what happens. I tried some tested guest OSes and some untested.

I tried three flavours of linux with automatic or manual memory hot plug support:
CentOS 6 cpu hotplug: works memory h<Screen Shot 2014-06-19 at 11.19.58 .png>otplug: Kernel sees memory, but ext4 filesystem crashes, says it’s mounted readonly, but cannot execute anything to try and read the logs.
latest Ubuntu and debian: same problem

Windows 2012: cpu hotplug: works memory hotplug: windows keeps running, but does not see the memory. nothing shows up in event viewer.

Used commands to add memory:
(qemu) object_add memory-ram,id=mem1,size=1G
object_add memory-ram,id=mem1,size=1G
(qemu) device_add dimm,id=dimm1,memdev=mem1
device_add dimm,id=dimm1,memdev=mem1

Am I doing something wrong? How can I make this work? If you need any logs. Let me know which one.

Regards,

Gerrit

On 23 Apr 2014, at 17:40 , Igor Mammedov <address@hidden> wrote:

On Wed, 23 Apr 2014 12:16:30 +0000
"Kolk, G. van der" <address@hidden> wrote:

Dear Qemu developers,

I'm doing a masters thesis project which involves Qemu. Especially cpu and memory hot plugging. But I have a hard time  finding the right git repository which contains the latest memory hot plugging work. Can anyone please point me in the right direction?

the last version was posted here:
https://lists.gnu.org/archive/html/qemu-devel/2014-04/msg00734.html


Regards,

Gerrit van der Kolk


--
Regards,
 Igor



reply via email to
[Prev in Thread] Current Thread [Next in Thread]