Christian Ehrhardt wrote:
Hi,
while working on the embedded powerpc port for kvm we have a lot of
dependencies on current qemu 0.9.0 code for ppc support. Internally we
currently run with a modified qemu, but eventually strive for integration
with kvm-userspace. Therefor I wanted to ask if
Hi Avi,
We also the similar problems, when we enable kvm/ipf. You know,
Qemu doesn't work on IPF both at host and guest sides.
So, we have some changes, and new-added stuffs to current Qemu code. Do
you think which tree we should push them to? Qemu upstream
or kvm-userspace?
Thanks
Zhang, Xiantao wrote:
Hi Avi,
We also the similar problems, when we enable kvm/ipf. You know,
Qemu doesn't work on IPF both at host and guest sides.
So, we have some changes, and new-added stuffs to current Qemu code. Do
you think which tree we should push them to? Qemu upstream
or
Avi Kivity wrote:
Laurent Vivier wrote:
(Yes, I know, it's again another bug I've introduced into KVM...)
To avoid this, I suggest that Nitin and yourself review each other's
patches. While I review every patch I commit, it works much better when
someone who's involved daily with the
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 registers like RSI or RDI. Moreover,
Bugs item #1805519, was opened at 2007-10-01 11:31
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=1805519group_id=180599
Please note that this message will contain a full copy of
Tobias Brink escribió:
Avi Kivity [EMAIL PROTECTED] writes:
Tobias Brink wrote:
I have a probably similar problem with OpenBSD 4.1 and kvm-37 and
kvm-39 (didn't have time to test any further versions). Kernel is
2.6.22-gentoo-r5 and processor is Intel Core2 Quad. I use the modules
Hello all,
After solving my problems installing OpenBSD 4.1 in KVM, I tried to
install Ubuntu 7.04 Feisty Fawn. The problem is that it gets stuck in a
black screen without having said anything at all. After some testing
with other isos I thought it could be related to the graphical
bootloader
hi,
after i try to merge centos and fedora kvm-36 spec files and patches
(ethernet qemu fix etc) and start the guests on the new kvm host the
guest install. the only thing what i got in qemu vnc window:
serial0 console
so the guest not even start to boot.
anybody has any tip?
may be the bios
Miguel Araujo wrote:
Hello all,
After solving my problems installing OpenBSD 4.1 in KVM, I tried to
install Ubuntu 7.04 Feisty Fawn. The problem is that it gets stuck in a
black screen without having said anything at all. After some testing
with other isos I thought it could be related to
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 can cross
compile for an x86-64 machine and vice versa. So now you will have
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 int80
instruction from a guest? A pointer to an answer is just as good as
an answer itself.
The
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
int80 instruction from a guest? A pointer to an answer is just as
good as an
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
int80 instruction from a guest? A pointer to an answer is
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 cannot span directories, but
once that's solved, we'll do that as this is most consistent with the
rest of the kernel.
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 cannot span directories, but
once that's solved, we'll do
This was committed in 1d55c096cce99f069d9ac8e3b2195d45adce9549 on Feb 7,
and clearly never actually compiled.
---
kernel/external-module-compat.h |6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/kernel/external-module-compat.h b/kernel/external-module-compat.h
index
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 can cross
compile for an x86-64 machine and vice versa. So
18 matches
Mail list logo
