On Wed, Oct 23, 2013 at 03:51:37PM +0900, MORITA Kazutaka wrote:
> At Wed, 23 Oct 2013 15:19:47 +0900,
> MORITA Kazutaka wrote:
> >
> > > +
> > > +Sheepdog
> > > +M: MORITA Kazutaka
> > > +S: Supported
> > > +F: block/sheepdog.c
> >
> > Acked-by: MORITA Kazutaka
>
> Is it okay to add Liu Yuan
On 23 October 2013 07:28, Giridhar Maruthy wrote:
> I did compare with kvmtool and found that the below fix boots SMP in
> mach-virt with qemu.
>
> diff --git a/target-arm/kvm.c b/target-arm/kvm.c
> index b92e00d..28b8e2b 100644
> --- a/target-arm/kvm.c
> +++ b/target-arm/kvm.c
> @@ -82,6 +82,7 @@
At Wed, 16 Oct 2013 15:38:37 +0800,
Liu Yuan wrote:
>
> 'copies' is actually uint8_t since day one, but request headers and some
> helper
> functions parameterize it as uint32_t for unknown reasons and effectively
> reserve 24 bytes for possible future use. This patch explicitly set the
> correc
Il 20/10/2013 15:56, Samuel Thibault ha scritto:
> +#define rand_a_b(a, b)\
> +(rand()%(int)(b-a)+a)
> +#define NDP_Interval rand_a_b(NDP_MinRtrAdvInterval, NDP_MaxRtrAdvInterval)
> +
> +static void ra_timer_handler(void *opaque)
> +{
> +timer_mod(ra_timer, qemu_clock_get_s(QEMU_CLOCK_VIRTU
Il 22/10/2013 09:24, Peter Maydell ha scritto:
>
> Ken -- any chance you could test git master? I think it would
> be more interesting to make sure that 1.7 works with Make 4.0:
> I don't know if anybody will care enough to backport this patch
> to 1.6.x.
Cc: qemu-sta...@nongnu.org
Mike Roth now
Take another think, I think I may use past tense through the doc,
but with more carefully meaning, such as:
the system has enter powerdown state.
If you agree with the tense, I'd like sent the reformed doc
in the following, before respin.
Indeed, which is why separating the docs from the
Hi,
My newly built qemu/win32 binary (v1.6.1) crashes in qemu-system-i386 and
qemu-system-x86_64 when
booting from an install CD.
C:\Program Files\qemu>qemu-system-x86_64 -boot d -vnc 0.0.0.0:20 -cdrom
NetBSD-6.1.2-amd64.iso
Assertion failed: qemu_in_coroutine(), file qemu-corou
v2:
- merge the reserved bits
This patch set makes use of copy_policy in struct SheepdogInode in order to
support recently introduced erasure coding volume in sheepdog.
Thanks
Yuan
Liu Yuan (2):
sheepdog: explicitly set copies as type uint8_t
sheepdog: pass copy_policy in the request
bloc
'copies' is actually uint8_t since day one, but request headers and some helper
functions parameterize it as uint32_t for unknown reasons and effectively
reserve 24 bytes for possible future use. This patch explicitly set the correct
for copies and reserve the left bytes.
This is a preparation pat
Currently copy_policy isn't used. Recent sheepdog supports erasure coding, which
make use of copy_policy internally, but require client explicitly passing
copy_policy from base inode to newly creately inode for snapshot related
operations.
If connected sheep daemon doesn't utilize copy_policy, pas
Il 23/10/2013 08:39, Michael W. Bombardieri ha scritto:
> Hi,
>
> My newly built qemu/win32 binary (v1.6.1) crashes in qemu-system-i386 and
> qemu-system-x86_64 when
> booting from an install CD.
>
> C:\Program Files\qemu>qemu-system-x86_64 -boot d -vnc 0.0.0.0:20 -cdrom
> NetBSD-6.1.2-am
On 17 October 2013 14:54, wrote:
> From: Markus Armbruster
>
> Many PCI host bridges consist of a sysbus device and a PCI device.
> You need both for the thing to work. Arguably, these bridges should
> be modelled as a single, composite devices instead of pairs of
> seemingly independent device
On 17 October 2013 14:54, wrote:
> From: Markus Armbruster
>
>
> Signed-off-by: Markus Armbruster
Reviewed-by: Peter Maydell
-- PMM
On 17 October 2013 14:54, wrote:
> From: Markus Armbruster
>
>
> Signed-off-by: Markus Armbruster
Reviewed-by: Peter Maydell
-- PMM
On 17 October 2013 14:54, wrote:
> From: Markus Armbruster
>
> An ICH9 southbridge contains several PCI devices, some of them with
> multiple functions. We model each function as a separate qdev. Two
> of them need some special wiring set up in pc_q35_init() to work: the
> LPC controller at 00
On 17 October 2013 14:54, wrote:
> From: Markus Armbruster
>
> A VT82C686B southbridge has multiple functions. We model each
> function as a separate qdev. One of them need some special wiring set
> up in mips_fulong2e_init() to work: the ISA bridge at 05.0.
>
> The IDE controller at 05.1 (via
On 17 October 2013 14:55, wrote:
> From: Markus Armbruster
>
> Drop it when there's no obvious reason why device_add could not work.
> Else keep and document why.
>
> * isa-fdc, port92, i8042, m48t59_isa, mc146818rtc, isa-pit, kvm-pit:
> drop (from the last two by dropping it from their abstra
On 17 October 2013 14:54, wrote:
> From: Markus Armbruster
>
> In an ideal world, machines can be built by wiring devices together
> with configuration, not code. Unfortunately, that's not the world we
> live in right now. We still have quite a few devices that need to be
> wired up by code.
On 17 October 2013 14:54, wrote:
> From: Markus Armbruster
>
> device_add plugs devices into suitable bus. For "real" buses, that
> actually connects the device. For sysbus, the connections need to be
> made separately, and device_add can't do that. The device would be
> left unconncected, an
Since more integer parameters would come in the future, so how about
set_migrate_parameter similar to set_migrate_capability?
It sets integer value, while set_migrate_capability sets bool value.
thanks,
On Mon, Oct 21, 2013 at 01:14:21AM +,
mrhi...@linux.vnet.ibm.com wrote:
> From: "Michael
On Tue, 24 Sep 2013 08:32:10 +0400
Antony Pavlov wrote:
ping-ping
> On Fri, 13 Sep 2013 11:33:24 +0400
> Antony Pavlov wrote:
>
> ping
>
> > Changes since v2:
> > * commit messages: drop ALL 'Reviewed-by' tags.
> > Drop Aurelien Jarno's tag because the patchseries
> > was completely rework
On Mon, Oct 21, 2013 at 02:26:15PM +0100, Stefan Hajnoczi wrote:
> There are a number of contributors who maintain block drivers (image
> formats and protocols). They should be listed in the MAINTAINERS file
> so that get_maintainer.pl lists them.
>
> Note that commits are still merged through Ke
This patch adds a python tool to the scripts directory that can read
a dumped migration stream which contains the debug_migration device
and construct a human readable JSON stream out of it.
It's very simple to use:
$ qemu-system-x86_64 -device debug_migration
(qemu) migrate "exec:cat > mig
This patch set adds support for a simple migration debugging method.
It adds a device that exports all metadata required to read a migration
stream from an external program as part of the migration stream. The
external program then does not need to have any knowledge of device internals
of the tar
We need to be able to access savevm handlers from code that lives
outside of savevm.c. Extract its struct definitions and declaration
into a separate header file.
Signed-off-by: Alexander Graf
---
include/qemu/savevm.h | 28
savevm.c | 24 ++-
This patch adds a pseudo device whose sole purpose is to encapsulate
a machine readable layout description of the vmstate stream layout inside
of the stream.
With this device enabled in the system while a migration is happening, we
have to chance to decypher the contents of the stream from an exte
https://groups.google.com/forum/#!forum/fosdem14-virt-and-iaas-devroom
Call for Participation
The scope for this devroom is open source, openly-developed projects in
the areas of virtualisation and IaaS type clouds, ranging from low level
to data center, up to cloud management platforms and cl
Public bug reported:
execute " qemu-system-x86_64-enable-kvm -machine accel=kvm:tcg -m 1G
-drive file=/dev/sda --full-screen -spice addr=127.0.0.1,port=5900
,disable-ticketing -vga qxl " on shell will get segment fault after
a few seconds if I don't connect to it with spicec client
i
/usr/local/bin/qemu-system-x86_64 -enable-kvm -machine accel=kvm:tcg -m
1G -drive file=/dev/sda -vga qxl
will give same error
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1243639
Title:
qemu-1
a funny thing:
if I change the "-drive file=/dev/sda" to "-drive file=/dev/sdb"
, it will not run into "segment fault".
The different between sda & sdb is as following:
linux is installed on /dev/sda and/dev/sdb is another physical
hard driver.
> Live cloning is a disaster waiting to happen if not done in a very
> carefully controlled environment (I could maybe see it useful across two
> private networks for forensic analysis or running "what-if" scenarios,
> but never for provisioning enterprise-quality public-facing servers).
> Remember
On 10/22/2013 11:00 AM, Anthony Liguori wrote:
On Tue, Oct 22, 2013 at 12:21 PM, Eduardo Otubo
wrote:
Inverting the way sandbox handles arguments, making possible to have no
argument and still have '-sandbox on' enabled.
Signed-off-by: Eduardo Otubo
---
The option '-sandbox on' is now used
Am 27.09.2013 09:05, schrieb Alexey Kardashevskiy:
> IBM POWERPC processors encode PVR as a CPU family in higher 16 bits and
> a CPU version in lower 16 bits. Since there is no significant change
> in behavior between versions, there is no point to add every single CPU
> version in QEMU's CPU list.
On Mon, Oct 14, 2013 at 03:24:43PM +0100, Peter Maydell wrote:
> On 26 September 2013 22:03, Christoffer Dall
> wrote:
> > For some reason only edge-triggered or enabled level-triggered
> > interrupts would set the pending state of a raised IRQ. This is not in
> > compliance with the specs, which
If software writes to the ISPENDR and sets the pending state of a
level-triggered interrupt, the falling edge of the hardware input must
not clear the pending state. Conversely, if software writes to the
ICPENDR, the pending state of a level-triggered interrupt should only be
cleared if the hardwa
On Mon, Oct 14, 2013 at 05:33:38PM +0100, Peter Maydell wrote:
> On 14 October 2013 16:36, Peter Maydell wrote:
[...]
>
> Tangentially, I notice that we don't correctly handle
> the PENDING bit for level triggered interrupts, since
> we do:
>
> /* Clear pending flags for both level and edg
On 2013-10-21 22:36, Eric Blake wrote:
On 10/20/2013 07:28 PM, Max Reitz wrote:
Since df2a6f29a5, bdrv_co_do_writev increases the total_sectors value of
a growable block devices on writes after the current end. This leads to
the virtual disk apparently growing in qcow2_save_vmstate, which in tur
On 2013-10-21 22:37, Eric Blake wrote:
On 10/20/2013 08:52 PM, Max Reitz wrote:
Saving the VM state is done using bdrv_pwrite. This function may perform
a read-modify-write, which in this case results in data being read from
beyond the end of the virtual disk. Since we are actually trying to
acc
Add a test for saving a VM state from a qcow2 image and loading it back
(with having restarted qemu in between); this should work without any
problems.
Signed-off-by: Max Reitz
---
Follow-up to (depends on):
- qcow2: Restore total_sectors value in save_vmstate
- qcow2: Unset zero_beyond_eof in
On 2013-10-21 22:37, Eric Blake wrote:
On 10/20/2013 08:52 PM, Max Reitz wrote:
Saving the VM state is done using bdrv_pwrite. This function may perform
a read-modify-write, which in this case results in data being read from
beyond the end of the virtual disk. Since we are actually trying to
acc
Opening the qcow2 image with BDRV_O_NO_FLUSH prevents any flushes during
the image creation. This means that the image has not yet been flushed
to disk when qemu-img create exits. This flush is delayed until the next
operation on the image involving opening it without BDRV_O_NO_FLUSH and
closing (o
Am 23.10.2013 11:00, schrieb Paolo Bonzini:
> Il 23/10/2013 08:39, Michael W. Bombardieri ha scritto:
>> Hi,
>>
>> My newly built qemu/win32 binary (v1.6.1) crashes in qemu-system-i386 and
>> qemu-system-x86_64 when
>> booting from an install CD.
>>
>> C:\Program Files\qemu>qemu-system-x86_64
[PATCH v6 1/5] hw/arm: add very initial support for Canon DIGIC SoC
[PATCH v6 2/5] hw/arm/digic: prepare DIGIC-based boards support
[PATCH v6 3/5] hw/arm/digic: add timer support
[PATCH v6 4/5] hw/arm/digic: add UART support
[PATCH v6 5/5] hw/arm/digic: add NOR ROM support
Changes since v5:
1. re
DIGIC is Canon Inc.'s name for a family of SoC
for digital cameras and camcorders.
There is no publicly available specification for
DIGIC chips. All information about DIGIC chip
internals is based on reverse engineering efforts
made by CHDK (http://chdk.wikia.com) and
Magic Lantern (http://www.mag
Also this patch adds initial support for Canon
PowerShot A1100 IS compact camera.
Signed-off-by: Antony Pavlov
---
hw/arm/Makefile.objs | 1 +
hw/arm/digic_boards.c | 88 +++
2 files changed, 89 insertions(+)
create mode 100644 hw/arm/digic_boar
Signed-off-by: Antony Pavlov
---
hw/arm/digic_boards.c | 71 +++
1 file changed, 71 insertions(+)
diff --git a/hw/arm/digic_boards.c b/hw/arm/digic_boards.c
index 77cfc81..bf6e015 100644
--- a/hw/arm/digic_boards.c
+++ b/hw/arm/digic_boards.c
@@ -2
Signed-off-by: Antony Pavlov
---
hw/arm/digic.c | 28 ++
hw/timer/Makefile.objs | 1 +
hw/timer/digic-timer.c | 140 +
hw/timer/digic-timer.h | 36 +
include/hw/arm/digic.h | 6 +++
5 files changed, 211 insertions(+
Signed-off-by: Antony Pavlov
Reviewed-by: Peter Maydell
---
hw/arm/digic.c | 16
hw/char/Makefile.objs | 1 +
hw/char/digic-uart.c | 195 +
hw/char/digic-uart.h | 45
include/hw/arm/digic.h | 2 +
5 files change
Paolo Bonzini, le Wed 23 Oct 2013 08:51:21 +0100, a écrit :
> > +void icmp6_init(Slirp *slirp)
> > +{
> > +srand(time(NULL));
> > +ra_timer = timer_new_s(QEMU_CLOCK_VIRTUAL, ra_timer_handler, slirp);
> > +timer_mod(ra_timer, qemu_clock_get_s(QEMU_CLOCK_VIRTUAL) +
> > NDP_Interval);
> >
sorry to mistake
The truth is that
t will NOT run into segment fault with /dev/sda but without -vga qxl
The qemu & the Host linux OS is iinstalled on /dev/sda
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bug
On 16 October 2013 10:36, Stacey Son wrote:
> Update FreeBSD system call numbers in freebsd/syscall_nr.h.
>
> Signed-off-by: Stacey Son
Reviewed-by: Ed Maste
It will run into segment fault with /dev/sda but without -vga qxl
The qemu & the Host linux OS is iinstalled on /dev/sda
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1243639
Title:
q
Hi All,
I know it's been a long time since this thread. But qemu 1.7 is
releasing, do you have any consensus on this?
Thanks.
Hi all,
I read the slides "An Update Overview of the QEMU Storage Stack", which
indicate that if caching mode=none, the host page cache is off and guest disk
write cache is on. My question is where the implementation is inside the qemu.
How to control the io to a virtual disk image( a raw disk
Hi,
I encount a qemu crash when the vnc client disconnection, and I got the next
log:
qemu: qemu_mutex_lock: Invalid argument
and the backtrace listed:
Core was generated by
`/mnt/sdd/gonglei/kvm/qemu-unstable/x86_64-softmmu/qemu-system-x86_64 -name
suse'.
Program terminated with signal 6, A
On Thu, Oct 24, 2013 at 11:36 AM, Yaodong Yang wrote:
> Hi all,
>
> I read the slides "An Update Overview of the QEMU Storage Stack", which
> indicate that if caching mode=none, the host page cache is off and guest
> disk write cache is on. My question is where the implementation is inside
> the q
currently it is not possible to distinguish by exitcode if there
has been an error or if bdrv_check is not supported by the image
format. Change the exitcode from 1 to 63 for the latter case.
Signed-off-by: Peter Lieven
---
v1->v2: As Eric suggested changed the exitcode from 255 to 63.
qemu-img
57 matches
Mail list logo
