[kvm-devel] Google Summer of Code

2007-03-03 Thread Benjamin Prosnitz
Will KVM be participating in Google's Summer of Code? I am reasonably familiar with KVM's sourcecode and would love to help out during the summer. Thanks, Benjamin Prosnitz - Take Surveys. Earn Cash. Influence the Future

Re: [kvm-devel] Interested in KVM development

2007-03-03 Thread Avi Kivity
Neo Jia wrote: > hi, > > I am quite interested in KVM project and have read through several > papers from VMware site related to the virtualization (also including > some papers from their reference list). I would like to try some small > bugs/enhancement first. > > Any suggestions? > There are

Re: [kvm-devel] [PATCH 2/3] Add a vcpu_migrated statistic

2007-03-03 Thread Avi Kivity
Leonard Norrgard wrote: > The previous patch introduces an IPI on every vcpu migration on SMP > machines to find out the TSC value on the previous cpu. We might be > able to avoid this IPI on systems that have a synchronized TSC by > checking for it in svm/vmx_vcpu_load: > > + /* If t

Re: [kvm-devel] [PATCH 1/3] Sync guest viewable TSC when vcpu migrated

2007-03-03 Thread Avi Kivity
Thanks for picking this up! Some comments below. Leonard Norrgard wrote: > Index: linux-2.6/drivers/kvm/svm.c > === > --- linux-2.6.orig/drivers/kvm/svm.c 2007-03-02 17:29:57.0 +0200 > +++ linux-2.6/drivers/kvm/svm.c 2

Re: [kvm-devel] kvm-15 on top of 2.6.20 - unresolved symbols

2007-03-03 Thread Avi Kivity
Emil Tantilov wrote: > Finally I got some time and played with this some > more. The unresolved symbols are caused by the fact > that the kvm module fails to load: > > FATAL: Error inserting kvm > (/lib/modules/2.6.20/extra/kvm.ko): Device or resource > busy > > I narrowed it down the following: >

Re: [kvm-devel] 32-bit FreeBSD under 64-bit KVM

2007-03-03 Thread Avi Kivity
Aurelien Jarno wrote: >> Can you try turning the '#undef AUDIT' to '#define AUDIT' in mmu.c? >> Also, change 'int dbg = 1' to 'int dbg = 0' in the same file. Note kvm >> will be very slower after this. dmesg will show any issues (issue a >> 'echo 9 > /proc/sysrq-trigger' to make sure all mess