Re: bhyve VM crashed
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 ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: bhyve VM crashed
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. ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: bhyve VM crashed
Yep, /usr/sbin/bhyveload -m 12G -d /vm/100amd64/disk.img -c /dev/nmdm1A 100amd64 Steve On Wed, Apr 09, 2014 at 04:54:36AM +0900, Takuya ASADA wrote: > Did you execute bhyveload before bhyve? > > > 2014-04-09 4:26 GMT+09:00 Steve Wills : > > > On Tue, Apr 08, 2014 at 11:43:27AM -0700, Peter Grehan wrote: > > > Hi Steve, > > > > > > > I experienced a bhyve VM crash with this message: > > > > > > > > vm exit[1] > > > > reason VMX > > > > rip 0x80c7490b > > > > inst_length 3 > > > > status 0 > > > > exit_reason 2 > > > > > > That's a triple-fault :( > > > > > > (the exit reasons are the VMX ones in Appendix C, Vol 3 of the Intel > > SDM). > > > > > > Any idea what was happening at the time ? > > > > The VM was building ports. I could try to deduce which ports, but I > > wouldn't be > > 100% sure. > > > > > 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, > > Steve > > ___ > > freebsd-virtualization@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > > To unsubscribe, send any mail to " > > freebsd-virtualization-unsubscr...@freebsd.org" > > ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: bhyve VM crashed
Did you execute bhyveload before bhyve? 2014-04-09 4:26 GMT+09:00 Steve Wills : > On Tue, Apr 08, 2014 at 11:43:27AM -0700, Peter Grehan wrote: > > Hi Steve, > > > > > I experienced a bhyve VM crash with this message: > > > > > > vm exit[1] > > > reason VMX > > > rip 0x80c7490b > > > inst_length 3 > > > status 0 > > > exit_reason 2 > > > > That's a triple-fault :( > > > > (the exit reasons are the VMX ones in Appendix C, Vol 3 of the Intel > SDM). > > > > Any idea what was happening at the time ? > > The VM was building ports. I could try to deduce which ports, but I > wouldn't be > 100% sure. > > > 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, > Steve > ___ > freebsd-virtualization@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to " > freebsd-virtualization-unsubscr...@freebsd.org" > ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: bhyve VM crashed
On Tue, Apr 08, 2014 at 11:43:27AM -0700, Peter Grehan wrote: > Hi Steve, > > > I experienced a bhyve VM crash with this message: > > > > vm exit[1] > > reason VMX > > rip 0x80c7490b > > inst_length 3 > > status 0 > > exit_reason 2 > > That's a triple-fault :( > > (the exit reasons are the VMX ones in Appendix C, Vol 3 of the Intel SDM). > > Any idea what was happening at the time ? The VM was building ports. I could try to deduce which ports, but I wouldn't be 100% sure. > 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, Steve ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: bhyve VM crashed
The host is running FreeBSD 11.0-CURRENT r264056. The guest is running FreeBSD 10.0-RELEASE r260789. Steve On Tue, Apr 08, 2014 at 02:39:00PM -0400, Aryeh Friedman wrote: > What was the guest OS? > > > On Tue, Apr 8, 2014 at 2:28 PM, Steve Wills wrote: > > > Hi, > > > > I experienced a bhyve VM crash with this message: > > > > vm exit[1] > > reason VMX > > rip 0x80c7490b > > inst_length 3 > > status 0 > > exit_reason 2 > > qualification 0x > > inst_type 0 > > inst_error 0 > > > > Not sure what that means, anyone have any ideas? This VM is running FreeBSD > > 10.0-RELEASE, 64bit. Let me know what other info would be helpful. > > > > Thanks, > > Steve > > > > ___ > > freebsd-virtualization@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > > To unsubscribe, send any mail to " > > freebsd-virtualization-unsubscr...@freebsd.org" > > > > > > -- > Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: bhyve VM crashed
Hi Steve, I experienced a bhyve VM crash with this message: vm exit[1] reason VMX rip 0x80c7490b inst_length 3 status 0 exit_reason 2 That's a triple-fault :( (the exit reasons are the VMX ones in Appendix C, Vol 3 of the Intel SDM). Any idea what was happening at the time ? Also, for the guest, do you have the config that was being used (e.g. bhyve command line) ? later, Peter. ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: bhyve VM crashed
What was the guest OS? On Tue, Apr 8, 2014 at 2:28 PM, Steve Wills wrote: > Hi, > > I experienced a bhyve VM crash with this message: > > vm exit[1] > reason VMX > rip 0x80c7490b > inst_length 3 > status 0 > exit_reason 2 > qualification 0x > inst_type 0 > inst_error 0 > > Not sure what that means, anyone have any ideas? This VM is running FreeBSD > 10.0-RELEASE, 64bit. Let me know what other info would be helpful. > > Thanks, > Steve > > ___ > freebsd-virtualization@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to " > freebsd-virtualization-unsubscr...@freebsd.org" > -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
bhyve VM crashed
Hi, I experienced a bhyve VM crash with this message: vm exit[1] reason VMX rip 0x80c7490b inst_length 3 status 0 exit_reason 2 qualification 0x inst_type 0 inst_error 0 Not sure what that means, anyone have any ideas? This VM is running FreeBSD 10.0-RELEASE, 64bit. Let me know what other info would be helpful. Thanks, Steve ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
