Where did you get the orignial starter script for this from was it from vmrun or the petitecloud sample script I posted... 2 reasons for asking:
1. It is turning out to be annoying inflexible in-terms of the values of various parameters (I can compensate for most of this in my personal playing with it to make it fit into petitecloud) 2. It uses a non-existent option (-I) Both are characterstics of petitecloud scripts but not so much of vmrun.sh (the main reason I do not recommend using petitecloud scripts except as nothing but barebone starter scripts if you use them to make your own). The reason for bringing all the above up is I am having a very hard time getting it to work and if it is from petitecloud can you please kindly walk me through how you went from my script to yours... the main issue I am attempting to over come is currently PC assumes that there is a single "disk" that represents the "instance" (a running instance is nothing more then loading it into RAM and wrapping a hyperv around it) [e.g. something like /vms/import/ubu.img] and that it contains *ALL* the data that is needed to boot (i.e. no other files are needed)... so far it appears (and I hope I am wrong) there is no way to force a linux instance into this model because you have to have the disk, the cd and the device map in the same dir but kept as separate files.... namely something like this: linux/ device.map disk.img cd.img seems to be the only model grub2-bhyve will be able to boot (symlinks at least on the surface seem to be a no go also...)... there are the following problems with this model though when doing mass VM's: * You have to copy the CD repeatedly to the boot dir (this is likely why openstack does not support cd based installs) * It makes for a really messy when attempting to make sure you completely nuke a vm when you delete it (currently pettiecloud does not delete the disk when the instance is deleted but this will be an option soon an likely the default) Of course the long term solution is unified off disk (vs. off loader) booting but until then any good work arounds? On Tue, Jan 28, 2014 at 6:23 AM, Markiyan Kushnir < markiyan.kush...@gmail.com> wrote: > 2014-01-28 Aryeh Friedman <aryeh.fried...@gmail.com>: > > Seems like it is a processor motherboard combo thing (see other thread) > > > > ah, ok. good to know :) > > -- > Markiyan. > > > > > On Sun, Jan 26, 2014 at 9:26 AM, Markiyan Kushnir > > <markiyan.kush...@gmail.com> wrote: > >> > >> yes, once I posted it I realized that these sysctls are not relevant > >> at this stage. > >> > >> There was a segfault, was that bhyvectl? May be it makes sense for > >> someone (a bhyve dev) to inspect it? > >> > >> -- > >> Markiyan. > >> > >> > >> 2014-01-26 Aryeh Friedman <aryeh.fried...@gmail.com>: > >> > > >> > > >> > > >> > On Sun, Jan 26, 2014 at 8:46 AM, Markiyan Kushnir > >> > <markiyan.kush...@gmail.com> wrote: > >> >> > >> >> hmm... > >> >> > >> >> 15:45:test-bhyve# md5 ubuntu-12.04.3-server-amd64.iso > >> >> MD5 (ubuntu-12.04.3-server-amd64.iso) = > >> >> 2cbe868812a871242cdcdd8f2fd6feb9 > >> > > >> > > >> > # md5 ubuntu/ubuntu.iso > >> > MD5 (ubuntu/ubuntu.iso) = 2cbe868812a871242cdcdd8f2fd6feb9 > >> > > >> > doing the sysctl does no good > >> > > >> > -- > >> > Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org > > > > > > > > > > -- > > Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org > -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org _______________________________________________ firstname.lastname@example.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"