WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] qcow support

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] qcow support
From: "Fabian Flägel" <fabigant@xxxxxxxxxxxxxx>
Date: Thu, 25 Sep 2008 11:37:57 +0200
Delivery-date: Thu, 25 Sep 2008 02:38:37 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=DNocUQsKUhK2X+jfCyoAQWYuL+kuz+01U7GxcvM7Dys=; b=Jfv6Adp6nkx92Vca6aV2YbBOiMWpDvnhLX/iI5+SeCJTKvV/bSzmyTzDmkF41eY7+D 7Cr96XH+QdX//5mWhPXOxijNZbkvcMc+UeXFShiDAjul+1LRvNMOMxn1ppIVNQSUwu0s b7NFe0RuSQaGW+QFX1JSqPCi8gK8s9kCxRbew=
Domainkey-signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=xnIwAWak3kc6D7KhjkR4mkjbChPL3peag45oLrrzA6TWD1a93xQvxlgxqfKICYsi1g 9yaq2rOjxBWaA0FoQYmjTeQYC2p8G4A834DyOxiOR+3sMioRDN+gGBmUV01+S3F341VU NdJMoTw+BqUEgEXG2mLZveYmZ4cJqBrODq0xs=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hi,

i would like to use qcow2-sparse-images which point to a backup-file.
After reading this: http://wiki.xensource.com/xenwiki/DmUserspace i
figured out that this feature seems to be unsupported by the ubuntu
8.04 LTS kernel and xen-3.2.1.

Is this a ubuntu-specific problem, or is it solved in Suse, Red Hat,
XenSource, whatever?

When i try to block-attach it, xm displays no error, but the device is
not created.

# xm block-attach 0 tap:qcow:/var/xen/domains/dapper10/test.img /dev/sdh1 w 0
# mount /dev/sdh1 /mnt/test/
mount: special device /dev/sdh1 does not exist

In the config file  'tap:qcow:/var/xen/domains/dapper10/test.img,sda2,w',

--> test.img is in use. And i thought there is no /dev/sdh1?
xm block-detach ...
Now the VM boots, but stucks after kernel waiting for
root-filesystem... In my understanding, test.img references to
disk.img, which is a raw-image, and should use on the first boot every
block from disk.img including the fs-type, etc.

# less test.img
shows the correct reference to disk.img, but it don't work either.

Any ideas?

Regards
Fabian

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] qcow support, Fabian Flägel <=