Date: Thu, 23 Jan 2014 18:34:32 +0100 From: =?utf-8?Q?Jonas_B=C3=BClow?= <jonas.bulow@gmail.com> To: Neel Natu <neelnatu@gmail.com> Cc: "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org> Subject: Re: Linux on BHyVe in 10.0-RELEASE Message-ID: <F66A3979-EE18-437A-8DCE-1F0FBD58DDF1@gmail.com> In-Reply-To: <CAFgRE9FmRNLrjePeHhX7r5d00GAMLzXjvKoZcY8wwqbYUX8T9g@mail.gmail.com> References: <CAEGOEeUo-spSp051MWg-4%2B_vDACBK9NqWOPz7LBdDEHvGS3=_w@mail.gmail.com> <52E0C1D4.9000304@freebsd.org> <CAEGOEeWbysCn5Ma-aGOLGmbJPTn0CTa%2BMjRvwGVYm7jJJ57coQ@mail.gmail.com> <52E0D1BB.2050807@callfortesting.org> <CAEGOEeVUvHmypGBgd0V=Ffhzex2zsVuihA8rbxhLX9QCFxvO%2Bg@mail.gmail.com> <CAGBxaXm1-0NBwOTx40V9C-Z0wF5a9y%2BHNMRuM-N5UansiiREeQ@mail.gmail.com> <CAEGOEeV2=3Nn-5rebUJfNL-xeutSZH5_i7HkiB9ucEC%2BPD2_nw@mail.gmail.com> <CAGBxaXkui_vc0RLNcXab6qE2YRXyXRcP-p=KmwtQBsF87mDYXw@mail.gmail.com> <CAEGOEeV7rOogDA3NhZFMjbQ30ygJ4s%2BnD=DkvMNj-KR3Vah35w@mail.gmail.com> <CAGBxaX=aBYeXVKC5TNW%2Bu_VNMbbrgU251XA0w7rVUmqZ=PvjAA@mail.gmail.com> <CAEGOEeVhK9mQ2xh3VPCoUNDQR5X-SE1ZEjnNp3CcRwmkMMCzRA@mail.gmail.com> <CAGBxaXkq=AG%2B%2BdwxpAu3W=0UQBgbWzutkSV=EauNGDsgTYNS1Q@mail.gmail.com> <CAEGOEeVshDQPm5pU0B5Mq5M3Bw3F2u1oMteTRbm8PY7qyWt=zA@mail.gmail.com> <CA%2BD9QhvsQ1oB%2BXL8fmB3P2XCXnuO2ONnf5zUSNB-CBdpVm5XWg@mail.gmail.com> <CAEGOEeXWE0hZhLBCXR2CNVwE9GH9xOMgzKGtfoxEkq9HhRretQ@mail.gmail.com> <CAFgRE9FmRNLrjePeHh X7r5d00GAMLzXjvKoZcY8wwqbYUX8T9g@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
There is no bhyve process when this happens. /j > 23 jan 2014 kl. 18:07 skrev Neel Natu <neelnatu@gmail.com>: >=20 > Hi Jonas, >=20 >> On Thu, Jan 23, 2014 at 8:00 AM, Jonas B=C3=BClow <jonas.bulow@gmail.com>= wrote: >> I will describe the steps when I manage to reproduce the installation. >> Right now I get stuck with undestroyable vm instances: >>=20 >> root@bulow:/mnt/bhyve-script # ls /dev/vmm/ >>=20 >> lin0 >>=20 >> root@bulow:/mnt/bhyve-script # bhyvectl --destroy --vm=3Dlin0 >>=20 >> errno =3D 22 >=20 > Hmm=E2=80=A6 can you tell what the bhyve process associated with lin0 is d= oing > from 'top' or 'ps'? >=20 > What happens if you send a SIGTERM to the bhyve process? >=20 > best > Neel >=20 >>=20 >> On Thu, Jan 23, 2014 at 3:44 PM, Matthias Gamsjager <mgamsjager@gmail.com= >wrote: >>=20 >>> Could you elaborate what you did to get it working? >>>=20 >>>=20 >>> On Thu, Jan 23, 2014 at 3:41 PM, Jonas B=C3=BClow <jonas.bulow@gmail.com= >wrote: >>>=20 >>>> Success. I have a working ubuntu 13.10 running under bhyve on FreeBSD >>>> 10.0-RELEASE. >>>>=20 >>>>=20 >>>>=20 >>>> /J >>>>=20 >>>>=20 >>>> On Thu, Jan 23, 2014 at 11:37 AM, Aryeh Friedman >>>> <aryeh.friedman@gmail.com>wrote: >>>>=20 >>>>>=20 >>>>>=20 >>>>>=20 >>>>> On Thu, Jan 23, 2014 at 5:05 AM, Jonas B=C3=BClow <jonas.bulow@gmail.c= om >>>>> wrote: >>>>>=20 >>>>>> 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 >>>>>=20 >>>>> Since I have not used bhyve-grub personally yet I can not recommend wh= at >>>>> 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 t= o >>>>> extract from it since they are often not the ones actual called. >>>>>=20 >>>>>=20 >>>>>>=20 >>>>>> 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). >>>>>=20 >>>>> 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 an= y >>>>> where (your home directory would be fine for example) >>>> _______________________________________________ >>>> freebsd-virtualization@freebsd.org mailing list >>>> http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization >>>> To unsubscribe, send any mail to " >>>> freebsd-virtualization-unsubscribe@freebsd.org" >> _______________________________________________ >> freebsd-virtualization@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization >> To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@free= bsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F66A3979-EE18-437A-8DCE-1F0FBD58DDF1>