Date: Tue, 28 Oct 2014 14:41:32 -0400 From: Allan Jude <allanjude@freebsd.org> To: freebsd-virtualization@freebsd.org Subject: Re: core dump after centos-6.5 install Message-ID: <544FE35C.4020509@freebsd.org> In-Reply-To: <544FE307.70200@nomadlogic.org> References: <544FDD34.7070506@nomadlogic.org> <544FE0D2.4090704@freebsd.org> <544FE307.70200@nomadlogic.org>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On 2014-10-28 14:40, Pete Wright wrote: > > > On 10/28/14 11:30, Allan Jude wrote: >> On 2014-10-28 14:15, Pete Wright wrote: >>> just had bhyve coredump on me and was wondering if anyone else had seen >>> this behavior: >>> >>>> uname -ar >>> FreeBSD pop.rubicorp.com 10.1-RC3 FreeBSD 10.1-RC3 #0 r273437: Tue Oct >>> 21 23:55:15 UTC 2014 >>> root@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 >>>> pkg info|grep grub2 >>> grub2-bhyve-0.24 Grub-emu loader for bhyve >>> >>> I was following the instructions on this page to use grub-bhyve to >>> install CentOS-6.5_amd64 on my 10.1-RC3 hypervisor: >>> https://www.monkeybrains.net/support/bhyve >>> >>> The installation went through as expected. I ran grub-bhyve w/o issues, >>> then executed the bhyve command and installation proceeded without >>> issue. When bhyve exited I re-ran my bhyve command to start my VM >>> resulting in this: >>> >>> >>>> sudo /tmp/cmd.sh >>> Assertion failed: (error == 0), function fbsdrun_addcpu, file >>> /usr/src/usr.sbin/bhyve/bhyverun.c, line 266. >>> Abort trap (core dumped) >>> >>> >>> I have run gdb against the resulting core file, but since there are no >>> debug symbols in there I don't think it's useful. Please let me know if >>> this is a pebkac event, or if I should file a PR. >>> >>> Thanks! >>> -pete >>> >> >> After the first run, before the second, did you bhyvectl --destroy --vm=blah >> >> and then do the grub-bhyve step again (off the disk instead of the >> install image this time) >> >> > > Thanks Allan - I misread the instructions on the site - makes sense. I > am working through getting centos to boot now. unfortunately the kernel > is not named vmlinuz by default IIRC. > > -pete > > If you follow my instructions here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/virtualization-host-bhyve.html#virtualization-bhyve-linux it walks you through using 'ls' in grub to find the correct name of the kernel files. -- Allan Jude [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQIcBAEBAgAGBQJUT+NeAAoJEJrBFpNRJZKfdLcQAINHNh/u2U2owhwFIxqaS09H QcY42lXzLdzte/49uot3CL4A3+CYMxW8ETBL7TFuRF7K1sMDYSPQx/95lcSfhzm4 6qTGK2xRnOehJNOd8pQmoKrwmI7t31G0I822LMfrIaGWjO/heUE+hNCFDO3WyHlJ J8GHUYaspTxtOoC/ZA8E+TYok1ypx71H59AzcQjalWBTXYJMyCt6O3FRluHfxOZ/ SUK6Db6AY0Wj/GpHqWmM7lPFZOr7HVFjcEWvcjRWYlSAhw4IGm3Ch1hllMGLVas+ I3uVk6ui6OInDO0pmt9Pj4ntKoUQU+M/tCtaOX/ikT2M1bOT2KEqPLd+Oz/BVURy JjA4eMsWnytQO2nf8XW69PtRu+zDusl/GEOT0YUhwZWkeST9yT+MEHIbBJGSv89C lv3UMd+BTzxfe2NdcNO7fT8KUCGbVHcnOFtzLiNI0ngJpKPlS5DtOC/WEVYjYgEm izPdpTXVVyw8OuwVqUo/InHQAcxH1ueZD2vBAA6SwzaqrZB2qaq5zXDNPIIhYLrr WnSryts4hDipOJjc7vZp/nqD/0i5nyoRxLN8X5GEguTcSbiFmoQB+uJbTT6N4Rrd 8zlCes0KwlEPpEBL1Y8rDNJMGK9qu1I2yT1oHf/RNEcCwlqZF0SsdPcuk4cG7hkL ItzAHKZifR9hdn/TDIKn =6bVO -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?544FE35C.4020509>