| 2018-01-29 02:40:33 |
quanxian |
bug |
|
|
added bug |
| 2018-01-29 18:26:58 |
Christian Ehrhardt |
intel: status |
New |
Incomplete |
|
| 2018-05-01 09:36:05 |
quanxian |
description |
Description:
When the host persistent memory is used as the backend of vNVDIMM, QEMU itself may write to the host pmem, e.g., in vNVDIMM label emulation and live migration. In those cases, QEMU needs to take necessary operations (e.g., flush&fence after writes, or store with non-temporal hint) to ensure the data persistence of its own writes to PMEM. Therefore, data on vNVDIMM can be in a consistent status on abnormal termination of QEMU (e.g., QEMU/host kernel crash, host power failure, etc.). Unfortunately, such operations are missed in current QEMU implementation.
Target Qemu Release:2.13
Target Release: 18.04 |
Description:
When the host persistent memory is used as the backend of vNVDIMM, QEMU itself may write to the host pmem, e.g., in vNVDIMM label emulation and live migration. In those cases, QEMU needs to take necessary operations (e.g., flush&fence after writes, or store with non-temporal hint) to ensure the data persistence of its own writes to PMEM. Therefore, data on vNVDIMM can be in a consistent status on abnormal termination of QEMU (e.g., QEMU/host kernel crash, host power failure, etc.). Unfortunately, such operations are missed in current QEMU implementation.
Target Kernel Release:TBD
Target Release: 18.10 |
|
| 2018-05-01 09:36:28 |
quanxian |
tags |
|
intel-kernel-18.10 |
|
| 2018-07-26 15:44:08 |
Joseph Salisbury |
intel: importance |
Undecided |
Medium |
|
| 2018-07-26 15:44:12 |
Joseph Salisbury |
intel: status |
Incomplete |
Triaged |
|
| 2018-07-26 15:44:17 |
Joseph Salisbury |
tags |
intel-kernel-18.10 |
intel-kernel-18.10 kernel-da-key |
|
| 2018-08-13 02:11:56 |
quanxian |
information type |
Proprietary |
Public |
|
| 2018-08-24 07:28:26 |
quanxian |
tags |
intel-kernel-18.10 kernel-da-key |
intel-virt-18.10 kernel-da-key |
|
| 2018-08-24 07:28:57 |
quanxian |
description |
Description:
When the host persistent memory is used as the backend of vNVDIMM, QEMU itself may write to the host pmem, e.g., in vNVDIMM label emulation and live migration. In those cases, QEMU needs to take necessary operations (e.g., flush&fence after writes, or store with non-temporal hint) to ensure the data persistence of its own writes to PMEM. Therefore, data on vNVDIMM can be in a consistent status on abnormal termination of QEMU (e.g., QEMU/host kernel crash, host power failure, etc.). Unfortunately, such operations are missed in current QEMU implementation.
Target Kernel Release:TBD
Target Release: 18.10 |
Description:
When the host persistent memory is used as the backend of vNVDIMM, QEMU itself may write to the host pmem, e.g., in vNVDIMM label emulation and live migration. In those cases, QEMU needs to take necessary operations (e.g., flush&fence after writes, or store with non-temporal hint) to ensure the data persistence of its own writes to PMEM. Therefore, data on vNVDIMM can be in a consistent status on abnormal termination of QEMU (e.g., QEMU/host kernel crash, host power failure, etc.). Unfortunately, such operations are missed in current QEMU implementation.
Target QEMU Release:3.0.0
Target Release: 18.10 |
|
| 2018-09-05 10:18:39 |
Christian Ehrhardt |
bug task added |
|
qemu (Ubuntu) |
|
| 2018-09-05 10:19:01 |
Launchpad Janitor |
qemu (Ubuntu): status |
New |
Confirmed |
|
| 2018-09-05 10:32:27 |
Christian Ehrhardt |
tags |
intel-virt-18.10 kernel-da-key |
intel-virt-18.10 kernel-da-key qemu-19.04 |
|
| 2018-09-05 14:52:50 |
Paul Lai |
bug |
|
|
added subscriber Paul Lai |
| 2018-10-26 05:01:38 |
quanxian |
tags |
intel-virt-18.10 kernel-da-key qemu-19.04 |
intel-virt-19.04 kernel-da-key qemu-19.04 |
|
| 2019-01-28 03:04:32 |
quanxian |
description |
Description:
When the host persistent memory is used as the backend of vNVDIMM, QEMU itself may write to the host pmem, e.g., in vNVDIMM label emulation and live migration. In those cases, QEMU needs to take necessary operations (e.g., flush&fence after writes, or store with non-temporal hint) to ensure the data persistence of its own writes to PMEM. Therefore, data on vNVDIMM can be in a consistent status on abnormal termination of QEMU (e.g., QEMU/host kernel crash, host power failure, etc.). Unfortunately, such operations are missed in current QEMU implementation.
Target QEMU Release:3.0.0
Target Release: 18.10 |
Description:
When the host persistent memory is used as the backend of vNVDIMM, QEMU itself may write to the host pmem, e.g., in vNVDIMM label emulation and live migration. In those cases, QEMU needs to take necessary operations (e.g., flush&fence after writes, or store with non-temporal hint) to ensure the data persistence of its own writes to PMEM. Therefore, data on vNVDIMM can be in a consistent status on abnormal termination of QEMU (e.g., QEMU/host kernel crash, host power failure, etc.). Unfortunately, such operations are missed in current QEMU implementation.
Target QEMU Release:3.0.0
Target Release: 19.04 |
|
| 2019-01-29 06:53:24 |
Christian Ehrhardt |
tags |
intel-virt-19.04 kernel-da-key qemu-19.04 |
intel-virt-19.04 kernel-da-key qemu-19.04 server-triage-discuss |
|
| 2019-01-30 15:51:41 |
Christian Ehrhardt |
tags |
intel-virt-19.04 kernel-da-key qemu-19.04 server-triage-discuss |
intel-virt-19.04 kernel-da-key qemu-19.04 |
|
| 2019-01-31 08:26:58 |
Christian Ehrhardt |
tags |
intel-virt-19.04 kernel-da-key qemu-19.04 |
intel-virt-19.04 kernel-da-key qemu-19.10 |
|
| 2019-05-06 08:39:53 |
quanxian |
intel: status |
Triaged |
Fix Released |
|
| 2019-05-06 08:39:57 |
quanxian |
qemu (Ubuntu): status |
Confirmed |
Fix Released |
|
