This was bound to come up eventually, but perhaps KVM isn't the best
name since it's overloading a rather commonly used acronym. A quick
google shows that besides the obvious clash with, well, KVMs, Sun also
used it for one of their JVMs.
http://java.sun.com/products/cldc/wp/
Thoughts? I fig
Simon Kagstrom wrote:
>> Very likely this is due to VT's inability to virtualize real mode
>> correctly. Is anyone in the mood to extend x86_emulate.c to support
>> real mode?
>
> I forgot to add that I've tested it in Xen as well, and it works
> there. Maybe someone has an AMD at hand to test
Jun Koi wrote:
> hi,
>
> in the structure kvm_context in libkvm:
>
> struct kvm_context {
> int fd;
> struct kvm_callbacks *callbacks;
> void *opaque;
> void *physical_memory;
> };
>
> i would propose to change the field name to "private" or "data",
> rather than "opaque", which
Avi Kivity wrote:
> Jun Koi wrote:
>> hi,
>>
>> i guess this question should be in your FAQ: does KVM work with Xen?
>> in the other word, is it possible to run KVM on Xen machine? (i.e
>> loading KVM on Dom0 or DomU. obviously it does not work on DomU, but i
>> am not sure about Dom0 case).
>>
Avi Kivity wrote:
>> Or gcc
>> might move the assignment of phys_addr to after the inline assembly.
>>
> "asm volatile" prevents that (and I'm not 100% sure it's necessary).
No, it won't necessarily. "asm volatile" simply forces gcc to emit the
assembler, even if it thinks its output doesn't g
At Thu, 09 Nov 2006 19:49:05 +0200,
Avi Kivity wrote:
>
> Avi Kivity wrote:
> >>0e75 660fb7ec movzx ebp, sp
> >>0e79 6601c5 add ebp, eax
> >>
> >>0e7c 660f01975200 lgdtsing
Avi Kivity wrote:
>>0e75 660fb7ec movzx ebp, sp
>>0e79 6601c5 add ebp,
>> eax 0e7c 660f01975200 lgdt
>> single ptr [bx+0x52]
>>0e82 0f20c0 mov
Arnd Bergmann wrote:
> On Thursday 09 November 2006 15:52, Avi Kivity wrote:
>
>> Wouldn't that make inline assembly useless? Suppose the contents is
>> itself a pointer. What about the pointed-to contents?
>>
>> e.g.
>>
>> int x = 3;
>> int *y = &x;
>> int z;
>>
>> asm ("mov
On Thursday 09 November 2006 15:52, Avi Kivity wrote:
> Wouldn't that make inline assembly useless? Suppose the contents is
> itself a pointer. What about the pointed-to contents?
>
> e.g.
>
> int x = 3;
> int *y = &x;
> int z;
>
> asm ("mov %1, %%rax; movl (%%rax), %0" : "=r"
Simon Kagstrom wrote:
> Hello!
>
> I'm trying to get etherboot running with KVM (version 2 from today),
> but have been unsucessful so far. It works well in plain qemu, but not
> with KVM.
>
> I'm running etherboot 5.4.2, ROM rtl8139:rtl8139 [0x10ec,0x8139] built
> as a "ISO bootable image without
Hello!
I'm trying to get etherboot running with KVM (version 2 from today),
but have been unsucessful so far. It works well in plain qemu, but not
with KVM.
I'm running etherboot 5.4.2, ROM rtl8139:rtl8139 [0x10ec,0x8139] built
as a "ISO bootable image without legacy floppy emulation (.iso)" on
h
Changes:
- much easier to get running, see updated HOWTO
- now just one download, get yours while supplies last
- single qemu binary for kvm and non-kvm runs (Anthony Liguori)
- accompanying external kernel module package has all bugfixes folded
in (plus a bit of cosmetics)
http://kvm.sou
Arnd Bergmann wrote:
> On Thursday 09 November 2006 14:36, Avi Kivity wrote:
>
>>> I'm not an expert on inline assembly, but don't you need an extra
>>> '"m" (phys_addr)' to make sure that gcc actually puts the variable
>>> on the stack instead of passing a NULL pointer as '"a"(&phys_addr)'?
>>>
On Thursday 09 November 2006 14:36, Avi Kivity wrote:
>
> >
> > I'm not an expert on inline assembly, but don't you need an extra
> > '"m" (phys_addr)' to make sure that gcc actually puts the variable
> > on the stack instead of passing a NULL pointer as '"a"(&phys_addr)'?
>
> Taking a variable's
Hesse, Christian wrote:
> HOST_CR4 0x2690
> ***
> *** pre launch
> vmcs_dump
> HOST_CR4 0x2690
> GUEST_CR4 0x2021
>
This doesn't look like pae mode. Bit 5 of cr4 should be set. This is
t
On Thursday 09 November 2006 14:29, Hesse, Christian wrote:
> On Thursday 09 November 2006 14:01, you wrote:
> > Can you try the attached patch (on top of the previous debug patch)? In
> > addition, please enable pae mode (CONFIG_HIGHMEM64G) to see if the cpu
> > has trouble switching from pae mod
Arnd Bergmann wrote:
> On Thursday 09 November 2006 12:08, Avi Kivity wrote:
>
>> Index: linux-2.6/drivers/kvm/kvm_main.c
>> ===
>> --- linux-2.6.orig/drivers/kvm/kvm_main.c
>> +++ linux-2.6/drivers/kvm/kvm_main.c
>> @@ -369,8 +369,
On Thursday 09 November 2006 14:01, you wrote:
> Hesse, Christian wrote:
> > On Wednesday 08 November 2006 09:28, Avi Kivity wrote:
> >> Okay. Please try to apply the two patches I posted yesterday. I don't
> >> see how they can help, but it's worth trying.
> >
> > Ok, here is the log. This time
On Thursday 09 November 2006 12:08, Avi Kivity wrote:
> Index: linux-2.6/drivers/kvm/kvm_main.c
> ===
> --- linux-2.6.orig/drivers/kvm/kvm_main.c
> +++ linux-2.6/drivers/kvm/kvm_main.c
> @@ -369,8 +369,8 @@ static void vmcs_clear(struc
Hesse, Christian wrote:
On Wednesday 08 November 2006 09:28, Avi Kivity wrote:
Okay. Please try to apply the two patches I posted yesterday. I don't
see how they can help, but it's worth trying.
Ok, here is the log. This time the system did not freeze completely, I could
still move
On Wednesday 08 November 2006 09:28, Avi Kivity wrote:
> Okay. Please try to apply the two patches I posted yesterday. I don't
> see how they can help, but it's worth trying.
Ok, here is the log. This time the system did not freeze completely, I could
still move the mouse cursor, grab the qemu
From: Simon Kagstrom <[EMAIL PROTECTED]>
This fixes compilation on some (32-bit) .configs.
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
Index: linux-2.6/drivers/kvm/kvm_main.c
===
--- linux-2.6.orig/drivers/kvm/kvm_main.c
+++ linux
Simon Kagstrom wrote:
> Hello!
>
> I wanted to try out KVM and followed the HOWTO. It worked fine, except
> for two things:
>
> * libuuid-dev is needed for qemu, which would be good if added to
> the prerequisites
>
Will do.
> * The build of kvm.ko failed since load_TR_desc() was not d
Some users have an older assembler installed which doesn't grok the
vmx instructions.
Fix by encoding the instruction opcodes directly.
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
Index: linux-2.6/drivers/kvm/kvm.h
===
--- linux-2
24 matches
Mail list logo
