Re: [kvm-devel] kvm-37 results
Jorge Lucángeli Obes wrote: > Windows Vista Ultimate 32-bit guest: hangs during boot. > *Command line: > -net nic,model=8139 -m 512 -localtime > *Nothing in dmesg besides processor 1 inicialization SIPI messages > *Still hangs during boot with 'no-kvm-irqchip' > > Can you double-check that you are using the bios.bin provided by kvm-37? -- error compiling committee.c: too many arguments to function - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] build failure on master branch
He, Qing wrote: > > You can try the attached patch to see if it works > Ouch. Applied, thanks. > > > *From:* [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] *On Behalf Of *He, Qing > *Sent:* 2007年9月10日 10:55 > *To:* Zhao, Yunfeng; kvm-devel@lists.sourceforge.net > *Subject:* Re: [kvm-devel] build failure on master branch > > Well, it seems hrtimer-compat patch breaks the build. > > HRTIMER_MOD_ABS is declared in enum, so we can’t say: > > #ifndef HRTIMER_MOD_ABS > > #define HRTIMER_MOD_ABS HRTIMER_ABS > > #endif > > maybe something like > > #if LINUX_VERSION_CODE >= KERNEL_VERSION(2.6.?) > > should be OK. > > > > *From:* [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] *On Behalf Of *Zhao, > Yunfeng > *Sent:* 2007年9月10日 10:41 > *To:* kvm-devel@lists.sourceforge.net > *Subject:* [kvm-devel] build failure on master branch > > I meet the following error when I build latest kvm master against > kernel 2.6.22 as external modules. > > And it’s ok if I build it against kvm kernel either build-in or as > external modules. > > /kvm-userspace/BUILD/kernel/lapic.c: In function 'start_apic_timer': > > /kvm-userspace/BUILD/kernel/lapic.c:609: error: 'HRTIMER_ABS' > undeclared (first use in this function) > > /kvm-userspace/BUILD/kernel/lapic.c:609: error: (Each undeclared > identifier is reported only once > > /kvm-userspace/BUILD/kernel/lapic.c:609: error: for each function it > appears in.) > > /kvm-userspace/BUILD/kernel/lapic.c: In function 'kvm_create_lapic': > > /kvm-userspace/BUILD/kernel/lapic.c:953: error: 'HRTIMER_ABS' > undeclared (first use in this function) > > /kvm-userspace/BUILD/kernel/lapic.c: In function 'kvm_migrate_apic_timer': > > /kvm-userspace/BUILD/kernel/lapic.c:1043: error: 'HRTIMER_ABS' > undeclared (first use in this function) > > /kvm-userspace/BUILD/kernel/lapic.o] Error 1 > > make[3]: *** Waiting for unfinished jobs > > make[2]: *** > [_module_/workspace/ia32e/nightly/kvm-master-2.6.22-rc4-20070910090114640/kvm-userspace/BUILD/kernel] > Error 2 > > make[2]: Leaving directory > `/usr/src/redhat/BUILD/kernel-2.6.22rc4g85f6038f' > > make[1]: *** [all] Error 2 > > make[1]: Leaving directory > `/workspace/ia32e/nightly/kvm-master-2.6.22-rc4-20070910090114640/kvm-userspace/BUILD/kernel' > > error: Bad exit status from /var/tmp/rpm-tmp.70011 (%build) > > thanks > > Yunfeng > > > > - > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ > > > ___ > kvm-devel mailing list > kvm-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/kvm-devel > -- error compiling committee.c: too many arguments to function - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] [PATCH 2/3] KVM: fix apic timer save/migration wheninactive
He, Qing wrote:
> resended, due to wrong attachment
>
>
Patch looks good, but needs a changelog comment and a signoff.
>> -Original Message-
>> From: [EMAIL PROTECTED]
>> [mailto:[EMAIL PROTECTED] On Behalf Of He, Qing
>> Sent: 2007年9月10日 13:59
>> To: Avi Kivity
>> Cc: kvm-devel@lists.sourceforge.net
>> Subject: Re: [kvm-devel] [PATCH 2/3] KVM: fix apic timer save/migration
>> wheninactive
>>
>> Avi,
>> This is the updated patch, which avoids inactive hrtimers from
>> unintended
>> migrations.
>>
>> save/restore timer logic is not included because it does not call
>> hrtimer_cancel
>> (hrtimer_active is different). It has relatively small impact, for it only
>> affects save/restore
>> at maybe guest BIOS time, maybe we can defer it to some later time
>>
>>
>>> -Original Message-
>>> From: Avi Kivity [mailto:[EMAIL PROTECTED]
>>> Sent: 2007年9月9日 15:39
>>> To: He, Qing
>>> Cc: kvm-devel@lists.sourceforge.net
>>> Subject: Re: [kvm-devel] [PATCH 2/3] KVM: fix apic timer save/migration
>>> when inactive
>>>
>>> He, Qing wrote:
>>>
>>> +if (atomic_read(&apic->timer.active))
>>>
>>>
>>>
>> Or here?
>>
>>
>>
>>> +hrtimer_start(timer, timer->expires,
>>> + HRTIMER_MODE_ABS);
>>> }
>>> EXPORT_SYMBOL_GPL(kvm_migrate_apic_timer);
>>>
>>>
>>>
>>>
> I think you could use the return value of hrtimer_cancel() here:
>
>if (hrtimer_cancel(...))
>hrtimer_start(...);
>
>
Thanks for commenting, previously I have thought of something like:
if (hrtimer_active(...)) {
hrtimer_cancel(...);
hrtimer_start(...);
}
But it is not able to handle pending state this way. Seems the return
value of
>>> hrtimer_cancel is fine. Another question is, when the hrtimer function
>>> returns
>>> HRTIMER_NORESTART, does the state finally turn to HRTIMER_STATE_INACTIVE?
>>>
>> >From my reading of the hrtimer code, yes. But I would view any code
>>
>>> which depends on the state with suspicion.
>>>
>>>
>>> --
>>> error compiling committee.c: too many arguments to function
>>>
>>>
>>>
>>> -
>>> This SF.net email is sponsored by: Microsoft
>>> Defy all challenges. Microsoft(R) Visual Studio 2005.
>>> http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
>>>
>>>
>>> ___
>>> kvm-devel mailing list
>>> kvm-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/kvm-devel
>>>
--
error compiling committee.c: too many arguments to function
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] unhandled vm exit on kvm36 with Etch 32 guest on AMD64
Joseph Wolff wrote: > Hello, > > I'm getting "unhandled vm exit:0xb8002" running a Debian Etch guest > under kvm36 on AMD64. > > This is a badly reported emulation failure. Is there anything in dmesg like "emulation failed but !mmio_needed?"? -- error compiling committee.c: too many arguments to function - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
[kvm-devel] expose host CPU features to guests: Take 2
As with Take 1 of this patch, its purpose is to expose host CPU features to
guests. It proved rather helpful to KVM in various benchmarks, and it should
similarly speed kqemu up. Note that it does not extend the set of emulated
opcodes, only exposes what's supported by the host CPU.
I changed the patch according to the comments on these mailing lists. Thanks
for your suggestions. Changes since "take 1" are:
- Use the new -cpu option to specify cpu features.
- Read host cpuid directly, instead of parsing /proc/cpuinfo. This approach is
less Linux-centric and should work with other OSs too. It means however, that
the cpuid is not checked for old CPU bugs. In the future, qemu should
negotiate the actually-supported features with the virutalizing kernel
module.
Index: hw/pc.c
===
RCS file: /sources/qemu/qemu/hw/pc.c,v
retrieving revision 1.83
diff -u -r1.83 pc.c
--- hw/pc.c 26 Aug 2007 17:51:39 - 1.83
+++ hw/pc.c 10 Sep 2007 06:54:00 -
@@ -666,7 +666,7 @@
DisplayState *ds, const char **fd_filename, int snapshot,
const char *kernel_filename, const char *kernel_cmdline,
const char *initrd_filename,
- int pci_enabled)
+ int pci_enabled, char *cpu_model)
{
char buf[1024];
int ret, linux_boot, i;
@@ -683,7 +683,9 @@
/* init CPUs */
for(i = 0; i < smp_cpus; i++) {
+void apply_i386_cpu_model(CPUX86State *env, char *cpu_model);
env = cpu_init();
+apply_i386_cpu_model(env, cpu_model);
if (i != 0)
env->hflags |= HF_HALTED_MASK;
if (smp_cpus > 1) {
@@ -948,7 +950,7 @@
pc_init1(ram_size, vga_ram_size, boot_device,
ds, fd_filename, snapshot,
kernel_filename, kernel_cmdline,
- initrd_filename, 1);
+ initrd_filename, 1, cpu_model);
}
static void pc_init_isa(int ram_size, int vga_ram_size, int boot_device,
@@ -962,7 +964,7 @@
pc_init1(ram_size, vga_ram_size, boot_device,
ds, fd_filename, snapshot,
kernel_filename, kernel_cmdline,
- initrd_filename, 0);
+ initrd_filename, 0, cpu_model);
}
QEMUMachine pc_machine = {
Index: target-i386/cpu.h
===
RCS file: /sources/qemu/qemu/target-i386/cpu.h,v
retrieving revision 1.45
diff -u -r1.45 cpu.h
--- target-i386/cpu.h 11 Jul 2007 22:48:58 - 1.45
+++ target-i386/cpu.h 10 Sep 2007 06:54:00 -
@@ -267,21 +267,44 @@
#define CPUID_CMOV (1 << 15)
#define CPUID_PAT (1 << 16)
#define CPUID_PSE36 (1 << 17)
+#define CPUID_PN (1 << 18)
#define CPUID_CLFLUSH (1 << 19)
-/* ... */
+#define CPUID_DTS (1 << 21)
+#define CPUID_ACPI (1 << 22)
#define CPUID_MMX (1 << 23)
#define CPUID_FXSR (1 << 24)
#define CPUID_SSE (1 << 25)
#define CPUID_SSE2 (1 << 26)
+#define CPUID_SS (1 << 27)
+#define CPUID_HT (1 << 28)
+#define CPUID_TM (1 << 29)
+#define CPUID_IA64 (1 << 30)
+#define CPUID_PBE (1 << 31)
#define CPUID_EXT_SSE3 (1 << 0)
#define CPUID_EXT_MONITOR (1 << 3)
+#define CPUID_EXT_DSCPL(1 << 4)
+#define CPUID_EXT_VMX (1 << 5)
+#define CPUID_EXT_SMX (1 << 6)
+#define CPUID_EXT_EST (1 << 7)
+#define CPUID_EXT_TM2 (1 << 8)
+#define CPUID_EXT_SSSE3(1 << 9)
+#define CPUID_EXT_CID (1 << 10)
#define CPUID_EXT_CX16 (1 << 13)
+#define CPUID_EXT_XTPR (1 << 14)
+#define CPUID_EXT_DCA (1 << 17)
+#define CPUID_EXT_POPCNT (1 << 22)
#define CPUID_EXT2_SYSCALL (1 << 11)
+#define CPUID_EXT2_MP (1 << 19)
#define CPUID_EXT2_NX (1 << 20)
+#define CPUID_EXT2_MMXEXT (1 << 22)
#define CPUID_EXT2_FFXSR (1 << 25)
+#define CPUID_EXT2_PDPE1GB (1 << 26)
+#define CPUID_EXT2_RDTSCP (1 << 27)
#define CPUID_EXT2_LM (1 << 29)
+#define CPUID_EXT2_3DNOWEXT (1 << 30)
+#define CPUID_EXT2_3DNOW (1 << 31)
#define EXCP00_DIVZ0
#define EXCP01_SSTP1
Index: target-i386/helper2.c
===
RCS file: /sources/qemu/qemu/target-i386/helper2.c,v
retrieving revision 1.48
diff -u -r1.48 helper2.c
--- target-i386/helper2.c 31 Jul 2007 23:09:18 - 1.48
+++ target-i386/helper2.c 10 Sep 2007 06:54:00 -
@@ -45,40 +45,8 @@
#endif
#endif /* USE_CODE_COPY */
-CPUX86State *cpu_x86_init(void)
+static int set_guest_cpu_basic(CPUX86State *env)
{
-CPUX86State *env;
-static int inited;
-
-env = qemu_mallocz(sizeof(CPUX86State));
-if (!env)
-return NULL;
-cpu_exec_init(env);
-
-/* init various static tables */
-if (!inited) {
-inited = 1;
-optimize_flags_init();
-}
-#ifdef USE_CODE_COPY
-/* testing code for code copy case */
-{
-struct modify_ldt_ldt_s ldt;
-
-ldt.entry_number = 1;
-ldt.base_addr = (unsigned long)e
Re: [kvm-devel] [PATCH 2/3] KVM: fix apic timer save/migration wheninactive
KVM: fix apic timer migration when inactive
When local apic timer is inactive or is expired in one shot mode, it should not
be restarted on vcpu and hrtimer migration. This patch fixes this.
Signed-off-by: Qing He <[EMAIL PROTECTED]>
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
>-Original Message-
>From: Avi Kivity [mailto:[EMAIL PROTECTED]
>Sent: 2007年9月10日 15:27
>To: He, Qing
>Cc: kvm-devel@lists.sourceforge.net
>Subject: Re: [kvm-devel] [PATCH 2/3] KVM: fix apic timer save/migration
>wheninactive
>
>He, Qing wrote:
>> resended, due to wrong attachment
>>
>>
>
>Patch looks good, but needs a changelog comment and a signoff.
>>> -Original Message-
>>> From: [EMAIL PROTECTED]
>>> [mailto:[EMAIL PROTECTED] On Behalf Of He, Qing
>>> Sent: 2007年9月10日 13:59
>>> To: Avi Kivity
>>> Cc: kvm-devel@lists.sourceforge.net
>>> Subject: Re: [kvm-devel] [PATCH 2/3] KVM: fix apic timer save/migration
>wheninactive
>>>
>>> Avi,
>>> This is the updated patch, which avoids inactive hrtimers from
>>> unintended
>>> migrations.
>>>
>>> save/restore timer logic is not included because it does not call
>>> hrtimer_cancel
>>> (hrtimer_active is different). It has relatively small impact, for it only
>>> affects
>save/restore
>>> at maybe guest BIOS time, maybe we can defer it to some later time
>>>
>>>
-Original Message-
From: Avi Kivity [mailto:[EMAIL PROTECTED]
Sent: 2007年9月9日 15:39
To: He, Qing
Cc: kvm-devel@lists.sourceforge.net
Subject: Re: [kvm-devel] [PATCH 2/3] KVM: fix apic timer save/migration
when
>inactive
He, Qing wrote:
+if (atomic_read(&apic->timer.active))
>>> Or here?
>>>
>>>
>>>
+hrtimer_start(timer, timer->expires,
+ HRTIMER_MODE_ABS);
}
EXPORT_SYMBOL_GPL(kvm_migrate_apic_timer);
>> I think you could use the return value of hrtimer_cancel() here:
>>
>>if (hrtimer_cancel(...))
>>hrtimer_start(...);
>>
>>
> Thanks for commenting, previously I have thought of something like:
> if (hrtimer_active(...)) {
> hrtimer_cancel(...);
> hrtimer_start(...);
> }
>
> But it is not able to handle pending state this way. Seems the return
> value of
>
hrtimer_cancel is fine. Another question is, when the hrtimer function
returns
HRTIMER_NORESTART, does the state finally turn to HRTIMER_STATE_INACTIVE?
>>> >From my reading of the hrtimer code, yes. But I would view any code
>>>
which depends on the state with suspicion.
--
error compiling committee.c: too many arguments to function
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel
>
>
>--
>error compiling committee.c: too many arguments to function
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] [PATCH] passing smp cpu count from CMOS
He, Qing wrote:
As discussed previously, this patch directly passes SMP CPU count to the
guest BIOS from CMOS by qemu, instead of sending SIPI and wait. CMOS
offset 0x7f is used.
This is the last functional piece for in-kernel APIC merge in kvm-37.
Signed-off-by: Qing He <[EMAIL PROTECTED]>
diff --git a/bios/rombios32.c b/bios/rombios32.c
index faf771e..3bb5e00 100755
--- a/bios/rombios32.c
+++ b/bios/rombios32.c
@@ -41,6 +41,9 @@ typedef unsigned long long uint64_t;
/* define it if the (emulated) hardware supports SMM mode */
#define BX_USE_SMM
+/* read CPU count from CMOS directly instead of probing */
+#define BX_CMOS_CPU_COUNT
+
#define cpuid(index, eax, ebx, ecx, edx) \
asm volatile ("cpuid" \
: "=a" (eax), "=b" (ebx), "=c" (ecx), "=d" (edx) \
@@ -442,9 +445,13 @@ void smp_probe(void)
sipi_vector = AP_BOOT_ADDR >> 12;
writel(APIC_BASE + APIC_ICR_LOW, 0x000C4600 | sipi_vector);
+#ifdef BX_CMOS_CPU_COUNT
+smp_cpus = cmos_readb(0x7f);
+#else
delay_ms(10);
smp_cpus = readw((void *)CPU_COUNT_ADDR);
+#endif
This means there's no BIOS SIPI, which is a little sad as it doesn't
exercise the lapic machinery.
diff --git a/qemu/hw/mc146818rtc.c b/qemu/hw/mc146818rtc.c
index bad4cbd..3c4c25d 100644
--- a/qemu/hw/mc146818rtc.c
+++ b/qemu/hw/mc146818rtc.c
@@ -33,6 +33,9 @@
#define RTC_HOURS_ALARM 5
#define RTC_ALARM_DONT_CARE0xC0
+/* KVM specific extension: smp cpu count passing */
+#define RTC_CMOS_CPU_COUNT 0x7f
+
#define RTC_DAY_OF_WEEK 6
#define RTC_DAY_OF_MONTH7
#define RTC_MONTH 8
@@ -356,6 +359,9 @@ static uint32_t cmos_ioport_read(void *opaque,
uint32_t addr)
pic_set_irq(s->irq, 0);
s->cmos_data[RTC_REG_C] = 0x00;
break;
+case RTC_CMOS_CPU_COUNT:
+ret = smp_cpus;
+break;
This really shouldn't be done from within the rtc.
Alternative patch attached, but works only with -no-kvm-irqchip.
--
error compiling committee.c: too many arguments to function
diff --git a/bios/BIOS-bochs-latest b/bios/BIOS-bochs-latest
index 4388ff2..c10ae62 100644
Binary files a/bios/BIOS-bochs-latest and b/bios/BIOS-bochs-latest differ
diff --git a/bios/BIOS-bochs-legacy b/bios/BIOS-bochs-legacy
index a720312..131e62b 100644
Binary files a/bios/BIOS-bochs-legacy and b/bios/BIOS-bochs-legacy differ
diff --git a/bios/rombios32.c b/bios/rombios32.c
index 816e5cc..1917b1c 100755
--- a/bios/rombios32.c
+++ b/bios/rombios32.c
@@ -441,7 +441,12 @@ void smp_probe(void)
sipi_vector = AP_BOOT_ADDR >> 12;
writel(APIC_BASE + APIC_ICR_LOW, 0x000C4600 | sipi_vector);
+#ifndef BX_QEMU
delay_ms(10);
+#else
+ while (cmos_readb(0x5f) + 1 != readw((void *)CPU_COUNT_ADDR))
+ ;
+#endif
smp_cpus = readw((void *)CPU_COUNT_ADDR);
}
diff --git a/qemu/hw/pc.c b/qemu/hw/pc.c
index d3b8786..7c6ceb1 100644
--- a/qemu/hw/pc.c
+++ b/qemu/hw/pc.c
@@ -163,7 +163,7 @@ static void cmos_init_hd(int type_ofs, int info_ofs, BlockDriverState *hd)
}
/* hd_table must contain 4 block drivers */
-static void cmos_init(ram_addr_t ram_size, ram_addr_t above_4g_mem_size, int boot_device, BlockDriverState **hd_table)
+static void cmos_init(ram_addr_t ram_size, ram_addr_t above_4g_mem_size, int boot_device, BlockDriverState **hd_table, int smp_cpus)
{
RTCState *s = rtc_state;
int val;
@@ -190,6 +190,7 @@ static void cmos_init(ram_addr_t ram_size, ram_addr_t above_4g_mem_size, int boo
rtc_set_memory(s, 0x5c, (unsigned int)above_4g_mem_size >> 24);
rtc_set_memory(s, 0x5d, above_4g_mem_size >> 32);
}
+rtc_set_memory(s, 0x5f, smp_cpus - 1);
if (ram_size > (16 * 1024 * 1024))
val = (ram_size / 65536) - ((16 * 1024 * 1024) / 65536);
@@ -778,7 +779,7 @@ static void pc_init1(ram_addr_t ram_size, int vga_ram_size, int boot_device,
floppy_controller = fdctrl_init(6, 2, 0, 0x3f0, fd_table);
-cmos_init(ram_size, above_4g_mem_size, boot_device, bs_table);
+cmos_init(ram_size, above_4g_mem_size, boot_device, bs_table, smp_cpus);
if (pci_enabled && usb_enabled) {
usb_uhci_init(pci_bus, piix3_devfn + 2);
diff --git a/qemu/pc-bios/bios.bin b/qemu/pc-bios/bios.bin
index 4388ff2..c10ae62 100644
Binary files a/qemu/pc-bios/bios.bin and b/qemu/pc-bios/bios.bin differ
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel
[kvm-devel] two warning messages while compiling 32bit kvm modules
Get two warning messages while compiling 32bit kvm.ko. CC [M] /workspace/tmp/37/kvm-37/kernel/lapic.o CC [M] /workspace/tmp/37/kvm-37/kernel/ioapic.o CC [M] /workspace/tmp/37/kvm-37/kernel/preempt.o LD [M] /workspace/tmp/37/kvm-37/kernel/kvm.o LD [M] /workspace/tmp/37/kvm-37/kernel/kvm-intel.o LD [M] /workspace/tmp/37/kvm-37/kernel/kvm-amd.o Building modules, stage 2. MODPOST 3 modules WARNING: "genapic" [/workspace/tmp/37/kvm-37/kernel/kvm.ko] undefined! WARNING: "__divdi3" [/workspace/tmp/37/kvm-37/kernel/kvm.ko] undefined! 64bit kvm hasn't the issue. Thanks Yunfeng - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
[kvm-devel] [ kvm-Bugs-1791444 ] [kvm-37]guest timer 2 times faster than network timer
Bugs item #1791444, was opened at 2007-09-10 16:43 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=1791444&group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: yunfeng (yunfeng) Assigned to: Nobody/Anonymous (nobody) Summary: [kvm-37]guest timer 2 times faster than network timer Initial Comment: Environment: HOST (ia32/ia32e/IA64): RHEL5, 2.6.22 kernel GUEST (ia32/ia32e/IA64): RHEL5 COMMIT: kvm-37 Hardware: Bensley/woodcrest 4 CPUS Bug detailed description: -- On KVM 37, timer of linux guest is very accurate. On UP linux guest, guest timer is 2 times faster than network timer. Here is some data of kernel build. kernelbuild Network-time 453s Guest-time 905s A strange thing is "real != user + sys" in the output of "time (make -j4 bzImage)". real 910.28 user 73.83 sys 377.03 Reproduce steps: -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1791444&group_id=180599 - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] two warning messages while compiling 32bit kvm modules
Zhao, Yunfeng wrote: > Get two warning messages while compiling 32bit kvm.ko. > > CC [M] /workspace/tmp/37/kvm-37/kernel/lapic.o > CC [M] /workspace/tmp/37/kvm-37/kernel/ioapic.o > CC [M] /workspace/tmp/37/kvm-37/kernel/preempt.o > LD [M] /workspace/tmp/37/kvm-37/kernel/kvm.o > LD [M] /workspace/tmp/37/kvm-37/kernel/kvm-intel.o > LD [M] /workspace/tmp/37/kvm-37/kernel/kvm-amd.o > Building modules, stage 2. > MODPOST 3 modules > WARNING: "genapic" [/workspace/tmp/37/kvm-37/kernel/kvm.ko] undefined! > What host kernel are you using? I don't see this on 2.6.23-rc3. > WARNING: "__divdi3" [/workspace/tmp/37/kvm-37/kernel/kvm.ko] undefined! > > This one is already fixed in kvm.git. -- error compiling committee.c: too many arguments to function - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] two warning messages while compiling 32bit kvm modules
I am using 2.6.22 kernel. >> > >What host kernel are you using? I don't see this on 2.6.23-rc3. > >> WARNING: "__divdi3" [/workspace/tmp/37/kvm-37/kernel/kvm.ko] undefined! >> >> > >This one is already fixed in kvm.git. > > >-- >error compiling committee.c: too many arguments to function - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
[kvm-devel] [ kvm-Bugs-1791448 ] [KVM-37]guest crashes when booting with 4 vcpus
Bugs item #1791448, was opened at 2007-09-10 16:54 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=1791448&group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: yunfeng (yunfeng) Assigned to: Nobody/Anonymous (nobody) Summary: [KVM-37]guest crashes when booting with 4 vcpus Initial Comment: Environment: HOST (ia32/ia32e/IA64): RHEL5+2.6.22 kernel,64bit GUEST (ia32/ia32e/IA64): RHEL5 64bit COMMIT: kvm-37 Hardware: harwitch/paxvile 16LPs Bug detailed description: -- KVM-37 cannot boot smp linux guest with 4 vcpus. The guest crashed immediately after executed the qemu command. If booting with 2 vcpus, the guest could be booted up but could only see one cpu info in the linux guests. [EMAIL PROTECTED] xvs]# /usr/kvm/bin/qemu-system-x86_64 -m 1024 -net nic,macaddr=00:11:22:33:44:55,model=rtl8139 -net tap,script=/etc/kvm/qemu-ifup -hda /dev/sda -smp 4 exception 6 (0) rax rbx rcx rdx 0600 rsi rdi rsp fffe rbp r8 r9 r10 r11 r12 r13 r14 r15 rip 0003 rflags 00033082 cs (/ p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) ds (/ p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) es (/ p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) ss (/ p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) fs (/ p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) gs (/ p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) tr (4085/2088 p 1 dpl 0 db 0 s 0 type b l 0 g 0 avl 0) ldt (/ p 1 dpl 0 db 0 s 0 type 2 l 0 g 0 avl 0) gdt 0/ idt 0/ cr0 6010 cr2 0 cr3 0 cr4 0 cr8 0 efer 0 code: 54 ff 00 --> f0 53 ff 00 f0 53 ff 00 f0 53 ff 00 f0 53 ff 00 f0 53 ff 00 f0 53 ff 00 f0 53 ff 00 f0 a5 fe 00 f0 87 e9 00 f0 53 ff 00 f0 53 ff 00 f0 53 ff Reproduce steps: Current result: Expected result: Basic root-causing log: -- -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1791448&group_id=180599 - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] kvm-37 problem w/ 64-bit division in lapic.c
[EMAIL PROTECTED] wrote: > On Sun, 09 Sep 2007 14:05:13 +0300 > Avi Kivity wrote: > >> This release merges the pic/lapic/ioapic into mainline. While some >> known issues exist, we're now at the point where it's better to get >> some wider exposure rather than keep it alone on a branch. >> >> Some regressions are expected; please report them as they appear. A >> new qmeu option -no-kvm-irqchip is available to disable the new >> functionality. > > (message seems to get stuck at gmane, sorry if it appears twice > eventually) > > My experience so far: > > On 32-bit Intel host, lapic fails to link due to missing 64bit > division. I tried the attached patch to fix the build, but Windows > XP froze before showing the booting screen. With -no-kvm-irqchip > they work, except the IE plugins like Flash & Java, which are broken > since kvm-29. With -no-kvm, qemu-system-x86_64 segfaults immediately. > > Regards, > -- > Jindrich Makovicka div64_32 is enough, does this function exist? - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] kvm-37 problem w/ 64-bit division in lapic.c
On 9/10/07, Dong, Eddie <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] wrote: > > On Sun, 09 Sep 2007 14:05:13 +0300 > > Avi Kivity wrote: > > > >> This release merges the pic/lapic/ioapic into mainline. While some > >> known issues exist, we're now at the point where it's better to get > >> some wider exposure rather than keep it alone on a branch. > >> > >> Some regressions are expected; please report them as they appear. A > >> new qmeu option -no-kvm-irqchip is available to disable the new > >> functionality. > > > > (message seems to get stuck at gmane, sorry if it appears twice > > eventually) > > > > My experience so far: > > > > On 32-bit Intel host, lapic fails to link due to missing 64bit > > division. I tried the attached patch to fix the build, but Windows > > XP froze before showing the booting screen. With -no-kvm-irqchip > > they work, except the IE plugins like Flash & Java, which are broken > > since kvm-29. With -no-kvm, qemu-system-x86_64 segfaults immediately. > > > > Regards, > > -- > > Jindrich Makovicka > > div64_32 is enough, does this function exist? afaik, __div64_32 is architecture specific, but do_div() could be actually used here. -- Jindrich Makovicka - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] Build of kvm-37 fails
Le 10/09/07, Gildas<[EMAIL PROTECTED]> a écrit : > Hi Avi, > > I had the same problem on a laptop with Core2 T7200 @ 2.00GHz > running ubuntu with kernel 2.6.20 > > Going in the kvm-37 source directory and applying the patch with > > patch -p1 > fixed the compilation problem for me but the VM I've tried crash with > > exception 6 (0) > rax rbx rcx rdx > 0600 > rsi rdi rsp fffe rbp > > r8 r9 r10 r11 > > r12 r13 r14 r15 > > rip 0003 rflags 00033082 > cs (/ p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) > ds (/ p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) > es (/ p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) > ss (/ p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) > fs (/ p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) > gs (/ p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) > tr (3085/2088 p 1 dpl 0 db 0 s 0 type b l 0 g 0 avl 0) > ldt (/ p 1 dpl 0 db 0 s 0 type 2 l 0 g 0 avl 0) > gdt 0/ > idt 0/ > cr0 6010 cr2 0 cr3 0 cr4 0 cr8 0 efer 0 > code: 54 ff 00 --> f0 53 ff 00 f0 53 ff 00 f0 53 ff 00 f0 53 ff 00 f0 > 53 ff 00 f0 53 ff 00 f0 53 ff 00 f0 a5 fe 00 f0 87 e9 00 f0 53 ff 00 > f0 53 ff 00 f0 53 ff > > They runned fine with kvm-36 but now they crash even with -no-kvm. I did further tests after I saw the bug report about the crash related to smp: I was running my vm with -smp 2. If I remove this option, they run fine. Cheers Gildas > 2007/9/9, Avi Kivity <[EMAIL PROTECTED]>: > > Pelle wrote: > > > Hi, > > > > > > I tried to compile the new kvm-37, and got the following errors: > > > > > > regards, Pelle > > > > > > > > > > > > > Does the attached patch help? > > > > -- > > error compiling committee.c: too many arguments to function > > > > > > - > > This SF.net email is sponsored by: Microsoft > > Defy all challenges. Microsoft(R) Visual Studio 2005. > > http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ > > ___ > > kvm-devel mailing list > > kvm-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/kvm-devel > > > > > > > - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] Build of kvm-37 fails
The patch fixes build problems, however the modules won't load properly, I don't know if this is a seperate issue or not. kernel is ubuntu feisty 2.6.20-16-generic $sudo modprobe kvm-intel WARNING: Error inserting kvm (/lib/modules/2.6.20-16-generic/extra/kvm.ko): Unknown symbol in module, or unknown parameter (see dmesg) FATAL: Error inserting kvm_intel (/lib/modules/2.6.20-16-generic/extra/kvm-intel.ko): Unknown symbol in module, or unknown parameter (see dmesg) $dmesg [54716.482444] kvm: Unknown symbol __divdi3 [54716.492596] kvm_intel: Unknown symbol kvm_lapic_reset [54716.492638] kvm_intel: Unknown symbol kvm_migrate_apic_timer [54716.492684] kvm_intel: Unknown symbol set_cr3 [54716.492750] kvm_intel: Unknown symbol kvm_put_guest_fpu [54716.492783] kvm_intel: Unknown symbol kvm_timer_intr_post [54716.492816] kvm_intel: Unknown symbol gfn_to_page [54716.492855] kvm_intel: Unknown symbol segment_base [54716.492888] kvm_intel: Unknown symbol kvm_get_msr_common [54716.492925] kvm_intel: Unknown symbol kvm_vcpu_uninit [54716.492959] kvm_intel: Unknown symbol kvm_emulate_halt [54716.492992] kvm_intel: Unknown symbol kvm_set_apic_base [54716.493025] kvm_intel: Unknown symbol kvm_get_apic_base [54716.493058] kvm_intel: Unknown symbol kvm_load_guest_fpu [54716.493100] kvm_intel: Unknown symbol kvm_lapic_find_highest_irr [54716.493133] kvm_intel: Unknown symbol emulator_write_emulated [54716.493167] kvm_intel: Unknown symbol kvm_exit_arch [54716.493202] kvm_intel: Unknown symbol emulate_instruction [54716.493244] kvm_intel: Unknown symbol kvm_inject_pending_timer_irqs [54716.493282] kvm_intel: Unknown symbol special_reload_dr7 [54716.493316] kvm_intel: Unknown symbol fx_init [54716.493349] kvm_intel: Unknown symbol kvm_create_lapic [54716.493386] kvm_intel: Unknown symbol in_special_section [54716.493428] kvm_intel: Unknown symbol set_cr4 [54716.493462] kvm_intel: Unknown symbol kvm_cpu_has_interrupt [54716.493496] kvm_intel: Unknown symbol kvm_lapic_get_cr8 [54716.493544] kvm_intel: Unknown symbol lmsw [54716.493577] kvm_intel: Unknown symbol kvm_hypercall [54716.493610] kvm_intel: Unknown symbol kvm_vcpu_cache [54716.493644] kvm_intel: Unknown symbol get_cr8 [54716.493679] kvm_intel: Unknown symbol end_special_insn [54716.493731] kvm_intel: Unknown symbol kvm_init_arch [54716.493777] kvm_intel: Unknown symbol set_cr0 [54716.493811] kvm_intel: Unknown symbol kvm_lapic_enabled [54716.493843] kvm_intel: Unknown symbol emulator_read_std [54716.493883] kvm_intel: Unknown symbol start_special_insn [54716.493922] kvm_intel: Unknown symbol set_cr8 [54716.493955] kvm_intel: Unknown symbol kvm_emulate_cpuid [54716.493992] kvm_intel: Unknown symbol kvm_vcpu_init [54716.494034] kvm_intel: Unknown symbol kvm_set_msr_common [54716.494074] kvm_intel: Unknown symbol kvm_mmu_load [54716.494108] kvm_intel: Unknown symbol kvm_cpu_get_interrupt [54716.494141] kvm_intel: Unknown symbol kvm_emulate_pio [54716.494174] kvm_intel: Unknown symbol kvm_resched Avi Kivity wrote: > Pelle wrote: >> Hi, >> >> I tried to compile the new kvm-37, and got the following errors: >> >> regards, Pelle >> >> >> > > Does the attached patch help? > - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] Build of kvm-37 fails
On 9/10/07, Pelle <[EMAIL PROTECTED]> wrote: > The patch fixes build problems, however the modules won't load properly, > I don't know if this is a seperate issue or not. > > kernel is ubuntu feisty 2.6.20-16-generic > > $sudo modprobe kvm-intel > WARNING: Error inserting kvm > (/lib/modules/2.6.20-16-generic/extra/kvm.ko): Unknown symbol in module, > or unknown parameter (see dmesg) > FATAL: Error inserting kvm_intel > (/lib/modules/2.6.20-16-generic/extra/kvm-intel.ko): Unknown symbol in > module, or unknown parameter (see dmesg) > > $dmesg > [54716.482444] kvm: Unknown symbol __divdi3 kvm.ko fails to load due to a 64 bit division, see: http://git.kernel.org/?p=linux/kernel/git/avi/kvm.git;a=commitdiff;h=e44af0f4ee99974ce40102e23784bc3cae7f4466 Luca > > [54716.492596] kvm_intel: Unknown symbol kvm_lapic_reset > [54716.492638] kvm_intel: Unknown symbol kvm_migrate_apic_timer > [54716.492684] kvm_intel: Unknown symbol set_cr3 > [54716.492750] kvm_intel: Unknown symbol kvm_put_guest_fpu > [54716.492783] kvm_intel: Unknown symbol kvm_timer_intr_post > [54716.492816] kvm_intel: Unknown symbol gfn_to_page > [54716.492855] kvm_intel: Unknown symbol segment_base > [54716.492888] kvm_intel: Unknown symbol kvm_get_msr_common > [54716.492925] kvm_intel: Unknown symbol kvm_vcpu_uninit > [54716.492959] kvm_intel: Unknown symbol kvm_emulate_halt > [54716.492992] kvm_intel: Unknown symbol kvm_set_apic_base > [54716.493025] kvm_intel: Unknown symbol kvm_get_apic_base > [54716.493058] kvm_intel: Unknown symbol kvm_load_guest_fpu > [54716.493100] kvm_intel: Unknown symbol kvm_lapic_find_highest_irr > [54716.493133] kvm_intel: Unknown symbol emulator_write_emulated > [54716.493167] kvm_intel: Unknown symbol kvm_exit_arch > [54716.493202] kvm_intel: Unknown symbol emulate_instruction > [54716.493244] kvm_intel: Unknown symbol kvm_inject_pending_timer_irqs > [54716.493282] kvm_intel: Unknown symbol special_reload_dr7 > [54716.493316] kvm_intel: Unknown symbol fx_init > [54716.493349] kvm_intel: Unknown symbol kvm_create_lapic > [54716.493386] kvm_intel: Unknown symbol in_special_section > [54716.493428] kvm_intel: Unknown symbol set_cr4 > [54716.493462] kvm_intel: Unknown symbol kvm_cpu_has_interrupt > [54716.493496] kvm_intel: Unknown symbol kvm_lapic_get_cr8 > [54716.493544] kvm_intel: Unknown symbol lmsw > [54716.493577] kvm_intel: Unknown symbol kvm_hypercall > [54716.493610] kvm_intel: Unknown symbol kvm_vcpu_cache > [54716.493644] kvm_intel: Unknown symbol get_cr8 > [54716.493679] kvm_intel: Unknown symbol end_special_insn > [54716.493731] kvm_intel: Unknown symbol kvm_init_arch > [54716.493777] kvm_intel: Unknown symbol set_cr0 > [54716.493811] kvm_intel: Unknown symbol kvm_lapic_enabled > [54716.493843] kvm_intel: Unknown symbol emulator_read_std > [54716.493883] kvm_intel: Unknown symbol start_special_insn > [54716.493922] kvm_intel: Unknown symbol set_cr8 > [54716.493955] kvm_intel: Unknown symbol kvm_emulate_cpuid > [54716.493992] kvm_intel: Unknown symbol kvm_vcpu_init > [54716.494034] kvm_intel: Unknown symbol kvm_set_msr_common > [54716.494074] kvm_intel: Unknown symbol kvm_mmu_load > [54716.494108] kvm_intel: Unknown symbol kvm_cpu_get_interrupt > [54716.494141] kvm_intel: Unknown symbol kvm_emulate_pio > [54716.494174] kvm_intel: Unknown symbol kvm_resched > > > Avi Kivity wrote: > > Pelle wrote: > >> Hi, > >> > >> I tried to compile the new kvm-37, and got the following errors: > >> > >> regards, Pelle > >> > >> > >> > > > > Does the attached patch help? > > > > - > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ > ___ > kvm-devel mailing list > kvm-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/kvm-devel > - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] unhandled vm exit on kvm36 with Etch 32 guest on AMD64
Using kvm-37, I was able to install a debian guest using debian-40r0-i386-DVD-1.iso, and run it, on both AMD and Intel machine. My hosts are both running Fedora 7 with linux kernel versions 2.6.21-1 and 2.6.23-rc3. Does your guest boot when adding '-no-kvm' to the command line ? Uri. Joseph Wolff wrote: > Hello, > > I'm getting "unhandled vm exit:0xb8002" running a Debian Etch guest > under kvm36 on AMD64. > > The host is a 4-core dual-dual AMD, and I was able to create the Debian > Etch (4.0) guest image just fine, using a standard install, from the > standard Debian DVD disc1: debian-40r0-i386-DVD-1.iso > > Distro is Ubuntu Gutsy, kernel is brand-new 2.6.22-11-server from the > Gutsy repo. The KVM36 was installed via apt-pinning from the Debian > (sid) repo (they're compatible - dependencies all met). The KVM36 is the > only thing from the sid repo. > > I originally upgraded to kvm36 because I was having this problem on the > default Gutsy kvm28, and the Guest Status page for Etch says kvm29 works > (albeit with Intel), but this is the same error I was getting with kvm28. > > > Here's the commandline and the subsequent regdump: > > [EMAIL PROTECTED]:/vm/143# kvm -vnc :1 -k en-us -net > nic,macaddr=de:ad:be:ef:01:43 -net tap -monitor > telnet::23143,server,nowait,nodelay -cdrom > /iso/debian-40r0-i386-DVD-1.iso -append vga=771 debian-40r0-i386.8G.qc2 > > In /etc/kvm/kvm-ifup, adding: tap0 > > unhandled vm exit: 0xb8002 > rax c0318000 rbx 0fa0 rcx 0fa0 rdx > c00b8000 > rsi c00b8000 rdi c110a980 rsp c0319fb8 rbp > c110a980 > r8 r9 r10 r11 > > r12 r13 r14 r15 > > rip c01bc276 rflags 0206 > cs 0060 (/ p 1 dpl 0 db 1 s 1 type b l 0 g 0 avl 0) > ds 007b (/ p 1 dpl 3 db 1 s 1 type 2 l 0 g 1 avl 0) > es 007b (/ p 1 dpl 3 db 1 s 1 type 3 l 0 g 1 avl 0) > ss 0068 (/ p 1 dpl 0 db 1 s 1 type 2 l 0 g 1 avl 0) > fs (/ p 0 dpl 0 db 0 s 0 type 0 l 0 g 0 avl 0) > gs (/ p 0 dpl 0 db 0 s 0 type 0 l 0 g 0 avl 0) > tr 0080 (c11006c0/2073 p 1 dpl 0 db 0 s 0 type 9 l 0 g 0 avl 0) > ldt 0088 (c0352020/0027 p 1 dpl 0 db 0 s 0 type 2 l 0 g 0 avl 0) > gdt c1109000/ff > idt c030f000/7ff > cr0 80050033 cr2 0 cr3 34f000 cr4 690 cr8 0 efer 0 > Aborted > [EMAIL PROTECTED]:/vm/143# > > > > Let me know, > > Cheers, > joe > > > > - > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ > ___ > kvm-devel mailing list > kvm-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/kvm-devel > - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] [PATCH] passing smp cpu count from CMOS
Avi Kivity wrote: > > Alternative patch attached, but works only with -no-kvm-irqchip. > > After removing smp_processor_id() from kvm_vcpu_kick() it works fairly well, unfortunately that means there's a timing issue with kernel lapic. -- error compiling committee.c: too many arguments to function - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] Build of kvm-37 fails
Hi Avi, I had the same problem on a laptop with Core2 T7200 @ 2.00GHz running ubuntu with kernel 2.6.20 Going in the kvm-37 source directory and applying the patch with patch -p1 f0 53 ff 00 f0 53 ff 00 f0 53 ff 00 f0 53 ff 00 f0 53 ff 00 f0 53 ff 00 f0 53 ff 00 f0 a5 fe 00 f0 87 e9 00 f0 53 ff 00 f0 53 ff 00 f0 53 ff They runned fine with kvm-36 but now they crash even with -no-kvm. Cheers Gildas 2007/9/9, Avi Kivity <[EMAIL PROTECTED]>: > Pelle wrote: > > Hi, > > > > I tried to compile the new kvm-37, and got the following errors: > > > > regards, Pelle > > > > > > > > Does the attached patch help? > > -- > error compiling committee.c: too many arguments to function > > > - > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ > ___ > kvm-devel mailing list > kvm-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/kvm-devel > > > - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] build failure on master branch
Hi, Avi The issue still exists on the latest kvm-userspace.git. Did you push the change to master? Thanks Yunfeng >-Original Message- >From: Avi Kivity [mailto:[EMAIL PROTECTED] >Sent: 2007年9月10日 15:24 >To: He, Qing >Cc: Zhao, Yunfeng; kvm-devel@lists.sourceforge.net >Subject: Re: [kvm-devel] build failure on master branch > >He, Qing wrote: >> >> You can try the attached patch to see if it works >> > >Ouch. Applied, thanks. > >> >> >> *From:* [EMAIL PROTECTED] >> [mailto:[EMAIL PROTECTED] *On Behalf Of *He, Qing >> *Sent:* 2007年9月10日 10:55 >> *To:* Zhao, Yunfeng; kvm-devel@lists.sourceforge.net >> *Subject:* Re: [kvm-devel] build failure on master branch >> >> Well, it seems hrtimer-compat patch breaks the build. >> >> HRTIMER_MOD_ABS is declared in enum, so we can’t say: >> >> #ifndef HRTIMER_MOD_ABS >> >> #define HRTIMER_MOD_ABS HRTIMER_ABS >> >> #endif >> >> maybe something like >> >> #if LINUX_VERSION_CODE >= KERNEL_VERSION(2.6.?) >> >> should be OK. >> >> >> >> *From:* [EMAIL PROTECTED] >> [mailto:[EMAIL PROTECTED] *On Behalf Of *Zhao, >> Yunfeng >> *Sent:* 2007年9月10日 10:41 >> *To:* kvm-devel@lists.sourceforge.net >> *Subject:* [kvm-devel] build failure on master branch >> >> I meet the following error when I build latest kvm master against >> kernel 2.6.22 as external modules. >> >> And it’s ok if I build it against kvm kernel either build-in or as >> external modules. >> >> /kvm-userspace/BUILD/kernel/lapic.c: In function 'start_apic_timer': >> >> /kvm-userspace/BUILD/kernel/lapic.c:609: error: 'HRTIMER_ABS' >> undeclared (first use in this function) >> >> /kvm-userspace/BUILD/kernel/lapic.c:609: error: (Each undeclared >> identifier is reported only once >> >> /kvm-userspace/BUILD/kernel/lapic.c:609: error: for each function it >> appears in.) >> >> /kvm-userspace/BUILD/kernel/lapic.c: In function 'kvm_create_lapic': >> >> /kvm-userspace/BUILD/kernel/lapic.c:953: error: 'HRTIMER_ABS' >> undeclared (first use in this function) >> >> /kvm-userspace/BUILD/kernel/lapic.c: In function 'kvm_migrate_apic_timer': >> >> /kvm-userspace/BUILD/kernel/lapic.c:1043: error: 'HRTIMER_ABS' >> undeclared (first use in this function) >> >> /kvm-userspace/BUILD/kernel/lapic.o] Error 1 >> >> make[3]: *** Waiting for unfinished jobs >> >> make[2]: *** >> >[_module_/workspace/ia32e/nightly/kvm-master-2.6.22-rc4-20070910090114640/k >vm-userspace/BUILD/kernel] >> Error 2 >> >> make[2]: Leaving directory >> `/usr/src/redhat/BUILD/kernel-2.6.22rc4g85f6038f' >> >> make[1]: *** [all] Error 2 >> >> make[1]: Leaving directory >> >`/workspace/ia32e/nightly/kvm-master-2.6.22-rc4-20070910090114640/kvm-users >pace/BUILD/kernel' >> >> error: Bad exit status from /var/tmp/rpm-tmp.70011 (%build) >> >> thanks >> >> Yunfeng >> >> >> >> - >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2005. >> http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ >> >> >> ___ >> kvm-devel mailing list >> kvm-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/kvm-devel >> > > >-- >error compiling committee.c: too many arguments to function - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] build failure on master branch
Zhao, Yunfeng wrote: > Hi, Avi > The issue still exists on the latest kvm-userspace.git. > Did you push the change to master? > Pushed now, thanks for the remainder. -- error compiling committee.c: too many arguments to function - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
[kvm-devel] kvm: Unknown symbol genapic
I can compile latest kvm.git as external modules of 2.6.22 kernel successfully. But I cannot insert kvm.ko. It failed with the error: kvm: Unknown symbol genapic thanks Yunfeng - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] kvm: Unknown symbol genapic
Zhao, Yunfeng wrote: > I can compile latest kvm.git as external modules of 2.6.22 kernel > successfully. > But I cannot insert kvm.ko. > It failed with the error: > kvm: Unknown symbol genapic > > Is this on i386 or x86_64? -- error compiling committee.c: too many arguments to function - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] kvm: Unknown symbol genapic
It's on x86_64. Thanks Yunfeng >-Original Message- >From: Avi Kivity [mailto:[EMAIL PROTECTED] >Sent: 2007年9月10日 23:15 >To: Zhao, Yunfeng >Cc: kvm-devel@lists.sourceforge.net >Subject: Re: [kvm-devel] kvm: Unknown symbol genapic > >Zhao, Yunfeng wrote: >> I can compile latest kvm.git as external modules of 2.6.22 kernel >> successfully. >> But I cannot insert kvm.ko. >> It failed with the error: >> kvm: Unknown symbol genapic >> >> > >Is this on i386 or x86_64? > > > > >-- >error compiling committee.c: too many arguments to function - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
[kvm-devel] rpms for kvm on centos
hi, for those of you who can't wait for the centos testing rpms i recompile a few packages for centos-5: https://www.lfarkas.org/linux/packages/centos/5/ there's no support for it and the centos repositories are always better then these packages:-) -- Levente "Si vis pacem para bellum!" - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] Using VMChannel to communicate with the host.
Dor Laor wrote: > I just tested it, it got a little deprecated over time since it call > pci_module_init instead of pci_register_* and some more irq function > deprecation.The sysfs interface in not complete and you can't read/write > from the device. > The qemu parameters are -vmchannel di:2258,unix:/tmp/file,server > 2258 is the vendor id for the device, you can use unix sockets ot even > tcp for the host end. > Hi Dor, Thanks, that got it up and running. But in the hypercall.c code (from the git repo) there is a "hello host" message that looks like it should be written to the host. How do I trigger that to be sent so my very simple "listening" program can read it? Thanks, Cam - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
[kvm-devel] caveman1
Wassup Dima My wife complains about my small cock ALL THE TIME! Xiahui Linnemann http://lxpeople.com/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] kvm-37 problem w/ 64-bit division in lapic.c
On Mon, 10 Sep 2007 11:49:02 +0200 "Jindrich Makovicka" <[EMAIL PROTECTED]> wrote: > On 9/10/07, Dong, Eddie <[EMAIL PROTECTED]> wrote: > > div64_32 is enough, does this function exist? > > afaik, __div64_32 is architecture specific, but do_div() could be > actually used here. This version should be faster. Signed-off-by: Jindrich Makovicka <[EMAIL PROTECTED]> -- Jindrich Makovicka lapic.c.diff2 Description: Binary data - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] unhandled vm exit on kvm36 with Etch 32 guest on AMD64
Here's the dmesg snippet from the run: [47823.616622] device tap0 entered promiscuous mode [47823.616633] audit(1189441272.489:14): dev=tap0 prom=256 old_prom=0 auid=4294967295 [47823.616638] br0: port 2(tap0) entering learning state [47830.252510] pf_interception: emulate fail [47830.308439] br0: port 2(tap0) entering disabled state [47830.351370] device tap0 left promiscuous mode [47830.351386] audit(1189441279.240:15): dev=tap0 prom=0 old_prom=256 auid=4294967295 [47830.351390] br0: port 2(tap0) entering disabled state So just the "pf_interception: emulate fail" is all. joe Avi Kivity wrote: > Joseph Wolff wrote: >> Hello, >> >> I'm getting "unhandled vm exit:0xb8002" running a Debian Etch guest >> under kvm36 on AMD64. >> >> > > This is a badly reported emulation failure. > > Is there anything in dmesg like "emulation failed but !mmio_needed?"? > > - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] [Qemu-devel] Re: expose host CPU features to guests
Paul Brook wrote: > > > What you really want to do is ask your virtualization module what > > > features it supports. > > > > Yes, that needs to be an additional filter. > > I'd have thought that would be the *only* interesting set for autodetection. If that means the same as the features which are efficient for the guest, then I agree. If there's a difference, I'd have thought you'd normally want the guest to use only those features which work at near-native performance, not those which involve a trap and long path through the virtualisation/emulation, even if they're supported. No example comes to mind, but that seems like the principle to go for, to me. -- Jamie - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] kvm: Unknown symbol genapic
Zhao, Yunfeng wrote: > It's on x86_64. > > Thanks > Yunfeng > > >> -Original Message- >> From: Avi Kivity [mailto:[EMAIL PROTECTED] >> Sent: 2007年9月10日 23:15 >> To: Zhao, Yunfeng >> Cc: kvm-devel@lists.sourceforge.net >> Subject: Re: [kvm-devel] kvm: Unknown symbol genapic >> >> Zhao, Yunfeng wrote: >> >>> I can compile latest kvm.git as external modules of 2.6.22 kernel >>> successfully. >>> But I cannot insert kvm.ko. >>> It failed with the error: >>> kvm: Unknown symbol genapic >>> >>> >>> >> Is this on i386 or x86_64? >> >> >> >> I had the same problem with kernel-2.6.22-gentoo-r5. Applied the patch from the email titled "kvm-37 problem w/ 64-bit division in lapic.c" and fixed the problem. So check it out. Simon - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
[kvm-devel] win2003 guest stutters
Hi, Please CC me, I'm not a subscriber to the list. I have a Debian unstable 64bit host on an intel S3000 quad core xeon X3210. Kernel 2.6.22-2-amd64 (debian flavour) and KVM28 and KVM36. Linux guests run very well. I installed Win2003 EE SP2 with --no-kvm, and disabled ACPI in the windows setup. Now I'm running this image with kvm -no-acpi -m 1024 -hda w2k3image.qcow2 -net nic,model=rtl8139 -net tap,vlan=0,ifname=tap3. (note I have KVM enabled at this point) This image works well half of the time (very responsive and no interruptions), but after some time it will completely freeze for a period of time (sometimes seconds, sometimes minutes it would seem). Both the network and the console are completely unresponsive. I can't see a pattern as to when it happens: sometimes the guest will work for 10 minutes without a hitch, sometimes I can't make it past the login screen. It is the only VM running at that time. Any help or suggestions would be greatly appreciated. Kind regards, Joris - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] Build of kvm-37 fails
This issue is fixed by Qing's patch to hrtimer migration yesterday, but it is not in yet given that the comments is not properly in. Eddie -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gildas Sent: 2007年9月10日 18:15 To: Avi Kivity Cc: kvm-devel Subject: Re: [kvm-devel] Build of kvm-37 fails Le 10/09/07, Gildas<[EMAIL PROTECTED]> a écrit : > Hi Avi, > > I had the same problem on a laptop with Core2 T7200 @ 2.00GHz > running ubuntu with kernel 2.6.20 > > Going in the kvm-37 source directory and applying the patch with > > patch -p1 > fixed the compilation problem for me but the VM I've tried crash with > > exception 6 (0) > rax rbx rcx rdx > 0600 > rsi rdi rsp fffe rbp > > r8 r9 r10 r11 > > r12 r13 r14 r15 > > rip 0003 rflags 00033082 > cs (/ p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) > ds (/ p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) > es (/ p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) > ss (/ p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) > fs (/ p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) > gs (/ p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) > tr (3085/2088 p 1 dpl 0 db 0 s 0 type b l 0 g 0 avl 0) > ldt (/ p 1 dpl 0 db 0 s 0 type 2 l 0 g 0 avl 0) > gdt 0/ > idt 0/ > cr0 6010 cr2 0 cr3 0 cr4 0 cr8 0 efer 0 > code: 54 ff 00 --> f0 53 ff 00 f0 53 ff 00 f0 53 ff 00 f0 53 ff 00 f0 > 53 ff 00 f0 53 ff 00 f0 53 ff 00 f0 a5 fe 00 f0 87 e9 00 f0 53 ff 00 > f0 53 ff 00 f0 53 ff > > They runned fine with kvm-36 but now they crash even with -no-kvm. I did further tests after I saw the bug report about the crash related to smp: I was running my vm with -smp 2. If I remove this option, they run fine. Cheers Gildas > 2007/9/9, Avi Kivity <[EMAIL PROTECTED]>: > > Pelle wrote: > > > Hi, > > > > > > I tried to compile the new kvm-37, and got the following errors: > > > > > > regards, Pelle > > > > > > > > > > > > > Does the attached patch help? > > > > -- > > error compiling committee.c: too many arguments to function > > > > > > - > > This SF.net email is sponsored by: Microsoft > > Defy all challenges. Microsoft(R) Visual Studio 2005. > > http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ > > ___ > > kvm-devel mailing list > > kvm-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/kvm-devel > > > > > > > - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] [PATCH] passing smp cpu count from CMOS
>-Original Message-
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED] On Behalf Of
>Avi Kivity
>Sent: 2007年9月10日 20:48
>To: He, Qing
>Cc: kvm-devel@lists.sourceforge.net
>Subject: Re: [kvm-devel] [PATCH] passing smp cpu count from CMOS
>
>Avi Kivity wrote:
>>
>> Alternative patch attached, but works only with -no-kvm-irqchip.
>>
>>
>
>After removing smp_processor_id() from kvm_vcpu_kick() it works fairly
>well, unfortunately that means there's a timing issue with
>kernel lapic.
>
Double checked the code, yes there is really not a small window where
the pre-read ipi_pcpu may be already out of date. Just remove the additional
condition check is fine, or we can have following patch since this is
only a performance concern in delivering virtual IRQ. Just let you fell
comfortable :-)
In either way, we are not precisely on demand signal IPI (i.e. we may
signal redundant IPIs which is harmless) since it is only a very minor
performance issue so I didn't use lock similar mechanism.
thx,eddie
diff --git a/drivers/kvm/irq.c b/drivers/kvm/irq.c
index 225c541..ab5769f 100644
--- a/drivers/kvm/irq.c
+++ b/drivers/kvm/irq.c
@@ -73,13 +73,11 @@ static void vcpu_kick_intr(void *info)
void kvm_vcpu_kick(struct kvm_vcpu *vcpu)
{
- int ipi_pcpu = vcpu->cpu;
-
if (waitqueue_active(&vcpu->wq)) {
wake_up_interruptible(&vcpu->wq);
++vcpu->stat.halt_wakeup;
}
- if (vcpu->guest_mode && ipi_pcpu != smp_processor_id())
+ if (vcpu->guest_mode && vcpu->cpu != smp_processor_id())
smp_call_function_single(ipi_pcpu, vcpu_kick_intr, vcpu, 0, 0);
}
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] [ANNOUNCE] kvm-37 release
On Sun, 09 Sep 2007 14:05:13 +0300
Avi Kivity <[EMAIL PROTECTED]> wrote:
> This release merges the pic/lapic/ioapic into mainline. While some
> known issues exist, we're now at the point where it's better to get
> some wider exposure rather than keep it alone on a branch.
>
> Some regressions are expected; please report them as they appear. A
> new qmeu option -no-kvm-irqchip is available to disable the new
> functionality.
My experience so far:
On 32-bit Intel host, lapic fails to link due to missing 64bit
division. I tried the attached patch to fix the build, but Windows
XP froze before showing the booting screen. With -no-kvm-irqchip
they work, except the IE plugins like Flash & Java, which are broken
since kvm-29. With -no-kvm, qemu-system-x86_64 segfaults immediately.
Regards,
--
Jindrich Makovicka
--- lapic.c~ 2007-09-09 12:51:09.0 +0200
+++ lapic.c 2007-09-09 16:12:38.0 +0200
@@ -31,6 +31,7 @@
#include
#include
#include
+#include
#include "irq.h"
#define PRId64 "d"
@@ -511,8 +512,8 @@
} else
passed = ktime_sub(now, apic->timer.last_update);
- counter_passed = ktime_to_ns(passed) /
- (APIC_BUS_CYCLE_NS * apic->timer.divide_count);
+ counter_passed = div64_64(ktime_to_ns(passed),
+ (APIC_BUS_CYCLE_NS * apic->timer.divide_count));
tmcct -= counter_passed;
if (tmcct <= 0) {
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] Intel-only or AMD Opteron as well?
On 2007-09-08, 14:59 GMT, Fernando Cassia wrote: > The above move by RedHat is a bit confusing... what can Xen do > that KVM cannot?. In other words, why should anyone even bother > with Xen with KVM around ??. I've read Xen is "more robust" > because it has a "one year lead" over KVM. But really, how does > this translate, if performance of Xen could be worse due to > more paravirtualization?. Or is Xen more optimized to > provide the "greatest possible consolidation" on servers (ie > less resource usage, less impact on cpu usage of a high number > of VMs?). (notwithstanding the domain of my email address, I am not part of the kernel/VM RH team, I am not developer or even programmer, and this is just my personal thinking not anything close to official position of Red Hat). a) Concerning maturity -- remember, RHEL 5 was created on the basis of Fedora Core 6, which was released in the fall 2006. In that moment, there was no KVM around. And you don't put technology which is not enough old into product which you are supposed to support for the next seven years. It is almost one year later and KVM is still in the stage of rapid development and substantial changes (IMHO and I think it is a good for all of us -- eagerly waiting for KVM host suspend/resume in 2.6.23). Again, you don't put such stuff into enteprise grade distribution. b) Concerning paravirtualization, I think you have it other way around -- given the fact that both host and guest know about virtualization, they can modify their behavior accordingly and work better than with full virtualization, when guest knows nothing. It is said that the disadvantage of fullvirt is slightly smaller with hardware accelerated virtualization (which is what KVM does), but again I know nothing about this. c) One thing which is very important to consider is libvirt. I think that is really smart move from Red Hat. Remember, all interesting tools for doing virtualization (virt-manager, virsh, virt-viewer, etc.) in Red Hat distributions are based on libvirt and so they agnostic vis-a-vis particular implementation of virtualization. So our users can learn about virtualization as such with Xen, and when some other technology (e.g., kvm, but who knows what will happen in seven years and whether some even better technology won't arise?) is good enough to be included into RHEL (for example, that actually missing paravirtualization is one of the biggest problems of kvm) or if something nasty happens to Xen, we can just switch the virtualization backend and everything will work for our users as before. Again, I think this is the way how to do a seven-years-supported distribution. Just my 0.02 CZK. Matěj -- http://www.ceplovi.cz/matej/blog/, Jabber: ceplmajabber.cz GPG Finger: 89EF 4BC6 288A BF43 1BAB 25C3 E09F EF25 D964 84AC A bird in the hand makes it awfully hard to blow your nose. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] kvm-37 results
On 9/10/07, Avi Kivity <[EMAIL PROTECTED]> wrote: > Jorge Lucángeli Obes wrote: > > Windows Vista Ultimate 32-bit guest: hangs during boot. > > *Command line: > > -net nic,model=8139 -m 512 -localtime > > *Nothing in dmesg besides processor 1 inicialization SIPI messages > > *Still hangs during boot with 'no-kvm-irqchip' > > > > Can you double-check that you are using the bios.bin provided by kvm-37? > [EMAIL PROTECTED]:~$ diff local/kvm-37/bios/BIOS-bochs-latest /usr/local/share/qemu/bios.bin [EMAIL PROTECTED]:~$ sudo qemu-system-x86_64 -localtime -m 512 -no-kvm-irqchip -L /usr/local/share/qemu stuff/images/vista/vista.img -net nic,model=rtl8139 -net user Gives the attached screen. Removing '-no-kvm-irqchip' hangs my Xubuntu Feisty 64 bit host (Core 2 Duo 5600). Unlike my previous Vista experiences, this install has worked before (http://bp2.blogger.com/_ie1hS2VW0Z4/Rqgdx0v5qfI/AAM/KUdnPvdQVsA/s400/vista_kvm.png). Cheers, Jorge <>- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
