Hi The trick was to go back to the beginning and start with a clean build appliance. Though I had selected the options below, I had tried other options first, and those seemed to be sticking, even after I changed the recipe.
Now on to how to get DHCP to work … Apologies Nathan > On 28 Jan 2016, at 15:31, Nathan Sowatskey <[email protected]> wrote: > > Hi > > I am using the Yocto Build Appliance to build a image using a profile of > qemux86-64, and recipe of core-image-full-cmdline. > > I then sftp the image to my OSX environment and run it as shown below. That > works fine, and I can log in as root. > > I want to use ssh to connect to the image, but ssh does not seem to either > running or even installed, as I don’t see /etc/init.d/ssh scripts. > > I am clearly missing a trick here. > > Any ideas please? > > Many thanks > > Nathan > > How I run the image is shown below. This is copied from the build appliance, > and I confess that I don’t understand all of the options yet. > > /usr/local/bin/qemu-system-x86_64 -kernel images/bzImage-qemux86-64.bin -net > nic,model=virtio -drive > file=images/core-image-base-qemux86-64.ext4,if=virtio,format=raw -show-cursor > -usb -vga vmware -no-reboot -m 256 -serial mon:vc -serial null --append > "vga=0 uvesafb.mode_option=640x480-32 root=/dev/vda rw mem=256M > ip=10.41.136.130::10.41.136.1:255.255.255.0 oprofile.timer=1 rootfstype=ext4 " > > > — > Nathan John Sowatskey > Consulting Engineer - Programmable Infrastructure, DevOps, IoT and SDN > [email protected] > www.linkedin.com/in/nathandevops > XMPP: [email protected] > Google: [email protected] > Skype: nathan_sowatskey > Twitter: NathanDotTo > GitHub: https://github.com/DevOps4Networks > http://www.kipling.org.uk/poems_if.htm > > -- > _______________________________________________ > yocto mailing list > [email protected] > https://lists.yoctoproject.org/listinfo/yocto -- _______________________________________________ yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/yocto
