FinnTux N/A wrote:
But here is a new version. Now with version number! :)
Changes:
- includes init script /etc/initd.d/kvm which starts and stops virtual
machines when booting and shutting down the host. Shutting down the
guest is done by sending system_powerdown to the guest. If the guest
Freddie Cash wrote:
On June 2, 2008 11:20 am FinnTux N/A wrote:
2008/6/2 Freddie Cash [EMAIL PROTECTED]:
Considering this is a test harness and not a control program, perhaps it
should be renamed in the kvm sources/builds, to something more
appropriate like kvmtest.
Anyways, I was afraid
Ben-Ami Yassour wrote:
Anthony Liguori [EMAIL PROTECTED] wrote on 04/29/2008 05:32:09 PM:
Subject
[PATCH] Handle vma regions with no backing page
This patch allows VMA's that contain no backing page to be used for
guest
memory. This is a drop-in replacement for Ben-Ami's first page in
his
2008/6/4 Avi Kivity [EMAIL PROTECTED]:
Jiri Kosina wrote:
[ re-introduced LKML to CC, and also added KVM CCs]
On Tue, 3 Jun 2008, Zdenek Kabelac wrote:
2008/6/3 Jiri Kosina [EMAIL PROTECTED]:
On Tue, 3 Jun 2008, Zdenek Kabelac wrote:
Another backtrace from suspend code path:
(T61,
Jan Kiszka wrote:
As Jerone pointed out, current kvm_invoke_guest_debug may segfault. The
reason is lacking re-initialization of cpu_single_env before
flush_queued_work is called. Here is the fix.
Applied, thanks. I also removed the same assignment a few lines later.
--
Do not meddle in
Carlo Marcelo Arenas Belon wrote:
complement 982e9b725e32f58158b6b9968f04e3377f52e63 with some basic
documentation, extracted from the commit message.
Applied, thanks.
--
Do not meddle in the internals of kernels, for they are subtle and quick to
panic.
--
To unsubscribe from this list:
Jiri Kosina wrote:
[ re-introduced LKML to CC, and also added KVM CCs]
On Tue, 3 Jun 2008, Zdenek Kabelac wrote:
2008/6/3 Jiri Kosina [EMAIL PROTECTED]:
On Tue, 3 Jun 2008, Zdenek Kabelac wrote:
Another backtrace from suspend code path:
(T61, 2GB, C2D, no SD card)
kernel
On Wed, 4 Jun 2008, Avi Kivity wrote:
Anthony Liguori wrote:
Thomas Gleixner wrote:
Can we please keep that code inside of drivers/clocksource/acpi_pm.c
without creating a new disconnected file in drivers/char ?
Btw, depending on the use case we might as well have a sysfs entry for
Eli Collins wrote:
Clear CR4.VMXE in hardware_disable. There's no reason to leave it set
after doing a VMXOFF.
VMware Workstation 6.5 checks CR4.VMXE as a proxy for whether the CPU
is in VMX mode, so leaving VMXE set means we'll refuse to power on.
With this change the user can power on
Zdenek Kabelac wrote:
Oops is from my real-hardware T61 (host) running the kvm-qemu (guest)
and was noticed after suspend.
But everything seemed to work just fine - hostguest continued to
operate normally after resume.
Can you reproduce this, with and without the kvm modules loaded?
--
I
Thomas Gleixner wrote:
On Wed, 4 Jun 2008, Avi Kivity wrote:
Anthony Liguori wrote:
Thomas Gleixner wrote:
Can we please keep that code inside of drivers/clocksource/acpi_pm.c
without creating a new disconnected file in drivers/char ?
Btw, depending on the use case we might as
Freddie Cash wrote:
Considering this is a test harness and not a control program, perhaps it
should be renamed in the kvm sources/builds, to something more
appropriate like kvmtest.
Sure, patches welcome.
--
I have a truly marvellous patch that fixes the bug which this
signature is too
Tobias Diedrich wrote:
Hi,
I get the following Oops when trying to start qemu-kvm
(Debian/unstable kvm package version 60+dfsg-1) on my system:
BUG: unable to handle kernel NULL pointer dereference at 0008
IP: [8021d44f] svm_vcpu_run+0x34/0x351
kvm-60 is quite old.
Marcelo Tosatti wrote:
On Sun, Jun 01, 2008 at 12:21:29PM +0300, Avi Kivity wrote:
Marcelo Tosatti wrote:
Addressing comments on the previous patchset, follows:
- Same fake C2 emulation
- /dev/pmtimer
- Support for multiple IO bitmap pages + userspace interface
- In-kernel ACPI
On Tue, 3 Jun 2008, Jiri Kosina wrote:
Ahh yes - you are right , I've completely forget about that old post -
I've thought that my post are usually getting fixed sooner :)
So yes - this is actually the same bug which is still not fixed within
the latest kernel - the machine is running
On Wed, 4 Jun 2008, Thomas Gleixner wrote:
OK, so it looks like KVM could be wrongly enabling IRQs/preemption on
the resume path. The original bug-report is on
http://lkml.org/lkml/2008/4/7/130
sysdev_resume() is supposed to run with interrupts disabled, at least
it was that way when
Jiri Kosina wrote:
On Wed, 4 Jun 2008, Thomas Gleixner wrote:
OK, so it looks like KVM could be wrongly enabling IRQs/preemption on
the resume path. The original bug-report is on
http://lkml.org/lkml/2008/4/7/130
sysdev_resume() is supposed to run with interrupts disabled, at least
Bugs item #1984384, was opened at 2008-06-04 13:49
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=1984384group_id=180599
Please note that this message will contain a full copy of
Bugs item #1984384, was opened at 2008-06-04 14:49
Message generated for change (Comment added) made by avik
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=1984384group_id=180599
Please note that this message will contain a full copy of the comment
On Tue, 2008-06-03 at 10:49 -0400, Beth Kon wrote:
I'm running an Ubuntu 7.10 guest on a kvm git build (commit
3125ffd6edb9384b3e418fc08fea99e7e1548a96) and am seeing repeated
messages like:
[3393.124685] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
frozen
[3393.127599]
Dave Hansen wrote:
On Thu, 2008-03-27 at 16:59 +0200, Avi Kivity wrote:
Dave Hansen wrote:
On Thu, 2008-03-27 at 12:10 +0200, Avi Kivity wrote:
btw, is this with = 4GB RAM on the host?
Well, are you asking whether I have PAE on or not? :)
No, I'm asking
On Wed, 2008-06-04 at 15:38 +0300, Avi Kivity wrote:
Beth Kon wrote:
On Tue, 2008-06-03 at 10:49 -0400, Beth Kon wrote:
I'm running an Ubuntu 7.10 guest on a kvm git build (commit
3125ffd6edb9384b3e418fc08fea99e7e1548a96) and am seeing repeated
messages like:
[3393.124685]
Gerd Hoffmann wrote:
Jeremy Fitzhardinge wrote:
Gerd Hoffmann wrote:
paravirt clock source patches, next round.
There is now a pvclock-abi.h file with the structs and some longish
comments in it and everybody is switched over to use the stuff in
there.
This all looks pretty
Ben-Ami Yassour wrote:
Amit,
Below is the patch for PCI passthrough tree, it enables a guest to
access a device's
memory mapped I/O regions directly, without requiring the host to trap
and
emulate every MMIO access.
This patch requires only userspace changes and it is relaying on the
Amit Shah wrote:
The first option can be enforced by calls to pci_enable_device() and
pci_request_regions(). This can solve the problem of assigning multiple
devices of the same guest as well.
Yes, that sounds good.
Dynamically unbinding devices is prone to a lot of errors and assumptions
Bugs item #1984384, was opened at 2008-06-04 05:49
Message generated for change (Comment added) made by dsahern
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=1984384group_id=180599
Please note that this message will contain a full copy of the comment
Bugs item #1984384, was opened at 2008-06-04 14:49
Message generated for change (Comment added) made by avik
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=1984384group_id=180599
Please note that this message will contain a full copy of the comment
On Wednesday 04 June 2008 19:49:21 Avi Kivity wrote:
Amit Shah wrote:
Dynamically unbinding devices is prone to a lot of errors and assumptions
and such policy shouldn't be enforced. We should either fail the
assignment and let the administrator take care of doing the right thing
and
Amit Shah wrote:
I was thinking of putting the device in suspend state. However, I checked a
few drivers and not all release resources during suspend. However, even if
this is possible, it becomes an enforced policy that a user may not like.
What happens if there is a real suspend?
The
Bugs item #1984384, was opened at 2008-06-04 13:49
Message generated for change (Comment added) made by ravpl
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=1984384group_id=180599
Please note that this message will contain a full copy of the comment
Bugs item #1984384, was opened at 2008-06-04 05:49
Message generated for change (Comment added) made by dsahern
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=1984384group_id=180599
Please note that this message will contain a full copy of the comment
On Tue, 2008-06-03 at 13:39 +0200, Andrea Arcangeli wrote:
On Tue, Jun 03, 2008 at 02:17:55PM +0300, Ben-Ami Yassour wrote:
Anthony Liguori [EMAIL PROTECTED] wrote on 04/29/2008 05:32:09 PM:
Subject
[PATCH] Handle vma regions with no backing page
This patch allows VMA's that contain
Laurent Vivier wrote:
When kernel has to send MMIO writes to userspace, it stores them
in memory until it has to pass the hand to userspace for another
reason. This avoids to have too many context switches on operations
that can wait.
These patches introduce an ioctl() to define MMIO allowed to
On Wednesday 04 June 2008 20:23:53 Avi Kivity wrote:
Amit Shah wrote:
I was thinking of putting the device in suspend state. However, I
checked a few drivers and not all release resources during suspend.
However, even if this is possible, it becomes an enforced policy that a
user may not
Avi Kivity wrote:
Looks like we need to reintroduce a refcount bit in the pte, and check
the page using the VMA.
I don't think mucking with the VMA is going to help. We're already
using the VMA to determine that the region is MMIO. What we need to be
able to do is figure out, given a
On Wed, 4 Jun 2008, Avi Kivity wrote:
Eli Collins wrote:
Clear CR4.VMXE in hardware_disable. There's no reason to leave it set after
doing a VMXOFF.
VMware Workstation 6.5 checks CR4.VMXE as a proxy for whether the CPU is in
VMX mode, so leaving VMXE set means we'll refuse to power on.
On Wed, Jun 04, 2008 at 06:09:24PM +0300, Ben-Ami Yassour1 wrote:
We noticed that pfn_valid does not always works as expected by
this patch to indicate that a pfn has a backing page. We have
seen a case where CONFIG_NUMA was not set and then where
pfn_valid returned 1 for an mmio
On Wed, Jun 04, 2008 at 07:17:55PM +0300, Muli Ben-Yehuda wrote:
On Wed, Jun 04, 2008 at 06:09:24PM +0300, Ben-Ami Yassour1 wrote:
We noticed that pfn_valid does not always works as expected by
this patch to indicate that a pfn has a backing page. We have
seen a case where
On Wed, Jun 04, 2008 at 02:41:20PM -0500, Anthony Liguori wrote:
The pfn does have a backing page. When using CONFIG_FLATMEM, pfn_valid()
is simply:
#ifdef CONFIG_FLATMEM
#define pfn_valid(pfn) ((pfn) end_pfn)
#endif
And this is true, pfn_valid() just indicates whether there is
On Wed, 2008-06-04 at 21:51 +0200, Andrea Arcangeli wrote:
Dave mentioned that SetPageReserved() doesn't necessarily get called
for
zones with bad alignment.
What does 'bad alignment' mean? Buddy was used to require each zone to
start at 1MAX_ORDER naturally aligned physical address (any
We've been using Xen 3.0 for the past 18-ish months on a couple boxes here
and were quite impressed with it, especially when using the xen-tools
package on Debian. But, it couldn't run FreeBSD or Windows guests on our
existing hardware, so we bought shiny new Opteron 2000-series systems
with
On Wednesday 04 June 2008 03:51:12 pm you wrote:
snip
Today, I managed to get a couple Linux guests to load using the
virtio drivers in kernel 2.6.25. Colour me impressed!
snip
That, combined with how easy it is to manage kvm (I wrote my own
management scripts and config file format that is a
Hello,
this is an update of the patch to test kvm on mmu notifier v18. I'll
post the mmu notifier v18 tomorrow after some more review but I can
post the kvm side in the meantime (which works with the previous v17
as well if anyone wants to test).
This has a relevant fix for kvm_unmap_rmapp:
There's a bug in the IOAPIC code for level-triggered interrupts. Its
relatively easy to trigger by sharing (virtio-blk + usbtablet was the
testcase, initially reported by Gerd von Egidy).
The remote_irr variable is used to indicate accepted but not yet acked
interrupts. Its cleared from the EOI
* Tobias Diedrich ([EMAIL PROTECTED]) wrote:
BUG: unable to handle kernel NULL pointer dereference at 0008
IP: [8021d44f] svm_vcpu_run+0x34/0x351
PGD 7e01b067 PUD 7bc86067 PMD 0
Oops: [1] PREEMPT
CPU 0
Modules linked in: zaurus cdc_ether usbnet snd_hda_intel
Resending the virtio-blk async patches, now that the reason for Gerd's
hangs are known.
The above results are on host hot-cached data, cold-cache data workloads
are the real winners, where the current code waits until each read
request is finished before submitting the next one.
ide:
Version
So drivers can do whatever necessary on reset.
Signed-off-by: Marcelo Tosatti [EMAIL PROTECTED]
Index: kvm-userspace.vblk/qemu/hw/virtio.c
===
--- kvm-userspace.vblk.orig/qemu/hw/virtio.c
+++ kvm-userspace.vblk/qemu/hw/virtio.c
@@
47 matches
Mail list logo
