Displaying 6 results from an estimated 6 matches for "pmem0".
Did you mean:
pmem
2020 Jul 02
2
Re: Two questions about NVDIMM devices
Daniel P. Berrangé <berrange@redhat.com> writes:
> On Thu, Jul 02, 2020 at 01:21:15PM +0200, Milan Zamazal wrote:
>> Hi,
>>
>
>> I've met two situations with NVDIMM support in libvirt where I'm not
>> sure all the parties (libvirt & I) do the things correctly.
>>
>> The first problem is with memory alignment and size changes. In
2020 Jul 09
0
NVDIMM in devdax mode and SELinux (was: Two questions about NVDIMM devices)
...nuine bug.
>
> OK, I'll try to find out what and where is the problem exactly.
The problem apparently is that /dev/dax* is a character device rather
than a block device (such as /dev/pmem*), which is not expected by
SELinux policy rules.
This is an NVDIMM in fsdax mode:
# ls -lZ /dev/pmem0
brw-rw----. 1 root disk system_u:object_r:device_t:s0 259, 0 Jul 9 11:39 /dev/pmem0
This is the same NVDIMM reconfigured as devdax:
# ls -lZ /dev/dax0.0
crw-------. 1 root root system_u:object_r:device_t:s0 252, 5 Jul 9 11:43 /dev/dax0.0
(Unix permissions are different, but when I chang...
2016 May 18
1
[PATCH v3] launch: direct: Add DAX root filesystem support.
v2 -> v3:
- Rebase on top of the other patches.
Rich.
2016 May 17
1
[PATCH v2] launch: direct: Add DAX root filesystem support.
NOTE: not for upstream, yet.
v1 -> v2:
- Remove the dependency on enabling ACPI, since ACPI is now
enabled all the time.
Rich.
2016 May 16
0
[PATCH] launch: direct: Add DAX root filesystem support.
...statbuf.st_size);
ADD_CMDLINE ("-device");
- ADD_CMDLINE (VIRTIO_BLK ",drive=appliance");
- }
+ ADD_CMDLINE ("nvdimm,memdev=mem1,id=nv1");
- appliance_dev = make_appliance_dev (g, virtio_scsi);
+ appliance_dev = safe_strdup (g, "/dev/pmem0");
+ } else {
+ ADD_CMDLINE ("-drive");
+ ADD_CMDLINE_PRINTF ("file=%s,snapshot=on,id=appliance,"
+ "cache=unsafe,if=none,format=raw",
+ appliance);
+
+ if (virtio_scsi) {
+ ADD_CMDLINE (&q...
2020 May 14
0
[virtio-dev] [PATCH v3 00/15] virtio-mem: paravirtualized memory
...reproduce this warning with set file as nvdimm with following command.
> sudo /home/teawater/qemu/qemu/x86_64-softmmu/qemu-system-x86_64 -machine pc,accel=kvm,kernel_irqchip,nvdimm -no-reboot -nographic -kernel /home/teawater/kernel/bk2/arch/x86/boot/bzImage -append "console=ttyS0 root=/dev/pmem0 swiotlb=noforce" -m 1g,slots=1,maxmem=2G -smp 1 -device nvdimm,id=nv0,memdev=mem0 -object memory-backend-file,id=mem0,mem-path=/home/teawater/old.img,size=268435456 -monitor unix:/home/teawater/qemu/m,server,nowait
>
> Best,
> Hui
--
Thanks,
David / dhildenb