Re: [kvm-devel] [ANNOUNCE] kvm-46 release

[Farkas Levente]

Avi Kivity wrote:
> Farkas Levente wrote:
>> Avi Kivity wrote:
>>   
>>> Farkas Levente wrote:
>>> 
>> we did a quick test against this version and it's turn out the smp
>> guests are still not working. even if we start only one linux guest
>> with
>> 4cpu on 4cpu host the guest kernel hangs at random stages of the kernel
>> loading process (if we run more smp guests then they hang earlier, but
>> different random stage), but it's never reach the end of the kernel so
>> hang somewhere inside the kernel. and the cpu usage of these process
>> goes up to until the qemu-kvm processes eat all cpus (ie. 100%). t
>>   
>>   
> What host cpu are you using?  What guest kernel version?  32-bit or
> 64-bit?
>
> I have no problems running a 4-way Linux guest here.
> 
> 
 - host:
   - Intel(R) Core(TM)2 Quad CPU Q6600  @ 2.40GHz
   - Intel S3000AHV
   - 8GB RAM
   - CentOS-5
   - kernel-2.6.18-8.1.14.el5 x86_64 64bit
 - guest-1:
   - CentOS-5
   - kernel-2.6.18-8.1.14.el5 i386 32bit
 - guest-2:
   - CentOS-5
   - kernel-2.6.18-8.1.14.el5 x86_64 64bit
 - guest-3:
   - Mandrake-9
   - kernel-2.4.19.16mdk-1-1mdk 32bit
 - guest-4:
   - Windows XP Professional 32bit

 start the first guest-1 with 4cpu produce the above hang. (and of course
 using kvm-46:-)

   
   
>>> Is it the only guest that hangs with -smp 4?  Or all of them?
>>> 
>> if i start this guest alone it's hang. if i start all guest-{1,2,3,4}
>> than all linux guest hangs expect windows which runs but see only one
>> cpu. ok now i try it for you:-) so:
>>
>> - host + guest-1 -> hang
>>
>> - host + guest-2 -> hang
>> in this case i've got a stack trace too on the host, and the host
>> working 2 more minutes (!?) so i see the top part of the stack
>> (shift-pageup) but when i try to take a picture the host crash and i can
>> only see the end:-( but next time i bale to catch it:
>> ---
>> BUG: soft lockup detected on CPU#0!
>>   
> 
> Yunfeng reports that this has been fixed, can you try the latest
> snapshot from http://people.qumranet.com/avi/snapshots/?

and the rpms in my repo, but i'd rather wait for kvm-47 since this's a
production server and i'd like to play with it only once a week:-)

-- 
  Levente   "Si vis pacem para bellum!"

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] [ANNOUNCE] kvm-46 release

[Gerd Hoffmann]

Izik Eidus wrote:
> can you send me your kvmctl.c file so i will look at it?
> it is somewhat hard to me understand how you did the things that way

I'm trying to back a vm with memory coming from a file map, see patch
attached against kvm-46 (was also attached earlier in this thread).

I've made kvm_create() optionally skip the memory setup, so I can create
my own later on.  That doesn't work though because creating the vcpu
fails then.

cheers,
  Gerd
* make kvm_create() skip all memory setup in case phys_mem_bytes == 0
* add kvm_register_userspace_phys_mem() to register any userspace memory
  as guest physical memory.

Signed-off-by: Gerd Hoffmann <[EMAIL PROTECTED]>
---
 user/kvmctl.c |   53 +
 user/kvmctl.h |3 +++
 2 files changed, 44 insertions(+), 12 deletions(-)

Index: kvm-46/user/kvmctl.c
===
--- kvm-46.orig/user/kvmctl.c
+++ kvm-46/user/kvmctl.c
@@ -443,20 +443,22 @@ int kvm_create(kvm_context_t kvm, unsign
 	}
 	kvm->vm_fd = fd;
 
-	r = ioctl(kvm->fd, KVM_CHECK_EXTENSION, KVM_CAP_USER_MEMORY);
-	if (r > 0)
-		r = kvm_alloc_userspace_memory(kvm, memory, vm_mem);
-	else
-		r = kvm_alloc_kernel_memory(kvm, memory, vm_mem);
-	if (r < 0)
-		return r;
+	if (phys_mem_bytes) {
+		r = ioctl(kvm->fd, KVM_CHECK_EXTENSION, KVM_CAP_USER_MEMORY);
+		if (r > 0)
+			r = kvm_alloc_userspace_memory(kvm, memory, vm_mem);
+		else
+			r = kvm_alloc_kernel_memory(kvm, memory, vm_mem);
+		if (r < 0)
+			return r;
 
-zfd = open("/dev/zero", O_RDONLY);
-mmap(*vm_mem + 0xa8000, 0x8000, PROT_READ|PROT_WRITE,
- MAP_PRIVATE|MAP_FIXED, zfd, 0);
-close(zfd);
+	zfd = open("/dev/zero", O_RDONLY);
+	mmap(*vm_mem + 0xa8000, 0x8000, PROT_READ|PROT_WRITE,
+	 MAP_PRIVATE|MAP_FIXED, zfd, 0);
+	close(zfd);
 
-	kvm->physical_memory = *vm_mem;
+		kvm->physical_memory = *vm_mem;
+	}
 
 	kvm->irqchip_in_kernel = 0;
 	if (!kvm->no_irqchip_creation) {
@@ -558,6 +560,33 @@ void *kvm_create_phys_mem(kvm_context_t 
 log, writable);
 }
 
+int kvm_register_userspace_phys_mem(kvm_context_t kvm,
+			unsigned long phys_start, void *userspace_addr,
+			unsigned long len, int slot, int log)
+{
+	int r;
+	struct kvm_userspace_memory_region memory = {
+		.slot = slot,
+		.memory_size = len,
+		.guest_phys_addr = phys_start,
+		.userspace_addr = (intptr_t)userspace_addr,
+		.flags = log ? KVM_MEM_LOG_DIRTY_PAGES : 0,
+	};
+
+	if (!kvm->physical_memory)
+		kvm->physical_memory = userspace_addr - phys_start;
+
+	r = ioctl(kvm->vm_fd, KVM_SET_USER_MEMORY_REGION, &memory);
+	if (r == -1) {
+		fprintf(stderr, "create_userspace_phys_mem: %s", strerror(errno));
+		return -1;
+	}
+
+	kvm_userspace_memory_region_save_params(kvm, &memory);
+
+	return 0;
+}
+
 /* destroy/free a whole slot.
  * phys_start, len and slot are the params passed to kvm_create_phys_mem()
  */
Index: kvm-46/user/kvmctl.h
===
--- kvm-46.orig/user/kvmctl.h
+++ kvm-46/user/kvmctl.h
@@ -404,6 +404,9 @@ void *kvm_create_phys_mem(kvm_context_t,
 			  unsigned long len, int slot, int log, int writable);
 void kvm_destroy_phys_mem(kvm_context_t, unsigned long phys_start, 
 			  unsigned long len, int slot);
+int kvm_register_userspace_phys_mem(kvm_context_t kvm,
+			unsigned long phys_start, void *userspace_addr,
+			unsigned long len, int slot, int log);
 int kvm_get_dirty_pages(kvm_context_t, int slot, void *buf);
 
 
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] [ANNOUNCE] kvm-46 release

[Izik Eidus]

On Mon, 2007-10-15 at 13:15 +0200, Gerd Hoffmann wrote:
> Izik Eidus wrote:
> > On Mon, 2007-10-15 at 13:00 +0200, Gerd Hoffmann wrote:
> >> Gerd Hoffmann wrote:
> >>
> >>> Something like this? (compiles, not tested yet).
> >> Hmm, no-go, results in "kvm_create_vcpu: Cannot allocate memory".
> > 
> > try use slot bigger bigger than 5 and smaller than 8
> 
> It doesn't come that far, kvm_create(&foo, 0, NULL) fails, seems doing
> vcpu_create() before memory setup doesn't work.
> 
> cheers,
>   Gerd
> 
> 
can you send me your kvmctl.c file so i will look at it?
it is somewhat hard to me understand how you did the things that way


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] [ANNOUNCE] kvm-46 release

[Gerd Hoffmann]

Izik Eidus wrote:
> On Mon, 2007-10-15 at 13:00 +0200, Gerd Hoffmann wrote:
>> Gerd Hoffmann wrote:
>>
>>> Something like this? (compiles, not tested yet).
>> Hmm, no-go, results in "kvm_create_vcpu: Cannot allocate memory".
> 
> try use slot bigger bigger than 5 and smaller than 8

It doesn't come that far, kvm_create(&foo, 0, NULL) fails, seems doing
vcpu_create() before memory setup doesn't work.

cheers,
  Gerd



-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] [ANNOUNCE] kvm-46 release

[Izik Eidus]

On Mon, 2007-10-15 at 13:00 +0200, Gerd Hoffmann wrote:
> Gerd Hoffmann wrote:
> 
> > Something like this? (compiles, not tested yet).
> 
> Hmm, no-go, results in "kvm_create_vcpu: Cannot allocate memory".

try use slot bigger bigger than 5 and smaller than 8
> cheers,
>   Gerd
> 
> -
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> ___
> kvm-devel mailing list
> kvm-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/kvm-devel


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] [ANNOUNCE] kvm-46 release

[Gerd Hoffmann]

Gerd Hoffmann wrote:

> Something like this? (compiles, not tested yet).

Hmm, no-go, results in "kvm_create_vcpu: Cannot allocate memory".

cheers,
  Gerd

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] [ANNOUNCE] kvm-46 release

[Gerd Hoffmann]

Avi Kivity wrote:
> Gerd Hoffmann wrote:
>> Avi Kivity wrote:
>>   
>>> We've now switched to allocating guest memory in userspace rather than
>>> in the kernel.
>>> 
>> Hmm, a quick glimpse over kvmctl.h doesn't show an obvious way how to
>> use that.  If I want to back vm memory with a file mapping, how can I do
>> that?
>>   
> 
> kvmctl.h doesn't expose an API for that currently, though is should be
> fairly trivial to do so.

Something like this? (compiles, not tested yet).

cheers,
  Gerd

* make kvm_create() skip all memory setup in case phys_mem_bytes == 0
* add kvm_register_userspace_phys_mem() to register any userspace memory
  as guest physical memory.

Signed-off-by: Gerd Hoffmann <[EMAIL PROTECTED]>
---
 user/kvmctl.c |   53 +
 user/kvmctl.h |3 +++
 2 files changed, 44 insertions(+), 12 deletions(-)

Index: kvm-46/user/kvmctl.c
===
--- kvm-46.orig/user/kvmctl.c
+++ kvm-46/user/kvmctl.c
@@ -443,20 +443,22 @@ int kvm_create(kvm_context_t kvm, unsign
 	}
 	kvm->vm_fd = fd;
 
-	r = ioctl(kvm->fd, KVM_CHECK_EXTENSION, KVM_CAP_USER_MEMORY);
-	if (r > 0)
-		r = kvm_alloc_userspace_memory(kvm, memory, vm_mem);
-	else
-		r = kvm_alloc_kernel_memory(kvm, memory, vm_mem);
-	if (r < 0)
-		return r;
+	if (phys_mem_bytes) {
+		r = ioctl(kvm->fd, KVM_CHECK_EXTENSION, KVM_CAP_USER_MEMORY);
+		if (r > 0)
+			r = kvm_alloc_userspace_memory(kvm, memory, vm_mem);
+		else
+			r = kvm_alloc_kernel_memory(kvm, memory, vm_mem);
+		if (r < 0)
+			return r;
 
-zfd = open("/dev/zero", O_RDONLY);
-mmap(*vm_mem + 0xa8000, 0x8000, PROT_READ|PROT_WRITE,
- MAP_PRIVATE|MAP_FIXED, zfd, 0);
-close(zfd);
+	zfd = open("/dev/zero", O_RDONLY);
+	mmap(*vm_mem + 0xa8000, 0x8000, PROT_READ|PROT_WRITE,
+	 MAP_PRIVATE|MAP_FIXED, zfd, 0);
+	close(zfd);
 
-	kvm->physical_memory = *vm_mem;
+		kvm->physical_memory = *vm_mem;
+	}
 
 	kvm->irqchip_in_kernel = 0;
 	if (!kvm->no_irqchip_creation) {
@@ -558,6 +560,33 @@ void *kvm_create_phys_mem(kvm_context_t 
 log, writable);
 }
 
+int kvm_register_userspace_phys_mem(kvm_context_t kvm,
+			unsigned long phys_start, void *userspace_addr,
+			unsigned long len, int slot, int log)
+{
+	int r;
+	struct kvm_userspace_memory_region memory = {
+		.slot = slot,
+		.memory_size = len,
+		.guest_phys_addr = phys_start,
+		.userspace_addr = (intptr_t)userspace_addr,
+		.flags = log ? KVM_MEM_LOG_DIRTY_PAGES : 0,
+	};
+
+	if (!kvm->physical_memory)
+		kvm->physical_memory = userspace_addr - phys_start;
+
+	r = ioctl(kvm->vm_fd, KVM_SET_USER_MEMORY_REGION, &memory);
+	if (r == -1) {
+		fprintf(stderr, "create_userspace_phys_mem: %s", strerror(errno));
+		return -1;
+	}
+
+	kvm_userspace_memory_region_save_params(kvm, &memory);
+
+	return 0;
+}
+
 /* destroy/free a whole slot.
  * phys_start, len and slot are the params passed to kvm_create_phys_mem()
  */
Index: kvm-46/user/kvmctl.h
===
--- kvm-46.orig/user/kvmctl.h
+++ kvm-46/user/kvmctl.h
@@ -404,6 +404,9 @@ void *kvm_create_phys_mem(kvm_context_t,
 			  unsigned long len, int slot, int log, int writable);
 void kvm_destroy_phys_mem(kvm_context_t, unsigned long phys_start, 
 			  unsigned long len, int slot);
+int kvm_register_userspace_phys_mem(kvm_context_t kvm,
+			unsigned long phys_start, void *userspace_addr,
+			unsigned long len, int slot, int log);
 int kvm_get_dirty_pages(kvm_context_t, int slot, void *buf);
 
 
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] [ANNOUNCE] kvm-46 release

[Avi Kivity]

Farkas Levente wrote:
> Avi Kivity wrote:
>   
>> Farkas Levente wrote:
>> 
> we did a quick test against this version and it's turn out the smp
> guests are still not working. even if we start only one linux guest
> with
> 4cpu on 4cpu host the guest kernel hangs at random stages of the kernel
> loading process (if we run more smp guests then they hang earlier, but
> different random stage), but it's never reach the end of the kernel so
> hang somewhere inside the kernel. and the cpu usage of these process
> goes up to until the qemu-kvm processes eat all cpus (ie. 100%). t
>   
>   
 What host cpu are you using?  What guest kernel version?  32-bit or
 64-bit?

 I have no problems running a 4-way Linux guest here.
 
 
>>> - host:
>>>   - Intel(R) Core(TM)2 Quad CPU Q6600  @ 2.40GHz
>>>   - Intel S3000AHV
>>>   - 8GB RAM
>>>   - CentOS-5
>>>   - kernel-2.6.18-8.1.14.el5 x86_64 64bit
>>> - guest-1:
>>>   - CentOS-5
>>>   - kernel-2.6.18-8.1.14.el5 i386 32bit
>>> - guest-2:
>>>   - CentOS-5
>>>   - kernel-2.6.18-8.1.14.el5 x86_64 64bit
>>> - guest-3:
>>>   - Mandrake-9
>>>   - kernel-2.4.19.16mdk-1-1mdk 32bit
>>> - guest-4:
>>>   - Windows XP Professional 32bit
>>>
>>> start the first guest-1 with 4cpu produce the above hang. (and of course
>>> using kvm-46:-)
>>>
>>>   
>>>   
>> Is it the only guest that hangs with -smp 4?  Or all of them?
>> 
>
> if i start this guest alone it's hang. if i start all guest-{1,2,3,4}
> than all linux guest hangs expect windows which runs but see only one
> cpu. ok now i try it for you:-) so:
>
> - host + guest-1 -> hang
>
> - host + guest-2 -> hang
> in this case i've got a stack trace too on the host, and the host
> working 2 more minutes (!?) so i see the top part of the stack
> (shift-pageup) but when i try to take a picture the host crash and i can
> only see the end:-( but next time i bale to catch it:
> ---
> BUG: soft lockup detected on CPU#0!
>   

Yunfeng reports that this has been fixed, can you try the latest
snapshot from http://people.qumranet.com/avi/snapshots/?


-- 
Do not meddle in the internals of kernels, for they are subtle and quick to 
panic.


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] [ANNOUNCE] kvm-46 release

[Avi Kivity]

Gerd Hoffmann wrote:
> Avi Kivity wrote:
>   
>> We've now switched to allocating guest memory in userspace rather than
>> in the kernel.
>> 
>
> Hmm, a quick glimpse over kvmctl.h doesn't show an obvious way how to
> use that.  If I want to back vm memory with a file mapping, how can I do
> that?
>   

kvmctl.h doesn't expose an API for that currently, though is should be
fairly trivial to do so.  The kernel API is straightforward: take this
bunch of memory and present it to a guest at some address.  The kernel
doesn't care if the memory came from a file mmap() or some other source.


-- 
Do not meddle in the internals of kernels, for they are subtle and quick to 
panic.


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] [ANNOUNCE] kvm-46 release

[Gerd Hoffmann]

Avi Kivity wrote:
> We've now switched to allocating guest memory in userspace rather than
> in the kernel.

Hmm, a quick glimpse over kvmctl.h doesn't show an obvious way how to
use that.  If I want to back vm memory with a file mapping, how can I do
that?

cheers,
  Gerd


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] [ANNOUNCE] kvm-46 release

[Anthony Liguori]

Jun Koi wrote:
> On 10/10/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
>   
>> Jun Koi wrote:
>> 
>>> On 10/10/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
>>>
>>>   
 Jun Koi wrote:

 
> Hi,
>
> On 10/10/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
>
>
>   
>> We've now switched to allocating guest memory in userspace rather than
>> in the kernel.  This is important if you have a mainframe, but also if
>> you want to share memory between guests and implement nice features like
>> swapping.
>>
>>
>> 
> This is interesting! But how can we do that now? (share memory between 
> guests)
>
>
>
>   
 It's not exposed by qemu, but you can now mmap() some file (or use SysV
 shared memory) and use that as guest memory.


 
>>> OK, lets say we have 2 guest VMs share a memory, like mmap() a tmpfs
>>> file (which is actually in memory). Now one writes to the memory
>>> (shared file). Can we guarantee that the memory immediately updated,
>>> so other will see the change immediately? Or the data might be cached
>>> for a while, befere being flushed to the shared memory?
>>>
>>>   
>> Changes are visible immediately.
>>
>> 
>
> OK, that is about sharing memory file. How about a shared file in
> which a file is a real physical file on the host?
>
> As far as I remember, there is a caution about sharing a file using
> mmap() between 2 processes, that is: if the first process modifies the
> shared file, it might take a while for the changes to be flushed from
> cache to the file. That means the other process doesnt see the change
> immediately.
>   

Changes to a mmap() file may not be flushed to the disk until an msync 
or munmap but if you've got it opened with MAP_SHARED, then everyone 
mapping will have access to the same physical memory IIUC.  You still 
need to use barriers to take into account SMP.  There may be some weird 
interactions if the area isn't mlocked but I'm not totally sure on that.

Regards,

Anthony Liguori

> I guess this problem affects us in this case, when we use a real
> (physical) file to share between 2 VMs, correct?
>
> Thanks,
> Jun
>
> -
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> ___
> kvm-devel mailing list
> kvm-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/kvm-devel
>
>   


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] [ANNOUNCE] kvm-46 release

[Jun Koi]

On 10/10/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
> Jun Koi wrote:
> > On 10/10/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
> >
> >> Jun Koi wrote:
> >>
> >>> Hi,
> >>>
> >>> On 10/10/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
> >>>
> >>>
>  We've now switched to allocating guest memory in userspace rather than
>  in the kernel.  This is important if you have a mainframe, but also if
>  you want to share memory between guests and implement nice features like
>  swapping.
> 
> 
> >>> This is interesting! But how can we do that now? (share memory between 
> >>> guests)
> >>>
> >>>
> >>>
> >> It's not exposed by qemu, but you can now mmap() some file (or use SysV
> >> shared memory) and use that as guest memory.
> >>
> >>
> >
> > OK, lets say we have 2 guest VMs share a memory, like mmap() a tmpfs
> > file (which is actually in memory). Now one writes to the memory
> > (shared file). Can we guarantee that the memory immediately updated,
> > so other will see the change immediately? Or the data might be cached
> > for a while, befere being flushed to the shared memory?
> >
>
> Changes are visible immediately.
>

OK, that is about sharing memory file. How about a shared file in
which a file is a real physical file on the host?

As far as I remember, there is a caution about sharing a file using
mmap() between 2 processes, that is: if the first process modifies the
shared file, it might take a while for the changes to be flushed from
cache to the file. That means the other process doesnt see the change
immediately.

I guess this problem affects us in this case, when we use a real
(physical) file to share between 2 VMs, correct?

Thanks,
Jun

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] [ANNOUNCE] kvm-46 release

[Haydn Solomon]

Thanks for clearing that up.


On 10/10/07, Dor Laor <[EMAIL PROTECTED]> wrote:
>
> Haydn Solomon wrote:
> > Should we be seeing a mmap file when running guests now or do we have
> > to use a special flag when running kvm?
> >
> Nope, the default is user space allocation were a regular malloc is used
> for allocating the guest ram from userspace.
> The mmap is for future shared memory implementations for parts of the
> guest memory space.
> > On 10/10/07, *Avi Kivity* < [EMAIL PROTECTED]
> > > wrote:
> >
> > Daniel P. Berrange wrote:
> > > On Wed, Oct 10, 2007 at 10:28:24AM +0200, Avi Kivity wrote:
> > >
> > >> We've now switched to allocating guest memory in userspace
> > rather than
> > >> in the kernel.  This is important if you have a mainframe, but
> > also if
> > >> you want to share memory between guests and implement nice
> > features like
> > >> swapping.
> > >>
> > >
> > > Is the memory allocation swappable by default, or still pinned
> > in RAM by
> > > default ?
> > >
> > >
> >
> > It's still not swappable.  That will come in a future release.
> >
> >
> > --
> > error compiling committee.c: too many arguments to function
> >
> >
> >
> -
> > This SF.net email is sponsored by: Splunk Inc.
> > Still grepping through log files to find problems?  Stop.
> > Now Search log events and configuration files using AJAX and a
> > browser.
> > Download your FREE copy of Splunk now >> http://get.splunk.com/
> > ___
> > kvm-devel mailing list
> > kvm-devel@lists.sourceforge.net
> > 
> > https://lists.sourceforge.net/lists/listinfo/kvm-devel
> > 
> >
> >
> > 
> >
> >
> -
> > This SF.net email is sponsored by: Splunk Inc.
> > Still grepping through log files to find problems?  Stop.
> > Now Search log events and configuration files using AJAX and a browser.
> > Download your FREE copy of Splunk now >> http://get.splunk.com/
> > 
> >
> > ___
> > kvm-devel mailing list
> > kvm-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/kvm-devel
> >
>
>
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] [ANNOUNCE] kvm-46 release

[Dor Laor]

Haydn Solomon wrote:
> Should we be seeing a mmap file when running guests now or do we have 
> to use a special flag when running kvm?
>
Nope, the default is user space allocation were a regular malloc is used 
for allocating the guest ram from userspace.
The mmap is for future shared memory implementations for parts of the 
guest memory space.
> On 10/10/07, *Avi Kivity* < [EMAIL PROTECTED] 
> > wrote:
>
> Daniel P. Berrange wrote:
> > On Wed, Oct 10, 2007 at 10:28:24AM +0200, Avi Kivity wrote:
> >
> >> We've now switched to allocating guest memory in userspace
> rather than
> >> in the kernel.  This is important if you have a mainframe, but
> also if
> >> you want to share memory between guests and implement nice
> features like
> >> swapping.
> >>
> >
> > Is the memory allocation swappable by default, or still pinned
> in RAM by
> > default ?
> >
> >
>
> It's still not swappable.  That will come in a future release.
>
>
> --
> error compiling committee.c: too many arguments to function
>
>
> -
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a
> browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> ___
> kvm-devel mailing list
> kvm-devel@lists.sourceforge.net
> 
> https://lists.sourceforge.net/lists/listinfo/kvm-devel
> 
>
>
> 
>
> -
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> 
>
> ___
> kvm-devel mailing list
> kvm-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/kvm-devel
>   


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] [ANNOUNCE] kvm-46 release

[Haydn Solomon]

Should we be seeing a mmap file when running guests now or do we have to use
a special flag when running kvm?

On 10/10/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
>
> Daniel P. Berrange wrote:
> > On Wed, Oct 10, 2007 at 10:28:24AM +0200, Avi Kivity wrote:
> >
> >> We've now switched to allocating guest memory in userspace rather than
> >> in the kernel.  This is important if you have a mainframe, but also if
> >> you want to share memory between guests and implement nice features
> like
> >> swapping.
> >>
> >
> > Is the memory allocation swappable by default, or still pinned in RAM by
> > default ?
> >
> >
>
> It's still not swappable.  That will come in a future release.
>
>
> --
> error compiling committee.c: too many arguments to function
>
>
> -
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> ___
> kvm-devel mailing list
> kvm-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/kvm-devel
>
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] [ANNOUNCE] kvm-46 release

[Avi Kivity]

Daniel P. Berrange wrote:
> On Wed, Oct 10, 2007 at 10:28:24AM +0200, Avi Kivity wrote:
>   
>> We've now switched to allocating guest memory in userspace rather than
>> in the kernel.  This is important if you have a mainframe, but also if
>> you want to share memory between guests and implement nice features like
>> swapping.
>> 
>
> Is the memory allocation swappable by default, or still pinned in RAM by
> default ?
>
>   

It's still not swappable.  That will come in a future release.


-- 
error compiling committee.c: too many arguments to function


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] [ANNOUNCE] kvm-46 release

[Daniel P. Berrange]

On Wed, Oct 10, 2007 at 10:28:24AM +0200, Avi Kivity wrote:
> We've now switched to allocating guest memory in userspace rather than
> in the kernel.  This is important if you have a mainframe, but also if
> you want to share memory between guests and implement nice features like
> swapping.

Is the memory allocation swappable by default, or still pinned in RAM by
default ?

Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-   Perl modules: http://search.cpan.org/~danberr/  -=|
|=-   Projects: http://freshmeat.net/~danielpb/   -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] [ANNOUNCE] kvm-46 release

[Farkas Levente]

Avi Kivity wrote:
> Farkas Levente wrote:
 we did a quick test against this version and it's turn out the smp
 guests are still not working. even if we start only one linux guest
 with
 4cpu on 4cpu host the guest kernel hangs at random stages of the kernel
 loading process (if we run more smp guests then they hang earlier, but
 different random stage), but it's never reach the end of the kernel so
 hang somewhere inside the kernel. and the cpu usage of these process
 goes up to until the qemu-kvm processes eat all cpus (ie. 100%). t
   
>>> What host cpu are you using?  What guest kernel version?  32-bit or
>>> 64-bit?
>>>
>>> I have no problems running a 4-way Linux guest here.
>>> 
>>
>> - host:
>>   - Intel(R) Core(TM)2 Quad CPU Q6600  @ 2.40GHz
>>   - Intel S3000AHV
>>   - 8GB RAM
>>   - CentOS-5
>>   - kernel-2.6.18-8.1.14.el5 x86_64 64bit
>> - guest-1:
>>   - CentOS-5
>>   - kernel-2.6.18-8.1.14.el5 i386 32bit
>> - guest-2:
>>   - CentOS-5
>>   - kernel-2.6.18-8.1.14.el5 x86_64 64bit
>> - guest-3:
>>   - Mandrake-9
>>   - kernel-2.4.19.16mdk-1-1mdk 32bit
>> - guest-4:
>>   - Windows XP Professional 32bit
>>
>> start the first guest-1 with 4cpu produce the above hang. (and of course
>> using kvm-46:-)
>>
>>   
> 
> Is it the only guest that hangs with -smp 4?  Or all of them?

if i start this guest alone it's hang. if i start all guest-{1,2,3,4}
than all linux guest hangs expect windows which runs but see only one
cpu. ok now i try it for you:-) so:

- host + guest-1 -> hang

- host + guest-2 -> hang
in this case i've got a stack trace too on the host, and the host
working 2 more minutes (!?) so i see the top part of the stack
(shift-pageup) but when i try to take a picture the host crash and i can
only see the end:-( but next time i bale to catch it:
---
BUG: soft lockup detected on CPU#0!

Call Trace:
   [] softlockup_tick+0xdb/0xed
 [] update_process_times+0x42/0x68
 [] smp_local_timer_interrupt+0x23/0x47
 [] smp_apic_timer_interrupt+0x41/0x47
 [] apic_timer_interrupt+0x66/0x6c
   [] :kvm:kvm_flush_remote_tlbs+0xfb/0x109
 [] :kvm:kvm_flush_remote_tlbs+0xea/0x109
 [] :kvm:kvm_mmu_pte_write+0x1fc/0x330
 [] :kvm:kvm_write_guest_page+0x98/0xa3
 [] :kvm:emulator_write_emulated_onepage+0x6e/0xce
 [] :kvm:x86_emulate_insn+0x2b99/0x3e58
 [] __memset+0x39/0xc0
 [] :kvm_intel:vmcs_readl+0x17/0x1c
 [] :kvm:emulate_instruction+0x152/0x290
 [] :kvm_intel:handle_exception+0x170/0x250
 [] :kvm:kvm_vcpu_ioctl+0x34b/0x10ba
 [] :kvm:kvm_vcpu_kick+0x34/0x8e
 [] :kvm:kvm_vm_ioctl+0x48a/0x6af
 [] zone_statistics+0x3e/0x6d
 [] get_page_from_freelist+0x35d/0x3cf
 [] zone_statistics+0x3e/0x6d
 [] get_page_from_freelist+0x35d/0x3cf
 [] __alloc_pages+0x65/0x2b2
 [] __next_cpu+0x19/0x28
 [] find_busiest_group+0x20d/0x621
 [] __next_cpu+0x19/0x28
 [] smp_send_reschedule+0x4e/0x53
 [] enqueue_task+0x41/0x56
 [] __activate_task+0x27/0x39
 [] try_to_wake_up+0x407/0x418
 [] __wake_up_common+0x3e/0x68
 [] __wake_up+0x38/0x4f
 [] __up_read+0x19/0x7f
 [] avc_has_perm+0x43/0x55
 [] inode_has_perm+0x56/0x63
 [] default_wake_function+0x0/0xe
 [] file_has_perm+0x94/0xa3
 [] do_ioctl+0x21/0x6b
 [] vfs_ioctl+0x248/0x261
 [] sys_ioctl+0x59/0x78
 [] tracesys+0xd1/0xdc
---
i hope shouldn't have to test all other guests:-(
but if i can help you in something more specific let me know:-)




-- 
  Levente   "Si vis pacem para bellum!"

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] [ANNOUNCE] kvm-46 release

[Avi Kivity]

Farkas Levente wrote:
>>> we did a quick test against this version and it's turn out the smp
>>> guests are still not working. even if we start only one linux guest with
>>> 4cpu on 4cpu host the guest kernel hangs at random stages of the kernel
>>> loading process (if we run more smp guests then they hang earlier, but
>>> different random stage), but it's never reach the end of the kernel so
>>> hang somewhere inside the kernel. and the cpu usage of these process
>>> goes up to until the qemu-kvm processes eat all cpus (ie. 100%). t
>>>   
>> What host cpu are you using?  What guest kernel version?  32-bit or 64-bit?
>>
>> I have no problems running a 4-way Linux guest here.
>> 
>
> - host:
>   - Intel(R) Core(TM)2 Quad CPU Q6600  @ 2.40GHz
>   - Intel S3000AHV
>   - 8GB RAM
>   - CentOS-5
>   - kernel-2.6.18-8.1.14.el5 x86_64 64bit
> - guest-1:
>   - CentOS-5
>   - kernel-2.6.18-8.1.14.el5 i386 32bit
> - guest-2:
>   - CentOS-5
>   - kernel-2.6.18-8.1.14.el5 x86_64 64bit
> - guest-3:
>   - Mandrake-9
>   - kernel-2.4.19.16mdk-1-1mdk 32bit
> - guest-4:
>   - Windows XP Professional 32bit
>
> start the first guest-1 with 4cpu produce the above hang. (and of course
> using kvm-46:-)
>
>   

Is it the only guest that hangs with -smp 4?  Or all of them?



-- 
error compiling committee.c: too many arguments to function


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] [ANNOUNCE] kvm-46 release

[Farkas Levente]

Avi Kivity wrote:
> Farkas Levente wrote:
>> Avi Kivity wrote:
>>  
>>> We've now switched to allocating guest memory in userspace rather than
>>> in the kernel.  This is important if you have a mainframe, but also if
>>> you want to share memory between guests and implement nice features like
>>> swapping.
>>> 
>>
>> we did a quick test against this version and it's turn out the smp
>> guests are still not working. even if we start only one linux guest with
>> 4cpu on 4cpu host the guest kernel hangs at random stages of the kernel
>> loading process (if we run more smp guests then they hang earlier, but
>> different random stage), but it's never reach the end of the kernel so
>> hang somewhere inside the kernel. and the cpu usage of these process
>> goes up to until the qemu-kvm processes eat all cpus (ie. 100%). t
> 
> 
> What host cpu are you using?  What guest kernel version?  32-bit or 64-bit?
> 
> I have no problems running a 4-way Linux guest here.

- host:
  - Intel(R) Core(TM)2 Quad CPU Q6600  @ 2.40GHz
  - Intel S3000AHV
  - 8GB RAM
  - CentOS-5
  - kernel-2.6.18-8.1.14.el5 x86_64 64bit
- guest-1:
  - CentOS-5
  - kernel-2.6.18-8.1.14.el5 i386 32bit
- guest-2:
  - CentOS-5
  - kernel-2.6.18-8.1.14.el5 x86_64 64bit
- guest-3:
  - Mandrake-9
  - kernel-2.4.19.16mdk-1-1mdk 32bit
- guest-4:
  - Windows XP Professional 32bit

start the first guest-1 with 4cpu produce the above hang. (and of course
using kvm-46:-)

-- 
  Levente   "Si vis pacem para bellum!"

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] [ANNOUNCE] kvm-46 release

[Avi Kivity]

Farkas Levente wrote:
> Avi Kivity wrote:
>   
>> We've now switched to allocating guest memory in userspace rather than
>> in the kernel.  This is important if you have a mainframe, but also if
>> you want to share memory between guests and implement nice features like
>> swapping.
>> 
>
> we did a quick test against this version and it's turn out the smp
> guests are still not working. even if we start only one linux guest with
> 4cpu on 4cpu host the guest kernel hangs at random stages of the kernel
> loading process (if we run more smp guests then they hang earlier, but
> different random stage), but it's never reach the end of the kernel so
> hang somewhere inside the kernel. and the cpu usage of these process
> goes up to until the qemu-kvm processes eat all cpus (ie. 100%). t


What host cpu are you using?  What guest kernel version?  32-bit or 64-bit?

I have no problems running a 4-way Linux guest here.

-- 
error compiling committee.c: too many arguments to function


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] [ANNOUNCE] kvm-46 release

[Farkas Levente]

Avi Kivity wrote:
> We've now switched to allocating guest memory in userspace rather than
> in the kernel.  This is important if you have a mainframe, but also if
> you want to share memory between guests and implement nice features like
> swapping.

we did a quick test against this version and it's turn out the smp
guests are still not working. even if we start only one linux guest with
4cpu on 4cpu host the guest kernel hangs at random stages of the kernel
loading process (if we run more smp guests then they hang earlier, but
different random stage), but it's never reach the end of the kernel so
hang somewhere inside the kernel. and the cpu usage of these process
goes up to until the qemu-kvm processes eat all cpus (ie. 100%). the
strange thing is that the host is running no error on console just these
 and similar are in dmesg:
---
Ignoring de-assert INIT to vcpu 1
SIPI to vcpu 1 vector 0x03
SIPI to vcpu 1 vector 0x03
Ignoring de-assert INIT to vcpu 2
SIPI to vcpu 2 vector 0x03
---

but the good news that if we run more single cpu guests (both linux and
windows) than it seems to working (at least in the last half an hour:-).
which means that kvm-46 is as usable as kvm-36 for us (which was not the
case with all previous version), but of course this's a very subjective
'fact':-)

-- 
  Levente   "Si vis pacem para bellum!"

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] [ANNOUNCE] kvm-46 release

[Farkas Levente]

Avi Kivity wrote:
> Farkas Levente wrote:
>> Avi Kivity wrote:
>>  
>>> We've now switched to allocating guest memory in userspace rather than
>>> in the kernel.  This is important if you have a mainframe, but also if
>>> you want to share memory between guests and implement nice features like
>>> swapping.
>>>
>>> Changes since kvm-45:
>>> - fix host oops on bad guest ioapic accesses
>>> - handle NMIs before enabling host interrupts
>>> - add general guest memory accessors (Izik Eidus)
>>> - allow user control over shadow cache size (Izik Eidus)
>>> - auto tune shadow cache size with guest memory (Izik Eidus)
>>> - allocate guest memory in userspace instead of in kernel (Izik Eidus)
>>> - code style fixes (Mike Day, Anthony Liguori)
>>> - lapic cleanups (Rusty Russell)
>>> - fix acpi interrupt reporting for FreeBSD
>>> - fix color problems on certain displays
>>> - Red Hat 7.1 support
>>> - vmmouse support (Dan Kenigsberg)
>>> - fix sdl window caption when keyboard is captured (Dan Kenigsberg)
>>> - improve libkvm configure script (Jerone Young)
>>> - improve bios compilation support on x86_64 hosts (Laurent Vivier)
>>> - fix acpi processor reporting for Windows 2000 with the ACPI HAL (Sheng
>>> Yang)
>>> 
>>
>> when i try to compile it on centos i've got this error (which is not
>> happend in kvm-45) :
>> --
>> iasl -tc -p acpi-dsdt.hex acpi-dsdt.dsl
>> make[1]: iasl: Command not found
>> --
>> where this iasl comes from? and where can i found it? i can't found in
>> any package even in external repos.
>>
>>   
> 
> How did you get this?  Normal 'make' doesn't try to compile the bios.

yes, but my spec based on fedora spec which use Jeremy Katz's patch to
bios boot menu, that's way i need it.

-- 
  Levente   "Si vis pacem para bellum!"

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] [ANNOUNCE] kvm-46 release

[Farkas Levente]

Farkas Levente wrote:
> Avi Kivity wrote:
>> We've now switched to allocating guest memory in userspace rather than
>> in the kernel.  This is important if you have a mainframe, but also if
>> you want to share memory between guests and implement nice features like
>> swapping.
>>
>> Changes since kvm-45:
>> - fix host oops on bad guest ioapic accesses
>> - handle NMIs before enabling host interrupts
>> - add general guest memory accessors (Izik Eidus)
>> - allow user control over shadow cache size (Izik Eidus)
>> - auto tune shadow cache size with guest memory (Izik Eidus)
>> - allocate guest memory in userspace instead of in kernel (Izik Eidus)
>> - code style fixes (Mike Day, Anthony Liguori)
>> - lapic cleanups (Rusty Russell)
>> - fix acpi interrupt reporting for FreeBSD
>> - fix color problems on certain displays
>> - Red Hat 7.1 support
>> - vmmouse support (Dan Kenigsberg)
>> - fix sdl window caption when keyboard is captured (Dan Kenigsberg)
>> - improve libkvm configure script (Jerone Young)
>> - improve bios compilation support on x86_64 hosts (Laurent Vivier)
>> - fix acpi processor reporting for Windows 2000 with the ACPI HAL (Sheng
>> Yang)
> 
> when i try to compile it on centos i've got this error (which is not
> happend in kvm-45) :
> --
> iasl -tc -p acpi-dsdt.hex acpi-dsdt.dsl
> make[1]: iasl: Command not found
> --
> where this iasl comes from? and where can i found it? i can't found in
> any package even in external repos.
> 

ok i find it for fedora and recompile it from there.

-- 
  Levente   "Si vis pacem para bellum!"

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] [ANNOUNCE] kvm-46 release

[Avi Kivity]

Farkas Levente wrote:
> Avi Kivity wrote:
>   
>> We've now switched to allocating guest memory in userspace rather than
>> in the kernel.  This is important if you have a mainframe, but also if
>> you want to share memory between guests and implement nice features like
>> swapping.
>>
>> Changes since kvm-45:
>> - fix host oops on bad guest ioapic accesses
>> - handle NMIs before enabling host interrupts
>> - add general guest memory accessors (Izik Eidus)
>> - allow user control over shadow cache size (Izik Eidus)
>> - auto tune shadow cache size with guest memory (Izik Eidus)
>> - allocate guest memory in userspace instead of in kernel (Izik Eidus)
>> - code style fixes (Mike Day, Anthony Liguori)
>> - lapic cleanups (Rusty Russell)
>> - fix acpi interrupt reporting for FreeBSD
>> - fix color problems on certain displays
>> - Red Hat 7.1 support
>> - vmmouse support (Dan Kenigsberg)
>> - fix sdl window caption when keyboard is captured (Dan Kenigsberg)
>> - improve libkvm configure script (Jerone Young)
>> - improve bios compilation support on x86_64 hosts (Laurent Vivier)
>> - fix acpi processor reporting for Windows 2000 with the ACPI HAL (Sheng
>> Yang)
>> 
>
> when i try to compile it on centos i've got this error (which is not
> happend in kvm-45) :
> --
> iasl -tc -p acpi-dsdt.hex acpi-dsdt.dsl
> make[1]: iasl: Command not found
> --
> where this iasl comes from? and where can i found it? i can't found in
> any package even in external repos.
>
>   

How did you get this?  Normal 'make' doesn't try to compile the bios.

You can download the iasl compiler from 
http://www.intel.com/technology/iapc/acpi/downloads.htm.

-- 
error compiling committee.c: too many arguments to function


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] [ANNOUNCE] kvm-46 release

[Farkas Levente]

Avi Kivity wrote:
> We've now switched to allocating guest memory in userspace rather than
> in the kernel.  This is important if you have a mainframe, but also if
> you want to share memory between guests and implement nice features like
> swapping.
> 
> Changes since kvm-45:
> - fix host oops on bad guest ioapic accesses
> - handle NMIs before enabling host interrupts
> - add general guest memory accessors (Izik Eidus)
> - allow user control over shadow cache size (Izik Eidus)
> - auto tune shadow cache size with guest memory (Izik Eidus)
> - allocate guest memory in userspace instead of in kernel (Izik Eidus)
> - code style fixes (Mike Day, Anthony Liguori)
> - lapic cleanups (Rusty Russell)
> - fix acpi interrupt reporting for FreeBSD
> - fix color problems on certain displays
> - Red Hat 7.1 support
> - vmmouse support (Dan Kenigsberg)
> - fix sdl window caption when keyboard is captured (Dan Kenigsberg)
> - improve libkvm configure script (Jerone Young)
> - improve bios compilation support on x86_64 hosts (Laurent Vivier)
> - fix acpi processor reporting for Windows 2000 with the ACPI HAL (Sheng
> Yang)

when i try to compile it on centos i've got this error (which is not
happend in kvm-45) :
--
iasl -tc -p acpi-dsdt.hex acpi-dsdt.dsl
make[1]: iasl: Command not found
--
where this iasl comes from? and where can i found it? i can't found in
any package even in external repos.

-- 
  Levente   "Si vis pacem para bellum!"

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] [ANNOUNCE] kvm-46 release

[Avi Kivity]

Jun Koi wrote:
> On 10/10/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
>   
>> Jun Koi wrote:
>> 
>>> Hi,
>>>
>>> On 10/10/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
>>>
>>>   
 We've now switched to allocating guest memory in userspace rather than
 in the kernel.  This is important if you have a mainframe, but also if
 you want to share memory between guests and implement nice features like
 swapping.

 
>>> This is interesting! But how can we do that now? (share memory between 
>>> guests)
>>>
>>>
>>>   
>> It's not exposed by qemu, but you can now mmap() some file (or use SysV
>> shared memory) and use that as guest memory.
>>
>> 
>
> OK, lets say we have 2 guest VMs share a memory, like mmap() a tmpfs
> file (which is actually in memory). Now one writes to the memory
> (shared file). Can we guarantee that the memory immediately updated,
> so other will see the change immediately? Or the data might be cached
> for a while, befere being flushed to the shared memory?
>   

Changes are visible immediately.


-- 
Do not meddle in the internals of kernels, for they are subtle and quick to 
panic.


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] [ANNOUNCE] kvm-46 release

[Jun Koi]

On 10/10/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
> Jun Koi wrote:
> > Hi,
> >
> > On 10/10/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
> >
> >> We've now switched to allocating guest memory in userspace rather than
> >> in the kernel.  This is important if you have a mainframe, but also if
> >> you want to share memory between guests and implement nice features like
> >> swapping.
> >>
> >
> > This is interesting! But how can we do that now? (share memory between 
> > guests)
> >
> >
>
> It's not exposed by qemu, but you can now mmap() some file (or use SysV
> shared memory) and use that as guest memory.
>

OK, lets say we have 2 guest VMs share a memory, like mmap() a tmpfs
file (which is actually in memory). Now one writes to the memory
(shared file). Can we guarantee that the memory immediately updated,
so other will see the change immediately? Or the data might be cached
for a while, befere being flushed to the shared memory?

Thanks,
Jun

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] [ANNOUNCE] kvm-46 release

[Avi Kivity]

Jun Koi wrote:
> Hi,
>
> On 10/10/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
>   
>> We've now switched to allocating guest memory in userspace rather than
>> in the kernel.  This is important if you have a mainframe, but also if
>> you want to share memory between guests and implement nice features like
>> swapping.
>> 
>
> This is interesting! But how can we do that now? (share memory between guests)
>
>   

It's not exposed by qemu, but you can now mmap() some file (or use SysV
shared memory) and use that as guest memory.

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to 
panic.


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] [ANNOUNCE] kvm-46 release

[Jun Koi]

Hi,

On 10/10/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
> We've now switched to allocating guest memory in userspace rather than
> in the kernel.  This is important if you have a mainframe, but also if
> you want to share memory between guests and implement nice features like
> swapping.

This is interesting! But how can we do that now? (share memory between guests)

Thanks,
Jun

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel