From: Michal Novotny <minovotn@redhat.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] qemu-xen-3.4-testing: Fix read-only image file handling
Date: Tue, 08 Jun 2010 12:39:27 +0200 [thread overview]
Message-ID: <4C0E1DDF.4030509@redhat.com> (raw)
In-Reply-To: <4C0E15C7.9020606@redhat.com>
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<minovotn@redhat.com>, RHCE
Virtualization Team (xen userspace), Red Hat
next prev parent reply other threads:[~2010-06-08 10:39 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-03 14:04 [PATCH] qemu-xen-3.4-testing: Fix read-only image file handling Michal Novotny
2010-06-03 14:12 ` Michal Novotny
2010-06-04 9:37 ` Michal Novotny
2010-06-04 10:42 ` Pasi Kärkkäinen
2010-06-04 10:57 ` Michal Novotny
2010-06-04 13:00 ` Michal Novotny
2010-06-04 13:11 ` Keir Fraser
2010-06-04 13:12 ` Pasi Kärkkäinen
2010-06-07 11:21 ` Michal Novotny
2010-06-07 11:39 ` Keir Fraser
2010-06-07 13:09 ` Michal Novotny
2010-06-07 13:14 ` Pasi Kärkkäinen
2010-06-07 18:24 ` Jeremy Fitzhardinge
2010-06-07 11:45 ` Pasi Kärkkäinen
2010-06-07 13:10 ` Michal Novotny
2010-06-07 13:14 ` Michal Novotny
2010-06-07 13:19 ` Pasi Kärkkäinen
2010-06-07 13:21 ` Michal Novotny
2010-06-07 13:25 ` Michal Novotny
2010-06-07 13:36 ` Michal Novotny
2010-06-07 13:46 ` Keir Fraser
2010-06-07 15:00 ` Michal Novotny
2010-06-07 15:17 ` M A Young
2010-06-07 15:28 ` Michal Novotny
2010-06-07 14:56 ` Pasi Kärkkäinen
2010-06-07 15:02 ` Michal Novotny
2010-06-07 16:12 ` Konrad Rzeszutek Wilk
2010-06-07 16:27 ` Michal Novotny
2010-06-07 16:34 ` Keir Fraser
2010-06-07 16:37 ` Michal Novotny
2010-06-07 17:56 ` Keir Fraser
2010-06-08 10:04 ` Michal Novotny
2010-06-08 10:39 ` Michal Novotny [this message]
2010-06-08 10:50 ` Keir Fraser
2010-06-08 10:52 ` Michal Novotny
2010-06-08 11:03 ` Keir Fraser
2010-06-08 11:06 ` Michal Novotny
2010-06-08 10:53 ` Keir Fraser
2010-06-08 10:54 ` Michal Novotny
2010-06-08 11:11 ` M A Young
2010-06-08 11:15 ` Michal Novotny
2010-06-07 14:06 ` Pasi Kärkkäinen
2010-06-07 13:25 ` M A Young
[not found] <C82EBB27.16AFC%keir.fraser@eu.citrix.com>
2010-06-04 13:45 ` Michal Novotny
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C0E1DDF.4030509@redhat.com \
--to=minovotn@redhat.com \
--cc=keir.fraser@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.