On Tue, Dec 21, 2010 at 04:00:32PM +, Richard W.M. Jones wrote:
> Markus, any idea when we might get the -accel option appearing in
> released versions of qemu/KVM?
Sorry, I thought this email wasn't going out to a public list. I
should be more careful next time.
I'll say in
On Thu, Jan 13, 2011 at 08:27:17AM -0800, Boris Derzhavets wrote:
> Windows 7 KVM install runs unbelievably fast on SL 6 ( alpha 3) vs F14 with
> the
> most recent libvirt stuff :
Boris can you help me to parse this ...
SL6 = Scientific Linux 6?
And you're saying that Windows 7 is much faster o
On Fri, Jan 14, 2011 at 12:39:39PM -0800, Boris Derzhavets wrote:
> > Newer virt-manager versions also allow setting this in the UI.
>
> I just set IDE Disk1 "cashe mode" none before install.
I thought you said they were using virtio?
Rich.
--
Richard Jones, Virtualization Group, Red Hat http
You shouldn't use local files (esp. not qcow2) for performance
testing.
What does it look like if you use an LV for disk?
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-p2v converts physical machines to virtual machines. Boot with a
live CD or over
On Fri, Jan 14, 2011 at 12:17:42PM -0800, Boris Derzhavets wrote:
>
>
This one (SL6) has cache=none, but the Fedora 14 XML you posted
does not.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
libguestfs lets you edit virtual machines. Supports
On Sat, Jan 15, 2011 at 03:15:05AM -0800, Boris Derzhavets wrote:
> Please,
> view thread.
I've read every part of the thread(s). You don't make it easy
to follow what you're talking about.
I would suggest:
(1) Organize your thoughts and experiments logically.
(2) When you have done (1), post
On Fri, Jan 21, 2011 at 12:23:40PM -0600, Michael Roth wrote:
> getfile() is confusingly named however, it's really just a means to
> peek at a text file like /proc/meminfo.
You might as well reuse the libguestfs API here because you get the
benefit of all the code that's been written, all the too
On Mon, Jan 24, 2011 at 10:08:09PM +, Richard W.M. Jones wrote:
> You might as well reuse the libguestfs API here because you get the
> benefit of all the code that's been written, all the tools on top, and
> a far more comprehensive API that would take you another 2 years to
&g
On Mon, Jan 24, 2011 at 04:26:09PM -0600, Anthony Liguori wrote:
> On 01/24/2011 04:20 PM, Richard W.M. Jones wrote:
> >On Mon, Jan 24, 2011 at 10:08:09PM +, Richard W.M. Jones wrote:
> >>You might as well reuse the libguestfs API here because you get the
> >>ben
On Mon, Jan 24, 2011 at 05:40:05PM -0600, Anthony Liguori wrote:
> BTW, how dependent is guestfsd on the guest that libguestfs uses? I
> wasn't even aware that it could be used outside of that context.
The daemon is compiled separately -- separate ./configure, make, etc.
You can run it on its own
de229af89c518 Mon Sep 17 00:00:00 2001
From: Richard W.M. Jones
Date: Fri, 24 Sep 2010 16:08:06 +0100
Subject: [PATCH] Watchdog: disable watchdog timer when hard-rebooting a guest.
This commit causes the watchdog timer to be reset when a guest is
hard-rebooted.
The failure case previously w
es the timer. Note the handler is called _either_
just after init _or_ when the guest reboots.
In the i6300esb case there is a small refactoring of the code so
that the device's internal state is now fully restored to defaults
on a reboot.
Signed-off-by: Richard W.M. Jones
--
Richard Jone
On Tue, Oct 12, 2010 at 03:00:13PM +0200, Markus Armbruster wrote:
> Markus Armbruster writes:
>
> > When I try -device isa-applesmc -device isa-applesmc, I get
> >
> > WARNING: Using AppleSMC with invalid key
> > qemu: hardware error: register_ioport_read: invalid opaque
> > [...]
>
On Thu, Oct 14, 2010 at 01:10:47PM +0100, Daniel P. Berrange wrote:
> Or a PCI bridge to wire up more PCI buses, so we raise the max limit for
> any type of device we emulate.
Break the 29/30/31 virtio-blk limit ... please!
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.re
On Thu, Oct 14, 2010 at 04:57:36PM -0500, Anthony Liguori wrote:
> On 10/14/2010 04:42 PM, Richard W.M. Jones wrote:
> >On Thu, Oct 14, 2010 at 01:10:47PM +0100, Daniel P. Berrange wrote:
> >>Or a PCI bridge to wire up more PCI buses, so we raise the max limit for
> >>an
On Tue, Oct 19, 2010 at 03:59:36PM +0200, Jan Kiszka wrote:
> Once we have "-trace events=...", defining the list of active
> tracepoints before starting qemu will be trivial (e.g. via a config
> file). Of course, this requires that all tracepoints are built-in...
Sorry that I've not been followin
On Thu, Oct 21, 2010 at 07:20:27AM +0200, Christoph Hellwig wrote:
> On Tue, Oct 19, 2010 at 03:29:51PM +0100, Richard W.M. Jones wrote:
> > On Tue, Oct 19, 2010 at 03:59:36PM +0200, Jan Kiszka wrote:
> > > Once we have "-trace events=...", defining the list of act
On Fri, Mar 04, 2011 at 12:45:54PM -0600, Justin M. Forbes wrote:
> F15:
> - qemu-0.14.0-2.fc15
> Updated to 0.14.0 final release and re-enabled cris and sparc emulation
A change in the command-line parsing code in qemu-img causes
virt-make-fs to break (because of a latent bug in virt-make
On Fri, Mar 04, 2011 at 10:27:57PM -0800, Don Raikes wrote:
> Hello,
>
> I am new to qemu, but have a specific application in mind.
>
> I want to use a qemu emulated knopix system on a usb key to do diagnostics on
> a running windows system.
>
> Is there a way for me to access things like the h
On Tue, Jan 25, 2011 at 09:12:15AM -0600, Anthony Liguori wrote:
> How much infrastructure does guestfd depend on within the guest? Do
> you need a full install with all of the bells and whistles or does
> it degrade cleanly when certain tools aren't available?
On Linux these are the libraries, b
I posted my thoughts about how this could work here:
https://www.redhat.com/archives/libguestfs/2011-January/msg00066.html
Rich.
PS. You don't need to be a subscriber to post to that list -- I
manually triage any messages sent by non-subscribers.
--
Richard Jones, Virtualization Group, Red Ha
On Tue, Feb 01, 2011 at 02:25:12PM +0300, Vasiliy G Tolstov wrote:
> On Tue, 2011-02-01 at 11:58 +0100, jes.soren...@redhat.com wrote:
> > From: Jes Sorensen
> >
> > Hi
> >
> > This is a first attempt to add fsfreeze support to virtagent. The idea
> > is for the guest agent to walk the list of l
On Tue, Feb 01, 2011 at 11:04:47PM +0300, Vasiliy G Tolstov wrote:
> On Tue, 2011-02-01 at 16:04 +0000, Richard W.M. Jones wrote:
>
> > There are some experimental patches to libguestfs to do live
> > filesystem and partition manipulations now:
> >
> > h
On Sat, Feb 05, 2011 at 04:36:11PM +, Stefan Hajnoczi wrote:
> Occassionally a commit that breaks the build gets merged into
> qemu.git/master. Build testing manually across all host platforms is
> not feasible for most developers. Remember we cover 32- and 64-bit
> x86 Linux, Windows, and o
I'm trying to speed up the process of loading kernel and initrd.
I found that the main loop which loads these into qemu memory does it
via executing in the guest:
rep insb (%dx),%es:(%edi)
In other words, reading it byte-at-a-time from an emulated IO port.
This is very slow[1] when your initrd
On Sat, Jul 17, 2010 at 10:50:59AM +0100, Richard W.M. Jones wrote:
> I understand from the git logs that fw_cfg was added because the old
> way was to load kernel & initrd into RAM directly, but this didn't
> work because SeaBIOS would clear the RAM, clobbering kernel & ini
These two patches implement a faster way to copy the kernel and initrd
data into the guest. The guest can set up a blit address and then
issue a blit command in order to tell qemu to copy the whole of the
configuration data into the predefined area of memory.
This saves a couple of seconds of bo
qemu to segfault.
Luckily since nothing in qemu uses writable entries at the moment,
this is not exploitable.
Signed-off-by: Richard W.M. Jones
---
hw/fw_cfg.c |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/hw/fw_cfg.c b/hw/fw_cfg.c
index 72866ae..37e6f1f 100644
--- a/hw/
and overall boot time is reduced correspondingly.
Signed-off-by: Richard W.M. Jones
---
hw/fw_cfg.c | 19 ++-
hw/fw_cfg.h |7 +--
pc-bios/optionrom/linuxboot.S |8
pc-bios/optionrom/optionrom.h | 37 +
On Sun, Jul 18, 2010 at 07:26:57PM +0200, Alexander Graf wrote:
> On 17.07.2010, at 11:53, Richard W.M. Jones wrote:
> > On Sat, Jul 17, 2010 at 10:50:59AM +0100, Richard W.M. Jones wrote:
> >> I understand from the git logs that fw_cfg was added because the old
> >
On Sun, Jul 18, 2010 at 10:47:27PM +0200, Alexander Graf wrote:
> > +if (blitaddr == 0)
> > +ret = 0; /* guest must set up a blit address beforehand */
>
> Coding style. I'm also not sure this has to be special-cased. Why care if the
> guest wants to corrupt its own address sp
On Mon, Jul 19, 2010 at 01:59:22AM +0200, Aurelien Jarno wrote:
> OpenBIOS also uses the same firmware interface, so it would need to be
> changed if this patch is accepted.
The patch leaves the old interface. Does it still need to be changed?
Rich.
--
Richard Jones, Virtualization Group, Red
On Mon, Jul 19, 2010 at 09:23:56AM +0300, Gleb Natapov wrote:
> That what I am warring about too. If we are adding device we have to be
> sure such device can actually exist on real hw too otherwise we may have
> problems later.
I don't understand why the constraints of real h/w have anything to d
On Mon, Jul 19, 2010 at 10:33:12AM +0300, Gleb Natapov wrote:
> On Mon, Jul 19, 2010 at 08:28:02AM +0100, Richard W.M. Jones wrote:
> > On Mon, Jul 19, 2010 at 09:23:56AM +0300, Gleb Natapov wrote:
> > > That what I am warring about too. If we are adding device we have to be
>
On Mon, Jul 19, 2010 at 10:55:33AM +0300, Gleb Natapov wrote:
> Why not put then on cdrom or disk?
It simplifies device and mountpoint enumeration not to have a separate
disk. It would also mean we couldn't use standard Fedora paths, or
we'd have to have bind-mount /bin etc on to the disk mount p
On Mon, Jul 19, 2010 at 11:40:41AM +0300, Gleb Natapov wrote:
> On Mon, Jul 19, 2010 at 09:34:11AM +0100, Richard W.M. Jones wrote:
> > On Mon, Jul 19, 2010 at 10:55:33AM +0300, Gleb Natapov wrote:
> > > Why not put then on cdrom or disk?
> >
> > It simplifies dev
On Mon, Jul 19, 2010 at 10:00:04AM +0100, Richard W.M. Jones wrote:
[...]
OK, it's early in the morning and I can't do maths. But we're still
asking a big increase in complexity versus optimizing something which
is just slow in qemu at the moment.
Rich.
--
Richard Jones, Virtu
On Mon, Jul 19, 2010 at 09:40:18AM +0200, Alexander Graf wrote:
> Richard, what does kvm_stat tell you while loading the initrd? Are
> there a lot of PIO requests or are we simply looping inside qemu
> code?
The two attached files were made by running kvm_stat -l > /tmp/...
during a single run sta
On Mon, Jul 19, 2010 at 12:19:22PM +0300, Gleb Natapov wrote:
> Vcpu executes "in %ax". Next instruction is executed 6 seconds later.
> All timers that should have been processed during this time fire at the
> same moment triggering all kind of timeouts. Think about watchdog that
> should be writte
This is the second version of the patch.
We don't use the word "blit" any more, instead this is replaced with
"DMA", even though it's not quite like a DMA operation on physical
hardware.
The guest writes the physical address and size to two 32 bit fw_cfg
variables. Then when the guest issues an
k is still called, causing qemu to segfault.
Luckily since nothing in qemu uses writable entries at the moment,
this is not exploitable.
Signed-off-by: Richard W.M. Jones
---
hw/fw_cfg.c |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/hw/fw_cfg.c b/hw/fw_cfg.c
index
wards compatible. ROMs using the old method will
work unchanged.
Signed-off-by: Richard W.M. Jones
---
hw/fw_cfg.c | 22 +-
hw/fw_cfg.h |8 ++--
pc-bios/optionrom/linuxboot.S |8
pc-bios/optio
On Mon, Jul 19, 2010 at 01:45:00PM +0300, Gleb Natapov wrote:
> On Mon, Jul 19, 2010 at 11:15:04AM +0100, Richard W.M. Jones wrote:
> >
> > This is the second version of the patch.
> >
> > We don't use the word "blit" any more, instead this is replaced
e when loading large images.
This change is backwards compatible. ROMs using the old method will
work unchanged.
Signed-off-by: Richard W.M. Jones
---
hw/fw_cfg.c | 35 +-
hw/fw_cfg.h | 10 +++-
pc-bios/optionrom/lin
On Mon, Jul 19, 2010 at 12:15:43PM +0300, Gleb Natapov wrote:
> That what we are talking about, no? We are trying to find faster way to
> load kernel/initrd and stay architectural. Honestly I would expect much
> greater speedup from Richard's approach like 2 seconds vs 8 seconds. It
> is hard to ju
On Mon, Jul 19, 2010 at 07:11:37PM +0300, Gleb Natapov wrote:
> And there are such that cause cpu to stall for 6.5 seconds when you do
> io to them? I never said that we should implement ISA or PCI device, I
> don't know why you bring them here.
Where is "6.5 seconds" coming from? That is the *to
On Tue, Jul 20, 2010 at 04:40:28PM +0300, Gleb Natapov wrote:
> Which remind me that ad-hoc DMA interface should be discoverable by a
> guest.
Judging by 'git annotate' this interface has already been extended 4
times without requiring this to be discoverable. However I will add
an extra config b
EATURES bitmask
to find out if a version of qemu has this feature.
Signed-off-by: Richard W.M. Jones
---
hw/fw_cfg.c | 37 ++-
hw/fw_cfg.h | 20 --
pc-bios/optionrom/linuxboot.S | 11
On Tue, Jul 27, 2010 at 10:26:10AM +0200, Markus Armbruster wrote:
> Anthony Liguori writes:
>
> > On 07/26/2010 02:19 PM, Avi Kivity wrote:
> [...]
> >> Regardless, outside of Windows users qemu will mostly be consumed
> >> via distribution branches, with different levels of backport
> >> happin
On Mon, Aug 02, 2010 at 12:47:53PM -0400, Kevin O'Connor wrote:
> On Mon, Aug 02, 2010 at 11:33:33AM -0500, Anthony Liguori wrote:
> > On 08/02/2010 11:11 AM, Kevin O'Connor wrote:
> > >Load the "bootsplash.jpg" file into fw_cfg if it is found in the roms
> > >directory.
> >
> > Sorry, I should ha
qemu compiled from today's git. Using the following command line:
$qemudir/x86_64-softmmu/qemu-system-x86_64 -L $qemudir/pc-bios \
-drive file=/dev/null,if=virtio \
-enable-kvm \
-nodefaults \
-nographic \
-serial stdio \
-m 500 \
-no-reboot \
-no-hpet \
-net
On Tue, Aug 03, 2010 at 02:33:02PM +0300, Gleb Natapov wrote:
> On Tue, Aug 03, 2010 at 12:13:06PM +0100, Richard W.M. Jones wrote:
> >
> > qemu compiled from today's git. Using the following command line:
> >
> > $qemudir/x86_64-softmmu/qemu-system-x86_64 -L $
On Tue, Aug 03, 2010 at 03:37:14PM +0300, Gleb Natapov wrote:
> On Tue, Aug 03, 2010 at 01:10:00PM +0100, Richard W.M. Jones wrote:
> > I can't see anything about this in the kernel changelog. Can you
> > point me to the commit or the key phrase to look for?
> >
>
On Tue, Aug 03, 2010 at 07:51:02AM -0500, Anthony Liguori wrote:
> If menu=off, it probably just shouldn't display. I assume
> libguestfs is passing menu=off...
We don't actually, but it is a tremendously good idea so I'll add it,
thanks :-)
Rich.
--
Richard Jones, Virtualization Group, Red Ha
Subject: [PATCH] Don't call fw_cfg e->callback if e->callback is NULL.
If you set up a fw_cfg writable entry without a callback, then
e->callback is still called, causing qemu to segfault.
Luckily since nothing in qemu uses writable entries at the moment,
this is not exploitable.
Sign
On Tue, Aug 03, 2010 at 01:54:12PM +0100, Richard W.M. Jones wrote:
> On Tue, Aug 03, 2010 at 07:51:02AM -0500, Anthony Liguori wrote:
> > If menu=off, it probably just shouldn't display. I assume
> > libguestfs is passing menu=off...
>
> We don't actually, but it
On Tue, Aug 03, 2010 at 04:19:39PM +0300, Avi Kivity wrote:
> On 08/03/2010 03:48 PM, Richard W.M. Jones wrote:
> >
> >Thanks for the explanation. I'll repost my "DMA"-like fw-cfg patch
> >once I've rebased it and done some more testing. This
On Tue, Aug 03, 2010 at 05:38:25PM +0300, Avi Kivity wrote:
> The time will only continue to grow as you add features and as the
> distro bloats naturally.
>
> Much better to create it once and only update it if some dependent
> file changes (basically the current on-the-fly code + save a list of
is done, allowing us to write an alternate asynchronous
version in future should that be necessary.
This change is backwards compatible. ROMs using the old method will
work unchanged.
The change is discoverable. ROMs may read the FW_CFG_FEATURES bitmask
to find out if a version of qemu has this fea
On Tue, Aug 03, 2010 at 07:10:18PM +0300, Avi Kivity wrote:
> -kernel and -initrd is a developer's interface intended to make life
> easier for users that use qemu to develop kernels. It was not
> intended as a high performance DMA engine. Neither was the firmware
> _configuration_ interface. Th
On Tue, Aug 03, 2010 at 11:39:43AM -0500, Anthony Liguori wrote:
> Let's be fair. I think we've all agreed to adjust the fw_cfg
> interface to implement DMA. The only requirement was that the DMA
> operation not be triggered from a single port I/O but rather based
> on a polling operation which b
On Tue, Aug 03, 2010 at 07:48:17PM +0300, Avi Kivity wrote:
> On 08/03/2010 07:44 PM, Avi Kivity wrote:
> >
> >It's not a good path to follow. Tomorrow we'll need to load 300MB
> >initrds and we'll have to rework this yet again. Meanwhile the
> >kernel and virtio support demand loading of any im
On Tue, Aug 03, 2010 at 07:44:49PM +0300, Avi Kivity wrote:
> On 08/03/2010 07:28 PM, Richard W.M. Jones wrote:
> >I have posted a small patch which makes this 650x faster without
> >appreciable complication.
>
> It doesn't appear to support live migration, or hiding
On Tue, Aug 03, 2010 at 08:58:10PM +0300, Avi Kivity wrote:
> Richard, can you test kvm.git
> master? it already contains one fix and we plan to add more.
Yup, I will ...
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming blog: http://rwm
On Tue, Aug 03, 2010 at 09:43:39PM +0300, Avi Kivity wrote:
> libguestfs does not depend on an x86 architectural feature.
> qemu-system-x86_64 emulates a PC, and PCs don't have -kernel. We
> should discourage people from depending on this interface for
> production use.
I really don't get this wh
On Tue, Aug 03, 2010 at 10:22:22PM +0300, Avi Kivity wrote:
> On 08/03/2010 10:13 PM, Richard W.M. Jones wrote:
> >On Tue, Aug 03, 2010 at 09:43:39PM +0300, Avi Kivity wrote:
> >>libguestfs does not depend on an x86 architectural feature.
> >>qemu-system-x86_64 emulat
On Tue, Aug 03, 2010 at 10:24:41PM +0300, Avi Kivity wrote:
> Why do we need to transfer roms? These are devices on the memory
> bus or pci bus, it just needs to be there at the right address.
> Boot splash should just be another rom as it would be on a real
> system.
Just like the initrd?
Rich.
On Wed, Aug 04, 2010 at 08:54:35AM +0300, Avi Kivity wrote:
> On 08/04/2010 01:06 AM, Richard W.M. Jones wrote:
> >On Tue, Aug 03, 2010 at 10:24:41PM +0300, Avi Kivity wrote:
> >>Why do we need to transfer roms? These are devices on the memory
> >>bus or pci bus, it ju
On Wed, Aug 04, 2010 at 12:52:23PM +0300, Avi Kivity wrote:
> On 08/04/2010 12:24 PM, Richard W.M. Jones wrote:
> >>>
> >>>Just like the initrd?
> >>There isn't enough address space for a 100MB initrd in ROM.
> >Because of limits of the original
On Wed, Aug 04, 2010 at 04:07:09PM +0300, Gleb Natapov wrote:
> On Wed, Aug 04, 2010 at 08:04:09AM -0500, Anthony Liguori wrote:
> > On 08/04/2010 03:17 AM, Avi Kivity wrote:
> > >For playing games, there are three options:
> > >- existing fwcfg
> > >- fwcfg+dma
> > >- put roms in 4GB-2MB (or what
On Wed, Aug 04, 2010 at 08:15:04AM -0500, Anthony Liguori wrote:
> On 08/04/2010 08:07 AM, Gleb Natapov wrote:
> >On Wed, Aug 04, 2010 at 08:04:09AM -0500, Anthony Liguori wrote:
> >>On 08/04/2010 03:17 AM, Avi Kivity wrote:
> >>>For playing games, there are three options:
> >>>- existing fwcfg
> >
On Wed, Aug 04, 2010 at 07:36:04PM +0300, Avi Kivity wrote:
> This is basically my suggestion to libguestfs: instead of generating
> an initrd, generate a bootable cdrom, and boot from that. The
> result is faster and has a smaller memory footprint. Everyone wins.
We had some discussion of this
On Wed, Aug 04, 2010 at 02:06:58PM -0600, David S. Ahern wrote:
>
>
> On 08/04/10 11:34, Avi Kivity wrote:
>
> >> And it's awesome for fast prototyping. Of course, once that fast
> >> becomes dog slow, it's not useful anymore.
> >
> > For the Nth time, it's only slow with 100MB initrds.
>
> 10
This isn't a problem with qemu as such, but it may affect you if you
use qemu with a newer glibc on a Linux kernel which does not support
the preadv(2) syscall natively. glibc will attempt to emulate
preadv(2) using pread(2) syscalls, but it doesn't align the user
buffer when it does this, and th
On Fri, Feb 12, 2010 at 11:28:57AM -0600, Anthony Liguori wrote:
> I think a configure option would be in order. Forever avoiding glibc is
> probably a bit extreme.
I think a configure option won't work. The issue here was that
the binary is being installed on a machine with an older
kernel.
On Mon, Feb 15, 2010 at 11:17:27PM +0100, Christoph Hellwig wrote:
> On Fri, Feb 12, 2010 at 06:47:55PM +0000, Richard W.M. Jones wrote:
> > I don't think there's a good solution for this at the qemu level.
> > However I have a working patch for glibc:
> >
On Tue, Feb 16, 2010 at 12:41:43PM +0200, Avi Kivity wrote:
> On 02/16/2010 12:16 AM, Christoph Hellwig wrote:
>> On Fri, Feb 12, 2010 at 11:28:57AM -0600, Anthony Liguori wrote:
>>
Yes. The BSDs tend to not play stupid emulation games in the libc, so
changes of these kinds of messup
On Thu, Feb 25, 2010 at 12:13:04PM -0300, Luiz Capitulino wrote:
>
> It's emitted whenever the watchdog device's timer expires. The action
> taken is provided in the 'data' member.
Patch looks good to me - ACK.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjo
On Wed, Nov 18, 2009 at 09:19:53PM +0100, Sebastian Herbszt wrote:
> Theodore Ts'o wrote:
>
> [snip]
>
>> I was ultimately able to work around the solution by deleting the
>> /usr/local/share/qemu/pxe-*.bin files, but that's a bit of a botch. It
>> would be nice if there was a way to disable the g
On Tue, Mar 09, 2010 at 09:03:41PM -0500, Kevin O'Connor wrote:
> On Tue, Mar 09, 2010 at 02:11:20PM +, Richard W.M. Jones wrote:
> > I noticed also with libguestfs that boot times have spiralled out of
> > control again, and it seems to be down to the SeaBIOS change. SeaB
On Tue, Mar 09, 2010 at 09:35:11PM -0600, Anthony Liguori wrote:
> On 03/09/2010 08:11 AM, Richard W.M. Jones wrote:
>> Did anyone attempt this?
>>
>> I noticed also with libguestfs that boot times have spiralled out of
>> control again, and it seems to be down to t
On Sat, Mar 06, 2010 at 11:42:34PM +0100, Marc Haber wrote:
> My goal is to have a possibility to give a "speaking" name to any
> block device handed into a guest instance by the host. That name
> should be visible inside the guest, just as a LV is visible with its
> name in the system running the
On Tue, Apr 06, 2010 at 02:43:47PM +0200, Alexander Graf wrote:
> Does VMware Player support OVF?
> Does VMware Workstation support OVF?
> Does VMware Server support OVF?
Yes, but "OVF" is a rather loose term here. OVF isn't too
well standardized. But ...
> Does it make sense to build an OVF wi
On Fri, Apr 09, 2010 at 10:06:51PM +0100, Jamie Lokier wrote:
> Daniel P. Berrange wrote:
> > I think this alteration of existing args is fr too complex & fragile,
> > and way overkill.
>
> Would it not be simpler, for the target audience, for the config to
> contain a one-line shell script to
On Thu, Apr 22, 2010 at 01:36:30PM -0500, Anthony Liguori wrote:
> I think we got to the point where there was general agreement on the
> usefulness of lock=read|write but where there was still some contention
> was on this whole notion of lock=exclusive|shared.
>
> I believe Richard Jones was
On Fri, Apr 23, 2010 at 09:07:28AM +0400, Michael Tokarev wrote:
> So we'll have to either
> trial and error, or open "normally", check
> if it's a block device and re-open with that
> flag set.
Perhaps I'm missing something, but why can't you stat(2) the name
first to see if it's a block device (
[from the commit message ...]
Allow qemu to acquire shared and exclusive locks on disk images.
This is done by extending the -drive option with an additional,
optional parameter:
-drive [...],lock=none
-drive [...],lock=shared
-drive [...],lock=exclusive
lock=none is the default, and it me
On Fri, Dec 04, 2009 at 11:15:12AM -0600, Anthony Liguori wrote:
> Richard W.M. Jones wrote:
>> [from the commit message ...]
>>
>> Allow qemu to acquire shared and exclusive locks on disk images.
>> This is done by extending the -drive option with an additi
On Sat, Dec 05, 2009 at 11:47:11AM -0600, Anthony Liguori wrote:
> I think I made my point poorly. Consider the following:
>
> qemu-img create -f raw base.img 10G
> qemu-img create -f qcow2 -b base.img cow1.img
> qemu-img create -f qcow2 -b base.img cow2.img
>
> qemu -drive file=cow1.img,lock=excl
On Mon, Dec 07, 2009 at 10:31:28AM +, Jamie Lokier wrote:
> Anthony Liguori wrote:
> > I'm not sure whether it's best to enable it by default because, as I
> > said earlier, I'm not comfortable with the lack of correctness wrt
> > advisory vs. mandatory locking.
>
> In my experience, disk im
On Mon, Dec 07, 2009 at 11:30:14AM +, Daniel P. Berrange wrote:
> On Mon, Dec 07, 2009 at 11:19:54AM +, Jamie Lokier wrote:
> > Daniel P. Berrange wrote:
> > > > Sometimes shared access to a raw image (partitioned or whole disk
> > > > filesystem) is ok, and sometimes it is not ok. Only th
On Mon, Dec 07, 2009 at 11:49:32AM +, Daniel P. Berrange wrote:
> On Mon, Dec 07, 2009 at 11:31:47AM +0000, Richard W.M. Jones wrote:
> > On Mon, Dec 07, 2009 at 11:30:14AM +, Daniel P. Berrange wrote:
> > > On Mon, Dec 07, 2009 at 11:19:54AM +, Jamie Lokier wrote:
&
On Mon, Dec 07, 2009 at 07:39:11AM -0600, Anthony Liguori wrote:
> Richard W.M. Jones wrote:
>> Also if we only acquire the lock during the commit operation then
>> we'll end up with disk corruption.
>
> Why do we end up with disk corruption?
Forget about locking for a
Here's a second go at this patch. The only change is that we add a
second parameter (backinglock=none|shared|exclusive) which can be used
to control locking on the first level (only) of backing disk.
Dan Berrange convinced me there was a case to retain a distinct shared
locking type.
For any qem
On Mon, Dec 07, 2009 at 08:22:24AM -0600, Anthony Liguori wrote:
> Richard W.M. Jones wrote:
>> On Mon, Dec 07, 2009 at 07:39:11AM -0600, Anthony Liguori wrote:
>>
>>> Richard W.M. Jones wrote:
>>>
>>>> Also if we only acquire the lock durin
On Tue, Dec 08, 2009 at 10:48:17AM +0100, Kevin Wolf wrote:
> Am 07.12.2009 15:31, schrieb Richard W.M. Jones:
> > So to be clear, the use case is that all the other VMs must be shut
> > down, then the VM which wants to commit will upgrade its lock and
> > commit, and then a
On Tue, Dec 08, 2009 at 11:00:17AM +0100, Kevin Wolf wrote:
> Am 07.12.2009 15:16, schrieb Richard W.M. Jones:
> > Here's a second go at this patch. The only change is that we add a
> > second parameter (backinglock=none|shared|exclusive) which can be used
> > to co
ere locking is *not* implemented:
cloop - directly open()s the file, no locking implemented
cow - same as cloop
curl - protocol probably doesn't support locking
nbd - same as curl
Signed-off-by: Richard W.M. Jones
---
block.c | 19 +--
block.h
On Tue, Dec 15, 2009 at 12:02:04PM -0600, Anthony Liguori wrote:
> Richard W.M. Jones wrote:
>> This is v3 of the lock patch, previously discussed here:
>>
>> http://lists.gnu.org/archive/html/qemu-devel/2009-12/threads.html#00461
>>
>> In this version I've
On Thu, Dec 17, 2009 at 11:53:45AM +0100, Christoph Hellwig wrote:
> If you're primarily interested in protection against other qemu
> instances you can add you code on top, but that seems like a rather
> marginal use case.
It's a pretty serious case for people accessing live virtual machines
with
601 - 700 of 1249 matches
Mail list logo
