Closed. This question is not about programming or software development. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 months ago.
The community reviewed whether to reopen this question 2 months ago and left it closed:
Original close reason(s) were not resolved
Improve this question
I'm running VirtualBox 6.1.32 on Windows 10 64-bit and trying to stand up my very first VM using OS-X Monterey.
When I start the virtual machine I get this error:
Failed to open a session for the virtual machine MAC_OS_MONTEREY.
Failed to query SMC value from the host (VERR_INVALID_HANDLE).
Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
These are the commands I've gleaned for setting it up on my AMD Ryzen 7 2700 Eight-Core Processor 3.20 GHz machine:
VBoxManage.exe modifyvm "MAC_OS_MONTEREY" --cpuidset 00000001 000106e5 00100800 0098e3fd bfebfbff
VBoxManage.exe modifyvm "MAC_OS_MONTEREY" --cpu-profile "Intel Core i7-6700K"
VBoxManage.exe setextradata "MAC_OS_MONTEREY" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "iMac19,1"
VBoxManage.exe setextradata "MAC_OS_MONTEREY" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0"
VBoxManage.exe setextradata "MAC_OS_MONTEREY" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-AA95B1DDAB278B95"
VBoxManage.exe setextradata "MAC_OS_MONTEREY" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc"
VBoxManage.exe setextradata "MAC_OS_MONTEREY" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1
VBoxManage.exe setextradata "MAC_OS_MONTEREY" "VBoxInternal2/EfiGraphicsResolution 1920x1080
VBoxManage.exe setextradata "MAC_OS_MONTEREY" "VBoxInternal/TM/TSCMode" "RealTSCOffset"
Running the following command fixed the issue for me.
VBoxManage.exe setextradata "Your macOS VM Name Here!!!" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 0
Run the below as Admin in CMD.
bcdedit /set hypervisorlaunchtype off
Then Restart your PC, and try again.
I had the same issue just like you, I fixed it for myself by downgrading VirtualBox to 6.1.30 instead of the newer builds. And for some reason, it worked. Hope it helps!
You can get the older versions here: https://www.virtualbox.org/wiki/Download_Old_Builds_6_1
Before rushing and changing your OS or virtualbox settings, simply try a reboot. This exact issue is what I had (Windows 11, was running Virtual Box 6.1.32, guest OS is Mac OS X 10.11.4) and the simple reboot helped.
had the same error and after turning "core isolation" in windows 10 off - the VM started flawlessly.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 5 years ago.
Improve this question
Yesterday I tried to upgrade from ubuntu 16.04 to 17.10.
When I upgraded to 17.04 it went all good, no problem.
But when I installed 17.10 I deleted the obsolete packages when it asked me to, and it changed my standard gnome loader to some new one.
And now when I am at the window to select the user, I can't move my mouse or input anything from my keyboard, just my poweroff works.
I tried to unplug the adapter and plug it in to see if it just freezes, but it does not, it recognizes when I plug/unplug the charger, everything seems fine, but the keyboard and mouse.
I tried to run a different kernel, or run in recovery mode but when I boot it freezes in the process.
I'll assume that you're using a laptop because you mentioned charger.
There might be an option in the BIOS for Legacy USB support try enabling that.
I only suggested that because I had the same problem and when I removed all of the packages, my keyboard and mouse drivers got removed as well, so I had to switch that option so it worked. After you boot and login, you can download drivers again and than you can disable this option.
Alternatively you can try plugging in external USB keyboard and trying if it works.
P.S.: When I booted my PC to linux for the first time, none of my USB peripherals worked, so I had to use PS2 keyboard and mouse to navigate, but when I enabled that option in BIOS, I was able to use it normally.
Can you explain in more detail, how it "freezes" when you boot into recovery(I expect you calling CLI recovery)
EDIT:
you can try following these steps:
use alt+f2 and login into a separate terminal session
remove gnome with
sudo apt-get autoremove gnome-core gnome-shell gnome-session
update broken packages
sudo apt-get -f install
run it twice!
reinstall it
sudo apt-get install gnome-core gnome-shell gnome-session
reboot
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 6 years ago.
Improve this question
I'm trying to configure my Ipega PG-9025 with Retropie with no succeed. I made some progress following this link (https://askubuntu.com/questions/608386/using-ipega-bluetooth-gamepad-with-steam-linux) but it only works at Emulation Station menu...
The gamepad stops working in every emulation system and also gives me some problems pairing and reconnecting my device.
Has someone any other advice? Any other try?
Thank you very much
Finally I found a solution: I installed the last Retropie 3.0 BETA version. It has the bluetooth manager integrated and you will need only some few steps to configure your Ipega PG-9025:
1) First time you'll need to pair your Ipega with Raspberry (once is done, no need to do this anymore).
Check if your dongle is correctly connected:
$ hcitool dev
Get your adapter number (e.g. hci0)
$ hciconfig
Scan your bluetooth Ipega device:
$ hcitool scan
Pair your device using the MAC number scanned previously:
$ sudo bluez-simple-agent hci# xx:xx:xx:xx:xx:xx
After pairing connect your controller:
$ sudo bluez-test-input connect xx:xx:xx:xx:xx:xx
You will need to trust this device to allow auto-connection after a reboot:
$ sudo bluez-test-device trusted xx:xx:xx:xx:xx:xx yes
2) Check if your controller is in the input devices and responds correctly:
Verify there is an input file in e.g. /dev/input/js0
$ ls /dev/input
You can also try your device using the following command:
$ jstest /dev/input/js0
3) Now you can configure it running the retropie_setup.sh script:
cd RetroPie-Setup/
sudo ./retropie_setup.sh
In the menu, select these options and follow the instructions:
SETUP (only if you already have run one of the installations above)
317 Register RetroArch controller
And that's all, if you need to use Neo Geo system you will need an extra configuration explained here: https://github.com/petrockblog/RetroPie-Setup/wiki/Neo-Geo#controls
It's just test your device (jstest /dev/input/js0) and set the button numbers in the correct config file.
Here my Ipega PG-9025 and Nintendo64 demo running in Retropie 3.0 BETA: https://www.youtube.com/watch?v=DmvQi0w0Tec
Great tutorial helped a lot.
I had to start bluetoothd deamon for all this to work
sudo bluetoothd
Some ppl had problems if thay had sixad service runing and paired with ps3 controler
sudo service sixad stop
Closed. This question is not about programming or software development. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 months ago.
Improve this question
I have Virtualbox (v4.3.18) installed on my Mac X (10.10) and created a VM with Ubuntu on it (ubuntu-14.04.1-desktop-amd64.iso). After the installation was completed, it asked to reboot, and when I checked the storage settings, the iso had been automatically removed. I went ahead and install software on the VM, but walked away and came back to find it had aborted. When I try to run the VM again, I see the following messages and I am unable to get back to Ubuntu: :
The only thing I have been able to do is add the iso back in the storage settings and re-install Ubuntu to be able to use it, but always temporarily since it keeps aborting. I don't want to "try it without installing" it, I want to be able to turn it off and on whenever I want and not have to reinstall every time. Does anyone know why the VM is aborting?
Is the "Enable EFI" parameter checked? it is on the system/motheboard page of the VM.
I met a similar problem once and checking the box solved the problem.
It might not be because of the virtual box problem. it might because of the memory issue. If you have less swap and it gets full then there is high chance of vbox machine gets aborted.
To check that first check weather your swap memory is full or not using htop command. If htop is not installed (sudo apt install htop in ubuntu, check for other flavors)
Put htop command and see if the swap is getting full. If yes you can increase the swap memory by following command
sudo swapoff -a
sudo dd if=/dev/zero of=/swapfile bs=1G count=8
sudo chmod 0600 /swapfile
sudo mkswap /swapfile
sudo swapon /swapfile
And then you do htop and see the swap size. it should be 8gb and not full. now your vbox won't be aborting repeatedly.
It solved my vbox problem after lot of research
This started happening to me with VBox 5.1.24 and Ubuntu 17.04 both of which have the latest patches as of July 22 2017. Ubuntu Desktop would attempt to start for 5-10 minutes. The purple splash screen transitioned back to a black text screen with a blinking cursor. The VM would become Aborted after 5-10 minutes. Doubling the amount of RAM for the VM (to 8 GB) resolved the issue.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
I am having trouble with CUDA installation on Linux.
I have tried the installation of CUDA 6 on:
Ubuntu 14.04 (x64)
Linux Mint 17 (x64)
The problem:
I have tried to simply download/execute the nvidia CUDA executable (it is a *.run file downloaded from nvidia website)
I have tried to install CUDA from the .deb file given by nvidia
I have tried to install CUDA from edgers repository
I have followed tens of tutorials, I have reinstalled at least 20 times Linux, just to be sure that I am working on a clean version.
In any case: I paid attention to define the variable environment at the end of the process: PATH and LD_LIBRARY_PATH so that they point to the recently installed CUDA directory. (/path/to/cuda/bin for PATH and /path/to/cuda/lib64 for LD_LIBRARY_PATH.
At the end of the process I am trying to compile and launch the sample code given by nVidia in the sample code thing that you can install/download.
The example I am running is "deviceQuery". (located in /path/to/cuda/samples/)
In any case, I had the nvidia (proprietary driver installation), not Nouveau.
And in any case, I have an error when I launch this deviceQuery. The error is either something like: no CUDA-able device detected.
Or something like nvidia-uvm is missing (I have tried to install nvidia-uvm, when I tried the installation from the edgers PPA repository, and the error I have when I launch the deviceQuery sample is then no no CUDA-able device detected.
The question
What is, the right, stable, clear way to install CUDA on ANY version of Linux.
I am ready to download, install ANY version of Linux.
Thanks a lot and very much for your help
Niether Ubuntu 14.04 nor Linux Mint 17 is an officially supported distro for CUDA 6.
I've just done two installs of CUDA 6.5RC on Fedora 20 64-bit.
load Fedora 20, select the C Development personality
download the CUDA 6.5RC 64-bit installer (.run file) from developer.nvidia.com (you have to be a registered developer)
switch to runlevel 3. To do this, take a look at the instructions in /etc/inittab, you basically want to do this, as root:
ln -sf /lib/systemd/system/multi-user.target /etc/systemd/system/default.target
remove the nouveau driver (as root):
echo -e "blacklist nouveau\noptions nouveau modeset=0" > /etc/modprobe.d/disable-nouveau.conf
dracut --force
reboot, and run the CUDA installer (.run file) as root. If you have 4GB or less of system memory, you may want to specify the temp directory that doesn't use tmpfs:
sh cuda_6.5.11_rc_linux_64.run -tmpdir /var/tmp
select accept, y, or <enter> as appropriate to accept the default options for loading the driver, toolkit, and samples.
you can now switch back to runlevel 5 if you want to.
run nvidia-smi as root, each time you reboot the system. This should not be necessary if you are running X (ie. runlevel 5). And there are other ways to address this as discussed in the getting started document.
Also refer to the linux getting started guide.
Instructions for other RHEL/CentOS/Fedora distros will be similar, and should work with previous CUDA versions (e.g. 6), if you don't want to use the 6.5RC toolkit. Be sure to select a distro that is officially supported for the CUDA toolkit you choose (in recent toolkits, refer to the getting started document.)
You'll also want to do those things you already know about, such as building the samples, setting your PATH and LD_LIBRARY_PATH environment variables, etc. This brief answer is not intended to be a replacement for reading the getting started document.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
As far as I know, Linux container is different from virtual machine. It's lightweight virtualization technology. So I'm wondering if it can be run on a virtual machine which provisioned by hypervisor like xen, kvm or vmware?
I was trying setup a Linux container(docker + LXC userspace tool) on a virtual machine based on zex. It failed.
[root#docker lib]# service docker start
Starting cgconfig service: Error: cannot mount cpuset to /cgroup/cpuset: Device or resource busy
/sbin/cgconfigparser; error loading /etc/cgconfig.conf: Cgroup mounting failed
Failed to parse /etc/cgconfig.conf [FAILED]
Starting docker: [ OK ]
and if trying to run a container:
root#docker lib]# docker run -i -t ubuntu /bin/echo hello world
lxc-start: error while loading shared libraries: liblxc.so.1: cannot open shared object file: No such file or directory
2014/03/27 14:03:27 Error: start: Cannot start container da0d674d3e31a7c36a9e352f64fd84986cbb872e526cb2dd6adb7473d4f5a430: exit status 127
Actually, I followed a blog to do, the author made it, while I screw it.
Any one can explain that? Or simply tell me it can not be ran on a virtual machine. Really appreciate.
Yes, it can. If your VM's operating system supports the appropriate filesystems, and have containers. I suggest you go though as suggested on https://www.docker.io/gettingstarted/ and use a recent Ubuntu release, since that is known to work.