Can't seem to find anything in the upstream changelogs or source to
indicate that such a change was made.
--
LVM backed drives should default to cache='none'
https://bugs.launchpad.net/bugs/568445
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed t
cache=writethrough and cache=none have equivalent data integrity.
FWIW, I believe most recent versions of virt-manager default to
cache=none for physical devices.
--
LVM backed drives should default to cache='none'
https://bugs.launchpad.net/bugs/568445
You received this bug notification because
@Anthony,
I'm aware that I can manipulate the cache settings via libvirt's XML.
That's currently what I've been doing, manually after every VM creation.
However, my point is that qemu clearly recommends that caching not be
used with disks stored on raw volumes. Additionally, virt-manager does
not
On Fri, 13 Aug 2010, Blue Swirl wrote:
> On Fri, Aug 13, 2010 at 9:01 PM, malc wrote:
> > On Fri, 13 Aug 2010, Blue Swirl wrote:
> >
> >> On Thu, Aug 12, 2010 at 5:50 PM, Blue Swirl wrote:
> >> > Add memory management rules, somewhat like libvirt HACKING.
> >> >
> >> > Signed-off-by: Blue Swirl
On Fri, Aug 13, 2010 at 9:01 PM, malc wrote:
> On Fri, 13 Aug 2010, Blue Swirl wrote:
>
>> On Thu, Aug 12, 2010 at 5:50 PM, Blue Swirl wrote:
>> > Add memory management rules, somewhat like libvirt HACKING.
>> >
>> > Signed-off-by: Blue Swirl
>> > ---
>> > CODING_STYLE | 8
>> > 1 f
On Fri, 13 Aug 2010, Blue Swirl wrote:
> On Thu, Aug 12, 2010 at 5:50 PM, Blue Swirl wrote:
> > Add memory management rules, somewhat like libvirt HACKING.
> >
> > Signed-off-by: Blue Swirl
> > ---
> > CODING_STYLE | 8
> > 1 files changed, 8 insertions(+), 0 deletions(-)
> >
> > di
On Fri, 13 Aug 2010, Blue Swirl wrote:
> On Thu, Aug 12, 2010 at 6:56 PM, malc wrote:
> > On Thu, 12 Aug 2010, Blue Swirl wrote:
> >
> >> Add a few rules, based loosely on libvirt HACKING.
> >>
> >> Blue Swirl (5):
> >> CODING_STYLE: add preprocessor rules
> >> CODING_STYLE: add C type rules
On 08/13/2010 02:37 PM, Stefano Stabellini wrote:
On Fri, 13 Aug 2010, Anthony Liguori wrote:
On 08/12/2010 09:10 AM, stefano.stabell...@eu.citrix.com wrote:
From: Anthony PERARD
Xen currently uses a different BIOS (hvmloader + rombios) therefore the
Qemu acpi_piix4 implementation wo
On 08/13/2010 02:35 PM, Stefano Stabellini wrote:
We should limit XenStore interactions to strictly be device model
setup. Any management operations should be done through QMP. The main
reason to take this approach is to ensure that we don't end up with a
more powerful interface via xenstore ve
On Fri, Aug 13, 2010 at 8:25 PM, Artyom Tarasenko
wrote:
> 2010/7/30 Blue Swirl :
>> On Tue, Jul 27, 2010 at 8:10 PM, Artyom Tarasenko
>> wrote:
>>> 2010/7/27 Blue Swirl :
On Mon, Jul 26, 2010 at 10:23 PM, Artyom Tarasenko
wrote:
> 2010/7/26 Blue Swirl :
>> On Mon, Jul 26, 2010
2010/8/6 Artyom Tarasenko :
> 2010/8/2 Artyom Tarasenko :
>> Btw, it would be nice to get this patch applied for 0.13: it's a pure
>> fix, and it allows running the OBP v2.10 for LX and some older OBP
>> versions for SS-20 too.
>
> ping? Objections?
>
No feedback? Are 0.13 patches only accepted wi
2010/7/30 Blue Swirl :
> On Tue, Jul 27, 2010 at 8:10 PM, Artyom Tarasenko
> wrote:
>> 2010/7/27 Blue Swirl :
>>> On Mon, Jul 26, 2010 at 10:23 PM, Artyom Tarasenko
>>> wrote:
2010/7/26 Blue Swirl :
> On Mon, Jul 26, 2010 at 4:53 PM, Artyom Tarasenko
> wrote:
>> 2010/6/21 Artyom
Hi Stefano/Anthony,
On 08/12/2010 09:08 AM, Stefano Stabellini wrote:
Hi all,
this is the long awaited patch series to add xen device model support in
qemu; the main author is Anthony Perard.
Thanks for sending this out. Overall, the series looks pretty good. I
think there's just a coup
On Fri, 13 Aug 2010, Anthony Liguori wrote:
> On 08/12/2010 09:10 AM, stefano.stabell...@eu.citrix.com wrote:
> > From: Anthony PERARD
> >
> > Xen currently uses a different BIOS (hvmloader + rombios) therefore the
> > Qemu acpi_piix4 implementation wouldn't work correctly with Xen.
> > We plan on
On Thu, Aug 12, 2010 at 5:51 PM, Blue Swirl wrote:
> Add rules for printf-like functions, based on libvirt HACKING.
>
> Signed-off-by: Blue Swirl
> ---
> CODING_STYLE | 10 ++
> 1 files changed, 10 insertions(+), 0 deletions(-)
>
> diff --git a/CODING_STYLE b/CODING_STYLE
> index b230a
On Thu, Aug 12, 2010 at 5:50 PM, Blue Swirl wrote:
> Add C type rules from libvirt HACKING. Also include
> a description of special QEMU scalar types.
>
> Signed-off-by: Blue Swirl
> ---
> CODING_STYLE | 56
> 1 files changed, 56 inserti
On Fri, 13 Aug 2010, Anthony Liguori wrote:
> Hi Stefano/Anthony,
>
> On 08/12/2010 09:08 AM, Stefano Stabellini wrote:
> > Hi all,
> > this is the long awaited patch series to add xen device model support in
> > qemu; the main author is Anthony Perard.
> >
>
> Thanks for sending this out. O
On Thu, Aug 12, 2010 at 5:50 PM, Blue Swirl wrote:
> Add memory management rules, somewhat like libvirt HACKING.
>
> Signed-off-by: Blue Swirl
> ---
> CODING_STYLE | 8
> 1 files changed, 8 insertions(+), 0 deletions(-)
>
> diff --git a/CODING_STYLE b/CODING_STYLE
> index 3f10d72..08
On 08/12/2010 09:10 AM, stefano.stabell...@eu.citrix.com wrote:
From: Anthony PERARD
Xen currently uses a different BIOS (hvmloader + rombios) therefore the
Qemu acpi_piix4 implementation wouldn't work correctly with Xen.
We plan on fixing this properly but at the moment we are just adding a
new
On 08/12/2010 09:10 AM, stefano.stabell...@eu.citrix.com wrote:
From: Anthony PERARD
Handle shutdown and reset requests in helper.c.
Signed-off-by: Anthony PERARD
Signed-off-by: Stefano Stabellini
---
target-xen/helper.c | 17 +
1 files changed, 17 insertions(+), 0 deletion
Oops, just noticed that the double-precision ops ought to copy the
unmodified lower part of the GPR, too. Updated patch attached.
Obviously this changes the sin(-1.0) result after the patch, too:
$ qemu-ppc -cpu e500v2 sintest -1.0
-0.8414709848079
** Patch added: "Updated fix for unary SPE ops
Stefan Hajnoczi writes:
> 1. Writing the trace buffer is currently synchronous - fwrite(3) is
> used by the unlucky caller that fills up the trace buffer. Ideally
> traces should never block and write-out would be asynchronous. With a
> regular file I'm not sure how much of an issue this is to p
On 08/12/2010 09:09 AM, stefano.stabell...@eu.citrix.com wrote:
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_machine_fv.c | 25
target-xen/cpu.h |1 +
targe
On 08/12/2010 09:09 AM, stefano.stabell...@eu.citrix.com wrote:
From: Anthony PERARD
Introduce a mapcache to handle the 64bit address space of the guest
from a 32bit userland process (Qemu).
The mapcache maps chucks of guest memory on demand, unmaps them when
they are not needed anymore.
Signed
On 08/12/2010 09:09 AM, stefano.stabell...@eu.citrix.com wrote:
From: Anthony PERARD
Introduce functions to read and write the state of the VM in xenstore.
This basically creates a new management interface for QEMU via the xenstore.
Our management interface is QMP. If you want to maintai
On 08/12/2010 09:09 AM, stefano.stabell...@eu.citrix.com wrote:
From: Anthony PERARD
This patch adds a new Xen device model target to Qemu, called
target-xen.
A xen specific target is definitely the wrong approach.
I understand the desire to avoid the TCG code. We would like to
(optiona
** Patch added: "Fix for unary SPE ops vs. 6cbf4c8c"
https://bugs.launchpad.net/bugs/617528/+attachment/1488575/+files/qemu.diff
--
Incorrect translation of unary PPC/SPE instructions (efdneg etc.)
https://bugs.launchpad.net/bugs/617528
You received this bug notification because you are a mem
Public bug reported:
The translation for the following PPC/SPE (e500) instructions is wrong
in QEMU git 6cbf4c8c:
evfsabs, evfsnabs, evfsneg
efdabs, efdnabs, efdneg
efsabs, efsnabs, efsneg
As you can see from the provided patch, these ought to write their
result to the destination re
On Thu, Aug 12, 2010 at 6:56 PM, malc wrote:
> On Thu, 12 Aug 2010, Blue Swirl wrote:
>
>> Add a few rules, based loosely on libvirt HACKING.
>>
>> Blue Swirl (5):
>> CODING_STYLE: add preprocessor rules
>> CODING_STYLE: add C type rules
>> CODING_STYLE: add memory management rules
>> CODI
On Fri, Aug 13, 2010 at 1:10 PM, Stefano Stabellini
wrote:
> On Thu, 12 Aug 2010, Blue Swirl wrote:
>> On Thu, Aug 12, 2010 at 2:09 PM, wrote:
>> > From: Anthony PERARD
>> >
>> > This patch adds a new Xen device model target to Qemu, called
>> > target-xen.
>>
>> I don't understand why it would
On Fri, Aug 13, 2010 at 3:22 PM, Miguel Di Ciurcio Filho
wrote:
> On Thu, Aug 12, 2010 at 3:56 PM, malc wrote:
>>
>> While intentions of this are good, i believe this goes too far, i doubt
>> that the proposed additions are enforcable and have no doubts that they
>> will be widely ignored and at
On Fri, Aug 13, 2010 at 12:47 PM, Ian Jackson wrote:
> Blue Swirl writes ("[Xen-devel] Re: [Qemu-devel] [PATCH 03/15] xen: Add a new
> target to qemu: target-xen"):
>> I don't understand why it would be a target, QEMU calls CPU
>> architectures targets. Isn't it possible to have Xen for Sparc, PP
On Thu, Aug 12, 2010 at 6:47 PM, malc wrote:
> On Thu, 12 Aug 2010, Blue Swirl wrote:
>
>> Add preprocessor rules from libvirt HACKING.
>>
>> Signed-off-by: Blue Swirl
>> ---
>> CODING_STYLE | 13 +
>> 1 files changed, 13 insertions(+), 0 deletions(-)
>>
>> diff --git a/CODING_STYL
On Thu, Aug 12, 2010 at 3:56 PM, malc wrote:
>
> While intentions of this are good, i believe this goes too far, i doubt
> that the proposed additions are enforcable and have no doubts that they
> will be widely ignored and at the same time provide more grounds for
> whining. Furthermore the exist
On Thu, Aug 12, 2010 at 7:10 PM, Blue Swirl wrote:
> On Thu, Aug 12, 2010 at 10:36 AM, Stefan Hajnoczi
> wrote:
>> This patch series adds static tracing to QEMU. It can be used to instrument
>> QEMU code by means of lightweight logging called trace events.
>>
>> Prerna and I are now posting the
When the vhost log is resized, we want to sync up to
the size of the old log. With that end address in place,
ignore regions that start after then end rather than
hitting assert.
Signed-off-by: Alex Williamson
---
hw/vhost.c |7 ---
1 files changed, 4 insertions(+), 3 deletions(-)
dif
Am 23.03.2009 19:05, schrieb Vincent Sanders:
We have updated the patches for basic Samsung S3c2410 support to the
latest release. The patch also contain support for the Simtec bast
board as an example use of the core support. This patch can be found
on our
website http://www.simtec.co.uk/produ
On Thu, Aug 12, 2010 at 7:02 PM, Blue Swirl wrote:
> On Thu, Aug 12, 2010 at 10:36 AM, Stefan Hajnoczi
> wrote:
>> From: Prerna Saxena
>> +#if defined(CONFIG_SIMPLE_TRACE)
>> +static void do_info_trace(Monitor *mon)
>> +{
>> + st_print_trace((FILE *)mon, &monitor_fprintf);
>
> The cast is ugl
On Thu, 12 Aug 2010, Blue Swirl wrote:
> On Thu, Aug 12, 2010 at 2:09 PM, wrote:
> > From: Anthony PERARD
> >
> > This patch adds a new Xen device model target to Qemu, called
> > target-xen.
>
> I don't understand why it would be a target, QEMU calls CPU
> architectures targets. Isn't it possi
On Thu, 12 Aug 2010, Blue Swirl wrote:
> On Thu, Aug 12, 2010 at 2:09 PM, wrote:
> > From: Anthony PERARD
> >
> > This patch introduces a generic function registration mechanism for
> > set_irq and map_irq in piix3, so that the two calls can be
> > overridden with platform specific functions whe
On Thu, 12 Aug 2010, Blue Swirl wrote:
> > +static inline void read_physical(uint64_t addr, unsigned long size, void
> > *val)
> > +{
> > +return cpu_physical_memory_rw((target_phys_addr_t)addr, val, size, 0);
> > +}
> > +
> > +static inline void write_physical(uint64_t addr, unsigned long siz
On Thu, 12 Aug 2010, Blue Swirl wrote:
> On Thu, Aug 12, 2010 at 2:10 PM, wrote:
> > From: Anthony PERARD
> >
> > Xen currently uses a different BIOS (hvmloader + rombios) therefore the
> > Qemu acpi_piix4 implementation wouldn't work correctly with Xen.
> > We plan on fixing this properly but a
On Thu, 12 Aug 2010, Blue Swirl wrote:
> On Thu, Aug 12, 2010 at 2:09 PM, wrote:
> > From: Anthony PERARD
> >
> > Introduce a write config notifier in piix_pci, so that clients can be
> > notified every time a pci config write happens.
> > The patch also makes use of the notification mechanism i
Thanks for the very detailed review, all the comments make perfect
sense, we'll address them in the next version of the series.
On Thu, 12 Aug 2010, Blue Swirl wrote:
> On Thu, Aug 12, 2010 at 2:09 PM, wrote:
> > From: Anthony PERARD
> >
> > Introduce a new emulated PCI device, specific to full
Blue Swirl writes ("[Xen-devel] Re: [Qemu-devel] [PATCH 03/15] xen: Add a new
target to qemu: target-xen"):
> I don't understand why it would be a target, QEMU calls CPU
> architectures targets. Isn't it possible to have Xen for Sparc, PPC or
> ARM? It should really be just a machine, not copy&pas
45 matches
Mail list logo
