Hello!
Anyone has succeed on making a kvm guest linux, say fedora 16, with
vmwgfx driver?
I want to make it work over dri interface, but probably without the
x-org, it will be some testbed for wayland builds.
My host is a fedora 16, with kernel 3.3.0-8, with a working dri card.
I run the kvm:
qe
On Wed, Apr 18, 2012 at 07:22:47PM +0300, Avi Kivity wrote:
> MMIO that are split across a page boundary are currently broken - the
> code does not expect to be aborted by the exit to userspace for the
> first MMIO fragment.
>
> This patch fixes the problem by generalizing the current code for han
On 04/19/2012 11:59 AM, Gleb Natapov wrote:
> On Wed, Apr 18, 2012 at 07:22:47PM +0300, Avi Kivity wrote:
> > MMIO that are split across a page boundary are currently broken - the
> > code does not expect to be aborted by the exit to userspace for the
> > first MMIO fragment.
> >
> > This patch fi
On 04/19/2012 10:34 AM, Alberich de megres wrote:
> Hello!
>
> Anyone has succeed on making a kvm guest linux, say fedora 16, with
> vmwgfx driver?
> I want to make it work over dri interface, but probably without the
> x-org, it will be some testbed for wayland builds.
>
> My host is a fedora 16,
The patch introduces a bitmap that will hold reasons apic should be
checked during vmexit. This is in a preparation for vp eoi patch
that will add one more check on vmexit. With the bitmap we can do
if(apic_attention) to check everything simultaneously which will
add zero overhead on the fast path.
On 04/18/2012 08:07 AM, Gerhard Wiesinger wrote:
> Negative also here:
> Don't see anything on screen on startup...
>
> From log, latest qemu-kvm git version:
> Running option rom at c180:3d4e
> Running option rom at c180:3da2
> Running option rom at c180:3df6
> Running option rom at c580:0003
> qe
Thanks!
Is there any other way on having at least 2d acceleration with qemu?
If it is possible, using ksm/drm.
Thanks!!!
On Thu, Apr 19, 2012 at 11:17 AM, Avi Kivity wrote:
> On 04/19/2012 10:34 AM, Alberich de megres wrote:
>> Hello!
>>
>> Anyone has succeed on making a kvm guest linux, say fe
On 04/19/2012 12:33 PM, Gleb Natapov wrote:
> The patch introduces a bitmap that will hold reasons apic should be
> checked during vmexit. This is in a preparation for vp eoi patch
> that will add one more check on vmexit. With the bitmap we can do
> if(apic_attention) to check everything simultane
On 04/19/2012 12:53 PM, Alberich de megres wrote:
> Thanks!
>
> Is there any other way on having at least 2d acceleration with qemu?
> If it is possible, using ksm/drm.
>
-vga qxl.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "un
I tried this one, but I have no /dev/dri/card0,
nor any module is loaded in the kernel that uses drm.
On Thu, Apr 19, 2012 at 11:53 AM, Avi Kivity wrote:
> On 04/19/2012 12:53 PM, Alberich de megres wrote:
>> Thanks!
>>
>> Is there any other way on having at least 2d acceleration with qemu?
>>
Folks,
This is a test report on upstream qemu-kvm testing (24853eece248d4a58d705c).
Tests were executed using latest autotest git (6a15572d5307fa0b).
This time we have tested 3 guests.
We are analysing the test results further to find out if the failure is in
autotest or in qemu-kvm. Will post
On Thu, Apr 19, 2012 at 12:33:22PM +0300, Gleb Natapov wrote:
> The patch introduces a bitmap that will hold reasons apic should be
> checked during vmexit. This is in a preparation for vp eoi patch
> that will add one more check on vmexit. With the bitmap we can do
> if(apic_attention) to check ev
On Thu, Apr 19, 2012 at 11:57:50AM +0200, Alberich de megres wrote:
> I tried this one, but I have no /dev/dri/card0,
> nor any module is loaded in the kernel that uses drm.
>
It doesn't use DRM/DRI yet. There is a userspace X driver,
xf86-video-qxl, that directly accesses the pci.
>
>
>
> On
On 04/19/2012 01:26 PM, Gleb Natapov wrote:
> >
> > Unrelated: this pattern is probably common. Would be nice to have a
> > __deposit_bit() function.
> >
> What semantics should it have? Set bit A in bitmap B if value C is
> non-zero?
>
void __deposit_bit(bool bit, unsigned index, unsigned long
From: Avi Kivity
Subject: Re: [PATCH 0/4] Export offsets of VMCS fields as note information for
kdump
Date: Wed, 18 Apr 2012 14:56:39 +0300
> On 04/18/2012 12:49 PM, zhangyanfei wrote:
>> >>
>> >
>> > What type of resource? Can you give an example?
>> >
>> Sorry. No concrete example for now.
On 04/19/2012 01:36 PM, HATAYAMA Daisuke wrote:
> From: Avi Kivity
> Subject: Re: [PATCH 0/4] Export offsets of VMCS fields as note information
> for kdump
> Date: Wed, 18 Apr 2012 14:56:39 +0300
>
> > On 04/18/2012 12:49 PM, zhangyanfei wrote:
> >> >>
> >> >
> >> > What type of resource? Can y
On 04/19/2012 01:35 PM, Avi Kivity wrote:
> On 04/19/2012 01:26 PM, Gleb Natapov wrote:
> > >
> > > Unrelated: this pattern is probably common. Would be nice to have a
> > > __deposit_bit() function.
> > >
> > What semantics should it have? Set bit A in bitmap B if value C is
> > non-zero?
> >
>
The patch introduces a bitmap that will hold reasons apic should be
checked during vmexit. This is in a preparation for vp eoi patch
that will add one more check on vmexit. With the bitmap we can do
if(apic_attention) to check everything simultaneously which will
add zero overhead on the fast path.
Forget changelog:
v1->v2:
- Add a comment before define of attention bits.
On Thu, Apr 19, 2012 at 02:06:29PM +0300, Gleb Natapov wrote:
> The patch introduces a bitmap that will hold reasons apic should be
> checked during vmexit. This is in a preparation for vp eoi patch
> that will add one mor
On Thu, Apr 19, 2012 at 12:53:12PM +0300, Avi Kivity wrote:
> On 04/19/2012 12:33 PM, Gleb Natapov wrote:
> > The patch introduces a bitmap that will hold reasons apic should be
> > checked during vmexit. This is in a preparation for vp eoi patch
> > that will add one more check on vmexit. With the
From: Avi Kivity
Subject: Re: [PATCH 0/4] Export offsets of VMCS fields as note information for
kdump
Date: Thu, 19 Apr 2012 13:42:42 +0300
> On 04/19/2012 01:36 PM, HATAYAMA Daisuke wrote:
>> From: Avi Kivity
>> Subject: Re: [PATCH 0/4] Export offsets of VMCS fields as note information
>> for
On 04/19/2012 02:27 PM, HATAYAMA Daisuke wrote:
> >> The reason why we want to retrieve guest machine's memory image as
> >> crash dump is that then we can debug guest machine's status using
> >> symbolic debugger such as gdb and crash utility.
> >>
> >> This is very useful. Please consider the sit
On Tue, Apr 17, 2012 at 09:46:44PM -0600, Alex Williamson wrote:
> As pointed out by Jason Baron, when assigning a device to a guest
> we first set the iommu domain pointer, which enables mapping
> and unmapping of memory slots to the iommu. This leaves a window
> where this path is enabled, but w
Linus, please pull from
git://git.kernel.org/pub/scm/virt/kvm/kvm.git master
To receive the following updates
Alex Williamson (2):
KVM: unmap pages from the iommu when slots are removed
KVM: lock slots_lock around device assignment
Avi Kivity (1):
KVM: VMX: Fix kvm_set_share
From: Avi Kivity
Subject: Re: [PATCH 0/4] Export offsets of VMCS fields as note information for
kdump
Date: Thu, 19 Apr 2012 14:31:56 +0300
> On 04/19/2012 02:27 PM, HATAYAMA Daisuke wrote:
>> >> The reason why we want to retrieve guest machine's memory image as
>> >> crash dump is that then we
On 04/19/2012 03:01 PM, HATAYAMA Daisuke wrote:
> >> It would be not helpful for the qemu crash case you are concerned
> >> about. We want to use the guest state data to look into guest
> >> machine's image in the crasshed qemu.
> >
> > Why?
> >
>
> It seems natural to check the situation from gu
Hello,
The Call for Proposals for the Linux Plumbers Conf 2012 is out. We're
looking for speakers to talk at the Virtualization microconference as
well as the main conference. The deadline for proposal submissions is
1st May. This year's edition of LPC is co-located with LinuxCon NA
and will be
Hello,
good news:
On Friday 30 March 2012 19:44:50 you wrote:
> On Monday 09 January 2012 12:41:41 Philipp Hahn wrote:
> > one of our VMs regularly get stuck: the VM is completely unresponsive (no
> > ssh, no serial console, no VNC). Using "gdbserver" and a remote system to
> > debug the running
This is a prototype for ACPI memory hotplug on x86_64 target. Based on some
earlier work and comments from Gleb.
Memslot devices are modeled with a new qemu command line
"-memslot id=name,start=start_addr,size=sz,node=pxm"
user is responsible for defining memslots with meaningful start/size val
The memory device generation is guided by qemu paravirt info. Seabios
first uses the info to setup SRAT entries for the hotplug-able memory slots.
Afterwards, build_memssdt uses the created SRAT entries to generate
appropriate memory device objects. One memory device (and corresponding SRAT
en
Define SSDT hotplug-able memory devices in _SB namespace. The dynamically
generated SSDT includes per memory device hotplug methods. These methods
just call methods defined in the DSDT. Also dynamically generate a MTFY
method and a MEON array of the online/available memory devices. Add file
src/ss
Each hotplug-able memory slot is a SysBusDevice. All memslots are initially
unpopulated. A hot-add operation for a particular memory slot creates a new
MemoryRegion of the given physical address offset, size and node proximity,
and attaches it to main system memory as a sub_region. A hot-remove
A 32-byte register is used to present up to 256 hotplug-able memory devices
to BIOS and OSPM. Hot-add and hot-remove functions trigger an ACPI hotplug
event through these. Only reads are allowed from these registers (from
BIOS/OSPM perspective). "memslot id add" will immediately populate the ne
Hotplugged memory is not persistent in the e820 memory maps. After hotplugging
a memslot and rebooting the VM, the hotplugged device is not present.
A possible solution is to add an e820 for the new memslot in the acpi_piix4
hot-add handler. On a reset, Seabios (see next patch in series) will
On a reboot, seabios regenerates srat/ssdt objects. If a valid e820 entry is
found spanning the whole address range of a hotplug memory device, the device
will be enabled. This ensures persistency of hotplugged memory slots across VM
reboots.
Signed-off-by: Vasilis Liaskovitis
---
src/acpi
Implement -memslot qemu-kvm command line option to define hotplug-able memory
slots.
Syntax: "-memslot id=name,start=addr,size=sz,node=nodeid"
e.g. "-memslot id=hot1,start=4294967296,size=1073741824,node=0"
will define a 1G memory slot starting at physical address 4G, belonging to numa
node
The numa_fw_cfg paravirt interface is extended to include SRAT information for
all hotplug-able memslots. There are 3 words for each hotplug-able memory slot,
denoting start address, size and node proximity. nb_numa_nodes is set to 1 by
default (not 0), so that we always pass srat info to SeaBI
Extend the DSDT to include methods for handling memory hot-add and hot-remove
notifications and memory device status requests. These functions are called
from the memory device SSDT methods.
Eject has only been tested with level gpe event, but will be changed to edge gpe
event soon, according to r
On Thu, 2012-04-19 at 14:59 +0530, Prem Karat wrote:
> Folks,
>
> This is a test report on upstream qemu-kvm testing (24853eece248d4a58d705c).
> Tests were executed using latest autotest git (6a15572d5307fa0b).
>
> This time we have tested 3 guests.
>
> We are analysing the test results further
On 04/19/2012 05:08 PM, Vasilis Liaskovitis wrote:
> The numa_fw_cfg paravirt interface is extended to include SRAT information
> for
> all hotplug-able memslots. There are 3 words for each hotplug-able memory
> slot,
> denoting start address, size and node proximity. nb_numa_nodes is set to 1
On 04/19/2012 05:08 PM, Vasilis Liaskovitis wrote:
> Implement -memslot qemu-kvm command line option to define hotplug-able memory
> slots.
> Syntax: "-memslot id=name,start=addr,size=sz,node=nodeid"
>
> e.g. "-memslot id=hot1,start=4294967296,size=1073741824,node=0"
> will define a 1G memory
On 04/19/2012 09:08 AM, Vasilis Liaskovitis wrote:
This is a prototype for ACPI memory hotplug on x86_64 target. Based on some
earlier work and comments from Gleb.
Memslot devices are modeled with a new qemu command line
"-memslot id=name,start=start_addr,size=sz,node=pxm"
Hi,
For 1.2, I'd r
On 04/19/12 10:50pm, Amos Kong wrote:
> On Thu, Apr 19, 2012 at 10:13 PM, Lucas Meneghel Rodrigues
> wrote:
>
> > On Thu, 2012-04-19 at 14:59 +0530, Prem Karat wrote:
> > > Folks,
> > >
> > > This is a test report on upstream qemu-kvm testing
> > (24853eece248d4a58d705c).
> > > Tests were executed
Signed-off-by: Jiří Župka
---
client/tests/kvm/multi_host.srv | 22 ++
1 files changed, 14 insertions(+), 8 deletions(-)
diff --git a/client/tests/kvm/multi_host.srv b/client/tests/kvm/multi_host.srv
index 5aafeda..e54325f 100644
--- a/client/tests/kvm/multi_host.srv
+++ b/
Migration over fd:
source:
1) Make new descriptor (pipe, socket) and send the descriptor
to qemu-monitor over unix socket.
2) Register the descriptor in qemu-monitor with function
getfd DSC_NAME
and close the descriptor in main process.
3) Migrate over descript
Test create socket get descriptor from socket and migrate through
the descriptor.
This test allow migration only of one machine at once.
Signed-off-by: Jiří Župka
---
client/tests/kvm/tests/migration_multi_host_fd.py | 124 +
client/virt/virt_utils.py
This patchset simplifies the freeing by RCU of mmu pages.
Xiao, I'm sure you thought of always freeing by RCU. Why didn't you choose
this way? I saves a couple of atomics in the fast path.
Avi Kivity (2):
KVM: MMU: Always free shadow pages using RCU
KVM: MMU: Recover space used by rcu_head
The non-RCU path costs us two atomic operations, as well as extra
code complexity.
Signed-off-by: Avi Kivity
---
arch/x86/include/asm/kvm_host.h |2 --
arch/x86/kvm/mmu.c | 46 ---
2 files changed, 9 insertions(+), 39 deletions(-)
diff --gi
By overlaying the field with 'link', we reduce the structure size by
16 bytes.
Changing call_rcu() to be per-page is not strictly necessary, but it
can help RCU estimate the amount of work pending.
Signed-off-by: Avi Kivity
---
arch/x86/include/asm/kvm_host.h |7 ---
arch/x86/kvm/mmu.c
Signed-off-by: Jiří Župka
---
client/tests/kvm/multi_host.srv | 22 ++
1 files changed, 14 insertions(+), 8 deletions(-)
diff --git a/client/tests/kvm/multi_host.srv b/client/tests/kvm/multi_host.srv
index 5aafeda..e54325f 100644
--- a/client/tests/kvm/multi_host.srv
+++ b/
Test create socket get descriptor from socket and migrate through
the descriptor.
This test allow migration only of one machine at once.
Signed-off-by: Jiří Župka
---
client/tests/kvm/tests/migration_multi_host_fd.py | 124 +
client/virt/virt_utils.py
Migration over fd:
source:
1) Make new descriptor (pipe, socket) and send the descriptor
to qemu-monitor over unix socket.
2) Register the descriptor in qemu-monitor with function
getfd DSC_NAME
and close the descriptor in main process.
3) Migrate over descript
Hi Stuart,
I have been doing some experiments, and I noticed that there are
additional QEMU threads, besides the ones reported by "info cpus"
command. In particular, the main QEMU thread (the one whose LWP is the
same as its PID), also consumes significant CPU time. Is this
expected?
Alex.
On We
Applied, thanks!
On Thu, Apr 19, 2012 at 1:27 PM, Jiří Župka wrote:
> This patch series adds
> 1) support for migration over fd.
> 2) Add multihost migration test over fd.
>
> pull-request: https://github.com/autotest/autotest/pull/312
>
> ___
> Autotes
Hi,
On Thu, Apr 19, 2012 at 09:49:31AM -0500, Anthony Liguori wrote:
> On 04/19/2012 09:08 AM, Vasilis Liaskovitis wrote:
> >This is a prototype for ACPI memory hotplug on x86_64 target. Based on some
> >earlier work and comments from Gleb.
> >
> >Memslot devices are modeled with a new qemu comman
Hi,
On Thu, Apr 19, 2012 at 05:22:52PM +0300, Avi Kivity wrote:
> On 04/19/2012 05:08 PM, Vasilis Liaskovitis wrote:
> > Implement -memslot qemu-kvm command line option to define hotplug-able
> > memory
> > slots.
> > Syntax: "-memslot id=name,start=addr,size=sz,node=nodeid"
> >
> > e.g. "-me
Jan/Avi: ping?
I would like to get this ABI detail clarified so it can be implemented
the right way on Qemu and KVM.
My proposal is to simply add tsc-deadline to the data returned by
GET_SUPPORTED_CPUID, making KVM_CAP_TSC_DEADLINE_TIMER unnecessary.
On Fri, Mar 23, 2012 at 02:17:52PM +, Li
From: Jeremy Fitzhardinge
This series replaces the existing paravirtualized spinlock mechanism
with a paravirtualized ticketlock mechanism. (targeted for 3.5 window)
Changes in V7:
- Reabsed patches to 3.4-rc3
- Added jumplabel split patch (originally from Andrew Jones rebased to
3.4-rc3
From: Jeremy Fitzhardinge
Rather than outright replacing the entire spinlock implementation in
order to paravirtualize it, keep the ticket lock implementation but add
a couple of pvops hooks on the slow patch (long spin on lock, unlocking
a contended lock).
Ticket locks have a number of nice pro
From: Raghavendra K T
The code size expands somewhat, and its better to just call
a function rather than inline it.
Thanks Jeremy for original version of ARCH_NOINLINE_SPIN_UNLOCK config patch,
which is simplified.
Suggested-by: Linus Torvalds
Signed-off-by: Raghavendra K T
---
arch/x86/Kc
From: Jeremy Fitzhardinge
Now that the paravirtualization layer doesn't exist at the spinlock
level any more, we can collapse the __ticket_ functions into the arch_
functions.
Signed-off-by: Jeremy Fitzhardinge
Tested-by: Attilio Rao
Signed-off-by: Raghavendra K T
---
arch/x86/include/asm/s
From: Jeremy Fitzhardinge
There's no need to do it at very early init, and doing it there
makes it impossible to use the jump_label machinery.
Signed-off-by: Jeremy Fitzhardinge
Reviewed-by: Konrad Rzeszutek Wilk
Signed-off-by: Raghavendra K T
---
arch/x86/xen/smp.c |2 +-
1 files change
From: Jeremy Fitzhardinge
Replace the old Xen implementation of PV spinlocks with and implementation
of xen_lock_spinning and xen_unlock_kick.
xen_lock_spinning simply registers the cpu in its entry in lock_waiting,
adds itself to the waiting_cpus set, and blocks on an event channel
until the ch
From: Jeremy Fitzhardinge
Signed-off-by: Jeremy Fitzhardinge
Reviewed-by: Konrad Rzeszutek Wilk
Signed-off-by: Raghavendra K T
---
arch/x86/xen/spinlock.c | 14 ++
1 files changed, 14 insertions(+), 0 deletions(-)
diff --git a/arch/x86/xen/spinlock.c b/arch/x86/xen/spinlock.c
in
From: Jeremy Fitzhardinge
Although the lock_spinning calls in the spinlock code are on the
uncommon path, their presence can cause the compiler to generate many
more register save/restores in the function pre/postamble, which is in
the fast path. To avoid this, convert it to using the pvops call
From: Jeremy Fitzhardinge
Increment ticket head/tails by 2 rather than 1 to leave the LSB free
to store a "is in slowpath state" bit. This halves the number
of possible CPUs for a given ticket size, but this shouldn't matter
in practice - kernels built for 32k+ CPU systems are probably
specially
From: Jeremy Fitzhardinge
Maintain a flag in the LSB of the ticket lock tail which indicates
whether anyone is in the lock slowpath and may need kicking when
the current holder unlocks. The flags are set when the first locker
enters the slowpath, and cleared when unlocking to an empty queue (ie,
From: Jeremy Fitzhardinge
If interrupts were enabled when taking the spinlock, we can leave them
enabled while blocking to get the lock.
If we can enable interrupts while waiting for the lock to become
available, and we take an interrupt before entering the poll,
and the handler takes a spinlock
From: Stefano Stabellini
Signed-off-by: Jeremy Fitzhardinge
Reviewed-by: Konrad Rzeszutek Wilk
Signed-off-by: Raghavendra K T
---
arch/x86/xen/smp.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/arch/x86/xen/smp.c b/arch/x86/xen/smp.c
index 9ac931b..2192f76 100644
--
From: Andrew Jones
Commit b202952075f62603bea9bfb6ebc6b0420db11949 introduced rate limiting
for jump label disabling. The changes were made in the jump label code
in order to be more widely available and to keep things tidier. This is
all fine, except now jump_label.h includes linux/workqueue.h,
Hi Yuan,
Can you point me to the latest revision of the code and provide some
guidance on how to test it? I really would love to see if it helps.
Best,
-Mike
- Original Message -
From: "Liu Yuan"
To: "Michael Baysek"
Cc: "Stefan Hajnoczi" , kvm@vger.kernel.org
Sent: Thursday, April
On Wed, Apr 18, 2012 at 07:22:47PM +0300, Avi Kivity wrote:
> MMIO that are split across a page boundary are currently broken - the
> code does not expect to be aborted by the exit to userspace for the
> first MMIO fragment.
>
> This patch fixes the problem by generalizing the current code for han
On Wed, Apr 18, 2012 at 07:23:50PM +0300, Avi Kivity wrote:
> s/kcm/kvm/.
>
> Signed-off-by: Avi Kivity
> ---
> arch/ia64/kvm/kvm-ia64.c |2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Applied, thanks.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of
On 04/20/2012 12:26 AM, Avi Kivity wrote:
> This patchset simplifies the freeing by RCU of mmu pages.
>
> Xiao, I'm sure you thought of always freeing by RCU. Why didn't you choose
> this way? I saves a couple of atomics in the fast path.
>
Avi, we have discussed it last year:
https://lkml.
On 04/20/2012 04:26 AM, Michael Baysek wrote:
> Can you point me to the latest revision of the code and provide some
> guidance on how to test it? I really would love to see if it helps.
There is no latest revision, I didn't continue the development when I
saw the sign that it wouldn't be acce
75 matches
Mail list logo
