Re: OpenBSD 5.3 guest on KVM

2015-11-06 Thread Paolo Bonzini
-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
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: OpenBSD 5.3 guest on KVM

2013-09-05 Thread Paolo Bonzini
-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-
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: OpenBSD 5.3 guest on KVM

2013-09-05 Thread Daniel Bareiro
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 2 -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


signature.asc
Description: Digital signature


Re: OpenBSD 5.3 guest on KVM

2013-09-05 Thread Gleb Natapov
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.
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: OpenBSD 5.3 guest on KVM

2013-09-05 Thread Daniel Bareiro
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=0x80455278 thread_id=22792
(qemu) info cpus
* CPU #0: pc=0x80455278 thread_id=22792
(qemu) info cpus
* CPU #0: pc=0x80455278 thread_id=22792
(qemu)
(qemu) info registers
RAX= RBX= RCX=0204 
RDX=b100
RSI=0022 RDI=80013900 RBP=8e7fcc80 
RSP=8e7fcb78
R8 =0004 R9 =0001 R10=0010 
R11=80455b90
R12=0006 R13=8e6f2010 R14=80119900 
R15=8e6f2000
RIP=80448c60 RFL=0046 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
ES =0023  bfff 00a0f300 DPL=3 DS16 [-WA]
CS =0008   00a09b00 DPL=0 CS64 [-RA]
SS =0010   00a09300 DPL=0 DS16 [-WA]
DS =0023  bfff 00a0f300 DPL=3 DS16 [-WA]
FS =0023  bfff 00a0f300 DPL=3 DS16 [-WA]
GS =0023 80a27b60 bfff 00a0f300 DPL=3 DS16 [-WA]
LDT=   
TR =0030 80011000 0067 8b00 DPL=0 TSS64-busy
GDT= 80011068 003f
IDT= 8001 0fff
CR0=8001003b CR2=1567dc558a60 CR3=00e6 CR4=07b0
DR0= DR1= DR2= 
DR3=
DR6=0ff0 DR7=0400
EFER=0d01
FCW=037f FSW= [ST=0] FTW=00 MXCSR=1fa0
FPR0=  FPR1= 
FPR2=  FPR3= 
FPR4=  FPR5= 
FPR6=  FPR7= 
XMM00=3fa24000 XMM01=3fe2b400
XMM02= XMM03=
XMM04= XMM05=
XMM06= XMM07=
XMM08= XMM09=
XMM10= XMM11=
XMM12= XMM13=
XMM14= XMM15=
(qemu)
(qemu) info registers
RAX= RBX= RCX=0204 
RDX=b100
RSI=0022 RDI=80013900 RBP=8e7fcc80 
RSP=8e7fcb78
R8 =0004 R9 =0001 R10=0010 
R11=80455b90
R12=0006 R13=8e6f2010 R14=80119900 
R15=8e6f2000
RIP=80448c60 RFL=0046 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
ES =0023  bfff 00a0f300 DPL=3 DS16 [-WA]
CS =0008   00a09b00 DPL=0 CS64 [-RA]
SS =0010   00a09300 DPL=0 DS16 [-WA]
DS =0023  bfff 00a0f300 DPL=3 DS16 [-WA]
FS =0023  bfff 00a0f300 DPL=3 DS16 [-WA]
GS =0023 80a27b60 bfff 00a0f300 DPL=3 DS16 [-WA]
LDT=   
TR =0030 80011000 0067 8b00 DPL=0 TSS64-busy
GDT= 80011068 003f
IDT= 8001 0fff
CR0=8001003b CR2=1567dc558a60 CR3=00e6 CR4=07b0
DR0= DR1= DR2= 
DR3=
DR6=0ff0 DR7=0400
EFER=0d01
FCW=037f FSW= [ST=0] FTW=00 MXCSR=1fa0
FPR0=  FPR1= 
FPR2=  FPR3= 
FPR4=  FPR5= 
FPR6=  FPR7= 
XMM00=3fa24000 XMM01=3fe2b400