Re: -current host, 10.1 client loops

In message <570c74cf.1080...@freebsd.org>, Peter Grehan writes: > I'll try with a bit more CPU oversubscription and see if I can hit >this. Thanks for the info - this should help track it down. For what its worth, I think the port being compiled was: /usr/ports/www/p5-Mozill

Re: -current host, 10.1 client loops

CTRL-T in the console works ... ==> _cpu_0 <== rip[0] 0xc0b14780 rip[0] 0xc0b14782 There are the RIPs that show when the system is idle. ==> _cpu_2 <== rip[2] 0xc100feb0 This is the TLB shootdown l

Re: -current host, 10.1 client loops

In message <570b3604.8020...@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="AuthenticAMD" Id=0x100f53 Family=0x10 Model=0x5 St

Re: -current host, 10.1 client loops

Hi Poul-Henning, With the host now running: FreeBSD 11.0-CURRENT #0 r297514M And (another) i386 guest running: FreeBSD 11.0-CURRENT #3 r297721M I do not see the problem. I'm going to try the 10.1/i386 guest over the weekend. I've not yet been able to reproduce this. I've

Re: -current host, 10.1 client loops

In message , =?UTF-8?Q?Olivier_Cochard=2DLabb=C3=A9?= writes: With the host now running: FreeBSD 11.0-CURRENT #0 r297514M And (another) i386 guest running: FreeBSD 11.0-CURRENT #3 r297721M I do not see the problem. I'm going to try the 10.1/i386 guest over the weeken

Re: -current host, 10.1 client loops

On Wed, Mar 16, 2016 at 10:25 PM, Poul-Henning Kamp wrote: > > How do I tell that script to use ahci-hd ? > > ​You just need to replace virtio-blk by ahci-hd in the script, like: sed 's/virtio-blk/ahci-hd/g' /usr/share/examples/bhyve/vmrun.sh > ~/vmrun-ahci.sh ​And running ~/vmrun-ahci.sh in pl

Re: -current host, 10.1 client loops

On Thu, Mar 17, 2016 at 12:38 AM, Poul-Henning Kamp wrote: > > In message > , > =?UTF-8?Q?Olivier_Cochard=2D > Labb=C3=A9?= writes: > > >>> How do I tell that script to use ahci-hd ? >>> >>> >>You just need to replace virtio-blk by ahci-hd in the script, like: > > Ok, it also hung with

Re: -current host, 10.1 client loops

In message , Neel Natu writes: I tried a i386 -current guest, and it hung, both cores spinning during a buildworld. This should make it pretty easy for somebody else to reproduce. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 F

Re: -current host, 10.1 client loops

In message , Neel Natu writes: >https://www.freebsd.org/releases/10.1R/errata.html#open-issues > >Can you try to reproduce after setting 'vfs.unmapped_buf_allowed=0' at >the guest loader prompt? > >The issue doesn't mention bhyve specifically but given that it's a >simple workaround it s

Re: -current host, 10.1 client loops

In message , Neel Natu writes: >A couple of suggestions to narrow it down further: >- try to reproduce with 2 or 4 vcpus (3 cpus is probably not a well >tested configuration) Well I only have 3 cpus to begin with, and it happened with two and not (so far) with one. >- try to reproduc

Re: -current host, 10.1 client loops

In message , =?UTF-8?Q?Olivier_Cochard=2D Labb=C3=A9?= writes: >> How do I tell that script to use ahci-hd ? >> >> >You just need to replace virtio-blk by ahci-hd in the script, like: Ok, it also hung with ahci-hd and two disks... Just to make sure I have asked about this: Are there

Re: -current host, 10.1 client loops

In message , Neel Natu writes: >- try to reproduce with the ahci-hd device emulation instead of virtio-blk. Ok, I tried to find how to do that but failed... I start bhyve like this: sh -x /usr/share/examples/bhyve/vmrun.sh \ -m 1G \ -c 1 \

Re: -current host, 10.1 client loops

In message , Neel Natu writes: >Can you try to reproduce after setting 'vfs.unmapped_buf_allowed=0' at >the guest loader prompt? It hung in a buildworld over night with this set. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 F

Re: -current host, 10.1 client loops

In message , =?UTF-8?Q?Olivier_Cochard=2D Labb=C3=A9?= writes: >You just need to replace virtio-blk by ahci-hd in the script, like: Crude :-) Ok, started it with two vcpus, will report later... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/I

Re: -current host, 10.1 client loops

In message , Neel Natu writes: >Also, if it is possible to reproduce with a single vcpu then it will >help when analyzing the output of ktrdump. Well, on the gutfeeling that it might help I gave a '-c 1' and that seems to prevent the problem from happening so I could get my builds done.

Re: -current host, 10.1 client loops

Hi, On Tue, Mar 15, 2016 at 7:36 AM, Poul-Henning Kamp wrote: > I'm seing bhyve go into some kind of endless loop while trying to > compile the gcc port on 10.1 as guest. > > In one case CTRL-T on the console kept working, but showed an rm(1) > process raking up CPU time. > > Are there known bogo

Re: -current host, 10.1 client loops

Hi, On Tue, Mar 15, 2016 at 2:30 PM, Poul-Henning Kamp wrote: > > In message > > , Neel Natu writes: > >>Also, if it is possible to reproduce with a single vcpu then it will >>help when analyzing the output of ktrdump. > > Well, on the gutfeeling that it might help I gave a '-c 1' and

-current host, 10.1 client loops

I'm seing bhyve go into some kind of endless loop while trying to compile the gcc port on 10.1 as guest. In one case CTRL-T on the console kept working, but showed an rm(1) process raking up CPU time. Are there known bogon in current/bhyve or using 10.1-R/i386 as a guest I have not spotted ? How