Re: KVM on Debian

Aaron Clausen wrote: [] is too old to support this. Is there a reasonably safe way of upgrading to one of the newer versions of KVM on this server? Can't say for "safe" but you can grab my .debs which I use here on a bunch of machines, from http://www.corpit.ru/debian/tls/kvm/ - both binaries

Re: slow guest performance with build load, looking for ideas

Avi Kivity wrote: On 06/15/2009 05:15 PM, Erik Jacobson wrote: [] So if I understand what you're saying: best not to use kvm guests for build servers with pre-Nehalem processors. pre-Nehalem / pre-Barcelona, > 4 vcpus, yes. How about 2 vcpus, and how about AMD processors ? Thanks /mjt --

Re: slow guest performance with build load, looking for ideas

Avi Kivity wrote: On 06/15/2009 06:25 PM, Michael Tokarev wrote: Avi Kivity wrote: On 06/15/2009 05:15 PM, Erik Jacobson wrote: [] So if I understand what you're saying: best not to use kvm guests for build servers with pre-Nehalem processors. pre-Nehalem / pre-Barcelona, > 4 vc

smp guest questions

After seeing words from Avi about that smp guests are ok now, I descided to try. And immediately got a few questions. Running on a Phenom 9750 machine (PhenomI), AMD780G chipset. Host is 2.6.29 x86-64, qemu-kvm 0.10.5, guests are linux with kvm paravirt bits enabled, also dynticks (on both host

Re: smp guest questions

Avi Kivity wrote: On 06/17/2009 11:38 AM, Michael Tokarev wrote: After seeing words from Avi about that smp guests are ok now, I descided to try. And immediately got a few questions. Running on a Phenom 9750 machine (PhenomI), AMD780G chipset. Host is 2.6.29 x86-64, qemu-kvm 0.10.5, guests

a few words about drive/pci add/remove

I tried drive hot add/remove today. And immediately had a few.. issues. qemu-kvm-0.10.5. First of all, there are several "definitions" of drive_add and several others in `help' monitor command output: This one appears to be real: drive_add pci_addr=[[:]:] [file=file][,if=type][,bus=n] [,unit=m]

Re: a few words about drive/pci add/remove

Mark McLoughlin wrote: On Wed, 2009-06-17 at 17:44 +0400, Michael Tokarev wrote: WARNING: at drivers/base/core.c:122 device_release+0x5f/0x70() Device 'virtio8' does not have a release() function, it is broken and must be fixed. This should be fixed in 2.6.29 Yes indeed, 2

Re: smp guest questions

ervals. Maybe some "random glitch", I dunno ;) In any way, since I can't provide more information about all this despite all my attempts to reproduce the situation.. I consider this issue closed, for now anyway. But let it be archived for future refefence :) Thanks! /mjt Michael Tokare

Re: VGA pass-through

Han, Weidong wrote: [] Currently VGA pass-through is not supported in KVM. It needs much work to support it. What does it need? Here's what I know of: - load the vga bios at 0xc - implement whatever main bios interfaces the vga vios expects - pass through the vga I/O ports Anything else

Re: VGA pass-through

Han, Weidong wrote: Michael Tokarev wrote: [] But how about using it as a "secondary" video card? Like, I can plug another add-on vga card into a free PCI slot and tell X to use that one instead of "default" card. Can kvm work like this? "secondary" means sec

Re: VGA pass-through

Han, Weidong wrote: Michael Tokarev wrote: Han, Weidong wrote: Michael Tokarev wrote: [] But how about using it as a "secondary" video card? Like, I can plug another add-on vga card into a free PCI slot and tell X to use that one instead of "default" card. Ca

Re: kvm-87 static build failure: cannot find -lpci

Antoine Martin wrote: [] LINK x86_64-softmmu/qemu-system-x86_64 /usr/lib/gcc/x86_64-pc-linux-gnu/4.3.2/../../../../x86_64-pc-linux-gnu/bin/ld: cannot find -lpci What gives? Is it your system or who's? Why the system does not have a usable libpci.a is a question for you, not for kvm... I g

kvm, drbd, elevator, rotational - quite an interesting co-operation

Hello. I'm new on drbd-user@, but long-time user of kvm. [A side note: drbd-user@ appears to be subscribers-only list. Sad consequence of spammers activity... I doubt many knowlegeable people on kvm@ are subscribed to drbd-user@ to be able to post there. Oh well.] Today I tried drbd for th

Re: kvm, drbd, elevator, rotational - quite an interesting co-operation

Javier Guerra wrote: On Thu, Jul 2, 2009 at 2:55 PM, Michael Tokarev wrote: kvm: i/o threads - should there be a way to control the amount of threads? With default workload generated by drbd on secondary node having less thread makes more sense. +1 on this. it seems reasonable to have

Re: [ANNOUNCE] kvm-88 release

Avi Kivity wrote: [] # /usr/local/bin/qemu-system-x86_64 -hda /home/jrr/vista-x86_64.img -m 1536M -net nic,vlan=0,macaddr=52:54:00:12:32:00 -net tap,vlan=0,ifname=tap1 -vga std -full-screen -smp 2 -usb -usbdevice tablet Can you try without -full-screen? Without -vga std? Note -usbdevice tab

Re: init scripts for KVM guests UPDATE!

Saman Behnam wrote: Hi there, here is an update for the "init scripts for KVM guests"I've wrote for starting and stopping the KVM guest machines either by saving and restoring or by gracefully shutdown and start. My question, is there an option within "libvirt" to make the KVM guest mashines ge

This combination of AMDprocessors is not suitable for SMP?

(yes there's no typo in $subject, it's an old formatting bug in printk). When booting kvm guest on an AMD CPU, guest kernel prints this warning: WARNING: This combination of AMDprocessors is not suitable for SMP. be it SMP or UP guest. What's wrong with this "combination", and can it be fixed

Re: kvm monitor socket - connection refused

28.06.2011 23:20, Iordan Iordanov wrote: > Hello, > > We are using KVM on Debian Squeeze (QEMU 0.12.5). Yesterday, I started a > virtual machine and let it run overnight. I don't recall doing anything > out of the ordinary to it. > > This morning, I wanted to issue some commands to it through the

Re: kvm monitor socket - connection refused

29.06.2011 19:20, Iordan Iordanov wrote: > > > On 06/28/11 18:29, Michael Tokarev wrote: >> The process listening on this socket no longer exist, >> it finished. With this command line it should stay in >> foreground till finished (there's no -daemonize etc), >

[heads-up] bridge in kernel 3.0~ and dhcp from kvm guest on tap device

The combination in $subject apparently stopped working -- I'm running 3.0-rc6 kernel on host where it doesn't work. The setup is -- a bridge, br0, to which host eth0 and guest tap devices are connected. When KVM guest boots, it tries to send DHCP requests to its ethernet device (it does not matte

guest suspend/resume & virtio: vring errors

I tried suspend/resume cycle for a linux guest today, with 100% failure result. There are 2 possible scenarious after resume (you need pretty recent guest kernel for it to work at all, earlier kernels, incl. early 2.6.32, just stops somewhere at the start of suspend cycle, but 2.6.32.42 and 3.0-rc

Re: guest suspend/resume & virtio: vring errors

09.07.2011 13:17, Gleb Natapov wrote: > On Fri, Jul 08, 2011 at 11:02:54PM +0400, Michael Tokarev wrote: >> I tried suspend/resume cycle for a linux guest >> today, with 100% failure result. There are 2 > Good. It works as expect :) Linux virtio drivers do not support PM. This

Re: guest suspend/resume & virtio: vring errors

09.07.2011 13:55, Gleb Natapov wrote: > On Sat, Jul 09, 2011 at 01:47:25PM +0400, Michael Tokarev wrote: >> 09.07.2011 13:17, Gleb Natapov wrote: >> This means that neither in-guest suspend/resume nor >> qemu-kvm migrate-to-file (which fails for a different >> rea

Re: guest suspend/resume & virtio: vring errors

09.07.2011 14:36, Gleb Natapov wrote: > On Sat, Jul 09, 2011 at 02:09:46PM +0400, Michael Tokarev wrote: >>> Heh. Is this S4 or S3 suspend resume? Looks like recent breakage. >>> The only knows problem to me is in win7/2008 S3 resume + net. >> >> How can I know i

Re: [PATCH] init: Support mounting devices from kernel command line

18.07.2011 15:55, Pekka Enberg wrote: > On Mon, Jul 18, 2011 at 12:06 PM, Sasha Levin wrote: >> This patch adds support to mounting devices using a kernel parameter. >> >> Such feature is usefull for virtual guests. It allows easily automating >> mounts without having to change the base image (whi

major slowdown in i/o (due to high CPU usage) from 2.6.32 to current

It all started by Svante Signell on IRC, see http://bugs.debian.org/634149 . The short story: running hurd guest image (on ide drive); when changing only host kernel from 2.6.32 to (in my case) 3.0.0-rc7, the i/o (especially write) speed of the guest reduces dramatically, as is host CPU usage. I

Re: network boot always enabled with 0.15.0

11.08.2011 17:59, Gleb Natapov wrote: > On Thu, Aug 11, 2011 at 01:57:04PM +, Dietmar Maurer wrote: [] >> Another possibility to disable network boot would be to avoid loading >> the pxe-XXX.rom network boot ROMs. Or is that a bad idea? >> > Ah yeah. Don't see anything bad if you do not what t

0.15: is glib actually needed?

Each time I build qemu-kvm, my build script complains that it is needlessly linked against libglib-2.0 without using any symbols from that library. So is glib really needed for qemu-kvm? How it's different from qemu-0.15? Thanks, /mjt -- To unsubscribe from this list: send the line "unsubscribe

linux guest + nfsserver + virtio + vhost + vnet_hdr = tons of OOMs

I were debugging an unrelated issue today (in nfs server), and noticed that the above combination, when doing lots of read requests from an nfs client, quickly reaches OOM condition which gets triggered very often. I used a 512-Mb guest with 32bit kernel inside. By doing a cp of a large directory

TSC in qem[-kvm] 1.1+ and in-kernel irqchip

As a follow-up to the patch "tsc: use kvmclock for calibration". There's another problem reported by several users. The sympthom is that grub does not show boot menu, it boots default entry right away without any pause. After quite some debugging it turned out to be TSC issue. Grub uses tsc for

Re: TSC in qem[-kvm] 1.1+ and in-kernel irqchip

On 10.08.2012 00:47, Marcelo Tosatti wrote: [] >>> calibrate_tsc (void) >>> { >>> /* First calibrate the TSC rate (relative, not absolute time). */ >>> grub_uint64_t start_tsc; >>> grub_uint64_t end_tsc; >>> >>> start_tsc = grub_get_tsc (); >>> grub_pit_wait (0x); >>> end_tsc = grub

Re: [Qemu-devel] TSC in qem[-kvm] 1.1+ and in-kernel irqchip

On 10.08.2012 11:33, Gleb Natapov wrote: > On Thu, Aug 09, 2012 at 10:27:43PM +0400, Michael Tokarev wrote: >> As a follow-up to the patch "tsc: use kvmclock for >> calibration". >> >> There's another problem reported by several users. >> The symp

Re: [Qemu-devel] TSC in qem[-kvm] 1.1+ and in-kernel irqchip

On 12.08.2012 12:10, Gleb Natapov wrote: [] > Any chance to bisect it? The bisecion leads to this commit: commit 17ee47418e65b1593defb30edbab33ccd47fc1f8 Merge: 13b0496 5d17c0d Author: Jan Kiszka Date: Tue Apr 10 16:26:23 2012 +0200 Merge commit '5d17c0d2df4998598e6002b27b8e47e792899a0f'

Re: [Qemu-devel] TSC in qem[-kvm] 1.1+ and in-kernel irqchip

On 13.08.2012 17:07, Jan Kiszka wrote: [] >> The bisecion leads to this commit: >> >> commit 17ee47418e65b1593defb30edbab33ccd47fc1f8 >> Merge: 13b0496 5d17c0d >> Author: Jan Kiszka >> Date: Tue Apr 10 16:26:23 2012 +0200 >> >> Merge commit '5d17c0d2df4998598e6002b27b8e47e792899a0f' into >>

Re: [PATCH uq/master] kvm: i8254: Finish time conversion fix

On 13.08.2012 22:18, Jan Kiszka wrote: > 0cdd3d1444 fixed reading back the counter load time from the kernel > while assuming the kernel would always update its load time on writing > the state. That is only true for channel 1, and so pit_get_channel_info > returned wrong output pin states for high

Re: KVM-enabled Linux 3.2 won't boot in kvm

19.08.2012 06:04, Neal Murphy пишет: > I've been using KVM for a few years now. I've had little trouble with it. But > now it's got me treed. I cannot get a KVM-enabled Linux 3.2.27 kernel to boot > in qemu-kvm unless I specify '-no-kvm'. I've used a similarly-built and - > configured 2.6.35 kern

Re: [Qemu-devel] x86, nops settings result in kernel crash

On 20.08.2012 21:13, Tomas Racek wrote: [] Can we trim the old, large and now not-so-relevant discussion please? ;) > I can provide you with more different traces if it can help. But I thought > that maybe it will be more useful for you to try it on your own. So I've > prepared some minimal debi

Re: qemu-kvm 1.1.1 hangs using 100% CPU when using ES1370 emulation

Thank you! /mjt > cpu model: AMD Turion(tm) II Neo N40L Dual-Core Processor > qemu-kvm version: 1.1.1 (Debian package by Michael Tokarev), > happened also with 1.1.0 > host: Debian wheezy, 3.2.23, x86_64 > guest: Debian wheezy, 3.2.23, x86_64 > > /usr/bin

Re: [ANNOUNCE] qemu-kvm-1.2.0-rc1

On 24.08.2012 23:12, Marcelo Tosatti wrote: > > qemu-kvm-1.2.0-rc1 is now available. This release is based on the > upstream qemu 1.2.0-rc1, plus device assignment. Is there a corresponding tag in the git tree? Thanks, /mjt -- To unsubscribe from this list: send the line "unsubscribe kvm" in th

Re: [Qemu-devel] [PATCH 4/4] kvm: i386: Add classic PCI device assignment

On 27.08.2012 22:56, Blue Swirl wrote: [] >> +static uint32_t slow_bar_readb(void *opaque, target_phys_addr_t addr) >> +{ >> +AssignedDevRegion *d = opaque; >> +uint8_t *in = d->u.r_virtbase + addr; > > Don't perform arithmetic with void pointers. There are a few places in common qemu cod

Re: /dev/kvm not sufficiently restricted, and in ways I didn't think were possible

On 28.08.2012 00:11, Henry Cejtin wrote: > I'm completely confused about access to /dev/kvm. In particular, it > looks like it is too open to access, but in a way that I don't > understand. > > On my machine, /dev/kvm is owned by root.root and mode 660. Here is the > output of ls:

Re: KVM got slow after adding more physical memory to host - SOLVED

On 06.09.2011 23:22, Nikola Ciprich wrote: > Hello guys, > > thanks to both of You for Your replies. The problem is solved, > exactly as Avi said, the DMA in windows got somehow disabled. > So this certainly was not related to adding the memory... > > anyways, note for further generations: > in w

Re: virtio localdisk performance

On 13.10.2011 13:05, benoit ROUSSELLE wrote: > Hello, > > Can someone running with virtio tell me if this is normal to have such > a difference with dd between host and guest machine ? > host dd is 500MB/s > guest dd is 150MB/s > > All other questions are optionnal for now :D Well, one question

Re: cannot create VM with image on zfs filesystem (zfsonlinux)

On 07.11.2011 17:57, Peter Lees wrote: > when trying to create a VM using a RAW image on a zfs filesystem, i get an > "invalid argument" error. [] > qemu: could not open disk image /space/vm_store/elveros_001.raw: Invalid > argument Please run qemu under strace to show what exactly it is doing.

Re: [regression] KVM: hangs and "irq timeout" booting HURD unless -no-kvm-irqchip passed

08.02.2011 04:40, Jonathan Nieder wrote: > Gleb Natapov wrote: > >> Is this patch helps? >> >> diff --git a/arch/x86/kvm/i8259.c b/arch/x86/kvm/i8259.c >> index 3cece05..62b1dde 100644 >> --- a/arch/x86/kvm/i8259.c >> +++ b/arch/x86/kvm/i8259.c >> @@ -549,6 +549,9 @@ static void pic_irq_request(st

Q: status of kvm/ subdir in qemu-kvm tarball?

What's the current status of files in kvm/ subdirectory in the qemu-kvm distribution (0.14 or git) ? As far as I can see, all that is old and unused stuff, which only confuses users. It is not used during build the Makefiles are obsolete and refers to non-existed files/directories, some remaining

Re: Q: status of kvm/ subdir in qemu-kvm tarball?

23.02.2011 14:31, Jan Kiszka wrote: > On 2011-02-23 12:04, Michael Tokarev wrote: >> What's the current status of files in kvm/ subdirectory >> in the qemu-kvm distribution (0.14 or git) ? [] > I think there are a few bits still in use: > > - kvm/kvm_stat this is a

Re: Q: status of kvm/ subdir in qemu-kvm tarball?

23.02.2011 15:58, Jan Kiszka wrote: > On 2011-02-23 12:42, Michael Tokarev wrote: [] >>> - kvm/include (latest kernel headers) *) >> >> This directory is always used (in configure) >> unless -kerneldir is specified - who uses that >> nowadays? I dunno. &g

Re: Q: status of kvm/ subdir in qemu-kvm tarball?

23.02.2011 16:45, Jan Kiszka wrote: > On 2011-02-23 14:15, Michael Tokarev wrote: [] >> It only matters if you want to build qemu-kvm for OLDER >> kernel without support of some features which are used by >> the userspace you're building. Provided 3 things: >

Re: Out-dated Qemu link on http://www.linux-kvm.org/Main_page

24.02.2011 12:08, Philipp Hahn wrote: > Hello, > > On in the "Common External Pages" > sections the "QEMU" link links to the out-dated Fixed, the link is set up to point to www.qemu.org. Thanks! /mjt -- To unsubscribe from

Re: 2.6.35.11 + qemu-kvm 0.14.0 + Windows XP RDP access = unstable

08.03.2011 09:43, Thomas Løcke wrote: > Hey all, Hello again Thomas! :) > I have 9 Windows XP guests running on a KVM host. The host is > Slackware 13.1 x86_64 with kernel 2.6.35.11. > > All the guests are being accessed using the built-in RDP server in > Windows XP. This worked perfectly with q

Re: 2.6.35.11 + qemu-kvm 0.14.0 + Windows XP RDP access = unstable

08.03.2011 11:08, Thomas Løcke wrote: [] >>> -net nic,macaddr=de:ad:be:ef:00:15,model=virtio \ >>> -net tap,ifname=tap_15,script=no,downscript=no \ >> >> Try switching from the obsolete -net tap to current >> -netdev syntax. See docs/qdev-device-use.txt in the >> qemu(-kvm) source tarball.

Re: 2.6.35.11 + qemu-kvm 0.14.0 + Windows XP RDP access = unstable

08.03.2011 09:43, Thomas Løcke wrote: [] > 2.6.35.11 + 0.13.0 = Flawless operation. It just hums along. > 2.6.35.11 + 0.14.0 = The connection to the internal Windows XP RDP > server breaks every 5-10 minutes. I ran winXP with 4 parallel RDP connections for over a hour here, "watching" some

Re: [Qemu-devel] segmentation fault in qemu-kvm-0.14.0

09.03.2011 10:26, Stefan Weil wrote: > Am 08.03.2011 23:53, schrieb Peter Lieven: >> Hi, >> >> during testing of qemu-kvm-0.14.0 i can reproduce the following >> segfault. i have seen similar crash already in 0.13.0, but had no time >> to debug. >> my guess is that this segfault is related to the t

FreeBSD boot hangs on qemu-kvm on AMD host

Hello. Dominik Klein (Cc'd) reported on irc that current FreeBSD release hangs at boot in qemu-kvm. It is trivially verifiable by d/loading the bootonly FreeBSD 8.2 CD image from ftp.freebsd.org and running kvm -cdrom FreeBSD-8.2-RELEASE-amd64-bootonly.iso. The guest unpacks kernel, draws a m

Re: FreeBSD boot hangs on qemu-kvm on AMD host

09.03.2011 15:50, Avi Kivity wrote: > On 03/09/2011 02:06 PM, Michael Tokarev wrote: >> Hello. >> >> Dominik Klein (Cc'd) reported on irc that current >> FreeBSD release hangs at boot in qemu-kvm. It is >> trivially verifiable by d/loading the bootonly >&g

Re: FreeBSD boot hangs on qemu-kvm on AMD host

09.03.2011 17:24, Gleb Natapov пишет: > On Wed, Mar 09, 2011 at 03:03:49PM +0200, Avi Kivity wrote: >> On 03/09/2011 02:59 PM, Michael Tokarev wrote: >>>> Please post the output of >>>> >>>>info register >>> >>> And this is

Re: FreeBSD boot hangs on qemu-kvm on AMD host

09.03.2011 18:38, Avi Kivity пишет: > On 03/09/2011 04:53 PM, Dominik Klein wrote: >> > Please try kvm.git and >> > report, it's likely fixed. >> >> With kvm.git kernel it works. >> >> Here's what I did: >> >> git clone git://git.kernel.org/pub/scm/virt/kvm/kvm.git >> cd kvm >> cp /boot/config-$(

Re: FreeBSD boot hangs on qemu-kvm on AMD host

09.03.2011 19:26, Avi Kivity wrote: > Sorry, I misread. So kvm.git works, we just have to identify what patch > fixed it. > > What's the last kernel that *didn't* work for you? 2.6.38-rc8 does not work - verified by Dominik. But kvm.git works. I know it warrants a very nice bisection :) /mjt

Re: FreeBSD boot hangs on qemu-kvm on AMD host

09.03.2011 19:34, Avi Kivity wrote: [] >>> > Sorry, I misread. So kvm.git works, we just have to identify what patch >>> > fixed it. >>> 2.6.38-rc8 does not work - verified by Dominik. >>> But kvm.git works. >> There's some chance it's e5d135f80b98b0. > If you apply it, also apply the followin

openbsd system_powerdown: "KVM internal error. Suberror: 1"

Hello. I installed an openbsd 4.8 image today to play with, and noticed that when issuing "system_powerdown" in kvm monitor, in about 5 seconds, qemu-kvm spews this message in a tight loop: KVM internal error. Suberror: 1 emulation failure KVM internal error. Suberror: 1 emulation failure ..

*insane* amount of host_state_reloads for openbsd guest in 0.14

I tried Openbsd 4.8 in kvm today and immediately noticed that it is running _very_ slow, boot takes several minutes to complete to the "login:" prompt. After investigating I found that kvm does really insane amount of host_state_reloads. Here are typical kvm_stats: During bootup while checking/mo

Re: *insane* amount of host_state_reloads for openbsd guest in 0.14

16.03.2011 22:48, Marcelo Tosatti wrote: > On Fri, Mar 11, 2011 at 03:02:33PM +0300, Michael Tokarev wrote: >> I tried Openbsd 4.8 in kvm today and immediately noticed >> that it is running _very_ slow, boot takes several minutes >> to complete to the "login:" pr

Re: openbsd system_powerdown: "KVM internal error. Suberror: 1"

16.03.2011 22:44, Marcelo Tosatti wrote: > On Fri, Mar 11, 2011 at 02:54:00PM +0300, Michael Tokarev wrote: >> Hello. >> >> I installed an openbsd 4.8 image today to play with, >> and noticed that when issuing "system_powerdown" in >> kvm monitor, in abou

Re: openbsd system_powerdown: "KVM internal error. Suberror: 1"

17.03.2011 20:52, Marcelo Tosatti wrote: [] > iret emulation is only partially implemented. Why is iret faulting > in the first place i don't know. Can you enable tracing with > > echo kvm > /$debugfs/tracing/set_event > > And save the tail of the log, including events at $RIP? Something like t

Re: openbsd system_powerdown: "KVM internal error. Suberror: 1"

21.03.2011 12:43, Avi Kivity wrote: > On 03/17/2011 10:18 PM, Michael Tokarev wrote: [] >> 47965.428791: kvm_exit: reason npf rip 0xd020203a >> 47965.428791: kvm_page_fault: address bfff0 error_code 4 >> 47965.428792: kvm_emulate_insn: 0:d020203a: 5a (prot32) >> 4

Re: KVM lock contention on 48 core AMD machine

21.03.2011 20:12, Eric Dumazet wrote: > Le lundi 21 mars 2011 à 19:02 +0200, Avi Kivity a écrit : > >> Any ideas on how to fix it? We could pre-allocate IDs and batch them in >> per-cpu caches, but it seems like a lot of work. >> > > Hmm, I dont know what syscalls kvm do, but even a timer_getti

Re: What are the rules for hyperthreaded CPUs?

On 05.12.2011 05:26, Todd And Margo Chester wrote: >> Hi All, >> >> My host has an i7-960 processor (4 cores, 8 hypterthreaded cores.) >> /proc/cpuinfo on my host shows 8 processors. >> >> On my Fedora Core 16 guest, /proc/cpuinfo shows 4 processors. >> >> Question: what is the maximum number of pr

winXP "Standard PC" HAL and qemu-kvm >= 0.15

As it turned out, a windowsXP machine does not work in qemu-kvm >= 0.15 (it loses network and USB entirely) if it is using "Standard PC" HAL. In 0.14 it worked fine, but not in 0.14 (I haven't tried any in-between versions yet). There are several HAL types available in winXP: these are "Uniproces

Re: winXP "Standard PC" HAL and qemu-kvm >= 0.15

On 05.12.2011 17:28, Avi Kivity wrote: [] >> I haven't debugged further yet, -- because it were >> not easy to find out what was causing the regression >> and how to reproduce it, and also because I don't think >> it is the right HAL for qemu-kvm guest anyway. > > It's not, but the regression indi

Re: winXP "Standard PC" HAL and qemu-kvm >= 0.15

On 06.12.2011 14:32, Avi Kivity wrote: > On 12/05/2011 10:19 PM, Michael Tokarev wrote: >> On 05.12.2011 17:28, Avi Kivity wrote: >> [] >>>> I haven't debugged further yet, -- because it were >>>> not easy to find out what was causing the regression >

Re: winXP "Standard PC" HAL and qemu-kvm >= 0.15

On 06.12.2011 16:27, Michael S. Tsirkin wrote: > On Tue, Dec 06, 2011 at 03:02:49PM +0400, Michael Tokarev wrote: [] >> And after applying Avi's instructions here's the real bisect >> result: >> >> ab431c283e7055bcd6fb622f212bb29e84a6a

Re: [Qemu-devel] winXP "Standard PC" HAL and qemu-kvm >= 0.15

[Added Jan Kiszka to Cc] On 06.12.2011 18:45, Michael Tokarev wrote: [complete thread: http://thread.gmane.org/gmane.comp.emulators.kvm.devel/82705] > More data points (all against qemu-kvm-0.15.0). > > First, as Avi pointed out, this patch references PIC which is > used by standa

Re: winXP "Standard PC" HAL and qemu-kvm >= 0.15

On 06.12.2011 20:38, Jan Kiszka wrote: > On 2011-12-06 17:29, Michael Tokarev wrote: [] >> It appears there are two issues here, one is fixed by >> 09de0f469c3c2a277c7874f6c60992c8b94719a9 and is 32bit-only, and >> another bisect leads to this commit:

Re: winXP "Standard PC" HAL and qemu-kvm >= 0.15

On 06.12.2011 20:57, Michael Tokarev wrote: > On 06.12.2011 20:38, Jan Kiszka wrote: >> On 2011-12-06 17:29, Michael Tokarev wrote: > [] >>> It appears there are two issues here, one is fixed by >>> 09de0f469c3c2a277c7874f6c60992c8b94719a9 and is 32bit-only, and &g

Re: winXP "Standard PC" HAL and qemu-kvm >= 0.15

On 06.12.2011 22:21, Jan Kiszka wrote: [] >> For the 0.15 .. 1.0 change, the first commit which restores the (broken >> in 0.15) functionality is this one: >> >> commit 86fbf97ceb4a9c46a609dd4ae053ba4262b68fe8 >> Author: Jan Kiszka >> Date: Fri Oct 7 09:19:45 2011 +0200 >> >> i8259: Clear EL

Re: winXP "Standard PC" HAL and qemu-kvm >= 0.15

[Removed some people from the Cc list] On 06.12.2011 22:45, Michael Tokarev wrote: [] >> git://git.kiszka.org/qemu-kvm.git queues/kvm-irqchip > > This tree does not boot for me at all (on regular x86-64 setup) - > it stays in bios after "Booting from hard disk" wit

Re: [Qemu-devel] winXP "Standard PC" HAL and qemu-kvm >= 0.15

On 07.12.2011 01:12, Jan Kiszka wrote: > On 2011-12-06 21:58, Jan Kiszka wrote: [] >> How embarrassing. Messed something up, maybe during rebase, and forgot >> to retest non-irqchip mode. Will fix and repost. > > Was even worse, a simple -ENOTTESTED case. Pushed an update at the same > location.

Re: [Qemu-devel] winXP "Standard PC" HAL and qemu-kvm >= 0.15

On 07.12.2011 13:02, Kevin Wolf wrote: > Am 06.12.2011 19:21, schrieb Jan Kiszka: [] >>> For the 0.15 .. 1.0 change, the first commit which restores the (broken >>> in 0.15) functionality is this one: >>> >>> commit 86fbf97ceb4a9c46a609dd4ae053ba4262b68fe8 >>> Author: Jan Kiszka >>> Date: Fri Oc

Re: [PATCH] vhost-net: add module alias

On 11.01.2012 08:54, Stephen Hemminger wrote: > By adding the a module alias, programs (or users) won't have to explicitly > call modprobe. Vhost-net will always be available if built into the kernel. > It does require assigning a permanent minor number for depmod to work. > Choose one next to TUN

Re: [PATCH] vhost-net: add module alias

On 11.01.2012 20:58, Stephen Hemminger wrote: > On Wed, 11 Jan 2012 11:07:47 +0400 > Michael Tokarev wrote: > >> On 11.01.2012 08:54, Stephen Hemminger wrote: >>> By adding the a module alias, programs (or users) won't have to explicitly >>> call modprobe.

Re: qemu-kvm: Inconsistent vgabios reference

On 15.01.2012 16:53, Avi Kivity wrote: > On 01/15/2012 02:50 PM, Jan Kiszka wrote: [] >> extboot is history since 2a06024dc1b1e27b1be0266379af397e61b4a9ad > > Yeah, but it isn't history for people running older qemu-kvm's. We > don't need extboot itself, but we do need to keep the boot option (as

Re: qemu-kvm: Inconsistent vgabios reference

On 15.01.2012 17:18, Avi Kivity wrote: > On 01/15/2012 03:10 PM, Michael Tokarev wrote: [] >> FWIW, I had to patch extboot back in for debian qemu-kvm 1.0, because >> of lack of boot support from scsi (and no alternative), and because >> many people's scripts who used boo

Re: Unable to start a guest using qemu-kvm directly

On 29.01.2012 19:17, Vinod Chegu wrote: > > Dear All, > > I am using RHEL 6.2 + KVM on a X86_64 server. I have been able to create > Linux > guests using virt-install (using virto and/or pci passthrough) and am able to > manage the guests using virsh and/or virt-manager for doing some basic s

1.1 release?

Are there any issues with 1.1 release of qemu-kvm? The RCs were followed qemu RCs quite closely, but the final 1.1 is still not released, anything wrong with it? Thanks! /mjt -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majord...@vger.kernel.org M

Re: 1.1 release?

On 07.06.2012 11:13, Avi Kivity wrote: > On 06/07/2012 10:10 AM, Michael Tokarev wrote: >> Are there any issues with 1.1 release of qemu-kvm? [] > Yes, there is a regression with IDE PIO that can hang a guest on boot. Any pointers on this? I were testing 1.1-rc with various guest

KVM internal error with some amounts of guest memory

Now that's something else. Reported by a debian user, but trivially reproducible. $ kvm -m 1.4g KVM internal error. Suberror: 1 emulation failure EAX=000e3c54 EBX= ECX= EDX=0cfd ESI= EDI= EBP= ESP=6fe8 EIP=000f309b EFL=0016 [AP-] CPL=0 II=0

Re: KVM internal error with some amounts of guest memory

On 14.06.2012 23:22, Michael Tokarev wrote: > Now that's something else. Reported by a debian user, but > trivially reproducible. > > $ kvm -m 1.4g > KVM internal error. Suberror: 1 > emulation failure > EAX=000e3c54 EBX= ECX= EDX=0cfd > ESI=0

Re: KVM internal error with some amounts of guest memory

On 14.06.2012 23:45, Michael Tokarev wrote: > On 14.06.2012 23:22, Michael Tokarev wrote: >> Now that's something else. Reported by a debian user, but >> trivially reproducible. >> >> $ kvm -m 1.4g >> KVM internal error. Suberror: 1 >> emulation failu

[bug 1.1] -M pc-1.0 + vhost = SIGSEGV

When running current git version of qemu-kvm with -M pc-1.0 and with vhost-net enabled, it crashes with SIGSEGV right when linux guest loads a virtio-net module. I haven't tried to debug this deeply. The first result is: (gdb) ru -M pc-1.0 -nodefconfig -nodefaults -rtc base=utc -device piix3-us

Re: [bug 1.1] -M pc-1.0 + vhost = SIGSEGV

On 01.07.2012 19:06, Michael Tokarev wrote: > When running current git version of qemu-kvm with -M pc-1.0 > and with vhost-net enabled, it crashes with SIGSEGV right when > linux guest loads a virtio-net module. And when this happens when a persistent tap device is used, that tap devic

Re: [bug 1.1] -M pc-1.0 + vhost = SIGSEGV

02.07.2012 11:20, Jan Kiszka wrote: > On 2012-07-01 17:06, Michael Tokarev wrote: >> When running current git version of qemu-kvm with -M pc-1.0 > > Just to clarify: you are talking about stable-1.1 git, not master. Yes, as the $Subject (partially) says. [] >> So it

Re: [ANNOUNCE] qemu-kvm-1.1.0

On 03.07.2012 03:32, Marcelo Tosatti wrote: > > qemu-kvm-1.1.0 is now available. This release is based on the upstream > qemu 1.1.0, plus kvm-specific enhancements. Please see the > original QEMU 1.1.0 release announcement [1] for details. Why the recent fixes from Jan hasn't been applied? I mea

Re: [Qemu-devel] [PATCH] kvm: align ram_size to page boundary

On 17.06.2012 17:14, Avi Kivity wrote: > On 06/17/2012 04:06 PM, Blue Swirl wrote: > >>> strtosz() is much too general. We could do it in vl.c without trouble. >>> However, it takes away our ability to emulate a "640k should be enough >>> for everyone" machine. >> >> Then how about current max o

Re: Win 2000 driver for -vga std ?

On 14.02.2012 05:42, Reeted wrote: Hello, subject says it all The driver for windows 2000 for the -vga std should be the Anapa VBE Vesa VBEMP if I understand correctly but I cannot on earth find this executable http://navozhdeniye.narod.ru/vbemp.htm all links for download all over the world are

Re: Use getaddrinfo for migration

Not a reply to the patch but a general observation. I noticed that the tcp migration uses gethostname (or getaddrinfo after this patch) from the main thread - is it really the way to go? Note that DNS query which is done may block for a large amount of time. Is it really safe in this context? S

Re: [PATCH] kvm-amd: Auto-load on CPUs with SVM.

On 28.03.2012 22:32, Josh Triplett wrote: > Enable x86 feature-based autoloading for the kvm-amd module on CPUs > with X86_FEATURE_SVM. > > Signed-off-by: Josh Triplett It appears to work fine on my amd boxen. The only problem is that I've no idea when it will be possible to finally disable the

Re: Virtio network performance on Debian

On 16.04.2012 13:01, Stefan Pietsch wrote: > On 12.04.2012 09:42, Hans-Kristian Bakke wrote: >> Hi >> >> For some reason I am not able to get good network performance using >> virtio/vhost-net on Debian KVM host (perhaps also valid for Ubuntu >> hosts then). >> Disc IO is very good and the guests f

Re: Virtio network performance on Debian

On 12.04.2012 11:42, Hans-Kristian Bakke wrote: > Hi > > For some reason I am not able to get good network performance using > virtio/vhost-net on Debian KVM host (perhaps also valid for Ubuntu > hosts then). The issue has been identified, after Hans-Kristian gave me access to his machine and I d

Re: kvm unhandled exit 4400

[Replying to my own email] 04.11.2010 00:16, Michael Tokarev wrote: > 03.11.2010 22:44, Khaled El Mously wrote: >> The host kernel is on Ubuntu: 2.6.32-25-generic >> >> The guest kernel is 2.6.34-something. >> >> I have figured out what the problem is. When I f

  1   2   3   4   >