Is it expected that qemu-kvm-0.10.x doesn't build/install extboot.bin?
This came up on the IRC channel last night. I would expect it to, but
the person in the IRC channel didn't get extboot.bin from the tarball
and none of the tags of 0.10.x I tried built it either.
--Iggy
--
To unsubscribe
On Wed, 2009-06-10 at 20:27 +0100, Jamie Lokier wrote:
> Michael S. Tsirkin wrote:
> > > I think the right long term answer to all this is a way to get QEMU to
> > > dump it's current machine configuration in glorious detail as a file
> > > which can be reloaded as a machine configuration.
> >
> >
In free_assigned_device, kvm_remove_ioperm_data won't be
called, because the check skips type IORESOURCE_IO. For
IORESOURCE_MEM, it should destroy the registered memory,
otherwise it may be failed to create new memory slot because
it is already there. hot add and hot remove a device several
times c
Following are the differences between version 1:
1) use framework to destroy VMs except the main_vm
2) use snapshot to boot other VMs except the first one
Regards,
Yolkfull
diff --git a/client/tests/kvm/kvm.py b/client/tests/kvm/kvm.py
index 9428162..1f553b4 100644
--- a/client/tests/kvm/kvm.py
On Fri, Jun 12, 2009 at 09:43:29AM +0100, Mark McLoughlin wrote:
> = Solution - Separate configuration from compat hints =
>
> As I suggested before:
>
> - Allow the VM manager to dump compat hints; this would be an opaque
> file format, more like the savevm format than a config file
Why
Hi,
I'm very sorry for crossposting, but I'm not sure whether my problem
is related to libvirt or kvm itself.
I've spent some time testing save/restore and it seems it's still not
really reliable. Starting guest, loading it with some applications
(ie kernel compilation) and saving/restoring it fo
Hi,
I figured out why Windows wasn't booting with the previous version
of the patch. It seems it didn't like the forward declaration of the
_PR.PRSC method.
Instead I found that it does seem to work if I add the calling method
_GRE.L02 in the SSDT, while the rest of the _GRE is declared in the
D
This patch adds the processes_command function to the preprocessor which
will run custom scripts before and after a test is executed.
processes_command will export all test parameters as environmental variables
for passing parameters to a custom script.
processes_command uses parameters defined i
On Fri, 2009-06-12 at 16:59 +0300, Michael S. Tsirkin wrote:
> On Fri, Jun 12, 2009 at 09:43:29AM +0100, Mark McLoughlin wrote:
> > = Solution - Separate configuration from compat hints =
> >
> > As I suggested before:
> >
> > - Allow the VM manager to dump compat hints; this would be an opaque
Mark McLoughlin wrote:
On Wed, 2009-06-10 at 20:27 +0100, Jamie Lokier wrote:
Michael S. Tsirkin wrote:
I think the right long term answer to all this is a way to get QEMU to
dump it's current machine configuration in glorious detail as a file
which can be reloaded as a machine configur
Mark McLoughlin wrote:
On Wed, 2009-06-10 at 20:27 +0100, Jamie Lokier wrote:
= Solution - Separate configuration from compat hints =
As I suggested before:
- Allow the VM manager to dump compat hints; this would be an opaque
file format, more like the savevm format than a config fil
On Fri, 2009-06-12 at 09:51 -0500, Anthony Liguori wrote:
> Mark McLoughlin wrote:
> > On Wed, 2009-06-10 at 20:27 +0100, Jamie Lokier wrote:
> >
> >> Michael S. Tsirkin wrote:
> >>
> I think the right long term answer to all this is a way to get QEMU to
> dump it's current machin
On Fri, 2009-06-12 at 09:55 -0500, Anthony Liguori wrote:
> Mark McLoughlin wrote:
> > On Wed, 2009-06-10 at 20:27 +0100, Jamie Lokier wrote:
> >
> > = Solution - Separate configuration from compat hints =
> >
> > As I suggested before:
> >
> > - Allow the VM manager to dump compat hints; this
Mark McLoughlin wrote:
On Fri, 2009-06-12 at 09:51 -0500, Anthony Liguori wrote:
Mark McLoughlin wrote:
On Wed, 2009-06-10 at 20:27 +0100, Jamie Lokier wrote:
Michael S. Tsirkin wrote:
I think the right long term answer to all this is a way to get QEMU to
dump
The 'autotest' subtest of KVM got broke during the merge, since the new
logging system introduces new line prefixes on the autotest output. This
patch series fixes this subtest. It consists on:
* Fix a a few bad long line breaks
* Make the results parsing based on the status files of the autotes
Mark McLoughlin wrote:
On Fri, 2009-06-12 at 09:55 -0500, Anthony Liguori wrote:
Mark McLoughlin wrote:
On Wed, 2009-06-10 at 20:27 +0100, Jamie Lokier wrote:
= Solution - Separate configuration from compat hints =
As I suggested before:
- Allow the VM manager to dump compat hin
Signed-off-by: Lucas Meneghel Rodrigues
---
client/tests/kvm/kvm_config.py | 14 +++---
client/tests/kvm/kvm_tests.py | 12 ++--
2 files changed, 13 insertions(+), 13 deletions(-)
diff --git a/client/tests/kvm/kvm_config.py b/client/tests/kvm/kvm_config.py
index 95eefcb..343
Changing the names of the control files being used on the autotest test
Signed-off-by: Lucas Meneghel Rodrigues
---
client/tests/kvm/kvm_tests.cfg.sample |5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/client/tests/kvm/kvm_tests.cfg.sample
b/client/tests/kvm/kvm_tes
The 'autotest' kvm subtest was relying on autotest output, that
now has the logging line prefixes. The logging line prefixes
breaks the results parser, so we would either have to make the
parser to strip the logging prefixes or read autotest status
files generated on the results directory. The late
Adding an autotest_control dir with control files that will be
used on the 'autotest' kvm test, with the original control files
used on the old kvm_runtest_2 directory.
Signed-off-by: Lucas Meneghel Rodrigues
---
client/tests/kvm/autotest_control/bonnie.control | 21
cli
That seems very strange ... why do you have to duplicate the existing
control files?
On Fri, Jun 12, 2009 at 9:13 AM, Lucas Meneghel Rodrigues
wrote:
> Adding an autotest_control dir with control files that will be
> used on the 'autotest' kvm test, with the original control files
> used on the o
On Fri, 2009-06-12 at 09:18 -0700, Martin Bligh wrote:
> That seems very strange ... why do you have to duplicate the existing
> control files?
In particular, in the old kvm autotest tree we used to have a control
file, control.60 inside the dbench directory, that specifies a shorter
(60s) run for
On Fri, 2009-06-12 at 11:11 -0500, Anthony Liguori wrote:
> Mark McLoughlin wrote:
> > On Fri, 2009-06-12 at 09:51 -0500, Anthony Liguori wrote:
> >
> >> Mark McLoughlin wrote:
> >>
> >>> On Wed, 2009-06-10 at 20:27 +0100, Jamie Lokier wrote:
> >>>
> >>>
> Michael S. Tsirkin
On Fri, 2009-06-12 at 11:12 -0500, Anthony Liguori wrote:
> Mark McLoughlin wrote:
> > On Fri, 2009-06-12 at 09:55 -0500, Anthony Liguori wrote:
> >
> >> Mark McLoughlin wrote:
> >>
> >>> On Wed, 2009-06-10 at 20:27 +0100, Jamie Lokier wrote:
> >>>
> >>> = Solution - Separate configurati
Mark McLoughlin wrote:
So, when libvirt creates a guest for the first time, it makes a copy of
the device tree and continues to use that even if qemu is upgraded.
That's enough to ensure compat is retained for all built-in devices.
However, in order to retain compat for that SCSI device (e.g. en
On Fri, 2009-06-12 at 12:00 -0500, Anthony Liguori wrote:
> Mark McLoughlin wrote:
> > So, when libvirt creates a guest for the first time, it makes a copy of
> > the device tree and continues to use that even if qemu is upgraded.
> > That's enough to ensure compat is retained for all built-in devi
On 6/12/09, Mark McLoughlin wrote:
> On Fri, 2009-06-12 at 12:00 -0500, Anthony Liguori wrote:
> > Mark McLoughlin wrote:
> > > So, when libvirt creates a guest for the first time, it makes a copy of
> > > the device tree and continues to use that even if qemu is upgraded.
> > > That's enough
On Fri, 2009-06-12 at 20:44 +0300, Blue Swirl wrote:
> If the device has different behavior or different properties from
> guest perspective compared to the old device, it should get a new
> device type so that you could specify in the device tree either the
> old device or the new one.
Yes, that
On Thu, 2009-06-11 at 14:15 +0300, Uri Lublin wrote:
> From: Supriya Kannery
>
> Default is to run each test once.
>
> Just add iterations = N in kvm_tests.cfg to the test(s) you
> want to run multiple times.
>
> Signed-off-by: Supriya Kannery
> Cc : Michael Goldish
> Signed-off-by: Uri Lubli
During the previous week, a significant amount of our backlog was
resolved and now our patch queue is smaller. If I did miss anything,
please let me know. Now we have 6 patches pending, as follows. Please if
you are the patch owner please consider re-working your patch or talk to
me, I can re-work
Hello Charlie,
thanks for the reply
> That should work fine. Your "..." sets up the drives, memory amount,
> etc., right? Why do you say it "doesn't seem to be the proper way"? What
> fails?
sure, I'm (hopefully) providing all the needed arguments.
>
> BTW, you might also do this: -incoming 'e
The performance counter MSRs are different for AMD and Intel CPUs and they
are chosen mainly by the CPUID vendor string. This patch catches writes to
all addresses (regardless of VMX/SVM path) and handles them in the generic
MSR handler routine. Writing a 0 into the event select register is somethi
Nikola Ciprich wrote:
using
... -incoming exec:cat /home/...image.vm
seems to start the machine, but it seems to be stuck, even though I removed -S
parameter.
That may well be a guest issue rather than a qemu migration problem --
I've seen similar difficulties for guests being resumed via in
We have been trying to test qemu-kvm virtual machines under an IO load.
The IO load is quite simple: A timed build of the linux kernel and modules.
I have found that virtual machines take more than twice as long to do this
build as the host. It doesn't seem to matter if I use virtio or not, Using
I've made some changes to the wiki to hopefully improve it's
usefulness. Especially to new kvm users.
I table-ized the management tools page info
I added some links to the main page for commonly used pages (inside
and outside the wiki)
Some of those links duplicate some of the links in the n
Add a user-space selftest of x86 instruction decoder at kernel build time.
When CONFIG_X86_DECODER_SELFTEST=y, Kbuild builds a test harness of x86
instruction decoder and performs it after building vmlinux.
The test compares the results of objdump and x86 instruction decoder
code and check there ar
Ensure safeness of inserting kprobes by checking whether the specified
address is at the first byte of a instruction on x86.
This is done by decoding probed function from its head to the probe point.
Signed-off-by: Masami Hiramatsu
Acked-by: Ananth N Mavinakayanahalli
Cc: Jim Keniston
Cc: Ingo
Add x86 instruction decoder to arch-specific libraries. This decoder
can decode x86 instructions used in kernel into prefix, opcode, modrm,
sib, displacement and immediates. This can also show the length of
instructions.
This version introduces instruction attributes for decoding instructions.
The
Add following APIs for accessing registers and stack entries from pt_regs.
- regs_query_register_offset(const char *name)
Query the offset of "name" register.
- regs_query_register_name(unsigned offset)
Query the name of register by its offset.
- regs_get_register(struct pt_regs *regs, uns
Add kprobes-based event tracer on ftrace.
This tracer is similar to the events tracer which is based on Tracepoint
infrastructure. Instead of Tracepoint, this tracer is based on kprobes(kprobe
and kretprobe). It probes anywhere where kprobes can probe(this means, all
functions body except for __kp
Hi Ingo and Steven,
Here, I'm resending v9 patches, which is just updated for the latest -tip.
Here are the patches of kprobe-based event tracer for x86, version 9,
which allows you to probe various kernel events through ftrace interface.
The tracer supports per-probe filtering which allows you t
Add dynamic ftrace_event_call support to ftrace. Trace engines can adds new
ftrace_event_call to ftrace on the fly. Each operator functions of the call
takes a ftrace_event_call data structure as an argument, because these
functions may be shared among several ftrace_event_calls.
Signed-off-by: Ma
Cleanup fix_riprel() in arch/x86/kernel/kprobes.c by using x86 instruction
decoder.
Signed-off-by: Masami Hiramatsu
Cc: Ananth N Mavinakayanahalli
Cc: Jim Keniston
Cc: Ingo Molnar
---
arch/x86/kernel/kprobes.c | 128 -
1 files changed, 23 insertio
Masami Hiramatsu wrote:
> Add x86 instruction decoder to arch-specific libraries. This decoder
> can decode x86 instructions used in kernel into prefix, opcode, modrm,
> sib, displacement and immediates. This can also show the length of
> instructions.
>
> This version introduces instruction attri
On Fri, Jun 05, 2009 at 12:02:02PM -0400, Gregory Haskins wrote:
> Hi Marcelo!
>
> Comments about the shutdown path ambiguity are in-line
>
> Gregory Haskins wrote:
> > iosignalfd is a mechanism to register PIO/MMIO regions to trigger an eventfd
> > signal when written to by a guest. Host usersp
Hmm,
I just noticed that dump file saved using virsh contains some libvirt
related headers, so I guess I can't just feed it directly to qemu-kvm.
So I guess best way to test save/restore without libvirt is to save
vm state using monitor and then restore it again.
But I can't find any clear docume
46 matches
Mail list logo
