Bugs item #1886769, was opened at 2008-02-05 08:13
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=1886769&group_id=180599
Please note that this message will contain a full copy
Bugs item #1886768, was opened at 2008-02-05 08:07
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=1886768&group_id=180599
Please note that this message will contain a full copy
# HG changeset patch
# User Hollis Blanchard <[EMAIL PROTECTED]>
# Date 1202189664 21600
# Node ID bede9476e203f5bf59d21cc3cd71a30de2ce2c44
# Parent dfb0e1d58b57dfdf76b3111565815599bd38b92d
Signed-off-by: Hollis Blanchard <[EMAIL PROTECTED]>
---
4 files changed, 9 insertions(+), 7 deletions(-)
a
On Tue, 5 Feb 2008, Andrea Arcangeli wrote:
> On Mon, Feb 04, 2008 at 11:09:01AM -0800, Christoph Lameter wrote:
> > On Sun, 3 Feb 2008, Andrea Arcangeli wrote:
> >
> > > > Right but that pin requires taking a refcount which we cannot do.
> > >
> > > GRU can use my patch without the pin. XPMEM o
# HG changeset patch
# User Hollis Blanchard <[EMAIL PROTECTED]>
# Date 1202189668 21600
# Node ID e6e0239e8df55c6af4e0b2959350215aaa119254
# Parent 7dd50dab9096c8e0125792e3f48083c3f47fceab
The ioctl accepts a core name as input and calls kvm_vm_ioctl_create_vcpu()
with the corresponding "guest op
These patches allow PowerPC to create vcpus of a particular type. Since we are
actually emulating the core's supervisor mode, we can choose to emulate any
type of core. However, since the core chosen will change the size of the vcpu
structure (among other things), we need to know it at vcpu creatio
# HG changeset patch
# User Hollis Blanchard <[EMAIL PROTECTED]>
# Date 1202189666 21600
# Node ID 7dd50dab9096c8e0125792e3f48083c3f47fceab
# Parent bede9476e203f5bf59d21cc3cd71a30de2ce2c44
Signed-off-by: Hollis Blanchard <[EMAIL PROTECTED]>
---
2 files changed, 3 insertions(+), 1 deletion(-)
in
On Mon, Feb 04, 2008 at 11:09:01AM -0800, Christoph Lameter wrote:
> On Sun, 3 Feb 2008, Andrea Arcangeli wrote:
>
> > > Right but that pin requires taking a refcount which we cannot do.
> >
> > GRU can use my patch without the pin. XPMEM obviously can't use my
> > patch as my invalidate_page[s]
Hi!
I just tried out KVM for the first time, and most things work amazingly
well!
However I experience strange problems with the networking. I am using
kvm command like this:
kvm -hda hda.cow -m 512 -smp 1 -k fi -net
nic,model=ne2k_pci,macaddr=52:54:01:00:00:02 -net tap
I have set up a brid
On Fri, 2008-02-01 at 17:34 +0800, Zhang, Xiantao wrote:
> From: Xiantao Zhang <[EMAIL PROTECTED]>
> Date: Fri, 1 Feb 2008 17:18:03 +0800
> Subject: [PATCH] Make non-x86 arch partially support make sync.
>
> Make non-x86 arch partially support make sync, and other archs
> can get right header file
Hello,
The merge with upstream changeset: af5ca3f4ec5cc4432a42a73b050dd8898ce8fd00
broke building an external module against 2.6.23:
CC [M] /root/kvm-userspace/kernel/kvm_main.o
/root/kvm-userspace/kernel/kvm_main.c:1271: error: unknown field ‘name’
specified in initializer
Which makes se
On Sun, 3 Feb 2008, Andrea Arcangeli wrote:
> On Thu, Jan 31, 2008 at 07:58:40PM -0800, Christoph Lameter wrote:
> > Ok. Andrea wanted the same because then he can void the begin callouts.
>
> Exactly. I hope the page-pin will avoid me having to serialize the KVM
> page fault against the start/en
On Sun, 3 Feb 2008, Andrea Arcangeli wrote:
> > Right but that pin requires taking a refcount which we cannot do.
>
> GRU can use my patch without the pin. XPMEM obviously can't use my
> patch as my invalidate_page[s] are under the PT lock (a feature to fit
> GRU/KVM in the simplest way), this is
On Mon, 2008-02-04 at 09:33 -0600, Anthony Liguori wrote:
> Izik Eidus wrote:
> > On Mon, 2008-02-04 at 09:11 -0600, Anthony Liguori wrote:
> >
> >> KVM supports more than 2GB of memory for x86_64 hosts. The following patch
> >> fixes a number of type related issues where int's were being used
Izik Eidus wrote:
> On Mon, 2008-02-04 at 09:11 -0600, Anthony Liguori wrote:
>
>> KVM supports more than 2GB of memory for x86_64 hosts. The following patch
>> fixes a number of type related issues where int's were being used when they
>> shouldn't have been. It also introduces CMOS support s
Izik Eidus wrote:
>> Do you recall what this change fixed? As Paul pointed out in IRC, using
>> the host type here doesn't really fix the problem (target_ulong would be
>> more appropriate). However, we're both curious what problem it's
>> actually fixing since sign extending the int should ju
Anthony Liguori wrote:
KVM supports more than 2GB of memory for x86_64 hosts. The following patch
fixes a number of type related issues where int's were being used when they
shouldn't have been. It also introduces CMOS support so the BIOS can build
the appropriate e820 tables.
For v2 of this p
On Mon, 2008-02-04 at 09:11 -0600, Anthony Liguori wrote:
> KVM supports more than 2GB of memory for x86_64 hosts. The following patch
> fixes a number of type related issues where int's were being used when they
> shouldn't have been. It also introduces CMOS support so the BIOS can build
> the
Hi Soren,
Soren Hansen wrote:
> These need to move into VGA_STATE_COMMON instead. Otherwise vmware_vga
> will get confoozled becuase it relies on vga.c for its vesa
> implementation. The patch is at:
>
>
> http://people.ubuntu.com/~soren/0001-Move-common-VGAState-attributes-to-VGA_STATE_COM
The -daemonize option is too restrictive when using with SDL. It also switches
the working directory to / too early which causes block devices with a relative
path to fail.
The -daemonize option is needed for my regression testing so I've included this
patch in the series.
This patch hasn't chan
Previously, the BIOS would probe the CPUs for SMP guests. This tends to be
very unreliably because of startup timing issues. By passing the number of
CPUs in the CMOS, the BIOS can detect the number of CPUs much more reliably.
Since v1, I've incorporated Fabrice's feedback so this is now a 1-lin
KVM supports more than 2GB of memory for x86_64 hosts. The following patch
fixes a number of type related issues where int's were being used when they
shouldn't have been. It also introduces CMOS support so the BIOS can build
the appropriate e820 tables.
For v2 of this patch, I've moved ram_addr
KVM supports the ability to use ACPI to shutdown guests. In order to enable
this requires some fixes to be able to generate the SCI interrupt and the
appropriate plumbing.
This patch hasn't changed since v1.
diff --git a/hw/acpi.c b/hw/acpi.c
index 2669e4e..e21ded0 100644
--- a/hw/acpi.c
+++ b/h
KVM is a Linux interface for providing userspace interfaces for accelerated
virtualization. It has been included since 2.6.20 and supports Intel VT and
AMD-V. Ports are under way for ia64, embedded PowerPC, and s390.
This set of patches provide basic support for KVM in QEMU. It does not include
On Fri, Feb 01, 2008 at 04:12:01PM -0600, Anthony Liguori wrote:
> Index: qemu/hw/vga_int.h
> ===
> --- qemu.orig/hw/vga_int.h2008-02-01 15:23:45.0 -0600
> +++ qemu/hw/vga_int.h 2008-02-01 15:29:04.0 -0600
> @@ -145
On Sun, 2008-02-03 at 23:45 +0100, Andrea Arcangeli wrote:
> Hello,
>
> there's a small glitch in the preempt notifier external module
> emulation. The overloaded debug handler will not detect when a debug
> exception has been generated by ptrace and it'll crash the host by
> calling the preempt
On Friday 01 February 2008 19:05:00 Christian Borntraeger wrote:
> Am Freitag, 1. Februar 2008 schrieb Christian Borntraeger:
> > Right. I will fix that with an additional patch.
>
> This patch goes on top of the minor number patch. Please let me know if
> you want a merged patch:
>
> Currently vir
On Sun, 2008-02-03 at 19:56 -0600, Anthony Liguori wrote:
> Hi Izik,
Hi
>
> Anthony Liguori wrote:
> > Index: qemu/cpu-all.h
> > ===
> > --- qemu.orig/cpu-all.h 2008-02-01 15:24:45.0 -0600
> > +++ qemu/cpu-all.h 2008-0
28 matches
Mail list logo
