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 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 will
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
- winxp 32bit
We run some booting multiple guest tests in our nightly testing.
Like booting two UP windows guests, booting one UP linux guest and one UP
windows guest, and booting 4 UP linux guests.
The first two cases have no problem in our testing.
And booting 4 UP linux guests may crash host, but this
From dc4cc1a804d9f7705648bdee3d7152054da8dea8 Mon Sep 17 00:00:00 2001
From: Sheng Yang [EMAIL PROTECTED]
Date: Tue, 9 Oct 2007 16:22:08 +0800
Subject: [PATCH] kvm: bios: decrease the cpu counts in ACPI table to 15
It seems Windows 2000 only support no more than 15 cpus in ACPI table,
otherwise
Avi:
It seems we are using global TSS, and init_rmode_tss will modify
the table each time when VCPU is reset. Should we move to per CPU TSS
for correct real mode emulation?
thx,eddie
-
This SF.net email is sponsored
Dong, Eddie 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
Dong, Eddie wrote:
+
+/*
+ * Reset VM.
+ *
+ */
+int kvm_vm_reset(struct kvm *kvm)
+{
+ struct kvm_vcpu *vcpu;
+ int i;
+
+ kvm_reset_devices(kvm);
+ for (i = 0; i KVM_MAX_VCPUS; i++) {
+ vcpu = kvm-vcpus[i];
+ if (!vcpu)
+ continue;
Dong, Eddie wrote:
[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
Dong, Eddie wrote:
Avi:
It seems we are using global TSS, and init_rmode_tss will modify
the table each time when VCPU is reset. Should we move to per CPU TSS
for correct real mode emulation?
Why is it a problem?
But, the real-mode tss can definitely be improved. Right now it uses
Yang, Sheng wrote:
From dc4cc1a804d9f7705648bdee3d7152054da8dea8 Mon Sep 17 00:00:00 2001
From: Sheng Yang [EMAIL PROTECTED]
Date: Tue, 9 Oct 2007 16:22:08 +0800
Subject: [PATCH] kvm: bios: decrease the cpu counts in ACPI table to 15
It seems Windows 2000 only support no more than 15 cpus in
Zhao, Yunfeng wrote:
We run some booting multiple guest tests in our nightly testing.
Like booting two UP windows guests, booting one UP linux guest and one UP
windows guest, and booting 4 UP linux guests.
The first two cases have no problem in our testing.
And booting 4 UP linux guests may
Avi Kivity wrote:
Zhao, Yunfeng wrote:
We run some booting multiple guest tests in our nightly testing.
Like booting two UP windows guests, booting one UP linux guest and one UP
windows guest, and booting 4 UP linux guests.
The first two cases have no problem in our testing.
And booting 4
Avi Kivity wrote:
For a graceful reboot, this one is not needed since every APs are
already brought to HALT status before BSP issue RESET signal. But in
case of non-graceful reboot, it is possible the VCPUs are still
executing guest instruction, so we kick the VCPU and then use
Farkas Levente wrote:
Avi Kivity wrote:
Zhao, Yunfeng wrote:
We run some booting multiple guest tests in our nightly testing.
Like booting two UP windows guests, booting one UP linux guest and one UP
windows guest, and booting 4 UP linux guests.
The first two cases have no problem
Avi Kivity wrote:
Farkas Levente wrote:
Avi Kivity wrote:
Zhao, Yunfeng wrote:
We run some booting multiple guest tests in our nightly testing.
Like booting two UP windows guests, booting one UP linux guest and one UP
windows guest, and booting 4 UP linux guests.
The first two
Farkas Levente wrote:
Avi Kivity wrote:
Farkas Levente wrote:
Avi Kivity wrote:
Zhao, Yunfeng wrote:
We run some booting multiple guest tests in our nightly testing.
Like booting two UP windows guests, booting one UP linux guest and one UP
windows
Avi Kivity wrote:
In native, RESET signal force every processor enter RESET status,
and then immediately after RESET signal is removed, all CPUs will
compete for BSP role, the winner continue execution, and failor will
be blocked till INIT/SIPI/SIPI.
I meant, you could set both to
Dong, Eddie wrote:
Avi Kivity wrote:
In native, RESET signal force every processor enter RESET status,
and then immediately after RESET signal is removed, all CPUs will
compete for BSP role, the winner continue execution, and failor will
be blocked till INIT/SIPI/SIPI.
I meant,
Avi Kivity wrote:
Zhao, Yunfeng wrote:
We run some booting multiple guest tests in our nightly testing.
Like booting two UP windows guests, booting one UP linux guest and one UP
windows guest, and booting 4 UP linux guests.
The first two cases have no problem in our testing.
And booting
Avi Kivity wrote:
If BSP mp_state becomes VCPU_MP_STATE_UNINITIALIZED, current code
can't wakeup it. We need additional code that I am not aware of now.
Current VCPU must be BSP, otherwise the code executing in Qemu will
have problem too.
But, for an ungraceful reset, nothing
Dong, Eddie wrote:
Avi Kivity wrote:
If BSP mp_state becomes VCPU_MP_STATE_UNINITIALIZED, current code
can't wakeup it. We need additional code that I am not aware of now.
Current VCPU must be BSP, otherwise the code executing in Qemu will
have problem too.
But, for an
Carlo Marcelo Arenas Belon wrote:
On Mon, Oct 08, 2007 at 02:29:32PM -0500, Anthony Liguori wrote:
3) We do nothing, add a warning to the compilation for the users to read at
compile time (most of them not aware that they should be using gcc-3.x instead
as they are used to see all the
Jerone Young wrote:
This patch enables configure script in user directory for cross compile.
Still doesn't apply. What are you generating the patches against?
--
error compiling committee.c: too many arguments to function
Byron Stanoszek wrote:
Even when I first started using
KVM, I had no positive feedback that KVM was even working properly (was the
device node created? am I using a cpu with the correct extensions? etc). I
eventually figured out that if 'lsmod' showed kvm-intel.ko usage 0, then I
knew it was
Jerone Young wrote:
I believe the problem is that I am not generating my patches in git
format. I have been using a mercuial mq tree to generate the patches I
have been sending. While they apply fine with patch command, apparently
git needs the patches fomatted correctly.
git generally
We've seen various big patches regarding portability from Christian and
Xianto, but none was merged to date. Maintaining a large patch set on
top of a quickly moving code base is painful.
I thought it might be cool to try to throw trivial patches at Avi that
obviously don't break things and push
Carsten Otte wrote:
We've seen various big patches regarding portability from Christian and
Xianto, but none was merged to date. Maintaining a large patch set on
top of a quickly moving code base is painful.
I thought it might be cool to try to throw trivial patches at Avi that
obviously
Carsten Otte wrote:
A header file named kvm_arch.h is being introduced that contains
prototypes for funtions in kvm_x86.c.
What's the motivation for the new header? So we have a list of
arch-dependent functions? Compiler-wise it could just as well remain in
kvm.h.
--
error compiling
The patches are based on an older snapshot. Grabbing todays git tree I
see there have been changes in user/Makefile. This would be why it is
failing.
On Tue, 2007-10-09 at 18:02 +0200, Avi Kivity wrote:
Jerone Young wrote:
I believe the problem is that I am not generating my patches in git
I believe the problem is that I am not generating my patches in git
format. I have been using a mercuial mq tree to generate the patches I
have been sending. While they apply fine with patch command, apparently
git needs the patches fomatted correctly.
I'll get everything together again and use
This patch enables enable makefile in user for cross compile.
This time is a proper git formatted patch.
Signed-off-by: Joerone Young [EMAIL PROTECTED]
diff --git a/user/Makefile b/user/Makefile
index 26eb530..522874b 100644
--- a/user/Makefile
+++ b/user/Makefile
@@ -1,14 +1,22 @@
include
This patch patch applies on the latest git tree.
This adds more cross compile capability to the user diretory
configure script.
Patch created with git this time :-)
Signed-off-by: Jerone Young [EMAIL PROTECTED]
diff --git a/user/configure b/user/configure
index 20b9367..ff10268 100755
---
This patch adds a --memory option to kvmctl to allow the memory size of the
guest to be specified.
Signed-off-by: Anthony Liguori [EMAIL PROTECTED]
diff --git a/user/main.c b/user/main.c
index 9a57a24..7fc0924 100644
--- a/user/main.c
+++ b/user/main.c
@@ -57,6 +57,7 @@ static __thread int vcpu;
The memory size is currently hardcoded into the linker script (end_of_memory).
This prevents the memory size from being specified dynamically in kvmctl.
This patch adds a PIO port that can be used to query the memory size in the
tests.
Signed-off-by: Anthony Liguori [EMAIL PROTECTED]
diff --git
This patch attempts to clean up kvmctl so that it can be more easily made to
work for multiple architectures and to support more emulation.
It introduces a io dispatch mechanism. This mechanism supports subpage
granularity but is optimized to efficiently cover regions of pages too. It's
a
On Tue, Oct 09, 2007 at 04:31:54PM -0500, Anthony Liguori wrote:
This patch adds a --memory option to kvmctl to allow the memory size of the
guest to be specified.
Signed-off-by: Anthony Liguori [EMAIL PROTECTED]
diff --git a/user/main.c b/user/main.c
index 9a57a24..7fc0924 100644
---
Muli Ben-Yehuda wrote:
while ((ch = getopt_long(argc, argv, sopts, lopts, opt_ind)) != -1) {
switch (ch) {
@@ -367,6 +372,24 @@ int main(int argc, char **argv)
case 'p':
enter_protected_mode = true;
break;
+
This patch won't apply with the previous two patches applied. I was
meant to be independently reviewable. I have a merged patch that I'll
send out tomorrow but please still comment on this version :-)
Regards,
Anthony Liguori
Anthony Liguori wrote:
This patch attempts to clean up kvmctl so
On Tue, Oct 09, 2007 at 05:09:19PM -0500, Anthony Liguori wrote:
+ default:
+ fprintf(stderr,
+ Unrecongized memory suffix: %c\n,
+ *endptr);
+ exit(1);
Muli Ben-Yehuda wrote:
On Tue, Oct 09, 2007 at 05:09:19PM -0500, Anthony Liguori wrote:
+ default:
+ fprintf(stderr,
+ Unrecongized memory suffix: %c\n,
+ *endptr);
+
I'm a KVM newb and can't find any information or
associated FAQ about KVM guest firewire support. If
there's no KVM support, I'm seeking alternative
recommendations, if KVM list members are so inclined.
My goal is to boot a dedicated and proprietary Linux
2.4 kernel based AVX1 LiveCD under KVM.
This fix cannot resolve this issue.
Against latest kvm commits, SMP linux with 4 vcpus still cannot boot up.
But the issue will not happen , if adding -smp4 -no-acpi.
Here is the error info in dmesg
BUG: soft lockup detected on CPU#0!
[c044a0b7] softlockup_tick+0x98/0xa6
[c042cc98]
The attached patch should fix, though there's probably another problem
lurking in there.
--
Any sufficiently difficult bug is indistinguishable from a feature.
Thanks, the patch worked it didn't hoze the host anymore.
- David Brown
44 matches
Mail list logo
