> -邮件原件-
> 发件人: Dr. David Alan Gilbert [mailto:dgilb...@redhat.com]
> 发送时间: 2018年4月12日 20:37
> 收件人: linzhecheng ; pbonz...@redhat.com
> 抄送: qemu-devel@nongnu.org; wangxin (U) ;
> Zhoujian (jay) ; quint...@redhat.com
> 主题: Re: [Qemu-devel] [Bug Report] vm pause
* linzhecheng (linzhech...@huawei.com) wrote:
> Hi, all
> I encounterd a bug when I try to migrate a windows vm.
>
> Enviroment information:
> host A: cpu E5620(model WestmereEP without flag xsave)
> host B: cpu E5-2643(model SandyBridgeEP with xsave)
>
> The reproduce steps is :
> 1. Start a win
Hi, all
I encounterd a bug when I try to migrate a windows vm.
Enviroment information:
host A: cpu E5620(model WestmereEP without flag xsave)
host B: cpu E5-2643(model SandyBridgeEP with xsave)
The reproduce steps is :
1. Start a windows 2008 vm with -cpu host(which means host-passthrough).
2. Mi
From the cocoa interface when I select pause QEMU doesn't pause. Instead QEMU
freezes. I have traced the problem to the qmp_stop() function. Here is the
stack trace:
+
2433 -[QemuCocoaAppController
On 14/06/2015 11:55, Mark Cave-Ayland wrote:
> On 13/05/15 10:01, Paolo Bonzini wrote:
>
>> On 12/05/2015 09:22, Michael Tokarev wrote:
>>> 12.05.2015 04:05, Peter Crosthwaite wrote:
On Thu, May 7, 2015 at 2:34 AM, Michael Tokarev wrote:
>>> ...
>> Ok, I can reproduce this, winXP BSODs
On Jun 14, 2015, at 5:55 AM, Mark Cave-Ayland wrote:
> On 13/05/15 10:01, Paolo Bonzini wrote:
>
>> On 12/05/2015 09:22, Michael Tokarev wrote:
>>> 12.05.2015 04:05, Peter Crosthwaite wrote:
On Thu, May 7, 2015 at 2:34 AM, Michael Tokarev wrote:
>>> ...
>> Ok, I can reproduce this, win
On 13/05/15 10:01, Paolo Bonzini wrote:
> On 12/05/2015 09:22, Michael Tokarev wrote:
>> 12.05.2015 04:05, Peter Crosthwaite wrote:
>>> On Thu, May 7, 2015 at 2:34 AM, Michael Tokarev wrote:
>> ...
> Ok, I can reproduce this, winXP BSODs on boot in tcg mode.
> Git bisect points to this:
>
On 12/05/2015 09:22, Michael Tokarev wrote:
> 12.05.2015 04:05, Peter Crosthwaite wrote:
>> On Thu, May 7, 2015 at 2:34 AM, Michael Tokarev wrote:
> ...
Ok, I can reproduce this, winXP BSODs on boot in tcg mode.
Git bisect points to this:
commit 23820dbfc79d1c9dce090b4c555994
On 05/12/2015 03:22 AM, Michael Tokarev wrote:
> 12.05.2015 04:05, Peter Crosthwaite wrote:
>> On Thu, May 7, 2015 at 2:34 AM, Michael Tokarev wrote:
> ...
Ok, I can reproduce this, winXP BSODs on boot in tcg mode.
Git bisect points to this:
commit 23820dbfc79d1c9dce090b4c555
On 12/05/2015 03:05, Peter Crosthwaite wrote:
> On Thu, May 7, 2015 at 2:34 AM, Michael Tokarev wrote:
>> 07.05.2015 09:47, Michael Tokarev wrote:
>>> 07.05.2015 09:12, Michael Tokarev wrote:
07.05.2015 04:11, G 3 wrote:
> Did you boot Windows XP to the desktop? I have tested Windows 95
12.05.2015 04:05, Peter Crosthwaite wrote:
> On Thu, May 7, 2015 at 2:34 AM, Michael Tokarev wrote:
...
>>> Ok, I can reproduce this, winXP BSODs on boot in tcg mode.
>>> Git bisect points to this:
>>>
>>> commit 23820dbfc79d1c9dce090b4c555994f2bb6a69b3
>>> Author: Peter Crosthwaite
>>> Date: M
On Thu, May 7, 2015 at 2:34 AM, Michael Tokarev wrote:
> 07.05.2015 09:47, Michael Tokarev wrote:
>> 07.05.2015 09:12, Michael Tokarev wrote:
>>> 07.05.2015 04:11, G 3 wrote:
Did you boot Windows XP to the desktop? I have tested Windows 95, Windows
2000, and Windows XP. All of them fail
On May 7, 2015, at 5:34 AM, Michael Tokarev wrote:
> 07.05.2015 09:47, Michael Tokarev wrote:
>> 07.05.2015 09:12, Michael Tokarev wrote:
>>> 07.05.2015 04:11, G 3 wrote:
Did you boot Windows XP to the desktop? I have tested Windows 95, Windows
2000, and Windows XP. All of them fail to
On May 7, 2015, at 2:47 AM, Michael Tokarev wrote:
> 07.05.2015 09:12, Michael Tokarev wrote:
>> 07.05.2015 04:11, G 3 wrote:
>>> Did you boot Windows XP to the desktop? I have tested Windows 95, Windows
>>> 2000, and Windows XP. All of them fail to boot to the desktop.
>>
>> Yes, booted to des
07.05.2015 09:47, Michael Tokarev wrote:
> 07.05.2015 09:12, Michael Tokarev wrote:
>> 07.05.2015 04:11, G 3 wrote:
>>> Did you boot Windows XP to the desktop? I have tested Windows 95, Windows
>>> 2000, and Windows XP. All of them fail to boot to the desktop.
>>
>> Yes, booted to desktop and did
07.05.2015 09:12, Michael Tokarev wrote:
> 07.05.2015 04:11, G 3 wrote:
>> Did you boot Windows XP to the desktop? I have tested Windows 95, Windows
>> 2000, and Windows XP. All of them fail to boot to the desktop.
>
> Yes, booted to desktop and did some minimal work in there,
> installnig one up
07.05.2015 04:11, G 3 wrote:
> Did you boot Windows XP to the desktop? I have tested Windows 95, Windows
> 2000, and Windows XP. All of them fail to boot to the desktop.
Yes, booted to desktop and did some minimal work in there,
installnig one update or two.
> Command used:
> ./i386-softmmu/qemu
Did you boot Windows XP to the desktop? I have tested Windows 95, Windows
2000, and Windows XP. All of them fail to boot to the desktop.
Command used:
./i386-softmmu/qemu-system-i386 -boot c -hda "Windows XP Hard Drive.img"
On Wed, May 6, 2015 at 2:44 PM, Programmingkid
wrote:
>
> On May 6, 201
06.05.2015 08:41, Programmingkid wrote
> Just wanted to note that for the i386 target, Windows XP as a guest fails to
> boot. When it safe mode, loading always stops at
> Windows\System32\Drivers\Mup.sys. The guest boots in QEMU 2.2.0, so this
> seems to indicate a bug with the May 5th or earli
Just wanted to note that for the i386 target, Windows XP as a guest fails to
boot. When it safe mode, loading always stops at
Windows\System32\Drivers\Mup.sys. The guest boots in QEMU 2.2.0, so this seems
to indicate a bug with the May 5th or earlier patch set.
Hi,
There is a issue that doing snapshot under a background migration could cause a
segfault.
Steps to reproduce this issue are:
1. dirty plenty of pages in the 1st guest
2. run command 'migrate -d tcp:***:***' in 1st monitor to migrate the 1st
guest to 2nd guest in background
3. r
hi all I found a bug in qemu, when i invoke:
cpu_physical_memory_rw(addr, mem_buf, noOfBytes, 0);
where addr=0x0 and noOfBytes=50, qemu will has segmentation fault. I call
the cpu_physical_memory_rw right after the qemu is started (haven't run yet)
with gdb.
Thanksfrom Peter
Hi Paolo and Vincenzo,
Here is a compile error in current uq/master
(ca916d3729564d0eb3c2374a96903f7e8aced8a7) as follows:
/root/qemu-kvm.git/kvm-stub.c:138:5: error: conflicting types for
'kvm_irqchip_add_irqfd_notifier'
/root/qemu-kvm.git/include/sysemu/kvm.h:312:5: note: previous
declaration o
Am 12.07.2013 um 10:59 schrieb Alexey Kardashevskiy :
> Hi!
>
> Got a small lesson from Ben how to post stuff to the list and here are more
> details :)
>
> Every PCI device which uses IO ports (at least vga, e1000, virtio-pci,
> rtl8139) is broken in the master branch of QEMU for powerpc-kvm.
Hi!
Got a small lesson from Ben how to post stuff to the list and here are more
details :)
Every PCI device which uses IO ports (at least vga, e1000, virtio-pci,
rtl8139) is broken in the master branch of QEMU for powerpc-kvm. The
problem is exactly with endianness. For example, setup_vq() from
d
On 2013-04-16 12:19, 李春奇 wrote:
> I looked up Intel manual for VM instruction error. Error number 7 means "VM
> entry with invalid control field(s)", which means in process of VM
> switching some control fields are not properly configured.
>
> I wonder why some emulated CPUs (e.g.Nehalem) can run
I looked up Intel manual for VM instruction error. Error number 7 means "VM
entry with invalid control field(s)", which means in process of VM
switching some control fields are not properly configured.
I wonder why some emulated CPUs (e.g.Nehalem) can run properly without
nested VMCS MSR support?
On 2013-04-16 05:49, 李春奇 wrote:
> I changed to the latest version of kvm kernel but the bug also occured.
>
> On the startup of L1 VM on the host, the host kern.log will output:
> Apr 16 11:28:22 Blade1-02 kernel: [ 4908.458090] kvm [2808]: vcpu0
> unhandled rdmsr: 0x345
> Apr 16 11:28:22 Blade1-
I changed to the latest version of kvm kernel but the bug also occured.
On the startup of L1 VM on the host, the host kern.log will output:
Apr 16 11:28:22 Blade1-02 kernel: [ 4908.458090] kvm [2808]: vcpu0
unhandled rdmsr: 0x345
Apr 16 11:28:22 Blade1-02 kernel: [ 4908.458166] kvm_set_msr_common:
On 2013-04-15 08:24, 李春奇 wrote:
> Hi all,
> In a nested virtualization environment of qemu+KVM, some emulated CPU (such
> as core2duo) may cause L2 guest crash after booting for a while. Here's my
> configuration:
>
> Host:
> Linux 3.5.7
You should better use latest version from kvm.git [1], bra
Hi all,
In a nested virtualization environment of qemu+KVM, some emulated CPU (such
as core2duo) may cause L2 guest crash after booting for a while. Here's my
configuration:
Host:
Linux 3.5.7
Qemu is the latest version from git repository.
Emulated CPU : core2duo
L1 guest:
Linux 3.5.7
Qemu is the
On Fri, Jul 27, 2012 at 12:44:20PM +0800, GaoYi wrote:
> Hi all,
>I am running a netbsd kernel in KVM, using Intel VT. However, the OS
> failed to start up with the following outputs:
>
> KVM internal error. Suberror: 1
> emulation failure.
> EAX=0001EBX=ECX=000
Hi all,
I am running a netbsd kernel in KVM, using Intel VT. However, the OS
failed to start up with the following outputs:
KVM internal error. Suberror: 1
emulation failure.
EAX=0001EBX=ECX=0005 EDX=0001
ESI=0001 EDI=001c4bd2 EBP=0011a72c
On 2012-03-28 14:44, Katrina Austin wrote:
> Hi Jan,
> Now I wanna to locate the instruction in the guest OS that causes this
> problem. However, I dont know how to make it as the guest OS has not yet
> started up. I would be much appreicated if you can provide some suggestions.
Not sure if
Hi Jan,
Now I wanna to locate the instruction in the guest OS that causes this
problem. However, I dont know how to make it as the guest OS has not yet
started up. I would be much appreicated if you can provide some suggestions.
Katrina
On Fri, Mar 23, 2012 at 8:13 PM, Jan Kiszka wrote:
> On
Hi Jan,
I have tried to specify the CPU type but got no luck. More specifically,
the bootrom of vxworks failed. I think the problem lies in the Intel VMX.
However, I don't know how to make further debugging. Hope you can provide
more suggestions from the bug report.
Best,
Katrina
On Fri
The microa-architecture of Intel Xeon E5620 is westmere-EP. So, how to
specify, e.g., -cpu westmere?
p.s. I cannot test it until tomorrow as I am out of office now.
Thanks,
katrina
On Fri, Mar 23, 2012 at 8:13 PM, Jan Kiszka wrote:
> On 2012-03-23 12:45, Katrina Austin wrote:
> > Hi Jan,
> >
>
On 2012-03-23 12:45, Katrina Austin wrote:
> Hi Jan,
>
>The host version is: linux-2.6.33.3. I removed the kvm incorporated in the
> linux kernel and rebuilt the kvm-kmod-3.3.tar.bz2. I have tried from
> kvm-kmod-2.6.33.3 to kvm-kmod.3.3. Unfortunately, no one worked. The tested
> guest ima
Hi Jan,
The host version is: linux-2.6.33.3. I removed the kvm incorporated in
the linux kernel and rebuilt the kvm-kmod-3.3.tar.bz2. I have tried from
kvm-kmod-2.6.33.3 to kvm-kmod.3.3. Unfortunately, no one worked. The tested
guest image is vxworks downloaded from
http://people.freebsd.org/~w
On 2012-03-23 09:19, Katrina Austin wrote:
> Hi all,
>
>I've built a guest image. It works well on KVM with a AMD X240 processor
> but failed with a intel E5620 processor. I am using kvm-kmod-3.3 and
> qemu-kvm-0.14.0. Here comes the report:
> kvm_emulate_insn: 0: 11a6d0: ff (p
Hi all,
I've built a guest image. It works well on KVM with a AMD X240 processor
but failed with a intel E5620 processor. I am using kvm-kmod-3.3 and
qemu-kvm-0.14.0. Actually it failed for all existing kvm version. Here
comes the report:
kvm_emulate_insn: 0: 11a6d0: ff (prot32)
Hi all,
I've built a guest image. It works well on KVM with a AMD X240 processor
but failed with a intel E5620 processor. I am using kvm-kmod-3.3 and
qemu-kvm-0.14.0. Here comes the report:
kvm_emulate_insn: 0: 11a6d0: ff (prot32) failed
kvm_userspace_exit: reaso
On Wed, 10 Nov 2010, malc wrote:
> On Wed, 10 Nov 2010, Torbjorn Granlund wrote:
>
> > malc writes:
> >
> > All is the keyword here, i doubt that exhaustive search was performed
> > furthermore, AMDs documentation (to the best of my knowledge still)
> > still maintains that ZF is undefine
On Wed, 10 Nov 2010, Torbjorn Granlund wrote:
> malc writes:
>
> All is the keyword here, i doubt that exhaustive search was performed
> furthermore, AMDs documentation (to the best of my knowledge still)
> still maintains that ZF is undefined.
>
> AMD indeed still says undefined in their
malc writes:
All is the keyword here, i doubt that exhaustive search was performed
furthermore, AMDs documentation (to the best of my knowledge still)
still maintains that ZF is undefined.
AMD indeed still says undefined in their documentation (as of two hours
ago). I have asked AMD for a
On Wed, 10 Nov 2010, Torbjorn Granlund wrote:
> malc writes:
>
> And this one was March 2009 (conveniently having the same file name
> 253666), the September 2010 issue reads differently:
>
> Flags Affected
> The CF flag contains the value of the selected bit. The ZF flag is
> unaf
malc writes:
And this one was March 2009 (conveniently having the same file name
253666), the September 2010 issue reads differently:
Flags Affected
The CF flag contains the value of the selected bit. The ZF flag is
unaffected. The OF, SF, AF, and PF flags are undefined.
Have the q
On Sat, 6 Nov 2010, malc wrote:
> On Sat, 6 Nov 2010, Nathan Froyd wrote:
>
> > On Sat, Nov 06, 2010 at 07:24:39PM +0100, Torbjorn Granlund wrote:
> > > malc writes:
> > >
> > > ZF is undefined according to AMD's 24594.pdf page 69.
> > >
> > > Ah, you're right. It seems that all existing
On Sat, 6 Nov 2010, Nathan Froyd wrote:
> On Sat, Nov 06, 2010 at 07:24:39PM +0100, Torbjorn Granlund wrote:
> > malc writes:
> >
> > ZF is undefined according to AMD's 24594.pdf page 69.
> >
> > Ah, you're right. It seems that all existing x86 implementations leave
> > ZF alone, though.
On Sat, Nov 06, 2010 at 07:24:39PM +0100, Torbjorn Granlund wrote:
> malc writes:
>
> ZF is undefined according to AMD's 24594.pdf page 69.
>
> Ah, you're right. It seems that all existing x86 implementations leave
> ZF alone, though. (I am not arguing that qeum is broken, the bug is in
>
On Sat, 6 Nov 2010, Torbjorn Granlund wrote:
> malc writes:
>
> ZF is undefined according to AMD's 24594.pdf page 69.
>
> Ah, you're right. It seems that all existing x86 implementations leave
> ZF alone, though. (I am not arguing that qeum is broken, the bug is in
> my code.)
>
> I apol
malc writes:
ZF is undefined according to AMD's 24594.pdf page 69.
Ah, you're right. It seems that all existing x86 implementations leave
ZF alone, though. (I am not arguing that qeum is broken, the bug is in
my code.)
I apologize for the false alarm!
--
Torbjörn
On Sat, 6 Nov 2010, Torbjorn Granlund wrote:
> [This is a bug report, reported here since I was redirected to some
> corporate site when attempting to follow the recommended bug report
> practice. If I am really required to register an account with a
> corporation in order to report a qemu bug, a
[This is a bug report, reported here since I was redirected to some
corporate site when attempting to follow the recommended bug report
practice. If I am really required to register an account with a
corporation in order to report a qemu bug, and that bug reports are not
accepted here, then please
Hi people,
I would like to tank you for your attention and patience. I don't understand
many things about emulators, nor linux. I started using Ubuntu-Linux this
year, and since then, i started to discover a new world. But sometimes i
have some problems and it's not so easy to a newbie to solve it
On Tuesday 17 November 2009 12:11:58 am Luiz Felipe wrote:
> Hi, i tried to use kqemu in ubuntu to start Windows XP SP3. I used the
> command line: "qemu -kernel-kqemu" and the system started to run windows on
> qemu. Although, i observed the following message on my shell:
>
> QEMU acceleration la
Hi, i tried to use kqemu in ubuntu to start Windows XP SP3. I used the
command line: "qemu -kernel-kqemu" and the system started to run windows on
qemu. Although, i observed the following message on my shell:
QEMU acceleration layer not activated: Permission denied
unknown keycodes `evdev(abnt2)_a
On Tue, Dec 18, 2007 at 04:52:47PM +, Paul Brook wrote:
> > - Qemu initializes all its memory to 0. Real hardware doesn't seem to
> > do that. This means that usage of uninitialized memory is very hard
> > to debug (because 0 is often a good value, while [random] is not, so
> > the prob
> - Qemu initializes all its memory to 0. Real hardware doesn't seem to
> do that. This means that usage of uninitialized memory is very hard
> to debug (because 0 is often a good value, while [random] is not, so
> the problem can only be seen on real hardware, which makes it hard to
> de
Hi,
While writing a kernel and testing it with qemu, I found some bugs in
qemu (and many in my kernel ;-) ). Here's a list of them. They are all
about x86 emulation on x86. Some are a bit old, and since my kernel is
now fixed I can't easily test if they still aren't fixed, though.
- When a pro
Hey there,
I've been doing a bit of programming with QuickBasic
using MS-DOS 6.22 running under QEMU 0.9.0/x86/Linux.
It's all fine and dandy except for one (big) problem:
sin() and cos() don't work correctly.
Here's a demonstration:
http://nonlogic.org/dump/bin/1183539319-glitchy.exe
It works f
I was running Windows 2000 Pro in QEMU (FreeBSD as host) and needed more
disk space. So I created a spare hard drive with this command:
$ qemu-img create -f qcow hd2.img 3GB
And then I started QEMU again like this:
qemu -hda hd.img -hdb hd2.img -cdrom scrap1.iso -kernel-kqemu
(hd.img already had
hi,
I just tried microsoft money 97 with qemu 0.8.1 without kqemu, and have
sometimes wrong additions :
example : 100 + 100 = 40
It is reproductible easily, as it does always the same error.
I tried on windows 95 and 98 SE, both have the same problem. On a not emulated
PC with 98 SE, I don't hav
To clarify the current behaviour of kqemu and QEMU with self-writing
code, the following table can be useful:
Supported feature QEMUkqemu
CS.limit no yes
NX bit yes (x86_64 on
I had a similar problem, but only when not using kqemu.
When using a stack overflow exploit, the shellcode provided only
executes when using kqemu. I can attribute this to either the
shellcode being in a different location (maybe someone can clarify
this, is qemu using a different memory layout e
Looks like SELinux to me. Even - you should raise it with whoever
writes your policy.
On Mon, 01 May 2006 23:29:54 +0200
Fabrice Bellard <[EMAIL PROTECTED]> wrote:
> Are you sure that the bug is really in kqemu ? It is possible that
> your guest kernel implements a security system which prevents
You're absolutely right. SELinux was enabled on the host. I disabled it and
now the self modying code runs with kqemu enabled.
So, I guess the current behaviour of qemu (without kqemu) is not really
wanted.
Le Lundi 1 Mai 2006 23:29, Fabrice Bellard a écrit :
> Are you sure that the bug is reall
Are you sure that the bug is really in kqemu ? It is possible that your
guest kernel implements a security system which prevents self modifying
code using segment limits which QEMU does not check (but kqemu checks
them !).
Regards,
Fabrice.
Even Rouault wrote:
Guest OS : Linux 2.6.15-1.2054
Guest OS : Linux 2.6.15-1.2054_FC5 i686 (Fedora Core 5 i386)
Host OS: Linux 2.6.12-10-amd64-k8 #1 x86_64 (Ubuntu 5.10 amd64)
QEMU Version : today CVS compiled with kqemu support
KQEMU : 1.3.0pre6
Binary used : qemu-system-x86-64 (so kqemu user-mode is used)
I'm running the simple C code attached.
Le mercredi, 2 nov 2005, à 01:00 Europe/Paris, Karl Magdsick a écrit :
gcc 4.x is known not to compile qemu, due to a register allocation bug
in gcc.
It can be fixed at QEMU's level with additional patches than posted
here and actually I have it working for x86 system emulation.
Unfortunatel
On Tue, Nov 01, 2005 at 07:08:19PM -0500, Julien Lancien wrote:
> I saw that there is a binary distribution for linux-i386, however,
> I'ld like to also get kqemu. Is there a way to do that without getting
> gcc 3 ?
>
> Thanks.
>
kqemu is immune to the gcc 3 problem that qemu has. You can use gc
Find out how to run gcc 3.x if you have it installed, e.g., on mine
(Mac OS X), gcc-3.3 does it, then:
./configure --cc=gcc-3.3
This seems to be enough (HOST_CC left as gcc doesn't break anything
but it may be safer to set that too as 3.x).
On 02/11/2005, at 10:00 AM, Karl Magdsick wrote:
On 11/1/05, Karl Magdsick <[EMAIL PROTECTED]> wrote:
> gcc 4.x is known not to compile qemu, due to a register allocation bug in gcc.
>
> Also, the current qemu code generator is an ugly hack that relies on some
> specifics of gcc 3.x function implementation. There is work being done
> on a _real_
gcc 4.x is known not to compile qemu, due to a register allocation bug in gcc.
Also, the current qemu code generator is an ugly hack that relies on some
specifics of gcc 3.x function implementation. There is work being done
on a _real_ code generator for qemu.
-Karl
On 11/1/05, Julien Lancien
Julien Lancien wrote:
Hi,
I am unable to compile qemu on my machine :p. I've attached the result
of the configure and make.
My gcc version is: 4.0.3 20051006 and kernel 2.6.13 vanilla.
I used the CVS snapshot, but I got mostly the same problem with the
0.7.2 version.
Tell me if you want more
Hi,
I am unable to compile qemu on my machine :p. I've attached the result
of the configure and make.
My gcc version is: 4.0.3 20051006 and kernel 2.6.13 vanilla.
I used the CVS snapshot, but I got mostly the same problem with the
0.7.2 version.
Tell me if you want more infos, and thanks for any
76 matches
Mail list logo
