Dong, Eddie wrote:
> [EMAIL PROTECTED] wrote:
>> hi,
>> i'm just try kvm-45. for me it still unusable, so switch back
>> to kvm-36:-(
>> setup:
>> - host: centos-5 x86-64 (4 core, 8gb ram)
>> - guest:
>> - centos-5 i386 4 cpu, 2gb
>> - centos-5 x86-64 4 cpu, 1gb
>> - mandrake-9 i586 2 cpu, 1gb
On Mon, Oct 08, 2007 at 02:29:32PM -0500, Anthony Liguori wrote:
>
> Eventually, KVM will merge with upstream QEMU. In that case, many
> people will be using QEMU without the desiring to use KVM. We don't
> want to introduce behavior in QEMU that is unmergable with upstream QEMU
> b/c that wi
aeroplanes. They had daily baths; they did their weekly laundry,
Always the offensive! Germany would keep on striking as long as she
approach, the real obstacle to full expression. But the moments were
account. Twelve months of war have not shaken conventional ideas
among the mountaineers of the
On Mon, Oct 08, 2007 at 06:23:30PM +0200, Avi Kivity wrote:
> Carlo Marcelo Arenas Belon wrote:
> >
> > If the qemu-cc option is not used but disable-gcc-check is requested then
> > assume that the default system gcc should be used (chosen by name)
> >
> > This patch fixes sourceforge bug id 180762
This patch enables the user directory make file for cross compiling.
Signed-off-by: Jerone Young <[EMAIL PROTECTED]>
diff -r e76b2ad97742 user/Makefile
--- a/user/Makefile Tue Oct 09 00:03:08 2007 -0500
+++ b/user/Makefile Tue Oct 09 00:03:59 2007 -0500
@@ -1,5 +1,13 @@
include config.mak
+
+
This patch enables configure script in user directory for cross compile.
Signed-off-by: Jerone Young <[EMAIL PROTECTED]>
diff -r b0a20b1a7339 user/configure
--- a/user/configure Mon Oct 08 23:48:50 2007 -0500
+++ b/user/configure Mon Oct 08 23:49:22 2007 -0500
@@ -2,13 +2,20 @@
prefix=/usr/lo
I'll redo 3-5 .. I'll also see what is up with this one. it applies fine
in my repo. Plus need to redo patch 3 anyway. Removing the CFLAGS+= was
not the best thing as the arch specific files had no way to ad CFLAGS.
Will submit even more patches shortly :-)
On Mon, 2007-10-08 at 18:36 +0200, Avi
Avi Kivity wrote:
> Dong, Eddie wrote:
>> Kernel side patch to introduce a new API for kernel device reset and
>> force vcpu mp_state to UNINATIALIZED state if it is reset.
>> thx,eddie
>>
>>
>>
>> +
>> +/*
>> + * Reset VM.
>> + *
>> + */
>> +int kvm_vm_reset(struct kvm *kvm)
>> +{
>> +struc
Avi Kivity wrote:
> Zhang, Xiantao wrote:
>> Hollis Blanchard wrote:
>>
>>> On Mon, 2007-10-08 at 10:36 +0800, Zhang, Xiantao wrote:
>>>
Avi Kivity wrote:
> Zhang, Xiantao wrote:
>
>> Avi Kivity wrote:
>>
>>
>>> Zhang, Xiantao wrote:
>>>
>>>
>>>
[EMAIL PROTECTED] wrote:
> Hello,
>
> Trying to install Windows XP Pro 64bits, the first phase goes
> quite well (except
> that it uses 100% of host's cpu), but crashes when trying to
> reboot with the
> following message:
>
> unhandled vm exit: 0x8021
> rax 0095b9e5 rbx 0095
[EMAIL PROTECTED] wrote:
> David Brown wrote:
>>> Can you run 'gdb /path/to/kvm.ko' and post the output of
>>> 'disassemble ioapic_mmio_write' please?
>>>
>>>
>>
>> Sorry for not getting back sooner.
>>
>> (gdb) disassemble ioapic_mmio_write
>> Dump of assembler code for function ioapic_mmio_w
[EMAIL PROTECTED] wrote:
> hi,
> i'm just try kvm-45. for me it still unusable, so switch back
> to kvm-36:-(
> setup:
> - host: centos-5 x86-64 (4 core, 8gb ram)
> - guest:
> - centos-5 i386 4 cpu, 2gb
> - centos-5 x86-64 4 cpu, 1gb
> - mandrake-9 i586 2 cpu, 1gb
> - winxp 32bit1
[EMAIL PROTECTED] wrote:
> Hello,
>
> I am currently evaluating kvm for using it for an application
> where correct
> time is absolutely critical. We therefore normally use NTP on
> these machines
> to synchronize them with GPS time. For a virtual machine in my
> eyes that
> means, the host should
Byron Stanoszek wrote:
> On Mon, 8 Oct 2007, Anthony Liguori wrote:
>>
>> If you're going to do anything, a firm warning when compiling with a
>> GCC4 override would be the best thing.
>
> I disagree with the compile warning. There have been times in the past
> when
> I've forgotten to "insmod kvm
On Mon, 8 Oct 2007, Anthony Liguori wrote:
> Carlo Marcelo Arenas Belon wrote:
>> Using gcc4 to compile qemu will generate broken code for its cpu emulation
>> but should be fine if using kvm only.
>>
>> This will allow users that have no access to gcc4 on their platforms to at
>> least get kvm co
Title: Untitled Document
Gentile membro Poste Italiane,
con BancoPostaonline, lÂaccesso Internet ai servizi finanziari di Poste Italiane, puoi apprezzare tutti i vantaggi del tuo
Jerone Young wrote:
> This patch enables configure script in "user" directory fro cross
> compile.
>
>
I applied the new 1/, but this doesn't?
Also, 3-5 ought to be one patch, otherwise bisection breaks.
--
Do not meddle in the internals of kernels, for they are subtle and quick to
panic.
Dong, Eddie wrote:
> commit e634910140a7e8a55322cd6a1d94fcfd77d9eae0
> Author: root <[EMAIL PROTECTED](none)>
> Date: Mon Oct 8 16:52:01 2007 +0800
>
> show vcpu_id in case of unknown hw exception.
>
>
Applied, thanks.
--
Do not meddle in the internals of kernels, for they are sub
Carlo Marcelo Arenas Belon wrote:
> Allow users to override the compiler checks for gcc3 that are required for
> compatibility with qemu in the same way that qemu does.
>
> If the qemu-cc option is not used but disable-gcc-check is requested then
> assume that the default system gcc should be used
[EMAIL PROTECTED] wrote:
> Hello,
> I have attached documentation for a segfault that happens on my system
> using kvm-45 but does not happen with kvm-44. I included what I
> thought was relevant.
> Using modules that were built during kernel build.
> I have gcc3.4 compatibility tools installed tha
Bugs item #1809565, was opened at 2007-10-08 18:09
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1809565&group_id=180599
Please note that this message will contain a full copy
Carlo Marcelo Arenas Belon wrote:
> Using gcc4 to compile qemu will generate broken code for its cpu emulation
> but should be fine if using kvm only.
>
> This will allow users that have no access to gcc4 on their platforms to at
> least get kvm compiled and use it while preventing them to run a br
This is a solution to the original problem with opensuse:
You can get gcc33 from the opensuse build service (this is the new
one-click-install)
http://software.opensuse.org/ymp/devel%3Atools%3Agcc/openSUSE_10.3/i586/
gcc33-3.3.3-41.6.i586.rpm.ymp
(or download specific rpm's from http://software.o
Using gcc4 to compile qemu will generate broken code for its cpu emulation
but should be fine if using kvm only.
This will allow users that have no access to gcc4 on their platforms to at
least get kvm compiled and use it while preventing them to run a broken
qemu if kvm is not available.
This is
Allow users to override the compiler checks for gcc3 that are required for
compatibility with qemu in the same way that qemu does.
If the qemu-cc option is not used but disable-gcc-check is requested then
assume that the default system gcc should be used (chosen by name)
This patch fixes sourcefo
Mike Day wrote:
> CodingStyle cleanup.
>
>
Applied, thanks.
--
Do not meddle in the internals of kernels, for they are subtle and quick to
panic.
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through
CodingStyle cleanup.
Signed-off-by: Mike D. Day <[EMAIL PROTECTED]>
---
This is the second attempt. It includes changes based on feedback, and
consolidates all the 10 previous CodingStyle patches into one patch.
drivers/kvm/kvm.h | 32 +-
drivers/kvm/kvm_main.c| 5
It works.:)
The issue disappeared after applied the patch.
Thanks
Yunfeng
>-Original Message-
>From: Avi Kivity [mailto:[EMAIL PROTECTED]
>Sent: 2007年10月8日 17:53
>To: Zhao, Yunfeng
>Cc: kvm-devel@lists.sourceforge.net
>Subject: Re: [kvm-devel] vga color
>
>Zhao, Yunfeng wrote:
>> All our
Zhao, Yunfeng wrote:
> It works.:)
> The issue disappeared after applied the patch.
>
Thanks, I applied and pushed it.
--
Any sufficiently difficult bug is indistinguishable from a feature.
-
This SF.net email is sponso
Hi,
sorry for the delay, but I've been on vacation. :-)
On Sun, 30 Sep 2007, Anthony Liguori wrote:
> Avi Kivity wrote:
> > Anthony Liguori wrote:
> >> As Avi pointed out, VT requires that SS.RPL == CS.RPL. We're seeing
> >> gfxboot fail under KVM because ss = 0x5761 while cs = 0x4004 during
>
Laurent Vivier wrote:
> Avi Kivity wrote:
>
>> Laurent Vivier wrote:
>>
>>> Avi Kivity wrote:
>>>
>>>
Aurelien Jarno wrote:
> It's actually described page 200 of the specifications (page 216 in
> ACPIspec30.pdf):
>
> Note: This descri
Avi Kivity wrote:
> Laurent Vivier wrote:
>> Avi Kivity wrote:
>>
>>> Aurelien Jarno wrote:
>>>
It's actually described page 200 of the specifications (page 216 in
ACPIspec30.pdf):
Note: This descriptor is meant for describing interrupts that are
connected to PIC-
Dong, Eddie wrote:
> This one is a preparation for kernel devices reset support.
>
>
>
>Split ioapic reset API and export PIC reset API
>
Please split into two patches, I need to fold them into the pic patch
and the ioapic patch.
>
> -static void pic_reset(void *opaque)
> +void kvm_p
Dong, Eddie wrote:
> Kernel side patch to introduce a new API for kernel device reset and
> force
> vcpu mp_state to UNINATIALIZED state if it is reset.
> thx,eddie
>
> +
> +/*
> + * Reset VM.
> + *
> + */
> +int kvm_vm_reset(struct kvm *kvm)
> +{
> + struct kvm_vcpu *vcpu;
> + int i;
> +
>
Dong, Eddie wrote:
> Kernel side patch to introduce a new API for kernel device reset and
> force
> vcpu mp_state to UNINATIALIZED state if it is reset.
> thx,eddie
>
>
>
> +
> +/*
> + * Reset VM.
> + *
> + */
> +int kvm_vm_reset(struct kvm *kvm)
> +{
> + struct kvm_vcpu *vcpu;
> + int i;
>
User level change to add callback to reset kernel devices.
thx,eddie
Add user reset callback support for kernel devices.
Signed-off-by: Yaozu (Eddie) Dong <[EMAIL PROTECTED]>
diff --git a/qemu/hw/pc.c b/qemu/hw/pc.c
index 4d0bb93..d81e7e1 100644
--- a/qemu/hw/pc.c
+++ b/qemu/hw/p
Kernel side patch to introduce a new API for kernel device reset and
force
vcpu mp_state to UNINATIALIZED state if it is reset.
thx,eddie
Add VM reset support in kernel side to
reset the kernel devices and VCPUs.
Signed-off-by: Yaozu (Eddie) Dong <[EMAIL PROTECTED]>
diff --git
This one is a preparation for kernel devices reset support.
Split ioapic reset API and export PIC reset API
Signed-off-by: Yaozu (Eddie) Dong <[EMAIL PROTECTED]>
diff --git a/drivers/kvm/i8259.c b/drivers/kvm/i8259.c
index a679157..abcf58f 100644
--- a/drivers/kvm/i8259.c
++
commit e634910140a7e8a55322cd6a1d94fcfd77d9eae0
Author: root <[EMAIL PROTECTED](none)>
Date: Mon Oct 8 16:52:01 2007 +0800
show vcpu_id in case of unknown hw exception.
Signed-off-by: Yaozu (Eddie) Dong <[EMAIL PROTECTED]>
diff --git a/user/kvmctl.c b/user/kvmctl.c
index 3dee407.
Under certain conditions, PIC interrupts should not be passed through by
the local APIC. This is usually when the guest uses the IOAPIC instead
of the PIC.
Currently qemu does not block PIC interrupts when the local APIC is
configured to do so; this results in interrupts begin received twice and
Zhang, Xiantao wrote:
> Hollis Blanchard wrote:
>
>> On Mon, 2007-10-08 at 10:36 +0800, Zhang, Xiantao wrote:
>>
>>> Avi Kivity wrote:
>>>
Zhang, Xiantao wrote:
> Avi Kivity wrote:
>
>
>> Zhang, Xiantao wrote:
>>
>>
>
Zhao, Yunfeng wrote:
> All our machines for KVM testing have the problem.
> I attached the output of "xdpyinfo" on one of them.
>
>
Please try the attached patch.
--
Any sufficiently difficult bug is indistinguishable from a feature.
diff --git a/qemu/sdl.c b/qemu/sdl.c
index 02500c9..3f3b7
Laurent Vivier wrote:
> Avi Kivity wrote:
>
>> Aurelien Jarno wrote:
>>
>>> It's actually described page 200 of the specifications (page 216 in
>>> ACPIspec30.pdf):
>>>
>>> Note: This descriptor is meant for describing interrupts that are
>>> connected to PIC-compatible
>>> interrupt co
Bugs item #1809327, was opened at 2007-10-08 16:51
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1809327&group_id=180599
Please note that this message will contain a full copy
All our machines for KVM testing have the problem.
I attached the output of "xdpyinfo" on one of them.
Thanks
Yunfeng
>-Original Message-
>From: Avi Kivity [mailto:[EMAIL PROTECTED]
>Sent: 2007年10月8日 16:15
>To: Zhao, Yunfeng
>Cc: kvm-devel@lists.sourceforge.net
>Subject: Re: [kvm-devel] v
This patch adds cross compile capability to the top level configure
script.
Updates:
Removed command line option --target-cpu to configure what qemu
executable to build.
diff -r f48e521e0add configure
--- a/configure Wed Oct 03 21:00:03 2007 -0500
+++ b/configure Mon Oct 08 03:30:41 2007 -0500
@@
On Mon, 2007-10-08 at 09:49 +0200, Christian Ehrhardt wrote:
> Hi,
> I saw that you derive $target_cpu from arch as I know it from your older
> internal and external patches.
> Now you added the configure command line option --target-cpu to allow to
> overwrite that $arch derived target.
> a) do
Avi Kivity wrote:
> Aurelien Jarno wrote:
>>
>> It's actually described page 200 of the specifications (page 216 in
>> ACPIspec30.pdf):
>>
>> Note: This descriptor is meant for describing interrupts that are
>> connected to PIC-compatible
>> interrupt controllers, which can only be programmed f
Zhao, Yunfeng wrote:
> Against latest commits I found that the colors on the windows guest
> become weird.
> For example, blue color has changed to red.
> Is there any change on vga of qemu?
>
>
Yes, I merged qemu-cvs and got some surprises.
This doesn't appear on all machines. Can you post t
Laurent Vivier wrote:
> for kvm-userspace:
>
> Allow to compile biossums on x86_64 and remove acpi-dsdt.hex on clean.
>
>
Applied, thanks.
--
Any sufficiently difficult bug is indistinguishable from a feature.
-
This SF
Rusty Russell wrote:
> Instead of the asymetry of kvm_free_apic, implement kvm_free_lapic().
> And guess what? I found a minor bug: we don't need to hrtimer_cancel()
> from kvm_main.c, because we do that in kvm_free_apic().
>
> Also:
> 1) kvm_vcpu_uninit should be the reverse order from kvm_vcpu_i
David Brown wrote:
Can you run 'gdb /path/to/kvm.ko' and post the output of 'disassemble
ioapic_mmio_write' please?
Sorry for not getting back sooner.
(gdb) disassemble ioapic_mmio_write
Dump of assembler code for function ioapic_mmio_write:
The attached patch should fix, though the
Aurelien Jarno wrote:
It's actually described page 200 of the specifications (page 216 in
ACPIspec30.pdf):
Note: This descriptor is meant for describing interrupts that are connected
to PIC-compatible
interrupt controllers, which can only be programmed for
Active-High-Edge-Triggered or
Hi,
I saw that you derive $target_cpu from arch as I know it from your older
internal and external patches.
Now you added the configure command line option --target-cpu to allow to
overwrite that $arch derived target.
a) do you have some use cases in mind where you need an overwritten target
ins
for kvm-userspace:
Allow to compile biossums on x86_64 and remove acpi-dsdt.hex on clean.
Signed-off-by: Laurent Vivier <[EMAIL PROTECTED]>
---
bios/Makefile |4 +++-
bios/acpi-dsdt.hex |8
2 files changed, 7 insertions(+), 5 deletions(-)
diff --git a/bios/Makefile b/bios/
55 matches
Mail list logo
