| |
|
 |
|
 |
|
|
|
| |
|
|
xen-users
Re: [Xen-users] qcow problems
Hi Marcel,
just noticed your post on this. You are right -- a patch to
security.py broke blktap disk name parsing. I've just checked in a
fix.
a.
On 11/2/06, Marcel Ritter <Marcel.Ritter@xxxxxxxxxxxxxxxxxxxx> wrote:
Hi!
Can someone please post a working qcow image setup? Is it currently possible
to use the "copy on write" feature, and if so how?
I'm trying to get this running (with Xen unstable), but the
documentation seems
to be out of date or incorrect.
According to tools/blktap/README it should be possible to add qcow images
to dom 0 by running:
linux# xm block-attach 0 tap:qcow:/tmp/hda /dev/xvda1 w 0
However this results in the error message:
Error: "Resource spec 'tap:qcow:/tmp/hda' contains no ':' delimiter"
The reason seems to be located in tools/python/xen/util/security.py:
...
# sanity check on resource name
try:
(type, resfile) = resource.split(":")
except:
err("Resource spec '%s' contains no ':' delimiter" % resource)
...
As far as I understand python, this causes an exception if the number
of ':'s is not 1. Perhaps this is the reason for "xm create" to fail
when using
...
disk = [ 'tap:qcow:/tmp/hda,w']
....
in the VM config file (example from tools/blktap/README)
So what's the correct way to set this up?
Hope someone can help.
TIA,
Marcel
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
| |
|
Home