All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Timo Benk <timo.benk@gmx.de>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: 3.0.3rc3 qcow image created with qemu-img not usable?
Date: Thu, 12 Oct 2006 08:02:51 -0500	[thread overview]
Message-ID: <452E3CFB.5030702@us.ibm.com> (raw)
In-Reply-To: <452DFFE9.20606@gmx.de>

You cannot attach block devices to Domain-0.  Furthermore, you cannot 
attach non-raw file-based block devices to paravirtual domains.

Regards,

Anthony Liugoir

Timo Benk wrote:
> Hi,
> 
> i am new to the qcow image format, so please forgive me if the following
> is just totally stupid:-)
> 
> I try to use a qcow formatted image in Xen created by qemu-img.
> 
> # qemu-img create -f qcow /tmp/test.img 1G
> 
> Then i try to attach that image to Domain-0.
> 
> # xm block-attach Domain-0 tap:qcow:/tmp/test.img /dev/xvda1 w 0
> 
> No error message so far, but ...
> 
> # mount /dev/xvda1 /mnt
> mount: special device /dev/xvda1 does not exist
> 
> # xm block-list Domain-0
> Vdev  BE handle state evt-ch ring-ref BE-path
> 51714    0    0     3      23     8
>   /local/domain/0/backend/tap/0/51714
> 
> # xm block-detach Domain-0 /dev/xvda1
> 
> # xm block-list Domain-0
> Vdev  BE handle state evt-ch ring-ref BE-path
> 51714    0    0     3      23     8
>   /local/domain/0/backend/tap/0/51714
> 
> qcow images created with qcow-create are working without any problems.
> 
> And a few additional questions i have:
> 
> - Is qcow encryption supported?
> - is qcow compression supported?
> 
> Greetings,
> -timo
> 

  reply	other threads:[~2006-10-12 13:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-12  8:42 3.0.3rc3 qcow image created with qemu-img not usable? Timo Benk
2006-10-12 13:02 ` Anthony Liguori [this message]
2006-10-12 13:17   ` Timo Benk
2006-10-12 13:59     ` Anthony Liguori

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=452E3CFB.5030702@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=timo.benk@gmx.de \
    --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.