* OpenBSD 5.3 guest on KVM
@ 2013-09-04 23:31 Daniel Bareiro
2013-09-05 8:30 ` Paolo Bonzini
2015-11-06 15:57 ` Paolo Bonzini
0 siblings, 2 replies; 6+ messages in thread
From: Daniel Bareiro @ 2013-09-04 23:31 UTC (permalink / raw)
To: KVM General
[-- Attachment #1: Type: text/plain, Size: 1374 bytes --]
Hi all!
These days I tested OpenBSD 5.3 and pleasantly surprised me notice that
they implemented VirtIO for block devices, network and memory
ballooning. It is an important step for those who contribute to the
project.
Now what I'm seeing is that there seems to be some sort of problem with
the ACPI to shutdown the VM. I remember that at one time it was not
working, then they corrected it and now seems to be new problems with
these messages.
I tried turning off the VM from libvirt (virsh) and also from Qemu
monitor booting the VM manually and in either case the result is the
same: the VM freezes.
# sysctl hw
hw.machine=amd64
hw.model=QEMU Virtual CPU version 1.1.2
hw.ncpu=1
hw.byteorder=1234
hw.pagesize=4096
hw.disknames=cd0:,sd0:be0e0f1c0cdc4dae,fd0:,fd1:
hw.diskcount=4
hw.cpuspeed=2009
hw.vendor=Bochs
hw.product=Bochs
hw.uuid=501ef229-2337-165f-8da3-905b12832049
hw.physmem=535814144
hw.usermem=535801856
hw.ncpufound=1
hw.allowpowerdown=1
hw.allowpowerdown set to 1 (the default) allows a power button shutdown.
Someone had this problem and could solve it somehow? There any debug
information I can provide to help solve this?
Thanks in advance for your reply.
Regards,
Daniel
--
Fingerprint: BFB3 08D6 B4D1 31B2 72B9 29CE 6696 BF1B 14E6 1D37
Powered by Debian GNU/Linux - Linux user #188.598
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: OpenBSD 5.3 guest on KVM
2013-09-04 23:31 OpenBSD 5.3 guest on KVM Daniel Bareiro
@ 2013-09-05 8:30 ` Paolo Bonzini
2013-09-05 15:44 ` Daniel Bareiro
2015-11-06 15:57 ` Paolo Bonzini
1 sibling, 1 reply; 6+ messages in thread
From: Paolo Bonzini @ 2013-09-05 8:30 UTC (permalink / raw)
To: dbareiro, KVM General
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Il 05/09/2013 01:31, Daniel Bareiro ha scritto:
> Someone had this problem and could solve it somehow? There any
> debug information I can provide to help solve this?
For simple troubleshooting try "info status" from the QEMU monitor.
You can also try this:
http://www.linux-kvm.org/page/Tracing
You will get a large log, you can send it to me offlist or via
something like Google Drive.
Paolo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJSKEEUAAoJEBvWZb6bTYby4+UP/2V99leGzgxccTS6s3LHwAk8
UomjlcPmzXZ6UlC8ppGfHkuzWm/jbhmkMGX8DYrdYOJdctugFpbOrIaPA/pC2Na4
8o2LWZ5burvztUVS8O5d4wmfLHIgOvuIFj8MQ5YJ571HiYUKq3oipQf1yL5kzbtU
1p4/0lrXRwAz++YKXFfZ3A1vIQ5Ms6WwwHljyfZMZNvafymT87cPNskX4P3aO81U
weYeTpIuTLdiBIzkA1Xqun7z3DzZszCB91UxeKTxvxZLiPHnaYocS7bTF8i710mQ
BUfBXFUTH0xt46O1QCLrNHqbojSPaUwr7pkK2x1dCYfPISN9+nmZ9BgHGZCTTVIn
Ga9kn0rdIfalpBXybgTFZBeqHimSYAou/CuVKgx4wLYMUVdE95dOFjVx3K9yOtfv
ulmKqh7yGlWB9ZNRC+qet0BcwA6ssgutcHVMa46V0vE22J0phTcBPWWpYLw18IBl
J2D5oOTEnZ3pqzxhXD2zjeD3pBBtZa+dsDLuhBIhkQI9Qcqv/N1I5oCEBOtbVBBh
aWb0vEOBjdw9+cfadxtl2VQUV6GfwasBbOktFYR7gIG3ji/Asf35ZeC1xHAFv7xw
2pxxfGxLmX0NXdwgvlXz45+V0ITK8ZzuoU4tc2JDEXUk9Q2Slb9vHwxDPtbnDeo/
uybOp9WiNmQvrA4Thg1V
=PwDG
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: OpenBSD 5.3 guest on KVM
2013-09-05 8:30 ` Paolo Bonzini
@ 2013-09-05 15:44 ` Daniel Bareiro
2013-09-05 18:00 ` Gleb Natapov
0 siblings, 1 reply; 6+ messages in thread
From: Daniel Bareiro @ 2013-09-05 15:44 UTC (permalink / raw)
To: KVM General
[-- Attachment #1: Type: text/plain, Size: 1413 bytes --]
Hi, Pablo.
On Thursday 05 September 2013 10:30:12 +0200,
Paolo Bonzini wrote:
> > Someone had this problem and could solve it somehow? There any
> > debug information I can provide to help solve this?
> For simple troubleshooting try "info status" from the QEMU monitor.
ss01:~# telnet localhost 4046
Trying ::1...
Connected to localhost.
Escape character is '^]'.
QEMU 1.1.2 monitor - type 'help' for more information
(qemu)
(qemu)
(qemu) info status
VM status: running
(qemu)
(qemu)
(qemu) system_powerdown
(qemu)
(qemu)
(qemu) info status
VM status: running
(qemu)
Then the VM freezes.
> You can also try this:
>
> http://www.linux-kvm.org/page/Tracing
>
> You will get a large log, you can send it to me offlist or via
> something like Google Drive.
The log has 612 MB (57 MB compressed with bzip2). I guess it must be
because there are other production VMs running on that host. Is there a
way of limiting the log? This result I got it running I found on the
link you sent me.
# trace-cmd record -b 20000 -e kvm
# trace-cmd report
I forgot to mention that I'm using KVM versions provided by the
repositories of Debian Wheezy:
Linux: 3.2.46-1+deb7u1
qemu-kvm: 1.1.2+dfsg-6
Thanks for your reply.
Regards,
Daniel
--
Fingerprint: BFB3 08D6 B4D1 31B2 72B9 29CE 6696 BF1B 14E6 1D37
Powered by Debian GNU/Linux - Linux user #188.598
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: OpenBSD 5.3 guest on KVM
2013-09-05 15:44 ` Daniel Bareiro
@ 2013-09-05 18:00 ` Gleb Natapov
2013-09-05 18:49 ` Daniel Bareiro
0 siblings, 1 reply; 6+ messages in thread
From: Gleb Natapov @ 2013-09-05 18:00 UTC (permalink / raw)
To: dbareiro, KVM General
On Thu, Sep 05, 2013 at 12:44:58PM -0300, Daniel Bareiro wrote:
> Hi, Pablo.
>
> On Thursday 05 September 2013 10:30:12 +0200,
> Paolo Bonzini wrote:
>
> > > Someone had this problem and could solve it somehow? There any
> > > debug information I can provide to help solve this?
>
> > For simple troubleshooting try "info status" from the QEMU monitor.
>
> ss01:~# telnet localhost 4046
> Trying ::1...
> Connected to localhost.
> Escape character is '^]'.
> QEMU 1.1.2 monitor - type 'help' for more information
> (qemu)
> (qemu)
> (qemu) info status
> VM status: running
> (qemu)
> (qemu)
> (qemu) system_powerdown
> (qemu)
> (qemu)
> (qemu) info status
> VM status: running
> (qemu)
>
> Then the VM freezes.
>
And now, after it freezes, do one more "info status" also "info cpus"
and "info registers". Also what do you mean by "freezes"? Do you see
that VM started to shutdown after you issued system_powerdown?
--
Gleb.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: OpenBSD 5.3 guest on KVM
2013-09-05 18:00 ` Gleb Natapov
@ 2013-09-05 18:49 ` Daniel Bareiro
0 siblings, 0 replies; 6+ messages in thread
From: Daniel Bareiro @ 2013-09-05 18:49 UTC (permalink / raw)
To: KVM General
[-- Attachment #1: Type: text/plain, Size: 6082 bytes --]
Hi, Gleb.
On Thursday 05 September 2013 21:00:50 +0300,
Gleb Natapov wrote:
> > > > Someone had this problem and could solve it somehow? There any
> > > > debug information I can provide to help solve this?
> > > For simple troubleshooting try "info status" from the QEMU monitor.
> > ss01:~# telnet localhost 4046
> > Trying ::1...
> > Connected to localhost.
> > Escape character is '^]'.
> > QEMU 1.1.2 monitor - type 'help' for more information
> > (qemu)
> > (qemu)
> > (qemu) info status
> > VM status: running
> > (qemu)
> > (qemu)
> > (qemu) system_powerdown
> > (qemu)
> > (qemu)
> > (qemu) info status
> > VM status: running
> > (qemu)
> >
> > Then the VM freezes.
> And now, after it freezes, do one more "info status" also "info cpus"
> and "info registers". Also what do you mean by "freezes"? Do you see
> that VM started to shutdown after you issued system_powerdown?
ss01:~# telnet localhost 4046
Trying ::1...
Connected to localhost.
Escape character is '^]'.
QEMU 1.1.2 monitor - type 'help' for more information
(qemu)
(qemu) info status
VM status: running
(qemu)
(qemu) system_powerdown
(qemu)
(qemu) info status
VM status: running
(qemu)
(qemu) info status
VM status: running
(qemu)
(qemu) info cpus
* CPU #0: pc=0xffffffff80455278 thread_id=22792
(qemu) info cpus
* CPU #0: pc=0xffffffff80455278 thread_id=22792
(qemu) info cpus
* CPU #0: pc=0xffffffff80455278 thread_id=22792
(qemu)
(qemu) info registers
RAX=0000000000000000 RBX=0000000000000000 RCX=0000000000000204 RDX=000000000000b100
RSI=0000000000000022 RDI=ffff800000013900 RBP=ffff80000e7fcc80 RSP=ffff80000e7fcb78
R8 =0000000000000004 R9 =0000000000000001 R10=0000000000100000 R11=ffffffff80455b90
R12=0000000000000006 R13=ffff80000e6f2010 R14=ffff800000119900 R15=ffff80000e6f2000
RIP=ffffffff80448c60 RFL=00000046 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
ES =0023 0000000000000000 ffffbfff 00a0f300 DPL=3 DS16 [-WA]
CS =0008 0000000000000000 ffffffff 00a09b00 DPL=0 CS64 [-RA]
SS =0010 0000000000000000 ffffffff 00a09300 DPL=0 DS16 [-WA]
DS =0023 0000000000000000 ffffbfff 00a0f300 DPL=3 DS16 [-WA]
FS =0023 0000000000000000 ffffbfff 00a0f300 DPL=3 DS16 [-WA]
GS =0023 ffffffff80a27b60 ffffbfff 00a0f300 DPL=3 DS16 [-WA]
LDT=0000 0000000000000000 0000ffff 00000000
TR =0030 ffff800000011000 00000067 00008b00 DPL=0 TSS64-busy
GDT= ffff800000011068 0000003f
IDT= ffff800000010000 00000fff
CR0=8001003b CR2=00001567dc558a60 CR3=0000000000e60000 CR4=000007b0
DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000
DR6=00000000ffff0ff0 DR7=0000000000000400
EFER=0000000000000d01
FCW=037f FSW=0000 [ST=0] FTW=00 MXCSR=00001fa0
FPR0=0000000000000000 0000 FPR1=0000000000000000 0000
FPR2=0000000000000000 0000 FPR3=0000000000000000 0000
FPR4=0000000000000000 0000 FPR5=0000000000000000 0000
FPR6=0000000000000000 0000 FPR7=0000000000000000 0000
XMM00=00000000000000003fa2400000000000 XMM01=00000000000000003fe2b40000000000
XMM02=00000000000000000000000000000000 XMM03=00000000000000000000000000000000
XMM04=00000000000000000000000000000000 XMM05=00000000000000000000000000000000
XMM06=00000000000000000000000000000000 XMM07=00000000000000000000000000000000
XMM08=00000000000000000000000000000000 XMM09=00000000000000000000000000000000
XMM10=00000000000000000000000000000000 XMM11=00000000000000000000000000000000
XMM12=00000000000000000000000000000000 XMM13=00000000000000000000000000000000
XMM14=00000000000000000000000000000000 XMM15=00000000000000000000000000000000
(qemu)
(qemu) info registers
RAX=0000000000000000 RBX=0000000000000000 RCX=0000000000000204 RDX=000000000000b100
RSI=0000000000000022 RDI=ffff800000013900 RBP=ffff80000e7fcc80 RSP=ffff80000e7fcb78
R8 =0000000000000004 R9 =0000000000000001 R10=0000000000100000 R11=ffffffff80455b90
R12=0000000000000006 R13=ffff80000e6f2010 R14=ffff800000119900 R15=ffff80000e6f2000
RIP=ffffffff80448c60 RFL=00000046 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
ES =0023 0000000000000000 ffffbfff 00a0f300 DPL=3 DS16 [-WA]
CS =0008 0000000000000000 ffffffff 00a09b00 DPL=0 CS64 [-RA]
SS =0010 0000000000000000 ffffffff 00a09300 DPL=0 DS16 [-WA]
DS =0023 0000000000000000 ffffbfff 00a0f300 DPL=3 DS16 [-WA]
FS =0023 0000000000000000 ffffbfff 00a0f300 DPL=3 DS16 [-WA]
GS =0023 ffffffff80a27b60 ffffbfff 00a0f300 DPL=3 DS16 [-WA]
LDT=0000 0000000000000000 0000ffff 00000000
TR =0030 ffff800000011000 00000067 00008b00 DPL=0 TSS64-busy
GDT= ffff800000011068 0000003f
IDT= ffff800000010000 00000fff
CR0=8001003b CR2=00001567dc558a60 CR3=0000000000e60000 CR4=000007b0
DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000
DR6=00000000ffff0ff0 DR7=0000000000000400
EFER=0000000000000d01
FCW=037f FSW=0000 [ST=0] FTW=00 MXCSR=00001fa0
FPR0=0000000000000000 0000 FPR1=0000000000000000 0000
FPR2=0000000000000000 0000 FPR3=0000000000000000 0000
FPR4=0000000000000000 0000 FPR5=0000000000000000 0000
FPR6=0000000000000000 0000 FPR7=0000000000000000 0000
XMM00=00000000000000003fa2400000000000 XMM01=00000000000000003fe2b40000000000
XMM02=00000000000000000000000000000000 XMM03=00000000000000000000000000000000
XMM04=00000000000000000000000000000000 XMM05=00000000000000000000000000000000
XMM06=00000000000000000000000000000000 XMM07=00000000000000000000000000000000
XMM08=00000000000000000000000000000000 XMM09=00000000000000000000000000000000
XMM10=00000000000000000000000000000000 XMM11=00000000000000000000000000000000
XMM12=00000000000000000000000000000000 XMM13=00000000000000000000000000000000
XMM14=00000000000000000000000000000000 XMM15=00000000000000000000000000000000
What I mean by "freeze" is that if the time for a system_powerdown I had
opened a VNC connection and a ssh connection, both stop responding. Not
even I see in the VNC session that the shutdown process starts.
Thanks for your reply.
Regards,
Daniel
--
Fingerprint: BFB3 08D6 B4D1 31B2 72B9 29CE 6696 BF1B 14E6 1D37
Powered by Debian GNU/Linux - Linux user #188.598
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: OpenBSD 5.3 guest on KVM
2013-09-04 23:31 OpenBSD 5.3 guest on KVM Daniel Bareiro
2013-09-05 8:30 ` Paolo Bonzini
@ 2015-11-06 15:57 ` Paolo Bonzini
1 sibling, 0 replies; 6+ messages in thread
From: Paolo Bonzini @ 2015-11-06 15:57 UTC (permalink / raw)
To: dbareiro, KVM list
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 05/09/2013 01:31, Daniel Bareiro wrote:
> Hi all!
>
> These days I tested OpenBSD 5.3 and pleasantly surprised me notice
> that they implemented VirtIO for block devices, network and memory
> ballooning. It is an important step for those who contribute to
> the project.
>
> Now what I'm seeing is that there seems to be some sort of problem
> with the ACPI to shutdown the VM. I remember that at one time it
> was not working, then they corrected it and now seems to be new
> problems with these messages.
>
> I tried turning off the VM from libvirt (virsh) and also from Qemu
> monitor booting the VM manually and in either case the result is
> the same: the VM freezes.
>
> # sysctl hw hw.machine=amd64 hw.model=QEMU Virtual CPU version
> 1.1.2 hw.ncpu=1 hw.byteorder=1234 hw.pagesize=4096
> hw.disknames=cd0:,sd0:be0e0f1c0cdc4dae,fd0:,fd1: hw.diskcount=4
> hw.cpuspeed=2009 hw.vendor=Bochs hw.product=Bochs
> hw.uuid=501ef229-2337-165f-8da3-905b12832049 hw.physmem=535814144
> hw.usermem=535801856 hw.ncpufound=1 hw.allowpowerdown=1
>
>
> hw.allowpowerdown set to 1 (the default) allows a power button
> shutdown.
>
> Someone had this problem and could solve it somehow? There any
> debug information I can provide to help solve this?
Sure, you can gather a trace on the host using trace-cmd.
trace-cmd record -e kvm qemu-system-x86_64 --enable-kvm ...
This will produce a huge trace.dat file. You can compress it with xz
and send it my way.
Thanks,
Paolo
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2015-11-06 15:57 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-09-04 23:31 OpenBSD 5.3 guest on KVM Daniel Bareiro
2013-09-05 8:30 ` Paolo Bonzini
2013-09-05 15:44 ` Daniel Bareiro
2013-09-05 18:00 ` Gleb Natapov
2013-09-05 18:49 ` Daniel Bareiro
2015-11-06 15:57 ` Paolo Bonzini
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox