* Brian J. Murrell [2011-12-15 15:28]:
> I have a CentOS 6 host system running a CentOS 6 KVM guest and the
> guest seems to get about 5x slower disk throughput than the host:
>
> host $ sudo dd of=/dev/datavol/disk1 if=/dev/zero bs=1M oflag=direct
> count=5
> 5+0 records in
> 5+0 re
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 feels snappy so it doesn't seem
> like there is som
Hi,
I'm running a Windows XP guest in KVM. After enabling the audio support
(-soundhw es1370) the CPU load of the KVM process in the host system
goes up to 100%.
Tested with: qemu-kvm-0.13.0 Debian 0.13.0+dfsg-1
KVM start command: kvm -m 512 -hda xp.img -soundhw es1370
Did you experience simil
* Michael Tokarev [2010-11-09 15:41]:
> Ok. This is wrong: neither of the two changes went into any
> stable release. Hence we've bugs which are long fixed but
> no one knows about this. As usual for qemu[-kvm] development.
I can reproduce the problem with the Debian release 0.12.5+dfsg-4.
So
On 19.05.2013 14:32, Gleb Natapov wrote:
> On Sun, May 19, 2013 at 02:00:31AM +0100, Ben Hutchings wrote:
>> Dear KVM maintainers, it appears that there is a gap in x86 emulation,
>> at least on a 32-bit host. Stefan found this when running GRML, a live
>> distribution which can be downloaded from
On 19.05.2013 14:32, Gleb Natapov wrote:
> On Sun, May 19, 2013 at 02:00:31AM +0100, Ben Hutchings wrote:
>> Dear KVM maintainers, it appears that there is a gap in x86 emulation,
>> at least on a 32-bit host. Stefan found this when running GRML, a live
>> distribution which can be downloaded from
On 05.06.2013 14:10, Gleb Natapov wrote:
> On Wed, Jun 05, 2013 at 01:57:25PM +0200, Stefan Pietsch wrote:
>> On 19.05.2013 14:32, Gleb Natapov wrote:
>>> On Sun, May 19, 2013 at 02:00:31AM +0100, Ben Hutchings wrote:
>>>> Dear KVM maintainers, it appears that t
On 06.06.2013 08:42, Gleb Natapov wrote:
> On Wed, Jun 05, 2013 at 02:51:19PM +0200, Stefan Pietsch wrote:
>> On 05.06.2013 14:10, Gleb Natapov wrote:
>>> On Wed, Jun 05, 2013 at 01:57:25PM +0200, Stefan Pietsch wrote:
>>>> On 19.05.2013 14:32, Gleb Natapov wrote:
&g
On 06.06.2013 13:40, Gleb Natapov wrote:
> On Thu, Jun 06, 2013 at 01:35:13PM +0200, Stefan Pietsch wrote:
>> I had no success with the Debian kernel 3.10~rc4-1~exp1 (3.10-rc4-686-pae).
>>
>> The machine hangs after "Enabling APIC mode: Flat. Using 1 I/O APICs"
On 09.06.2013 11:43, Gleb Natapov wrote:
> On Thu, Jun 06, 2013 at 02:10:39PM +0200, Stefan Pietsch wrote:
>> On 06.06.2013 13:40, Gleb Natapov wrote:
>>> On Thu, Jun 06, 2013 at 01:35:13PM +0200, Stefan Pietsch wrote:
>>
>>>> I had no success with the Debian
On 13.06.2013 15:42, Paolo Bonzini wrote:
> Il 13/06/2013 07:57, Stefan Pietsch ha scritto:
>> git bisect tells me:
>> 79fd50c67f91136add9726fb7719b57a66c6f763 is the first bad commit
>
> This is an s390 commit, so the bisect somehow went wrong. Can you
> confirm that 3
On 13.06.2013 16:59, Stefan Pietsch wrote:
> On 13.06.2013 15:42, Paolo Bonzini wrote:
>> Il 13/06/2013 07:57, Stefan Pietsch ha scritto:
>>> git bisect tells me:
>>> 79fd50c67f91136add9726fb7719b57a66c6f763 is the first bad commit
>>
>> This is an s390 c
On 17.06.2013 18:07, Paolo Bonzini wrote:
> Il 16/06/2013 02:25, Stefan Pietsch ha scritto:
>> Bisecting leads to
>>
>> git bisect bad 378a8b099fc207ddcb91b19a8c1457667e0af398
>> git bisect good 007a3b547512d69f67ceb9641796d64552bd337e
>> git bisect good 1f3141e
On 19.06.2013 15:41, Gleb Natapov wrote:
> On Sun, Jun 16, 2013 at 02:25:04AM +0200, Stefan Pietsch wrote:
>>
>> first bad commit: [25391454e73e3156202264eb3c473825afe4bc94]
>> KVM: VMX: don't clobber segment AR of unusable segments.
>>
>>
>&
On 19.06.2013 16:38, Gleb Natapov wrote:
> On Wed, Jun 19, 2013 at 04:12:04PM +0200, Stefan Pietsch wrote:
>> On 19.06.2013 15:41, Gleb Natapov wrote:
>>> On Sun, Jun 16, 2013 at 02:25:04AM +0200, Stefan Pietsch wrote:
>>>>
>>>> first bad commit: [25391454
On 23.06.2013 09:51, Gleb Natapov wrote:
> On Thu, Jun 20, 2013 at 07:01:49PM +0200, Stefan Pietsch wrote:
>>> Can you provide the output of 25391454e73e3156202264eb3c473825afe4bc94
>>> and emulate_invalid_guest_state=0. Also run "x/20i $pc-20" in
On 23.06.2013 19:36, Gleb Natapov wrote:
> On Sun, Jun 23, 2013 at 06:51:30PM +0200, Stefan Pietsch wrote:
>> On 23.06.2013 09:51, Gleb Natapov wrote:
>>> On Thu, Jun 20, 2013 at 07:01:49PM +0200, Stefan Pietsch wrote:
>>>>> Can you provide the output of 2539145
On 24.06.2013 13:47, Gleb Natapov wrote:
> On Mon, Jun 24, 2013 at 01:43:26PM +0200, Stefan Pietsch wrote:
>> On 23.06.2013 19:36, Gleb Natapov wrote:
>>> On Sun, Jun 23, 2013 at 06:51:30PM +0200, Stefan Pietsch wrote:
>>>> On 23.06.2013 09:51, Gleb Natapov wrote:
&g
On 24.06.2013 14:30, Gleb Natapov wrote:
> On Mon, Jun 24, 2013 at 01:59:34PM +0200, Stefan Pietsch wrote:
>> As soon as I remove "kvmvapic.bin" the virtual machine boots with
>> qemu-kvm 1.5.0. I just verified this with Linux kernel 3.10.0-rc5.
>> &qu
On 26.06.2013 12:47, Gleb Natapov wrote:
> On Mon, Jun 24, 2013 at 10:42:57PM +0200, Stefan Pietsch wrote:
>> On 24.06.2013 14:30, Gleb Natapov wrote:
>>> On Mon, Jun 24, 2013 at 01:59:34PM +0200, Stefan Pietsch wrote:
>>>> As soon as I remove "kvmvapic.
Hi all,
starting a virtual machine (Debian sid) with KVM on my host running
kernel 3.10.1 (Debian 3.10-1-686-pae) produces these messages:
[ 765.522920] Uhhuh. NMI received for unknown reason 31 on CPU 0.
[ 765.522927] Do you have a strange power saving mode enabled?
[ 765.522930] Dazed and co
On 26.07.2013 20:39, Gleb Natapov wrote:
> On Fri, Jul 26, 2013 at 08:25:19PM +0200, Stefan Pietsch wrote:
>> Hi all,
>>
>> starting a virtual machine (Debian sid) with KVM on my host running
>> kernel 3.10.1 (Debian 3.10-1-686-pae) produces these messages:
>>
On 29.07.2013 11:16, Gleb Natapov wrote:
> On Mon, Jul 29, 2013 at 11:09:51AM +0200, Stefan Pietsch wrote:
>> On 26.07.2013 20:39, Gleb Natapov wrote:
>>> On Fri, Jul 26, 2013 at 08:25:19PM +0200, Stefan Pietsch wrote:
>>>> Hi all,
>>>>
>>>>
On 30.07.2013 07:31, Gleb Natapov wrote:
> What happen if you run perf on your host (perf record -a)?
> Do you see same NMI messages?
It seems that "perf record -a" triggers some delayed NMI messages.
They appear about 20 or 30 minutes after the command. This seems strange.
--
To unsubscribe fro
On 31.07.2013 11:20, Gleb Natapov wrote:
> On Wed, Jul 31, 2013 at 11:10:01AM +0200, Stefan Pietsch wrote:
>> On 30.07.2013 07:31, Gleb Natapov wrote:
>>
>>> What happen if you run perf on your host (perf record -a)?
>>> Do you see same NMI messages?
>>
>
On 04.08.2013 14:44, Gleb Natapov wrote:
> On Fri, Aug 02, 2013 at 08:24:38AM +0200, Stefan Pietsch wrote:
>> On 31.07.2013 11:20, Gleb Natapov wrote:
>>> On Wed, Jul 31, 2013 at 11:10:01AM +0200, Stefan Pietsch wrote:
>>>> On 30.07.2013 07:31, Gleb Natapov wrote:
>
On 25.08.2013 13:45, Gleb Natapov wrote:
> On Fri, Aug 09, 2013 at 09:14:13PM +0200, Stefan Pietsch wrote:
>> On 04.08.2013 14:44, Gleb Natapov wrote:
>>> On Fri, Aug 02, 2013 at 08:24:38AM +0200, Stefan Pietsch wrote:
>>>> On 31.07.2013 11:20, Gleb Natapov wrote:
&g
Hi all,
when I run KVM with this command the Windows 8 installation stops with
error code 0x005D:
kvm -m 1024 -hda win8.img -cdrom windows_8_x86.iso
After adding the option "-cpu host" the installation proceeds to a black
screen and hangs.
With Virtualbox the installation succeeds.
The host
* Gleb Natapov [2013-01-06 11:11]:
> On Fri, Jan 04, 2013 at 10:58:33PM +0100, Stefan Pietsch wrote:
> > Hi all,
> >
> > when I run KVM with this command the Windows 8 installation stops with
> > error code 0x005D:
> > kvm -m 1024 -hda win8.img -cdrom window
* Ren, Yongjie [2013-01-07 09:38]:
> you met issue only for 32bit Win8 (not 64 bit Win8), right?
> I think it's the same issue as the below bug I reported.
> https://bugs.launchpad.net/qemu/+bug/1007269
> You can try with '-cpu coreduo' or '-cpu core2duo' in qemu-kvm command line.
Yes, I'm talki
30 matches
Mail list logo
