Re: [libvirt] Error when creating VM with persistent memory

2019-09-10 Thread Michal Prívozník
On 9/4/19 6:31 PM, Dan Williams wrote: > On Wed, Sep 4, 2019 at 12:56 AM Seema Pandit wrote: >> >> Actually there is still some issue around this. When trying to start another >> VM, so using even more pmem, there is a different issue now. Error copied >> below. >> >> []# virsh start manual_clon

Re: [libvirt] Error when creating VM with persistent memory

2019-09-04 Thread Dan Williams
On Wed, Sep 4, 2019 at 12:56 AM Seema Pandit wrote: > > Actually there is still some issue around this. When trying to start another > VM, so using even more pmem, there is a different issue now. Error copied > below. > > []# virsh start manual_clone > > error: Failed to start domain manual_clon

Re: [libvirt] Error when creating VM with persistent memory

2019-09-04 Thread Dan Williams
On Mon, Sep 2, 2019 at 10:10 AM Seema Pandit wrote: > > After adding the memoryBacking tag in xml as below (in addition, to other xml > changes to add nvdimm), virsh could allocate AD memory larger than the system > RAM and VMs could start successfully. > > > > > > > > > > > > This

Re: [libvirt] Error when creating VM with persistent memory

2019-09-04 Thread Seema Pandit
Actually there is still some issue around this. When trying to start another VM, so using even more pmem, there is a different issue now. Error copied below. []# virsh start manual_clone error: Failed to start domain manual_clone error: internal error: qemu unexpectedly closed the monitor: ftrun

Re: [libvirt] Error when creating VM with persistent memory

2019-09-02 Thread Seema Pandit
After adding the memoryBacking tag in xml as below (in addition, to other xml changes to add nvdimm), virsh could allocate AD memory larger than the system RAM and VMs could start successfully. This adds share=yes in command line. -object memory-backend-file,id=memnvdimm0,pre

Re: [libvirt] Error when creating VM with persistent memory

2019-09-01 Thread Michal Privoznik
On 8/31/19 7:33 PM, Seema Pandit wrote: Hi Michal, Thank you for the reply. I was having issues compiling qemu code on fedora29. So instead of dropping prealloc in virsh, tried adding prealloc=yes in qemu command line. prealloc=yes works. It does not lead to using more system memory when using DA

Re: [libvirt] Error when creating VM with persistent memory

2019-08-31 Thread Seema Pandit
Hi Michal, Thank you for the reply. I was having issues compiling qemu code on fedora29. So instead of dropping prealloc in virsh, tried adding prealloc=yes in qemu command line. prealloc=yes works. It does not lead to using more system memory when using DAX. +Dan Here are the steps: ndctl create-

Re: [libvirt] Error when creating VM with persistent memory

2019-08-28 Thread Michal Privoznik
On 8/27/19 9:58 AM, Seema Pandit wrote: > error: internal error: qemu unexpectedly closed the monitor: ftruncate: > Invalid argument 2019-08-22T04:16:08.744402Z qemu-system-x86_64: -object > memory-backend-file,id=memnvdimm0,prealloc=yes,mem-path=/dev/dax1.0,size=403726925824: > unable to map backi

[libvirt] Error when creating VM with persistent memory

2019-08-27 Thread Seema Pandit
I am trying to create a VM with added persistent memory using virsh. It fails when persistent memory namespace size is larger than available system memory. Please see error below, prealloc=yes is set in the command line. For dax type namespace, as I understand, prealloc should not be needed. Is thi