On Tue, Feb 26, 2008 at 05:11:32PM +1100, Nick Piggin wrote:
> > You are missing one point here. The MPI specifications that have
> > been out there for decades do not require the process use a library
> > for allocating the buffer. I realize that is a horrible shortcoming,
> > but that is the wo
On Thursday 21 February 2008 21:58, Robin Holt wrote:
> On Thu, Feb 21, 2008 at 03:20:02PM +1100, Nick Piggin wrote:
> > > > So why can't you export a device from your xpmem driver, which
> > > > can be mmap()ed to give out "anonymous" memory pages to be used
> > > > for these communication buffers
Almost 7 hours and the uniprocessor case is still chugging along.
david
Avi Kivity wrote:
> david ahern wrote:
>> david ahern wrote:
>>
>>> Avi Kivity wrote:
>>>
- the in-kernel ioapic is buggy and needs the extra kicking the
optimization prevents. Can be checked by re-adding
>> I don't know if the patch was still needed now, since it was posted
>> long ago(I don't know which issue it solved). I'd like to post a
>> revert patch if necessary.
>>
>
> I believe the patch is still necessary, since we still need to
> guarantee that a vcpu's tsc is monotonous. I think the
On Mon, 2008-02-25 at 13:47 -0600, Anthony Liguori wrote:
> This patch adds support to QEMU for Rusty's recently introduce virtio balloon
> driver. The user-facing portions of this are the introduction of a "balloon"
> and "info balloon" command in the monitor.
>
The patch looks good. Might be
On Sun, Feb 24, 2008 at 04:40:09AM -0800, SourceForge.net wrote:
> Bugs item #1900829, was opened at 2008-02-24 14:40
> 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=1900829
On Wed, 20 Feb 2008 09:20:08 -0800 Randy Dunlap wrote:
> On Wed, 20 Feb 2008 16:07:03 +0200 Avi Kivity wrote:
>
> > > Looks like KVM conflicts with CONFIG_VOYAGER...
> > >
> >
> > Attached patch should fix.
> >
> > Subject: x86: disable KVM on Voyager
> >
> > Most classic Pentiums don't have h
hi,
the attached patch fixes some glitches when switching to fullscreen mode
using ctrl+alt+f or when booting using -full-screen.
up to now the VM simply dies if one of the following situations occur:
* user switches from windowed to fullscreen mode using a resolution
which is too high (mea
Hi,
Original bug was submitted at http://bugs.debian.org/467043. The summary
is that installs of Windows XP from pre-kvm-60 (pre-59?), then upgrading
to kvm-60 or 61 causes Windows to trigger activation due to "computer
changed too much". Downgrading to kvm-58 or previous resolves the issue.
Have
Kurt Neufeld burgundywall.com> writes:
>
> It turns out I did have everything correctly configured but it still
> doesn't work. The problem is that I cannot get a DHCP address on my vm.
Almost correctly.
> Some general questions, should br0 be up or down? What should my vm MAC
> be? The same
Alexander Graf wrote:
>
> On Feb 25, 2008, at 6:40 PM, Avi Kivity wrote:
>
>> Alexander Graf wrote:
>>>
>>> The ebx store was done because of PIC code, which does not allow ebx
>>> to get clobbered. If we are not in PIC code, =r contains ebx as GPR
>>> though, so the assumption that ebx needs to
On Wed, Feb 20, 2008 at 12:48:39PM +0200, Dan Aloni wrote:
> On Wed, Feb 20, 2008 at 11:09:44AM +0200, Avi Kivity wrote:
> > Dan Aloni wrote:
> > > It happens at 100% of the times I invoke kexec.
> > >
> > >
> >
> > Can you provide a commandline which triggers this? I'm completely
> > ignorant
I could have sworn that we had patches that made KVM
depend on !VOYAGER and !VISWS, but with 2.6.25-rc3 and linux-next,
it's possible to select VOYAGER machine type (x86_32) and then
enable KVM and watch the build fail.
ERROR: "smp_ops" [arch/x86/kvm/kvm.ko] undefined!
make[1]: *** [__modpost] Err
On Feb 25, 2008, at 6:40 PM, Avi Kivity wrote:
> Alexander Graf wrote:
>>
>> The ebx store was done because of PIC code, which does not allow
>> ebx to get clobbered. If we are not in PIC code, =r contains ebx as
>> GPR though, so the assumption that ebx needs to be restored was
>> wrong th
Avi Kivity wrote:
> Farkas Levente wrote:
>> Avi Kivity wrote:
>>
>>> Farkas Levente wrote:
>>>
will be a new release in the near future? since many of us waiting for
this bug to be fixed on quad and other multi core cpus.
>>> Certainly. Can you try out the attac
Farkas Levente wrote:
> Avi Kivity wrote:
>
>> Farkas Levente wrote:
>>
>>> will be a new release in the near future? since many of us waiting for
>>> this bug to be fixed on quad and other multi core cpus.
>>>
>>>
>>>
>> Certainly. Can you try out the attached patch?
>>
>
>
Avi Kivity wrote:
> Farkas Levente wrote:
>> will be a new release in the near future? since many of us waiting for
>> this bug to be fixed on quad and other multi core cpus.
>>
>>
>
> Certainly. Can you try out the attached patch?
thanks. it works!:-)))
we've been waiting for this in the las
Alexander Graf wrote:
>
> The ebx store was done because of PIC code, which does not allow ebx
> to get clobbered. If we are not in PIC code, =r contains ebx as GPR
> though, so the assumption that ebx needs to be restored was wrong
> then. This new version only enables the store/restore code if
Marcelo Tosatti wrote:
> Subject says it all.
>
Applied, thanks.
--
error compiling committee.c: too many arguments to function
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Stu
Zhang, Xiantao wrote:
> Updated one. Sorry for inconvenience.
>
Applied, thanks.
--
error compiling committee.c: too many arguments to function
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microso
So this is a new version of the same patch. It should be rather safe
now, as most cases are handled by gcc.
Signed-off-by: Alexander Graf <[EMAIL PROTECTED]>
diff --git a/qemu/qemu-kvm-x86.c b/qemu/qemu-kvm-x86.c
index 37354fb..3062d1b 100644
--- a/qemu/qemu-kvm-x86.c
+++ b/qemu/qemu-kvm-x86.c
@@
david ahern wrote:
> david ahern wrote:
>
>> Avi Kivity wrote:
>>
>>> - the in-kernel ioapic is buggy and needs the extra kicking the
>>> optimization prevents. Can be checked by re-adding the optimization to
>>> kvm_ioapic_set_irq() (keeping it removed in qemu). If it works, the
>>> prob
On Mon, 2008-02-25 at 17:34 +0800, Zhang, Xiantao wrote:
> From: Xiantao Zhang <[EMAIL PROTECTED]>
> Date: Mon, 25 Feb 2008 17:11:43 +0800
> Subject: [PATCH] kvm: Using kzalloc to avoid allocating kvm_regs from
> kernel stack.
>
> Since the size of struct kvm_regs maybe too big to allocate from ke
david ahern wrote:
> Avi Kivity wrote:
>> - the in-kernel ioapic is buggy and needs the extra kicking the
>> optimization prevents. Can be checked by re-adding the optimization to
>> kvm_ioapic_set_irq() (keeping it removed in qemu). If it works, the
>> problem is in userspace. If it fails, the
On Mon, 2008-02-25 at 10:38 -0600, Hollis Blanchard wrote:
> On Mon, 2008-02-25 at 17:34 +0800, Zhang, Xiantao wrote:
> > From: Xiantao Zhang <[EMAIL PROTECTED]>
> > Date: Mon, 25 Feb 2008 17:11:43 +0800
> > Subject: [PATCH] kvm: Using kzalloc to avoid allocating kvm_regs from
> > kernel stack.
> >
Avi Kivity wrote:
> david ahern wrote:
>> I've run a lot more tests:
>>
>>
>> - if I remove the "if (!change) return" optimization from pci_set_irq the
>> rtl8139 nic worked fine for 16+ hours. I'm not recommending this as a
>> fix, just
>> confirming that the problem goes away.
>>
>>
>
> Inter
Avi Kivity wrote:
> Glauber Costa wrote:
>>>
>>> There is now code in rombios32.c to do this. It needs to be
>>> removed. See acpi_build_processor_ssdt().
>>
>> Building the table by hand is trivial in the case where the processors
>> are just _listed_, and can be easily justified. This first p
Glauber Costa wrote:
>>
>> There is now code in rombios32.c to do this. It needs to be
>> removed. See acpi_build_processor_ssdt().
>
> Building the table by hand is trivial in the case where the processors
> are just _listed_, and can be easily justified. This first patch just
> add the _STA
Avi Kivity wrote:
> Glauber Costa wrote:
>> mark processors as present through the _STA method
>>
>> Signed-off-by: Glauber Costa <[EMAIL PROTECTED]>
>> ---
>> bios/acpi-dsdt.dsl | 19 +++
>> 1 files changed, 19 insertions(+), 0 deletions(-)
>>
>> diff --git a/bios/acpi-dsdt.dsl
Subject says it all.
Signed-off-by: Marcelo Tosatti <[EMAIL PROTECTED]>
diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
index e1aa6c9..ff7ef12 100644
--- a/arch/x86/kvm/x86.c
+++ b/arch/x86/kvm/x86.c
@@ -595,8 +595,10 @@ int kvm_set_msr_common(struct kvm_vcpu *vcpu, u32 msr, u64
data)
On Feb 25, 2008, at 11:45 AM, Avi Kivity wrote:
Alexander Graf wrote:
On Feb 25, 2008, at 10:34 AM, Avi Kivity wrote:
Yang, Sheng wrote:
On Monday 25 February 2008 16:41:25 Zhao, Yunfeng wrote:
Hi, all,
This is today's KVM test result against kvm.git
81e4400b4df4e597a81c19c1161aa03c73613
you may try disable gfxboot by quickly
pressing Shift key when you start your guest OS. (very quickly)
On 2/23/08, Anthony Liguori <[EMAIL PROTECTED]> wrote:
>
> [EMAIL PROTECTED] wrote:
>
> > I looked for a gz o bz archive. Is there a tarball with gfxboot
> > disable program (URL)?
>
>
> I'm not
Updated one. Sorry for inconvenience.
Xiantao
0001-kvm-Using-kzalloc-to-avoid-allocating-kvm_regs-from.patch
Description: 0001-kvm-Using-kzalloc-to-avoid-allocating-kvm_regs-from.patch
-
This SF.net email is sponsored by: Mic
Colin Paul Adams wrote:
>> "Avi" == Avi Kivity <[EMAIL PROTECTED]> writes:
>>
>
> Avi> Colin Paul Adams wrote:
> >> This isn't mentioned on the guest status page.
> >>
> >> I went ahead and tried it anyway (32-bit). It works fine if I
> >> don't specify -sm
Alexander Graf wrote:
>
> On Feb 25, 2008, at 10:34 AM, Avi Kivity wrote:
>
>> Yang, Sheng wrote:
>>> On Monday 25 February 2008 16:41:25 Zhao, Yunfeng wrote:
>>>
Hi, all,
This is today's KVM test result against kvm.git
81e4400b4df4e597a81c19c1161aa03c73613710 and kvm-userspace.
On Feb 25, 2008, at 10:34 AM, Avi Kivity wrote:
Yang, Sheng wrote:
On Monday 25 February 2008 16:41:25 Zhao, Yunfeng wrote:
Hi, all,
This is today's KVM test result against kvm.git
81e4400b4df4e597a81c19c1161aa03c73613710 and kvm-userspace.git
08385e49dcff3585f597870af67301d7659a1ecb.
One
Please use the new one. Add the check for failed allocation.
From: Xiantao Zhang <[EMAIL PROTECTED]>
Date: Mon, 25 Feb 2008 17:25:07 +0800
Subject: [PATCH] kvm: Using kzalloc to avoid allocating kvm_regs from
kernel stack.
Since the size of kvm_regs maybe too big to allocate from kernel stack,
h
From: Xiantao Zhang <[EMAIL PROTECTED]>
Date: Mon, 25 Feb 2008 17:11:43 +0800
Subject: [PATCH] kvm: Using kzalloc to avoid allocating kvm_regs from
kernel stack.
Since the size of struct kvm_regs maybe too big to allocate from kernel
stack,
here use kzalloc to allocate it.
Signed-off-by: Xiantao Z
Yang, Sheng wrote:
> On Monday 25 February 2008 16:41:25 Zhao, Yunfeng wrote:
>
>> Hi, all,
>>
>> This is today's KVM test result against kvm.git
>> 81e4400b4df4e597a81c19c1161aa03c73613710 and kvm-userspace.git
>> 08385e49dcff3585f597870af67301d7659a1ecb.
>>
>> One new issue has been found in t
On Monday 25 February 2008 16:41:25 Zhao, Yunfeng wrote:
> Hi, all,
>
> This is today's KVM test result against kvm.git
> 81e4400b4df4e597a81c19c1161aa03c73613710 and kvm-userspace.git
> 08385e49dcff3585f597870af67301d7659a1ecb.
>
> One new issue has been found in today's testing:
> 1. fc5/fc6/rhel
Hey,
this patch works like a charm! No pointer trails, no bars through
dialogs... Perfect quality. Thanks alot Andreas!
Arne
On Fr, 2008-02-22 at 21:36 +0100, Andreas Winkelbauer wrote:
> hi,
>
> the attached patch fixes the screen corruption issues which were
> reported by others, see:
>
> h
Jerone Young wrote:
> The top level directory of kvm-userspace is starting to get a little
> crowded as we start to bring in more external dependencies. Perhaps we
> can create a folder "tools" and move directories:
> bios
> extboot
> vgabios
>
> The reason I mention this is soon I will be sending
david ahern wrote:
> I've run a lot more tests:
>
>
> - if I remove the "if (!change) return" optimization from pci_set_irq the
> rtl8139 nic worked fine for 16+ hours. I'm not recommending this as a fix,
> just
> confirming that the problem goes away.
>
>
Interesting. What can cause this to
Hi, all,
This is today's KVM test result against kvm.git
81e4400b4df4e597a81c19c1161aa03c73613710 and kvm-userspace.git
08385e49dcff3585f597870af67301d7659a1ecb.
One new issue has been found in today's testing:
1. fc5/fc6/rhel5u1 no-acpi up guests can't boot on pae host
https://sourceforge.net/
Bugs item #1901208, was opened at 2008-02-25 16:31
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=1901208&group_id=180599
Please note that this message will contain a full copy
45 matches
Mail list logo
