Re: [kvm-devel] boot stops after console handover?
On Sat, Jan 12, 2008 at 06:07:19PM +, Antoine Martin wrote: > >> If that doesn't work, maybe you can upload an image > >> for me to debug. > > > > http://194.145.196.85/kvm/vmlinuz-2.6.24-rc7.bz2 > > > Any luck? Any other ideas for me to try? see if the problem goes away with -no-kvm-irqchip and using "nolapic" in the guest kernel if that doesn't fix it, use the last kvm code as an external module Carlo - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] boot stops after console handover?
On Sun, Jan 13, 2008 at 01:19:13AM +, Antoine Martin wrote: > Carlo Marcelo Arenas Belon wrote: > > On Sat, Jan 12, 2008 at 11:01:28PM +0200, Avi Kivity wrote: > >> Antoine Martin wrote: > >> > >>> FYI, just tried building 2.6.24-rc7-git4 and got this warning: > >>> (...) > >> Probably harmless, but worth reporting to lkml. > > > > couldn't replicate it here, but I'd seen usually those kind of errors > > when building a kernel that hasn't been "mrproper" between re-configurations > > > cp .config ../config-2.6.24-rc7-git4 > make mrproper > cp ../config-2.6.24-rc7-git4 .config make oldconfig # presumed > make -j 4 replicated with your configuration, but can't still reproduce it with mine even when forcing as you do CONFIG_KVM=y CONFIG_KVM_INTEL=y available from : http://tapir.sajinet.com.pe/kvm/config-2.6.24-rc7-git4 > (...) > MODPOST vmlinux.o > WARNING: vmlinux.o(.text+0x2cb657): Section mismatch: reference to > .init.text:register_cpu_notifier (between 'kvm_init_x86' and 'kvm_sched_in') > WARNING: vmlinux.o(.text.head+0xe4): Section mismatch: reference to > .init.data.2:trampoline_level4_pgt (between 'ident_complete' and > 'secondary_startup_64') > WARNING: vmlinux.o(.text.head+0xeb): Section mismatch: reference to > .init.data.2:trampoline_level4_pgt (between 'ident_complete' and > 'secondary_startup_64') > LD vmlinux > SYSMAP System.map > SYSMAP .tmp_System.map > > You can grab the .config here: > http://194.145.196.85/kvm/config-2.6.24-rc7-git4 is this the configuration for the host kernel? if you want to use the last code for kvm you should have CONFIG_KVM disabled and instead use the external module as instructed in (HINT: you don't have a patched kernel) : http://kvm.qumranet.com/kvmwiki/HOWTO1 not sure which version will be part of 2.6.24 but I suspect it might not be kvm 59. Carlo - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] boot stops after console handover?
Carlo Marcelo Arenas Belon wrote: > On Sat, Jan 12, 2008 at 11:01:28PM +0200, Avi Kivity wrote: >> Antoine Martin wrote: >> >>> FYI, just tried building 2.6.24-rc7-git4 and got this warning: >>> (...) >> Probably harmless, but worth reporting to lkml. > > couldn't replicate it here, but I'd seen usually those kind of errors > when building a kernel that hasn't been "mrproper" between re-configurations > cp .config ../config-2.6.24-rc7-git4 make mrproper cp ../config-2.6.24-rc7-git4 .config make -j 4 (...) MODPOST vmlinux.o WARNING: vmlinux.o(.text+0x2cb657): Section mismatch: reference to .init.text:register_cpu_notifier (between 'kvm_init_x86' and 'kvm_sched_in') WARNING: vmlinux.o(.text.head+0xe4): Section mismatch: reference to .init.data.2:trampoline_level4_pgt (between 'ident_complete' and 'secondary_startup_64') WARNING: vmlinux.o(.text.head+0xeb): Section mismatch: reference to .init.data.2:trampoline_level4_pgt (between 'ident_complete' and 'secondary_startup_64') LD vmlinux SYSMAP System.map SYSMAP .tmp_System.map You can grab the .config here: http://194.145.196.85/kvm/config-2.6.24-rc7-git4 Antoine - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] [PATCH 2/3] [PATCH] kvmclock - the host part.
Avi Kivity wrote: > Anthony Liguori wrote: >> Glauber de Oliveira Costa wrote: >> >>> This is the host part of kvm clocksource implementation. As it does >>> not include clockevents, it is a fairly simple implementation. We >>> only have to register a per-vcpu area, and start writting to it >>> periodically. >>> >>> The area is binary compatible with xen, as we use the same >>> shadow_info structure. >>> >>> diff --git a/include/asm-x86/kvm_para.h b/include/asm-x86/kvm_para.h >>> index c6f3fd8..abe412a 100644 >>> --- a/include/asm-x86/kvm_para.h >>> +++ b/include/asm-x86/kvm_para.h >>> @@ -1,5 +1,6 @@ >>> #ifndef __X86_KVM_PARA_H >>> #define __X86_KVM_PARA_H >>> +#include >>> >> >> Can we abstract that out into a neutral header instead of including >> the Xen headers directly in KVM. Please rename the structure too to >> something neutral. >> >> Including something as generic as xen/interface/xen.h when CONFIG_XEN >> may not be set is not a good thing, I believe. >> > > Well, one of the motivations behind this is to actually supply a Xen > clock to Xen guests. So maybe we can call the feature a "kvm > xenclock" instead and feel justified in including Xen headers. > > However, you are probably right in that we are getting into a > dependency and kconfig hell we do not yet deserve. Not even > mentioning that CONFIG_XEN is a guest thing while kvmclock is also a > host thing. > > So we are probably better of using a non-Xen structure that > accidentally happens to be binary compatible with the Xen interface. > Stranger things have happened. Yes, this is what I meant. My concerns is dependencies and namespace pollution. I think using the same interface is a very Good Thing. Regards, Anthony Liguori > If we agree on this, please define _only_ the time-related parts so we > have a decoupled interface. We'll need two msrs: one for wc and one > for vcpu time. > - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] boot stops after console handover?
On Sat, Jan 12, 2008 at 11:01:28PM +0200, Avi Kivity wrote: > Antoine Martin wrote: > > > FYI, just tried building 2.6.24-rc7-git4 and got this warning: > > (...) > > LD vmlinux.o > > MODPOST vmlinux.o > > WARNING: vmlinux.o(.text+0x2cb657): Section mismatch: reference to > > .init.text:register_cpu_notifier (between 'kvm_init_x86' and 'kvm_sched_in') > > WARNING: vmlinux.o(.text.head+0xe4): Section mismatch: reference to > > .init.data.2:trampoline_level4_pgt (between 'ident_complete' and > > 'secondary_startup_64') > > WARNING: vmlinux.o(.text.head+0xeb): Section mismatch: reference to > > .init.data.2:trampoline_level4_pgt (between 'ident_complete' and > > 'secondary_startup_64') > > LD vmlinux > > Probably harmless, but worth reporting to lkml. couldn't replicate it here, but I'd seen usually those kind of errors when building a kernel that hasn't been "mrproper" between re-configurations Carlo - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] boot stops after console handover?
Antoine Martin wrote: >>> If that doesn't work, maybe you can upload an image >>> for me to debug. >>> >> http://194.145.196.85/kvm/vmlinuz-2.6.24-rc7.bz2 >> >> > Any luck? Any other ideas for me to try? > > Haven't got around to it yet, sorry. > FYI, just tried building 2.6.24-rc7-git4 and got this warning: > (...) > LD vmlinux.o > MODPOST vmlinux.o > WARNING: vmlinux.o(.text+0x2cb657): Section mismatch: reference to > .init.text:register_cpu_notifier (between 'kvm_init_x86' and 'kvm_sched_in') > WARNING: vmlinux.o(.text.head+0xe4): Section mismatch: reference to > .init.data.2:trampoline_level4_pgt (between 'ident_complete' and > 'secondary_startup_64') > WARNING: vmlinux.o(.text.head+0xeb): Section mismatch: reference to > .init.data.2:trampoline_level4_pgt (between 'ident_complete' and > 'secondary_startup_64') > LD vmlinux > > Probably harmless, but worth reporting to lkml. -- Any sufficiently difficult bug is indistinguishable from a feature. - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] [PATCH 1/2] include kvm_para.h
Glauber de Oliveira Costa wrote: > have qemu-kvm to include kvm_para, allowing access to paravirt definitions > > Signed-off-by: Glauber de Oliveira Costa <[EMAIL PROTECTED]> > --- > qemu/qemu-kvm-x86.c |1 + > 1 files changed, 1 insertions(+), 0 deletions(-) > > diff --git a/qemu/qemu-kvm-x86.c b/qemu/qemu-kvm-x86.c > index c79ca36..21ec112 100644 > --- a/qemu/qemu-kvm-x86.c > +++ b/qemu/qemu-kvm-x86.c > @@ -14,6 +14,7 @@ extern int kvm_irqchip; > #include > #include > #include > +#include > IIRC, early versions of kvm_para.h were userspace unfriendly, so we need a version code check (or better, a KVM_CAP_ check) around this. -- Any sufficiently difficult bug is indistinguishable from a feature. - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] [PATCH] KVM: add KVM_SYNC_SHADOW_WITH_USER ioctl (v2)
Anthony Liguori wrote: >>> >> >> With mmu notifiers (posted two minutes after this) shadow is >> implicitly synced with userspace. Since it seems to be progressing >> rapidly, I won't apply this patch in the hope that mmu notifiers can >> be ready for 2.6.25. > > Does that mean that we'll only support ballooning on host kernels > > 2.6.25 are you going to do judo with debug registers to implement it > for older kernels? Good question. We may choose not to support it (distros may backport it if they wish), or do some evil hackery, or apply KVM_SYNC_SHADOW_WITH_USER _only_ to the external module. -- Any sufficiently difficult bug is indistinguishable from a feature. - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
[kvm-devel] current kvm userspace git doesn't compile on i386
Current kvm userspace git configured with ./configure --prefix=/opt/kvm --with-patched-kernel --qemu-cc=/usr/bin/gcc-3.4 gives: /usr/bin/gcc-3.4 -L /home/hch/work/kvm-userspace/qemu/../libkvm -g -o qemu-system-x86_64 vl.o osdep.o monitor.o pci.o loader.o isa_mmio.o migration.o block-raw-posix.o lsi53c895a.o usb-ohci.o eeprom93xx.o eepro100.o ne2000.o pcnet.o rtl8139.o hypercall.o virtio.o virtio-net.o virtio-blk.o ide.o pckbd.o ps2.o vga.o sb16.o es1370.o dma.o fdc.o mc146818rtc.o serial.o i8259.o i8254.o pcspk.o pc.o cirrus_vga.o apic.o parallel.o acpi.o piix_pci.o usb-uhci.o vmmouse.o vmport.o vmware_vga.o extboot.o gdbstub.o ../libqemu_common.a libqemu.a /home/hch/work/kvm-userspace/qemu/../libkvm/libkvm.a -lm -lz -lkvm -lgnutls -L/usr/lib -lSDL -lrt -lpthread -lutil libqemu.a(kvm-tpr-opt.o): In function `enable_vapic': /home/hch/work/kvm-userspace/qemu/kvm-tpr-opt.c:221: undefined reference to `kvm_enable_vapic' libqemu.a(kvm-tpr-opt.o): In function `kvm_tpr_opt_setup': /home/hch/work/kvm-userspace/qemu/kvm-tpr-opt.c:287: undefined reference to `kvm_enable_tpr_access_reporting' collect2: ld returned 1 exit status make[2]: *** [qemu-system-x86_64] Error 1 make[2]: Leaving directory `/home/hch/work/kvm-userspace/qemu/x86_64-softmmu' make[1]: *** [subdir-x86_64-softmmu] Error 2 make[1]: Leaving directory `/home/hch/work/kvm-userspace/qemu' make: *** [qemu] Error 2 - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] [RFC] fix VMX TSC synchronicity
Will Trives wrote: > Hello, > > 64 bit environment Intel Q6600 processor. > > I did hand apply the patch so I might have got something wrong. > > Guest was a 32 bit kubuntu 7.10. > > Basically I just mounted a few disk images with " -drive > file=/whatever,if=scsi " and used gparted to copy a partition from one > to the other. > > It's probably something I have done wrong, i'll test it again in a few > more days. > > I've trashed more than one image by running multiple guests with the same image, can this be the case here? -- Any sufficiently difficult bug is indistinguishable from a feature. - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] [PATCH 2/3] [PATCH] kvmclock - the host part.
Anthony Liguori wrote: > Glauber de Oliveira Costa wrote: > >> This is the host part of kvm clocksource implementation. As it does >> not include clockevents, it is a fairly simple implementation. We >> only have to register a per-vcpu area, and start writting to it periodically. >> >> The area is binary compatible with xen, as we use the same shadow_info >> structure. >> >> diff --git a/include/asm-x86/kvm_para.h b/include/asm-x86/kvm_para.h >> index c6f3fd8..abe412a 100644 >> --- a/include/asm-x86/kvm_para.h >> +++ b/include/asm-x86/kvm_para.h >> @@ -1,5 +1,6 @@ >> #ifndef __X86_KVM_PARA_H >> #define __X86_KVM_PARA_H >> +#include >> > > Can we abstract that out into a neutral header instead of including the > Xen headers directly in KVM. Please rename the structure too to > something neutral. > > Including something as generic as xen/interface/xen.h when CONFIG_XEN > may not be set is not a good thing, I believe. > Well, one of the motivations behind this is to actually supply a Xen clock to Xen guests. So maybe we can call the feature a "kvm xenclock" instead and feel justified in including Xen headers. However, you are probably right in that we are getting into a dependency and kconfig hell we do not yet deserve. Not even mentioning that CONFIG_XEN is a guest thing while kvmclock is also a host thing. So we are probably better of using a non-Xen structure that accidentally happens to be binary compatible with the Xen interface. Stranger things have happened. If we agree on this, please define _only_ the time-related parts so we have a decoupled interface. We'll need two msrs: one for wc and one for vcpu time. -- Any sufficiently difficult bug is indistinguishable from a feature. - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] [PATCH 2/3] [PATCH] kvmclock - the host part.
Glauber de Oliveira Costa wrote:
> This is the host part of kvm clocksource implementation. As it does
> not include clockevents, it is a fairly simple implementation. We
> only have to register a per-vcpu area, and start writting to it periodically.
>
> The area is binary compatible with xen, as we use the same shadow_info
> structure.
>
> @@ -412,7 +413,7 @@ static u32 msrs_to_save[] = {
> #ifdef CONFIG_X86_64
> MSR_CSTAR, MSR_KERNEL_GS_BASE, MSR_SYSCALL_MASK, MSR_LSTAR,
> #endif
> - MSR_IA32_TIME_STAMP_COUNTER,
> + MSR_IA32_TIME_STAMP_COUNTER, MSR_PARAVIRT_CLOCK,
> };
>
Let us be good citizens and put the msr into our private MSR_KVM_*
namespace.
>
>
> +#define WC_OFFSET offsetof(struct shared_info, wc_version)
> +
> +static void kvm_write_guest_time(struct kvm_vcpu *v)
> +{
> + struct timespec ts, wc_ts;
> + int wc_args[3]; /* version, wc_sec, wc_nsec */
> + unsigned long flags;
> + struct kvm_vcpu_arch *vcpu = &v->arch;
> +
> + if (!vcpu->shared_info)
> + return;
> +
> + /* Make the update of both version numbers visible to guest */
> + wc_args[0] = ++vcpu->wc_version;
> + kvm_write_guest(v->kvm, vcpu->shared_info + WC_OFFSET, wc_args,
> + sizeof(wc_args));
> + vcpu->hv_clock.version++;
> + kvm_write_guest(v->kvm, vcpu->clock_addr, &vcpu->hv_clock,
> + sizeof(vcpu->hv_clock));
> +
> + /* Keep irq disabled to prevent changes to the clock */
> + local_irq_save(flags);
> + kvm_get_msr(v, MSR_IA32_TIME_STAMP_COUNTER,
> + &vcpu->hv_clock.tsc_timestamp);
> + wc_ts = current_kernel_time();
> + ktime_get_ts(&ts);
> + local_irq_restore(flags);
> +
> + /* With all the info we got, fill in the values */
> + wc_args[1] = wc_ts.tv_sec;
> + wc_args[2] = wc_ts.tv_nsec;
> + wc_args[0] = ++vcpu->wc_version;
> +
> + vcpu->hv_clock.system_time = ts.tv_nsec +
> + (NSEC_PER_SEC * (u64)ts.tv_sec);
> + vcpu->hv_clock.version++;
> +
> + /* And finally, let the guest see them */
> + kvm_write_guest(v->kvm, vcpu->shared_info + WC_OFFSET, wc_args,
> + sizeof(wc_args));
> + kvm_write_guest(v->kvm, vcpu->clock_addr, &vcpu->hv_clock,
> + sizeof(vcpu->hv_clock));
> +}
> +
>
Why write things twice? This is per-vcpu, and the guest cannot see
anything between the two writes.
Also, kvm_write_guest() needs mmap_sem for read. Suggest you grab the
page using gfn_to_page() and kmap_atomic() it instead.
--
Any sufficiently difficult bug is indistinguishable from a feature.
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] Where are vmentry failure caugth?
Avi Kivity wrote: > Guillaume Thouvenin wrote: > >> On Thu, 10 Jan 2008 17:32:35 +0200 >> Avi Kivity <[EMAIL PROTECTED]> wrote: >> >> >> >>> I think 33 is the error code, which means we got a general protection >>> fault while accessing segment 0x33. >>> >>> What guest code is running when this happens? The dump sometimes >>> includes the current code. >>> >>> >> When it happened I started an openSUSE-10.3 installation. Here is the >> complete dump: >> What version of gfxboot does openSUSE 10.3 use? gfxboot was broken for KVM until very recently. This is probably what you're seeing. Regards, Anthony Liguori >> [guill]$ ./qemu-system-x86_64 -hda ~/disk_images/openSUSE-10.3.qcow2 -cdrom >> ~/iso_images/openSUSE-10.3-GM-x86_64-mini.iso -boot d -m 1024 >> exception 13 (33) >> rax 0671 rbx 0080 rcx rdx >> 13ca >> rsi 00055e1c rdi 00055e1d rsp fffa0080 rbp >> 200b >> r8 r9 r10 r11 >> >> r12 r13 r14 r15 >> >> rip b071 rflags 00033096 >> cs 4004 (00040040/ p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) >> ds 4004 (00040040/ p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) >> es 00ff (0ff0/ p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) >> ss ff11 (000ff110/ p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) >> fs 3002 (00030020/ p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) >> gs (/ p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) >> tr (fffbd000/2088 p 1 dpl 0 db 0 s 0 type b l 0 g 0 avl 0) >> ldt (/ p 1 dpl 0 db 0 s 0 type 2 l 0 g 0 avl 0) >> gdt 40920/47 >> idt 0/ >> cr0 6010 cr2 0 cr3 0 cr4 0 cr8 0 efer 0 >> code: 17 06 29 4b 01 18 eb 18 a8 25 aa 19 28 4c 01 28 4d 01 01 17 --> 0f 17 >> 0f 01 17 0f 17 12 01 17 2c 25 4b 19 21 00 02 17 1a 94 0a 76 67 61 3d 30 78 >> 25 78 20 >> Aborted >> >> In the console I got: >> [86955.117391] handle_exception: unexpected, vectoring info 0x8306 intr >> info 0x8b0d >> [86955.193194] pending exception: not handled yet >> [86955.219948] pending exception: not handled yet >> >> > > We probably need to understand the first handle_exception message; > things have probably gone very wrong afterwards. > > - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] [PATCH] KVM: add KVM_SYNC_SHADOW_WITH_USER ioctl (v2)
Avi Kivity wrote: > Marcelo Tosatti wrote: >> Export nukeing of shadow MMU pages through an ioctl, required for >> consistency on balloon inflate. >> >> > > With mmu notifiers (posted two minutes after this) shadow is > implicitly synced with userspace. Since it seems to be progressing > rapidly, I won't apply this patch in the hope that mmu notifiers can > be ready for 2.6.25. Does that mean that we'll only support ballooning on host kernels > 2.6.25 are you going to do judo with debug registers to implement it for older kernels? Regards, Anthony Liguori - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] Setting hardware breakpoints in guest OS
[EMAIL PROTECTED] wrote: > Can hardware breakpoints be set (and trapped, and handled) inside a guest > OS (specifially Windows XP2)? > > I noticed the other day that software (malicious code, in fact) packed with > the EXE compressor PELock won't run under QEMU+KVM. I guessed that this was > because h/w breakpoints aren't being trapped. (The PELock incarnation used > in this case relies on SEH and H/W breaks -- verifying that they take place > correctly -- in its decryption code in order to try to make it harder to > extract the original content from packed files.) > > A quick try with OllyDbg suggested that I wasn't able to provoke hardware > traps in my own code, either. Olly allows me to specify a H/W breakpoint > but I never seem to get control back at the desired address. INT 1 and INT > 3 debugging work just fine (i.e. tracing and software breakpoints). > > Is this "one of those things" to do with virtualisation? QEMU+kqemu handles > PELock files just fine. While we tried to make debugging inside the guest work, this was never really tested, so it's likely broken. I'll try to look at what it will take to make it work; I don't think there's much needed. What hardware are you using? If you have both AMD and Intel hardware, you might have better luck switching, since this is very subarch dependent. -- Any sufficiently difficult bug is indistinguishable from a feature. - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] Where are vmentry failure caugth?
Guillaume Thouvenin wrote: > On Thu, 10 Jan 2008 17:32:35 +0200 > Avi Kivity <[EMAIL PROTECTED]> wrote: > > >> I think 33 is the error code, which means we got a general protection >> fault while accessing segment 0x33. >> >> What guest code is running when this happens? The dump sometimes >> includes the current code. >> > > When it happened I started an openSUSE-10.3 installation. Here is the > complete dump: > > [guill]$ ./qemu-system-x86_64 -hda ~/disk_images/openSUSE-10.3.qcow2 -cdrom > ~/iso_images/openSUSE-10.3-GM-x86_64-mini.iso -boot d -m 1024 > exception 13 (33) > rax 0671 rbx 0080 rcx rdx > 13ca > rsi 00055e1c rdi 00055e1d rsp fffa0080 rbp > 200b > r8 r9 r10 r11 > > r12 r13 r14 r15 > > rip b071 rflags 00033096 > cs 4004 (00040040/ p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) > ds 4004 (00040040/ p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) > es 00ff (0ff0/ p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) > ss ff11 (000ff110/ p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) > fs 3002 (00030020/ p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) > gs (/ p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) > tr (fffbd000/2088 p 1 dpl 0 db 0 s 0 type b l 0 g 0 avl 0) > ldt (/ p 1 dpl 0 db 0 s 0 type 2 l 0 g 0 avl 0) > gdt 40920/47 > idt 0/ > cr0 6010 cr2 0 cr3 0 cr4 0 cr8 0 efer 0 > code: 17 06 29 4b 01 18 eb 18 a8 25 aa 19 28 4c 01 28 4d 01 01 17 --> 0f 17 > 0f 01 17 0f 17 12 01 17 2c 25 4b 19 21 00 02 17 1a 94 0a 76 67 61 3d 30 78 25 > 78 20 > Aborted > > In the console I got: > [86955.117391] handle_exception: unexpected, vectoring info 0x8306 intr > info 0x8b0d > [86955.193194] pending exception: not handled yet > [86955.219948] pending exception: not handled yet > We probably need to understand the first handle_exception message; things have probably gone very wrong afterwards. -- Any sufficiently difficult bug is indistinguishable from a feature. - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] KVM and Vista question
Anup Gangwar wrote: > Hello All, > > I was trying to get Vista 64-bit to boot off QEMU and was pointed to > this list from the QEMU developers list. From the guest compatibility > page I could gather that KVM with Intel host is able to boot a Vista > 64-bit guest, however the stand-alone version of QEMU does not (yet) > support booting Vista. Could someone please provide more insight as to > how this is achieved. My understanding is that there are problems in: > > 1. ACPI code in QEMU BIOS > 2. Deficiencies in device model > > I believe that these issues are addressed in the QEMU tree being > maintained with KVM. Is there anything additional which KVM does to > get Vista to work? You might try using the kvm bios, or looking at the changelog for the bios. There may be other necessary changes as well, but unfortunately nothing springs to mind. -- Any sufficiently difficult bug is indistinguishable from a feature. - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] [PATCH] KVM: add KVM_SYNC_SHADOW_WITH_USER ioctl (v2)
Marcelo Tosatti wrote: > Export nukeing of shadow MMU pages through an ioctl, required for > consistency on balloon inflate. > > With mmu notifiers (posted two minutes after this) shadow is implicitly synced with userspace. Since it seems to be progressing rapidly, I won't apply this patch in the hope that mmu notifiers can be ready for 2.6.25. -- Any sufficiently difficult bug is indistinguishable from a feature. - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] mmu notifiers
Christoph Lameter wrote: > >> Excellent, the more users the patch has, the easier it will be to justify it. >> > > We'd like to make sure though that we can sleep when the hooks have been > called. We may have to sent a message to kick remote ptes out when local > pte changes happen. > > It may be as simple as moving the notifier calls down to a sleeping context, away from the pte lock and any friends. kvm also needs to send a message on an mmu notification, but that's just an IPI within the same host. -- Any sufficiently difficult bug is indistinguishable from a feature. - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] mmu notifiers
Christoph Lameter wrote: > On Thu, 10 Jan 2008, Avi Kivity wrote: > > >> Actually sharing memory is possible even without this patch; one simply >> mmap()s a file into the address space of both guests. Or are you referring >> to >> something else? >> > > A file from where? If a file is read by two guests then they will have > distinct page structs. > > Two kvm instances mmap() the file (from anywhere) into the guest address space. That memory is shared, and will be backed by the same page structs at the same offset. -- Any sufficiently difficult bug is indistinguishable from a feature. - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] boot stops after console handover?
>> If that doesn't work, maybe you can upload an image >> for me to debug. > > http://194.145.196.85/kvm/vmlinuz-2.6.24-rc7.bz2 > Any luck? Any other ideas for me to try? FYI, just tried building 2.6.24-rc7-git4 and got this warning: (...) LD vmlinux.o MODPOST vmlinux.o WARNING: vmlinux.o(.text+0x2cb657): Section mismatch: reference to .init.text:register_cpu_notifier (between 'kvm_init_x86' and 'kvm_sched_in') WARNING: vmlinux.o(.text.head+0xe4): Section mismatch: reference to .init.data.2:trampoline_level4_pgt (between 'ident_complete' and 'secondary_startup_64') WARNING: vmlinux.o(.text.head+0xeb): Section mismatch: reference to .init.data.2:trampoline_level4_pgt (between 'ident_complete' and 'secondary_startup_64') LD vmlinux Cheers Antoine - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] [RFC] fix VMX TSC synchronicity
Hello, 64 bit environment Intel Q6600 processor. I did hand apply the patch so I might have got something wrong. Guest was a 32 bit kubuntu 7.10. Basically I just mounted a few disk images with " -drive file=/whatever,if=scsi " and used gparted to copy a partition from one to the other. It's probably something I have done wrong, i'll test it again in a few more days. Regards, Will On Sat, 2008-01-12 at 10:28 -0200, Marcelo Tosatti wrote: > On Sat, Jan 12, 2008 at 02:11:30PM +1100, Will Trives wrote: > > Hello, > > > > Just thought i'd mention that this patch caused disk corruption in my > > virtual machines, particularly when using scsi emulation. > > > > I got few errors like this as well: > > > > lsi_scsi: error: ORDERED queue not implemented > > lsi_scsi: error: IO with unknown tag 65577 > > Hi Will, > > Can you please be more descriptive of your environment? What guest OS ? > How many CPU's do you have assigned to it ? > > Are you sure you're talking about the "VMX TSC" patch in the Subject: > line? > > Thanks - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] [RFC] fix VMX TSC synchronicity
On Sat, Jan 12, 2008 at 02:11:30PM +1100, Will Trives wrote: > Hello, > > Just thought i'd mention that this patch caused disk corruption in my > virtual machines, particularly when using scsi emulation. > > I got few errors like this as well: > > lsi_scsi: error: ORDERED queue not implemented > lsi_scsi: error: IO with unknown tag 65577 Hi Will, Can you please be more descriptive of your environment? What guest OS ? How many CPU's do you have assigned to it ? Are you sure you're talking about the "VMX TSC" patch in the Subject: line? Thanks - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] Bug: vmmouse doesn't seem to work properly with xorg 7.3
On Saturday 12 January 2008 08:45:29 Will Trives wrote: > Hello, > > As per subject the vmmouse driver does not appear to work with any > distro of Linux that uses Xorg 7.3, at least that has been my > experience. > > The mouse appears to be jammed over to the right hand side. Does exporting $ export SDL_VIDEO_X11_DGAMOUSE=0 on the host help? You can also try -usbdevice tablet command line option to qemu. - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
