I don't see any --format..option
[root@localhost ~]# qemu-nbd --help
Usage: qemu-nbd [OPTIONS] FILE
QEMU Disk Network Block Device Server
-p, --port=PORT port to listen on (default `10809')
-o, --offset=OFFSET offset into the image
-b, --bind=IFACE interface to bind to (default
On 2018-12-04 15:46, ZEESHAN HAYAT wrote:
> Hi,
> I am trying to access target/nios2/cpu.h in vl.c. If I add #include
> "target/nios2/cpu.h" in vl.c, I get the following errors:
You can not include a target-specific header file in common code. vl.c
is only compiled once for all targets, but targe
disconnect and reconnect with *-f raw* option...
qemu-nbd --connect /dev/nbd0* --format=raw* /home/test/test.3.5.1b.debug/
test.3.5.1b.debug.raw
Le mar. 4 déc. 2018 à 14:32, ramakanth varala
a écrit :
> [root@localhost ~]# file
> /home/test/test.3.5.1b.debug/test.3.5.1b.debug.raw
> /home/test/
hope this will help you to debug your problem...
# qemu-img create /tmp/test.raw 512M
Formatting '/tmp/test.raw', fmt=raw size=536870912
# qemu-img create -f qcow2 /tmp/test.qcow 512M
Formatting '/tmp/test.qcow', fmt=qcow2 size=536870912 cluster_size=65536
lazy_refcounts=off refcount_bits=16
# ll
there is an underlying problem : try to disconnect and then re-connect the
exported (network) device (eg. the over side)...
http://www.microhowto.info/howto/connect_to_a_remote_block_device_using_nbd.html
Le mar. 4 déc. 2018 à 12:25, ramakanth varala
a écrit :
> first time i got below..
>
> [ro
Hi Pascal..
I tried like below..
[root@localhost ~]# qemu-nbd -d /dev/nbd0
/dev/nbd0 disconnected
[root@localhost ~]# qemu-nbd --connect /dev/nbd0p1
/home/test/test.3.5.1b.debug/test.3.5.1b.debug.raw
qemu-nbd: Could not access '/dev/nbd0p1': No such file or directory
On Tue, Dec 4, 2018 at 4:
first time i got below..
[root@localhost ~]# kpartx -a /dev/ndb0
failed to stat() /dev/ndb0
from second time onwards like below..
[root@localhost ~]# kpartx -a /dev/nbd0
device-mapper: resume ioctl failed: Invalid argument
On Tue, Dec 4, 2018 at 4:23 PM Jan Schermer wrote:
> Partigion is mis
try to disconnect and then re-connect the exported (network) device (eg.
the over side)...
Le mar. 4 déc. 2018 à 11:53, Jan Schermer a écrit :
> Partigion is missing :-)
> try:
> kpartx -a /dev/ndb0
>
>
> > On 4 Dec 2018, at 11:35, ramakanth varala
> wrote:
> >
> > Hi Pascal..
> >
> > yes its R
Partigion is missing :-)
try:
kpartx -a /dev/ndb0
> On 4 Dec 2018, at 11:35, ramakanth varala wrote:
>
> Hi Pascal..
>
> yes its RW ...
>
> [root@localhost ~]# fdisk -l /dev/nbd0
>
> Disk /dev/nbd0: 21.4 GB, 21474836480 bytes
> 255 heads, 63 sectors/track, 2610 cylinders
> Units = cylinders
Hi Pascal..
yes its RW ...
[root@localhost ~]# fdisk -l /dev/nbd0
Disk /dev/nbd0: 21.4 GB, 21474836480 bytes
255 heads, 63 sectors/track, 2610 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/nbd0p1 1
hi,
you left fdisk without saving the changes (w before q), so there can't be
two partitions.
on the other hand, we should find the existing partition...
there is a strange warning when fdisk starts: what is on the over side of
nbd0 ?
is /dev/nbd0 rw ?
if you can't re-read the partitions table, ca
11 matches
Mail list logo
