- Ryan Harper ry...@us.ibm.com wrote:
The wiki documents[1] object addressing quite well, but we should
include it in the example config file as well.
1.
http://www.linux-kvm.org/page/KVM-Autotest/Parameters#Addressing_objects_.28VMs.2C_images.2C_NICs_etc.29
--
Ryan Harper
Hi, guys
I am trying to mange my KVM VM by libvirt, but I get troubles. If you
have the experience, can you have a look about my issue?
Before I send out this email, I already search libvirt.org and google it, No
useful content found.
If you have a step by step document or you know the
Gerd Hoffmann wrote:
Izik Eidus wrote:
The main problem that ksm will face when removing the fd interface is:
right now when you register memory into ksm, you open fd, and then ksm
do get_task_mm(), we will do mmput when the file will be closed
Did you test whenever it really cleans
Avi Kivity wrote:
There is no choice. Exiting from the guest to the kernel to userspace
is prohibitively expensive, you can't do that on every packet.
I didn't look at virtio-net very closely yet. I wonder why the
notification is that a big issue though. It is easy to keep the number
of
Gerd Hoffmann wrote:
Avi Kivity wrote:
There is no choice. Exiting from the guest to the kernel to userspace
is prohibitively expensive, you can't do that on every packet.
I didn't look at virtio-net very closely yet. I wonder why the
notification is that a big issue though. It is
Sheng Yang wrote:
tip is still broken for me, did a fix go in for this?
Yes. The fix have already been picked up by Avi, please wait a while for push.
Currently my queue is broken due to some qemu display regression. You
can find my queue in the 'pending' branch on kernel.org.
--
Kumar, Venkat wrote:
Thanks for the reply.
I had wrong understanding that Qemu runs in Guest.
But now I understand that *ioctl(fd, KVM_RUN, 0);* will tell KVM to
load the guest and whenever there is an exception in the guest, KVM
traps it and executes the host code post ioctl depending
Izik Eidus wrote:
Gerd Hoffmann wrote:
Did you test whenever it really cleans up in case you kill -9 qemu?
I recently did something simliar with the result that the extra
reference hold on mm_struct prevented the process memory from being
zapped ...
cheers,
Gerd
Did you use mmput()
Check shared ring status when stuffing a request. If there are requests
That means you're bouncing cache lines all the time. Probably not a big
issue on single socket but could be on larger systems.
-Andi
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message
Gerd Hoffmann wrote:
Avi Kivity wrote:
There is no choice. Exiting from the guest to the kernel to userspace
is prohibitively expensive, you can't do that on every packet.
I didn't look at virtio-net very closely yet. I wonder why the
notification is that a big issue though. It
I'm wondering about something i suggested many moons ago: to look
into the KVM decoder+emulator (arch/x86/kvm/x86_emulate.c).
Hi Ingo,
Me and Masami just discussed this a few emails ago in this thread:)
-Andi
--
a...@linux.intel.com -- Speaking for myself only.
--
To unsubscribe from this
On Fri, Apr 03, 2009 at 01:18:54PM +0200, Andi Kleen wrote:
Check shared ring status when stuffing a request. If there are requests
That means you're bouncing cache lines all the time. Probably not a big
issue on single socket but could be on larger systems.
If the backend is running on a
Gregory Haskins wrote:
Yes, but the important thing to point out is it doesn't *replace*
PCI. It simply an alternative.
Does it offer substantial benefits over PCI? If not, it's just extra
code.
First of all, do you think I would spend time designing it if I didn't
think so?
Herbert Xu wrote:
On Fri, Apr 03, 2009 at 02:03:45PM +0300, Avi Kivity wrote:
If the host is able to consume a request immediately, and the guest is
not able to batch requests, this breaks down. And that is the current
situation.
Hang on, why is the host consuming the request
Andi Kleen wrote:
Check shared ring status when stuffing a request. If there are requests
That means you're bouncing cache lines all the time. Probably not a big
issue on single socket but could be on larger systems.
That's why I'd like requests to be handled on the vcpu thread
On Fri, Apr 03, 2009 at 02:46:04PM +0300, Avi Kivity wrote:
The host writes the packet to tap, at which point it is consumed from
its point of view. The host would like to mention that if there was an
API to notify it when the packet was actually consumed, then it would
gladly use it.
Hallo,
as I want to switch from XEN to KVM I've made some performance tests
to see if KVM is as peformant as XEN. But tests with a VMU that receives
a streamed video, adds a small logo to the video and streams it to a
client
have shown that XEN performs much betten than KVM.
In XEN the vlc
2009/4/3 Ingo Molnar mi...@elte.hu:
* Avi Kivity a...@redhat.com wrote:
Ingo Molnar wrote:
kvm has three requirements not needed by kprobes:
- it wants to execute instructions, not just decode them, including
generating faults where appropriate
- it is performance critical
- it needs to
Gregory Haskins wrote:
Avi Kivity wrote:
Gregory Haskins wrote:
So again, I am proposing for consideration of accepting my work (either
in its current form, or something we agree on after the normal review
process) not only on the basis of the future development of the
platform, but
Avi Kivity wrote:
Ingo Molnar wrote:
ok, the structure and concept looks quite good now, really nice!
I'm wondering about something i suggested many moons ago: to look into
the KVM decoder+emulator (arch/x86/kvm/x86_emulate.c).
I remember there were some issues with that (one problem being
* Masami Hiramatsu mhira...@redhat.com wrote:
Hmm, I'd like to know actually kvm aims to emulate all kinds of
instructions. If so, I might find some bugs in x86_emulate.c.
However, I don't know all bugs. To find all of them, we have to
port x86_emulate.c to user-space, decode binaries
Masami Hiramatsu wrote:
Hmm, I'd like to know actually kvm aims to emulate all kinds of
instructions.
We're less interested in fpu/sse. The interesting instructions are
those used for page table management, mmio, and real mode execution.
If so, I might find some bugs in x86_emulate.c.
Hi Avi,
I think we have since covered these topics later in the thread, but in
case you wanted to know my thoughts here:
Avi Kivity wrote:
Gregory Haskins wrote:
Yes, but the important thing to point out is it doesn't *replace*
PCI. It simply an alternative.
Does it offer
The cpuTime of a VM reported by kvm72 is ok (real seconds ) while
that reported by kvm-84 is not
Are you aware of this . Was it fixed in latest kvm releases since 84 ?
I access couTime via libvirt . (same version in both cases) .
thanks
Zvi Dubitzky
Virtualization and System
Gregory Haskins wrote:
I'll rephrase. What are the substantial benefits that this offers
over PCI?
Simplicity and optimization. You don't need most of the junk that comes
with PCI. Its all overhead and artificial constraints. You really only
need things like a handful of hypercall
Add following APIs for accessing registers and stack entries from pt_regs.
- query_register_offset(const char *name)
Query the offset of name register.
- query_register_name(unsigned offset)
Query the name of register by its offset.
- get_register(struct pt_regs *regs, unsigned offset)
* Gerd Hoffmann (kra...@redhat.com) wrote:
mmput() call was in -release() callback, -release() in turn never was
called because the kernel didn't zap the mappings because of the
reference ...
Don't have this issue. That mmput() is not tied to zapping mappings,
rather zapping files. IOW, I
Avi Kivity wrote:
Gregory Haskins wrote:
Avi Kivity wrote:
Gregory Haskins wrote:
So again, I am proposing for consideration of accepting my work
(either
in its current form, or something we agree on after the normal review
process) not only on the basis of the future development of
You should ask about this on the libvirt mailing list and IRC channel,
not here.
That said, a few quick points:
1. the libvirt you're running is very old.
2. you might consider setting the emulator to point to a shell script
which records the command line it's called with to a file before
Avi Kivity wrote:
Cam Macdonell wrote:
I think there is value for static memory sharing. It can be used for
fast, simple synchronization and communication between guests (and the
host) that use need to share data that needs to be updated frequently
(such as a simple cache or notification
Ingo Molnar wrote:
* Masami Hiramatsu mhira...@redhat.com wrote:
Hmm, I'd like to know actually kvm aims to emulate all kinds of
instructions. If so, I might find some bugs in x86_emulate.c.
However, I don't know all bugs. To find all of them, we have to
port x86_emulate.c to user-space,
Anyone has experience to assign PCI-E based InfiniBand card to
guest OS(RHEL5U2 with kernel 2.6.18-92) on latest AMD with IOMMU
support. Host OS has kernel 2.6.29.
Steps I used:
$ echo -n 8086 10de /sys/bus/pci/drivers/pci-stub/new_id
$ echo -n :00:19.0
* Gregory Haskins (ghask...@novell.com) wrote:
Let me ask you this: If you had a clean slate and were designing a
hypervisor and a guest OS from scratch: What would you make the bus
look like?
Well, virtio did have a relatively clean slate. And PCI (as _one_
transport option) is what it
* Eric Liu (ericliu2...@hotmail.com) wrote:
Anyone has experience to assign PCI-E based InfiniBand card to
guest OS(RHEL5U2 with kernel 2.6.18-92) on latest AMD with IOMMU
support. Host OS has kernel 2.6.29.
Steps I used:
$ echo -n 8086 10de /sys/bus/pci/drivers/pci-stub/new_id
$ echo
On Fri, 2009-04-03 at 12:02 -0400, Masami Hiramatsu wrote:
Ensure safeness of inserting kprobes by checking whether the specified
address is at the first byte of a instruction. This is done by decoding
probed function from its head to the probe point.
changes from v4:
- change a comment
Here are the exact steps I used:
1. lspci -n on host:
06:00.0 0c06: 15b3:634a (rev a0)
I want to assign this device to guest.
2. Uninstall driver for this device.
3. Unbind device with the following commands:
echo 15b3 634a /sys/bus/pci/drivers/pci-stub/new_id
echo
On Fri, 2009-04-03 at 12:55 -0400, Masami Hiramatsu wrote:
Ingo Molnar wrote:
* Masami Hiramatsu mhira...@redhat.com wrote:
Hmm, I'd like to know actually kvm aims to emulate all kinds of
instructions. If so, I might find some bugs in x86_emulate.c.
However, I don't know all bugs. To
Avi Kivity wrote:
Gregory Haskins wrote:
I'll rephrase. What are the substantial benefits that this offers
over PCI?
Simplicity and optimization. You don't need most of the junk that comes
with PCI. Its all overhead and artificial constraints. You really only
need things like a
Chris Wright wrote:
* Gregory Haskins (ghask...@novell.com) wrote:
Let me ask you this: If you had a clean slate and were designing a
hypervisor and a guest OS from scratch: What would you make the bus
look like?
Well, virtio did have a relatively clean slate. And PCI (as _one_
Jim Keniston wrote:
On Fri, 2009-04-03 at 12:02 -0400, Masami Hiramatsu wrote:
Ensure safeness of inserting kprobes by checking whether the specified
address is at the first byte of a instruction. This is done by decoding
probed function from its head to the probe point.
changes from v4:
-
On Thursday 02 April 2009 18:58:26 you wrote:
It is my understanding that you need vt-d/iommu support. I didn't think any
existing amd chipsets had iommu support. You may want to look into that.
Hi Brian,
thanks for you response.
I found a tool [1] from Intel to disable the Boot ROM on the
On Tue, 2009-03-17 at 11:50 +0800, Sheng Yang wrote:
This framework can be easily extended to support device capability, like
MSI/MSI-x.
Sheng,
Are you already looking at adding support for PM and EXP capabilities?
The bnx2 driver is an example that won't claim the device if these
capabilities
The cpuTime of a VM reported by kvm72 is ok (real seconds ) while
that reported by kvm-84 is not
Are you aware of this . Was it fixed in latest kvm releases since 84 ?
I access the cpuTime via libvirt . (same version in both cases) .
thanks
Zvi Dubitzky
Virtualization and System
I'm wondering if we need a spot for device specific fixups for PCI
pass-through. In the example below, I want to expose a single port of
an Intel 82571EB quad port copper NIC to a guest. It works great until
I shutdown the guest, at which point the guest e1000e driver knows by
the device ID
+static struct pt_regs_offset regoffset_table[] = {
^ const
--
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
Excerpts from Ryan Harper's message of Qua Abr 01 12:55:58 -0300 2009:
Wondering if anyone else using kvm-autotest stepmaker has ever seen this
error:
Traceback (most recent call last):
File
/home/rharper/work/git/build/kvm-autotest/client/tests/kvm_runtest_2/stepmaker.
py, line 146, in
x86: kprobes checks safeness of insertion address.
From: Masami Hiramatsu mhira...@redhat.com
Ensure safeness of inserting kprobes by checking whether the specified
address is at the first byte of a instruction. This is done by decoding
probed function from its head to the probe point.
changes
On Tue, 2009-03-17 at 11:50 +0800, Sheng Yang wrote:
+if (*ctrl_word PCI_MSIX_ENABLE) {
+if (assigned_dev_update_msix_mmio(pci_dev) 0) {
+perror(assigned_dev_update_msix_mmio);
+return;
+}
+if (kvm_assign_irq(kvm_context,
- Eduardo Habkost ehabk...@raisama.net wrote:
Excerpts from Ryan Harper's message of Qua Abr 01 12:55:58 -0300
2009:
Wondering if anyone else using kvm-autotest stepmaker has ever seen
this
error:
Traceback (most recent call last):
File
Roland McGrath wrote:
+static struct pt_regs_offset regoffset_table[] = {
^ const
Oops, exactly.
Perhaps, I need to update insn.c to make bitmap tables
static const too.
Thank you,
--
Masami Hiramatsu
Software Engineer
Hitachi Computer Products (America) Inc.
Software Solutions
This patch fixes the following issue:
Excerpts from Eduardo Habkost's message of Fri Apr 03 17:37:56 -0300 2009:
Excerpts from Ryan Harper's message of Wed Apr 01 12:55:58 -0300 2009:
Wondering if anyone else using kvm-autotest stepmaker has ever seen this
error:
Traceback (most recent
On Tue, Mar 24, 2009 at 11:47:33AM +0200, Avi Kivity wrote:
index 2ea8262..48169d7 100644
--- a/arch/x86/kvm/x86.c
+++ b/arch/x86/kvm/x86.c
@@ -3109,6 +3109,8 @@ static int vcpu_enter_guest(struct kvm_vcpu *vcpu,
struct kvm_run *kvm_run)
kvm_write_guest_time(vcpu);
Add following APIs for accessing registers and stack entries from pt_regs.
- query_register_offset(const char *name)
Query the offset of name register.
- query_register_name(unsigned offset)
Query the name of register by its offset.
- get_register(struct pt_regs *regs, unsigned offset)
Add x86 instruction decoder to arch-specific libraries. This decoder
can decode all x86 instructions into prefix, opcode, modrm, sib,
displacement and immediates. This can also show the length of
instructions.
changes from v4:
- make bitmap tables static.
Signed-off-by: Jim Keniston
On Tue, Mar 24, 2009 at 04:57:46PM -0500, Ryan Harper wrote:
* Alex Williamson alex.william...@hp.com [2009-03-24 16:07]:
On a 2.6.29, x86_64 host/guest, what's special about specifying a guest
size of -m 3586 when using -mem-path backed by hugetlbfs? 3585 works,
3586 hangs here:
Masami Hiramatsu wrote:
Add x86 instruction decoder to arch-specific libraries. This decoder
can decode all x86 instructions into prefix, opcode, modrm, sib,
displacement and immediates. This can also show the length of
instructions.
changes from v4:
- make bitmap tables static.
Hi Masami,
Hi Peter,
H. Peter Anvin wrote:
Masami Hiramatsu wrote:
Add x86 instruction decoder to arch-specific libraries. This decoder
can decode all x86 instructions into prefix, opcode, modrm, sib,
displacement and immediates. This can also show the length of
instructions.
changes from v4:
-
Bugs item #2729621, was opened at 2009-04-03 21:02
Message generated for change (Tracker Item Submitted) made by byron_clark
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2729621group_id=180599
Please note that this message will contain a full copy of
Bugs item #2729621, was opened at 2009-04-03 21:02
Message generated for change (Comment added) made by byron_clark
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2729621group_id=180599
Please note that this message will contain a full copy of the comment
On Fri, Apr 3, 2009 at 3:32 AM, Hollis Blanchard holl...@us.ibm.com wrote:
(I'll address the MMU issue in a separate mail.)
On Thu, 2009-04-02 at 11:56 -0700, Rahul Kulkarni wrote:
Another potential issue could be the initial environment (described
earlier as option 2) not being what BSD
On Fri, 2009-04-03 at 00:52 +0200, Alexander Graf wrote:
That sounds a lot like what I imlemented for real mode on 970. I
assume the PID is similar to a full SLB context and AS=1/AS=0 is
just
another bit that could as well be in the PID?
Mostly... however, when an interrupt occurs, AS
61 matches
Mail list logo
