-
Couldn't load subscription status.
- Fork 128
add dax support #495
base: master
Are you sure you want to change the base?
add dax support #495
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
qemu docs says
- "slots=$N" should be equal to or larger than the total amount of
normal RAM devices and vNVDIMM devices, e.g. $N should be >= 2 here.
Do we need to specify additional ram slots when adding nvdimm? It looks like the guest only has one slot currently:
root@ubuntu-fio-2760258893:/# lshw -class memory
*-firmware
description: BIOS
vendor: Bochs
physical id: 0
version: Bochs
date: 01/01/2011
size: 96KiB
*-memory
description: System Memory
physical id: 1000
size: 128MiB
capacity: 128MiB
*-bank
description: DIMM RAM
physical id: 0
slot: DIMM 0
size: 128MiB
width: 64 bits
hypervisor/qemu/qemu.go
Outdated
| Execute: "human-monitor-command", | ||
| Arguments: map[string]interface{}{ | ||
| "command-line": "object_add memory-backend-file,id=mem" + strconv.Itoa(blockInfo.PmemId) + | ||
| ",share=off,mem-path=" + filename + ",size=" + strconv.FormatInt(size, 10), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
qemu docs says
"share=off", then guest writes won't be applied to the backend
file and thus will be invisible to other guests.
Does it mean all guest modification to rootfs will be lost?
|
updated. Hypervisor=qemu # or # Hypervisor=libvirt |
|
"EnableNvdimm" needs to be added to BootConfig. otherwise the PR breaks cases with the older qemus. |
Signed-off-by: Lai Jiangshan <jiangshanlai@gmail.com>
|
@laijs should we close this PR? |
Signed-off-by: Lai Jiangshan jiangshanlai@gmail.com