From mboxrd@z Thu Jan 1 00:00:00 1970 From: Juergen Gross Subject: Re: Hypervisor error messages after xl block-detach with linux 3.18-rc5 Date: Tue, 25 Nov 2014 18:01:24 +0100 Message-ID: <5474B5E4.9000908@suse.com> References: <546EFAE3.80404@suse.com> <20141121135747.GB2886@laptop.dumpdata.com> <5473008C.4080604@suse.com> <1416823327.26329.25.camel@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1416823327.26329.25.camel@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Campbell Cc: "xen-devel@lists.xensource.com" , Stefano Stabellini List-Id: xen-devel@lists.xenproject.org On 11/24/2014 11:02 AM, Ian Campbell wrote: > On Mon, 2014-11-24 at 10:55 +0100, Juergen Gross wrote: >> On 11/21/2014 02:57 PM, Konrad Rzeszutek Wilk wrote: >>> On Fri, Nov 21, 2014 at 09:42:11AM +0100, Juergen Gross wrote: >>>> Hi, >>>> >>>> while testing my "linear p2m list" patches I saw the following >>>> problem (even without my patches in place): >>>> >>>> In dom0 running linux 3.18-rc5 on top of Xen 4.4.1 I modified the >>>> disk image of a guest by attaching it to dom0: >>>> >>>> xl block-attach 0 file:/var/lib/libvirt/images/opensuse13-1/xvda,xvda,w >>>> mount /dev/xvda2 /mnt >>>> ... >>>> umount /mnt >>>> xl block-detach 0 xvda >> >> Did some more testing: >> - Seems to occur only when attaching a block device to dom0 > > That means a qdisk backed situation then, I think. > > Is your qemu up to date? > > http://xenbits.xen.org/gitweb/?p=qemu-upstream-unstable.git;a=commit;h=abbbc2f09a53f8f9ee565356ab11a78af006e45e resulted in slightly different messages, but could be related? Newest qemu and xen-unstable together with my dom0 kernel patch made all issues go away at a first glance. Juergen