- "Anthony Liguori" wrote:
> A lot of people copy libvirt's command line from ps -ef and then
> wonder why the
> VM isn't working correctly. Let's be kind and tell them what they
> should do
> instead.
>
> Without this patch, if you run with an invalid -net tap,fd=X, the
> guest still
> ru
On 10/09/2010 01:40 AM, Luiz Capitulino wrote:
On Tue, 28 Sep 2010 16:57:44 +0200
"Michael S. Tsirkin" wrote:
On Tue, Sep 28, 2010 at 11:53:43AM -0300, Luiz Capitulino wrote:
On Mon, 27 Sep 2010 15:52:44 +0800
Jason Wang wrote:
monitor_get_fd() may also be used to parse f
This patch checks the validity of 9p related commandline
arguments and throws error if the arguments are not appropriate.
Signed-off-by: Harsh Prateek Bora
---
fsdev/qemu-fsdev.c | 39 ++-
hw/virtio-9p.c |2 +-
2 files changed, 27 insertions(+), 14 d
On Tue, Oct 12, 2010 at 09:32, guenthert wrote:
> Public bug reported:
>
> Throughout the (sparse) documentation and the cmd-line help text, Qemu
> refers to VLAN ("virtual" LANs), which are unrelated to 802.1Q (tagged
> ethernet) VLAN, which, IMHO is _very_ confusing. Beyond that, it's also
> unn
Public bug reported:
Throughout the (sparse) documentation and the cmd-line help text, Qemu
refers to VLAN ("virtual" LANs), which are unrelated to 802.1Q (tagged
ethernet) VLAN, which, IMHO is _very_ confusing. Beyond that, it's also
unnecessary, as the network in question isn't "virtual", only t
Hi,
Currently qemu-kvm build fail on RHEL5 with gcc 4.1.2, build can pass on
Fedora11 with gcc 4.4.1, can anybody look on RHEL5 system?
Gcc: 4.1.2
system: RHEL5.1
qemu-kvm: 85566812a4f8cae721fea0224e05a7e75c08c5dd
...
LINK qemu-img
LINK qemu-io
CClibhw64/virtio-9p-local.o
cc1: warni
On Mon, Oct 11, 2010 at 12:18:55PM +0200, Gleb Natapov wrote:
> Currently if VM is started with multiple disks it is almost impossible to
> guess which one of them will be used as boot device especially if there
> is a mix of ATA/virtio/SCSI devices. Essentially BIOS decides the order
> and without
On 10/11/2010 06:45 PM, Luiz Capitulino wrote:
On Mon, 11 Oct 2010 17:15:30 -0500
Anthony Liguori wrote:
After suffering from a prolonged maintainer softlockup, I'm attempting
to get 0.13.0 release process back on track.
I've tagged qemu-0.13.0-rc3 in git which only carries a few changes
On Mon, 11 Oct 2010 17:15:30 -0500
Anthony Liguori wrote:
> After suffering from a prolonged maintainer softlockup, I'm attempting
> to get 0.13.0 release process back on track.
>
> I've tagged qemu-0.13.0-rc3 in git which only carries a few changes
> since 0.13.0-rc1. Most notably, a series
On Mon, Oct 11, 2010 at 02:08:13PM +0200, Gleb Natapov wrote:
> On Mon, Oct 11, 2010 at 01:16:00PM +0200, Bernhard Kohl wrote:
> > I think this also applies to network booting via gPXE. Usually our VMs
> > have 4 NICs, mixed virtio-net and PCI pass-through. 2 of the NICs shall
> > be used for booti
On Mon, Oct 11, 2010 at 07:04:25PM +0200, Gleb Natapov wrote:
> On Mon, Oct 11, 2010 at 12:01:58PM -0500, Anthony Liguori wrote:
> > On 10/11/2010 10:52 AM, Stefan Hajnoczi wrote:
> > >SeaBIOS may do that but gPXE internally just probes all PCI devices.
> > >It does not take advantage of the PCI bu
After suffering from a prolonged maintainer softlockup, I'm attempting
to get 0.13.0 release process back on track.
I've tagged qemu-0.13.0-rc3 in git which only carries a few changes
since 0.13.0-rc1. Most notably, a series of updates from Kevin Wolf and
Cam Macdonell's ivshmem device.
I t
On 10/11/2010 02:41 PM, Sebastian Herbszt wrote:
> H. Peter Anvin wrote:
>> On 10/11/2010 01:30 PM, Anthony Liguori wrote:
>>> On 10/11/2010 02:59 PM, Gleb Natapov wrote:
No boot rom should do that. extboot wreaks havoc when it is used.
And since virtio is now supported by bios there is n
H. Peter Anvin wrote:
On 10/11/2010 01:30 PM, Anthony Liguori wrote:
On 10/11/2010 02:59 PM, Gleb Natapov wrote:
No boot rom should do that. extboot wreaks havoc when it is used.
And since virtio is now supported by bios there is no reason to use it.
You don't really have a choice. You could
On Mon, Oct 11, 2010 at 03:50:08PM -0500, Anthony Liguori wrote:
> On 10/11/2010 03:36 PM, Gleb Natapov wrote:
> >On Mon, Oct 11, 2010 at 03:30:21PM -0500, Anthony Liguori wrote:
> >>On 10/11/2010 02:59 PM, Gleb Natapov wrote:
> >>>No boot rom should do that. extboot wreaks havoc when it is used.
>
On 10/11/2010 01:30 PM, Anthony Liguori wrote:
> On 10/11/2010 02:59 PM, Gleb Natapov wrote:
>> No boot rom should do that. extboot wreaks havoc when it is used.
>> And since virtio is now supported by bios there is no reason to use it.
>
> You don't really have a choice. You could be doing hardw
On 10/07/2010 09:54 AM, Michael S. Tsirkin wrote:
Here are some fixes, all over the place.
I am guessing the below fixes all make sense for the 0.13 branch, too.
The per-device notifier patch is the only one that does not
fix bugs, but it is needed for a bugfix patch on qemu-kvm stable
that depe
On 10/11/2010 03:36 PM, Gleb Natapov wrote:
On Mon, Oct 11, 2010 at 03:30:21PM -0500, Anthony Liguori wrote:
On 10/11/2010 02:59 PM, Gleb Natapov wrote:
No boot rom should do that. extboot wreaks havoc when it is used.
And since virtio is now supported by bios there is no reason to us
On Mon, Oct 11, 2010 at 03:30:21PM -0500, Anthony Liguori wrote:
> On 10/11/2010 02:59 PM, Gleb Natapov wrote:
> >No boot rom should do that. extboot wreaks havoc when it is used.
> >And since virtio is now supported by bios there is no reason to use it.
>
> You don't really have a choice. You co
On 10/11/2010 02:59 PM, Gleb Natapov wrote:
No boot rom should do that. extboot wreaks havoc when it is used.
And since virtio is now supported by bios there is no reason to use it.
You don't really have a choice. You could be doing hardware passthrough
and the ROM on the card may hijack
On 10/11/2010 12:51 PM, Anthony Liguori wrote:
>
> -kernel hijacks int19 so it cannot participate in any kind of boot
> order. It's either present (and therefore the bootable disk) or not
> present.
>
That's a misdesign, though: it should be able to participate in BBS as a
BEV.
-hpa
On Mon, Oct 11, 2010 at 02:51:09PM -0500, Anthony Liguori wrote:
> On 10/11/2010 07:07 AM, Gerd Hoffmann wrote:
> > Hi,
> >
> >>Floppy? Yes, I think we do.
> >
> >And *one* floppy controllers can actually have *two* drives
> >connected, although booting from 'b' doesn't work IIRC.
> >
> >>>and sin
On Mon, Oct 11, 2010 at 02:48:48PM -0500, Anthony Liguori wrote:
> On 10/11/2010 07:16 AM, Gleb Natapov wrote:
> >On Mon, Oct 11, 2010 at 02:07:14PM +0200, Gerd Hoffmann wrote:
> >> Hi,
> >>
> >>>Floppy? Yes, I think we do.
> >>And *one* floppy controllers can actually have *two* drives
> >>conne
On 10/11/2010 07:07 AM, Gerd Hoffmann wrote:
Hi,
Floppy? Yes, I think we do.
And *one* floppy controllers can actually have *two* drives connected,
although booting from 'b' doesn't work IIRC.
and since one PCI device may
control more then one disk (ATA slave/master, SCSI LUNs). We can
On 10/11/2010 07:16 AM, Gleb Natapov wrote:
On Mon, Oct 11, 2010 at 02:07:14PM +0200, Gerd Hoffmann wrote:
Hi,
Floppy? Yes, I think we do.
And *one* floppy controllers can actually have *two* drives
connected, although booting from 'b' doesn't work IIRC.
and since
Public bug reported:
KVM/Qemu should check whether the disk images have write permissions in
order to prevent users from getting weird IO errors in their VMs without
understanding what's happening.
** Affects: qemu
Importance: Undecided
Status: New
** Affects: kvm (Ubuntu)
Imp
Port qemu-kvm's
commit 4b62fff1101a7ad77553147717a8bd3bf79df7ef
Author: Huang Ying
Date: Mon Sep 21 10:43:25 2009 +0800
MCE: Relay UCR MCE to guest
UCR (uncorrected recovery) MCE is supported in recent Intel CPUs,
where some hardware error such as some memory error can be repo
Port qemu-kvm's signalfd compat code.
commit 5a7fdd0abd7cd24dac205317a4195446ab8748b5
Author: Anthony Liguori
Date: Wed May 7 11:55:47 2008 -0500
Use signalfd() in io-thread
This patch reworks the IO thread to use signalfd() instead of sigtimedwait()
This will eliminate the ne
Port qemu-kvm's
commit 1bab5d11545d8de5facf46c28630085a2f9651ae
Author: Huang Ying
Date: Wed Mar 3 16:52:46 2010 +0800
Add savevm/loadvm support for MCE
MCE registers are saved/load into/from CPUState in
kvm_arch_save/load_regs. To simulate the MCG_STATUS clearing upon
res
From: Huang Ying
In QEMU-KVM, physical address != RAM address. While MCE simulation
needs physical address instead of RAM address. So
kvm_physical_memory_addr_from_ram() is implemented to do the
conversion, and it is invoked before being filled in the IA32_MCi_ADDR
MSR.
Reported-by: Dean Nelson
Block SIGALRM, SIGIO and consume them via signalfd.
Signed-off-by: Marcelo Tosatti
Index: qemu/cpus.c
===
--- qemu.orig/cpus.c
+++ qemu/cpus.c
@@ -33,6 +33,7 @@
#include "exec-all.h"
#include "cpus.h"
+#include "compatfd.h"
#
To be used by next patches.
Signed-off-by: Marcelo Tosatti
Index: qemu/cpu-common.h
===
--- qemu.orig/cpu-common.h
+++ qemu/cpu-common.h
@@ -47,7 +47,8 @@ void qemu_ram_free(ram_addr_t addr);
/* This should only be used for ram loc
Port qemu-kvm's MCE support
commit c68b2374c9048812f488e00ffb95db66c0bc07a7
Author: Huang Ying
Date: Mon Jul 20 10:00:53 2009 +0800
Add MCE simulation support to qemu/kvm
KVM ioctls are used to initialize MCE simulation and inject MCE. The
real MCE simulation is implemented in
Port qemu-kvm's KVM MCE (Machine Check Exception) handling to qemu. It
allows qemu to propagate MCEs to the guest.
v2:
- rename do_qemu_ram_addr_from_host.
- fix kvm_on_sigbus/kvm_on_sigbus_vcpu naming.
- fix bank register restoration (Dean Nelson).
v3:
- condition MCE generation on MCE_SEG_P bit
commit ce6325ff1af34dbaee91c8d28e792277e43f1227
Author: Glauber Costa
Date: Wed Mar 5 17:01:10 2008 -0300
Augment info cpus
This patch exposes the thread id associated with each
cpu through the already well known 'info cpus' interface.
Signed-off-by: Marcelo Tosatti
Index: q
Jes, I feel a bit bad finding still more faults, but here goes...
jes.soren...@redhat.com writes:
> From: Jes Sorensen
>
> strtosz() returns -1 on error. It now supports human unit formats in
> eg. 1.0G, with better error handling.
>
> Signed-off-by: Jes Sorensen
> ---
> cutils.c | 61
On Mon, Oct 11, 2010 at 12:01:58PM -0500, Anthony Liguori wrote:
> On 10/11/2010 10:52 AM, Stefan Hajnoczi wrote:
> >2010/10/11 Gleb Natapov:
> >>On Mon, Oct 11, 2010 at 01:48:09PM +0100, Stefan Hajnoczi wrote:
> >>>On Mon, Oct 11, 2010 at 12:16 PM, Bernhard Kohl
> >>>wrote:
> Am 11.10.2010 1
On 10/11/2010 10:52 AM, Stefan Hajnoczi wrote:
2010/10/11 Gleb Natapov:
On Mon, Oct 11, 2010 at 01:48:09PM +0100, Stefan Hajnoczi wrote:
On Mon, Oct 11, 2010 at 12:16 PM, Bernhard Kohl wrote:
Am 11.10.2010 12:18, schrieb ext Gleb Natapov:
Currently if VM is starte
The crashes were most likely fixed by commit
e8637c9013609271772cc0c3436cb1240cd6b034 , which is a part of 0.13 and
while it applies to 0.12 just fine, it didn't went into 0.12-stable.
--
qemu 0.11.50: Guest boot failed when the drive interface is scsi
https://bugs.launchpad.net/bugs/485251
You r
On 10/11/2010 03:42 PM, Stefan Hajnoczi wrote:
>
> A leak is acceptable (it won't grow; it's just an unused, incorrect
> freelist), but data corruption is not.
The alternative is for the freelist to be a non-compat feature bit.
That means older QEMU binaries cannot use a QED image that has en
Stefan Weil writes:
> Am 11.10.2010 16:53, schrieb Markus Armbruster:
>> Blue Swirl writes:
>>
>>> Compiling with GCC 4.6.0 20100925 produced warnings:
>>> /src/qemu/hw/eepro100.c: In function 'eepro100_read4':
>>> /src/qemu/hw/eepro100.c:1351:14: error: 'val' may be used
>>> uninitialized in th
On 10/11/2010 11:18 AM, Anthony Liguori wrote:
On 10/11/2010 10:46 AM, Stefan Hajnoczi wrote:
On Mon, Oct 11, 2010 at 05:39:01PM +0200, Avi Kivity wrote:
On 10/11/2010 05:30 PM, Stefan Hajnoczi wrote:
It was discussed before, but I don't think we came to a
conclusion. Are
there any circ
On 10/11/2010 12:18 PM, Gleb Natapov wrote:
Currently if VM is started with multiple disks it is almost impossible to
guess which one of them will be used as boot device especially if there
is a mix of ATA/virtio/SCSI devices. Essentially BIOS decides the order
and without looking into the code
On 10/11/2010 11:02 AM, Avi Kivity wrote:
On 10/11/2010 05:49 PM, Anthony Liguori wrote:
On 10/11/2010 09:58 AM, Avi Kivity wrote:
A leak is unacceptable. It means an image can grow to an unbounded
size. If you are a server provider offering multitenancy, then a
malicious guest can potentia
On 10/11/2010 05:39 PM, Gleb Natapov wrote:
On Mon, Oct 11, 2010 at 05:09:22PM +0200, Avi Kivity wrote:
> On 10/11/2010 12:18 PM, Gleb Natapov wrote:
> >Currently if VM is started with multiple disks it is almost impossible to
> >guess which one of them will be used as boot device especially
On Mon, Oct 11, 2010 at 03:10:16PM +0200, Avi Kivity wrote:
> On 10/11/2010 12:37 PM, Stefan Hajnoczi wrote:
> >On Sun, Oct 10, 2010 at 11:10:15AM +0200, Avi Kivity wrote:
> >> On 10/08/2010 05:48 PM, Stefan Hajnoczi wrote:
> >> >This patch implements the read/write state machine. Operations a
From: Anthony PERARD
The mapcache maps chucks of guest memory on demand, unmaps them when
they are not needed anymore.
Each call to qemu_get_ram_ptr makes a call to qemu_map_cache with the
lock option, so mapcache will not unmap these ram_ptr.
Signed-off-by: Anthony PERARD
Signed-off-by: Stefa
From: Anthony PERARD
Signed-off-by: Anthony PERARD
---
hw/acpi_piix4.c |4
hw/xen.h|2 ++
xen-all.c |7 +++
xen-stub.c |4
4 files changed, 17 insertions(+), 0 deletions(-)
diff --git a/hw/acpi_piix4.c b/hw/acpi_piix4.c
index c8733e5..058bd5f 10
Am 10.10.2010 00:46, schrieb Andreas Färber:
Am 04.10.2010 um 21:29 schrieb Stefan Weil:
Am 25.09.2010 09:46, schrieb Blue Swirl:
On Thu, Sep 23, 2010 at 8:44 PM, Stefan Weil
wrote:
Am 23.09.2010 22:33, schrieb Blue Swirl:
On Thu, Sep 23, 2010 at 7:28 PM, Stefan Weil
wrote:
Replace the
From: Anthony PERARD
This come with the initialisation of Xen.
Signed-off-by: Anthony PERARD
---
Makefile.target |5 +
hw/xen.h| 10 ++
vl.c|2 ++
xen-all.c | 25 +
xen-stub.c | 17 +
5 files chang
From: Anthony PERARD
Introduce two functions qemu_shutdown_requested_get and
qemu_reset_requested_get to get the value of shutdown/reset_requested
without reset it.
Signed-off-by: Anthony PERARD
Signed-off-by: Stefano Stabellini
---
sysemu.h |2 ++
vl.c | 10 ++
2 files chan
From: Anthony PERARD
Open and bind event channels; map ioreq and buffered ioreq rings.
Signed-off-by: Anthony PERARD
Signed-off-by: Stefano Stabellini
---
hw/xen_common.h |3 +
xen-all.c | 407 +++
2 files changed, 410 insertions(
On Mon, Oct 11, 2010 at 01:48:09PM +0100, Stefan Hajnoczi wrote:
> On Mon, Oct 11, 2010 at 12:16 PM, Bernhard Kohl wrote:
> > Am 11.10.2010 12:18, schrieb ext Gleb Natapov:
> >>
> >> Currently if VM is started with multiple disks it is almost impossible to
> >> guess which one of them will be used
From: Anthony PERARD
This function allows to unlock a ram_ptr give by qemu_get_ram_ptr. After
a call to qemu_ram_ptr_unlock, the pointer may be unmap from QEMU when
used with Xen.
Signed-off-by: Anthony PERARD
---
cpu-common.h |1 +
exec.c | 10 ++
xen-mapcache.c | 34
On Mon, Oct 11, 2010 at 04:52:31PM +0100, Stefan Hajnoczi wrote:
> 2010/10/11 Gleb Natapov :
> > On Mon, Oct 11, 2010 at 01:48:09PM +0100, Stefan Hajnoczi wrote:
> >> On Mon, Oct 11, 2010 at 12:16 PM, Bernhard Kohl
> >> wrote:
> >> > Am 11.10.2010 12:18, schrieb ext Gleb Natapov:
> >> >>
> >> >>
From: Anthony PERARD
This tells to the xen management tool that the machine can begin run.
Signed-off-by: Anthony PERARD
---
xen-all.c | 27 +++
1 files changed, 27 insertions(+), 0 deletions(-)
diff --git a/xen-all.c b/xen-all.c
index a0d1b9b..fc862cb 100644
--- a/x
From: Anthony PERARD
Introduce a 8259 Interrupt Controller for target-xen; every set_irq
call makes a Xen hypercall.
Signed-off-by: Anthony PERARD
Signed-off-by: Stefano Stabellini
---
hw/xen_common.h |2 ++
hw/xen_machine_fv.c |5 ++---
xen-all.c | 12
3
From: Anthony PERARD
Introduce a new emulated PCI device, specific to fully virtualized Xen
guests. The device is necessary for PV on HVM drivers to work.
Signed-off-by: Anthony PERARD
Signed-off-by: Stefano Stabellini
---
Makefile.target |1 +
hw/hw.h |3 +
hw/pci_id
From: Anthony PERARD
This patch introduces Xen specific call in piix_pci.
The specific part for Xen is in write_config, set_irq and get_pirq.
Signed-off-by: Anthony PERARD
Signed-off-by: Stefano Stabellini
---
hw/piix_pci.c | 28 ++--
hw/xen.h |6 ++
xe
From: Anthony PERARD
Signed-off-by: Anthony PERARD
---
hw/xen_backend.c | 308
hw/xen_disk.c| 412 +++---
hw/xen_nic.c | 222 +++---
3 files changed, 471 insertions(+), 47
From: Anthony PERARD
Add the Xen FV (Fully Virtualized) machine to Qemu;
this is groundwork to add Xen device model support in Qemu.
Signed-off-by: Anthony PERARD
Signed-off-by: Stefano Stabellini
---
Makefile.target |3 +
hw/xen_common.h |5 ++
hw/xen_machine_fv.c | 158
On 10/11/2010 04:06 PM, Stefan Hajnoczi wrote:
On Mon, Oct 11, 2010 at 03:44:38PM +0200, Avi Kivity wrote:
> On 10/11/2010 03:42 PM, Stefan Hajnoczi wrote:
> >>
> >> A leak is acceptable (it won't grow; it's just an unused, incorrect
> >> freelist), but data corruption is not.
> >
> >
From: Anthony PERARD
This option gives the ability to switch one "accelerator" like kvm, xen
or the default one tcg. We can specify more than one accelerator by
separate them by a comma. QEMU will try each one and use the first whose
works.
So,
-accel xen,kvm,tcg
which would try Xen support fi
Am 11.10.2010 17:30, schrieb Stefan Hajnoczi:
> On Mon, Oct 11, 2010 at 03:58:07PM +0200, Kevin Wolf wrote:
>> Am 08.10.2010 17:48, schrieb Stefan Hajnoczi:
>>> Signed-off-by: Stefan Hajnoczi
>>> ---
>>> docs/specs/qed_spec.txt | 94
>>> +++
>>> 1 fi
On 10/11/2010 10:46 AM, Stefan Hajnoczi wrote:
On Mon, Oct 11, 2010 at 05:39:01PM +0200, Avi Kivity wrote:
On 10/11/2010 05:30 PM, Stefan Hajnoczi wrote:
It was discussed before, but I don't think we came to a conclusion. Are
there any circumstances under which you don't want to
From: Anthony PERARD
Update the libxenctrl calls in Qemu to use the new interface, otherwise
Qemu wouldn't be able to build against new versions of the library.
We also check libxenctrl version in configure, from Xen 3.3.0 to Xen
unstable.
Signed-off-by: Anthony PERARD
Signed-off-by: Stefano S
On 10/11/2010 05:41 PM, Anthony Liguori wrote:
On 10/11/2010 10:24 AM, Avi Kivity wrote:
On 10/11/2010 05:02 PM, Anthony Liguori wrote:
On 10/11/2010 08:44 AM, Avi Kivity wrote:
On 10/11/2010 03:42 PM, Stefan Hajnoczi wrote:
>
> A leak is acceptable (it won't grow; it's just an unused,
i
Am 11.10.2010 16:53, schrieb Markus Armbruster:
Blue Swirl writes:
Compiling with GCC 4.6.0 20100925 produced warnings:
/src/qemu/hw/eepro100.c: In function 'eepro100_read4':
/src/qemu/hw/eepro100.c:1351:14: error: 'val' may be used
uninitialized in this function [-Werror=uninitialized]
/src/q
From: Anthony PERARD
Hi all,
This is the fifth version of the patch series that adds Xen device model support
in QEMU.
The change we have made on the last version are:
- We removed the Xen specific ACPI PIIX4 implementation and added a Xen call
in
acpi_piix4.c for the sleep state.
- W
2010/10/11 Gleb Natapov :
> On Mon, Oct 11, 2010 at 01:48:09PM +0100, Stefan Hajnoczi wrote:
>> On Mon, Oct 11, 2010 at 12:16 PM, Bernhard Kohl
>> wrote:
>> > Am 11.10.2010 12:18, schrieb ext Gleb Natapov:
>> >>
>> >> Currently if VM is started with multiple disks it is almost impossible to
>> >>
On 10/11/2010 10:24 AM, Avi Kivity wrote:
On 10/11/2010 05:02 PM, Anthony Liguori wrote:
On 10/11/2010 08:44 AM, Avi Kivity wrote:
On 10/11/2010 03:42 PM, Stefan Hajnoczi wrote:
>
> A leak is acceptable (it won't grow; it's just an unused, incorrect
> freelist), but data corruption is not.
On 10/11/2010 05:49 PM, Anthony Liguori wrote:
On 10/11/2010 09:58 AM, Avi Kivity wrote:
A leak is unacceptable. It means an image can grow to an unbounded
size. If you are a server provider offering multitenancy, then a
malicious guest can potentially grow the image beyond it's allotted
si
Am 08.10.2010 17:48, schrieb Stefan Hajnoczi:
> Signed-off-by: Stefan Hajnoczi
> ---
> docs/specs/qed_spec.txt | 94
> +++
> 1 files changed, 94 insertions(+), 0 deletions(-)
> create mode 100644 docs/specs/qed_spec.txt
>
> diff --git a/docs/specs/
On 10/11/2010 05:30 PM, Stefan Hajnoczi wrote:
>
> It was discussed before, but I don't think we came to a conclusion. Are
> there any circumstances under which you don't want to set the
> QED_CF_BACKING_FORMAT flag?
I suggest the following:
QED_CF_BACKING_FORMAT_RAW = 0x1
When set, the ba
On Mon, Oct 11, 2010 at 05:09:22PM +0200, Avi Kivity wrote:
> On 10/11/2010 12:18 PM, Gleb Natapov wrote:
> >Currently if VM is started with multiple disks it is almost impossible to
> >guess which one of them will be used as boot device especially if there
> >is a mix of ATA/virtio/SCSI devices.
On Mon, Oct 11, 2010 at 03:58:07PM +0200, Kevin Wolf wrote:
> Am 08.10.2010 17:48, schrieb Stefan Hajnoczi:
> > Signed-off-by: Stefan Hajnoczi
> > ---
> > docs/specs/qed_spec.txt | 94
> > +++
> > 1 files changed, 94 insertions(+), 0 deletions(-)
> >
On Mon, Oct 11, 2010 at 03:44:38PM +0200, Avi Kivity wrote:
> On 10/11/2010 03:42 PM, Stefan Hajnoczi wrote:
> >>
> >> A leak is acceptable (it won't grow; it's just an unused, incorrect
> >> freelist), but data corruption is not.
> >
> >The alternative is for the freelist to be a non-compat fea
On 10/11/2010 09:58 AM, Avi Kivity wrote:
A leak is unacceptable. It means an image can grow to an unbounded
size. If you are a server provider offering multitenancy, then a
malicious guest can potentially grow the image beyond it's allotted
size causing a Denial of Service attack against ano
Blue Swirl writes:
> Compiling with GCC 4.6.0 20100925 produced warnings:
> /src/qemu/hw/eepro100.c: In function 'eepro100_read4':
> /src/qemu/hw/eepro100.c:1351:14: error: 'val' may be used
> uninitialized in this function [-Werror=uninitialized]
> /src/qemu/hw/eepro100.c: In function 'eepro100_
On Mon, Oct 11, 2010 at 05:42:30PM +0200, Avi Kivity wrote:
> On 10/11/2010 05:39 PM, Gleb Natapov wrote:
> >On Mon, Oct 11, 2010 at 05:09:22PM +0200, Avi Kivity wrote:
> >> On 10/11/2010 12:18 PM, Gleb Natapov wrote:
> >> >Currently if VM is started with multiple disks it is almost impossible
On Mon, Oct 11, 2010 at 05:39:01PM +0200, Avi Kivity wrote:
> On 10/11/2010 05:30 PM, Stefan Hajnoczi wrote:
> >>
> >> It was discussed before, but I don't think we came to a conclusion. Are
> >> there any circumstances under which you don't want to set the
> >> QED_CF_BACKING_FORMAT flag?
> >
On 10/11/2010 08:04 AM, Avi Kivity wrote:
On 10/11/2010 12:09 PM, Stefan Hajnoczi wrote:
On Sun, Oct 10, 2010 at 11:20:09AM +0200, Avi Kivity wrote:
> On 10/08/2010 05:48 PM, Stefan Hajnoczi wrote:
> >Signed-off-by: Stefan Hajnoczi
> >---
> > docs/specs/qed_spec.txt | 94
On 10/11/2010 08:44 AM, Avi Kivity wrote:
On 10/11/2010 03:42 PM, Stefan Hajnoczi wrote:
>
> A leak is acceptable (it won't grow; it's just an unused, incorrect
> freelist), but data corruption is not.
The alternative is for the freelist to be a non-compat feature bit.
That means older QEMU
On 10/11/2010 04:54 PM, Anthony Liguori wrote:
On 10/11/2010 08:04 AM, Avi Kivity wrote:
On 10/11/2010 12:09 PM, Stefan Hajnoczi wrote:
On Sun, Oct 10, 2010 at 11:20:09AM +0200, Avi Kivity wrote:
> On 10/08/2010 05:48 PM, Stefan Hajnoczi wrote:
> >Signed-off-by: Stefan Hajnoczi
> >---
> >
Am 08.10.2010 17:48, schrieb Stefan Hajnoczi:
> This patch introduces the qed on-disk layout and implements image
> creation. Later patches add read/write and other functionality.
>
> Signed-off-by: Stefan Hajnoczi
> ---
> Makefile.objs |1 +
> block/qed.c | 530
> ++
On 10/11/2010 05:02 PM, Anthony Liguori wrote:
On 10/11/2010 08:44 AM, Avi Kivity wrote:
On 10/11/2010 03:42 PM, Stefan Hajnoczi wrote:
>
> A leak is acceptable (it won't grow; it's just an unused, incorrect
> freelist), but data corruption is not.
The alternative is for the freelist to be
On Mon, Oct 11, 2010 at 2:21 PM, Kevin Wolf wrote:
> Am 08.10.2010 17:48, schrieb Stefan Hajnoczi:
>> This code is also available from git:
>>
>> http://repo.or.cz/w/qemu/stefanha.git/shortlog/refs/heads/qed
>
> This doesn't seem to be the same as the latest patches you posted to
> qemu-devel. For
Blue Swirl writes:
> Compiling with GCC 4.6.0 20100925 produced warnings like:
> /src/qemu/hw/mips_fulong2e.c: In function 'mips_fulong2e_init':
> /src/qemu/hw/mips_fulong2e.c:274:16: error: variable 'rtc_state' set
> but not used [-Werror=unused-but-set-variable]
> /src/qemu/hw/mips_fulong2e.c:2
On 10/11/2010 08:10 AM, Avi Kivity wrote:
On 10/11/2010 12:37 PM, Stefan Hajnoczi wrote:
On Sun, Oct 10, 2010 at 11:10:15AM +0200, Avi Kivity wrote:
> On 10/08/2010 05:48 PM, Stefan Hajnoczi wrote:
> >This patch implements the read/write state machine. Operations are
> >fully asynchronous an
Jes Sorensen writes:
> On 10/11/10 10:51, Markus Armbruster wrote:
>> jes.soren...@redhat.com writes:
>>> +/*
>>> + * Convert string to bytes, allowing either K/k for KB, M/m for MB,
>>> + * G/g for GB or T/t for TB. Default without any postfix is MB.
>>> + * End pointer will be returned in *end,
On Mon, Oct 11, 2010 at 03:04:03PM +0200, Avi Kivity wrote:
> On 10/11/2010 12:09 PM, Stefan Hajnoczi wrote:
> >On Sun, Oct 10, 2010 at 11:20:09AM +0200, Avi Kivity wrote:
> >> On 10/08/2010 05:48 PM, Stefan Hajnoczi wrote:
> >> >Signed-off-by: Stefan Hajnoczi
> >> >---
> >> > docs/specs/qe
Maybe Kevin or Christoph (cc'ed) can help.
Mathias Krause writes:
> On 24.09.2010 14:47, Markus Armbruster wrote:
>> Mathias Krause writes:
>>
>>> On 17.09.2010 15:27, Anthony Liguori wrote:
On 09/17/2010 01:50 AM, Mathias Krause wrote:
> Am 16.09.2010 19:20 schrieb Anthony Liguori:
>
Am 08.10.2010 17:48, schrieb Stefan Hajnoczi:
> This code is also available from git:
>
> http://repo.or.cz/w/qemu/stefanha.git/shortlog/refs/heads/qed
This doesn't seem to be the same as the latest patches you posted to
qemu-devel. Forgot to push?
Kevin
On 10/11/2010 12:37 PM, Stefan Hajnoczi wrote:
On Sun, Oct 10, 2010 at 11:10:15AM +0200, Avi Kivity wrote:
> On 10/08/2010 05:48 PM, Stefan Hajnoczi wrote:
> >This patch implements the read/write state machine. Operations are
> >fully asynchronous and multiple operations may be active at an
On 10/11/10 10:51, Markus Armbruster wrote:
> jes.soren...@redhat.com writes:
>> +/*
>> + * Convert string to bytes, allowing either K/k for KB, M/m for MB,
>> + * G/g for GB or T/t for TB. Default without any postfix is MB.
>> + * End pointer will be returned in *end, if end is valid.
>> + * Retur
On 10/11/2010 02:52 PM, Markus Armbruster wrote:
Warns about this line in check-qjson.c:
QObject *obj = qobject_from_json("");
The obvious fix (add -Wno-format-zero-length to gcc_flags) doesn't
work, because -Wall switches it on again. Fix by putting configured
flags last.
Signed-off-by:
On 10/11/2010 12:09 PM, Stefan Hajnoczi wrote:
On Sun, Oct 10, 2010 at 11:20:09AM +0200, Avi Kivity wrote:
> On 10/08/2010 05:48 PM, Stefan Hajnoczi wrote:
> >Signed-off-by: Stefan Hajnoczi
> >---
> > docs/specs/qed_spec.txt | 94
+++
> > 1
On Mon, Oct 11, 2010 at 12:16 PM, Bernhard Kohl wrote:
> Am 11.10.2010 12:18, schrieb ext Gleb Natapov:
>>
>> Currently if VM is started with multiple disks it is almost impossible to
>> guess which one of them will be used as boot device especially if there
>> is a mix of ATA/virtio/SCSI devices.
From: Jes Sorensen
strtosz() returns -1 on error. It now supports human unit formats in
eg. 1.0G, with better error handling.
Signed-off-by: Jes Sorensen
---
cutils.c | 61 +
qemu-common.h |1 +
vl.c | 31 +--
Warns about this line in check-qjson.c:
QObject *obj = qobject_from_json("");
The obvious fix (add -Wno-format-zero-length to gcc_flags) doesn't
work, because -Wall switches it on again. Fix by putting configured
flags last.
Signed-off-by: Markus Armbruster
---
configure |5 +++--
1 fi
1 - 100 of 134 matches
Mail list logo
