Let me try this again from Thunderbird:
Here is a patch that merges the externals for IDE and SCSI with a --disk
as Paul requested. Let me know if you want different keywords.
Chuck
diff -Nuar -X diff_excludes /hg-qemu/hw/pc.c /qemu-new/hw/pc.c
--- /hg-qemu/hw/pc.c2006-10-09
Chuck,
IMHO, in order to be able to use such patches as yours (big patches),
I think it would be the best to attached them as compressed files
(gzip, bz2).
That way, almost any mailer knows how to handle attachment without
scrambling the patch formatting
Thanks,
Hetz
On 12/12/06, Chuck Brazie
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.
Unfortunatelly, only read access
I have no ideas why path.c is so complex. Any? In the attachment
rewritten version. It has tested with qemu-arm.
With old version I had the problem. It hangs due loop of symlinks. :(
path.c.patch
Description: Binary data
___
Qemu-devel mailing list
Hi,
Just saw this on slashdot
(http://linux.slashdot.org/article.pl?sid=06/12/12/0135240). From the
news:
In a fashion comparable to that of Xen a modified QEMU is used for
the supportive emulation of typical PC components of the virtual
machines
So, when it will run with a non-modified QEMU?
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,
with the unmodified
Ricardo Almeida wrote:
Hi,
Just saw this on slashdot
(http://linux.slashdot.org/article.pl?sid=06/12/12/0135240). From the
news:
In a fashion comparable to that of Xen a modified QEMU is used for
the supportive emulation of typical PC components of the virtual
machines
So, when it will run
Hi,
My name is Dor and I'm one of the contributors for the KVM.
Ricardo Almeida wrote:
Hi,
Just saw this on slashdot
(http://linux.slashdot.org/article.pl?sid=06/12/12/0135240). From
the
news:
In a fashion comparable to that of Xen a modified QEMU is used for
the supportive
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.
Hetz Ben Hamo wrote:
Chuck,
IMHO, in order to be able to use such patches as yours (big patches),
I think it would be the best to attached them as compressed files
(gzip, bz2).
Ugh. It's a text plain attachment. No mailers will scramble that. A
lot of mailing lists will drop any non
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
and for
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
images locally,
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 images.
Would be
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 this.
I've
--- Anthony Liguori [EMAIL PROTECTED] a écrit :
Hetz Ben Hamo wrote:
Chuck,
IMHO, in order to be able to use such patches as yours (big patches),
I think it would be the best to attached them as compressed files
(gzip, bz2).
Ugh. It's a text plain attachment. No mailers will
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 everybody missing the
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.
How is everybody
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 images.
Using
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
Daniel Jacobowitz wrote:
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.
How is
Hello All,
the appended patch fixes the case where a ELF Linux binary has a
zero-sized .bss, or none at all.
Thiemo
Index: qemu-work/linux-user/elfload.c
===
--- qemu-work.orig/linux-user/elfload.c 2006-12-12 18:25:00.0
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 everybody missing the point? :-) mount -o loop doesn't mount
qcow
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
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
Hello All,
the appended patch check the machine type and the endianness of the
ELF binaries involved. For MIPS it removes the raw binary backward
compatibility mode, recent kernels won't work with as raw binaries.
I'm not sure if machine check is good enough. If it has to check
for more than one
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
On Tue, Dec 12, 2006 at 07:02:33AM -0500, Chuck Brazie wrote:
Here is a patch that merges the externals for IDE and SCSI with a --disk
as Paul requested. Let me know if you want different keywords.
I was able to apply the patch (almost) cleanly to a November snapshot.
The following
On Tue, 2006-12-12 at 15:42 -0800, Russell Jackson wrote:
On Tue, Dec 12, 2006 at 07:02:33AM -0500, Chuck Brazie wrote:
Here is a patch that merges the externals for IDE and SCSI with a --disk
as Paul requested. Let me know if you want different keywords.
I was able to apply the patch
On Tue, Dec 12, 2006 at 03:57:36PM -0800, Daniel Stekloff wrote:
I was able to apply the patch (almost) cleanly to a November snapshot.
The following invocation results in the LSI controller showing up in
Windows XP, but the disk(s) do not. Am I missing something?
qemu -kernel-kqemu
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 result in
30 matches
Mail list logo
