[kvm-devel] Message for new year

2007-12-27 Thread lauriedvm
As the new year...
http://newyearcards2008.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] README: How to run kvm guests on IA64

2007-12-27 Thread Amit Shah
On Thursday 27 December 2007 13:20:06 Zhang, Xiantao wrote:
  It shouldn't have any confilicts, since they belong to different
  archs. Currently, you know source code is placed at
  arch/{$arch}/kvm, and Makefile and Kconfig aslo there.
  So, it doesn't impact any issues, since ia64 and x86_64 are totally
  different archs.  For example, you can define HAS_IO_PORT macro for
  ia64 and x86, but they don't invoke any conficlts.:)
 
  What about files that get shared?

 I think common files shouldn't use KVM_CONFIG_INTEL.

Even then I'm not sure we should use a common #define within the sources that 
will apply to two different architectures in different ways under different 
build environments. Avi, what do you think?

  The build system should pick up the relevant files
  from /lib/modules/`uname -r`/build/ If it doesn't, it's a bug. (It
  works for me on x86.)

 If we built on target machine,  you are right. But if the build machine
 is not target machine, how to build ?

We can use the --kerneldir option in that case. However, this might be too 
much info (and very confusing) for a basic README.


 Xiantao

-
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] README: How to run kvm guests on IA64

2007-12-27 Thread Avi Kivity
Amit Shah wrote:
 On Thursday 27 December 2007 13:20:06 Zhang, Xiantao wrote:
   
 It shouldn't have any confilicts, since they belong to different
 archs. Currently, you know source code is placed at
 arch/{$arch}/kvm, and Makefile and Kconfig aslo there.
 So, it doesn't impact any issues, since ia64 and x86_64 are totally
 different archs.  For example, you can define HAS_IO_PORT macro for
 ia64 and x86, but they don't invoke any conficlts.:)
 
 What about files that get shared?
   
 I think common files shouldn't use KVM_CONFIG_INTEL.
 

 Even then I'm not sure we should use a common #define within the sources that 
 will apply to two different architectures in different ways under different 
 build environments. Avi, what do you think?
   

I agree in principle, but I don't see a big hurry to change things.  
Let's get it merged first.

-- 
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] Oops on 2.6.23.11 with KVM 57

2007-12-27 Thread Avi Kivity
Guido Guenther wrote:
 On Sat, Dec 22, 2007 at 09:59:43PM +0200, Avi Kivity wrote:
   
 Guido Guenther wrote:
 
 Hi,
 I got the Oops below on an Dual CPU Dual-Core AMD Opteron(tm) Processor
 2220 running a 32bit kernel. Kernel is 2.6.23.11, kvm version 57.
 Doesn't happen all the time but usually right at VM startup. Seems to be
 easier to trigger when starting up several VMs in row. 
   
 What guest are you running?  smp or uni?
 
 Uniprocessor Linux, standard etch 2.6.18 kernel.

 kvm commandline was:

 -M pc -m 512 -smp 1 -monitor pty -boot c -hda /dev/mapper/foo -hdb
 /dev/mapper/bar -net nic,macaddr=54:52:00:1b:9b:10,vlan=0 -net
 tap,fd=11,script=,vlan=0 -usb -usbdevice tablet -vnc 127.0.0.1:0

   

Looks like memory corruption; this was a call through a function pointer 
that pointed into userspace.

Please try kvm-58, that has a fix for preemption notifiers on AMD; this 
may solve the problem.

-- 
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 Test result, kernel KVM58rc1, userspace KVM58rc1

2007-12-27 Thread Zhao, Yunfeng
Hi
This is today's KVM test result against KVM58 RC1: kvm.git 
1d536bc26aec043a102f0fd02899985fd5f77653 and kvm-userspace.git 
52f00b3c49354a06a95ded4a2e932c9cd55fe7df
One issue has been fixed:
1. PAE host hanged on some platforms while booting guests
https://sourceforge.net/tracker/index.php?func=detailaid=1849200group_id=180599atid=893831

Save/restore still fails on ia32e host, and sometimes it causes host to crash.

Issues:
1. Crashme causes RHEL5 guest kernel panic
The guest will kernel panic immediately after starting the test.
https://sourceforge.net/tracker/?func=detailatid=893831aid=1840711group_id=180599
2. Timer of guest is inaccurate
https://sourceforge.net/tracker/?func=detailatid=893831aid=1826080group_id=180599
3. Cannot install 64bit vista guests.
https://sourceforge.net/tracker/?func=detailatid=893831aid=1836905group_id=180599
4. Fails to save/restore guests ia32 host
https://sourceforge.net/tracker/index.php?func=detailaid=1824525group_id=180599atid=893831
5. xp and win2k3 guest crashes
https://sourceforge.net/tracker/?func=detailatid=893831aid=1819768group_id=180599
6. xpsp2 with 2vpus may fail to boot
https://sourceforge.net/tracker/index.php?func=detailaid=1805017group_id=180599atid=893831
7. Cannot boot 32bit smp RHEL5.1 guest on 64bit host
https://sourceforge.net/tracker/?func=detailatid=893831aid=1812043group_id=180599

Test environment



Platform    woodcrest
CPU 4
Memory size 8G'



Details



PAE:

1. boot guest with 256M memory   PASS
2. boot two windows xp guestPASS
3. boot 4 same guest in parallel PASS
4. boot linux and windows guest in parallel  PASS
5. boot guest with 1500M memory  PASS
6. boot windows 2003 with ACPI enabled   FAIL
7. boot Windows xp with ACPI enabled   FAIL
8. boot Windows 2000 without ACPI   PASS
9. kernel build on SMP linux guest PASS
10. LTP on SMP linux guest  PASS
11. boot base kernel linux PASS
12. save/restore 32-bit HVM guestsPASS
13. live migration 32-bit HVM guests   PASS
14. boot SMP Windows xp with ACPI enabled FAIL
15. boot SMP Windows 2003 with ACPI enabled  FAIL
16. boot SMP Windows 2000 with ACPI enabled  FAIL



IA32e:

1. boot four 32-bit guest in parallel PASS
2. boot four 64-bit guest in parallel PASS
3. boot 4G 64-bit guest      PASS
4. boot 4G pae guest      PASS
5. boot 32-bit linux and 32 bit windows guest in parallel    PASS
6. boot 32-bit guest with 1500M memory PASS
7. boot 64-bit guest with 1500M memory     PASS
8. boot 32-bit guest with 256M memory   PASS
9. boot 64-bit guest with 256M memory   PASS
10. boot two 32-bit windows xp in parallel   PASS
11. boot four 32-bit different guest in para  PASS
12. save/restore 64-bit linux guests FAIL
13. save/restore 32-bit linux guests PASS
14. boot 32-bit SMP windows 2003 with ACPI enabled  PASS
15. boot 32-bit SMP Windows 2000 with ACPI enabled  FAIL
16. boot 32-bit SMP Windows xp with ACPI enabled  FAIL
17. boot 32-bit Windows 2000 without ACPI PASS
18. boot 64-bit Windows xp with ACPI enabled    PASS
19. boot 32-bit Windows xp without ACPI     PASS
20. boot 64-bit vista       
PASS
21. kernel build in 32-bit linux guest OS     PASS
22. kernel build in 64-bit linux guest OS     PASS
23. LTP on SMP 32-bit linux guest OS   PASS
24. LTP on SMP 64-bit linux guest OS   PASS
25. boot 64-bit guests with ACPI enabled       PASS
26. boot 32-bit x-server      
PASS   
27. boot 64-bit SMP windows XP with ACPI enabled    FAIL
28. boot 64-bit SMP windows 2003 with ACPI enabled    PASS
29. live migration 64bit linux guests FAIL
30. live migration 32bit linux guests PASS


Report Summary on IA32-pae

Summary Test Report of Last Session
=
Total   PassFail

Re: [kvm-devel] KVM Test result, kernel KVM58rc1, userspaceKVM58rc1

2007-12-27 Thread Zhao, Yunfeng


-Original Message-
From: Izik Eidus [mailto:[EMAIL PROTECTED]
Sent: 2007年12月27日 17:19
To: Zhao, Yunfeng
Cc: kvm-devel
Subject: Re: [kvm-devel] KVM Test result, kernel KVM58rc1, userspaceKVM58rc1


On Thu, 2007-12-27 at 17:16 +0800, Zhao, Yunfeng wrote:


 Save/restore still fails on ia32e host, and sometimes it causes host to 
 crash.

the host side was not fixed?
you still get this bad_page? or is it something else?
[Yunfeng] Maybe I should describe it more clearly. On ia32e host save/restore 
of ia32 guest has no problem, save/restore of ia32e guest fails.
IA32e guest will kernel panic after restored. No error messages in dmesg of the 
host.
See the snapshot pic, 
https://sourceforge.net/tracker/download.php?group_id=180599atid=893831file_id=259855aid=1824525


-
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-1858940 ] Kernel panic - not syncing: IO-APIC + timer doesn't work.

2007-12-27 Thread SourceForge.net
Bugs item #1858940, was opened at 2007-12-27 15:08
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=893831aid=1858940group_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: Kai Londenberg (kai_londenberg)
Assigned to: Nobody/Anonymous (nobody)
Summary: Kernel panic - not syncing: IO-APIC + timer doesn't work. 

Initial Comment:

The problem:

When booting a Guest with -smp 2 option (and without -no-acpi, since that's 
essential for SMP), I get a Kernel panic.

My Setup:

Host:

64_86 bit Ubuntu 7.10 with custom built 2.6.23.12 Kernel.
AMD Dual CPU with Virtualization extensions.

Guest:

Ubuntu 6.06 - Server -  with pre-compiled 2.6.15.29 server Kernel, with SMP 
Support.


I logged the kernel output via serial console redirection into a file.









--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=893831aid=1858940group_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


[kvm-devel] [ kvm-Bugs-1858949 ] USB is unstable

2007-12-27 Thread SourceForge.net
Bugs item #1858949, was opened at 2007-12-27 16:26
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=893831aid=1858949group_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: Technologov (technologov)
Assigned to: Nobody/Anonymous (nobody)
Summary: USB is unstable

Initial Comment:
USB often locks up VMs/slows down/loses responsiveness/or BSODs.

Windows XP VM loses responsiveness is the most common scenario.

This is especially true for complex, multi-function USB devices.

Some simpler devices work.

Tested on: Intel 64, F7/x64, KVM-58.

It happens both with KVM and -no-kvm.

-Alexey Technologov, 27.12.2007.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=893831aid=1858949group_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


[kvm-devel] XP install

2007-12-27 Thread Jerry Geis
Hi - I am using kvm-amd (kvm-58) (Turion 2200+ amd 64 host)
I installed XP just fine. However now on the reboot to actually startup XP
all it does is continue to show the page
start windows normally
start windows in safe mode
etc...

Once I select anything it just shows this page again.

Is there a known issue with booting/running XP that I have missed?

My kernel is 2.6.23. centos 5.1

Jerry

-
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] [PATCH] libkvm: fix mungled default case for switch in kvm_arch_run

2007-12-27 Thread Carlo Marcelo Arenas Belon
This patch corrects 03f1b5e137e7e4c8dd51dbaea6779be853f4fde0, that
modified the logic behind kvm_arch_run because of a mangled endif
which accidentally included the default entry for the switch.

kvm_arch_run as defined in 4f19bdea03330641fd48514ea84d1ed1bf431507
was affected by returning 0 by default instead of 1 and reporting
the following warning at compile time :

  libkvm-x86.c:201:9: warning: extra tokens at end of #endif directive

Signed-off-by: Carlo Marcelo Arenas Belon [EMAIL PROTECTED]
---
 libkvm/libkvm-x86.c |3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)

diff --git a/libkvm/libkvm-x86.c b/libkvm/libkvm-x86.c
index e6eb66e..2fa8146 100644
--- a/libkvm/libkvm-x86.c
+++ b/libkvm/libkvm-x86.c
@@ -198,7 +198,8 @@ int kvm_arch_run(struct kvm_run *run,kvm_context_t kvm, int 
vcpu)
case KVM_EXIT_TPR_ACCESS:
r = handle_tpr_access(kvm, run, vcpu);
break;
-#endif default:
+#endif
+   default:
r = 1;
break;
}
-- 
1.5.2.5


-
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] [PATCH] libkvm: fix stack underflow in MMIO read write calls

2007-12-27 Thread Carlo Marcelo Arenas Belon
This patch complement 6eabe2ba30a673c4280df75b28520e0e1f4a2171 so that
all callbacks used for MMIO read/write use the ABI exported in libkvm.h.

This fixes the following warnings was reported at compile time :

  main.c:392: warning: initialization from incompatible pointer type
  main.c:393: warning: initialization from incompatible pointer type
  qemu/qemu-kvm.c:532: warning: initialization from incompatible pointer type
  qemu/qemu-kvm.c:533: warning: initialization from incompatible pointer type

Signed-off-by: Carlo Marcelo Arenas Belon [EMAIL PROTECTED]
---
 qemu/qemu-kvm.c |6 ++
 user/main.c |4 ++--
 2 files changed, 4 insertions(+), 6 deletions(-)

diff --git a/qemu/qemu-kvm.c b/qemu/qemu-kvm.c
index a61b95c..9aee903 100644
--- a/qemu/qemu-kvm.c
+++ b/qemu/qemu-kvm.c
@@ -483,15 +483,13 @@ static int kvm_outl(void *opaque, uint16_t addr, uint32_t 
data)
 return 0;
 }
 
-static int kvm_mmio_read(void *opaque, uint64_t addr,
-   uint8_t *data, int len, int is_write)
+static int kvm_mmio_read(void *opaque, uint64_t addr, uint8_t *data, int len)
 {
cpu_physical_memory_rw(addr, data, len, 0);
return 0;
 }
 
-static int kvm_mmio_write(void *opaque, uint64_t addr,
-   uint8_t *data, int len, int is_write)
+static int kvm_mmio_write(void *opaque, uint64_t addr, uint8_t *data, int len)
 {
cpu_physical_memory_rw(addr, data, len, 1);
return 0;
diff --git a/user/main.c b/user/main.c
index 4d870fa..a2d6b8b 100644
--- a/user/main.c
+++ b/user/main.c
@@ -366,7 +366,7 @@ static int test_pre_kvm_run(void *opaque, int vcpu)
return 0;
 }
 
-static int test_mem_read(void *opaque, uint64_t addr, void *data, unsigned len)
+static int test_mem_read(void *opaque, uint64_t addr, uint8_t *data, int len)
 {
if (addr  IORAM_BASE_PHYS || addr + len  IORAM_BASE_PHYS + IORAM_LEN)
return 1;
@@ -374,7 +374,7 @@ static int test_mem_read(void *opaque, uint64_t addr, void 
*data, unsigned len)
return 0;
 }
 
-static int test_mem_write(void *opaque, uint64_t addr, void *data, unsigned 
len)
+static int test_mem_write(void *opaque, uint64_t addr, uint8_t *data, int len)
 {
if (addr  IORAM_BASE_PHYS || addr + len  IORAM_BASE_PHYS + IORAM_LEN)
return 1;
-- 
1.5.2.5


-
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