From: John Snow <1877418@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1877418] Re: qemu-nbd freezes access to VDI file
Date: Thu, 28 May 2020 22:17:21 -0000 [thread overview]
Message-ID: <159070424107.14155.13915357337529578312.malone@gac.canonical.com> (raw)
In-Reply-To: 158887096525.4808.16857448132122344597.malonedeb@soybean.canonical.com
I don't recommend you use VDI images in this way; we do not intend to
support performant RW access; support for VDI images is there to convert
to qcow2 or raw, generally.
That said, some questions that might be interesting to know the answer
to:
- Try converting your VDI image to raw or qcow2 and mounting that instead. Does the conversion work successfully? Can you export that image via qemu-nbd and mount it? Does it work?
- Do non-BTRFS filesystems cause any problems?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1877418
Title:
qemu-nbd freezes access to VDI file
Status in QEMU:
New
Status in btrfs-progs package in Ubuntu:
New
Bug description:
Mounted Oracle Virtualbox .vdi drive (dynamically allocated), which has GTP+BTRFS:
sudo modprobe nbd max_part=16
sudo qemu-nbd -c /dev/nbd0 /storage/btrfs.vdi
mount /dev/nbd0p1 /mydata/
Then I am operating on the btrfs filesystem and suddenly it freezes.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1877418/+subscriptions
next prev parent reply other threads:[~2020-05-28 22:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-07 17:02 [Bug 1877418] [NEW] qemu-nbd freezes access to VDI file Bump
2020-05-07 17:12 ` [Bug 1877418] " Bump
2020-05-07 17:18 ` Bump
2020-05-28 22:17 ` John Snow [this message]
2020-05-28 23:15 ` Bump
2020-05-29 18:49 ` John Snow
2020-05-29 23:45 ` Bump
2020-06-01 17:33 ` John Snow
2020-11-05 12:33 ` Thomas Huth
2021-01-05 4:17 ` Launchpad Bug Tracker
2021-01-05 4:17 ` Launchpad Bug Tracker
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=159070424107.14155.13915357337529578312.malone@gac.canonical.com \
--to=1877418@bugs.launchpad.net \
--cc=qemu-devel@nongnu.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.