Hardware hangup note for Ctrl+C to get past.
http://www.reddit.com/r/debian/comments/25h49k/debain_wheezy_network_installation_freezes_after/
Configured LVM environment with /home, /usr/, and /var on spinning platter drive.
Configured an IP reservation on my DHCP server, though I may change this to a true static address at some point.
Instructions for linux-headers and virtualbox setup: https://wiki.debian.org/VirtualBox
Downloaded the extension pack with wget http://download.virtualbox.org/virtualbox/4.1.36/Oracle_VM_VirtualBox_Extension_Pack-4.1.36-97684.vbox-extpack (NOTE: you will need to download the appropriate version for your installed VirtualBox version. Run vboxmanage -v and compare the output version to the versions available at https://www.virtualbox.org/wiki/Downloads; it apears you will need to match at least Major.Minor version numbers) and installed using instructions at https://www.virtualbox.org/manual/ch08.html#vboxmanage-extpack.
Created a separate logical volume on my SSD drive. Dedicated it to the Win10 guest (see https://wiki.archlinux.org/index.php/VirtualBox#Create_a_VM_configuration_to_boot_from_the_physical_drive).
Created a VM from the CLI. Had to actually go into the BIOS and enable AMD-V on my Gigabyte 78LMT-USB3 as it was disabled. Could not get the version of VirtualBox included with the Debian distribution to give anything except the “Your PC needs to restart” 0x0000005D error, even when trying to force the NX bit using info for setting CMPXCHG16B as found at http://www.makeuseof.com/tag/try-windows-10-youre-running-linux/. Ultimately ended up loosely following instructions from http://www.admin-magazine.com/Articles/Server-Virtualization-with-VirtualBox but substituting “wheezy contrib” for “lucid contrib” early in the instructions, and substituting 4.3 for 4.1, then running a “modifyvm” and setting ostype to Windows81_64. Once this was done, I was able to start the install process. Yay.
Had to modify the e1000g0 adapter config from http://www.perkin.org.uk/posts/create-virtualbox-vm-from-the-command-line.html to instead be “eth0” since I’m on a linux box (also had to remove it before re-adding, got an error when even attempting to start the machine).
Mouse pointer was batty, like it was scaled. Ended up downloading the appropriate VirtualBox guest additions to the host machine, mounting them in the DVD drive, selecting the AMD64 file, bringing up properties and setting to compatibility mode Windows 8 (can’t seem to locate where I found this), and was able to install. Pointer synced, system is on the web.
Second Steps – Debian LXC Guest for KDE
Debian 7.8
#From https://wiki.debian.org/LXC - loosely
apt-get install lxc
apt-get install bridge-utils libvirt-bin debootstrap
# Failed with:
# Failed to fetch http://security.debian.org/pool/updates/main/libx/libxml2/libxml2-utils_2.8.0+dfsg1-7+wheezy3_amd64.deb 404 Not Found [IP: 128.31.0.63 80]
# E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
apt-get
apt-get install bridge-utils libvirt-bin debootstrap
# Successful this time
echo -e "cgroup\t/sys/fs/cgroup\tcgroup\tdefaults\t0\t0" >>/etc/fstab
mount /sys/fs/cgroup
mount
# Confirmed that cgroup is mounted
lxc-checkconfig
# All show enabled
# Check out http://www.turnkeylinux.org/blog/announcing-turnkey-lxc, maybe add
# Turnkey template for some other functionality on this box
# Switched tracks and decided to try out Docker
# From http://docs.docker.com/installation/debian/#debian-wheezystable-7x-64-bit
echo "deb http://http.debian.net/debian wheezy-backports main" >> /etc/apt/sources.list
apt-get update
apt-get install -t wheezy-backports linux-image-amd64
reboot
# SSH'ed back into machine, verify new kernel
uname -a
wget https://get.docker.com/
chmod +x index.html
gpasswd -a my-account docker
service docker restart
# Service apparently did not restart, so had to start it again manually
service docker start
# Now as non-root
# Determined the following from http://www.syncano.com/getting-started-docker/
docker pull ubuntu:14.10
docker images
# Lists the newly pulled image; attempted to run it.
docker run -t ubuntu:14.10
# At this point, continuously encountered an error similar to the following:
# FATA[0034] Error response from daemon: Cannot start container (container UUID here): [8] System error: write /sys/fs/cgroup/docker/(container UUID here)/cgroup.procs: no space left on device
# There is definitely space left on the device, I do not appear to be lacking inodes as others seem to have encountered similarly, and permissions look OK.
# Started to install strace to troubleshoot further... but I need to get an accounting system back online.
# Switched to a VirtualBox KDE environment plan. I guess I can always kill it later :)
lvm lvcreate -L 10g -n kmm
wget http://peppermintos.com/iso/Peppermint-5-20140623-amd64.iso
vboxmanage createvm --name kmm --register
vboxmanage modifyvm kmm --memory 1024 --acpi on --boot1 dvd --nic1 bridged --bridgeadapter1 eth0
VBoxManage internalcommands createrawvmdk -filename ~/VirtualBox\ VMs/kmm/kmmSSD.vmdk -rawdisk /dev/amdfx/kmm
vboxmanage storagectl kmm --name "SATA Controller" --add sata
vboxmanage storageattach kmm --storagectl "SATA Controller" --port 0 --device 0 --type hdd --medium ~/VirtualBox\ VMs/kmm/kmmSSD.vmdk
vboxmanage storageattach kmm --storagectl "SATA Controller" --port 1 --device 0 --type dvddrive --medium ./Peppermint-5-20140623-amd64.iso
vboxmanage modifyvm kmm --ostype Ubuntu_64 --vrde on --vrdeport 22888
vboxmanage startvm kmm --type headless
# Able to RDP in and started Peppermint install process.
