Bugs item #2019608, was opened at 2008-07-16 15:03
Message generated for change (Comment added) made by awwy
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2019608group_id=180599
Please note that this message will contain a full copy of the comment
Thanks Dave
On Mon, Jul 28, 2008 at 12:04 PM, Dave Waters [EMAIL PROTECTED] wrote:
The second revision of PV NIC for Windows is on the KVM Source Forge site:
http://sourceforge.net/project/showfiles.php?group_id=180599
Dave Waters
-Original Message-
From: Sukanto Ghosh [EMAIL
On Mon, 28 Jul 2008 15:06:17 +0800, Stephen Liu wrote:
On running
# kvm -m 750 -cdrom /dev/scd0 -boot d ubuntu6.06.img
add -vnc :number
or disable graphics completly (see kvm --help)
Hi Thomas,
Thanks for your advice.
There is no graphic running on the server which
On Tuesday 22 July 2008 20:13:53 Ben-Ami Yassour wrote:
-int kvm_pic_read_irq(struct kvm_pic *s)
+int kvm_pic_read_irq(struct kvm *kvm)
{
int irq, irq2, intno;
+ struct kvm_pic *s = pic_irqchip(kvm);
irq = pic_get_irq(s-pics[0]);
if (irq = 0) {
@@ -186,6 +187,8 @@
* On Sunday 27 Jul 2008 23:02:06 Farkas Levente wrote:
Greg Kurtzer wrote:
On Sat, Jul 26, 2008 at 1:12 AM, Avi Kivity [EMAIL PROTECTED] wrote:
Greg Kurtzer wrote:
Hello,
I noticed some problems with the e1000 implementation in kvm = 70. At
first glance it seemed liked a PXE problem
* On Tuesday 22 Jul 2008 17:43:53 Ben-Ami Yassour wrote:
Based on a patch from: Amit Shah [EMAIL PROTECTED]
This patch adds support for handling PCI devices that are assigned to
the guest.
The device to be assigned to the guest is registered in the host kernel
and interrupt delivery is
In my case, it is possible but seems unlikely as I can switch between
a working KVM-69 and KVM=70 and replicate the bug (nothing related to
the TAP or bridge support or configuration on the system is changing
in my scenario). Still it could be a bug that just gets tickled by the
newer KVM's, but I
Henrik Holst wrote:
There is a boot regression in kvm-72:
scsi and virtio images will not survive a reboot from within the
guest. Only drives with if=ide survives a rebooting of the guest.
That is, this will create a guest that will survive any number of reboots:
qemu-system-x86_64 -M
--- Thomas Mueller [EMAIL PROTECTED] wrote:
On Mon, 28 Jul 2008 15:06:17 +0800, Stephen Liu wrote:
On running
# kvm -m 750 -cdrom /dev/scd0 -boot d ubuntu6.06.img
add -vnc :number
or disable graphics completly (see kvm --help)
Hi Thomas,
Thanks for your
2008/7/28 Anthony Liguori [EMAIL PROTECTED]:
Henrik Holst wrote:
There is a boot regression in kvm-72:
scsi and virtio images will not survive a reboot from within the
guest. Only drives with if=ide survives a rebooting of the guest.
That is, this will create a guest that will survive any
KVM intends to use paravirt code to calibrate khz. Xen
current code will do just fine. So as a first step, factor out
code to pvclock.c.
Signed-off-by: Glauber Costa [EMAIL PROTECTED]
---
arch/x86/kernel/pvclock.c | 12
arch/x86/xen/time.c | 11 ++-
Hi Alberto,
Thanks for your advice.
On Monday 28 July 2008 08:09:58 am you wrote:
# kvm -hda ubuntu6.06.img -cdrom /dev/scd0 -m 512 -boot d -vnc IP:0
Could not parse VNC address
# kvm -hda ubuntu6.06.img -cdrom /dev/scd0 -m 512 -boot d -vnc IP:1
Could not parse VNC address
The IP
--- Ian Kirk [EMAIL PROTECTED] wrote:
Stephen Liu wrote:
# kvm -hda ubuntu6.06.img -cdrom /dev/scd0 -m 512 -boot d -vnc IP:0
Could not parse VNC address
IP is not a valid ip address?
Sorry I don't follow. Please explain in more detail.
B.R.
satimis
Send instant messages to your
From: Kay, Allen M [EMAIL PROTECTED]
This patch extends the VT-d driver to support KVM
[Ben: fixed memory pinning]
Signed-off-by: Kay, Allen M [EMAIL PROTECTED]
Signed-off-by: Weidong Han [EMAIL PROTECTED]
Signed-off-by: Ben-Ami Yassour [EMAIL PROTECTED]
---
drivers/pci/dmar.c
In some cases it is not enough to identify mmio memory slots by
pfn_valid. This patch adds checking the PageReserved as well.
Signed-off-by: Ben-Ami Yassour [EMAIL PROTECTED]
Signed-off-by: Muli Ben-Yehuda [EMAIL PROTECTED]
---
virt/kvm/kvm_main.c | 22 +++---
1 files changed,
[Ben: fixed memory pinning]
Signed-off-by: Kay, Allen M [EMAIL PROTECTED]
Signed-off-by: Weidong Han [EMAIL PROTECTED]
Signed-off-by: Ben-Ami Yassour [EMAIL PROTECTED]
---
arch/x86/kvm/Makefile |2 +-
arch/x86/kvm/vtd.c | 180
Follwing is the patch for the userspace part
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Based on a patch from: Amit Shah [EMAIL PROTECTED]
We can assign a device from the host machine to a guest. The
original code comes from Neocleus.
A new command-line option, -pcidevice is added.
For example, to invoke it for an Ethernet device sitting at
PCI bus:dev.fn 04:08.0 with host IRQ 18,
On Mon, 2008-07-28 at 14:49 +0800, Han, Weidong wrote:
Ben-Ami Yassour wrote:
From: Kay, Allen M [EMAIL PROTECTED]
{
if (pfn_valid(pfn))
return PageReserved(pfn_to_page(pfn));
I cannot find this is_mmio_pfn() definition on main KVM tree, and failed
to patch it.
On Mon, 2008-07-28 at 15:27 +0800, Yang, Sheng wrote:
On Tuesday 22 July 2008 20:13:53 Ben-Ami Yassour wrote:
-int kvm_pic_read_irq(struct kvm_pic *s)
+int kvm_pic_read_irq(struct kvm *kvm)
{
int irq, irq2, intno;
+ struct kvm_pic *s = pic_irqchip(kvm);
irq =
Am Sonntag, 27. Juli 2008 schrieb Avi Kivity:
This is really a no-op, since s390 will nack a KVM_CAP_SET_TSS_ADDR
query. Of course, the change is an improvement.
@@ -92,8 +92,11 @@ int get_free_slot(kvm_context_t kvm)
if (tss_ext 0)
i = 0;
else
+#if
Hi Henrik,
Thanks for your advice.
- snip -
You should run it as:
# kvm -hda ubuntu6.06.img -cdrom /dev/scd0 -m 512 -boot d -vnc :0
Tried it just hangs there. I don't run X on the server.
Then it is working, since you are running it with -vnc :0 kvm/qemu
will provide all the output to the
Thanks for your advice and URL.
Performed following test but failed.
# kvm -hda ubuntu6.06.img -cdrom /dev/scd0 -m 512 -boot d -vnc IP:0
Could not parse VNC address
# kvm -hda ubuntu6.06.img -cdrom /dev/scd0 -m 512 -boot d -vnc IP:1
on kvm-machine) kvm -hda ubuntu6.06.img
On my machine with gcc 3.4, kvm uses ~2k of stack in a few
select functions. This is mostly because gcc fails to
notice that the different case: statements could have their
stack usage combined. It overflows very nicely if interrupts
happen during one of these large uses.
This patch uses two
Same as the last one, but this time we use kmalloc()
for all of the uses.
Note that the kfree()s take advantage of the fact that
kfree() is OK on NULL.
Signed-off-by: Dave Hansen [EMAIL PROTECTED]
---
virt/kvm/kvm_main.c | 48 ++--
1 files changed,
This time it is kvm_arch_vcpu_ioctl(). Use dynamic
allocations to reduce its stack usage.
Signed-off-by: Dave Hansen [EMAIL PROTECTED]
---
arch/x86/kvm/x86.c | 20 +---
1 files changed, 13 insertions(+), 7 deletions(-)
diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
Since this probably is due to something in qemu it would be great if
the release-log to kvm could include towards which revision of the
qemu svn repository that was merged. Or am I to understand that the
merge was performed on the same day as the new kvm release was
released?
I'm thinking
Dave Hansen wrote:
On my machine with gcc 3.4, kvm uses ~2k of stack in a few
select functions. This is mostly because gcc fails to
notice that the different case: statements could have their
stack usage combined. It overflows very nicely if interrupts
happen during one of these large uses.
Bugs item #2030701, was opened at 2008-07-28 14:03
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2030701group_id=180599
Please note that this message will contain a full copy of
Bugs item #2030703, was opened at 2008-07-28 14:05
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2030703group_id=180599
Please note that this message will contain a full copy of
Hi Andrea,
On Fri, Jul 25, 2008 at 04:24:52PM +0200, Andrea Arcangeli wrote:
Hello,
This is the latest version of the kvm mmu notifier patch.
This allows largepages to be invalidated too, and a separate patch
takes care of alias locking (2/5) and memslot locking (3/5).
While in the
On Mon, Jul 28, 2008 at 06:11:04PM -0300, Marcelo Tosatti wrote:
+static int kvm_unmap_rmapp(struct kvm *kvm, unsigned long *rmapp)
+{
+ u64 *spte;
+ int need_tlb_flush = 0;
+
+ while ((spte = rmap_next(kvm, rmapp, NULL))) {
[EMAIL PROTECTED], [EMAIL PROTECTED]
Bcc:
Subject: [RFC][PATCH] VMX: Add and enhance VMentry failure detection
mechanism
Reply-To:
This patch is *not* meant to be merged. This patch fixes the random
crashes with gfxboot and it doesn't crash anymore at random
instructions.
It mainly does
Please ignore this messed up e-mail, Sorry!
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Fri, Jul 25, 2008 at 04:26:39PM +0200, Andrea Arcangeli wrote:
This allows the mmu notifier code to run unalias_gfn with only the
mmu_lock held. Only alias writes need the mmu_lock held. Readers will
either take the slots_lock in read mode or the mmu_lock.
Signed-off-by: Andrea Arcangeli
On Fri, Jul 25, 2008 at 04:32:03PM +0200, Andrea Arcangeli wrote:
This allows reading memslots with only the mmu_lock hold for mmu
notifiers that runs in atomic context and with mmu_lock held.
Compared to previous versions I had to move this:
- if (mem-slot = kvm-nmemslots)
-
On Mon, Jul 28, 2008 at 06:51:50PM -0300, Marcelo Tosatti wrote:
Looks good.
Cool, thanks for the review of the three patches! Now I only hope
Andrew will post his -mm patches to Linus without waiting any further.
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a
37 matches
Mail list logo
