Xu Nakajima
2007-Mar-13 09:13 UTC
[Xen-users] xm block-attach and qcow image - why does it fail ? second try
Hello, This is a second post, with a trial which is different from the first one , in order to solve my blcok-attach problem. I tried the following two actions, according to the blktap readme: qcow-create 1000 qcowFile.img Creating file size 1048576000 Created cksum: 1813725440 then xm block-attach 0 tap:qcow:qcowFile.img /dev/xvda1 w 0 I see in the /var/log/xen/xend.log: [2007-03-13 11:03:32 xend 2423] DEBUG (blkif:24) exception looking up device number for /dev/xvda1: [Errno 2] No such file or directory: ''/dev/xvda1'' Running: mount /dev/xvda1 /mnt/disk mount: special device /dev/xvda1 does not exist ls /dev/xvda* ls: No match. houldn''t this qcow-create and xm block-attach work ? should I run before "mknod /dev/xvda1"? which parameters should I pass? Can somebody please try this ? I hope that this mystery will be solved ! Regards, Xu ____________________________________________________________________________________ Never miss an email again! Yahoo! Toolbar alerts you the instant new Mail arrives. http://tools.search.yahoo.com/toolbar/features/mail/ _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Reasonably Related Threads
- qcow-create buffer overflow?
- mounting using "xm block-attach" does not work; "special device /dev/xvda1 does not exist." error
- QCOW snapshots and recursive file backings
- Bug#695645: xen-utils-common: xm block-attach does not create /dev/xvd* devices on dom0
- Qcow files