similar to: [nbdkit] Serving "temporary disks" over NBD

Displaying 20 results from an estimated 10000 matches similar to: "[nbdkit] Serving "temporary disks" over NBD"

2015 Nov 07
0
Re: mkfs.ext2 succeeds despite nbd write errors?
On Sat, Nov 07, 2015 at 12:21:29AM -0600, Jason Pepas wrote: > Hi, > > So I've been hacking together an nbdkit plugin (similar to the "file" > plugin, but it splits the file up into chunks): > https://github.com/pepaslabs/nbdkit-chunks-plugin > > I got it to the point of being a working prototype. Then I threw it > onto a raspberry pi, which it turns out
2015 Nov 07
2
mkfs.ext2 succeeds despite nbd write errors?
Hi, So I've been hacking together an nbdkit plugin (similar to the "file" plugin, but it splits the file up into chunks): https://github.com/pepaslabs/nbdkit-chunks-plugin I got it to the point of being a working prototype. Then I threw it onto a raspberry pi, which it turns out only has a 50/50 shot of fallocate() working correctly. I'm checking the return code of
2017 Apr 23
0
Proper way to remove a qemu-nbd-mounted volume usnig lvm
I either haven't searched for the right thing or the web doesn't contain the answer. I have used the following to mount an image and now I need to know the proper way to reverse the process. qemu-nbd -c /dev/nbd0 <qcow2 image using lvm> vgscan --cache (had to use --cache to get the qemu-nbd volume to be recognized, lvmetad is running) vgchange -ay
2019 Jun 27
2
mkfs fails on qemu-nbd device
Hi All, I am unable to figure out the issue here, when I try to create a filesystem (ext4) on a virtual disk using qemu-nbd. This happens intermittently. Following is the sequence of commands:- $> qemu-img create -f qcow2 test.qcow2 30G $> qemu-nbd --connect=/dev/nbd0 test.qcow2 $> *mkfs.ext4 /dev/nbd0* * mkfs.ext4: Device size reported to be zero. Invalid partition specified, or*
2018 Oct 13
0
Re: Provide NBD via Browser over Websockets
[adding nbdkit readers] On 10/13/18 1:39 PM, Eric Wheeler wrote: > Hello all, > > It might be neat to attach ISOs to KVM guests via websockets. Basically > the browser would be the NBD "server" and an NBD client would run on the > hypervisor, then use `virsh change-media vm1 hdc --insert /dev/nbd0` could > use an ISO from my desk to boot from. Are you using qemu as
2017 Jul 28
1
Re: performance between guestfish and qemu-nbd
2017-07-28 0:31 GMT+08:00 Richard W.M. Jones <rjones@redhat.com>: > On Fri, Jul 28, 2017 at 12:23:04AM +0800, lampahome wrote: > > 2017-07-27 20:18 GMT+08:00 Richard W.M. Jones <rjones@redhat.com>: > > > > > On Thu, Jul 27, 2017 at 06:34:13PM +0800, lampahome wrote: > > > > I can mount qcow2 img to nbd devices through guestfish or qemu-nbd > >
2017 Jul 27
0
Re: performance between guestfish and qemu-nbd
On Fri, Jul 28, 2017 at 12:23:04AM +0800, lampahome wrote: > 2017-07-27 20:18 GMT+08:00 Richard W.M. Jones <rjones@redhat.com>: > > > On Thu, Jul 27, 2017 at 06:34:13PM +0800, lampahome wrote: > > > I can mount qcow2 img to nbd devices through guestfish or qemu-nbd > > > > > > I'm curious about which performance is better? > > > > They
2020 May 28
0
Re: Provide NBD via Browser over Websockets
On Thu, May 28, 2020 at 12:24:22AM +0000, Eric Wheeler wrote: > On Mon, 15 Oct 2018, Nir Soffer wrote: > > On Sat, Oct 13, 2018 at 9:45 PM Eric Wheeler <nbd@lists.ewheeler.net> wrote: > > Hello all, > > > > It might be neat to attach ISOs to KVM guests via websockets.  Basically > > the  browser would be the NBD "server" and an
2013 Apr 04
2
launch failure of appliance with nbd drive
I'm using qemu-nbd to setup the device with an offset into the image. Using libguestfs version 1.21.22 Code for adding the drive: char *server[] = { "localhost:3000", NULL }; if (guestfs_add_drive_opts (g, "" /* export name - see below */, GUESTFS_ADD_DRIVE_OPTS_FORMAT, "raw", GUESTFS_ADD_DRIVE_OPTS_PROTOCOL, "nbd",
2017 Jul 27
2
Re: performance between guestfish and qemu-nbd
2017-07-27 20:18 GMT+08:00 Richard W.M. Jones <rjones@redhat.com>: > On Thu, Jul 27, 2017 at 06:34:13PM +0800, lampahome wrote: > > I can mount qcow2 img to nbd devices through guestfish or qemu-nbd > > > > I'm curious about which performance is better? > > They do quite different things, they're not comparable. > > Can you specifically give the
2007 Nov 13
2
lvm over nbd?
I have a system with a large LVM VG partition. I was wondering if there is a way i could share the partition using nbd and have the nbd-client have access the LVM as if it was local. SYSTEM A: /dev/sda3 is a LVM partition and is assigned to VG volgroup1. I want to share /dev/sda3 via nbd-server SYSTEM B: receives A''s /dev/sda3 as /dev/nbd0. I want to access it as VG volgroup1. I am
2020 May 28
2
Re: Provide NBD via Browser over Websockets
On Mon, 15 Oct 2018, Nir Soffer wrote: > On Sat, Oct 13, 2018 at 9:45 PM Eric Wheeler <nbd@lists.ewheeler.net> wrote: > Hello all, > > It might be neat to attach ISOs to KVM guests via websockets.  Basically > the  browser would be the NBD "server" and an NBD client would run on the > hypervisor, then use `virsh change-media vm1 hdc
2020 May 28
3
Re: Provide NBD via Browser over Websockets
On Thu, 28 May 2020, Richard W.M. Jones wrote: > On Thu, May 28, 2020 at 12:24:22AM +0000, Eric Wheeler wrote: > > On Mon, 15 Oct 2018, Nir Soffer wrote: > > > On Sat, Oct 13, 2018 at 9:45 PM Eric Wheeler <nbd@lists.ewheeler.net> wrote: > > > Hello all, > > > > > > It might be neat to attach ISOs to KVM guests via websockets. 
2020 May 29
0
Re: Provide NBD via Browser over Websockets
On Fri, May 29, 2020 at 07:50:14AM -0500, Eric Blake wrote: > [adding qemu list] > > On 5/29/20 4:37 AM, Richard W.M. Jones wrote: > > Going back to the original email from 2018: > > > > > It might be neat to attach ISOs to KVM guests via websockets.  Basically > > > the  browser would be the NBD "server" and an NBD client would run on the
2020 May 29
0
Re: Provide NBD via Browser over Websockets
Going back to the original email from 2018: > It might be neat to attach ISOs to KVM guests via websockets.  Basically > the  browser would be the NBD "server" and an NBD client would run on the > hypervisor, then use `virsh change-media vm1 hdc --insert /dev/nbd0` could > use an ISO from my desk to boot from. > > Here's an HTML5 open file example: >
2014 Apr 23
1
Fwd: [s3-bug-review] [RHEL7] [Virtual disks] Met error messages while the guest OS booting up on a nbd device.
Hi, all We met an issue while doing the nbd related test, will you please help to review if this issue is a bug? Thank you! ================================================= Subject: [s3-bug-review] [RHEL7] [Virtual disks] Met error messages while the guest OS booting up on a nbd device. Description: Start a guest with only one nbd device and with a linux OS installed on the nbd device,
2017 Nov 21
1
[nbdkit PATCH] maint: Mention upstream NBD in README
It's worth having a link to the upstream NBD protocol as part of README. Fix a typo while at it. Signed-off-by: Eric Blake <eblake@redhat.com> --- README | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/README b/README index 7b5de90..7806cf5 100644 --- a/README +++ b/README @@ -11,7 +11,7 @@ The key features are: libraries or included in proprietary code. *
2020 May 29
2
Re: Provide NBD via Browser over Websockets
[adding qemu list] On 5/29/20 4:37 AM, Richard W.M. Jones wrote: > Going back to the original email from 2018: > >> It might be neat to attach ISOs to KVM guests via websockets.  Basically >> the  browser would be the NBD "server" and an NBD client would run on the >> hypervisor, then use `virsh change-media vm1 hdc --insert /dev/nbd0` could >> use
2019 Jun 27
0
Re: mkfs fails on qemu-nbd device
On Thu, Jun 27, 2019 at 16:22:27 +0530, Tanmoy Sinha wrote: > Hi All, > > I am unable to figure out the issue here, when I try to create a filesystem > (ext4) on a virtual disk using qemu-nbd. This happens intermittently. > > Following is the sequence of commands:- > > $> qemu-img create -f qcow2 test.qcow2 30G > > > $> qemu-nbd --connect=/dev/nbd0
2020 Jan 22
3
[PATCH libnbd] PROPOSAL Add nbdcp (NBD copying) tool.
This is a proposal for an NBD to/from file copying tool (not actually written). Obviously this would duplicate functionality which is already available in qemu-img convert. The reasons for writing this tool would be: - to produce a tool which is very focused on the specific needs of virt-v2v and similar migration scenarios - to have a small tool with minimal dependencies - fix some of