Subject: [patch] KVM: fix hypercall cache/decache
From: Ingo Molnar <[EMAIL PROTECTED]>
a recent change to kvm_hypercall() flipped around the order of
->cache_regs() and ->decache_regs(), but that is bogus and causes
ESP/RIP corruption: ->cache_regs() will 'cache' the CPU-side registers
into th
Ingo Molnar wrote:
> Subject: [patch] KVM: fix hypercall cache/decache
> From: Ingo Molnar <[EMAIL PROTECTED]>
>
> a recent change to kvm_hypercall() flipped around the order of
> ->cache_regs() and ->decache_regs(), but that is bogus and causes
> ESP/RIP corruption: ->cache_regs() will 'cache' t
* Avi Kivity <[EMAIL PROTECTED]> wrote:
> Ingo Molnar wrote:
> >Subject: [patch] KVM: fix hypercall cache/decache
> >From: Ingo Molnar <[EMAIL PROTECTED]>
> >
> >a recent change to kvm_hypercall() flipped around the order of
> >->cache_regs() and ->decache_regs(), but that is bogus and causes
>
Managing userspace in subversion and the kernel in git is proving to be
quite a pain. Branches have to be maintained in parallel, tagging is
awkward, and bisection is fairly impossible.
What do people think about putting libkvm and qemu into the usr
directory of the kernel repo? It's slightly
>>> On Tue, Mar 20, 2007 at 8:13 AM, in message <[EMAIL PROTECTED]>,
Avi Kivity <[EMAIL PROTECTED]> wrote:
> Managing userspace in subversion and the kernel in git is proving to be
> quite a pain. Branches have to be maintained in parallel, tagging is
> awkward, and bisection is fairly impossi
Gregory Haskins wrote:
> Avi Kivity <[EMAIL PROTECTED]> wrote:
>
>> Managing userspace in subversion and the kernel in git is proving to be
>> quite a pain. Branches have to be maintained in parallel, tagging is
>> awkward, and bisection is fairly impossible.
>>
>> What do people think about
>>> On Tue, Mar 20, 2007 at 8:37 AM, in message <[EMAIL PROTECTED]>,
Avi Kivity <[EMAIL PROTECTED]> wrote:
> Gregory Haskins wrote:
>> Avi Kivity <[EMAIL PROTECTED]> wrote:
>>
>>> Managing userspace in subversion and the kernel in git is proving to be
>>> quite a pain. Branches have to be m
Gregory Haskins wrote:
> So if you can make the integration with the kernel tree work from a political
> standpoint, I'd say go for it.
>
There's really no political issue, as it's completely internal to kvm
development. It just seemed wierd and wrong so I thought I'd see if
someone has a b
>>> On Tue, Mar 20, 2007 at 9:02 AM, in message <[EMAIL PROTECTED]>,
Avi Kivity <[EMAIL PROTECTED]> wrote:
> Gregory Haskins wrote:
>> So if you can make the integration with the kernel tree work from a
> political standpoint, I'd say go for it.
>>
>
> There's really no political issue, as i
On Tuesday 20 March 2007, Avi Kivity wrote:
> Managing userspace in subversion and the kernel in git is proving to be
> quite a pain. Branches have to be maintained in parallel, tagging is
> awkward, and bisection is fairly impossible.
>
> What do people think about putting libkvm and qemu into
Highlights: acpi works again.
Changes from kvm-16:
- live migration enhancements (Uri Lublin)
- better/working acpi support
- revert to unhacked qemu bios
- fix some 32-bit nonpae guests (*BSD)
- initial ballooning support
- random fixes
Note that if you use the modules from Linux 2.6.20, you ne
>On Tuesday 20 March 2007, Avi Kivity wrote:
>> Managing userspace in subversion and the kernel in git is proving to be
>> quite a pain. Branches have to be maintained in parallel, tagging is
>> awkward, and bisection is fairly impossible.
>>
>> What do people think about putting libkvm and qemu i
Arnd Bergmann wrote:
> On Tuesday 20 March 2007, Avi Kivity wrote:
>
>> Managing userspace in subversion and the kernel in git is proving to be
>> quite a pain. Branches have to be maintained in parallel, tagging is
>> awkward, and bisection is fairly impossible.
>>
>> What do people think ab
Avi Kivity wrote:
> Arnd Bergmann wrote:
>
>> On Tuesday 20 March 2007, Avi Kivity wrote:
>>
>>
>>> Managing userspace in subversion and the kernel in git is proving to be
>>> quite a pain. Branches have to be maintained in parallel, tagging is
>>> awkward, and bisection is fairly imp
Bugs item #1684364, was opened at 2007-03-20 15:10
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=1684364&group_id=180599
Please note that this message will contain a full copy
On Tuesday 20 March 2007, Avi Kivity wrote:
> How does that work with multiple developers?
You need a set of well-understood rules if more than one person
has commit access to the repository.
The most simple rule would be that everyone just adds patches at
the end of the quilt series. When you su
Anthony Liguori wrote:
>>
>
> I think a single repository with libkvm and a QEMU and kernel patch
> queue (quilt or mq, it doesn't matter to me) would be best.
>
> Patches in the main queue would get folded upstream quickly
> (hopefully). Devs would submit new patches that you may choose to
>
Arnd Bergmann wrote:
> On Tuesday 20 March 2007, Avi Kivity wrote:
>
>> How does that work with multiple developers?
>>
>
> You need a set of well-understood rules if more than one person
> has commit access to the repository.
>
> The most simple rule would be that everyone just adds patche
Hello KVM devs,
I've just downloaded and checked out KVM-17. I tried
installing a Windows XP SP2 guest, using the following
script (notice how I did NOT use the '-no-acpi' flag):
qemu -hda /var/vm/img/WinXP.img -cdrom
/var/vm/iso/WinXP.iso -boot d -m 512
The first phase of installation went s
Alessandro Sardo wrote:
> Hello KVM devs,
>
> I've just downloaded and checked out KVM-17. I tried
> installing a Windows XP SP2 guest, using the following
> script (notice how I did NOT use the '-no-acpi' flag):
>
> qemu -hda /var/vm/img/WinXP.img -cdrom
> /var/vm/iso/WinXP.iso -boot d -m 512
>
Avi Kivity wrote:
> Arnd Bergmann wrote:
>
>> On Tuesday 20 March 2007, Avi Kivity wrote:
>>
>>
>>> How does that work with multiple developers?
>>>
>>>
>> You need a set of well-understood rules if more than one person
>> has commit access to the repository.
>>
>> The most s
Anthony Liguori wrote:
>
> I find using a patch queue useful though for submitting things
> upstream. A good example is our QEMU changes. It's a real pain to
> break apart the SVN history into individual patches.
Why not just extract diffs with 'svn diff'? That's what I did/do.
>
> I tend to
On Tuesday 20 March 2007, Avi Kivity wrote:
> > I find using a patch queue useful though for submitting things
> > upstream. A good example is our QEMU changes. It's a real pain to
> > break apart the SVN history into individual patches.
>
> Why not just extract diffs with 'svn diff'? That's
Hello Avi,
it works with this patch. I got an Windows 2000 with an ACPI HAL which
can boot now.
Thanks
Daniel
PS. Have you applied this patch to KVM 17?
Avi Kivity schrieb:
> Daniel Hecken wrote:
>> Hello!
>>
>> I have installed Windows 2000 on KVM SVN snapshot 4539 and the module
>> from the
Hi,
Do you use a software bridge and a tun/tap device ?
If you do, what is your network configuration (host + guest) ?
If you do not, search the list to find how to do it.
You'll need to setup a bridge (either manually or using an init script posted),
and add a '-net tap,script=/etc/kvm/qemu-ifup'
Folks --
The instructions on getting a source tree, e.g., kvm-17 is a bit
convoluted. I know that you'd like to simplify the process from a
development standpoint (i.e., the unification mail the last couple of
days discusses this). But, could I encourage you to document the
process of ge
Randy Thelen wrote:
> Folks --
>
> The instructions on getting a source tree, e.g., kvm-17 is a bit
> convoluted. I know that you'd like to simplify the process from a
> development standpoint (i.e., the unification mail the last couple of
> days discusses this). But, could I encourage you
I am trying to capture in vmx.c the hardware
performance counter(PMU) interrupt of a i386 Linux
kernel running with perfmon on a Core 2 Duo machine
running with kvm-15. host is running kvm with VT-x in
x86-64 mode.
The PMU interrupt is programmed in the APIC LVT entry
(set to 0xee)by the guest OS.
Randy Thelen wrote:
> Folks --
>
> The instructions on getting a source tree, e.g., kvm-17 is a bit
> convoluted. I know that you'd like to simplify the process from a
> development standpoint (i.e., the unification mail the last couple of
> days discusses this). But, could I encourage you
Shobha Ranganathan wrote:
> I am trying to capture in vmx.c the hardware
> performance counter(PMU) interrupt of a i386 Linux
> kernel running with perfmon on a Core 2 Duo machine
> running with kvm-15. host is running kvm with VT-x in
> x86-64 mode.
>
> The PMU interrupt is programmed in the APIC
>I am trying to capture in vmx.c the hardware
>performance counter(PMU) interrupt of a i386 Linux
>kernel running with perfmon on a Core 2 Duo machine
>running with kvm-15. host is running kvm with VT-x in
>x86-64 mode.
>
>The PMU interrupt is programmed in the APIC LVT entry
>(set to 0xee)by the g
31 matches
Mail list logo
