On Tue, Apr 9, 2013 at 9:05 PM, Alex Williamson
alex.william...@redhat.com wrote:
Hi Linus,
Here's one small fix for vfio that I'd like to get in for 3.9;
tightening the range checking around a vfio ioctl. Thanks!
Alex
The following changes since commit
, but the virtio_blk userland seems to freeze.
Any idea what happens here?
./kvm run -d /scratch/rw/fc14_64_image.qcow2 -p root=/dev/vda1
nolapic init=/bin/sh notsc hpet=disable debug
Warning: Forcing read-only support for QCOW
# kvm run -k ../../arch/x86/boot/bzImage -m 320 -c 2 --name guest-9815
eeaarrllyy
On Mon, Jun 6, 2011 at 8:35 AM, Rusty Russell ru...@rustcorp.com.au wrote:
On Sat, 4 Jun 2011 17:37:04 +0200, Christian Dietrich
christian.dietr...@informatik.uni-erlangen.de wrote:
Since printk_ratelimit() shouldn't be used anymore (see comment in
include/linux/printk.h), replace it with
We've don't use Ubuntu (we use Gentoo/KVM 0.12.5) but we've had a
similar problem with kernels 2.6.32-r11 (this is Gentoo specific and
means update -r11 and not release candidate 11) and with the first three
releases of 2.6.34 especially when NFS was involved. We're currently
running
I've had the same issues too. I'm using Gentoo.
Kernel packages 2.6.32-r7 (Release 7 not RC-7)
have had this problem. Haven't tested -r8 to -r10.
Kernel 2.6.32-r11 is currently working fine. 2.6.34
was working too but it crashed after two days with a
clock syncing issue. I'm hopping that
Liang Guo gave me this advice some weeks ago:
you may use kvm-nbd or qemu-nbd to present kvm image
as a NBD device, so
that you can use nbd-client to access them. eg:
kvm-nbd /vm/sid1.img
modprobe nbd
nbd-client localhost 1024 /dev/nbd0
fdisk -l /dev/nbd0
Didn't work for me because I
Thanks for the patch! It seems to solve the problem that
under load ( 50 MBit/s) the network goes down. I've applied
the patch to KVM 0.12.2 running Gentoo. Host and guest is running
kernel 2.6.32 currently (kernel 2.6.30 in guest and 2.6.32 in
host works also for us).
Another host doing the same
Hi,
thanks for that! I've running a lot of hosts still running with
kernel 2.6.30 and KVM 88 without problems. It seems that
all qemu-kvm versions = 0.11.0 have this problem incl.
the latest 0.12.2. So if one of the enterprise distributions
will choose one of this versions for inclusion in there
You can add the option -cpu host to KVM. Then you get
the same cache size information as your host has.
Robert
On 01/22/10 15:31, Hristo Tomov wrote:
Hello!
I have following problem with KVM. I have quad-core processor
Xeon X7350 ( 8MB L2 cache ). The processor shares 4 MB L2 cache
that a segfault of Qemu/KVM can corrupt a whole image
while the host itself was running without any problems as the
segfault happened. Seems that the data is lost. But thanks again
anyway!
Robert
On 01/22/10 15:35, Liang Guo wrote:
2010/1/20 RW k...@tauceti.net mailto:k...@tauceti.net
Some months ago I also thought elevator=noop should be a good idea.
But it isn't. It works good as long as you only do short IO requests.
Try using deadline in host and guest.
Robert
On 01/21/10 18:26, Antoine Martin wrote:
I've tried various guests, including most recent Fedora12 kernels,
currently since tauceti.net is offline until monday. I haven't
tested noop in these benchmarks because of the problems
mentioned above. But it compares deadline and cfq a little bit
on a HP DL 380 G6 server.
Robert
On 01/21/10 22:08, Thomas Beinicke wrote:
On Thursday 21 January 2010 21:08:38 RW
When I start qemu-img with strace I get the output below. Does
this help to to identify the problem?
scotty images # strace qemu-img convert -f qcow2 nweb.img -O raw test.img
execve(/usr/bin/qemu-img, [qemu-img, convert, -f, qcow2,
nweb.img, -O, raw, test.img], [/* 44 vars */]) = 0
brk(0)
I've currently a HP DL 380 G6 server which I can use for some benchmarks
I want to share with you. Maybe someone find it interesting or usefull.
Both host and guest running Gentoo with kernel 2.6.31.1 (which is stable
2.6.31 update 1). The host have the following components:
2 x Intel Xeon CPU
I've read the article a few days ago and it was interesting.
As I upgraded vom 2.6.29 to 2.6.30 (Gentoo) I also saw a dramatic
increase disk and filesystem performance. But then I realized
that the default mode for ext3 changed to data=writeback.
So I changed that back to data=ordered and
15 matches
Mail list logo
