I can't get vmx cpu extensions to show up in Virtualbox guests despite enabling nested paging and enable vmx in virtualbox guest but this doesn't help that you check VT-X or the AMD Virtualization SVM it enables it for the guest to use BUT does not pass it through. This means if you check cat /proc/cpuinfo in the guest you will see the CPUdoesn't support virtualization. It looks like VirtualBox still hasn't implemented this! But there is good news I&n........

This is not the normal "black screen"issue and I was shocked to eventually find out why. The normal advice of reconfiguring Xorg didn't work. Even booting into "Recovery Mode" did not help. Here is the short end of the stick that fixed it: sudo apt-get install mdm mate-desktop-environment Yes you got it right, mdm and the mate-desktop-environment / gnome were somehow uninstalled. This must be whe........

It really is as simple as: cdrecord -v dev=/dev/sr0 pathtoyourisoimage.iso -v is for verbose, I prefer it but if you don't you won't see as much output like below (I like to know the details and exactly what's happening) dev=/dev/sr0 specifies the device name of your burner (they say not to use it and to specify some weird annoying device string but using the raw /dev has always worked for me and is how it should have been implemented from the start IMHO)........

Normally if you're in a certain directory you could do: find *.txt and it will work as expected, but it won't work recursively through child directories, here's the correct way to do it: find . -type f -name *.txt The "-type f" is optional because that means only files, but we could have specified d for directory etc... The above command will work recursively as you'd expect. In that way I find "find" to be un........

In file included from drivers/block/cciss.c:1015: include/asm-generic/pci-dma-compat.h: In function `cmd_special_free': drivers/block/cciss.c:196: sorry, unimplemented: inlining failed in call to 'cciss_tag_discard_error_bits': function body not available include/asm-generic/pci-dma-compat.h:25: sorry, unimplemented: called from here make[2]: *** [drivers/block/cciss.o] Error 1 make[1]: *** [drivers/block] Error 2 make: *** [drivers] Error 2........

Virtualbox Error I tried to copy a .vdi of one container to use in another one, basically to clone instead of having to install the OS again. Failed to start the virtual machine Centos 5.5 Mirror. Medium '/home/testuser/.VirtualBox/HardDisks/Centos 5.5 Mirror.vdi' is not accessible. UUID {a1a9fad7-0402-4867-b8f3-39fb49454bc5} of the medium '/home/testuser/.VirtualBox/HardDisks/Centos 5.5 Mirror.vdi' does not match the value {4945a0e8-0ed5-4736-9088-bcaf........

This is a great way to use your ftp server space, for example on your web hosting account (althoughI believe many hosts don't allow storage like this), but if you have a VPS/Dedicated Server etc.., this would be perfect. Imagine how easy it is to work with an ftp account that you can just mount as a normal partition or directory in Linux, it would be great for backups etc.. Name curlftpfs - mount a ftp host as a local directory Synopsis........

CC drivers/message/fusion/mptsas.o drivers/message/fusion/mptsas.c: In function `mptsas_port_delete': drivers/message/fusion/mptsas.c:106: sorry, unimplemented: inlining failed in call to 'mptsas_set_rphy': function body not available drivers/message/fusion/mptsas.c:462: sorry, unimplemented: called from here make[3]: *** [drivers/message/fusion/mptsas.o] Error 1 make[2]: *** [drivers/message/fusion] Error 2 mak........

Linux Kernel v2.6.30.3 102220 blocks CHK include/linux/version.h CHK include/linux/utsrelease.h SYMLINK include/asm -> include/asm-x86 CALL scripts/checksyscalls.sh CHK include/linux/compile.h CC drivers/net/igb/igb_main.o drivers/net/igb/igb_main.c: In function `igb_up':........

User username from 127.0.0.1 not allowed because not listed in AllowUsers What's going on? The user was created properly, it has been defined as having a shell entry and the entry for /etc/passwd and /etc/shadow is set just fine. This is a new and very smart/secure feature of SSHD. It is simple and yet effective, but also very annoying if you didn't know about it being implemented and that hand editing of /etc/ssh/sshd_config is required to allow a newly add........