On Tue, Apr 08, 2014 at 02:14:32PM -0700, Peter Grehan wrote: > Hi Steve, > > > The VM was building ports. I could try to deduce which ports, but I > > wouldn't be 100% sure. > > Probably no need, unless this can be repro'd by building that > particular port.
Ok, I'll keep an eye out for that. > Some more questions: Were there other VMs running at the same time ? Yes, there's currently a 9.2 amd64 guest as well, which was also running then and is still running. > What's the type of host CPU/number of CPUs/amount of RAM ? Did the VM hw.model: Intel(R) Xeon(R) CPU E5-2660 0 @ 2.20GHz hw.ncpu: 32 hw.physmem: 68644569088 > have much uptime before the crash ? Have you been able to run similar Was up maybe 4 days, not 100% sure, but I think that's right. > VMs on prior CURRENT releases without this issue (i.e. have we > introduced a regression) ? Don't know, just started doing this. > >> Also, for the guest, do you have the config that was being used > >> (e.g. bhyve command line) ? > > > > /usr/sbin/bhyve -c 4 -m 12G -A -H -P -g 0 -s 0:0,hostbridge -s > > 1:0,lpc -s 2:0,virtio-net,tap1,mac=58:9c:fc:01:01:02 -s > > 3:0,virtio-blk,/vm/100amd64/disk.img -l com1,/dev/nmdm1A 100amd64 > > Thanks for that. > > If you see this again, would you be able to grab VM state for all the > vcpus with > > bhyvectl --get-all --cpu=0 --vm=100amd64 > bhyvectl --get-all --cpu=1 --vm=100amd64 > bhyvectl --get-all --cpu=2 --vm=100amd64 > bhyvectl --get-all --cpu=3 --vm=100amd64 Will do, thanks! Steve _______________________________________________ email@example.com mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"