On 22/12/14 12:06, Denis V. Lunev wrote:
From: Simon Zolin
Creates a FIFO pair that can be used with existing file read/write
interfaces to communicate with processes spawned via the forthcoming
guest-file-exec interface.
Signed-off-by: Simon Zolin
Acked-by: Roman Kagan
Signed-off-by: Denis
Use the 'xl pci-attach $DomU $BDF' command to attach more then
one PCI devices to the guest, then detach the devices with
'xl pci-detach $DomU $BDF', after that, re-attach these PCI
devices again, an error message will be reported like following:
libxl: error: libxl_qmp.c:287:qmp_handle_error_resp
On 23/12/2014 23:12, Laszlo Ersek wrote:
> Apologies if this problem is known. After building qemu at ab0302ee:
>
> $ qemu-system-x86_64 -usb
>
> qemu-system-x86_64: util/qemu-option.c:387: qemu_opt_get_bool_helper:
> Assertion `opt->desc && opt->desc->type == QEMU_OPT_BOOL' failed.
Does this
Am 23.12.2014 um 23:47 schrieb Peter Maydell:
> On 23 December 2014 at 22:36, Stefan Weil wrote:
>> Am 23.12.2014 um 23:22 schrieb Peter Maydell:
>>> --- a/hw/ppc/spapr.c
>>> +++ b/hw/ppc/spapr.c
>>> @@ -1438,7 +1438,7 @@ static void ppc_spapr_init(MachineState *machine)
>>> }
>>> if (
On 2014/12/24 17:30, Paolo Bonzini wrote:
>
>
> On 23/12/2014 23:12, Laszlo Ersek wrote:
>> Apologies if this problem is known. After building qemu at ab0302ee:
>>
>> $ qemu-system-x86_64 -usb
>>
>> qemu-system-x86_64: util/qemu-option.c:387: qemu_opt_get_bool_helper:
>> Assertion `opt->desc &&
Signed-off-by: zhanghailiang
---
Hi,
This patch implements guest-network-get-interfaces command for
Windows.
This patch is RFC because the value of network 'prefix' length may be wrong
When there is an adapter with multiple IP which have different netmask.
The main reason is I get this value by
Public bug reported:
QEMU version: QEMU emulator version 2.2.50, Copyright (c) 2003-2008 Fabrice
Bellard
QEMU GIT version: ab0302ee764fd702465aef6d88612cdff4302809
Configure flags: ./configure --enable-kvm --prefix=/opt/qemu-devel
Linux version: Ubuntu 14.04.1 LTS
Kernel version: 3.13.0-43-generi
What does qemu say when aborting?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1405385
Title:
QEMU crashes when virtio network cards are used together with e1000
network cards
Status in QEMU:
Hm. I guess it says nothing, as else some write(2) should be seen by
strace. So it is like abort() not assert(). And we have about 800
abort() calls in the code. Oh well.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs
Today is the final day of QEMU Advent Calendar 2014:
http://www.qemu-advent-calendar.org/#day-24
A huge thanks to all the contributors who built fun and interesting
disk images for the advent calendar. It was very successful and a
great way to celebrate QEMU.
We drove 480 GB of web traffic, 41,0
On 12/24/14 10:30, Paolo Bonzini wrote:
>
>
> On 23/12/2014 23:12, Laszlo Ersek wrote:
>> Apologies if this problem is known. After building qemu at ab0302ee:
>>
>> $ qemu-system-x86_64 -usb
>>
>> qemu-system-x86_64: util/qemu-option.c:387: qemu_opt_get_bool_helper:
>> Assertion `opt->desc && op
Indeed, it does not say anything, it simply crashes. Besides the strace
log I created I can't find any other usefull information in other
logfiles.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/140538
Document that when using qemu_ram_resize for anything mapped into guest
address space, it's the job of the resize function to update guest
visible state.
Signed-off-by: Michael S. Tsirkin
---
Adding a comment at dgilbert's request.
This is a separate patch to avoid deferring merging the
code its
On 24/12/2014 12:43, Michael S. Tsirkin wrote:
> Document that when using qemu_ram_resize for anything mapped into guest
> address space, it's the job of the resize function to update guest
> visible state.
>
> Signed-off-by: Michael S. Tsirkin
> ---
>
> Adding a comment at dgilbert's request.
On 12/24/2014 12:12 AM, Laszlo Ersek wrote:
Apologies if this problem is known. After building qemu at ab0302ee:
The problem is not known.
Thanks for finding it and testing it!
Marcel
$ qemu-system-x86_64 -usb
qemu-system-x86_64: util/qemu-option.c:387: qemu_opt_get_bool_helper: Assertion `o
The following changes since commit d86fb03469e016af4e54f04efccbc20a8afa3e19:
Merge remote-tracking branch 'remotes/spice/tags/pull-spice-20141216-1' into
staging (2014-12-16 16:52:42 +)
are available in the git repository at:
git://git.kernel.org/pub/scm/virt/kvm/mst/qemu.git tags/for_u
Add API to allocate resizeable RAM MR.
This looks just like regular RAM generally, but
has a special property that only a portion of it
(used_length) is actually used, and migrated.
This used_length size can change across reboots.
Follow up patches will change used_length for such blocks at migr
Add API to change MR size.
Will be used internally for RAM resize.
Signed-off-by: Michael S. Tsirkin
---
include/exec/memory.h | 10 ++
memory.c | 16
2 files changed, 26 insertions(+)
diff --git a/include/exec/memory.h b/include/exec/memory.h
index f64ab5e
Use resizeable ram API so we can painlessly extend ROMs in the
future. Note: migration is not affected, as we are
not actually changing the used length for RAM, which
is the part that's migrated.
Use this in acpi: reserve x16 more RAM space.
Signed-off-by: Michael S. Tsirkin
---
hw/lm32/lm32_h
simple wrapper so callers don't need to know about
dirty bitmap clients.
Signed-off-by: Michael S. Tsirkin
---
include/exec/ram_addr.h | 8
1 file changed, 8 insertions(+)
diff --git a/include/exec/ram_addr.h b/include/exec/ram_addr.h
index 8fc75cd..18ec092 100644
--- a/include/exec/ra
Make cpu_physical_memory_set/clear_dirty_range
behave symmetrically.
To clear range for a given client type only, add
cpu_physical_memory_clear_dirty_range_type.
Signed-off-by: Michael S. Tsirkin
---
include/exec/ram_addr.h | 15 ---
exec.c | 2 +-
2 files changed,
This patch allows us to distinguish between two
length values for each block:
max_length - length of memory block that was allocated
used_length - length of block used by QEMU/guest
Currently, we set used_length - max_length, unconditionally.
Follow-up patches allow used_length <= max_leng
If block used_length does not match, try to resize it.
Signed-off-by: Michael S. Tsirkin
---
arch_init.c | 13 -
1 file changed, 8 insertions(+), 5 deletions(-)
diff --git a/arch_init.c b/arch_init.c
index 106f46e..cfedbf0 100644
--- a/arch_init.c
+++ b/arch_init.c
@@ -1086,11 +1086
On 24/12/2014 12:03, Laszlo Ersek wrote:
> On 12/24/14 10:30, Paolo Bonzini wrote:
>>
>>
>> On 23/12/2014 23:12, Laszlo Ersek wrote:
>>> Apologies if this problem is known. After building qemu at ab0302ee:
>>>
>>> $ qemu-system-x86_64 -usb
>>>
>>> qemu-system-x86_64: util/qemu-option.c:387: qemu_
Add API to allocate "resizeable" RAM.
This looks just like regular RAM generally, but
has a special property that only a portion of it
(used_length) is actually used, and migrated.
This used_length size can change across reboots.
Follow up patches will change used_length for such blocks at migrat
On Wed, Dec 24, 2014 at 12:45:47PM +0100, Paolo Bonzini wrote:
>
>
> On 24/12/2014 12:43, Michael S. Tsirkin wrote:
> > Document that when using qemu_ram_resize for anything mapped into guest
> > address space, it's the job of the resize function to update guest
> > visible state.
> >
> > Signed
On 24/12/2014 13:21, Michael S. Tsirkin wrote:
> > Wait, I thought the agreement was to first merge Igor's patches to
> > generate the SSDT from C code, and then see if this was still necessary?
>
> To first *review* Igor's patches.
>
> I can't merge more ACPI code until I know how we are
> han
On 24/12/2014 12:51, Michael S. Tsirkin wrote:
> The following changes since commit d86fb03469e016af4e54f04efccbc20a8afa3e19:
>
> Merge remote-tracking branch 'remotes/spice/tags/pull-spice-20141216-1'
> into staging (2014-12-16 16:52:42 +)
>
> are available in the git repository at:
>
>
On 24 December 2014 at 12:25, Paolo Bonzini wrote:
> On 24/12/2014 12:51, Michael S. Tsirkin wrote:
>>
>> pc: resizeable ROM blocks
>>
>> This makes ROM blocks resizeable. This infrastructure is required for other
>> functionality w
On Wed, Dec 24, 2014 at 01:25:16PM +0100, Paolo Bonzini wrote:
> On 24/12/2014 12:51, Michael S. Tsirkin wrote:
> > The following changes since commit d86fb03469e016af4e54f04efccbc20a8afa3e19:
> >
> > Merge remote-tracking branch 'remotes/spice/tags/pull-spice-20141216-1'
> > into staging (2014
This part of the ACPI tables can vary in size across machine types, but
does not depend on the command-line. It is an SSDT just because it is
the same for i440fx and Q35, and making it an SSDT made the code a bit
simpler. However, it also complicates backwards compatibility, so
merge it with the
Right now, the SSDT/DSDT is split in three parts:
- code that doesn't need patching goes in the DSDT. Furthermore,
code in this category that is shared between PIIX4 and Q35 is
handled via #include. There was one exception, the SMC._STA
method is patched and is in the DSDT.
- shared code
The new algorithm introduced by the previous patch lets us make tables
smaller and avoid migration bugs due to large tables.
Use it for 2.3+ machine types by tweaking the default fixed_table_align
and acpi_table_align values. At the same time, preserve backwards-compatible
logic for pc-i440fx-2.2
Signed-off-by: Paolo Bonzini
---
hw/i386/acpi-build.c | 7 ++-
hw/i386/acpi-dsdt-common.dsl | 14 +++---
hw/i386/acpi-dsdt-isa.dsl| 6 +-
hw/i386/acpi-dsdt.dsl| 10 ++
hw/i386/q35-acpi-dsdt.dsl| 9 ++---
5 files changed, 22 insertions(+), 24
Signed-off-by: Paolo Bonzini
---
hw/i386/acpi-dsdt-common.dsl | 345 +-
hw/i386/acpi-dsdt-dbug.dsl| 41 -
hw/i386/acpi-dsdt-hpet.dsl| 48 --
hw/i386/acpi-dsdt-isa.dsl | 132 ---
hw/i386/acpi-dsdt-mem-hotplug.ds
Add padding after the DSDT. Tables that vary depending on the
command-line arguments will have to be byte-equivalent across QEMU
versions >= 2.2, while fixed tables (including the DSDT) can be
changed freely.
Signed-off-by: Paolo Bonzini
---
hw/i386/acpi-build.c | 19 +++
hw/i38
Signed-off-by: Paolo Bonzini
---
hw/i386/Makefile.objs | 2 +-
hw/i386/acpi-build.c | 38 +++---
hw/i386/{ssdt-misc.dsl => acpi-dsdt-common.dsl}| 8 ++---
...ex.generated => acpi-dsdt-common.hex.generated} | 4 +--
Now that the alignment is parameterized, we can share the call to
acpi_align_size between all three (1.7-2.0/2.1/2.2+) sizing algorithms.
Also, with the new rule that SSDT cannot change except with
machine-type compat code, the magic 97 constant for a CPU's
AML size is not anymore "legacy", so ren
On 24/12/2014 14:12, Paolo Bonzini wrote:
> Right now, the SSDT/DSDT is split in three parts:
>
> - code that doesn't need patching goes in the DSDT. Furthermore,
> code in this category that is shared between PIIX4 and Q35 is
> handled via #include. There was one exception, the SMC._STA
>
On Wed, Dec 24, 2014 at 02:12:39PM +0100, Paolo Bonzini wrote:
> Right now, the SSDT/DSDT is split in three parts:
>
> - code that doesn't need patching goes in the DSDT. Furthermore,
> code in this category that is shared between PIIX4 and Q35 is
> handled via #include. There was one except
On Fri, Dec 19, 2014 at 11:27:57AM -0200, Eduardo Habkost wrote:
> On Thu, Dec 18, 2014 at 09:24:11AM +, Dr. David Alan Gilbert wrote:
> > * David Gibson (da...@gibson.dropbear.id.au) wrote:
> > > On Fri, Dec 12, 2014 at 11:13:41AM +, Dr. David Alan Gilbert (git)
> > > wrote:
> > > > From:
On 24/12/2014 15:19, Michael S. Tsirkin wrote:
> So I'll have to review in detail, overall the patches
> do look pretty clean.
Q35 is broken though (GArray resizing messes up the tables, fixed
locally and caught by bios-tables-test even before trying it out!). I
hope to send out the fixed versi
At Mon, 22 Dec 2014 17:41:33 +0800,
$B=y>.$AAz(B wrote:
>
> [1 ]
> hi,all,
> when i use `qemu-img snapshot -c test-s sheepdog:test` to create a
> snapshot of sheepdog vdi,the snapshot's lock not be released.
>
> root@hty-compute1:~/qemu# ./qemu-img create sheepdog:test 1G
> Formatting 's
Can you try this again on a more recent QEMU please; a lot has happened
in the last 5 years.
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/491345
This part of the ACPI tables can vary in size across machine types, but
does not depend on the command-line. It is an SSDT just because it is
the same for i440fx and Q35, and making it an SSDT made the code a bit
simpler. However, it also complicates backwards compatibility, so
merge it with the
Right now, the SSDT/DSDT is split in three parts:
- code that doesn't need patching goes in the DSDT. Furthermore,
code in this category that is shared between PIIX4 and Q35 is
handled via #include. There was one exception, the SMC._STA
method is patched and is in the DSDT.
- shared code
Now that the alignment is parameterized, we can share the call to
acpi_align_size between all three (1.7-2.0/2.1/2.2+) sizing algorithms.
Also, with the new rule that SSDT cannot change except with
machine-type compat code, the magic 97 constant for a CPU's
AML size is not anymore "legacy", so ren
Signed-off-by: Paolo Bonzini
---
hw/i386/acpi-dsdt-common.dsl | 345 +-
hw/i386/acpi-dsdt-dbug.dsl| 41 -
hw/i386/acpi-dsdt-hpet.dsl| 48 --
hw/i386/acpi-dsdt-isa.dsl | 132 ---
hw/i386/acpi-dsdt-mem-hotplug.ds
All the changes to generated files are in the header, so there is
no need to rebuild test data.
Signed-off-by: Paolo Bonzini
---
hw/i386/Makefile.objs | 2 +-
hw/i386/acpi-build.c | 36 +++---
hw/i386/{ssdt-misc.dsl => a
The new algorithm introduced by the previous patch lets us make tables
smaller and avoid migration bugs due to large tables.
Use it for 2.3+ machine types by tweaking the default fixed_table_align
and acpi_table_align values. At the same time, preserve backwards-compatible
logic for pc-i440fx-2.2
Signed-off-by: Paolo Bonzini
---
hw/i386/acpi-build.c | 12 +-
hw/i386/acpi-dsdt-common.dsl | 14 +-
hw/i386/acpi-dsdt-common.hex.generated | 1578 +++-
hw/i386/acpi-dsdt-isa.dsl |6 +-
hw/i386/acpi-dsdt.dsl | 10 +-
Add padding after the DSDT. Tables that vary depending on the
command-line arguments will have to be byte-equivalent across QEMU
versions >= 2.2, while fixed tables (including the DSDT) can be
changed freely.
Signed-off-by: Paolo Bonzini
---
hw/i386/acpi-build.c | 19 +++
hw/i38
On Wed, Dec 24, 2014 at 03:43:41PM +0100, Paolo Bonzini wrote:
>
>
> On 24/12/2014 15:19, Michael S. Tsirkin wrote:
> > So I'll have to review in detail, overall the patches
> > do look pretty clean.
>
> Q35 is broken though (GArray resizing messes up the tables, fixed
> locally and caught by bi
On Tue, Dec 23, 2014 at 11:45:00PM +, Peter Maydell wrote:
> On 23 December 2014 at 23:29, Rabin Vincent wrote:
> > +static size_t round4(size_t size)
> > +{
> > +return ((size + 3) / 4) * 4;
> > +}
>
> Is this different from ROUND_UP(size, 4) ?
> If we can use the standard macro from the
On 24 December 2014 at 16:54, Rabin Vincent wrote:
> On Tue, Dec 23, 2014 at 11:45:00PM +, Peter Maydell wrote:
>> Assuming the answer is "still 64 bit core dump" you need
>> to do something here to sync the 32 bit TCG state into the
>> 64 bit xregs array. (KVM can take care of itself.)
>
> I
Hi Peter,
Thank you very much for your help, I really appreciate it. I've tested
both your patch and your workaround to make ls work (I've created a xfs
partition to put my image) and everything works greatly.
Merry Xmas.
Michel
--
You received this bug notification because you are a member of
a backtrace from a coredump or gdb would be better; it'll tell us the line the
abort is on and the state at that point.
Run it under gdb and do
bt full
and paste the result.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://b
Hi,
When IO error happens in physical device, qemu block layer supports error
reporting, error ignoring and error stoping(for example, virtio-blk). Can we
have any way to resend the error IO?
thanks
--
Bin Wu
On Thu, 12/25 09:57, Bin Wu wrote:
> Hi,
>
> When IO error happens in physical device, qemu block layer supports error
> reporting, error ignoring and error stoping(for example, virtio-blk). Can we
> have any way to resend the error IO?
With error stop, the request is retried after resume.
Fam
On Tue, Dec 23, 2014 at 03:22:06PM +1100, David Gibson wrote:
>On Mon, Dec 15, 2014 at 11:15:07AM +1100, Gavin Shan wrote:
>> The emulation for EEH RTAS requests from guest isn't covered
>> by QEMU yet and the patch implements them.
>>
>> The patch defines constants used by EEH RTAS calls and adds
On Tue, Dec 23, 2014 at 03:24:58PM +1100, David Gibson wrote:
>On Mon, Dec 15, 2014 at 11:15:06AM +1100, Gavin Shan wrote:
>> From: Alexey Kardashevskiy
>>
>> This makes find_phb()/find_dev() public and changed its names
>> to spapr_pci_find_phb()/spapr_pci_find_dev() as they are going to
>> be u
On 2014/12/25 10:42, Fam Zheng wrote:
> On Thu, 12/25 09:57, Bin Wu wrote:
>> Hi,
>>
>> When IO error happens in physical device, qemu block layer supports error
>> reporting, error ignoring and error stoping(for example, virtio-blk). Can we
>> have any way to resend the error IO?
>
> With error s
22.12.2014 20:47, Peter Maydell wrote:
> The m68k signal frame setup code which writes the signal return
> trampoline code to the stack was assuming that a 'long' was 32 bits;
> on 64 bit systems this meant we would end up writing the 32 bit
> (2 insn) trampoline sequence to retaddr+4,retaddr+6 ins
These patches eliminate data writes completely on Linux if fallocate
FALLOC_FL_ZERO_RANGE or FALLOC_FL_PUNCH_HOLE are supported on
underlying filesystem. This should seriously increase performance in
some cases.
Signed-off-by: Denis V. Lunev
CC: Kevin Wolf
CC: Stefan Hajnoczi
This sequence works efficiently if FALLOC_FL_ZERO_RANGE is not supported.
The idea is that FALLOC_FL_PUNCH_HOLE could not increase file size
but it cleans already allocated blocks inside the file. If we have to
create something new, simple fallocate will do the job.
This should increase performanc
this efficiently writes zeroes in the middle of the file on Linux
systems if the kernel is capable enough.
Signed-off-by: Denis V. Lunev
CC: Kevin Wolf
CC: Stefan Hajnoczi
---
block/raw-posix.c | 11 +++
configure | 19 +++
2 files changed, 30 insertions(+)
dif
From: Simon Zolin
If write operation fails on a pipe whose reading end is closed, qemu-ga
won't be terminated, but instead write() will fail with error EPIPE.
execve() inherits signals that are ignored, so reset SIGPIPE to its default
handler before calling execve() in a forked process.
Signed-
On Thu, 12/25 11:46, Bin Wu wrote:
> On 2014/12/25 10:42, Fam Zheng wrote:
> > On Thu, 12/25 09:57, Bin Wu wrote:
> >> Hi,
> >>
> >> When IO error happens in physical device, qemu block layer supports error
> >> reporting, error ignoring and error stoping(for example, virtio-blk). Can
> >> we
> >>
68 matches
Mail list logo
