From: Henrik Holst <henrik@witsbits.com>
To: Avi Kivity <avi@redhat.com>
Cc: KVM list <kvm@vger.kernel.org>
Subject: Re: [ANNOUNCE] kvm-77 release
Date: Mon, 13 Oct 2008 11:33:35 +0200 [thread overview]
Message-ID: <1223890415.6127.30.camel@henrik-desktop> (raw)
In-Reply-To: <48F1E742.7080902@redhat.com>
sön 2008-10-12 klockan 14:02 +0200 skrev Avi Kivity:
> This release fixes the -std-vga regression which bothered those of us
> who have large or widescreen monitors (note the option is now named
> '-vga std' due to upstream qemu changes). Other significant changes
> include better disk performance if you have a fast host storage subsystem.
>
> Changes from kvm-76:
> - merge bochs-bios-cvs
> - merge qemu-svn
> - more -cpu options
> - faster disk emulation (esp. with scsi/virtio)
> - improved NMI support (Jan Kiszka)
> - improve >4GB memory support (Alex Williamson)
> - memory alias cleanups (Glauber Costa)
> - fix kvmtrace segfault (Ryota OZAKI)
> - make external module compile on split source/object configs (Alexander
> Graf)
> - allows compiling on opensuse
> - fix -std-vga regression
> - fix migration failure at end of migration protocol
> - map mmio pages for device assignment (Weidong Han)
> - silence lapic kernel messages (Jan Kiszka)
> - fix vcpu reset (Gleb Natapov)
> - fix missed invlpg on EPT-enabled machines with EPT disabled (Marcelo
> Tosatti)
> - device assignment on ia64 (Xiantao Zhang)
> - memory type support on EPT (Sheng Yang)
>
>
> Notes:
> If you use the modules bundled with kvm-77, you can use any version
> of Linux from 2.6.16 upwards. You may also use kvm-77 userspace with
> the kvm modules provided by Linux 2.6.25 or above. Some features may
> only be available in newer releases.
>
> http://kvm.qumranet.com
>
>
We have encountered a regression with kvm-77 here, we previously ran
kvm-74 so I am not yet sure if this regression was introduced in 77 or
76,75 (I will try and test these versions asap).
Ubuntu-8.10-server-amd64 cannot find the drive (tested with ide, scsi and virtio). Log on the guest screen:
*** glibc detected *** modprobe: realloc(): invalid next size: 0x0000000000f95cb0 ***
Aborted
*** glibc detected *** modprobe: realloc(): invalid next size: 0x0000000001247cb0 ***
Aborted
*** glibc detected *** modprobe: realloc(): invalid next size: 0x00000000025a8cb0 ***
Aborted
*** glibc detected *** modprobe: realloc(): invalid next size: 0x0000000001529cb0 ***
Aborted
*** glibc detected *** modprobe: realloc(): invalid next size: 0x0000000001276cb0 ***
Aborted
*** glibc detected *** modprobe: realloc(): invalid next size: 0x0000000001bf1cb0 ***
Aborted
udevd[915]: add_to_rules: invalid rule '/etc/udev/rules.d/05-options.rules:1'
udevd[915]: add_to_rules: invalid rule '/etc/udev/rules.d/05-options.rules:2'
udevd[915]: add_to_rules: invalid rule '/etc/udev/rules.d/05-options.rules:3'
udevd[915]: add_to_rules: invalid rule '/etc/udev/rules.d/05-options.rules:4'
and on and on, ending with the system complaning that it cannot find the
drive with the old UUID value. Booting the very same image on kvm-74
produced none of these errors what so ever.
If giving the guest more than 2GiB of memory there is a stream of
"segmentation fault" lines, probably from modprobe
Ubuntu-8.04 boots just fine under kvm-77 so it feels like a mismatch
with the guest 2.6.27 kernel. Tested both 2.27-4 and 2.27-7 to no avail.
The host is Debian Lenny with a 2.6.26-1-amd64 kernel and a Q6600 with
8GB RAM
/Henrik Holst
Witsbits AB
next prev parent reply other threads:[~2008-10-13 9:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-12 12:02 [ANNOUNCE] kvm-77 release Avi Kivity
2008-10-12 18:18 ` Don Parsons
2008-10-17 15:08 ` APIC problems with kvm-77 (was Re: [ANNOUNCE] kvm-77 release) Carlo Marcelo Arenas Belon
2008-10-17 17:15 ` Sheng Yang
2008-10-17 23:46 ` APIC problems with kvm-77 (was Re: [ANNOUNCE] kvm-77 release) SOLVED Donald Parsons
2008-10-13 9:33 ` Henrik Holst [this message]
2008-10-13 9:44 ` [ANNOUNCE] kvm-77 release Henrik Holst
2008-10-13 11:40 ` Henrik Holst
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1223890415.6127.30.camel@henrik-desktop \
--to=henrik@witsbits.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox