The changes so that the vmwarevga code respects the E820 region runs
afoul of the fact that the VBE bios used has a hard-coded base address
for vesa modes. Thus when syslinux uses VBE to do its graphical bits,
the lfb address doesn't match what the bios thinks it is :-/
Test case is any Fedora
On Wed, 2008-01-02 at 19:13 +0200, Avi Kivity wrote:
Can you try the option '-no-kvm' both with kvm-57 and kvm-58?
-no-kvm works. I can hit this just booting a live CD both on a 32bit
and a 64bit host. It looks like compatibility with old kernels is
broken (the kvm package only contains the
On Sat, 2007-12-01 at 12:10 +0200, Avi Kivity wrote:
Zhang, Xiantao wrote:
I think new archs for kvm doesn't need to care about kvm-abi
case in their code, since current abi is bigger than 10. But in current
libkvm.c, we can see that many abi-specific code in it. How to handle it
?
.
Also ends up being a little bit simpler because we're doing less mucking
around with the timer.
Signed-off-by: Jeremy Katz [EMAIL PROTECTED]
Jeremy
diff --git a/bios/BIOS-bochs-latest b/bios/BIOS-bochs-latest
index c10ae62..e13af69 100644
Binary files a/bios/BIOS-bochs-latest and b/bios/BIOS-bochs
On Wed, 2007-09-12 at 15:19 -0500, Anthony Liguori wrote:
Very cool!
Long-term itch of mine scratched :-)
My mailer doesn't want to quote your patch, but I noticed the following:
+
+/* set the default based on the keypress or menu */
[snip]
But the CMOS memory isn't persisted in
There are cases[1] where you want to be able to pass more ldflags to
qemu's configure. This lets you set LDFLAGS to accomplish that
Signed-off-by: Jeremy Katz [EMAIL PROTECTED]
Jeremy
[1] Such as with the new build-id support in binutils so that you can
pass --build-id to the linker while
On Tue, 2007-06-19 at 11:05 +0300, Avi Kivity wrote:
Richard Hughes wrote:
On Sun, 2007-06-17 at 11:10 +0300, Avi Kivity wrote:
I posted a patchset which does just that, when the F kernel
integrates
it (through inclusion of 2.6.23 or by patching the current kernel),
Fedora will be
On Wed, 2007-01-31 at 12:32 +0200, Avi Kivity wrote:
Jeremy Katz wrote:
Avi Kivity wrote:
I've committed kvm support for host suspend-to-disk (and hopefully
resume too). This means you can suspend your machine with running
vms, and resume it later will all vms returning to the saved
Avi Kivity wrote:
Jeremy Katz wrote:
On Wed, 2007-01-31 at 12:32 +0200, Avi Kivity wrote:
Jeremy Katz wrote:
Avi Kivity wrote:
I've committed kvm support for host suspend-to-disk (and hopefully
resume too). This means you can suspend your machine with running
vms, and resume it later
When using kvm on my laptop, I get the following oops if I try using kvm
after a suspend (ACPI S3)/resume cycle. At first I thought it went away
if I unloaded the module before suspending and then reloading it
afterwards, but I can't reproduce that working now, so I might have just
been
On Thu, 2006-12-21 at 11:20 +0200, Avi Kivity wrote:
Jeremy Katz wrote:
Currently, kvm ends up just using the standard qemu cpu initialization.
This means that all x86_64 virtual machines appear to have an
AuthenticAMD (AMD64) processor. This ends up causing a problem when
booting some
Currently, kvm ends up just using the standard qemu cpu initialization.
This means that all x86_64 virtual machines appear to have an
AuthenticAMD (AMD64) processor. This ends up causing a problem when
booting some x86_64 Linux kernels as they attempt to do AMD64 specific
initialization for
12 matches
Mail list logo
