From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michal Novotny Subject: Re: [PATCH] qemu-xen-3.4-testing: Fix read-only image file handling Date: Tue, 08 Jun 2010 12:39:27 +0200 Message-ID: <4C0E1DDF.4030509@redhat.com> References: <4C0E15C7.9020606@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4C0E15C7.9020606@redhat.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On 06/08/2010 12:04 PM, Michal Novotny wrote: > On 06/07/2010 07:56 PM, Keir Fraser wrote: >> ... >> I suggest add some tracing to function dom0_init() in xenstored and see >> where that function is failing. The two most obvious places were the >> opening >> of those two files in /proc. If they exist then I'm not sure what >> else could >> be going wrong. >> >> Oh, you should be able to cat /proc/xen/ksd_port and get an integer >> value. >> /proc/xen/ksd_kva by contrast gets mmap()ed by xenstored. > Thank you all, I was able to make it running (using some qemu-dm example in the example) at least for my testing of HVM guest read-only image handling fix (I didn't try it for PV guests yet) and I have to confirm that my patch to fix read-only image file handling (sent to the list as the first e-mail in this thread) is working fine with both xen-3.4-testing and xen-4.1-unstable. The fix is for xen-iommu located in iommu-dir (downloaded from git). Is this the right list to post this patch to? It can't be going to qemu-devel list since this is really closely connected to xenstore which is not a part of qemu at all so this is for the xenstore layer of qemu-dm mainly. Thanks, Michal -- Michal Novotny, RHCE Virtualization Team (xen userspace), Red Hat