On 2009/10/25 17:51, Dietmar Maurer wrote:
Do you support multiple guests accessing the same image?
A VM image can be attached to any VMs but one VM at a time; multiple
running VMs cannot access to the same VM image.
I guess this is a problem when you want to do live migrations?
Yes, because
Rationale: The following code is difficult to read, but allowed by the
current coding style.
if (a == 5) printf("a was 5.\n");
else if (a == 6) printf("a was 6.\n");
else printf("a was something else entirely.\n");
Signed-off-by: Aurelien Jarno
---
CODING_STYLE | 10 +-
1
On Oct 24, 2009, at 18:09, ext Filip Navara wrote:
> The support for multiple keyboard devices is essential for emulating
> embedded boards where multiple input devices are present (eg. keypad
> and rotary encoder) which are implemented using separate QEMU devices.
Nice to see someone else ne
From:Qun yi m9807...@mail.ntust.edu.tw
I want use qemu-system-arm to emulator 2 arm's cpus
but when i key the qemu-system-arm -smp 2 (i have use kernel and initrd,this is
simple)
It give me a message "Number of smp cpus requested 2, exceed max cpus"
which files i must insertions or deletions to
Dietmar Maurer wrote:
Also, on _loaded_ systems, I noticed creating/removing logical volumes
can take really long (several minutes); where allocating a file of a
given size would just take a fraction of that.
Allocating a file takes much longer, unless you use a 'sparse' file.
If you mean "a
On (Sat) Oct 24 2009 [12:36:54], Jan Kiszka wrote:
> Amit Shah wrote:
> > The OPENED event gets sent also when qemu resets its state initially.
> > The consumers of the event aren't interested in receiving this event
> > on reset.
>
> The monitor was. Now its initial prompt on activation is broken
Jan-Simon Möller wrote:
> We encontered problems with the low default value for the stacksize in
> usermode (ok, whats "low").
> For environments like scratchbox, its hard to use "-s" as qemu is called by
> binfmt mechanism.
> The attached patch makes this configurable at compile-time.
Note, th
"Jan-Simon Möller" wrote:
> @@ -2481,6 +2485,16 @@ if test "$target_user_only" = "yes" -a "$static" =
> "no" -a \
>ldflags="-pie $ldflags"
> fi
>
> +# change default stacksize in usermode
> +#
> +if test "$target_user_only" = "yes" -a "$user_mode_stacksize" != "" ; then
> + cflags="-DUSER_MO
On Sat, Oct 24, 2009 at 03:18:59PM +0300, juha.riihim...@nokia.com wrote:
> From: Juha Riihimäki
>
> This is the revised set of patches for the ARM translator and it includes a
> number of smaller fixes and improvements. The series should be applied in
> sequence as the modifications are mostly
We encontered problems with the low default value for the stacksize in usermode
(ok, whats "low").
For environments like scratchbox, its hard to use "-s" as qemu is called by
binfmt mechanism.
The attached patch makes this configurable at compile-time.
Signed-off-by: Jan-Simon Möller
diff --g
Am Sonntag 25 Oktober 2009 16:54:16 schrieb Laurent Desnogues:
> Wouldn't it be better to set this earlier only if target_user_only
> is set to yes and use cflags?
>
> Something like this:
>
> if test "$target_user_only" = "yes" -a "$user_mode_stacksize" != ""; then
> cflags="-DUSER_MODE_STACKS
On Thu, Oct 22, 2009 at 10:25:59AM -0700, Jay Schulist wrote:
> I have an issue with perl and qemu that I'm hoping someone knows what
> is happening. I'm using qemu-i386 on a fedora 11 intel system and the
> following command fails:
>
> $ qemu-i386 -L / /usr/bin/perl -e 'print `perl -v`'
[...]
>
2009/10/25 Jan-Simon Möller :
> Hi !
>
> We encontered problems with the low default value for the stacksize in
> usermode (ok, whats "low").
> For environments like scratchbox, its hard to use "-s" as qemu is called by
> binfmt mechanism.
> The attached patch makes this configurable at compile-t
On Sun, 25 Oct 2009 17:28:33 +0200
Avi Kivity wrote:
> On 10/23/2009 03:59 PM, Anthony Liguori wrote:
> > Your answer may be, this is for a developer and they'll be aware of
> > all the short comings/gotchas but this ends up being a rather
> > user-hostile interface. People are never as aware
On 10/23/2009 03:59 PM, Anthony Liguori wrote:
Your answer may be, this is for a developer and they'll be aware of
all the short comings/gotchas but this ends up being a rather
user-hostile interface. People are never as aware of short
comings/gotchas as we'd like them to be. If there was no
Hi !
We encontered problems with the low default value for the stacksize in usermode
(ok, whats "low").
For environments like scratchbox, its hard to use "-s" as qemu is called by
binfmt mechanism.
The attached patch makes this configurable at compile-time.
Signed-off-by: Jan-Simon Möller
d
On 10/23/2009 06:43 PM, Mark McLoughlin wrote:
On Fri, 2009-10-23 at 20:25 +0400, Michael Tokarev wrote:
I've two questions:
o what's the intended usage of all-vlan-equal case, when kvm (or qemu)
reflects packets from one interface to another? It's what bridge
in linux is for, I th
On Sat, Oct 24, 2009 at 1:19 PM, wrote:
> From: Juha Riihimäki
>
> Reduce the amount of TCG ops generated from NEON vld/vst instructions
> by simplifying the code generation.
>
> Signed-off-by: Juha Riihimäki
> ---
> target-arm/translate.c | 67 ---
On Sat, Oct 24, 2009 at 1:19 PM, wrote:
> From: Juha Riihimäki
>
> All other bits except for the EN in the VFP FPEXC register are defined
> as subarchitecture specific and real functionality for any of the
> other bits has not been implemented in QEMU. However, current code
> allows modifying al
On Sat, Oct 24, 2009 at 1:19 PM, wrote:
> From: Juha Riihimäki
>
> Current code is broken at least on gcc 4.2, the result of a comparison
> "-1 >= sizeof(type) * 8" results true and causes wrong code path to
> be taken. The fix has been revised to use a type cast instead of
> abs() function and
On Sat, Oct 24, 2009 at 1:19 PM, wrote:
> From: Juha Riihimäki
>
> Add support for NEON vld1.64 and vst1.64 instructions. This patch is
> revised to follow more closely the specification and raises
> undefined exception if 64bit element size is used for vld2/vst2 or
> vld4/vst4 instructions.
>
>
On Sat, Oct 24, 2009 at 1:19 PM, wrote:
> From: Juha Riihimäki
>
> In the existing code shift value is clobbered during the pass loop.
> This patch changes the code so that it stores the intermediate
> result in the target neon register directly and eliminates the need
> to use a temporary to ho
On 10/14/2009 04:30 PM, Glauber Costa wrote:
Hello people,
As I promised, I am sending a very brief PoC wrt split devices and in-kernel
irqchip.
In this mail, I am including only the ioapic version for apreciation. I also
have i8259,
and apic will take me a little bit more. This is just to try
On Thu, Oct 22, 2009 at 06:57:27PM -0200, Marcelo Tosatti wrote:
> On Thu, Oct 22, 2009 at 02:00:15PM +0200, Michael S. Tsirkin wrote:
> > Hi!
> > I'm sometimes getting segfaults when I kill qemu.
> > This time I caught it when qemu was under gdb:
> >
> >
> > Program received signal SIGSEGV, Segm
> >> Do you support multiple guests accessing the same image?
> >
> > A VM image can be attached to any VMs but one VM at a time; multiple
> > running VMs cannot access to the same VM image.
I guess this is a problem when you want to do live migrations?
- Dietmar
> Also, on _loaded_ systems, I noticed creating/removing logical volumes
> can take really long (several minutes); where allocating a file of a
> given size would just take a fraction of that.
Allocating a file takes much longer, unless you use a 'sparse' file.
- Dietmar
On Thu, Oct 22, 2009 at 11:05:55AM +0200, Kevin Wolf wrote:
> Yes, it might look like overkill to introduce a abstraction for exactly
> two backends. I felt the same way. But then, the current implementation
> just feels totally wrong. It absolutely intransparent when we fall back
> to paio, and be
27 matches
Mail list logo