[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] blktap2: need more than 3 values to unpack
The tap:aio:/pathto/file.img syntax that you're using in your config was
changed before blktap2 was introduced. tap:tapdisk:aio:/pathto/file.img is
apparently the correct syntax now, though the README didn't get updated to
reflect this. Our blktap2 documentation is no better - I'll try to
remedy that this week.
If you're still seeing this error:
"Error: 'file' object has no attribute 'find'"
Then I might be able to help, but I'm not sure how to reproduce it. If
you send a log file and config for this latter error I'll take a look.
Yang seems to be reporting the same thing in another thread.
On Mon, 1 Jun 2009, Dan Magenheimer wrote:
Hmmm... trying blktap2 for the first time, using 19682.
I had thought that the syntax hadn't changed, but I am
getting what appears to be a parsing error on my vbd line.
"ValueError: need more than 3 values to unpack"
Thinking maybe that "w!" was the culprit, I changed
it to "w" with no change in result.
Looking at the python code that generated the error,
I tried to figure out the syntax by experimentation
but without luck. I tried:
but got "Error: 'file' object has no attribute 'find'"
To see if I could use the old blktap, I tried
but got the dreaded "Error: Device 768 (tap) could not be
connected. Hotplug scripts not working"
Am I missing something in the syntax for blktap2?
Is there a how-to or readme I didn't find? Or
is there some required dependency I don't know about
that is missing?
I thought maybe I had a bad install, so rebuilt and
reinstalled with the same result.
xend.log and config file attached.
P.S. I am trying blktap2 because both blktap and
file-backed fail. Blktap sometimes reads garbage
from the file and
Xen-devel mailing list