Hi Jonas, On Thu, Jan 23, 2014 at 9:34 AM, Jonas Bülow <[email protected]> wrote: > There is no bhyve process when this happens. >
I am at a loss to explain this. Do you happen to have a console log or shell history that may help in figuring this out? Even better would be if you can reproduce this and I can debug this locally based on your steps. best Neel > /j > >> 23 jan 2014 kl. 18:07 skrev Neel Natu <[email protected]>: >> >> Hi Jonas, >> >>> On Thu, Jan 23, 2014 at 8:00 AM, Jonas Bülow <[email protected]> wrote: >>> I will describe the steps when I manage to reproduce the installation. >>> Right now I get stuck with undestroyable vm instances: >>> >>> root@bulow:/mnt/bhyve-script # ls /dev/vmm/ >>> >>> lin0 >>> >>> root@bulow:/mnt/bhyve-script # bhyvectl --destroy --vm=lin0 >>> >>> errno = 22 >> >> Hmm… can you tell what the bhyve process associated with lin0 is doing >> from 'top' or 'ps'? >> >> What happens if you send a SIGTERM to the bhyve process? >> >> best >> Neel >> >>> >>> On Thu, Jan 23, 2014 at 3:44 PM, Matthias Gamsjager >>> <[email protected]>wrote: >>> >>>> Could you elaborate what you did to get it working? >>>> >>>> >>>> On Thu, Jan 23, 2014 at 3:41 PM, Jonas Bülow <[email protected]>wrote: >>>> >>>>> Success. I have a working ubuntu 13.10 running under bhyve on FreeBSD >>>>> 10.0-RELEASE. >>>>> >>>>> >>>>> >>>>> /J >>>>> >>>>> >>>>> On Thu, Jan 23, 2014 at 11:37 AM, Aryeh Friedman >>>>> <[email protected]>wrote: >>>>> >>>>>> >>>>>> >>>>>> >>>>>> On Thu, Jan 23, 2014 at 5:05 AM, Jonas Bülow <[email protected] >>>>>> wrote: >>>>>> >>>>>>> I do use the precanned bhyve-script "vm0" (if that is what you mean). >>>>> It >>>>>>> explicitly mentions linux support. bhyveload can't be user for other >>>>> images >>>>>>> than FreeBSD so I don't know how to use your script for a linux OS >>>>>> >>>>>> Since I have not used bhyve-grub personally yet I can not recommend what >>>>>> the correct loader command line but if bhyve-script is in anyway >>>>> related to >>>>>> vmrun.sh I would be highly suspicious of any command lines you manage to >>>>>> extract from it since they are often not the ones actual called. >>>>>> >>>>>> >>>>>>> >>>>>>> I assume the image is file backed as I have not assigned a dedicated >>>>>>> partition to the vm (and I don't know how to do that). >>>>>> >>>>>> You can keep them anywhere no need for a special volume (mater of fact I >>>>>> was just reusing the name of one of the diretoriess that PC creates >>>>> during >>>>>> install even without it being a different vol [just assumes any FS >>>>>> boundaries are the host OS's problem)... you can put the disk image any >>>>>> where (your home directory would be fine for example) >>>>> _______________________________________________ >>>>> [email protected] mailing list >>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization >>>>> To unsubscribe, send any mail to " >>>>> [email protected]" >>> _______________________________________________ >>> [email protected] mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization >>> To unsubscribe, send any mail to >>> "[email protected]" _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "[email protected]"
