Salvador Fandino wrote:
I have run some tests and found that it's easy to cause a deadlock just
untaring a file over an nbd device being served from localhost (using
the standard nbd-server or my own, it doesn't matter).
Another interesting finding is that when the deadlock happens, qemu-nbds
is
Avi Kivity wrote:
> Martin Guy wrote:
>>> - write tons of data to nbd device, data ends up in pagecache
>>> - memory gets low, kswapd wakes up, calls nbd device to actually write
>>> the data
>>> - nbd issues a request, which ends up on the nbd server on the same
>>> machine
>>> - the nbd server al
Martin Guy wrote:
- write tons of data to nbd device, data ends up in pagecache
- memory gets low, kswapd wakes up, calls nbd device to actually write
the data
- nbd issues a request, which ends up on the nbd server on the same
machine
- the nbd server allocates memory
- memory allocation hangs
- write tons of data to nbd device, data ends up in pagecache
- memory gets low, kswapd wakes up, calls nbd device to actually write
the data
- nbd issues a request, which ends up on the nbd server on the same machine
- the nbd server allocates memory
- memory allocation hangs waiting for kswapd
Anthony Liguori wrote:
Mounting a partition being served on the same host as read-write can
cause deadlocks. From nbd-2.9.0 README file:
This text is pretty old. Is this still valid? This would imply that
things like loop can result in dead locks. I don't see why flushing
one device would
> >> And write access works for me. What's this limitation you speak of?
> >
> > Mounting a partition being served on the same host as read-write can
> > cause deadlocks. From nbd-2.9.0 README file:
>
> This text is pretty old. Is this still valid? This would imply that
> things like loop can re
Salvador Fandino wrote:
Anthony Liguori wrote:
Salvador Fandiño wrote:
Hi,
The patch available from http://qemu-forum.ipi.fi/viewtopic.php?t=2718
adds a new utility, qemu-nbds, that implements a NBD server (see
http://nbd.sf.net) for QEMU images.
Using this utility it is posible to mount imag
On 12/12/06, Daniel Jacobowitz <[EMAIL PROTECTED]> wrote:
How is everybody missing the point? :-) mount -o loop doesn't mount
qcow images.
you could also mount it through a samba tunnel
--
Christian
___
Qemu-devel mailing list
Qemu-devel@nongnu.o
Paul Brook wrote:
mount -o loop does this.
How is everybody missing the point? :-) mount -o loop doesn't mount
qcow images.
Would be that difficult to write a qcow fs module ?
qcow is an image format, not a filesystem.
I'd guess it should be possible to use the device-mapper framework to do
> > > > > It's mostly intended to be used for accessing the files inside
> > > > > QEMU disk images locally, without having to launch a virtual
> > > > > machine and accessing then from there.
> > > >
> > > > mount -o loop does this.
> > >
> > > How is everybody missing the point? :-) mount -o
> > > It's mostly intended to be used for accessing the files inside QEMU
> > > disk images locally, without having to launch a virtual machine and
> > > accessing then from there.
> >
> > mount -o loop does this.
>
> How is everybody missing the point? :-) mount -o loop doesn't mount
> qcow image
On Tue, Dec 12, 2006 at 06:33:22PM +0100, Sylvain Petreolle wrote:
> > > > It's mostly intended to be used for accessing the files inside QEMU disk
> > > > images locally, without having to launch a virtual machine and accessing
> > > > then from there.
> > >
> > > mount -o loop does this.
> >
>
Hi,
On Tue, 12 Dec 2006, Sylvain Petreolle wrote:
> > > > It's mostly intended to be used for accessing the files inside QEMU disk
> > > > images locally, without having to launch a virtual machine and accessing
> > > > then from there.
> > >
> > > mount -o loop does this.
> >
> > How is everyb
> > > mount -o loop does this.
> >
> > How is everybody missing the point? :-) mount -o loop doesn't mount
> > qcow images.
>
> Would be that difficult to write a qcow fs module ?
qcow is an image format, not a filesystem.
I'd guess it should be possible to use the device-mapper framework to do t
> > > It's mostly intended to be used for accessing the files inside QEMU disk
> > > images locally, without having to launch a virtual machine and accessing
> > > then from there.
> >
> > mount -o loop does this.
>
> How is everybody missing the point? :-) mount -o loop doesn't mount
> qcow ima
Anthony Liguori wrote:
> Salvador Fandiño wrote:
>> Hi,
>>
>> The patch available from http://qemu-forum.ipi.fi/viewtopic.php?t=2718
>> adds a new utility, qemu-nbds, that implements a NBD server (see
>> http://nbd.sf.net) for QEMU images.
>>
>> Using this utility it is posible to mount images in a
On Tue, Dec 12, 2006 at 04:58:32PM +, Paul Brook wrote:
> On Tuesday 12 December 2006 17:00, Salvador Fandino wrote:
> > It serves disk images in any format QEMU can handle, for instance, qcow
> > images.
> >
> > It's mostly intended to be used for accessing the files inside QEMU disk
> > image
On Tuesday 12 December 2006 17:00, Salvador Fandino wrote:
> Martin Guy wrote:
> >> The patch available from http://qemu-forum.ipi.fi/viewtopic.php?t=2718
> >> adds a new utility, qemu-nbds, that implements a NBD server
> >
> > I have been using nbd volumes mounted from inside qemu for filestore
>
Martin Guy wrote:
>> The patch available from http://qemu-forum.ipi.fi/viewtopic.php?t=2718
>> adds a new utility, qemu-nbds, that implements a NBD server
>
> I have been using nbd volumes mounted from inside qemu for filestore
> and for swap, both read-write, served from files and from partitions
Salvador Fandiño wrote:
Hi,
The patch available from http://qemu-forum.ipi.fi/viewtopic.php?t=2718 adds a
new utility, qemu-nbds, that implements a NBD server (see http://nbd.sf.net)
for QEMU images.
Using this utility it is posible to mount images in any format supported by
QEMU.
Unfortuna
20 matches
Mail list logo
