Hi,
If I use the kernel function "get_user_pages()" within a guest kernel
module, will this ensure that the
guests pages are never swapped out by the host ? Will it lock these
pages in memory ?
(Has anyone tried this ? )
Thanks
Arn
--
To unsubscribe from this list: send the line "unsubscribe kvm
On Mon, Jul 7, 2008 at 6:29 PM, Anthony Liguori <[EMAIL PROTECTED]> wrote:
> Avi Kivity wrote:
>>
>> Mohammed Gamal wrote:
>>
>> I think they're fine. Can you check the vmentry patch now, with Anthony's
>> testcase?
>
> The following patch makes the problem almost 100% reproducible on my system.
>
Switching from e1000 to rtl8139 appears to work around the issue.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Glauber Costa wrote:
On Mon, Jul 7, 2008 at 4:21 PM, Anthony Liguori <[EMAIL PROTECTED]> wrote:
Marcelo Tosatti wrote:
On Mon, Jul 07, 2008 at 03:27:16PM -0300, Glauber Costa wrote:
I agree. A paravirt solution solves the problem.
Please, look at the patch I've attached.
It does __delay
Andy Smith wrote:
Hi,
Is it possible at the moment to export a single partition to a kvm
guest as a virtio block device, like you can with Xen? e.g. with
LVM on the host, /dev/somevg/somelv -> /dev/vda1 ?
As far as I can see at the moment this is possible but it would have
to be the whole of /
Sukanto Ghosh wrote:
1. Is the maximum no. of vcpus in a particular guest limited to the
no. of host cpus ? (I guess not)
No.
2. Is there any attempt made to co-schedule all of a guest's vcpus, in
order to avoid any spinlock holding problem ?
Right now, no. There is some discussion
Bugs item #2012799, was opened at 2008-07-07 16:29
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=2012799&group_id=180599
Please note that this message will contain a full copy
On Mon, Jul 7, 2008 at 3:09 PM, Sukanto Ghosh
<[EMAIL PROTECTED]> wrote:
> 3. Are there any means to do content-based page sharing between guests
> as VMware does ?
is it VMWare, or NetApp the one doing this? or you mean RAM page
sharing? if so, sounds like a big performance tradeoff for a little
1. Is the maximum no. of vcpus in a particular guest limited to the
no. of host cpus ? (I guess not)
2. Is there any attempt made to co-schedule all of a guest's vcpus, in
order to avoid any spinlock holding problem ?
3. Are there any means to do content-based page sharing between guests
as VMwa
On Mon, Jul 07, 2008 at 02:31:55PM -0300, Marcelo Tosatti wrote:
> On Sun, Jul 06, 2008 at 12:15:56AM +0300, Avi Kivity wrote:
> > Marcelo Tosatti wrote:
> >> On Sat, Jul 05, 2008 at 08:25:30PM +0300, Avi Kivity wrote:
> >>
> @@ -1955,6 +1955,22 @@ void kvm_mmu_slot_remove_write_access(st
>
On Mon, Jul 7, 2008 at 4:21 PM, Anthony Liguori <[EMAIL PROTECTED]> wrote:
> Marcelo Tosatti wrote:
>>
>> On Mon, Jul 07, 2008 at 03:27:16PM -0300, Glauber Costa wrote:
>>
I agree. A paravirt solution solves the problem.
>>>
>>> Please, look at the patch I've attached.
>>>
>>> It do
Marcelo Tosatti wrote:
On Mon, Jul 07, 2008 at 03:27:16PM -0300, Glauber Costa wrote:
I agree. A paravirt solution solves the problem.
Please, look at the patch I've attached.
It does __delay with host help. This may have the nice effect of not
busy waiting for long-enough delays,
On Fri, Jul 4, 2008 at 6:57 PM, David Mair <[EMAIL PROTECTED]> wrote:
> Slohm Gadaburi wrote:
>> I found out I can't use Ubuntu's kvm package because it doesn't
>> support vm snapshots.
>>
>> I am going to use a vanilla kvm and was wondering which version do you
>> recommend me to use
>> (my bigges
On Mon, Jul 07, 2008 at 03:27:16PM -0300, Glauber Costa wrote:
> > I agree. A paravirt solution solves the problem.
>
> Please, look at the patch I've attached.
>
> It does __delay with host help. This may have the nice effect of not
> busy waiting for long-enough delays, and may well.
>
> It
On Sun, Jul 6, 2008 at 10:56 PM, Anthony Liguori <[EMAIL PROTECTED]> wrote:
> Glauber Costa wrote:
>>
>> Marcelo Tosatti wrote:
>>>
>>> Hello,
>>>
>>> I have been discussing with Glauber and Gerd the problem where KVM
>>> guests miscalibrate loops_per_jiffy if there's sufficient load on the
>>> hos
On Wed, Jul 02, 2008 at 01:40:21PM -0300, Marcelo Tosatti wrote:
> I have been discussing with Glauber and Gerd the problem where KVM
> guests miscalibrate loops_per_jiffy if there's sufficient load on the
> host.
>
> calibrate_delay_direct() failed to get a good estimate for
> loops_per_jiffy.
>
On Mon, Jul 7, 2008 at 2:12 PM, Jamie Lokier <[EMAIL PROTECTED]> wrote:
> Gerd Hoffmann wrote:
>> Glauber Costa wrote:
>> > Talking to hollis last week, he pointed out that a better solution
>> > would be to make all of them to use the same kernel interface. It's a
>> > valid approach, but I believ
On Sun, Jul 06, 2008 at 12:15:56AM +0300, Avi Kivity wrote:
> Marcelo Tosatti wrote:
>> On Sat, Jul 05, 2008 at 08:25:30PM +0300, Avi Kivity wrote:
>>
@@ -1955,6 +1955,22 @@ void kvm_mmu_slot_remove_write_access(st
}
}
+int kvm_mmu_slot_has_shadowed_page(struct kvm *kvm,
Several times over the last few days, I've lost network connectivity
from one of my guests. This has happened only during interactive
sessions in which I take an action resulting in a large screen update. I
have tried flood pinging (only with the default, small packet size), and
not been able t
Gerd Hoffmann wrote:
> Glauber Costa wrote:
> > Talking to hollis last week, he pointed out that a better solution
> > would be to make all of them to use the same kernel interface. It's a
> > valid approach, but I believe an user-space interface would be more
> > flexible. That's why I'm still mai
On Mon, 2008-07-07 at 15:56 +0200, [EMAIL PROTECTED] wrote:
> From: Christian Ehrhardt <[EMAIL PROTECTED]>
>
> The current implementation of kvmtrace uses always a 64 bit cycle variable,
> but get_cycles() which is used to fill it is "unsigned long" which might be 32
> bit.
> This reduces the accu
On Sat, Jul 5, 2008 at 5:29 AM, Mark McLoughlin <[EMAIL PROTECTED]> wrote:
> It's certainly possible the hangs you're seeing were caused by the
> IOAPIC interrupt injection bug I just sent out a fix for - you could try
> doing an install either running kvm-qemu -no-kvm-irqchip or booting the
> gues
On Mon, 2008-07-07 at 15:56 +0200, [EMAIL PROTECTED] wrote:
> From: Christian Ehrhardt <[EMAIL PROTECTED]>
>
> The current implementation of kvmtrace uses always a 64 bit cycle variable,
> but get_cycles() which is used to fill it is "unsigned long" which might be 32
> bit.
> This reduces the accu
On Mon, Jul 7, 2008 at 11:07 PM, Christian Ehrhardt
<[EMAIL PROTECTED]> wrote:
> Jun Koi wrote:
>>
>> Hi,
>>
>> Could anybody explain a bit about kvmtrace? I cannot find any doc on
>> it anywhere.
>>
>> - Is there any short usage instruction for kvmtrace?
>>
>
> I don't know if there is an official
Avi Kivity wrote:
Mohammed Gamal wrote:
I think they're fine. Can you check the vmentry patch now, with
Anthony's testcase?
The following patch makes the problem almost 100% reproducible on my
system. This strongly suggests a timing issue.
Regards,
Anthony Liguori
foo.patch
Descripti
Avi Kivity wrote:
Mohammed Gamal wrote:
On Mon, Jul 7, 2008 at 5:24 PM, Avi Kivity <[EMAIL PROTECTED]> wrote:
Mohammed Gamal wrote:
Hello,
Guillaume Thouvenin's VMentry failure detection patch was reverted
before because it broke guest rebooting. Although it turned out it
didn't, it was
Mohammed Gamal wrote:
On Mon, Jul 7, 2008 at 5:24 PM, Avi Kivity <[EMAIL PROTECTED]> wrote:
Mohammed Gamal wrote:
Hello,
Guillaume Thouvenin's VMentry failure detection patch was reverted
before because it broke guest rebooting. Although it turned out it
didn't, it was preferred not to
On Mon, Jul 7, 2008 at 5:24 PM, Avi Kivity <[EMAIL PROTECTED]> wrote:
> Mohammed Gamal wrote:
>>
>> Hello,
>> Guillaume Thouvenin's VMentry failure detection patch was reverted
>> before because it broke guest rebooting. Although it turned out it
>> didn't, it was preferred not to re-include it bec
Mohammed Gamal wrote:
Hello,
Guillaume Thouvenin's VMentry failure detection patch was reverted
before because it broke guest rebooting. Although it turned out it
didn't, it was preferred not to re-include it because it was not
reliable enough. Although it is working fine with me, I want to know
Jun Koi wrote:
Hi,
Could anybody explain a bit about kvmtrace? I cannot find any doc on
it anywhere.
- Is there any short usage instruction for kvmtrace?
I don't know if there is an official doc yet, but you can just start
with the simple version like:
./kvmtrace -o outfile -w 5
which tr
Hello,
Guillaume Thouvenin's VMentry failure detection patch was reverted
before because it broke guest rebooting. Although it turned out it
didn't, it was preferred not to re-include it because it was not
reliable enough. Although it is working fine with me, I want to know
why it wasn't re-include
From: Jerone Young <[EMAIL PROTECTED]>
This patch enables KVM_TRACE to build for PowerPC arch. This means just
adding sections to Kconfig and Makefile.
Signed-off-by: Jerone Young <[EMAIL PROTECTED]>
Signed-off-by: Christian Ehrhardt <[EMAIL PROTECTED]>
---
[diffstat]
Kconfig | 11 ++
[PATCH 1/5] kvmtrace: Remove use of bit fields in kvm trace structure v3
From: Christian Ehrhardt <[EMAIL PROTECTED]>
From: Jerone Young <[EMAIL PROTECTED]>
This patch fixes kvmtrace use on big endian systems. When using bit fields the
compiler will lay data out in the wrong order expected when l
From: Christian Ehrhardt <[EMAIL PROTECTED]>
This series contains the revised patch set Jerone/Hollis posted last week
as well as the extension to use the KVM_TRACE infrastructure to trace
the embedded powerpc instruction emulation.
The series contains five patches (2 generic / 3 powerpc code):
S
From: Christian Ehrhardt <[EMAIL PROTECTED]>
This patch adds trace points for the instruction emulation on embedded powerpc
utilizing the KVM_TRACE interface.
The userspace portion to map and analyze the new ppc trace records will follow
soon.
Signed-off-by: Christian Ehrhardt <[EMAIL PROTECTED]>
From: Christian Ehrhardt <[EMAIL PROTECTED]>
The current implementation of kvmtrace uses always a 64 bit cycle variable,
but get_cycles() which is used to fill it is "unsigned long" which might be 32
bit.
This reduces the accuracy e.g. on embedded powerpc since we would have a 64bit
value but get_
From: Jerone Young <[EMAIL PROTECTED]>
From: Jerone Young <[EMAIL PROTECTED]>
This patch adds trace points to track powerpc TLB activities using the
KVM_TRACE infrastructure.
Update to v1:
- fixed wrong indents reported by checkpatch
Signed-off-by: Jerone Young <[EMAIL PROTECTED]>
Signed-
Glauber Costa wrote:
> Talking to hollis last week, he pointed out that a better solution
> would be to make all of them to use the same kernel interface. It's a
> valid approach, but I believe an user-space interface would be more
> flexible. That's why I'm still maintaining this set (now in tree-
Bugs item #2012453, was opened at 2008-07-07 14:36
Message generated for change (Comment added) made by blinkiz
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2012453&group_id=180599
Please note that this message will contain a full copy of the comment t
Bugs item #2012453, was opened at 2008-07-07 14:36
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=2012453&group_id=180599
Please note that this message will contain a full copy
Bugs item #1881532, was opened at 2008-01-29 02:16
Message generated for change (Comment added) made by ravpl
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1881532&group_id=180599
Please note that this message will contain a full copy of the comment thr
Amit Shah wrote:
This will be useful for acking irqs of assigned devices
And also for improving time drift tracking.
Please make this more generic by having a list of callbacks. There
could also be just one list, rather than one for the ioapic and one for
the pic as implemented now.
I
Avi Kivity wrote:
> Zhang, Xiantao wrote:
>> Avi Kivity wrote:
>>
>>> Zhang, Xiantao wrote:
>>>
Hi, Avi
This patchset intends to enable kvm/ia-64 to build kvm
components in userspace. You know, current userspace code only
supports x86 to build kvm components, but kvm/ia
Qemu e1000 NIC didn't work well for guest windows on xen/ia64.
After investigation, it's a e1000 TSE bug.
Previously, all data descriptors used TSE context descriptor by default,
It's not correct, per spec, data descriptor uses TSE bit to indicate
whether use TSE,
Legacy data descripter never use T
Bugs item #2009439, was opened at 2008-07-03 06:51
Message generated for change (Comment added) made by markmc
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2009439&group_id=180599
Please note that this message will contain a full copy of the comment th
Hi All,
This is today's KVM test result against kvm.git
dfed967e2c690f1737b98940152e3e2655e6ab42 and kvm-userspace.git
619ca34310a8968b6939fa6aba5b85a16b20315e.
There's no new issue today.
Three Old Issues:
1. 32bits Rhel5/FC6 guest may fail to re
46 matches
Mail list logo
