Due to upstream qemu changes we no longer expose the host cpu vendor id
to the guest. This leads to failures when the syscall/sysenter instructions
are used in compatibility mode.
Change the default to override when kvm is enabled.
Signed-off-by: Avi Kivity a...@redhat.com
---
On 12/28/2009 12:52 AM, Anthony Liguori wrote:
As a reviewer, you can read qemu-commits to see when something has
been committed.
I have the same problem fwiw. I don't read qemu-commits because I
always look at the contents of origin when I fetch from it to see what
others are doing.
On Mon, Dec 28, 2009 at 10:58:32AM +0200, Avi Kivity wrote:
On 12/28/2009 12:52 AM, Anthony Liguori wrote:
As a reviewer, you can read qemu-commits to see when something has
been committed.
I have the same problem fwiw. I don't read qemu-commits because I
always look at the contents of
On Sun, Dec 27, 2009 at 05:01:38PM -0600, Anthony Liguori wrote:
Personally, I think blanket rules get in the way more than they help and
the only thing that's worse is arguing about the merits of them :-)
No rules is also not good :) I hope everyone can agree on principle,
and we'll see
On Thu, Dec 24, 2009 at 12:15:47PM +0300, Michael Tokarev wrote:
In qemu-kvm this place looks even more interesting:
-runas user Change to user id user just before starting the VM.
-readconfig file
-writeconfig file
read/write config file-no-kvm disable KVM
Hi,
I think it is something about OpenBios.
Is there anybody who successfully did it with qemu-sloaris-sparc?
Thanks.
Fred
On Mon, Dec 28, 2009 at 10:58:32AM +0200, Avi Kivity wrote:
On 12/28/2009 12:52 AM, Anthony Liguori wrote:
As a reviewer, you can read qemu-commits to see when something has
been committed.
I have the same problem fwiw. I don't read qemu-commits because I
always look at the contents of
On Mon, Dec 28, 2009 at 12:15:10PM +0100, Aurelien Jarno wrote:
On Mon, Dec 28, 2009 at 10:58:32AM +0200, Avi Kivity wrote:
On 12/28/2009 12:52 AM, Anthony Liguori wrote:
As a reviewer, you can read qemu-commits to see when something has
been committed.
I have the same problem fwiw.
This fixes the loading of a stripped kernel with zero malloc disabled.
Signed-off-by: Aurelien Jarno aurel...@aurel32.net
---
hw/elf_ops.h |9 +++--
1 files changed, 7 insertions(+), 2 deletions(-)
diff --git a/hw/elf_ops.h b/hw/elf_ops.h
index 6093dea..d0811ca 100644
--- a/hw/elf_ops.h
Aurelien Jarno wrote:
This fixes the loading of a stripped kernel with zero malloc disabled.
*Raises an eyebrow*
Even though there's different perspectives over whether qemu_malloc(0)
should be allowed, inherited from ambiguity over malloc(0),
realloc(p,0) has always had a standard,
On Mon, Dec 28, 2009 at 02:53:25PM +, Jamie Lokier wrote:
Aurelien Jarno wrote:
This fixes the loading of a stripped kernel with zero malloc disabled.
*Raises an eyebrow*
Even though there's different perspectives over whether qemu_malloc(0)
should be allowed, inherited from
realloc(ptr, 0) is always allowed by the standard. The return value is
either NULL or a pointer that can be freed with free().
Allow usage of qemu_realloc(ptr, 0), and return NULL in that case, as
free(NULL) should always be a nop.
This fixes -kernel with stripped kernels.
Signed-off-by:
This patch adds a physical block size attribute to virtio disks,
corresponding to /sys/devices/.../physical_block_size. It is defined as
the request alignment which will not trigger RMW cycles. This can be
important for modern disks which use 4K physical sectors (though they
still support 512
On Mon, 28 Dec 2009, Jamie Lokier wrote:
Aurelien Jarno wrote:
This fixes the loading of a stripped kernel with zero malloc disabled.
*Raises an eyebrow*
Even though there's different perspectives over whether qemu_malloc(0)
should be allowed, inherited from ambiguity over malloc(0),
On Mon, Dec 28, 2009 at 11:06:20AM -0800, Richard Henderson wrote:
On 12/24/2009 07:18 AM, Aurelien Jarno wrote:
My main concern about this patch is that I don't really understand why
the current fp exceptions, the current rounding mode or flush_to_zero
mode are stored in FP_STATUS. I think it
On Mon, Dec 28, 2009 at 08:48:22PM +0100, Aurelien Jarno wrote:
On Mon, Dec 28, 2009 at 11:06:20AM -0800, Richard Henderson wrote:
On 12/24/2009 07:18 AM, Aurelien Jarno wrote:
My main concern about this patch is that I don't really understand why
the current fp exceptions, the current
On Mon, Dec 28, 2009 at 08:52:28PM +0100, Aurelien Jarno wrote:
On Mon, Dec 28, 2009 at 08:48:22PM +0100, Aurelien Jarno wrote:
On Mon, Dec 28, 2009 at 11:06:20AM -0800, Richard Henderson wrote:
On 12/24/2009 07:18 AM, Aurelien Jarno wrote:
My main concern about this patch is that I don't
On Mon, Dec 28, 2009 at 04:49:00PM +0100, Aurelien Jarno wrote:
realloc(ptr, 0) is always allowed by the standard. The return value is
either NULL or a pointer that can be freed with free().
Allow usage of qemu_realloc(ptr, 0), and return NULL in that case, as
free(NULL) should always be a
According to C99, realloc(non_null, 0) != free(non_null), that's why
it is forbidden in QEMU.
When there are no symbols, nsyms equals to 0. Free the syms structure
and set it to NULL instead of reallocating it with a size of 0.
This fixes -kernel with stripped kernels.
Signed-off-by: Aurelien
On Mon, Dec 28, 2009 at 10:48:00AM +0200, Avi Kivity wrote:
Due to upstream qemu changes we no longer expose the host cpu vendor id
to the guest. This leads to failures when the syscall/sysenter instructions
are used in compatibility mode.
Change the default to override when kvm is enabled.
Hi,
as a follow-up to a previous thread
(http://lists.nongnu.org/archive/html/qemu-devel/2009-12/msg01089.html)
the qemu-system-mips seems to work better than described above on a
OpenSolaris/SPARC host systen when the following patch is applied:
On 12/24/2009 07:18 AM, Aurelien Jarno wrote:
My main concern about this patch is that I don't really understand why
the current fp exceptions, the current rounding mode or flush_to_zero
mode are stored in FP_STATUS. I think it would be better to have
dedicated variable(s) in the cpu state
Hi,
Im a newbie to qemu use.
so i got a lot error!..
I build qemu from source with the version 0.10.3,
But when i start qemu with the command below, i got the message
Could not initialize SDL - exiting
after that Qemu exit. I dig the web ,but i could not find any answers,so
I ask
Hello
The stat64/fstat64 syscalls are broken for alpha linux-user.
This is because Alpha, even though it is native 64-bits, has a stat64
syscall that is different than regular stat. This means that the
TARGET_LONG_BITS==64 check in syscall.c isn't enough. Below is
a patch that fixes things
Hi
Unfortunately QEMU doesn't work for me because it uses absolute paths
instead of environmental variables.
Proof;
http://i46.tinypic.com/11tbz1l.jpg
The environmental variable which should be used is %ProgramFiles%
Please correct this programmatically. (LOL, if that's a word!)
In return for
25 matches
Mail list logo
