Avi Kivity a écrit :
> Aurelien Jarno wrote:
>> On Sat, Jul 21, 2007 at 12:25:45AM +0200, Aurelien Jarno wrote:
>>
>>> Hi,
>>>
>>> I have just noticed that there is a huge performance regression in
>>> network transfers between kvm-29 and kvm-31. Using the RTL8139 emulated
>>> card, I have seen
Hi,
Due to changes to kmem_cache_create, kvm-31 fails to build against
linux-2.6.22-git16:
CC [M] /home/users/chris/rpm/BUILD/kvm-31/kernel/vmx-debug.o
CC [M] /home/users/chris/rpm/BUILD/kvm-31/kernel/kvm_main.o
CC [M] /home/users/chris/rpm/BUILD/kvm-31/kernel/mmu.o
/home/users/chris/rp
Hi,
Could anybody explain to me why we need cache_regs()? And in which
case we should call this function?
On vmx, cache_regs() saves RSP & RIP, but ignore other registers. Why is that?
Thank you,
Jun
-
This SF.net email is
David Windsor wrote:
> On 7/21/07 2:21 AM, "Avi Kivity" <[EMAIL PROTECTED]> wrote:
>
>
>> Anthony Liguori wrote:
>>
>>> James Morris wrote:
>>>
>>>
On Fri, 20 Jul 2007, Daniel P. Berrange wrote:
> It could be - if your put the policy a
Hi all,
For a long time I am seeing data corruption in guests when using KVM,
but I am convinced only since today that the problem comes from KVM.
The symptoms are a few bytes that are mangled to 0x00 in a file that has
been written. For now I have only seen 2 or 4 consecutive bytes mangled,
but
Aurelien Jarno wrote:
> Hi all,
>
> For a long time I am seeing data corruption in guests when using KVM,
> but I am convinced only since today that the problem comes from KVM.
>
> The symptoms are a few bytes that are mangled to 0x00 in a file that has
> been written. For now I have only seen 2 or
Hi,
I found there is a bug with configure file shipped with kvm-31. Here is
the part of configure file:
===
target_cpu() {
if [[ $(uname -m) = i?86 ]]; then
echo x86_64
else
uname -m
fi
}
===
!?86 will match i386,
On Sat, Jul 21, 2007 at 12:46:29PM -0500, Anthony Liguori wrote:
> Aurelien Jarno wrote:
> >Hi all,
> >
> >For a long time I am seeing data corruption in guests when using KVM,
> >but I am convinced only since today that the problem comes from KVM.
> >
> >The symptoms are a few bytes that are mangl
On Sat, 21 Jul 2007, Anthony Liguori wrote:
> Can you already write an selinux policy that changes the label of a
> process when it open()s a different file?
No, and you normally want to do this over an exec anyway, to ensure the
new execution state is clean.
- James
--
James Morris
<[EMAIL
Aurelien Jarno wrote:
> On Sat, Jul 21, 2007 at 12:46:29PM -0500, Anthony Liguori wrote:
>
>> Aurelien Jarno wrote:
>>
>>> Hi all,
>>>
>>> For a long time I am seeing data corruption in guests when using KVM,
>>> but I am convinced only since today that the problem comes from KVM.
>>>
>>> T
On Sat, Jul 21, 2007 at 01:03:42PM -0500, Anthony Liguori wrote:
> >I am using raw files for the disk in all cases.
> >
> >Note that I have just seen a three bytes corruption. Building the glibc
> >seems to be a good way to reproduce the bug, as a lot of source files
> >are generated on the fly dur
James Morris wrote:
> On Sat, 21 Jul 2007, Anthony Liguori wrote:
>
>> Can you already write an selinux policy that changes the label of a
>> process when it open()s a different file?
>
> No, and you normally want to do this over an exec anyway, to
> ensure the new execution state is clean.
>
T
Just curious, is kvm-devel a moderated list? I sent two emails to the
list, but neither made to the list. If it's moderated list, please at
least let me know why they are rejected. If not, then there is something
wrong with the list server receiving emails.
Simon
---
Hi,
In kvm_vcpu_ioctl_get_regs() function (kvm_main.c), we have a comment
like this: "Dont leak debug flags in case they were set for guest
debugging".
What is the reasons that make us filter out TF and RF bit in EFLAGS like that?
Thanks,
Jun
>Hi,
>
>Could anybody explain to me why we need cache_regs()? And in which
>case we should call this function?
It's done in order to copy the content of several vmcs registers into
regular variables.
Decache does the opposite
>
>On vmx, cache_regs() saves RSP & RIP, but ignore other registers. Wh
15 matches
Mail list logo