From: Ian Campbell <ian.campbell@citrix.com>
To: "Fabio Fantoni" <fabio.fantoni@m2r.biz>,
"osstest service owner" <osstest-admin@xenproject.org>,
xen-devel@lists.xensource.com,
"Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>,
"David Vrabel" <david.vrabel@citrix.com>
Subject: Re: [linux-3.14 bisection] complete test-amd64-i386-xl-qcow2
Date: Tue, 1 Sep 2015 11:10:24 +0100 [thread overview]
Message-ID: <1441102224.27618.19.camel@citrix.com> (raw)
In-Reply-To: <55E5721B.8080704@m2r.biz>
On Tue, 2015-09-01 at 11:38 +0200, Fabio Fantoni wrote:
> Hi, recently I tested qcow2 overlay on raw base as domUs disks (qcow2
> format in xl already specified) and I found that disk was always
> corrupted (without nothing about in logs).
> I tried with diffent versions of upstream qemu (2.2 and 2.4) and dom0
> kernel (3.2 from wheezy repo and 3.16 from wheezy-backports), maybe also
> related to this?
Not sure, doesn't sound too much like this one. Probably more likely a qemu
or xl issue, I suggest you raise it in its own thread with details of what
you are doing.
>
Ian.
next prev parent reply other threads:[~2015-09-01 10:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-26 20:02 [linux-3.14 bisection] complete test-amd64-i386-xl-qcow2 osstest service owner
2015-09-01 9:19 ` Ian Campbell
2015-09-01 9:38 ` Fabio Fantoni
2015-09-01 10:10 ` Ian Campbell [this message]
2015-09-01 9:57 ` Ian Jackson
2015-09-01 10:05 ` Ian Campbell
2015-09-02 9:03 ` Ian Campbell
2015-09-02 9:18 ` Ian Campbell
2015-09-03 11:05 ` Luis Henriques
2015-09-03 11:16 ` [Xen-devel] " David Vrabel
2015-09-03 12:21 ` Luis Henriques
2015-09-11 15:10 ` Ian Campbell
2015-09-11 15:51 ` Greg Kroah-Hartman
2015-09-11 15:55 ` Ian Campbell
2015-09-26 17:30 ` Greg Kroah-Hartman
2015-09-28 9:27 ` Ian Campbell
2015-09-28 9:43 ` Ian Campbell
2015-10-08 22:14 ` Ben Hutchings
2015-10-09 9:15 ` Ian Campbell
2015-10-12 10:11 ` [Xen-devel] " David Vrabel
2015-10-12 12:56 ` Ben Hutchings
2015-10-12 13:01 ` David Vrabel
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=1441102224.27618.19.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=david.vrabel@citrix.com \
--cc=fabio.fantoni@m2r.biz \
--cc=marmarek@invisiblethingslab.com \
--cc=osstest-admin@xenproject.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).