On 4/19/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
> Linus,
>
> Please pull from the 'linus' branch of
>
> git://git.kernel.org/pub/scm/linux/kernel/git/avi/kvm.git
>
> To get a one-liner fixing a host oops running non-pae guests.
>
> Avi Kivity (1):
> KVM: Fix off-by-one when writing to a
Signed-off-by: Gregory Haskins <[EMAIL PROTECTED]>
---
drivers/kvm/Makefile |2
drivers/kvm/kernint.c | 168 +
drivers/kvm/kvm.h | 14
drivers/kvm/kvm_main.c | 142 +
drivers/kvm/lapic.c| 1472
include/linux/kvm.h|
Adds an abstraction to the LAPIC logic so that we can later substitute it
for an in-kernel model.
Signed-off-by: Gregory Haskins <[EMAIL PROTECTED]>
---
drivers/kvm/kvm.h |4 +-
drivers/kvm/kvm_main.c | 19
drivers/kvm/lapic.h| 76 ++
drivers
The VCPU executes synchronously w.r.t. userspace today, and therefore
interrupt injection is pretty straight forward. However, we will soon need
to be able to inject interrupts asynchronous to the execution of the VCPU
due to the introduction of SMP, paravirtualized drivers, and asynchronous
hype
The current code is geared towards using a user-mode (A)PIC. This patch adds
an "irqdevice" abstraction, and implements a "userint" model to handle the
duties of the original code. Later, we can develop other irqdevice models
to handle objects like LAPIC, IOAPIC, i8259, etc, as appropriate
Sign
From: None
---
drivers/kvm/kvm.h | 31 ++
drivers/kvm/kvm_main.c | 82 +---
2 files changed, 101 insertions(+), 12 deletions(-)
diff --git a/drivers/kvm/kvm.h b/drivers/kvm/kvm.h
index fceeb84..181099f 100644
--- a/drivers/k
The following is my patch series for adding in-kernel APIC support. It
supports three "levels" of dynamic configuration (via a new ioctl):
* level 0 = (default) compatiblity mode (everything in userspace)
* level 1 = LAPIC in kernel, IOAPIC/i8259 in userspace
* level 2 = All three in kernel
On Thu, 19 Apr 2007, Linus Torvalds wrote:
>
> You can either do
>
> git reset --hard ORIG_HEAD
> git reset --hard @{1}
Btw, on the same kind of subject: the whole "what was my previous HEAD"
issues are obviously also how you'd generally want to see what those
new patches were, r
You are correct. The disk image(s) must be available to both the sending and
receiving qemu/kvm processes. Otherwise, we would have to copy (or rsync if a
base copy exists) the disk image. This copy operation would usually take a long
time as the image is very big.
Also, writing to temporary loc
The kvm migration wiki seems to imply (but not directly state) that the
disk image file must be on a shared filesystem for both the sending and
the receiving kvm/qemu processes.
Is this correct? And if so, what are the semantics that kvm/qemu
requires of the filesystem hosting the image? Is there
On Thu, 19 Apr 2007, Jeff Garzik wrote:
>
> What is the easiest way to completely undo a pull, reverting the branch to the
> HEAD present before the pull?
You can either do
git reset --hard ORIG_HEAD
(git will set ORIG_HEAD before things like pulls or resets, so you can
always go bac
On Thu, Apr 19, 2007 at 03:34:01PM -0400, Jeff Garzik wrote:
> David Brown wrote:
> >>What is the easiest way to completely undo a pull, reverting the branch
> >>to the HEAD present before the pull?
> >>
> >
> >If the pull doesn't merge successfully then usually doing a `git-reset
> >--hard` will b
David Brown wrote:
>> What is the easiest way to completely undo a pull, reverting the branch
>> to the HEAD present before the pull?
>>
>
> If the pull doesn't merge successfully then usually doing a `git-reset
> --hard` will blow everything away back to normal, but Linus may do
> different thing
> What is the easiest way to completely undo a pull, reverting the branch
> to the HEAD present before the pull?
>
If the pull doesn't merge successfully then usually doing a `git-reset
--hard` will blow everything away back to normal, but Linus may do
different things.
- David Brown
---
Linus Torvalds wrote:
>
> On Thu, 19 Apr 2007, Avi Kivity wrote:
>> Please pull from the 'linus' branch of
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/avi/kvm.git
>
> *please* put the branch-name after the git repo, so that I can
> cut-and-paste without noticing only afterwards that th
On Thu, 19 Apr 2007, Avi Kivity wrote:
>
> Please pull from the 'linus' branch of
>
> git://git.kernel.org/pub/scm/linux/kernel/git/avi/kvm.git
*please* put the branch-name after the git repo, so that I can
cut-and-paste without noticing only afterwards that the diffstat doesn't
match what
Linus,
Please pull from the 'linus' branch of
git://git.kernel.org/pub/scm/linux/kernel/git/avi/kvm.git
To get a one-liner fixing a host oops running non-pae guests.
Avi Kivity (1):
KVM: Fix off-by-one when writing to a nonpae guest pde
---
drivers/kvm/mmu.c |1 +
1 files change
Ed Schofield wrote:
>>
>> As it's a FAQ I added a page on the wiki:
>>
>> http://kvm.qumranet.com/kvmwiki/Intel_Real_Mode_Emulation_Problems
>>
>> if anyone has more specific instructions for various guests, please add
>> them there.
>
> Ah, I'd missed that. Thanks a lot!
>
It's new :)
--
err
On 4/19/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
> Ed Schofield wrote:
> >>
> >> This looks like our usual real-mode trouble. What guest are you
> >> running?
> >
> > Linux x86_64 (a Ubuntu Feisty prerelease boot CD from a few months
> > ago). I could try some other guests too if it would help.
>
Ed Schofield wrote:
>>
>> This looks like our usual real-mode trouble. What guest are you
>> running?
>
> Linux x86_64 (a Ubuntu Feisty prerelease boot CD from a few months
> ago). I could try some other guests too if it would help.
>
> Could you point to any links to useful info on this real-mod
On 4/19/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
> Ed Schofield wrote:
> > Hi all,
> >
> > I'm trying out kvm and running into problems reported as "exception
> > 12" and "exception 13" and segfaults. I'm using a HP Compaq dc7700p
> > system with an Intel Q965 chipset running x86_64 Ubuntu Feisty.
Ed Schofield wrote:
> Hi all,
>
> I'm trying out kvm and running into problems reported as "exception
> 12" and "exception 13" and segfaults. I'm using a HP Compaq dc7700p
> system with an Intel Q965 chipset running x86_64 Ubuntu Feisty.
>
> When I try to run either kvm-16 included with Feisty or m
Hi all,
I'm trying out kvm and running into problems reported as "exception
12" and "exception 13" and segfaults. I'm using a HP Compaq dc7700p
system with an Intel Q965 chipset running x86_64 Ubuntu Feisty.
When I try to run either kvm-16 included with Feisty or my own kvm-19
compiled from sourc
Hello,
> Savevm really saves the RAM, hardware state. It shouldn't take
> forever anyway. For snapshoting the hard disk you can use qemu-img or
> just stop; sync;copy
I don't want to copy 6 Gbyte around. What I want is:
I have one Diskiamge and a lot of co
>
>Hello,
>is it possible to a *diskimage* only snapshot with qemu?
>
>I tried "savevm snapshotname" but even if the machine is powered of it
>takes forever, so I assume he saves the memory of a powered-off
machine.
Savevm really saves the RAM, hardware state.
It shouldn't take forever anyway.
Fo
Hello,
is it possible to a *diskimage* only snapshot with qemu?
I tried "savevm snapshotname" but even if the machine is powered of it
takes forever, so I assume he saves the memory of a powered-off machine.
Thomas
-
It seems that this particular error was caused by return value of
rmode_tss_base() being 'int'.
There are a lot of places in qemu where 'int' variables are used for
addresses. Even after fixing these, I have some problems, probably
because conflicts of PCI memory I/O space with RAM.
Thanks,
Sergey
On Thursday 19 April 2007 06:43:23 Avi Kivity wrote:
> Andrew Walrond wrote:
> > On Wednesday 18 April 2007 16:50:00 Avi Kivity wrote:
> >> What's your VM HAL
> >> (http://kvm.qumranet.com/kvmwiki/Windows_ACPI_Workaround step 5)?
> >
> > MPS Uniprocessor PC
> >
> > And after following those ins
28 matches
Mail list logo
