On 07/21/2009 08:21 PM, Martin Bligh wrote:
The advantages I see are: 1. it more closely follows the current
autotest structure/layout, 2. solves the problem of separating each test
out of the ever growing kvm_test.py and gives a sub dir of each test for
better structure (something we have been t
On Tue, Jul 21, 2009 at 10:45:31AM +0300, Yaniv Kaul wrote:
> On 7/21/2009 9:11 AM, Yolkfull Chow wrote:
>
>
>>
>> Previously, I used 'create partition primary' to verify whether the disk
>> could be formatted but always got an error:
>> ---
>> diskpart has encou
Hi folks,
Debian 5.0
KVM
I need to copy the text on client's (VM) terminal. Please advise how to
highlight the text with mouse pointer.
TIA
B.R.
SL
Send instant messages to your online friends http://uk.messenger.yahoo.com
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
(yes there's no typo in $subject, it's an old formatting
bug in printk).
When booting kvm guest on an AMD CPU, guest kernel prints
this warning:
WARNING: This combination of AMDprocessors is not suitable for SMP.
be it SMP or UP guest. What's wrong with this "combination",
and can it be fixed
When updating irq routing entries, we should memcpy the new entry
over the old one. Current code gets it wrong, and only works because
it's uncommon for guests to change tables.
Signed-off-by: Michael S. Tsirkin
---
Changes since v1:
updated irqchip case as well
qemu-kvm.c |4 ++--
1 fil
On Wed, Jul 22, 2009 at 05:18:49PM -0300, Marcelo Tosatti wrote:
>
> On Wed, Jul 22, 2009 at 05:41:13PM +0300, Michael S. Tsirkin wrote:
> > over the old one. Current code gets it wrong, and only works because
> > it's uncommon for guests to change MSI tables.
>
> Non-msi case seems to suffer fro
On Thu, Jul 23, 2009 at 02:10:31PM +0930, Rusty Russell wrote:
> On Wed, 22 Jul 2009 01:29:25 am Michael S. Tsirkin wrote:
> > - if (info->vector != VIRTIO_MSI_NO_VECTOR)
> > + if (info->vector != VIRTIO_MSI_NO_VECTOR) {
> > free_irq(vp_dev->msix_entries[info->vector].vector, vq);
>
Hi All,
I am using kvm-88 user space package with linux-2.6.25 kernel. I f i run
following command system gets hang.
./qemu-system-x86_64 -hda new.qcow2 -cdrom rhel-server-5.3-i386-dvd.iso
-boot d -m 512
When i print dmesg it displays as follows:
BUG: unable to handle kernel NULL pointer der
On Thu, Jul 23, 2009 at 03:06:07PM +0530, Haneef Syed wrote:
> Hi All,
>
> I am using kvm-88 user space package with linux-2.6.25 kernel. I f i run
> following command system gets hang.
>
Please use kvm-88 kernel package.
> ./qemu-system-x86_64 -hda new.qcow2 -cdrom rhel-server-5.3-i386-dvd.iso
If i use kvm-88 kernel package then system does not crash
but it uses qemu emulation but not kvm. I want kvm emulation so
can u tell me how to achieve that.
Gleb Natapov
07/23/2009 03:09 PM
To
Haneef Syed
cc
kvm@vger.kernel.org, virtualizat...@lists.linux-foundation.org,
a...@redhat.com
Wolfgang Nothdurft wrote:
> Hi,
>
> what limits does kvm have with device assignment and vt-d enabled.
>
> - Is it possible to assign pci devices behind the same pci bridge to
> different guests?
For devices behind conventional PCI bridges, the source-id in the DMA requests
is the requester-id
On Thu, Jul 23, 2009 at 02:10:31PM +0930, Rusty Russell wrote:
> On Wed, 22 Jul 2009 01:29:25 am Michael S. Tsirkin wrote:
> > - if (info->vector != VIRTIO_MSI_NO_VECTOR)
> > + if (info->vector != VIRTIO_MSI_NO_VECTOR) {
> > free_irq(vp_dev->msix_entries[info->vector].vector, vq);
>
On Thu, Jul 23, 2009 at 01:56:58PM +0930, Rusty Russell wrote:
> On Wed, 22 Jul 2009 01:29:09 am Michael S. Tsirkin wrote:
> > Free up msi vector tables.
>
> Michael, this papers over the bug, but doesn't actually fix the problem.
>
> The problem is that vp_free_vectors() does not do the reverse
Michael Tokarev wrote:
(yes there's no typo in $subject, it's an old formatting
bug in printk).
When booting kvm guest on an AMD CPU, guest kernel prints
this warning:
WARNING: This combination of AMDprocessors is not suitable for SMP.
be it SMP or UP guest. What's wrong with this "combinati
On Thu, Jul 23, 2009 at 03:13:25PM +0530, Haneef Syed wrote:
> If i use kvm-88 kernel package then system does not crash
>
> but it uses qemu emulation but not kvm. I want kvm emulation so
>
If it uses qemu emulation then you haven't installed kvm-88 kernel modules
properly.
> can u tell me how
Hi All !
In addition to Floppy controllers KVM-88 also break VirtIO hard disks. (Windows
2003 Drivers refuse to work now)
Linux (RHEL 5.3/x64) still boots off VirtIO Hard Disk.
It turned out to be a Qemu merge into KVM userspace:
kvm-87-119-ga8b7f95 (commit a8b7f959d1fd97c4ccaf08ce750020ecd08b
Here are a couple of fixes for virtio device removal.
Since these fix regressions (for devices with msi-x capability), I think
we need them for 2.6.31.
Changes since v1:
- rewrote the patches according to Rusty's comments
Michael S. Tsirkin (2):
virtio: fix double free_irq on device removal
msix_user_vectors counted both per-vq and shared/config vectors.
This causes BUG_ON when device is removed, as
free_vectors tries to free per-vq vectors.
Count per-vq vectors separately so they are only freed by del_vq.
Signed-off-by: Michael S. Tsirkin
---
drivers/virtio/virtio_pci.c | 38 ++
Make vp_free_vectors do the reverse of vq_request_vectors.
Signed-off-by: Michael S. Tsirkin
---
drivers/virtio/virtio_pci.c | 28 +++-
1 files changed, 15 insertions(+), 13 deletions(-)
diff --git a/drivers/virtio/virtio_pci.c b/drivers/virtio/virtio_pci.c
index a40e4
On Tue, Jul 21, 2009 at 11:05 AM, Ryan Harper wrote:
> * Michael Goldish [2009-07-21 07:38]:
>>
>> - "Lucas Meneghel Rodrigues" wrote:
>>
>> > Currently we have our kvm test control file and configuration file,
>> > having them split like this makes it harder for users to edit it,
>> > let's
On Tue, Jul 21, 2009 at 11:37 AM, David Huff wrote:
> Michael all very good comments, I specifically like the windows config
> file idea.
>
> The way I always envisioned it was something like this..
>
> The config file specifies the whole test matrix, ie all variants that
> you could run each t
> Um, I am afraid we have the different result... With your
> scheduler patch, we got 1% more performance improvement
> in the quick test. Of course more tests are needed to
> find a better value of delay.
What was your test case? How many runs did you do?
My results had a lot of variance in the
On Thu, Jul 23, 2009 at 07:37:37AM -0400, Alexey Eromenko wrote:
>
> Hi All !
>
> In addition to Floppy controllers KVM-88 also break VirtIO hard disks.
> (Windows 2003 Drivers refuse to work now)
>
> Linux (RHEL 5.3/x64) still boots off VirtIO Hard Disk.
>
> It turned out to be a Qemu merge i
When adding a vector fails, the used counter should
not be incremented, otherwise on vector change we will
try to update the routing entry.
Signed-off-by: Michael S. Tsirkin
---
hw/msix.c | 10 --
1 files changed, 8 insertions(+), 2 deletions(-)
diff --git a/hw/msix.c b/hw/msix.c
inde
Hi Gleb,
After installing kvm-88 kernel package and issuing modprobe kvm-intel and
in dmesg it displays as follows
"loaded kvm module (kvm-kmod-devel-86)"
it confirms that kvm-88 kernel modules are installed properly but still i
m unable to fix installation bug..?
Gleb Natapov
07/23/20
- "Marcelo Tosatti" wrote:
> On Thu, Jul 23, 2009 at 07:37:37AM -0400, Alexey Eromenko wrote:
> >
> > Hi All !
> >
> > In addition to Floppy controllers KVM-88 also break VirtIO hard
> disks. (Windows 2003 Drivers refuse to work now)
> >
> > Linux (RHEL 5.3/x64) still boots off VirtIO Har
On (Tue) Jul 21 2009 [19:54:00], Michael S. Tsirkin wrote:
> On Fri, Jul 17, 2009 at 06:34:40PM +0530, Amit Shah wrote:
> > Hello,
> >
> > Using recent qemu-kvm userspace with a slightly older kernel module I
> > get this when using the virtio-net device:
I was getting this with a very recent ker
>> If any of those tests fails (with some built in fault tolerance for a
>> small
>> hardware fallout rate), we stop the testing. All of that control flow
>> is governed by a control file. It sounds complex, but it's really not
>> if you build your "building blocks" carefully, and it's extremely po
Hi folks,
Debian 5.0
KVM
How to remove/delete VM (client) on command line instead of on Virt-manager.
Ex.
$ sudo virsh --connect qemu:///system
virsh # list --all
Id Name State
--
- vm10 shut off
- vm11 shut o
Hi all!
I'm using KVM-62 on a host with Ubuntu Hardy Heron server amd64
installed from Ubuntu repositories with a productive VM running an
application server.
I am observing in the VM a 'swapper tainted' in some of the processors
which cause that the application server is spontaneously restarted.
On Thu, Jul 23, 2009 at 07:17:51PM +0530, Haneef Syed wrote:
> Hi Gleb,
>
> After installing kvm-88 kernel package and issuing modprobe kvm-intel and
> in dmesg it displays as follows
>
> "loaded kvm module (kvm-kmod-devel-86)"
>
> it confirms that kvm-88 kernel modules are installed properly
This patch series fixes a regression reported by Amit Shah
(see Subject: Re: qemu-kvm missing some msix capability check,
Message-Id: 20090723142550.ga4...@amit-x200.redhat.com)
Since Amit's testing, I have refactored the change slightly to make the
patch smaller.
Rusty, can this go in for 2.6.3
This makes delete vq the reverse of find vq.
This is required to make it possible to retry find_vqs
after a failure, otherwise the list gets corrupted.
Signed-off-by: Michael S. Tsirkin
---
drivers/virtio/virtio_pci.c |6 +-
1 files changed, 5 insertions(+), 1 deletions(-)
diff --git a/
virtio currently fails to find any vqs if the device supports msi-x but fails
to assign it to a queue. Turns out, this actually happens for old host kernels
which can't allocate a gsi for the vector. As a result guest does not use
virtio net. Fix this by retrying with less vectors and finally di
Stephen Liu wrote:
>
> Hi folks,
>
> Debian 5.0
> KVM
>
> How to remove/delete VM (client) on command line instead of on Virt-manager.
>
> Ex.
> $ sudo virsh --connect qemu:///system
>
> virsh # list --all
> Id Name State
> --
> - vm10
Stephen Liu wrote:
>
> Hi folks,
>
> Debian 5.0
> KVM
>
> I need to copy the text on client's (VM) terminal. Please advise how to
> highlight the text with mouse pointer.
If you are running kvm with a VNC or SDL display, it is a graphical
display and you cannot select text from the host. You
Hi,
did anyone recently tried current KVM for Intel over some real-time
Linux? I'm seeing more than 500 us latency peaks on the host,
specifically during VM startup. This applies to both 2.6.29.6-rt23 and
Xenomai/I-pipe. For -rt, I both tried the included (patched) KVM modules
as well as kvm.git h
Today i thought it would be a good idea to take a look onto the kvm and
libvirt of rhel5.4 beta.
I did a update of my rhel5.3-installation with a selfbuilt libvirt 0.6.3
and kvm-85 which i removed before doing the update.
Afterwards i had no kvm-capabilities. There is no /etc/init.d/kvm -
lookin
Okay, had to delete /lib/modules/2.6.18-155.el5/weak-updates/kvm.ko
was created during upgrade.
--
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
On Wed, Jul 22, 2009 at 05:41:22PM +0300, Michael S. Tsirkin wrote:
> Kernels up to 2.6.31 have a bug: MSI entries where looked at when irq
> is acked, address_lo was interpreted as irqchip, and
> address_hi as pin. If that matches a real interrupt this prevents
> ack notifier from being processed
On Thu, Jul 23, 2009 at 11:52:16AM +0300, Michael S. Tsirkin wrote:
> When updating irq routing entries, we should memcpy the new entry
> over the old one. Current code gets it wrong, and only works because
> it's uncommon for guests to change tables.
>
> Signed-off-by: Michael S. Tsirkin
Applie
Jan Kiszka wrote:
> Hi,
>
> did anyone recently tried current KVM for Intel over some real-time
> Linux? I'm seeing more than 500 us latency peaks on the host,
> specifically during VM startup. This applies to both 2.6.29.6-rt23 and
> Xenomai/I-pipe. For -rt, I both tried the included (patched) KVM
On Thu, Jul 23, 2009 at 04:59:38PM -0300, Marcelo Tosatti wrote:
> On Wed, Jul 22, 2009 at 05:41:22PM +0300, Michael S. Tsirkin wrote:
> > Kernels up to 2.6.31 have a bug: MSI entries where looked at when irq
> > is acked, address_lo was interpreted as irqchip, and
> > address_hi as pin. If that m
Hi,
As I understand, the KVM code (kvm-86) may clear the write bit when
setting a shadow page table entry so that it can detect when an entry
needs to be marked dirty later. However, it also plays with the write
bit depending on whether the shadow page is allowed to be unsynched or
not. I'm not qui
Hi
I am trying to boot a patched version of Boch's BIOS on KVM. It works fine with
Qemu with -no-kvm option. However I get following with KVM
unhandled vm exit: 0x8021 vcpu_id 0
rax rbx 133a rcx rdx
0008
rsi 0008 rdi 00
On Wed, Jul 22, 2009 at 11:53:26PM +0200, Jan Kiszka wrote:
> Release and re-acquire preemption and IRQ lock in the same order as
> vcpu_enter_guest does.
This should happen in vcpu_enter_guest, before it decides to disable
preemption/irqs (so you consolidate the control there).
Maybe add a new m
On Thu, Jul 23, 2009 at 12:07:24AM +0200, Jan Kiszka wrote:
> When building against a split kernel, we have to add its source path to
> the include path. Otherwise arch/*/kvm/trace.h cannot be found.
>
> Signed-off-by: Jan Kiszka
Applied this and the vmx.c return value one, thanks.
> ---
>
>
Yes.. Host kernel oop like below.. Both Host and guest goes to deadlock
condition.
Gleb Natapov
Sent by: kvm-ow...@vger.kernel.org
07/23/2009 09:02 PM
To
Haneef Syed
cc
a...@redhat.com, kvm@vger.kernel.org,
virtualizat...@lists.linux-foundation.org
Subject
Re: KVM-88 Crash with Linux-2.6.
Hi Jim,
Thanks for your advice.
This is a server box running KVM for virtualizaion. All VM (guests) are
headless w/o X (graphic) installed except the host which is running Debian 5.0
as workstation. I run ssh to configure VM remotely w/o problem. The only
problem is before the VM get ssh
On Friday 24 July 2009 04:59:51 Saksena, Abhishek wrote:
> Hi
> I am trying to boot a patched version of Boch's BIOS on KVM. It works fine
> with Qemu with -no-kvm option. However I get following with KVM
The first thing come to my mind is your bios lacks some reserved page for VMX.
See qemu-kvm/
On Thu, Jul 23, 2009 at 11:19:05PM +0300, Michael S. Tsirkin wrote:
> On Thu, Jul 23, 2009 at 04:59:38PM -0300, Marcelo Tosatti wrote:
> > On Wed, Jul 22, 2009 at 05:41:22PM +0300, Michael S. Tsirkin wrote:
> > > Kernels up to 2.6.31 have a bug: MSI entries where looked at when irq
> > > is acked,
it is not needed.
Signed-off-by: Glauber Costa
---
qemu-kvm.c |8 +---
1 files changed, 1 insertions(+), 7 deletions(-)
diff --git a/qemu-kvm.c b/qemu-kvm.c
index 5e7dc0a..b15d5d6 100644
--- a/qemu-kvm.c
+++ b/qemu-kvm.c
@@ -2356,13 +2356,7 @@ int kvm_physical_memory_set_dirty_tracking(
Creation of those devices can be a lot simpler. In particular,
if we start by assuming they will be on, and disabling later if
anything fails (user request counts as failing here), we can remove
two variables that really serves no reason.
Signed-off-by: Glauber Costa
---
qemu-kvm-x86.c | 33 ++
On Fri, Jul 24, 2009 at 07:49:56AM +0530, Haneef Syed wrote:
> Yes.. Host kernel oop like below.. Both Host and guest goes to deadlock
> condition.
>
>
This oops doesn't look kvm specific. Try to run with -net none.
>
>
> Gleb Natapov
> Sent by: kvm-ow...@vger.kernel.org
> 07/23/2009 09:02
54 matches
Mail list logo
