From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:55653) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b2MWj-0002nm-KB for qemu-devel@nongnu.org; Mon, 16 May 2016 13:42:01 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1b2MWe-0003kV-N6 for qemu-devel@nongnu.org; Mon, 16 May 2016 13:41:57 -0400 Received: from mga11.intel.com ([192.55.52.93]:65209) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b2MWe-0003kF-HO for qemu-devel@nongnu.org; Mon, 16 May 2016 13:41:52 -0400 References: <20160516150401.GC28935@redhat.com> From: Xiao Guangrong Message-ID: <573A05D4.9050906@linux.intel.com> Date: Tue, 17 May 2016 01:39:32 +0800 MIME-Version: 1.0 In-Reply-To: <20160516150401.GC28935@redhat.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] Question about vNVDIMM file format List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Richard W.M. Jones" , qemu-devel@nongnu.org On 05/16/2016 11:04 PM, Richard W.M. Jones wrote: > I'm playing with ext4 and DAX. Thanks for your try, Rich! :) > > I'm using: > > -object memory-backend-file,id=mem1,share,mem-path=/var/tmp/pmem,size=4G \ > -device nvdimm,memdev=mem1,id=nv1 > > where /var/tmp/pmem is a 4 GB ext4 filesystem image (no partition > table). I can mount this in the guest using: > > mount -o dax /dev/pmem0 /mnt > > and everything appears to work. > > I read in the mailing list that the pmem file has some internal > structure for storing config data, stored in the last 128 KB of the > file. Is that still the case? The patchset supporting label data has not been merged yet so currently there is no label data for vNVDIMM device.