On 15/02/15 19:03, Jan Kiszka wrote:
> On 2015-02-15 19:01, Jan Kiszka wrote:
>> On 2015-02-15 16:30, Marc Zyngier wrote:
>>> On Sun, Feb 15 2015 at 3:07:50 pm GMT, Jan Kiszka
>>> wrote:
On 2015-02-15 15:59, Marc Zyngier wrote:
> On Sun, Feb 15 2015 at 2:40:40 pm GMT, Jan Kiszka
>
On 2015-02-16 09:57, Marc Zyngier wrote:
> On 15/02/15 19:03, Jan Kiszka wrote:
>> On 2015-02-15 19:01, Jan Kiszka wrote:
>>> On 2015-02-15 16:30, Marc Zyngier wrote:
On Sun, Feb 15 2015 at 3:07:50 pm GMT, Jan Kiszka
wrote:
> On 2015-02-15 15:59, Marc Zyngier wrote:
>> On Sun, F
On 16 February 2015 at 06:56, Jan Kiszka wrote:
> This applies to both emulated and KVM accelerated mode. If I run the
> same image (and guest kernel) emulated on my x86 box, there is still a
> difference between both disk modes, but it's not that excessive. On ARM
> the system requires minutes to
Hi,
next issue related to KVM/QEMU on the TK1: The guest image I'm running
gives proper framebuffer output when in emulation mode. Once KVM is
enabled, the screen is - at best - only initially updated. Sometimes I
see the famous tux images and a bit of the console texts, but usually it
stays black
On Mon, Feb 16, 2015 at 2:43 PM, Jan Kiszka wrote:
> Hi,
>
> next issue related to KVM/QEMU on the TK1: The guest image I'm running
> gives proper framebuffer output when in emulation mode. Once KVM is
> enabled, the screen is - at best - only initially updated. Sometimes I
> see the famous tux im
On 2015-02-16 10:20, Anup Patel wrote:
> On Mon, Feb 16, 2015 at 2:43 PM, Jan Kiszka wrote:
>> Hi,
>>
>> next issue related to KVM/QEMU on the TK1: The guest image I'm running
>> gives proper framebuffer output when in emulation mode. Once KVM is
>> enabled, the screen is - at best - only initiall
On 2015-02-16 10:34, Alexander Spyridakis wrote:
> On Mon, Feb 16, 2015 at 2:43 PM, Jan Kiszka wrote:
>> Hi,
>>
>> next issue related to KVM/QEMU on the TK1: The guest image I'm running
>> gives proper framebuffer output when in emulation mode. Once KVM is
>> enabled, the screen is - at best - onl
Hello all,
On a RHEL 6.4 server i created a vm with 2 VCPU and
expecting to see single process with 2 threads on host.
but
top -p "pid-of-qemu" -H
shows many threads randomly being created and
destroyed,"pid-of-qemu" remains the same but other threads' pid keep
on changing.
C
Hi Christoffer,
On Sun, Feb 15, 2015 at 9:03 PM, Christoffer Dall
wrote:
> Hi Anup,
>
> On Mon, Jan 12, 2015 at 09:49:13AM +0530, Anup Patel wrote:
>> On Mon, Jan 12, 2015 at 12:41 AM, Christoffer Dall
>> wrote:
>> > On Tue, Dec 30, 2014 at 11:19:13AM +0530, Anup Patel wrote:
>> >> (dropping pre
On s390, we've got to make sure to hold the IPTE lock while accessing
logical memory. So let's add an ioctl for reading and writing logical
memory to provide this feature for userspace, too.
Signed-off-by: Thomas Huth
---
Documentation/virtual/kvm/api.txt | 45 +++
arch/s39
On Mon, Feb 16, 2015 at 05:46:54PM +0530, Anup Patel wrote:
> Hi Christoffer,
>
> On Sun, Feb 15, 2015 at 9:03 PM, Christoffer Dall
> wrote:
> > Hi Anup,
> >
> > On Mon, Jan 12, 2015 at 09:49:13AM +0530, Anup Patel wrote:
> >> On Mon, Jan 12, 2015 at 12:41 AM, Christoffer Dall
> >> wrote:
> >> >
Synchronized the kvm.h Linux header for the new ioctl.
Signed-off-by: Thomas Huth
---
linux-headers/linux/kvm.h | 21 +
1 files changed, 21 insertions(+), 0 deletions(-)
diff --git a/linux-headers/linux/kvm.h b/linux-headers/linux/kvm.h
index 12045a1..a5f2c8e 100644
--- a/
These two patches enable QEMU to make use of the new KVM_GUEST_MEM_OP
ioctl on s390x (see my kernel patch with the title "KVM: s390: Add MEMOP
ioctls for reading/writing guest memory" that I've posted on the KVM
mailing list).
The first patch in this series updates the Linux headers with the new
io
Add code to make use of the new ioctl for reading from / writing to
virtual guest memory. By using the ioctl, the memory accesses are now
protected with the so-called ipte-lock in the kernel.
Signed-off-by: Thomas Huth
---
target-s390x/cpu.h|7 +++
target-s390x/kvm.c| 3
Juan Quintela wrote:
> Hi
>
> Please, send any topic that you are interested in covering.
Gentle reminder that we still don't have agenda for tomorrow call.
Thanks, Juan.
>
>
> Call details:
>
> By popular demand, a google calendar public entry with it
>
>
> https://www.google.com/calendar
On 16/02/2015 11:54, mad Engineer wrote:
> Hello all,
> On a RHEL 6.4 server i created a vm with 2 VCPU and
> expecting to see single process with 2 threads on host.
> but
> top -p "pid-of-qemu" -H
>
> shows many threads randomly being created and
> destroyed,"pid-of-qemu" r
On 15/02/15 17:30, Raghavendra K T wrote:
> --- a/arch/x86/xen/spinlock.c
> +++ b/arch/x86/xen/spinlock.c
> @@ -41,7 +41,7 @@ static u8 zero_stats;
> static inline void check_zero(void)
> {
> u8 ret;
> - u8 old = ACCESS_ONCE(zero_stats);
> + u8 old = READ_ONCE(zero_stats);
> i
Hello you guys,
it is possible to decrypt a kvm volume only by using the command line
after starting it?
Best regards
Henry
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/m
I can observe this only one of the Intel Xeon machines (which has 48
CPUs and 1TB memory), but very reliably reproducible.
Reproducer:
- Just ensure physical host (L0) and guest hypervisor (L1) are running
3.20.0-0.rc0.git5.1 Kernel (I used from Fedora's Rawhide).
Preferably on an Inte
Thanks for the response.
Can a vm process create any number of extra threads based
on i/o requirement ,or is there any relation between number of VCPU
allowed and these extra threads.
I hope these threads are for disk i/o and for network it uses
vhost-'pid' process.
Thanks for your he
On 2015-02-16 21:40, Kashyap Chamarthy wrote:
> I can observe this only one of the Intel Xeon machines (which has 48
> CPUs and 1TB memory), but very reliably reproducible.
>
>
> Reproducer:
>
> - Just ensure physical host (L0) and guest hypervisor (L1) are running
> 3.20.0-0.rc0.git5.1 Ke
On 17/02/2015 05:44, mad Engineer wrote:
> Thanks for the response.
>Can a vm process create any number of extra threads based
> on i/o requirement ,or is there any relation between number of VCPU
> allowed and these extra threads.
No, there is not relation. The I/O threads are crea
22 matches
Mail list logo
