verified. Our system is connected through eth0 to a network that has a functional maas running. As such, we can boot guests that dhcp onto the network and should network boot.
Configuring maas is beyond the scope of this verification report. # enable proposed $ mirror=http://ports.ubuntu.com/ubuntu-ports $ echo "deb $mirror trusty-proposed main universe" | sudo tee -a /etc/apt/sources.list $ sudo apt-get -q update ## to get a functional qemu-system-ppc64, we use kilo cloud archive $ sudo apt-add-repository -y cloud-archive:kilo-proposed $ sudo apt-get update $ sudo apt-get install -qy qemu-system-ppc qemu-slof $ dpkg-query --show qemu-slof qemu-slof 20140630+dfsg-1ubuntu1~14.04 # configure eth0 to be a bridge $ sudo apt-get install -qy bridge-utils $ ifdown eth0 $ eni="/etc/network/interfaces" $ cp "$eni" "$eni.dist" $ cat > "$eni" <<EOF auto lo auto br0 iface br0 inet dhcp bridge_ports eth0 EOF ifup br0 ## setup kvm, we're running linux-generic-lts-utopic kernel $ uname -r 3.16.0-30-generic $ sudo sh -cx 'grep "kvm_" /proc/modules || modprobe kvm_hv || modprobe kvm_pr' $ sudo chmod 666 /dev/kvm $ sudo ppc64_cpu --smt=off ## try booting a qemu-system-ppc via netboot $ myname=$(id -un) $ sudo ip tuntap add mode tap user $myname mytap0 $ sudo ip link set mytap0 up $ qemu-system-ppc64 -machine pseries,usb=off \ -device spapr-vscsi \ -device spapr-vlan,netdev=net00 \ -netdev type=tap,id=net00,script=no,downscript=no,ifname=mytap0 \ -boot n -display none -nographic -m 4G -echr 0x05 ## eventually this will show 'booting under maas direction' ## and the system is even enlisted into maas $ apt-cache policy qemu-system-ppc qemu-slof linux-generic-lts-utopic qemu-system-ppc: Installed: 1:2.1+dfsg-11ubuntu2~cloud0 Candidate: 1:2.1+dfsg-11ubuntu2~cloud0 Version table: *** 1:2.1+dfsg-11ubuntu2~cloud0 0 500 http://ubuntu-cloud.archive.canonical.com/ubuntu/ trusty-proposed/kilo/main ppc64el Packages 100 /var/lib/dpkg/status 2.0.0+dfsg-2ubuntu1.10 0 500 http://ports.ubuntu.com/ubuntu-ports/ trusty-updates/main ppc64el Packages 2.0.0+dfsg-2ubuntu1.9 0 500 http://ports.ubuntu.com/ubuntu-ports/ trusty-security/main ppc64el Packages 2.0.0~rc1+dfsg-0ubuntu3 0 500 http://ports.ubuntu.com/ubuntu-ports/ trusty/main ppc64el Packages qemu-slof: Installed: 20140630+dfsg-1ubuntu1~14.04 Candidate: 20140630+dfsg-1ubuntu1~14.04 Version table: *** 20140630+dfsg-1ubuntu1~14.04 0 500 http://ports.ubuntu.com/ubuntu-ports/ trusty-proposed/universe ppc64el Packages 100 /var/lib/dpkg/status 20131015+dfsg-1ubuntu1 0 500 http://ports.ubuntu.com/ubuntu-ports/ trusty/universe ppc64el Packages linux-generic-lts-utopic: Installed: 3.16.0.30.23 Candidate: 3.16.0.30.23 Version table: *** 3.16.0.30.23 0 500 http://ports.ubuntu.com/ubuntu-ports/ trusty-updates/main ppc64el Packages 500 http://ports.ubuntu.com/ubuntu-ports/ trusty-proposed/main ppc64el Packages 100 /var/lib/dpkg/status 3.16.0.29.22 0 500 http://ports.ubuntu.com/ubuntu-ports/ trusty-security/main ppc64el Packages ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1374568 Title: network boot doesn't work (need newer slof.bin) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/slof/+bug/1374568/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
