Zhang, Xiantao wrote:
> Sorry for confusing you. Is it clear now?
Thanks, yea this makes your intention clear to me. I think what you
describe is an odd way to initialize both modules, and I'd like to
suggest to try to come up with the reverse approach where kvm.ko loads
your other module via r
I use bcc from dev86-0.16.17 (fedora rpm). You can compile it from the source.
There are some problems using it on 64 bit platforms. I use a 32bit fedora VM
to build such binaries.
Shahar
From: Francesc Romà i Frigolé [mailto:[EMAIL PROTECTED]
Sent: Mond
On Fri, 23 Nov 2007 19:54:46 +0200
Avi Kivity <[EMAIL PROTECTED]> wrote:
>
> No new macros in the emulator please. Just inline it at the callsite.
>
Ok I make the modification.
: c->dst.bytes);
> > break;
> > case 0xa6 ..
Neo Jia wrote:
> Avi Kivity wrote:
>
>> Neo Jia wrote:
>>
>>> On Nov 24, 2007 12:00 AM, Avi Kivity <[EMAIL PROTECTED]> wrote:
>>>
>>>
Neo Jia wrote:
> The version of kvm I used for kvm module is
> "694401697ccd822bb08019731c3ee1bb34323d8e" and th
hello,
can someone give me an information regarding the cross compile ability of kvm
(especially for qemu)?
Which is the first version of kvm, which is considered to be able to cross
compile?
I tried KVM-28, which failed totally to cross-compile and I used KVM-53, which
already had better sup
This patch emulates the CMPS instruction. I made corrections requested
by Avi (removed macro and added the memory access). I fixed an
inversion between arguments VCPU_REGS_RSI and VCPU_REGS_RDI in function
register_address(). I also added the test if DS segment is overridden
with a segment override
# HG changeset patch
# User Jerone Young <[EMAIL PROTECTED]>
# Date 1196087575 21600
# Node ID ccf9dd8a8e0a4513090d44d52c879fb9dfbb79dd
# Parent 32d8bd91d9441d2a3655593a0aaf99f6c403d70f
Add ifdef in irqchip struct for x86 only structures.
This patch fixes a small issue where sturctures:
k
# HG changeset patch
# User Jerone Young <[EMAIL PROTECTED]>
# Date 1196089537 21600
# Node ID 9749d43f49ca6fa369a94e26e85e96e9ca9c999e
# Parent f1f4385ec96bd49d5505292b8676e7937574f355
Add ifdefs to libkvm.h to pervent warnings for other archs
This patch adds ifdefs around x86 specific functions
Guillaume Thouvenin wrote:
> This patch emulates the CMPS instruction. I made corrections requested
> by Avi (removed macro and added the memory access). I fixed an
> inversion between arguments VCPU_REGS_RSI and VCPU_REGS_RDI in function
> register_address(). I also added the test if DS segment is
Jerone Young wrote:
> # HG changeset patch
> # User Jerone Young <[EMAIL PROTECTED]>
> # Date 1196089537 21600
> # Node ID 9749d43f49ca6fa369a94e26e85e96e9ca9c999e
> # Parent f1f4385ec96bd49d5505292b8676e7937574f355
> Add ifdefs to libkvm.h to pervent warnings for other archs
>
> This patch adds i
Jerone Young wrote:
> # HG changeset patch
> # User Jerone Young <[EMAIL PROTECTED]>
> # Date 1196087575 21600
> # Node ID ccf9dd8a8e0a4513090d44d52c879fb9dfbb79dd
> # Parent 32d8bd91d9441d2a3655593a0aaf99f6c403d70f
> Add ifdef in irqchip struct for x86 only structures.
>
> This patch fixes a smal
Hmm... so now begins the conflict with userspace and kernel space header
sharing ;-)
So the issue (which can be easily fixed) is that CONFIG_X86 is not
recognized in any userspace apps. While __i386__ & __x86_64__ are. Now
this can easily be added to our build system. But it does show the
problem.
On Mon, 2007-11-26 at 11:57 +0100, Gerd Koenig wrote:
> hello,
>
> can someone give me an information regarding the cross compile ability of kvm
> (especially for qemu)?
> Which is the first version of kvm, which is considered to be able to cross
> compile?
It would be one of the newer versio
For some reason acpi refuses to start on a Fedora 8 guest. The dmesg
says at the very begining "no DMI BIOS year, acpi=force is required to
enable ACPI". I then put acpi=force on the command line and it
sometimes works and sometimes doesn't. What I mean by works is
sometimes it issues the acpi shut
Jerone Young wrote:
> Hmm... so now begins the conflict with userspace and kernel space header
> sharing ;-)
>
> So the issue (which can be easily fixed) is that CONFIG_X86 is not
> recognized in any userspace apps. While __i386__ & __x86_64__ are. Now
> this can easily be added to our build system
David Brown wrote:
> For some reason acpi refuses to start on a Fedora 8 guest. The dmesg
> says at the very begining "no DMI BIOS year, acpi=force is required to
> enable ACPI". I then put acpi=force on the command line and it
> sometimes works and sometimes doesn't. What I mean by works is
> some
> Known issue (cause not yet identified).
I wonder how many of these things are qemu's fault really...
- David Brown
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http:/
David Brown wrote:
>> Known issue (cause not yet identified).
>>
>
> I wonder how many of these things are qemu's fault really...
>
>
Many, but knowing that doesn't help in any way. There's no better open
source hardware emulation platform I know of.
(does the issue reproduce with -no-k
Zhao, Yunfeng wrote:
> Hi, all,
>
> This is today's KVM test result against kvm.git
> 51727A110220681F6F43B005D069E28C58F5D151 and kvm-userspace.git
> 6a385c9539f9746d7ff51ef34c064c3eba86448b.
>
> One regression:
> 1. Cannot install 64bit vista guests.
> https://sourceforge.net/tracker/?func=deta
Perhaps we could just move the declaration of kvm_irqchip to an arch
specific header instead of introducing #ifdef's?
Does ia64 have a i8259a?
Regards,
Anthony Liguori
Jerone Young wrote:
> # HG changeset patch
> # User Jerone Young <[EMAIL PROTECTED]>
> # Date 1196087575 21600
> # Node ID ccf
Avi Kivity wrote:
> rx and tx are closely related. You rarely have one without the other.
>
> In fact, a turned implementation should have zero kicks or interrupts
> for bulk transfers. The rx interrupt on the host will process new tx
> descriptors and fill the guest's rx queue; the guest's trans
using kvm-53 a problem with migration (not working
even with regular migration)
fails with kvm:
[EMAIL PROTECTED]:/home/kvm$ sudo
/usr/local/kvm/bin/qemu-system-x86_64 -hda winxp.img
-boot c -m 512
BUG: kvm_dirty_pages_log_change: invalid parameters
32+1 records in
32+1 records out
16781 bytes (1
On Wed, Oct 10, 2007 at 03:53:10PM +0200, magicboiz wrote:
> Sun Solaris Express(9/07), does not detect the hard disk..I attach
> an screenshot.
from the screenshot it seems that the problem is not with the hard disk but
with the cdrom.
attached patch to qemu (not yet committed upstream) fixe
From c050ed6225f314b86a0dabf11c7f677de097c39f Mon Sep 17 00:00:00 2001
From: Sheng Yang <[EMAIL PROTECTED]>
Date: Tue, 27 Nov 2007 14:41:06 +0800
Subject: [PATCH] KVM: Fix compile error caused by no defined CONFIG_X86
For was included by qemu, which didn't define CONFIG_X86,
kvm compiles fail on
From 5a3ca0556bb3f8b9e18d392535312c370c2dd2f7 Mon Sep 17 00:00:00 2001
From: Sheng Yang <[EMAIL PROTECTED]>
Date: Tue, 27 Nov 2007 14:51:44 +0800
Subject: [PATCH] kvm: qemu: Fix compile error in non-x86 arch
This patch disable PIC/IOAPIC live migration support for non-x86 arch.
Signed-off-by: She
>From 2d054cce30ae2e837b24144195b9785a20e08c4a Mon Sep 17 00:00:00 2001
From: Neo Jia <[EMAIL PROTECTED]>
Date: Mon, 26 Nov 2007 23:29:53 -0800
Subject: [PATCH] Remove build output file in user/test/x86/lib.
This patch will remove the generated files (.*.d, *.o) in directory
user/test/x86/lib unde
On Mon, 2007-11-26 at 20:08 -0500, phrek wrote:
> using kvm-53 a problem with migration (not working
> even with regular migration)
>
we know this
there is a problem that we try to fix first, and then we will upgrade
the support for new kvm versions
-
On Nov 26, 2007 2:16 AM, Avi Kivity <[EMAIL PROTECTED]> wrote:
>
> Neo Jia wrote:
> > Avi Kivity wrote:
> >
> >> Neo Jia wrote:
> >>
> >>> On Nov 24, 2007 12:00 AM, Avi Kivity <[EMAIL PROTECTED]> wrote:
> >>>
> >>>
> Neo Jia wrote:
>
>
> > The version of kvm I used for kvm module
28 matches
Mail list logo
