Bugs item #1958467, was opened at 2008-05-06 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=1958467&group_id=180599
Please note that this message will contain a full copy
Bugs item #1958464, was opened at 2008-05-06 14:34
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=1958464&group_id=180599
Please note that this message will contain a full copy
With today's tip, I cannot insert PAE KVM modules.
Lots of unknown symbols have been reported while inserting kvm.ko.
error inserting '/usr/kvm/kvm.ko': -1 Unknown symbol in module
dmesg:
kvm_intel: Unknown symbol kvm_set_cr4
kvm_intel: Unknown symbol kvm_set_cr0
kvm_intel: Unknown symbol kvm_
On May 4, 2008, at 9:56 AM, Avi Kivity wrote:
> Marcelo Tosatti wrote:
>> Add three PCI bridges to support 128 slots.
>>
>> Changes since v1:
>> - Remove I/O address range "support" (so standard PCI I/O space is
>> used).
>> - Verify that there's no special quirks for 82801 PCI bridge.
>> - Int
Avi Kivity wrote:
> Marcelo Tosatti wrote:
>
>> Add three PCI bridges to support 128 slots.
>>
>> Changes since v1:
>> - Remove I/O address range "support" (so standard PCI I/O space is used).
>> - Verify that there's no special quirks for 82801 PCI bridge.
>> - Introduce separate flat IRQ mappi
On May 4, 2008, at 9:56 AM, Avi Kivity wrote:
> Marcelo Tosatti wrote:
>> Add three PCI bridges to support 128 slots.
>>
>> Changes since v1:
>> - Remove I/O address range "support" (so standard PCI I/O space is
>> used).
>> - Verify that there's no special quirks for 82801 PCI bridge.
>> - Int
Intel-iommu driver changes for kvm vt-d support. Important changes are
in intel-iommu.c. The rest of the changes are for moving intel-iommu.h
and iova.h from drivers/pci directory to include/linux directory.
Signed-off-by: Allen M Kay <[EMAIL PROTECTED]>
b/drivers/pci/dmar.c |
Kvm-user-mode patch. Still todo: move vt.d to kvm-intel.ko module.
Signed-off-by: Allen M Kay <[EMAIL PROTECTED]>
-
Kbuild |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
-
diff --git a/kernel/Kbuild b/kernel/Kbuild
index e3e97ab..7455605 100644
--- a/kernel/Kbuild
+++ b/ker
Kvm kernel changes.
Signed-off-by: Allen M Kay <[EMAIL PROTECTED]>
--
arch/x86/kvm/Makefile |2
arch/x86/kvm/vtd.c | 183
+
arch/x86/kvm/x86.c |7 +
include/asm-x86/kvm_host.h |3
include/asm-x86/kvm_para.h |
Following three patches contains vt-d support for pci passthrough. It
contains diff's base on Amit's 4/22 passthrough tree.
The hardware environment used for this work is an Intel Weybridge system
(Q35). The passthrough device is an E1000 NIC. I'm still using irqhook
mechanism for interrupt inje
On Mon, May 05, 2008 at 08:34:05PM +0200, Andrea Arcangeli wrote:
> On Mon, May 05, 2008 at 12:25:06PM -0500, Jack Steiner wrote:
> > Agree. My apologies... I should have caught it.
>
> No problem.
>
> > __mmu_notifier_register/__mmu_notifier_unregister seems like a better way to
> > go, although
On Mon, May 05, 2008 at 12:25:06PM -0500, Jack Steiner wrote:
> Agree. My apologies... I should have caught it.
No problem.
> __mmu_notifier_register/__mmu_notifier_unregister seems like a better way to
> go, although either is ok.
If you also like __mmu_notifier_register more I'll go with it. T
On Monday 05 May 2008 11:04:52 Jerone Young wrote:
> These patches fell through the cracks.
>
> This set of patches fixes setting memory for PowerPC bamboo board model.
Besides just setting memory in qemu, you must also set it in the device tree.
This sets the memory in the device tree so that i
On Mon, May 05, 2008 at 07:14:34PM +0200, Andrea Arcangeli wrote:
> On Mon, May 05, 2008 at 11:21:13AM -0500, Jack Steiner wrote:
> > The GRU does the registration/deregistration of mmu notifiers from
> > mmap/munmap.
> > At this point, the mmap_sem is already held writeable. I hit a deadlock
> >
On Mon, May 05, 2008 at 11:21:13AM -0500, Jack Steiner wrote:
> The GRU does the registration/deregistration of mmu notifiers from
> mmap/munmap.
> At this point, the mmap_sem is already held writeable. I hit a deadlock
> in mm_lock.
It'd been better to know about this detail earlier, but frankly
Attached is a patch that fixes a guest crash when booting older Linux kernels.
The problem stems from the fact that we are currently emulating
MSR_K7_EVNTSEL[0-3], but not emulating MSR_K7_PERFCTR[0-3]. Because of this,
setup_k7_watchdog() in the Linux kernel receives a GPF when it attempts to wri
On Fri, May 02, 2008 at 05:05:04PM +0200, Andrea Arcangeli wrote:
> # HG changeset patch
> # User Andrea Arcangeli <[EMAIL PROTECTED]>
> # Date 1209740175 -7200
> # Node ID 1489529e7b53d3f2dab8431372aa4850ec821caa
> # Parent 5026689a3bc323a26d33ad882c34c4c9c9a3ecd8
> mmu-notifier-core
I upgrad
# HG changeset patch
# User Jerone Young <[EMAIL PROTECTED]>
# Date 1210003411 18000
# Branch merge
# Node ID c455452c9b217abed8a2e6147bbeb91f33ff1799
# Parent cf3ccc3add69052aade695c746151b1cb8812252
Fix memory defined in device tree by declaring it dynamically for bamboo board
model
This fixes
# HG changeset patch
# User Jerone Young <[EMAIL PROTECTED]>
# Date 1210003408 18000
# Branch merge
# Node ID cf3ccc3add69052aade695c746151b1cb8812252
# Parent 97e439fdd4e91c3fb1ef9055f073add55084d69f
Add function dt_cell_multi to hw/device_tree.c
This patch adds function dt_cell_multi to allow f
These patches fell through the cracks.
This set of patches fixes setting memory for PowerPC bamboo board model.
Besides just setting memory in qemu, you must also set it in the device tree.
This sets the memory in the device tree so that it can be something other then
the hard coded memory size
On Mon, May 05, 2008 at 09:47:59AM +0200, Gerd Hoffmann wrote:
> Marcelo Tosatti wrote:
> > On Thu, Apr 24, 2008 at 10:37:04AM +0200, Gerd Hoffmann wrote:
> >> Hi folks,
> >>
> >> My first attempt to send out a patch series with git ...
> >>
> >> The patches fix the kvm paravirt clocksource code
Daniel P. Berrange wrote:
> I'm forwarding this patch from upstream QEMU because its impotant to get
> this fixed in KVM to make serial console installs usable now libvirt can
> talk to KVM serial ports over PTYs.
>
> It was reported in this thread:
>
> http://lists.gnu.org/archive/html/qemu-deve
Anthony Liguori wrote:
>>
>> Please break the SIGUSR1 changes into a separate patch. Ditto with
>> *fd syscall compat.
>
> Done. I didn't make the syscall compat stuff separate patches because
> that would break bisect on older hosts. However, I did split it up
> logically between the remove
It's a little odd to use signals to raise a notification on a file descriptor
when we can just work directly with a file descriptor instead. This patch
converts the SIGUSR1 based notification in the io-thread to instead use an
eventfd file descriptor. If eventfd isn't available, we use a pipe() i
The select() in the IO thread may wait a long time before rebuilding the
fd set. Whenever we do something that changes the fd set, we should interrupt
the IO thread.
Signed-off-by: Anthony Liguori <[EMAIL PROTECTED]>
diff --git a/qemu/vl.c b/qemu/vl.c
index 1192759..e9f0ca4 100644
--- a/qemu/vl.
This patch reworks the IO thread to use signalfd() instead of sigtimedwait().
This will eliminate the need to use SIGIO everywhere. In this version of the
patch, we use signalfd() when it's available. When it isn't available, we
create a separate thread and use sigwaitinfo() to simulate signalfd(
QEMU is rather aggressive about exhausting the wait period when selecting.
This is fine when the wait period is low and when there is significant delays
in-between selects as it improves IO throughput.
With the IO thread, there is a very small delay between selects and our wait
period for select i
On Mon, May 5, 2008 at 3:57 PM, Anthony Liguori <[EMAIL PROTECTED]> wrote:
> WinXP fails to boot with your patch applied too. FWIW, Ubuntu 8.04 has
> a fixed version of gfxboot that doesn't do nasty things with SS on
> privileged mode transitions.
>
WinXP fails with the patch applied too. Ubun
[EMAIL PROTECTED] wrote:
> I've added Heiko's patch to my patchqueue. But since this is
> drivers/s390/kvm this should go in over the kvm.git. See patch below.
Acked-by: Carsten Otte <[EMAIL PROTECTED]>
-
This SF.net email is
On Mon, 2008-05-05 at 16:00 +0300, Avi Kivity wrote:
> Christian Borntraeger wrote:
> >> Hmm... this should help:
> >>
> >> ---
> >> drivers/s390/kvm/kvm_virtio.c | 40
> >>
> > +++-
> >
> >> 1 file changed, 23 insertions(+), 17 deletions(-)
> >>
Christian Borntraeger wrote:
>> Hmm... this should help:
>>
>> ---
>> drivers/s390/kvm/kvm_virtio.c | 40
>>
> +++-
>
>> 1 file changed, 23 insertions(+), 17 deletions(-)
>>
>
> Thanks Heiko.
> I did a short test and it seems to work.
>
> Acked-b
Guillaume Thouvenin wrote:
> On Sat, 3 May 2008 13:56:56 +0530
> Balaji Rao <[EMAIL PROTECTED]> wrote:
>
>
>
>> With your patch applied ubuntu 8.04 livecd fails to boot. Not any better
>> with Marcelo's patch on top.
>>
>
> Hi Balaji,
>
> And without the patch, can you boot the ubuntu 8
On Monday 05 May 2008 06:10:08 pm Guillaume Thouvenin wrote:
> On Sat, 3 May 2008 13:56:56 +0530
>
> Balaji Rao <[EMAIL PROTECTED]> wrote:
> > With your patch applied ubuntu 8.04 livecd fails to boot. Not any better
> > with Marcelo's patch on top.
>
> Hi Balaji,
>
> And without the patch, can you
On Sat, 3 May 2008 13:56:56 +0530
Balaji Rao <[EMAIL PROTECTED]> wrote:
> With your patch applied ubuntu 8.04 livecd fails to boot. Not any better
> with Marcelo's patch on top.
Hi Balaji,
And without the patch, can you boot the ubuntu 8.04 livecd?
Regards,
Guillaume
-
> Hmm... this should help:
>
> ---
> drivers/s390/kvm/kvm_virtio.c | 40
+++-
> 1 file changed, 23 insertions(+), 17 deletions(-)
Thanks Heiko.
I did a short test and it seems to work.
Acked-by: Christian Borntraeger <[EMAIL PROTECTED]>
This looks almost
Avi Kivity wrote:
> Michal Ludvig wrote:
loaded kvm module (kvm-68)
kvm: emulating exchange as write
Unable to handle kernel NULL pointer dereference at
RIP:
[] :kvm:x86_emulate_insn+0x3fa/0x4240
>>>
>>> Please apply the attached patch, and post 'dme
Michal Ludvig wrote:
loaded kvm module (kvm-68)
kvm: emulating exchange as write
Unable to handle kernel NULL pointer dereference at
RIP:
[] :kvm:x86_emulate_insn+0x3fa/0x4240
Please apply the attached patch, and post 'dmesg | grep writeback'.
writeback: b 01 mordm e0
I'm forwarding this patch from upstream QEMU because its impotant to get
this fixed in KVM to make serial console installs usable now libvirt can
talk to KVM serial ports over PTYs.
It was reported in this thread:
http://lists.gnu.org/archive/html/qemu-devel/2008-05/msg00014.html
With the fina
Avi Kivity wrote:
> Michal Ludvig wrote:
>>
>> Hi again, just wanted to let you know that I still get this Oops with
>> kvm-68. It comes a bit later, not during the boot but after the XP
>> desktop comes up. As there were some changes in kernel/x86_emulate.c
>> the patch you provided for kvm-66
Marcelo Tosatti wrote:
> On Thu, Apr 24, 2008 at 10:37:04AM +0200, Gerd Hoffmann wrote:
>> Hi folks,
>>
>> My first attempt to send out a patch series with git ...
>>
>> The patches fix the kvm paravirt clocksource code to be compatible with
>> xen and they also factor out some code which can be
Anthony Liguori wrote:
> This patch reworks the IO thread to use signalfd() instead of sigtimedwait().
> This will eliminate the need to use SIGIO everywhere. In this version of the
> patch, we use signalfd() when it's available. When it isn't available, we
> create a separate thread and use sigw
Michal Ludvig wrote:
Hi again, just wanted to let you know that I still get this Oops with
kvm-68. It comes a bit later, not during the boot but after the XP
desktop comes up. As there were some changes in kernel/x86_emulate.c
the patch you provided for kvm-66 can't be applied anymore.
load
Avi Kivity wrote:
> Avi Kivity wrote:
>> Izik Eidus wrote:
>>> Michal Ludvig wrote:
>>>
Avi Kivity wrote:
> Avi Kivity wrote:
>
>> Michal Ludvig wrote:
>>
>>> Hi,
>>>
>>> I've experienced a kernel Oops on 2.6.24 with kvm 66 on AMD in
>>> 64
Avi Kivity wrote:
> Izik Eidus wrote:
>> Michal Ludvig wrote:
>>
>>> Avi Kivity wrote:
>>>
Avi Kivity wrote:
> Michal Ludvig wrote:
>
>> Hi,
>>
>> I've experienced a kernel Oops on 2.6.24 with kvm 66 on AMD in
>> 64bit mode while starting up Wi
Avi Kivity wrote:
> Izik Eidus wrote:
>> Michal Ludvig wrote:
>>
>>> Avi Kivity wrote:
>>>
Avi Kivity wrote:
> Michal Ludvig wrote:
>
>> Hi,
>>
>> I've experienced a kernel Oops on 2.6.24 with kvm 66 on AMD in
>> 64bit mode while starting up Win
Izik Eidus wrote:
> Michal Ludvig wrote:
>
>> Avi Kivity wrote:
>>
>>> Avi Kivity wrote:
>>>
Michal Ludvig wrote:
> Hi,
>
> I've experienced a kernel Oops on 2.6.24 with kvm 66 on AMD in 64bit
> mode while starting up WinXP:
>
> The host is
46 matches
Mail list logo
