Actually, although not intended (and was not tested), KVM's migration
capability enables save/restore of non-qcow images.
I used it to debug the migration code.
Please look at the bottom of http://kvm.qumranet.com/kvmwiki/Migration
(savevm/loadvm to an external state file).
BTW, my little trick
Hello,
I have FC7 with windows 2003 installed under it using kvm.
I know that by alt/ctrl/f you can toggle the windows 2003 screen so
that it will be full screen or not.
My question is:
I am launching windows 2003 from linux by
/usr/local/kvm/bin/qemu-system-x86_64 . -hda vdisk.img -cdrom
On 7/2/07, Mark Ryden [EMAIL PROTECTED] wrote:
My question is:
I am launching windows 2003 from linux by
/usr/local/kvm/bin/qemu-system-x86_64 . -hda vdisk.img -cdrom
/dev/hdb -no-acpi -boot d -m 384.
-full-screen and, please, man pages exist for a reason ;)
Luca
I had a host running kvm-27 oops on me last week. The system had been
up for about 2 weeks, and had probably run and stopped at least a couple
hundred kvm guests. I don't think it is very reproducible, but here it
is anyway. The host is running 2.6.20.4.
Here's the actual BUG_ON() that was
On 7/2/07, Dave Hansen [EMAIL PROTECTED] wrote:
I had a host running kvm-27 oops on me last week. The system had been
up for about 2 weeks, and had probably run and stopped at least a couple
hundred kvm guests. I don't think it is very reproducible, but here it
is anyway. The host is
Dave Hansen wrote:
I had a host running kvm-27 oops on me last week. The system had been
up for about 2 weeks, and had probably run and stopped at least a couple
hundred kvm guests. I don't think it is very reproducible, but here it
is anyway. The host is running 2.6.20.4.
On Mon, 2007-07-02 at 20:58 +0200, Luca wrote:
MMU working memory was exhausted during a guest context switch. It has
been fixed by:
KVM: Lazy guest cr3 switching
4b82b37a35a085a07d9ed84efee06c69655fd3d1
which is included in KVM-28.
OK, I'll give kvm-28 a shot. Thanks for the help!
Hi
I cant get pxeboot to work in kvm-28. I built kvm-28 on ubuntu 7.04
(feisty) and everything has worked great. But when testing pxeboot with:
/usr/local/kvm/bin/qemu -net nic,vlan=0 -net
tap,vlan=0,script=/etc/qemu-ifup2,ifname=foo kvm-stuff/etch.qcow2.img
-boot n
It doesnt work. It boots c
Dong, Eddie wrote:
Here is the updated patch with all comments fixed.
Meanwhile I enabled SVM support by copying code from Xen and managed to
find an AMD box to have a shoot, it works!
Please also find the svm patch.
drivers/kvm/kvm_irq.c | 59 ++
drivers/kvm/kvm_irq.h | 64
Uri Lublin wrote:
Actually, although not intended (and was not tested), KVM's migration
capability enables save/restore of non-qcow images.
I used it to debug the migration code.
Please look at the bottom of http://kvm.qumranet.com/kvmwiki/Migration
(savevm/loadvm to an external state
While QEMU can remap portions of physical ram to a higher address in
phys_ram_base, KVM requires that the memory be present where it would be in
physical memory. Make sure to copy the option ROMs to the right space in
physical memory when KVM is enabled.
Signed-off-by: Anthony Liguori [EMAIL
Peter Skogström wrote:
Hi
I cant get pxeboot to work in kvm-28. I built kvm-28 on ubuntu 7.04
(feisty) and everything has worked great. But when testing pxeboot with:
I was able to reproduce and fix your problem. Let me know if you have
any problems with the patch I posted.
Regards,
This patch adds support to gdbstub and the monitor to sync CPU state before
and after the user views/changes it. I also added kvm_allowed guards to
kvm_{load,save}_registers. I chose to do it here so that callers didn't need
to use the guards. We should probably provide nop implementations so
Avi Kivity wrote:
Anthony Liguori wrote:
This patch adds support to gdbstub and the monitor to sync CPU state before
and after the user views/changes it.
Signed-off-by: Anthony Liguori [EMAIL PROTECTED]
diff --git a/qemu/gdbstub.c b/qemu/gdbstub.c
index c33a66e..a3b82af 100644
---
Anthony Liguori wrote:
#ifdef USE_KVM is needed here.
I thought a patch was recently submitted that made kvm_allowed not
depend on USE_KVM?
I must have missed it, or forgotten.
If not, do you have a problem with one?
It serves as a delimiter of what code we introduced, but then,
+/* for KVM_SET_IRQ_LEVEL */
+struct kvm_irq_level {
+__u32 irq;
+__u32 level;
+};
Please add an irqchip index, so this can be used for
configurations with
multiple irqchips (likely ioapics). You'll also need to add
padding so
the structure is 64-bit aligned.
Adding
16 matches
Mail list logo
