Date: Tue, 08 Apr 2014 14:14:32 -0700 From: Peter Grehan <grehan@freebsd.org> To: Steve Wills <swills@freebsd.org> Cc: freebsd-virtualization@freebsd.org Subject: Re: bhyve VM crashed Message-ID: <534466B8.9060708@freebsd.org> In-Reply-To: <20140408192635.GB89356@mouf.net> References: <20140408182844.GC84921@mouf.net> <5344434F.6000004@freebsd.org> <20140408192635.GB89356@mouf.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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. Some more questions: Were there other VMs running at the same time ? What's the type of host CPU/number of CPUs/amount of RAM ? Did the VM have much uptime before the crash ? Have you been able to run similar VMs on prior CURRENT releases without this issue (i.e. have we introduced a regression) ? >> 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 later, Peter.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?534466B8.9060708>