O, I checked minutes ago (using local mirror), everthing is fine.
I got live migration works for FC5_32 which uses PIC only.
Eddie
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find pro
Insist on a reason when injecting a #GP into a guest
All places but one already do a printk before injecting a #GP: just
formalize it a little.
Signed-off-by: Rusty Russell <[EMAIL PROTECTED]>
diff -r f75b0a5fc387 drivers/kvm/kvm_main.c
--- a/drivers/kvm/kvm_main.cMon Jul 23 11:16:12 2007 +1
On Tue, 2007-07-24 at 09:21 +0300, Avi Kivity wrote:
> Rusty Russell wrote:
> > Actually, get_user_pages() does that for you. You have to make R/O any
> > writable pte where the guest doesn't set the dirty bit (so you can trap
> > it later) but last I put a printk in there, Linux doesn't do that.
Rusty Russell wrote:
> On Tue, 2007-07-24 at 08:30 +0300, Avi Kivity wrote:
>
>> Rusty Russell wrote:
>>
>>> On Mon, 2007-07-23 at 13:27 +0300, Avi Kivity wrote:
>>>
>>>
Having an address_space (like your patch does) is remarkably simple, and
requires few hooks from the
On Tue, 2007-07-24 at 08:30 +0300, Avi Kivity wrote:
> Rusty Russell wrote:
> > On Mon, 2007-07-23 at 13:27 +0300, Avi Kivity wrote:
> >
> >> Having an address_space (like your patch does) is remarkably simple, and
> >> requires few hooks from the current vm. However using existing vmas
> >>
Dong, Eddie wrote:
> ???
> I didn't think the APIC is removed.
> Who and which commit?
>
commit 394b6efba95f21d22687743def9aa1a0b7125809
Author: Eddie Dong <[EMAIL PROTECTED]>
Date: Thu Jul 19 12:12:53 2007 +0300
kvm: rename KVM_CAP_PIC to KVM_CAP_IRQCHIP
had parts of the patch that rem
On Tue, 2007-07-24 at 08:17 +0300, Avi Kivity wrote:
> With the ioctl interface, vms aren't really tied to tasks.
True, but this is really a debugging aid.
> How about current->pid (or with struct pid and containers, probably
> current->something->something->pid)?
I was reluctant because there's
???
I didn't think the APIC is removed.
Who and which commit?
Eddie
Avi Kivity wrote:
> He, Qing wrote:
>> Avi/Eddie,
>> I just noticed that the latest commit in lapic2 branch of
>> kvm-userspace effectively disabled in-kernel apic and ioapic. I
>> don't suppose it's intended, is it?
>>
>>
He, Qing wrote:
> Avi/Eddie,
> I just noticed that the latest commit in lapic2 branch of
> kvm-userspace effectively disabled in-kernel apic and ioapic. I don't
> suppose it's intended, is it?
>
>
It was a mistake on my part. I re-did the commit and pushed a new
version (you need to fetc
This patch is only for idea collection so far.
The dilemma is that how to export the pic/IOAPIC/apic state data
structure
to user and make sure it has same/similar structure in user level.
Otherwise a
convert is a must and we must maintain the converter.
With this, PIC only guest can do live migr
Shaohua Li wrote:
> On Mon, 2007-07-23 at 18:27 +0800, Avi Kivity wrote:
>
>> Shaohua Li wrote:
>>
>>> This patch series make kvm guest pages be able to be swapped out and
>>> dynamically allocated. Without it, all guest memory is allocated at
>>> guest start time.
>>>
>>> patches are again
Rusty Russell wrote:
> On Mon, 2007-07-23 at 13:27 +0300, Avi Kivity wrote:
>
>> Having an address_space (like your patch does) is remarkably simple, and
>> requires few hooks from the current vm. However using existing vmas
>> mapped by the user has many advantages:
>>
>> - compatible with s
Shaohua Li wrote:
>>>
>>>
>> You're not removing any shadows of the page, in case that page is a
>> guest page table. But I don't see anything wrong with it -- the page
>> won't change while it's in swap.
>>
> You are right. Should we?
>
I don't think so. It's just strange to ha
Against lapic2
This is a pre-cleanup for in kernel irqchip live migration support.
A guest may not have APIC but still have apic_base_msr be
save/restored in current live migration framework.
Signed-off-by: Yaozu (Eddie) Dong <[EMAIL PROTECTED]>
diff --git a/drivers/kvm/i8259.c b/drivers/kvm/i8
Shaohua Li wrote:
>>
>>> 1. vmcs_readl/vmcs_writel are called with preempt enabled
>>>
>>>
>> Why is that bad?
>>
> 1. raw_smp_processor_id()
> 2. migrate to other cpu
> 3. current->kvm_vcpu->cpu != the cpu id of step 1.
> you will see the warning.
>
Ah, that code is gone from pre
Avi/Eddie,
I just noticed that the latest commit in lapic2 branch of
kvm-userspace effectively disabled in-kernel apic and ioapic. I don't
suppose it's intended, is it?
Thanks,
Qing
-
This SF.net email is sponsored by
Jeff Dike wrote:
> On Mon, Jul 23, 2007 at 01:27:40PM +0300, Avi Kivity wrote:
>
>> Having an address_space (like your patch does) is remarkably simple, and
>> requires few hooks from the current vm. However using existing vmas
>> mapped by the user has many advantages:
>>
>
> It's also
Rusty Russell wrote:
> On Mon, 2007-07-23 at 14:32 +0100, Daniel P. Berrange wrote:
>
>> As Avi
>> says I dont't see how a individual QEMU process could provide any meaningful
>> identifier itself aside from its PID whose uniqueness is guarenteed by the
>> OS on its behalf.
>>
>
> Indeed.
Fix wrote:
>>> Host system: Linux
>>> Processor: Athlon64 X2 3600+
>>> Kernel: 2.6.22.1
>>> KVM version: 31
>>>
>>> Guest system: Linux
>>> Kernel: 2.6.22.1
>>>
>>> $ kvm -hda linux.img -boot c -m 256
>>>
>>> Host system freeze immediately after pressing in
>>> LILO
>>>
>>> /var/log/messages:
>>>
Just verified that the performance issue has already been fixed on KVM-32.
Thanks
Yunfeng
>-Original Message-
>From: Avi Kivity [mailto:[EMAIL PROTECTED]
>Sent: 2007年7月24日 0:12
>To: Zhao, Yunfeng
>Cc: kvm-devel@lists.sourceforge.net
>Subject: Re: [kvm-devel] ABAT Testing report, kernel 7
Hi,
Is the QEMU option to access host's directories as read-only FAT12
floppies expected to work in KVM-17? I tried to use a directory with a
single file (name shorter than 8 chars), I got a floppy device
emulated, but it looked like a blank floppy (no files).
Has anybody been successful with thi
Oh, I am sorry that it is the internal links.
-Original Message-
From: Anthony Liguori [mailto:[EMAIL PROTECTED]
Sent: 2007年7月24日 10:55
To: Zhang, Jingke
Cc: kvm-devel@lists.sourceforge.net
Subject: Re: [kvm-devel] [perf] KVM performance healthiness report --- kernel:
1f839d5e..., usersp
Zhang, Jingke wrote:
>
> Hi all,
>
> We have done the performance test for KVM commit (2007-07-20):
>
> Kernel: 1f839d5e7a627d245d63294b2a385b6202fadf1a
>
> Userspace: e6f43cccaf2319667f1408ca0ae79c82e813fa93
>
> By these URLs, detail info could be seen:
>
> Ia32e-KVM:
> http://otc-qa.sh.intel.com
Hi all,
We have done the performance test for KVM commit (2007-07-20):
Kernel: 1f839d5e7a627d245d63294b2a385b6202fadf1a
Userspace: e6f43cccaf2319667f1408ca0ae79c82e813fa93
By these URLs, detail info could be seen:
Ia32e-KVM:
http://otc-qa.sh.intel.com/kvm-perf/report.pl?cs
On Mon, 2007-07-23 at 20:34 +0800, Christoph Hellwig wrote:
> On Mon, Jul 23, 2007 at 03:29:36PM +0300, Avi Kivity wrote:
> > >Actually it requires lots of deep down VM internals symbols that'll
> never
> > >get exported.
> > >
> > >
> >
> > What's "it" here? kvm-specific address space or generic
On Mon, 2007-07-23 at 19:32 +0800, Avi Kivity wrote:
> Shaohua Li wrote:
> > Make KVM guest pages be allocated dynamically and able to be swaped
> out.
> >
> > One issue: all inodes returned from anon_inode_getfd are shared,
> > if one module changes field of the inode, other moduels might break.
>
On Mon, 2007-07-23 at 19:16 +0800, Avi Kivity wrote:
> Shaohua Li wrote:
> > add a routine to zap all shadow pgtble for a gfn. If kvm supports
> SMP,
> > the API should zap pgtble for all vcpus, but kvm shadow page table
> > really should be per-vm, instead of per-vcpu.
> >
> >
>
> kvm shadow pa
On Mon, 2007-07-23 at 18:46 +0800, Avi Kivity wrote:
> Shaohua Li wrote:
> > fix some bugs in kvm-sch patch.
> >
>
> There is now a 'preempt-hooks' branch on kvm.git with the
> preempt-hooks
> work. I'll continually update and rebase it against master.
>
> > 1. vmcs_readl/vmcs_writel are calle
On Mon, 2007-07-23 at 18:27 +0800, Avi Kivity wrote:
> Shaohua Li wrote:
> > This patch series make kvm guest pages be able to be swapped out and
> > dynamically allocated. Without it, all guest memory is allocated at
> > guest start time.
> >
> > patches are against latest git, and you need first
On 7/24/07, Rusty Russell <[EMAIL PROTECTED]> wrote:
> On Mon, 2007-07-23 at 14:32 +0100, Daniel P. Berrange wrote:
> > As Avi
> > says I dont't see how a individual QEMU process could provide any meaningful
> > identifier itself aside from its PID whose uniqueness is guarenteed by the
> > OS on it
On Mon, 2007-07-23 at 13:27 +0300, Avi Kivity wrote:
> Having an address_space (like your patch does) is remarkably simple, and
> requires few hooks from the current vm. However using existing vmas
> mapped by the user has many advantages:
>
> - compatible with s390 requirements
> - allows the
On Mon, 2007-07-23 at 14:32 +0100, Daniel P. Berrange wrote:
> As Avi
> says I dont't see how a individual QEMU process could provide any meaningful
> identifier itself aside from its PID whose uniqueness is guarenteed by the
> OS on its behalf.
Indeed. I use it in my pr_guest() patch which repl
<>-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> htt
On Mon, Jul 23, 2007 at 01:27:40PM +0300, Avi Kivity wrote:
> Having an address_space (like your patch does) is remarkably simple, and
> requires few hooks from the current vm. However using existing vmas
> mapped by the user has many advantages:
It's also needed for a SKAS-like UML client, whe
Avi Kivity wrote:
> Simon Gao wrote:
>>
>> So from kvm-31 and on, qemu command will become qemu-system-x86_64 no
>> matter host system is 32bit or 64bit? So it's possible to compile 64bit
>> kvm qemu with only 32bit libraries?
>>
>>
>
> Yes and yes. That's even more true for upstream qemu as w
> > Host system: Linux
> > Processor: Athlon64 X2 3600+
> > Kernel: 2.6.22.1
> > KVM version: 31
> >
> > Guest system: Linux
> > Kernel: 2.6.22.1
> >
> > $ kvm -hda linux.img -boot c -m 256
> >
> > Host system freeze immediately after pressing in
> > LILO
> >
> > /var/log/messages:
> >
> > Jul 23
Just one fix, but a biggie. Enjoy.
Changes since kvm-32:
- fix massive performance regression
Notes:
If you use the modules from kvm-33, you can use any version of Linux
from 2.6.9 upwards.
If you use the modules from Linux 2.6.20, you need to use kvm-12.
If you use the modules from
Zhao, Yunfeng wrote:
> Hi, all
>
> This is today's ABAT testing result against kvm.git
> 76f0301b5e4d2603d8e1ee5295db29faea660b49 and kvm-userspace.git
> 04cff0e47c4cc1e3d51f917a657b97ac2ed29719
> We are still using UP guests in the testing, we will try to enable some SMP
> Windows and Linux tes
Hello,
I have tried what you suggested but I could not reproduce the problem
anymore with KVM-32... guess it could have been fixed somewhere in
between the new releases. However, I am noticing two new issues:
1) rebooting the guest never works
2) I *very* often get BSODs as the one I sent as a
On Mon, Jul 23, 2007 at 04:39:33PM +0300, Avi Kivity wrote:
> Daniel P. Berrange wrote:
> >When managing QEMU & KVM guests, libvirt provides 3 identifiers with
> >varying levels of uniqueness
> >
> > - ID - a integer unique amongst all active guests on a host
> > - Name - a string uninque amongst a
Daniel P. Berrange wrote:
> When managing QEMU & KVM guests, libvirt provides 3 identifiers with
> varying levels of uniqueness
>
> - ID - a integer unique amongst all active guests on a host
> - Name - a string uninque amongst all active & inactive guests on a host
> - UUID - 32 byte hex string
On Mon, Jul 23, 2007 at 02:19:41PM +0300, Avi Kivity wrote:
> Avi Kivity wrote:
> > Carsten Otte wrote:
> >> Avi Kivity wrote:
> >>> From a Linux point of view, the pid identifies the VM. A
> >>> management application can, however, use its own VM identifiers as
> >>> it sees fit, and map the (
Christoph Hellwig wrote:
>
>> Generic vmas will be more intrusive AFAICT.
>>
>
> People use intrusive differently. Doing big changes to core code is not
> a problem if we actually get a proper interface. Just exporting core
> function without other changes and then writing code in modules th
On Mon, Jul 23, 2007 at 03:29:36PM +0300, Avi Kivity wrote:
> >Actually it requires lots of deep down VM internals symbols that'll never
> >get exported.
> >
> >
>
> What's "it" here? kvm-specific address space or generic vmas.
The patches in this thread.
> Generic vmas will be more intrusive
Christoph Hellwig wrote:
> On Mon, Jul 23, 2007 at 01:27:40PM +0300, Avi Kivity wrote:
>
>> Having an address_space (like your patch does) is remarkably simple, and
>> requires few hooks from the current vm. However using existing vmas
>> mapped by the user has many advantages:
>>
>
> Ac
On Mon, Jul 23, 2007 at 01:27:40PM +0300, Avi Kivity wrote:
> Having an address_space (like your patch does) is remarkably simple, and
> requires few hooks from the current vm. However using existing vmas
> mapped by the user has many advantages:
Actually it requires lots of deep down VM intern
On 7/22/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
> Adam Monsen wrote:
[...]
> > Dell tells me I bought a "Dual Core Pentium D, 930 Processor, 2X2MB
> > Cache, 3.0GHz 800MHz Front Side Bus". It came as part of a Dell
> > PowerEdge 830 package; the cheapest I could find that supported Intel
> > VT.
Fix wrote:
> Host system: Linux
> Processor: Athlon64 X2 3600+
> Kernel: 2.6.22.1
> KVM version: 31
>
> Guest system: Linux
> Kernel: 2.6.22.1
>
> $ kvm -hda linux.img -boot c -m 256
>
> Host system freeze immediately after pressing in
> LILO
>
> /var/log/messages:
>
> Jul 23 11:57:10 linux kerne
Avi Kivity wrote:
> It may make sense to add a vmid to qemu (or to keep it in the management
> application entirely). Certainly the kernel doesn't need to know about it.
Yes, I agree that should be userland only.
-
This SF.n
Shaohua Li wrote:
> Make KVM guest pages be allocated dynamically and able to be swaped out.
>
> One issue: all inodes returned from anon_inode_getfd are shared,
> if one module changes field of the inode, other moduels might break.
> Should we introduce a new API to not share inode?
>
> Signed-off
Avi Kivity wrote:
> Carsten Otte wrote:
>> Avi Kivity wrote:
>>> From a Linux point of view, the pid identifies the VM. A
>>> management application can, however, use its own VM identifiers as
>>> it sees fit, and map the (possibly persistent, gloablly unique, and
>>> ridiculously long) VMID t
Carsten Otte wrote:
> Avi Kivity wrote:
>> From a Linux point of view, the pid identifies the VM. A management
>> application can, however, use its own VM identifiers as it sees fit,
>> and map the (possibly persistent, gloablly unique, and ridiculously
>> long) VMID to the pid.
> It might be
Shaohua Li wrote:
> add a routine to zap all shadow pgtble for a gfn. If kvm supports SMP,
> the API should zap pgtble for all vcpus, but kvm shadow page table
> really should be per-vm, instead of per-vcpu.
>
>
kvm shadow page tables _are_ per-vm. Current kvm.git even makes that
more explici
Avi Kivity wrote:
> From a Linux point of view, the pid identifies the VM. A management
> application can, however, use its own VM identifiers as it sees fit, and
> map the (possibly persistent, gloablly unique, and ridiculously long)
> VMID to the pid.
It might be preferable to have something
Shaohua Li wrote:
> convert kvm lock to a mutex.
>
> TBD: after this change, a lot of logic in kvm can be simplified, eg, we
> don't need release lock and then do operation blocking.
>
This is now in the preempt-hooks branch.
--
error compiling committee.c: too many arguments to function
-
Jun Koi wrote:
> Hi,
>
> Do you think that it is necessary to have something like id for a
> specific VM on KVM? Without it, how can we identify a VM? By qemu's
> pid? Is that good, as we then depend on a particular device model?
>
From a Linux point of view, the pid identifies the VM. A mana
Shaohua Li wrote:
> fix some bugs in kvm-sch patch.
>
There is now a 'preempt-hooks' branch on kvm.git with the preempt-hooks
work. I'll continually update and rebase it against master.
> 1. vmcs_readl/vmcs_writel are called with preempt enabled
>
Why is that bad?
> 2. preempt_count che
Hi,
Do you think that it is necessary to have something like id for a
specific VM on KVM? Without it, how can we identify a VM? By qemu's
pid? Is that good, as we then depend on a particular device model?
Thanks,
Jun
-
This
Shahar Livne wrote:
> Hi,
>
>
> I have just downloaded the latest release kvm-32.tar.gz and found that
> it is corrupted.
>
> The file was probably uploaded via ftp in ascii mode (and not binary).
>
>
Yes. I updated the file; hopefully the sourceforge mirror system will
re-propagate it (rig
Hi,
I have just downloaded the latest release kvm-32.tar.gz and found that
it is corrupted.
The file was probably uploaded via ftp in ascii mode (and not binary).
It can be fixed using:
http://www.gzip.org/fixgz.c
Regards,
Shahar
--
Shaohua Li wrote:
> This patch series make kvm guest pages be able to be swapped out and
> dynamically allocated. Without it, all guest memory is allocated at
> guest start time.
>
> patches are against latest git, and you need first patch Avi's kvm-sch
> integration patch
> (http://sourceforge.net
kvm-32 contains an important silent data corruption fix, as well as a
number of minor fixes and updates.
Changes since kvm-31:
- fix oops with the slub allocator (CONFIG_SLUB)
- fix cmov instruction emulation, trashed by the mmio rmw fix
- fix rare, silent data corruption on writes that cross a p
Nguyen Anh Quynh wrote:
> On 7/23/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
>> Nguyen Anh Quynh wrote:
>> > This patch makes "install" compile code, and "install-rpm" package
>> rpms.
>>
>> 'install' and 'install-rpm' are typically run as root, and we don't want
>> to compile as root.
>
> Is it be
On 7/23/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
> Nguyen Anh Quynh wrote:
> > This patch makes "install" compile code, and "install-rpm" package rpms.
>
> 'install' and 'install-rpm' are typically run as root, and we don't want
> to compile as root.
Is it because of security reason, or something
Hi, all
This is today's ABAT testing result against kvm.git
76f0301b5e4d2603d8e1ee5295db29faea660b49 and kvm-userspace.git
04cff0e47c4cc1e3d51f917a657b97ac2ed29719
We are still using UP guests in the testing, we will try to enable some SMP
Windows and Linux tests in this week.
One new issue is
Nguyen Anh Quynh wrote:
> This patch makes "install" compile code, and "install-rpm" package rpms.
'install' and 'install-rpm' are typically run as root, and we don't want
to compile as root.
--
error compiling committee.c: too many arguments to function
-
Bugs item #1758756, was opened at 2007-07-23 16:58
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=1758756&group_id=180599
Please note that this message will contain a full copy
Nguyen Anh Quynh wrote:
> kvmctl.c: The first param of mmap() should be NULL rather than 0.
>
Applied, thanks.
--
error compiling committee.c: too many arguments to function
-
This SF.net email is sponsored by: Splunk Inc
This patch makes "install" compile code, and "install-rpm" package rpms.
Signed-off-by: Nguyen Anh Quynh <[EMAIL PROTECTED]>
diff --git a/Makefile b/Makefile
index 37b01d2..dd3f51c 100644
--- a/Makefile
+++ b/Makefile
@@ -22,7 +22,7 @@ initdir = /etc/init.d
confdir = /etc/kvm
utilsdir = /etc/kv
kvmctl.c: The first param of mmap() should be NULL rather than 0.
Signed-off-by: Nguyen Anh Quynh <[EMAIL PROTECTED]>
diff --git a/user/kvmctl.c b/user/kvmctl.c
index 3b0d8bc..43b374d 100644
--- a/user/kvmctl.c
+++ b/user/kvmctl.c
@@ -222,7 +222,7 @@ int kvm_create_vcpu(kvm_context_t kvm, int slo
Rusty Russell wrote:
> We add the kvm to the vm_list before initializing the vcpu mutexes,
> which can be mutex_trylock()'ed by decache_vcpus_on_cpu().
>
Applied this as well as the next one.
Good to see a thorough non-CodingStyle review of the entire code base --
thanks!
--
error compiling
Fix wrote:
> Host system: Linux
> Processor: Athlon64 X2 3600+
> Kernel: 2.6.22.1
> KVM version: 31
>
> Guest system: Linux
> Kernel: 2.6.22.1
>
> $ kvm -hda linux.img -boot c -m 256
>
> Host system freeze immediately after pressing in
> LILO
>
>
If the guest doesn't have any private informat
Simon Gao wrote:
>
> So from kvm-31 and on, qemu command will become qemu-system-x86_64 no
> matter host system is 32bit or 64bit? So it's possible to compile 64bit
> kvm qemu with only 32bit libraries?
>
>
Yes and yes. That's even more true for upstream qemu as well -- you can
run a 64-bit
Aurelien Jarno wrote:
> I have tried this branch, and the data get corrupted another way. This
> is due to the fact that the source address is not incremented for the
> second write. The patch below fixes that.
>
> With this patch, I haven't be able to make any corruption. I have added
> a printk i
Don't fall through and turn on PAE in this case.
Signed-off-by: Rusty Russell <[EMAIL PROTECTED]>
diff -r f75b0a5fc387 drivers/kvm/kvm_main.c
--- a/drivers/kvm/kvm_main.cMon Jul 23 11:16:12 2007 +1000
+++ b/drivers/kvm/kvm_main.cMon Jul 23 17:05:30 2007 +1000
@@ -548,6 +548,7 @@ void set_
We add the kvm to the vm_list before initializing the vcpu mutexes,
which can be mutex_trylock()'ed by decache_vcpus_on_cpu().
Signed-off-by: Rusty Russell <[EMAIL PROTECTED]>
diff -r b0134ad0aebe drivers/kvm/kvm_main.c
--- a/drivers/kvm/kvm_main.cThu Jul 19 16:37:12 2007 +1000
+++ b/drivers/
76 matches
Mail list logo
