From: 白い熊@相撲道 <guix-devel_gnu.org@sumou.com>
To: guix-devel@gnu.org
Subject: qemu-nbd: Failed to bind socket: No such file or directory
Date: Wed, 25 Mar 2015 05:26:52 +0100 [thread overview]
Message-ID: <cd4795b07378aa8c33c1b7f50ff09253@hcoop.net> (raw)
I'm completely baffled...
Using qemu, I'm trying to mount a qcow2 image to manipulate its files. I
insmoded the nbd kernel module. The block devices exist:
~$ ls -l /dev/nbd*
brw-rw---- 1 root disk 43, 0 Mar 24 18:09 /dev/nbd0
brw-rw---- 1 root disk 43, 1 Mar 24 18:09 /dev/nbd1
brw-rw---- 1 root disk 43, 10 Mar 24 18:09 /dev/nbd10
brw-rw---- 1 root disk 43, 11 Mar 24 18:09 /dev/nbd11
brw-rw---- 1 root disk 43, 12 Mar 24 18:09 /dev/nbd12
brw-rw---- 1 root disk 43, 13 Mar 24 18:09 /dev/nbd13
brw-rw---- 1 root disk 43, 14 Mar 24 18:09 /dev/nbd14
brw-rw---- 1 root disk 43, 15 Mar 24 18:09 /dev/nbd15
brw-rw---- 1 root disk 43, 2 Mar 24 18:09 /dev/nbd2
brw-rw---- 1 root disk 43, 3 Mar 24 18:09 /dev/nbd3
brw-rw---- 1 root disk 43, 4 Mar 24 18:09 /dev/nbd4
brw-rw---- 1 root disk 43, 5 Mar 24 18:09 /dev/nbd5
brw-rw---- 1 root disk 43, 6 Mar 24 18:09 /dev/nbd6
brw-rw---- 1 root disk 43, 7 Mar 24 18:09 /dev/nbd7
brw-rw---- 1 root disk 43, 8 Mar 24 18:09 /dev/nbd8
brw-rw---- 1 root disk 43, 9 Mar 24 18:09 /dev/nbd9
But:
~$ sudo qemu-nbd -c /dev/nbd0 disk.qcow2
Failed to bind socket: No such file or directory
What is going on? I've searched the web, but have no idea what the
problem could be.
Does anyone have an idea what is the issue?
--
白い熊@相撲道
next reply other threads:[~2015-03-25 4:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-25 4:26 白い熊@相撲道 [this message]
2015-03-26 21:24 ` qemu-nbd: Failed to bind socket: No such file or directory Ludovic Courtès
2015-03-28 0:29 ` 白い熊@相撲道
2015-03-28 14:41 ` Ludovic Courtès
2015-04-26 4:07 ` 宋文武
2015-04-29 20:28 ` Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cd4795b07378aa8c33c1b7f50ff09253@hcoop.net \
--to=guix-devel_gnu.org@sumou.com \
--cc=guix-devel@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).