On Tue, 2007-10-02 at 14:11 +1000, Rusty Russell wrote:
On Tue, 2007-10-02 at 01:19 +, Hollis Blanchard wrote:
On Sun, 30 Sep 2007 15:56:16 +0200, Avi Kivity wrote:
Eventually I'd like to see the code in arch/*/kvm. That's probably not
easily doable right now because modules
Laurent Vivier wrote:
This patch corrects some errors appearing when we have an emulation failure
on an operation using REP prefix.
When x86_emulate_insn() fails, saving EIP and ECX is not enough as emulation
should have modified other registers like RSI or RDI. Moreover, the emulation
can
Laurent Vivier wrote:
Avi Kivity wrote:
Laurent Vivier wrote:
This patch corrects some errors appearing when we have an emulation
failure
on an operation using REP prefix.
When x86_emulate_insn() fails, saving EIP and ECX is not enough as
emulation
should have modified other
On Tue, 2007-10-02 at 01:01 -0500, Hollis Blanchard wrote:
On Tue, 2007-10-02 at 14:11 +1000, Rusty Russell wrote:
On Tue, 2007-10-02 at 01:19 +, Hollis Blanchard wrote:
On Sun, 30 Sep 2007 15:56:16 +0200, Avi Kivity wrote:
Eventually I'd like to see the code in arch/*/kvm.
On 10/2/07, Cam Macdonell [EMAIL PROTECTED] wrote:
Anthony Liguori wrote:
Cam Macdonell wrote:
Anthony Liguori wrote:
Cameron Macdonell wrote:
Hi,
I'm trying to understand guest virtualization at the lower levels.
I have a somewhat basic question: How does KVM virtualize an
On 10/1/07, Anthony Liguori [EMAIL PROTECTED] wrote:
Cameron Macdonell wrote:
Hi,
I'm trying to understand guest virtualization at the lower levels. I
have a somewhat basic question: How does KVM virtualize an int80
instruction from a guest? A pointer to an answer is just as good as
Hi all,
The lapic code uses ktime_t and hrtimers, which means we no longer
build for kernels 2.6.15 and below. Is it worth trying to fake this
infrastructure up, building without lapic, or abandoning 2.6.16?
Thanks,
Rusty.
This makes it easier to check kvm-userspace compatibility layer.
---
check-compat.sh | 27 +++
1 files changed, 27 insertions(+), 0 deletions(-)
create mode 100755 check-compat.sh
diff --git a/check-compat.sh b/check-compat.sh
new file mode 100755
index
Rusty Russell wrote:
Hi all,
The lapic code uses ktime_t and hrtimers, which means we no longer
build for kernels 2.6.15 and below. Is it worth trying to fake this
infrastructure up, building without lapic, or abandoning 2.6.16?
I think we can stub the code away, and hack the
Please can anyone give me some kvm-TODO.
(preferably on x86_64 and i686)
Thanks regards,
Onkar
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
Onkar wrote:
Please can anyone give me some kvm-TODO.
(preferably on x86_64 and i686)
there is page on this at kvm homepage:
http://kvm.qumranet.com/kvmwiki/TODO
check out this list, and if you need help in anything just ask :)
Thanks regards,
Onkar
Qemu-cvs as of yesterday has been merged into kvm. Everything I tested
still works, but undoubtedly a few rough edges remain. The merge brings
too many goodies to list; have fun exploring.
I've also thrown in a network latency improvement when using the tap
device (bridged networking); on
Rusty Russell wrote:
This makes it easier to check kvm-userspace compatibility layer.
I actually started to write something like this, except it pulled older
kernels from git.
Thanks.
---
check-compat.sh | 27 +++
1 files changed, 27 insertions(+), 0
Bugs item #1806241, was opened at 2007-10-02 12:27
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=1806241group_id=180599
Please note that this message will contain a full copy of
Under certain conditions, PIC interrupts should not be passed through by
the local APIC. This is usually when the guest uses the IOAPIC instead
of the PIC.
Currently qemu does not block PIC interrupts when the local APIC is
configured to do so; this results in interrupts begin received twice
Hi all,
That's not something new, but I never seen the problem mentioned here.
FreeBSD does not work on KVM, approximately since the lapic merge.
However, that does not seem related to lapic, as using -no-kvm-irqchip
does not help. With -no-kvm I get a page fault in kernel mode, while the
normal
Rusty Russell wrote:
Whatever way we go, grouping both host and guest support in the same dir
seems confusing (which is why lguest is moving to arch/i386/lguest/ for
guest and drivers/lguest/i386/ for host).
That really is funny. Our s39host is just the other way round:
arch/s390/sie for the
Hi Aurélien,
did you try kvm-45 ?
Laurent
Aurelien Jarno wrote:
Hi all,
That's not something new, but I never seen the problem mentioned here.
FreeBSD does not work on KVM, approximately since the lapic merge.
However, that does not seem related to lapic, as using -no-kvm-irqchip
does
Laurent Vivier a écrit :
Hi Aurélien,
did you try kvm-45 ?
Yes the test is done with kvm-45.
--
.''`. Aurelien Jarno | GPG: 1024D/F1BCDB73
: :' : Debian developer | Electrical Engineer
`. `' [EMAIL PROTECTED] | [EMAIL PROTECTED]
`-
Avi Kivity a écrit :
Aurelien Jarno wrote:
Hi all,
That's not something new, but I never seen the problem mentioned here.
FreeBSD does not work on KVM, approximately since the lapic merge.
However, that does not seem related to lapic, as using -no-kvm-irqchip
does not help. With -no-kvm I
Avi Kivity wrote:
Aurelien Jarno wrote:
Hi all,
That's not something new, but I never seen the problem mentioned here.
FreeBSD does not work on KVM, approximately since the lapic merge.
However, that does not seem related to lapic, as using -no-kvm-irqchip
does not help. With -no-kvm I get
Aurelien Jarno wrote:
Avi Kivity a écrit :
Aurelien Jarno wrote:
Hi all,
That's not something new, but I never seen the problem mentioned here.
FreeBSD does not work on KVM, approximately since the lapic merge.
However, that does not seem related to lapic, as using
On Mon, 2007-10-01 at 17:23 -0600, Cam Macdonell wrote:
Actually, I looking into doing a PhD dissertation :) I'm just trying to
get a better working understanding of how kvm (and other VMMs) handle
instructions like int80 that should trap into the OS, but of course in a
VM need to trap
Laurent Vivier a écrit :
Avi Kivity wrote:
Aurelien Jarno wrote:
Hi all,
That's not something new, but I never seen the problem mentioned here.
FreeBSD does not work on KVM, approximately since the lapic merge.
However, that does not seem related to lapic, as using -no-kvm-irqchip
does
Jun Koi wrote:
On 10/1/07, Anthony Liguori [EMAIL PROTECTED] wrote:
Cameron Macdonell wrote:
Hi,
I'm trying to understand guest virtualization at the lower levels. I
have a somewhat basic question: How does KVM virtualize an int80
instruction from a guest? A pointer to an
Bugs item #1806334, was opened at 2007-10-02 15:52
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=1806334group_id=180599
Please note that this message will contain a full copy of
Bugs item #1806338, was opened at 2007-10-02 16:06
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=1806338group_id=180599
Please note that this message will contain a full copy of
Bugs item #1806377, was opened at 2007-10-02 16:45
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=1806377group_id=180599
Please note that this message will contain a full copy of
Bugs item #1806380, was opened at 2007-10-02 16:52
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=1806380group_id=180599
Please note that this message will contain a full copy of
SourceForge.net a écrit :
Bugs item #1806380, was opened at 2007-10-02 16:52
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=1806380group_id=180599
Please note that this
I would not say totally, given that I am able to run both i386 and amd64
Debian unstable in guest SMP mode.
What is your host OS ? CPU ? KVM ?
--
-Alexey Eremenko Technologov
-
This SF.net email is sponsored by:
Alexey Eremenko a écrit :
I would not say totally, given that I am able to run both i386 and amd64
Debian unstable in guest SMP mode.
What is your host OS ? CPU ? KVM ?
Host: Debian Etch amd64
CPU: Intel Core 2
KVM: 45
--
.''`. Aurelien Jarno | GPG: 1024D/F1BCDB73
: :' :
Aurelien Jarno wrote:
Avi Kivity a écrit :
Aurelien Jarno wrote:
Hi all,
That's not something new, but I never seen the problem mentioned here.
FreeBSD does not work on KVM, approximately since the lapic merge.
However, that does not seem related to lapic, as using
On official web site said:
In progress:
* Paravirtualized networking
* Paravirtualized block device
Where can find sources of that work, if it is possible ?
-
This SF.net email is sponsored by: Microsoft
Defy all
On Tue, 2007-10-02 at 07:59 +0200, Avi Kivity wrote:
Jerone Young wrote:
This is the first of many patches to begin to make kvm source a lot
better for compiling for other architecture support (that is not x86 or
x86-64).
This patch makes it possible so that someone on an x86 machine
Avi Kivity a écrit :
Aurelien Jarno wrote:
Avi Kivity a écrit :
Aurelien Jarno wrote:
Hi all,
That's not something new, but I never seen the problem mentioned here.
FreeBSD does not work on KVM, approximately since the lapic merge.
However, that does not seem related to lapic,
Aurelien Jarno a écrit :
Avi Kivity a écrit :
Aurelien Jarno wrote:
Avi Kivity a écrit :
Aurelien Jarno wrote:
Hi all,
That's not something new, but I never seen the problem mentioned here.
FreeBSD does not work on KVM, approximately since the lapic merge.
However, that does
Aurelien Jarno a écrit :
Aurelien Jarno a écrit :
Avi Kivity a écrit :
Aurelien Jarno wrote:
Avi Kivity a écrit :
Aurelien Jarno wrote:
Hi all,
That's not something new, but I never seen the problem mentioned here.
FreeBSD does not work on KVM, approximately since the lapic
This patch makes things better for cross compiling. It also makes adding
a new architecture to the current make system much easier.
Signed-off-by: Jerone Young [EMAIL PROTECTED]
diff --git a/user/Makefile b/user/Makefile
index 26eb530..9567e8f 100644
--- a/user/Makefile
+++ b/user/Makefile
@@
This adds the ability to change CC, ARCH, LD variables with configure
script in user directory.
Signed-off-by: Jerone Young [EMAIL PROTECTED]
diff --git a/user/configure b/user/configure
index 0bdd3de..20b9367 100755
--- a/user/configure
+++ b/user/configure
@@ -2,13 +2,18 @@
Hello,
Trying to install Windows XP Pro 64bits, the first phase goes quite well (except
that it uses 100% of host's cpu), but crashes when trying to reboot with the
following message:
unhandled vm exit: 0x8021
rax 0095b9e5 rbx 0095b9c0 rcx 0095b9e5 rdx
Hi,
Rebooting a FC6 guest crashes with KVM-45, below is the output.
exception 13 (0)
rax rbx rcx rdx
0600
rsi rdi rsp rbp
r8 r9
Hi Laurent,
This patch looks much cleaner to me.
I see you are saving the regs like this in the patch.
memcpy(c-regs, ctxt-vcpu-regs, sizeof c-regs);
But I don't see any place in the patch these regs getting restored after
failure.
Is it taken care of the code outside of the patch?
Thanks
Anyone know when to release include the following features
Paravirtualized networking
Paravirtualized block device KVM Tap network is slower than Xen. Can we
optimize it?
-
This SF.net email is sponsored by: Microsoft
Defy all
This patch removes duplicate code at vl.c. Once the KVM-only
part defines how much physicall memory it wants, the rest should
be the same for everybody.
Signed-off-by: Glauber de Oliveira Costa [EMAIL PROTECTED]
---
qemu/vl.c | 23 +--
1 files changed, 9 insertions(+), 14
vast yellow wrote:
Anyone know when to release include the following features
# Paravirtualized networking
I have such a code in a separate git repository. It is not yet
production ready.
The next release is a rebase of Rusty code for virtio and some KVM/Qemu
backend.
It probably be ready
On 10/2/07, Glauber de Oliveira Costa [EMAIL PROTECTED] wrote:
@@ -8246,7 +8246,7 @@ int main(int argc, char **argv)
help(1);
if (ram_size PHYS_RAM_MAX_SIZE) {
fprintf(stderr, qemu: at most %d MB RAM can be
simulated\n,
-
This patch removes duplicate code at vl.c. Once the KVM-only
part defines how much physicall memory it wants, the rest should
be the same for everybody.
Signed-off-by: Glauber de Oliveira Costa [EMAIL PROTECTED]
---
qemu/vl.c | 23 +--
1 files changed, 9 insertions(+), 14
48 matches
Mail list logo
