From owner-freebsd-virtualization@freebsd.org Mon Apr 11 17:53:30 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6A93BB0C455 for ; Mon, 11 Apr 2016 17:53:30 +0000 (UTC) (envelope-from phk@phk.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id 006B21122; Mon, 11 Apr 2016 17:53:29 +0000 (UTC) (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.55.3]) by phk.freebsd.dk (Postfix) with ESMTP id A8E084FB03; Mon, 11 Apr 2016 17:53:21 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.15.2/8.15.2) with ESMTP id u3BHrKMo016581; Mon, 11 Apr 2016 17:53:20 GMT (envelope-from phk@phk.freebsd.dk) To: Peter Grehan cc: "freebsd-virtualization@freebsd.org" Subject: Re: -current host, 10.1 client loops In-reply-to: <570B3604.8020500@freebsd.org> From: "Poul-Henning Kamp" References: <20918.1458052609@critter.freebsd.dk> <23329.1458077441@critter.freebsd.dk> <28223.1458163559@critter.freebsd.dk> <723.1460154499@critter.freebsd.dk> <570B3604.8020500@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <16579.1460397200.1@critter.freebsd.dk> Content-Transfer-Encoding: quoted-printable Date: Mon, 11 Apr 2016 17:53:20 +0000 Message-ID: <16580.1460397200@critter.freebsd.dk> X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Apr 2016 17:53:30 -0000 -------- In message <570B3604.8020500@freebsd.org>, Peter Grehan writes: Ok, host is: 11.0-CURRENT #0 r297514M: Sun Apr 3 13:11:49 UTC 2016 CPU: AMD Athlon(tm) II X3 455 Processor (3311.19-MHz K8-class CPU) Origin=3D"AuthenticAMD" Id=3D0x100f53 Family=3D0x10 Model=3D0x5 Ste= pping=3D3 Features=3D0x178bfbff Features2=3D0x802009 AMD Features=3D0xee500800 AMD Features2=3D0x837ff SVM: NP,NRIP,NAsids=3D64 TSC: P-state invariant real memory =3D 17179869184 (16384 MB) avail memory =3D 16573874176 (15806 MB) Event timer "LAPIC" quality 400 ACPI APIC Table: <090712 APIC1033> FreeBSD/SMP: Multiprocessor System Detected: 3 CPUs FreeBSD/SMP: 1 package(s) x 3 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 Guest is (still) 10.1-R Running with: sed 's/virtio-blk/ahci-hd/' \ /usr/share/examples/bhyve/vmrun.sh \ > vmrun_ada.sh sh vmrun_ada.sh \ -m 1G \ -c 3 \ -t ${VMN} \ -d ${P}.root.dd \ -d ${P}.swap.dd \ -d ${P}.tami_install.dd \ vm${VMU} || true Hanging now, trying to build some port. I may be able to find out which exact port later, but for now I'll leave it hanging, in case you have any ideas for pulling out more info. CTRL-T in the console works load: 10.99 cmd: sh 43413 [running] 22940.67r 0.00u 0.00s 100% 228k load: 10.99 cmd: sh 43413 [running] 22940.88r 0.00u 0.00s 100% 228k load: 10.99 cmd: sh 43413 [running] 22941.08r 0.00u 0.00s 100% 228k load: 10.99 cmd: sh 43413 [running] 22941.28r 0.00u 0.00s 100% 228k load: 10.99 cmd: sh 43413 [running] 22941.49r 0.00u 0.00s 100% 228k ^Z ^Z load: 10.29 cmd: sh 43413 [running] 22957.30r 0.00u 0.00s 100% 228k load: 10.29 cmd: sh 43413 [running] 22957.49r 0.00u 0.00s 100% 228k load: 10.29 cmd: sh 43413 [running] 22957.66r 0.00u 0.00s 100% 228k load: 10.29 cmd: sh 43413 [running] 22957.83r 0.00u 0.00s 100% 228k ^Z Suspended = root@:~ # = root@:~ # = root@:~ # = root@:~ # ps -axlwH load: 10.53 cmd: csh 669 [runnable] 29867.68r 0.02u 107.86s 0% 2392k load: 10.53 cmd: csh 669 [runnable] 29868.27r 0.02u 107.86s 0% 2392k load: 10.53 cmd: csh 669 [runnable] 29868.52r 0.02u 107.86s 0% 2392k [... 3 hours later still the same ...] > Also, if the guest looks like it hangs, you can extract the RIPs with > bhyvectl --get-rip --cpu=3D0 --vm=3D > bhyvectl --get-rip --cpu=3D1 --vm=3D > > This might give a hint as to where the guest is spinning. =3D=3D> _cpu_0 <=3D=3D rip[0] 0x00000000c0b14780 rip[0] 0x00000000c0b14782 rip[0] 0x00000000c0b14780 rip[0] 0x00000000c0b14780 rip[0] 0x00000000c0b14780 rip[0] 0x00000000c0b14780 =3D=3D> _cpu_1 <=3D=3D rip[1] 0x00000000c0b14780 rip[1] 0x00000000c0b14782 rip[1] 0x00000000c0b14780 rip[1] 0x00000000c0b14780 rip[1] 0x00000000c0b14780 rip[1] 0x00000000c0b14780 =3D=3D> _cpu_2 <=3D=3D rip[2] 0x00000000c100feb0 rip[2] 0x00000000c100feb0 rip[2] 0x00000000c100feb0 rip[2] 0x00000000c100feb0 rip[2] 0x00000000c100feb0 rip[2] 0x00000000c100feb2 Any ideas ? -- = Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe = Never attribute to malice what can adequately be explained by incompetence= .