Anthony Liguori anth...@codemonkey.ws writes:
- any additional input on probed_raw?
Isn't it a fait accompli? I stopped providing input when commit
79368c81 appeared.
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More
hi all,
i just started learning kvm and i want to get a clear way to learn it. i know
that qemu uses ioctl to control vm. so i want to know the code entry of create
cpu/memory of vm in qemu. in which file can i find them and get a clear
understanding of it. any help will be appreciated.
Hello,
On 07/26/2010 09:57 PM, Michael S. Tsirkin wrote:
For freeze, it probably is okay but for stop, I think it's better to
keep the semantics straight forward.
What are the semantics then? What do we want stop followed
by queue and flush to do?
One scenario I can think of is the
Hello,
On 07/26/2010 10:19 PM, Michael S. Tsirkin wrote:
Let's try to define what do we want to achieve then. Do you want
code that flushes workers not to block when workers are frozen? How
will we handle work submitted when worker is frozen?
As I wrote earlier, it's not necessarily about
in qemu/vl.c function main calls qemu_main,
int main(int argc, char **argv)
{
qemu_main(argc, argv, NULL);
}
but there is no implementation of qemu_main() found.
where is the entry
point?N§²æìr¸yúèØb²X¬¶Ç§vØ^)Þº{.nÇ+·¤¾h§¶¡Ü¨}©²Æ zÚj:+v¨¾«êçzZ+Ê+zf£¢·h§~Ûiÿûàz¹
Hi list
I did some KVM testing with help from Alexander Graf and Chris Wright
back in March, trying to passthrough various USB 2.0 PCI cards and
onboard Intel USB hubs. I never got it to work completely, I ended up
with some timing issues or similar, causing artifacts in the picture
from a
I've been searching for howto on this but all the guides/docs I've
found seem to assume that we would want to either convert from an
existing VMWare/Xen VM or install a whole new VM.
So my question is: is it possible to create an image of a running
physical machine and then start it on another
On 07/26/2010 11:47 AM, Andre Przywara wrote:
Does this go away with CONFIG_DEBUG_RODATA=n? If so, it's a known
bug in the atomic_*() clobber lists.
Unfortunately the bug persists even with CONFIG_DEBUG_RODATA disabled.
The debug options I had enabled now are:
CONFIG_DEBUG_DEVRES=y
On 07/26/2010 08:58 PM, ewheeler wrote:
O
n 07/26/2010 07:01 PM, Neo Jia wrote:
hi,
I am seeing an unhandled vm exit: 0x11 on Win7 with KVM-88 release and
wondering if I am still able to dump the code from guest OS when this
happens. But it looks that all instructions are 0s after adding one
On Mon, Jul 26, 2010 at 05:28:21PM -0500, Anthony Liguori wrote:
On 07/26/2010 04:28 PM, Chris Wright wrote:
Please send in any agenda items you are interested in covering.
- 0.13 update
I'll pre-empt the 0.13 question with an answer. I'm just testing the
VNC changes and if all
Avi Kivity wrote:
On 07/26/2010 11:47 AM, Andre Przywara wrote:
Does this go away with CONFIG_DEBUG_RODATA=n? If so, it's a known
bug in the atomic_*() clobber lists.
Unfortunately the bug persists even with CONFIG_DEBUG_RODATA disabled.
The debug options I had enabled now are:
On 07/27/2010 02:49 PM, Andre Przywara wrote:
What is the guest executing when it hangs?
Both VCPUs are halted, the monitor and System.map tell me it's in
native_safe_halt().
The code sequence confirms this, it is an intentional sti;hlt condition.
Using -smp 16 also shows that all 16 VCPUs
Avi Kivity wrote:
On 07/27/2010 02:49 PM, Andre Przywara wrote:
What is the guest executing when it hangs?
Both VCPUs are halted, the monitor and System.map tell me it's in
native_safe_halt().
The code sequence confirms this, it is an intentional sti;hlt condition.
Using -smp 16 also shows
On 07/27/2010 03:21 PM, Andre Przywara wrote:
Avi Kivity wrote:
On 07/27/2010 02:49 PM, Andre Przywara wrote:
What is the guest executing when it hangs?
Both VCPUs are halted, the monitor and System.map tell me it's in
native_safe_halt().
The code sequence confirms this, it is an
On 07/27/2010 02:19 AM, Markus Armbruster wrote:
Anthony Liguorianth...@codemonkey.ws writes:
- any additional input on probed_raw?
Isn't it a fait accompli? I stopped providing input when commit
79368c81 appeared.
No. 79368c81 was to close the security hole (and I do
On Tue, 2010-07-20 at 09:35 +0800, Amos Kong wrote:
The kvm_net_utils.py is a just a place that wraps common network
related commands which is used to do the network-related tests.
Use -1 as the packet ratio for loss analysis.
Use quiet mode when doing the flood ping.
Signed-off-by: Jason
On Tue, 2010-07-20 at 09:35 +0800, Amos Kong wrote:
This test use ping to check the virtual nics, it contains two kinds of test:
1. Packet loss ratio test, ping the guest with different size of packets.
2. Stress test, flood ping guest then use ordinary ping to test the network.
The interval
This patchset changes interrupt injection to be done from normal process
context instead of interrupts disabled context. This is useful for real
mode interrupt injection on Intel without the current hacks (injecting as
a software interrupt of a vm86 task), reducing latencies, and later, for
Change the interrupt injection code to work from preemptible, interrupts
enabled context. This works by adding a -cancel_injection() operation
that undoes an injection in case we were not able to actually enter the guest
(this condition could never happen with atomic injection).
Signed-off-by:
This allows reuse of vmx_complete_interrupts() for cancelling injections.
Signed-off-by: Avi Kivity a...@redhat.com
---
arch/x86/kvm/vmx.c |9 ++---
1 files changed, 6 insertions(+), 3 deletions(-)
diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
index 7483da7..738b21f 100644
---
No code changes.
Signed-off-by: Avi Kivity a...@redhat.com
---
arch/x86/kvm/vmx.c | 47 +++
1 files changed, 23 insertions(+), 24 deletions(-)
diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
index 4122baa..7686a7a 100644
---
vmx_complete_interrupts() does too much, split it up:
- vmx_vcpu_run() gets the cache important vmcs fields part
- a new vmx_complete_atomic_exit() gets the parts that must be done atomically
- a new vmx_recover_nmi_blocking() does what its name says
- vmx_complete_interrupts() retains the
Instead of blindly attempting to inject an event before each guest entry,
check for a possible event first in vcpu-requests. Sites that can trigger
event injection are modified to set KVM_REQ_EVENT:
- interrupt, nmi window opening
- ppr updates
- i8259 output changes
- local apic irr changes
-
Currently vmx_complete_interrupts() can decode event information from vmx
exit fields into the generic kvm event queues. Make it able to decode
the information from the entry fields as well by parametrizing it.
Signed-off-by: Avi Kivity a...@redhat.com
---
arch/x86/kvm/vmx.c | 34
On 07/27/10 02:13, Alex Williamson wrote:
On Mon, 2010-07-26 at 18:28 -0500, Anthony Liguori wrote:
On 07/26/2010 05:28 PM, Anthony Liguori wrote:
On 07/26/2010 04:28 PM, Chris Wright wrote:
Please send in any agenda items you are interested in covering.
- 0.13 update
I'll pre-empt the
Am 27.07.2010 15:00, schrieb Anthony Liguori:
On 07/27/2010 02:19 AM, Markus Armbruster wrote:
Anthony Liguorianth...@codemonkey.ws writes:
- any additional input on probed_raw?
Isn't it a fait accompli? I stopped providing input when commit
79368c81 appeared.
No.
On 07/27/2010 06:51 AM, Daniel P. Berrange wrote:
On Mon, Jul 26, 2010 at 05:28:21PM -0500, Anthony Liguori wrote:
On 07/26/2010 04:28 PM, Chris Wright wrote:
Please send in any agenda items you are interested in covering.
- 0.13 update
I'll pre-empt the 0.13 question
On 07/27/2010 09:30 AM, Anthony Liguori wrote:
On 07/27/2010 06:51 AM, Daniel P. Berrange wrote:
On Mon, Jul 26, 2010 at 05:28:21PM -0500, Anthony Liguori wrote:
On 07/26/2010 04:28 PM, Chris Wright wrote:
Please send in any agenda items you are interested in covering.
-
Avi Kivity wrote:
On 07/27/2010 03:21 PM, Andre Przywara wrote:
Avi Kivity wrote:
On 07/27/2010 02:49 PM, Andre Przywara wrote:
What is the guest executing when it hangs?
Both VCPUs are halted, the monitor and System.map tell me it's in
native_safe_halt().
The code sequence confirms
On 07/27/2010 04:48 PM, Andre Przywara wrote:
Wierd. Maybe the clock goes crazy.
Let's see if it jumps forward alot:
} while (unlikely(last != ret));
+
+ {
+static u64 last_report;
+if (ret last_report + 1) {
+last_report = ret;
On Tue, 2010-07-20 at 09:35 +0800, Amos Kong wrote:
According to different nic model set different MTU for it. And ping from guest
to host, to see whether tested size can be received by host.
Signed-off-by: Jason Wang jasow...@redhat.com
Signed-off-by: Amos Kong ak...@redhat.com
---
0
On Tue, 2010-07-20 at 09:35 +0800, Amos Kong wrote:
This test is the basic test of transfering file between host and guest. Try to
transfer a large file from host to guest, and transfer it back to host, then
compare the files by diff command.
The default file size is 4000M, scp timeout is
Avi Kivity wrote:
On 07/27/2010 04:48 PM, Andre Przywara wrote:
Wierd. Maybe the clock goes crazy.
Let's see if it jumps forward alot:
} while (unlikely(last != ret));
+
+ {
+static u64 last_report;
+if (ret last_report + 1) {
+
0.13
- -rc0 tagged, propagating now
- no more features, bug fix only
- although a few things, like shared memory device, are still feasible
qemu64 cpu model
- currently model 2
- this cpu simply does not exist at all in the real world
- model 13 or higher windows 32bit will enable MSI/-X
Kevin Wolf kw...@redhat.com writes:
Am 27.07.2010 15:00, schrieb Anthony Liguori:
On 07/27/2010 02:19 AM, Markus Armbruster wrote:
Anthony Liguorianth...@codemonkey.ws writes:
- any additional input on probed_raw?
Isn't it a fait accompli? I stopped providing input when commit
On 07/27/2010 10:22 AM, Markus Armbruster wrote:
Kevin Wolfkw...@redhat.com writes:
Am 27.07.2010 15:00, schrieb Anthony Liguori:
On 07/27/2010 02:19 AM, Markus Armbruster wrote:
Anthony Liguorianth...@codemonkey.ws writes:
- any additional input on
On Tue, Jul 27, 2010 at 10:28:04AM -0500, Anthony Liguori wrote:
On 07/27/2010 10:22 AM, Markus Armbruster wrote:
Kevin Wolfkw...@redhat.com writes:
Am 27.07.2010 15:00, schrieb Anthony Liguori:
On 07/27/2010 02:19 AM, Markus Armbruster wrote:
Anthony
On Mon, Jul 26, 2010 at 08:08:34PM +0200, Oleg Nesterov wrote:
On 07/26, Sridhar Samudrala wrote:
I have been testing out a similar patch that uses kernel_thread() without
CLONE_FILES
flag rather than create_kthread() and then closing the files.
!CLONE_FILES can't help. copy_files()
This patch fixes a bug in a nested hypervisor that heavily
switches between real-mode and long-mode. The problem is
fixed by syncing back efer into the guest vmcb on emulated
vmexit.
Signed-off-by: Joerg Roedel joerg.roe...@amd.com
---
arch/x86/kvm/svm.c |1 +
1 files changed, 1
Hi Avi, Marcelo,
here are two small patches for kvm-amd. The first patch fixes a small bug in
nested svm efer handling. The second patch implements emulation for the
next_rip feature.
Regards,
Joerg
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a
This patch implements the emulations of the svm next_rip
feature in the nested svm implementation in kvm.
Signed-off-by: Joerg Roedel joerg.roe...@amd.com
---
arch/x86/kvm/svm.c |8 +++-
1 files changed, 7 insertions(+), 1 deletions(-)
diff --git a/arch/x86/kvm/svm.c
On 07/27/2010 06:28 PM, Anthony Liguori wrote:
If we add docs/deprecated-features.txt, schedule removal for at least
1 year in the future, and put a warning in the code that prints
whenever raw is probed, I think I could warm up to this.
Since libvirt should be insulating users from this
On Tue, Jul 27, 2010 at 07:17:06PM +0300, Avi Kivity wrote:
On 07/27/2010 06:28 PM, Anthony Liguori wrote:
If we add docs/deprecated-features.txt, schedule removal for at least
1 year in the future, and put a warning in the code that prints
whenever raw is probed, I think I could warm up
* Daniel P. Berrange (berra...@redhat.com) wrote:
On Tue, Jul 27, 2010 at 07:17:06PM +0300, Avi Kivity wrote:
On 07/27/2010 06:28 PM, Anthony Liguori wrote:
If we add docs/deprecated-features.txt, schedule removal for at least
1 year in the future, and put a warning in the code that
On 07/27/2010 07:29 PM, Chris Wright wrote:
QEMU stderr+out is already recorded in /var/lib/libvirt/qemu/$GUESTNAME.log
along with the env variables and argv used to spawn it. Or did you mean
provide an API + virsh command /virt-manager UI for accessing the logs ?
I read that to
* Avi Kivity (a...@redhat.com) wrote:
On 07/27/2010 07:29 PM, Chris Wright wrote:
QEMU stderr+out is already recorded in /var/lib/libvirt/qemu/$GUESTNAME.log
along with the env variables and argv used to spawn it. Or did you mean
provide an API + virsh command /virt-manager UI for accessing
On 07/27/2010 07:36 PM, Chris Wright wrote:
If things work there's no reason for the user to go look at the
logs. An exclamation point invites clicking.
Even better would be an ABRT plugin, so if something goes
(marginally) wrong, the siren pops up and you're invited to report
the bug.
On Tue, Jul 27, 2010 at 09:29:13AM -0700, Chris Wright wrote:
* Daniel P. Berrange (berra...@redhat.com) wrote:
On Tue, Jul 27, 2010 at 07:17:06PM +0300, Avi Kivity wrote:
On 07/27/2010 06:28 PM, Anthony Liguori wrote:
If we add docs/deprecated-features.txt, schedule removal for at
On 07/27/2010 07:42 PM, Daniel P. Berrange wrote:
I read that to mean...propagate stderr from qemu to be right in front of
the user. So that's output from virsh or in virt-manager. Trouble is,
that's only useful (at best) when starting a guest. Perhaps some
virt-manager thing (an
On 07/27/2010 07:47 PM, Avi Kivity wrote:
On 07/27/2010 07:42 PM, Daniel P. Berrange wrote:
I read that to mean...propagate stderr from qemu to be right in
front of
the user. So that's output from virsh or in virt-manager. Trouble is,
that's only useful (at best) when starting a guest.
resend for bug fix related to removal of irqfd
Support an inter-vm shared memory device that maps a shared-memory object as a
PCI device in the guest. This patch also supports interrupts between guest by
communicating over a unix domain socket. This patch applies to the qemu-kvm
repository.
On Tue, Jul 27, 2010 at 07:42:34PM +0300, Avi Kivity wrote:
On 07/27/2010 07:36 PM, Chris Wright wrote:
If things work there's no reason for the user to go look at the
logs. An exclamation point invites clicking.
Even better would be an ABRT plugin, so if something goes
(marginally)
On 07/27/2010 08:01 PM, Daniel P. Berrange wrote:
It's annoying to us old hands, but it does give that nice integrated
system feel that we're missing, and it works even if virt-manager is in
the background (or if you don't use virt-manager at all).
Given that there's a kerneloops pluging
On 07/27/2010 07:14 PM, Joerg Roedel wrote:
This patch implements the emulations of the svm next_rip
feature in the nested svm implementation in kvm.
Signed-off-by: Joerg Roedeljoerg.roe...@amd.com
---
arch/x86/kvm/svm.c |8 +++-
1 files changed, 7 insertions(+), 1 deletions(-)
On 07/27/2010 07:14 PM, Joerg Roedel wrote:
This patch fixes a bug in a nested hypervisor that heavily
switches between real-mode and long-mode. The problem is
fixed by syncing back efer into the guest vmcb on emulated
vmexit.
This is vmware? IIRC their old kernel was 32-bit, so they need to
On Mon, Jul 26, 2010 at 09:31:58PM +0200, Tejun Heo wrote:
Hello,
On 07/26/2010 09:14 PM, Tejun Heo wrote:
On 07/26/2010 06:51 PM, Michael S. Tsirkin wrote:
I noticed that with vhost, flush_work was getting the worker
pointer as well. Can we live with this API change?
Yeah, the
qemu-kvm-0.12.5 is now available. This release is based on the
upstream qemu 0.12.5, plus kvm-specific enhancements. Please see the
original qemu 0.12.5 release announcement for details.
This release can be used with the kvm kernel modules provided by your
distribution kernel, or by the
Sridhar,
I pushed a patchset with all known issues fixed,
on my vhost-net-next branch.
For now this ignores the cpu mask issue, addressing
only the cgroups issue.
Would appreciate testing and reports.
Thanks,
--
MST
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of
On 2010-07-26 20:59, Arjan Koers wrote:
I ran into the same problem. 2.6.34.1 and 2.6.35-rc6 SMP guest
kernels hang during boot.
It appears that last is way ahead of ret twice.
The kernel boots with this debug patch that makes the clock go
backwards if the difference is big:
last =
On Sun, Jul 25, 2010 at 02:39:43PM +0300, Avi Kivity wrote:
The pusha tests fail on AMD, which virtualizes real mode correctly. Fix
the tests.
Avi Kivity (3):
test: realmode: fix pusha test
test: realmode: initialize all bits of esp
test: realmode: fix pusha test stack
On Fri, Jul 23, 2010 at 03:47:18PM -0600, Alex Williamson wrote:
When supported by the host kernel, we can use read/write on the
PCI sysfs resource file for I/O port regions. This allows us to
avoid raw in/out commands and works with deprivileged guests via
libvirt.
Signed-off-by: Alex
On Fri, Jul 23, 2010 at 12:59:49PM +0800, Xiao Guangrong wrote:
Separate expect status updates operation, later we can just modify the access
way(i,e the AC_ACCESS_* flags)
Signed-off-by: Xiao Guangrong xiaoguangr...@cn.fujitsu.com
---
kvm/test/x86/access.c | 131
Andre Przywara wrote:
Avi Kivity wrote:
On 07/27/2010 04:48 PM, Andre Przywara wrote:
Wierd. Maybe the clock goes crazy.
Let's see if it jumps forward alot:
} while (unlikely(last != ret));
+
+ {
+static u64 last_report;
+if (ret last_report +
Gleb Natapov wrote:
On Wed, Jul 21, 2010 at 09:25:31AM +0300, Harri Olin wrote:
Gleb Natapov kirjoitti:
On Mon, Jul 19, 2010 at 10:17:02AM +0300, Harri Olin wrote:
Gleb Natapov kirjoitti:
On Thu, Jul 15, 2010 at 03:19:44PM +0200, Christoph Adomeit wrote:
But one Windows 2008 64 Bit Server
[ Sorry for the long hiatus, I've been wrapped up in other issues.]
I think the fundamental issue to resolve is to decide on the model which the
VFIO driver presents to its users.
Fundamentally, VFIO as part of the OS must protect the system from its users
and also protect the users from each
This adds a unit test for real mode emulation of the iret instruction
Signed-off-by: Mohammed Gamal m.gamal...@gmail.com
---
kvm/test/x86/realmode.c | 23 +++
1 files changed, 23 insertions(+), 0 deletions(-)
diff --git a/kvm/test/x86/realmode.c b/kvm/test/x86/realmode.c
Ths patch adds IRET instruction (opcode 0xcf).
Currently, only IRET in real mode is emulated. Protected mode support is to be
added later if needed.
Signed-off-by: Mohammed Gamal m.gamal...@gmail.com
Changes from v1:
- Corrected handling of eflags
---
arch/x86/kvm/emulate.c | 69
This adds a unit test for real mode emulation of the iret instruction
Signed-off-by: Mohammed Gamal m.gamal...@gmail.com
---
kvm/test/x86/realmode.c | 23 +++
1 files changed, 23 insertions(+), 0 deletions(-)
diff --git a/kvm/test/x86/realmode.c b/kvm/test/x86/realmode.c
On Tue, Jul 27, 2010 at 03:13:14PM -0700, Tom Lyon wrote:
[ Sorry for the long hiatus, I've been wrapped up in other issues.]
I think the fundamental issue to resolve is to decide on the model which the
VFIO driver presents to its users.
Fundamentally, VFIO as part of the OS must protect
On Tue, 2010-07-27 at 23:42 +0300, Michael S. Tsirkin wrote:
Sridhar,
I pushed a patchset with all known issues fixed,
on my vhost-net-next branch.
For now this ignores the cpu mask issue, addressing
only the cgroups issue.
Would appreciate testing and reports.
I had to apply the
On Tue, Jul 27, 2010 at 05:41:41PM -0700, Sridhar Samudrala wrote:
On Tue, 2010-07-27 at 23:42 +0300, Michael S. Tsirkin wrote:
Sridhar,
I pushed a patchset with all known issues fixed,
on my vhost-net-next branch.
For now this ignores the cpu mask issue, addressing
only the cgroups
Sridhar, David,
I pushed a mergeable buffers patchset on my vhost-net-next branch,
on top of the threading changes.
This is a minimal patch, which in my testing has zero impact on
non-mergeable path.
Please give this a spin and let me know.
Thanks!
--
MST
--
To unsubscribe from this list:
On Wed, Jul 28, 2010 at 04:27:35AM +0300, Michael S. Tsirkin wrote:
Sridhar, David,
I pushed a mergeable buffers patchset on my vhost-net-next branch,
on top of the threading changes.
This is a minimal patch, which in my testing has zero impact on
non-mergeable path.
Please give this a
On 07/27/2010 11:51 AM, Andre Przywara wrote:
Andre Przywara wrote:
Avi Kivity wrote:
On 07/27/2010 04:48 PM, Andre Przywara wrote:
Wierd. Maybe the clock goes crazy.
Let's see if it jumps forward alot:
} while (unlikely(last != ret));
+
+ {
+static u64
On 07/28/2010 02:06 AM, Mohammed Gamal wrote:
Ths patch adds IRET instruction (opcode 0xcf).
Currently, only IRET in real mode is emulated. Protected mode support is to be
added later if needed.
@@ -1778,6 +1778,69 @@ static int emulate_popa(struct x86_emulate_ctxt *ctxt,
return rc;
On 07/28/2010 02:22 AM, Mohammed Gamal wrote:
This adds a unit test for real mode emulation of the iret instruction
Signed-off-by: Mohammed Gamalm.gamal...@gmail.com
---
kvm/test/x86/realmode.c | 23 +++
1 files changed, 23 insertions(+), 0 deletions(-)
diff --git
On 07/28/2010 07:21 AM, Avi Kivity wrote:
On 07/28/2010 02:22 AM, Mohammed Gamal wrote:
This adds a unit test for real mode emulation of the iret instruction
Signed-off-by: Mohammed Gamalm.gamal...@gmail.com
---
kvm/test/x86/realmode.c | 23 +++
1 files changed, 23
77 matches
Mail list logo
