Using 'wait_for' for logging into migrated guest repeats the work of
'wait_for_login' which exists already. We just need to change the name
of 'dest_vm'.
Signed-off-by: Yolkfull Chow
---
client/tests/kvm/kvm_test_utils.py |1 +
client/tests/kvm/tests/migration.py |7 ++-
2 files cha
Bugs item #2936094, was opened at 2010-01-21 11:07
Message generated for change (Tracker Item Submitted) made by kolobrod
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2936094&group_id=180599
Please note that this message will contain a full copy of the
On Thu, Jan 21, 2010 at 11:43 AM, Michael Tokarev wrote:
> Marcelo Tosatti wrote:
>> qemu-kvm-0.12.2 is now available. This release is based on the
>> upstream qemu 0.12.2, plus kvm-specific enhancements. Please see the
>> original qemu 0.12.2 release announcement for details.
>
> Thank you Avi,
Chris Wright wrote:
> * Daniel P. Berrange (berra...@redhat.com) wrote:
>> To be honest all possible naming schemes for '-cpu ' are just as
>> unfriendly as each other. The only user friendly option is '-cpu host'.
>>
>> IMHO, we should just pick a concise naming scheme & document it. Given
>> the
* Daniel P. Berrange (berra...@redhat.com) wrote:
> To be honest all possible naming schemes for '-cpu ' are just as
> unfriendly as each other. The only user friendly option is '-cpu host'.
>
> IMHO, we should just pick a concise naming scheme & document it. Given
> they are all equally unfriend
On Monday 18 January 2010, john cooper wrote:
> +.name = "Conroe",
> +.level = 2,
> +.vendor1 = CPUID_VENDOR_INTEL_1,
> +.vendor2 = CPUID_VENDOR_INTEL_2,
> +.vendor3 = CPUID_VENDOR_INTEL_3,
> +.family = 6, /* P6 */
> +.model = 2,
Marcelo Tosatti wrote:
> qemu-kvm-0.12.2 is now available. This release is based on the
> upstream qemu 0.12.2, plus kvm-specific enhancements. Please see the
> original qemu 0.12.2 release announcement for details.
Thank you Avi, Marcelo and all others, for the new release.
On my side, I've up
On 01/20/2010 02:26 PM, Daniel P. Berrange wrote:
To be honest all possible naming schemes for '-cpu' are just as
unfriendly as each other. The only user friendly option is '-cpu host'.
IMHO, we should just pick a concise naming scheme& document it. Given
they are all equally unfriendly, the on
On Wed, Jan 20, 2010 at 03:09:53PM -0500, john cooper wrote:
> Anthony Liguori wrote:
> > On 01/19/2010 02:03 PM, Chris Wright wrote:
> >> * Anthony Liguori (anth...@codemonkey.ws) wrote:
> >>
> >>> I'm very much against having -cpu Nehalem. The whole point of this is
> >>> to make things easie
Jamie Lokier wrote:
> john cooper wrote:
>> As before a cpu feature 'check' option is added which warns when
>> feature flags (either implicit in a cpu model or explicit on the
>> command line) would have otherwise been quietly unavailable to a
>> guest:
>>
>> # qemu-system-x86_64 ... -cpu Neha
Anthony Liguori wrote:
> On 01/19/2010 02:03 PM, Chris Wright wrote:
>> * Anthony Liguori (anth...@codemonkey.ws) wrote:
>>
>>> I'm very much against having -cpu Nehalem. The whole point of this is
>>> to make things easier for a user and for most of the users I've
>>> encountered, -cpu Nehalem
Jamie Lokier wrote:
> Anthony Liguori wrote:
>> On 01/18/2010 10:45 AM, john cooper wrote:
>>> x86 Conroe Intel Celeron_4x0 (Conroe/Merom Class Core 2)
>>> x86 Penryn Intel Core 2 Duo P9xxx (Penryn Class Core 2)
>>> x86 Nehalem Intel Core i7 9xx (Nehalem
On 01/20/2010 04:00 AM, Avi Kivity wrote:
> On 01/20/2010 12:02 PM, Gleb Natapov wrote:
>>
>> I can inject the event as HW interrupt on vector greater then 32 but not
>> go through APIC so EOI will not be required. This sounds
>> non-architectural
>> and I am not sure kernel has entry point code fo
qemu-kvm-0.12.2 is now available. This release is based on the
upstream qemu 0.12.2, plus kvm-specific enhancements. Please see the
original qemu 0.12.2 release announcement for details.
This release can be used with the kvm kernel modules provided by your
distribution kernel, or by the modules
On 01/20/2010 02:02 AM, Gleb Natapov wrote:
You can have the guest OS take an exception on a vector above 31 just
fine; you just need it to tell the hypervisor which vector it, the OS,
assigned for this purpose.
VMX doesn't allow to inject hardware exception with vector greater then 31.
SDM 3
Jan Kiszka wrote:
> Jan Kiszka wrote:
>> Tom Horsley wrote:
>>> On Fri, 15 Jan 2010 18:37:57 +0100
>>> Jan Kiszka wrote:
>>>
Tom Horsley wrote:
> I just submitted this fedora bug with lots of details:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=555788
>
> It sure seems
To enable proper debug register emulation under all conditions, trap
access to all DR0..7. This may be optimized later on.
Signed-off-by: Jan Kiszka
---
arch/x86/kvm/svm.c | 14 +-
1 files changed, 13 insertions(+), 1 deletions(-)
diff --git a/arch/x86/kvm/svm.c b/arch/x86/kvm/sv
Enhance mov dr instruction emulation used by SVM so that it properly
handles dr4/5: alias to dr6/7 if cr4.de is cleared. Otherwise return
EMULATE_FAIL which will let our only possible caller in that scenario,
ud_interception, re-inject UD.
We do not need to inject faults, SVM does this for us (exc
As we trap all debug register accesses, we do not need to switch real
DR6 at all. Clean up update_exception_bitmap at this chance, too.
Signed-off-by: Jan Kiszka
---
arch/x86/kvm/vmx.c | 23 ++-
1 files changed, 6 insertions(+), 17 deletions(-)
diff --git a/arch/x86/kvm/v
Make sure DR4 and DR5 are aliased to DR6 and DR7, respectively, if
CR4.DE is not set.
Signed-off-by: Jan Kiszka
---
arch/x86/kvm/vmx.c | 35 ++-
1 files changed, 26 insertions(+), 9 deletions(-)
diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
index 4903b4
Injecting GP without an error code is a bad idea (causes unhandled guest
exits). Moreover, we must not skip the instruction if we injected an
exception.
Signed-off-by: Jan Kiszka
---
arch/x86/kvm/vmx.c | 13 -
1 files changed, 8 insertions(+), 5 deletions(-)
diff --git a/arch/x86
Major parts of this series were already posted a while ago during the
debug register switch optimizations. This version now comes with an
additional fix for VMX (patch 1) and a rework of mov dr emulation for
SVM.
Find this series also at git://git.kiszka.org/linux-kvm.git queues/debugregs
Jan Kis
On Wed, 20 Jan 2010, Avi Kivity wrote:
> I'm uncomfortable with pushing Davide's patch into stable and possibly causing
> regressions with unrelated applications. Can't a guest live with a spurious
> interrupt? It's not like they're unknown.
Better material for .33 instead of stable, I agree.
On 01/20/2010 07:00 AM, Avi Kivity wrote:
On 01/20/2010 12:02 PM, Gleb Natapov wrote:
I can inject the event as HW interrupt on vector greater then 32 but not
go through APIC so EOI will not be required. This sounds
non-architectural
and I am not sure kernel has entry point code for this kind o
On 01/20/2010 07:12 PM, Randy Dunlap wrote:
On Wed, 20 Jan 2010 18:10:16 +1100 Stephen Rothwell wrote:
Hi all,
Changes since 20100119:
The kvm tree lost its build failure.
on i386/X86_32:
arch/x86/kvm/x86.c:3810: warning: left shift count>= width of type
arch/x86/kvm/x86.c:3812:
On 01/20/2010 07:00 PM, Anthony Liguori wrote:
So I have a nice patchset emulating this instruction (quite a pain,
since this is the first sse instruction we emulate), but it doesn't
help. The guest keeps using it so the display is incredibly slow.
Turns out the real problem is somewhere else
On Wed, 20 Jan 2010 18:10:16 +1100 Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20100119:
>
> The kvm tree lost its build failure.
on i386/X86_32:
arch/x86/kvm/x86.c:3810: warning: left shift count >= width of type
arch/x86/kvm/x86.c:3812: warning: left shift count >= width of type
arc
On 01/20/2010 10:46 AM, Avi Kivity wrote:
On 01/14/2010 04:20 PM, Avi Kivity wrote:
On 01/14/2010 04:06 PM, Dominik Brodowski wrote:
x/5i $eip
0x7f317ab64a7b: movdqa %xmm0,(%rdi)
0x7f317ab64a7f: movdqa %xmm0,0x10(%rdi)
0x7f317ab64a84: movdqa %xmm0,0x20(%rdi)
0x7f317ab64a89
On 01/14/2010 04:20 PM, Avi Kivity wrote:
On 01/14/2010 04:06 PM, Dominik Brodowski wrote:
x/5i $eip
0x7f317ab64a7b: movdqa %xmm0,(%rdi)
0x7f317ab64a7f: movdqa %xmm0,0x10(%rdi)
0x7f317ab64a84: movdqa %xmm0,0x20(%rdi)
0x7f317ab64a89: movdqa %xmm0,0x30(%rdi)
0x7f317ab64a
On 01/20/2010 05:13 PM, Levy, Lior wrote:
Hi all,
I am having some errors when building KVM 88 module.
That's pretty old. Take a look at
http://www.linux-kvm.org/page/Getting_the_kvm_kernel_modules. For
userspace, use the qemu-kvm-0.12 series.
--
error compiling committee.c: too many
On Tuesday 19 January 2010 05:57:53 pm Chris Wright wrote:
> * Tom Lendacky (t...@linux.vnet.ibm.com) wrote:
> > On Wednesday 13 January 2010 03:52:28 pm Chris Wright wrote:
> > > (Mark cc'd, sound familiar?)
> > >
> > > * Tom Lendacky (t...@linux.vnet.ibm.com) wrote:
> > > > On Sunday 10 January 2
Hi all,
I am having some errors when building KVM 88 module.
I configured the package as follows:
> ./configure --prefix=/usr/local/kvm
> --kerneldir=/usr/src/kernels/linux-2.6.30.2
And then typed:
> make
I am getting a lot of undefined reference errors. For example:
xen_domainbuild.o: In funct
On Wed, Jan 20, 2010 at 05:09:32PM +0200, Avi Kivity wrote:
> On 01/20/2010 04:58 PM, Michael S. Tsirkin wrote:
>>
>>> I'm uncomfortable with pushing Davide's patch into stable and possibly
>>> causing regressions with unrelated applications. Can't a guest live
>>> with a spurious interrupt?
>>>
On 01/20/2010 04:58 PM, Michael S. Tsirkin wrote:
I'm uncomfortable with pushing Davide's patch into stable and possibly
causing regressions with unrelated applications. Can't a guest live
with a spurious interrupt?
Well guests mask/unmask vector on each interrupt, so this will trigger
On Wed, Jan 20, 2010 at 04:10:37PM +0200, Avi Kivity wrote:
> On 01/19/2010 04:52 PM, Michael S. Tsirkin wrote:
>> On Sun, Jan 17, 2010 at 02:42:50PM +0200, Avi Kivity wrote:
>>
>>> On 01/13/2010 07:12 PM, Michael S. Tsirkin wrote:
>>>
Deassigning irqfd and assigning back caused spur
Thanks Jan. That fixed it.
Nicholas
Jan Kiszka wrote:
Hi Nicholas,
please don't drop CCs on reply.
Nicholas Amon wrote:
Hi Jan,
Thanks for responding. Yes, I am able to step instruction when I
disable kvm w/ the no-kvm option. My host kernel is 64bit 2.6.27 and
the program that I a
On Wed, Jan 20, 2010 at 08:21:44AM -0600, Anthony Liguori wrote:
> On 01/19/2010 06:15 PM, Chris Wright wrote:
> >* Anthony Liguori (anth...@codemonkey.ws) wrote:
> >>On 01/19/2010 02:03 PM, Chris Wright wrote:
> >>>* Anthony Liguori (anth...@codemonkey.ws) wrote:
> >>>
> I'm very much against
Hi there,
i have a problem with the -pidfile ... option in qemu 0.10.50. If I
start the machine, the pidfile with the correct PID will be created.
After shutdown the pidfile still exists. How can I instruct qemu to
delete the pidfile after machine shutdown?
Regards,
Tobias
On 01/19/2010 06:15 PM, Chris Wright wrote:
* Anthony Liguori (anth...@codemonkey.ws) wrote:
On 01/19/2010 02:03 PM, Chris Wright wrote:
* Anthony Liguori (anth...@codemonkey.ws) wrote:
I'm very much against having -cpu Nehalem. The whole point of this is
to make things eas
On 01/19/2010 04:52 PM, Michael S. Tsirkin wrote:
On Sun, Jan 17, 2010 at 02:42:50PM +0200, Avi Kivity wrote:
On 01/13/2010 07:12 PM, Michael S. Tsirkin wrote:
Deassigning irqfd and assigning back caused spurious interrupt. fix this
by clearing the counter on deassign. This is on top
On Wed, 2010-01-20 at 08:33 -0500, Michael Goldish wrote:
> - "Lucas Meneghel Rodrigues" wrote:
>
> > Update the config file tests_base.cfg with the
> > recently added windows unattended install files
> > (r4109), so one is actually able to use them
> > on tests.
> >
> > Signed-off-by: Lucas
On Wed, 2010-01-20 at 08:24 -0500, Michael Goldish wrote:
> - "Lucas Meneghel Rodrigues" wrote:
>
> > qemu upstream has slight differences regarding qemu-kvm
> > on the set of flags it supports. One of the most important
> > differences is that on qemu we have to set -enable-kvm
> > explicite
- "Lucas Meneghel Rodrigues" wrote:
> Update the config file tests_base.cfg with the
> recently added windows unattended install files
> (r4109), so one is actually able to use them
> on tests.
>
> Signed-off-by: Lucas Meneghel Rodrigues
> ---
> client/tests/kvm/tests_base.cfg.sample |
- "Lucas Meneghel Rodrigues" wrote:
> qemu upstream has slight differences regarding qemu-kvm
> on the set of flags it supports. One of the most important
> differences is that on qemu we have to set -enable-kvm
> explicitely. Take this into consideration on the base
> configuration files an
On 01/20/2010 01:59 PM, Michael S. Tsirkin wrote:
I'm guessing we need this for 2.6.32 stable and 2.6.33 as well?
That's what 'queued' means.
Aha. Which git branch is used for these?
kvm-updates/2.6.33. Cc: sta...@kernel.org means it will get
auto-submitted to 2.6.
On Wed, Jan 20, 2010 at 01:52:00PM +0200, Avi Kivity wrote:
> On 01/20/2010 01:36 PM, Michael S. Tsirkin wrote:
>> On Sun, Jan 17, 2010 at 02:40:13PM +0200, Avi Kivity wrote:
>>
>>> On 01/13/2010 06:58 PM, Michael S. Tsirkin wrote:
>>>
Looks like repeatedly binding same fd to multipl
On 01/20/2010 12:02 PM, Gleb Natapov wrote:
I can inject the event as HW interrupt on vector greater then 32 but not
go through APIC so EOI will not be required. This sounds non-architectural
and I am not sure kernel has entry point code for this kind of event, it
has one for exception and one f
On 01/20/2010 01:36 PM, Michael S. Tsirkin wrote:
On Sun, Jan 17, 2010 at 02:40:13PM +0200, Avi Kivity wrote:
On 01/13/2010 06:58 PM, Michael S. Tsirkin wrote:
Looks like repeatedly binding same fd to multiple gsi's with irqfd can
use up a ton of kernel memory for irqfd structures.
A
- "Lucas Meneghel Rodrigues" wrote:
> If we are going unattended install, make sure the step based
> setup doesn't run, as the unattended install procedure
> already takes care of guest setup.
>
> Signed-off-by: Lucas Meneghel Rodrigues
> ---
> client/tests/kvm/tests.cfg.sample |
This substitution got missed somehow
Signed-off-by: Juan Quintela
---
configure |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/configure b/configure
index 20c374a..be739e1 100755
--- a/configure
+++ b/configure
@@ -1747,7 +1747,7 @@ cat > $TMPC << EOF
int main(void) {
On Sun, Jan 17, 2010 at 02:40:13PM +0200, Avi Kivity wrote:
> On 01/13/2010 06:58 PM, Michael S. Tsirkin wrote:
>> Looks like repeatedly binding same fd to multiple gsi's with irqfd can
>> use up a ton of kernel memory for irqfd structures.
>>
>> A simple fix is to allow each fd to only trigger one
On 01/20/2010 11:57 AM, Sheng Yang wrote:
No protection for ring->first and ring->last? Seems it can writing the
same element pointed by ring->first twice, then skip one element at
(ring->first + 1)...
ring->first is owned by userspace, while ring->last is owned by the
kernel, so no pr
Nowdays (qemu 0.12) seabios loads option roms from pci rom bars. So
there is no need any more to scan for option roms and have qemu load
them. Zap the code.
Signed-off-by: Gerd Hoffmann
---
hw/device-assignment.c | 75
1 files changed, 0 inser
When I start qemu-img with strace I get the output below. Does
this help to to identify the problem?
scotty images # strace qemu-img convert -f qcow2 nweb.img -O raw test.img
execve("/usr/bin/qemu-img", ["qemu-img", "convert", "-f", "qcow2",
"nweb.img", "-O", "raw", "test.img"], [/* 44 vars */]) =
Hi Nicholas,
please don't drop CCs on reply.
Nicholas Amon wrote:
> Hi Jan,
>
> Thanks for responding. Yes, I am able to step instruction when I
> disable kvm w/ the no-kvm option. My host kernel is 64bit 2.6.27 and
> the program that I am debugging is 32 bit but starts in real mode. But
On Tue, Jan 19, 2010 at 12:10:17PM -0800, H. Peter Anvin wrote:
> On 01/19/2010 09:44 AM, Gleb Natapov wrote:
> >
> > Yes it can be done this way and I'll look into it once more. Using
> > exception vector is more convenient for three reasons: it allows to pass
> > additional data in error code, i
On Wednesday 20 January 2010 17:47:48 Avi Kivity wrote:
> On 01/20/2010 11:34 AM, Sheng Yang wrote:
> >> I think we can even do this from the I/O thread, without stopping a
> >> vcpu, since the colaesced mmio page is not tied to a vcpu but is a vm
> >> property.
> >
> > This one sounds better. But
On 01/20/2010 11:34 AM, Sheng Yang wrote:
I think we can even do this from the I/O thread, without stopping a
vcpu, since the colaesced mmio page is not tied to a vcpu but is a vm
property.
This one sounds better. But I've taken a look at the current userspace code:
#if defined(KVM
On Wednesday 20 January 2010 17:11:51 Avi Kivity wrote:
> On 01/20/2010 10:35 AM, Sheng Yang wrote:
> > The default action of calesced MMIO is, cache the writing in buffer,
> > until: 1. The buffer is full.
> > 2. Or the exit to QEmu due to other reasons.
> >
> > But this would result in a very lat
On 01/20/2010 10:35 AM, Sheng Yang wrote:
The default action of calesced MMIO is, cache the writing in buffer, until:
1. The buffer is full.
2. Or the exit to QEmu due to other reasons.
But this would result in a very late writing in some condition.
1. The each time write to MMIO content is smal
On Wednesday 20 January 2010 16:35:59 Sheng Yang wrote:
> The default action of calesced MMIO is, cache the writing in buffer, until:
> 1. The buffer is full.
> 2. Or the exit to QEmu due to other reasons.
>
> But this would result in a very late writing in some condition.
> 1. The each time write
The default action of calesced MMIO is, cache the writing in buffer, until:
1. The buffer is full.
2. Or the exit to QEmu due to other reasons.
But this would result in a very late writing in some condition.
1. The each time write to MMIO content is small.
2. The writing interval is big.
3. No nee
62 matches
Mail list logo
