Have you checked if your cpu supports virtualization?https://wiki.archlinux.org/index.php/KVM
on 02/10/2013 – Made popular on 02/10/2013
Hello,did you try the this from:http://ubuntuforums.org/showthread.php?t=1860008 orhttp://forum.kde.org/viewtopic.php?f=66&t=89710Go to System Settings → Startup and Shutdown → Session Management and check the “Offer shutdown options” checkbox.
Things should be working as outlined in the wiki: https://wiki.archlinux.org/index.php/Sy … managementIf you think it's important, you can add a line about halt, although it's already mentioned in systemd FAQ https://wiki.archlinux.org/index.php/Sy … r_stays_onThere's also https://wiki.archlinux.org/index.php/Al … o_ShutdownObviously you can use an alias e.g.alias halt='sudo sy
The ArchLinux Wiki has the best documentation available and with the problems you describe here, if it does not suffice, ArchLinux is likely not for you.Everyone can install ArchLinux and most can use it, but it does require more from the user than Ubuntu and such.https://wiki.archlinux.org/index.php/The_Arch_Wayhttps://wiki.archlinux.org/index.php/Beginners%27_Guide
Network and Xorg issues sounds to me like you did too much in one go.https://wiki.archlinux.org/index.php/Be … leshootingCheck the connection, check the driver status and load the module: https://wiki.archlinux.org/index.php/Ne … figurationIf the network interface doesn't show up (eth0), read this part: https://wiki.archlinux.org/index.php/Ne … Interfaces
First thing that comes to mind on an unexpected shutdown is to fsck it. https://wiki.archlinux.org/index.php/FsckIt runs fsck at boot but the interval is set to run fsck every 30 boots according to the wiki. Give that a shot first while waiting for others more knowledgeable to reply. Good luck!