On Wed, 2009-09-30 at 21:15 +0200, Gerd Hoffmann wrote:
On 09/30/09 15:59, Mark McLoughlin wrote:
I'm planning on adding -hostnet and -nic arguments, which would not use
vlans by default but rather connect the nic directly to the host side.
No new -nic argument please. We should just
On 09/30/2009 10:04 PM, Gregory Haskins wrote:
A 2.6.27 guest, or Windows guest with the existing virtio drivers, won't work
over vbus.
Binary compatibility with existing virtio drivers, while nice to have,
is not a specific requirement nor goal. We will simply load an updated
KMP/MSI
On Thu, Oct 01, 2009 at 10:34:17AM +0200, Avi Kivity wrote:
Second, I do not use ioeventfd anymore because it has too many problems
with the surrounding technology. However, that is a topic for a
different thread.
Please post your issues. I see ioeventfd/irqfd as critical kvm
Hi,
we are running some stopped (sending stop via kvm-monitor socket)
vm's on our system. My intention was to pause (stop) the vm's and
unpause (cont) them on demand (very fast, without time delay, within 2
seconds ..).
After 'stop'ing, the vm's still using CPU-load, like the top will
tell:
One more,
So, how can I prevent the paused/stopped VM's to use my CPU from
the hostsystem ? Is there a way to handle this ?
If i send a signal STOP/CONT (kill -STOP pid or kill -CONT pid)
to the KVM-process, it looks like the kvm does not (sure ;-) use
any host CPU usage.
- Are there some
Christoph Hellwig h...@infradead.org wrote:
On Tue, Sep 22, 2009 at 03:25:13PM +0200, Juan Quintela wrote:
Christoph Hellwig h...@infradead.org wrote:
Btw, what's the state of getting compatfd upstream? It's a pretty
annoying difference between qemu upstream and qemu-kvm.
I haven't
On Thu, Oct 01, 2009 at 01:58:10PM +0200, Juan Quintela wrote:
Discused with Anthony about it. signalfd is complicated for qemu
upstream (too difficult to use properly), and eventfd ... The current
eventfd emulation is worse than the pipe code that it substitutes.
His suggestion here was
On Wed, Sep 30, 2009 at 02:11:52PM -0700, Shirley Ma wrote:
Hello all,
Anybody found this problem before? I kept hitting this issue for 2.6.31
guest kernel even with a simple network test.
INFO: task kjournal:337 blocked for more than 120 seconds.
echo 0
On Wed, Sep 30, 2009 at 05:39:07PM +0200, Juan Quintela wrote:
Now, also remove pre_task_link setting in save_state_to_tss16.
commit b237ac37a149e8b56436fabf093532483bff13b0
Author: Gleb Natapov g...@redhat.com
Date: Mon Mar 30 16:03:24 2009 +0300
KVM: Fix task switch back
On Wed, Sep 30, 2009 at 05:05:35PM -1000, Zachary Amsden wrote:
Patch is self-explanatory
.
commit 071a800cd07c2b9d13c7909aa99016d89a814ae6
Author: Zachary Amsden zams...@redhat.com
Date: Wed Sep 30 17:03:16 2009 -1000
Remove warning due to kvm_mmu_notifier_change_pte being static
Christoph Hellwig wrote:
On Thu, Oct 01, 2009 at 01:58:10PM +0200, Juan Quintela wrote:
Discused with Anthony about it. signalfd is complicated for qemu
upstream (too difficult to use properly), and eventfd ... The current
eventfd emulation is worse than the pipe code that it substitutes.
Juan Quintela wrote:
Discused with Anthony about it. signalfd is complicated for qemu
upstream (too difficult to use properly),
It's not an issue of being difficult.
To emulate signalfd, we need to create a thread that writes to a pipe
from a signal handler. The problem is that a write()
On 10/01/2009 04:23 PM, Anthony Liguori wrote:
Juan Quintela wrote:
Discused with Anthony about it. signalfd is complicated for qemu
upstream (too difficult to use properly),
It's not an issue of being difficult.
To emulate signalfd, we need to create a thread that writes to a pipe
from a
It occurs to me that we're handling assigned device interrupts
inefficiently: an interrupt is received on cpu A, injected, and wakes up
(or forces out of guest mode) a vcpu on cpu B. This involved an IPI and
bothers two cpus instead of one.
But we often known which vcpu will be woken up
On Wed, Sep 30, 2009 at 2:36 PM, Marcelo Tosatti mtosa...@redhat.com wrote:
On Wed, Sep 30, 2009 at 08:51:43AM -0300, Lucas Meneghel Rodrigues wrote:
Today's git test failed due to a build problem:
/usr/local/autotest/tests/kvm/src/kvm_kmod/x86/kvm_main.c:381: error:
unknown field
On 09/22/2009 06:19 PM, H. Peter Anvin wrote:
Ingo Molnar wrote:
* Avi Kivity a...@redhat.com wrote:
On 09/19/2009 09:40 AM, Avi Kivity wrote:
Add a general per-cpu notifier that is called whenever the kernel is
about to return to userspace. The notifier uses a thread_info flag
and existing
On 10/01/2009 08:21 AM, Avi Kivity wrote:
Re-ping?
If accepted, please merge just the core patch and I will carry all of
them in parallel. Once tip is merged I'll drop my copy of the first patch.
I was just talking to Ingo about this... would you consider this .32 or
.33 material at his
On 10/01/2009 05:25 PM, H. Peter Anvin wrote:
On 10/01/2009 08:21 AM, Avi Kivity wrote:
Re-ping?
If accepted, please merge just the core patch and I will carry all of
them in parallel. Once tip is merged I'll drop my copy of the first patch.
I was just talking to Ingo about
On Wed, 2009-09-30 at 20:51 -0500, Charles Duffy wrote:
Ross Boylan wrote:
http://www.linux-kvm.org/page/HOWTO1 says to build kvm I should get the
latest kvm-release.tar.gz.
http://www.linux-kvm.org/page/Downloads says If you want to use the
latest version of KVM kernel modules and
On 09/30/2009 04:21 AM, Ross Boylan wrote:
http://www.linux-kvm.org/page/HOWTO1 says to build kvm I should get the
latest kvm-release.tar.gz.
http://www.linux-kvm.org/page/Downloads says If you want to use the
latest version of KVM kernel modules and supporting userspace, you can
download the
On 09/30/2009 03:59 PM, Mark McLoughlin wrote:
I think we should keep the vlan stuff, just de-emphasise it.
Maybe we should do what X.org does, break it silently and remove it some
time later when no one complains.
--
Do not meddle in the internals of kernels, for they are subtle and
On Thu, 2009-10-01 at 18:42 +0200, Avi Kivity wrote:
On 09/30/2009 04:21 AM, Ross Boylan wrote:
http://www.linux-kvm.org/page/HOWTO1 says to build kvm I should get the
latest kvm-release.tar.gz.
http://www.linux-kvm.org/page/Downloads says If you want to use the
latest version of KVM
Avi Kivity wrote:
On 10/01/2009 04:23 PM, Anthony Liguori wrote:
Juan Quintela wrote:
Discused with Anthony about it. signalfd is complicated for qemu
upstream (too difficult to use properly),
It's not an issue of being difficult.
To emulate signalfd, we need to create a thread that writes
On Thu, 2009-10-01 at 10:20 -0300, Marcelo Tosatti wrote:
I've hit this in the past with ext3, mounting with data=writeback made
it
disappear.
Thanks. I will make a try. Someone should fix this.
Shirley
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message
On 10/01/2009 06:50 PM, Anthony Liguori wrote:
Avi Kivity wrote:
On 10/01/2009 04:23 PM, Anthony Liguori wrote:
Juan Quintela wrote:
Discused with Anthony about it. signalfd is complicated for qemu
upstream (too difficult to use properly),
It's not an issue of being difficult.
To emulate
On Thu, 2009-10-01 at 18:49 +0200, Avi Kivity wrote:
On 09/30/2009 03:59 PM, Mark McLoughlin wrote:
I think we should keep the vlan stuff, just de-emphasise it.
Maybe we should do what X.org does, break it silently and remove it some
time later when no one complains.
Well, the
On 10/01/2009 06:51 PM, Ross Boylan wrote:
So which file should I start from?
qemu-kvm is the userspace component, kvm-kmod is the kernel component as
an external module. 'kvm' is a package containing both.
That helps a lot; maybe that info could go up on the bugs or faq page.
Avi Kivity wrote:
On 10/01/2009 08:06 PM, Jim Paris wrote:
That's what I do. Just as a warning, if you're using the libvirt
packages from Debian unstable, make sure you also install
linux-libc-dev from unstable before building qemu-kvm.
Otherwise, virtio networking will fail. The reason is
Avi Kivity wrote:
On 09/30/2009 10:04 PM, Gregory Haskins wrote:
A 2.6.27 guest, or Windows guest with the existing virtio drivers,
won't work
over vbus.
Binary compatibility with existing virtio drivers, while nice to have,
is not a specific requirement nor goal. We will simply
I talked to Mingming, she suggested to use different IO scheduler. The
default scheduler is cfg, after I switch to noop, the problem is gone.
So there seems a bug in cfg scheduler. It's easily reproduced it when
running the guest kernel, so far I haven't hit this problem on the host
side.
If I
On Thu, Oct 1, 2009 at 4:00 PM, Shirley Ma mashi...@us.ibm.com wrote:
I talked to Mingming, she suggested to use different IO scheduler. The
default scheduler is cfg, after I switch to noop, the problem is gone.
deadline is the most recommended one for virtualization hosts. some
distros set it
On Wed, 30 Sep 2009 08:05:16 -0500
Anthony Liguori aligu...@us.ibm.com wrote:
Avi Kivity wrote:
On 09/30/2009 01:54 AM, Anthony Liguori wrote:
Hi,
Now that 0.11.0 is behind us, it's time to start thinking about 0.12.0.
I'd like to do a few things different this time around. I don't
On Thu, 2009-10-01 at 16:03 -0500, Javier Guerra wrote:
deadline is the most recommended one for virtualization hosts. some
distros set it as default if you select Xen or KVM at installation
time. (and noop for the guests)
I spoke too earlier, after a while noop scheduler hit the same issue.
Switching to different scheduler doesn't make the problem gone away.
Shirley
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Disable paravirt MMU capability reporting, so that new (or rebooted)
guests switch to native operation.
Paravirt MMU is a burden to maintain and does not bring significant
advantages compared to shadow anymore.
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
diff --git a/arch/x86/kvm/x86.c
Yes, and I really don't want to overdo it. PV for mfmsr/mtmsr and
mfspr/mtspr is really necessary. X86 simply has that in hardware.
Note to Avi: This is also because we aren't actually using the
virtualization feature of the processor, but instead running
the guest basically in user space.
36 matches
Mail list logo
