I am using Ubuntu 14.04.4 LTS for memsql. I have tried to disable transparent_hugepage by adding line to grub
I have change the
GRUB_CMDLINE_LINUX_DEFAULT="console=tty1 console=ttyS0"
to
GRUB_CMDLINE_LINUX_DEFAULT="console=tty1 console=ttyS0" "transparent_hugepage=never"
Then I execute sudo update-grub in the shell. and below error has thrown
/usr/sbin/grub-mkconfig: 11: /etc/default/grub: transparent_hugepage=never: not found
Kindly help me on this.
You probably want:
GRUB_CMDLINE_LINUX_DEFAULT="console=tty1 console=ttyS0 transparent_hugepage=never"
Related
I have Ubuntu 18 on mu VMware software and try to install QT based on this youtube video. The issue is when I want to run the following command:
sudo ./qt-opensource-linux-x64-5.11.3.run
I get this error:
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
QXcbConnection: Could not connect to display
Aborted
Any help?
Thank you very much.
It looks like this might simply be a case of the DISPLAY environment variable not being set.
Try ssh with X11 forwarding rather than sudo. So something like...
ssh -X root#localhost <full-path-to>/qt-opensource-linux-x64-5.11.3.run
I am new to Linux and I am trying to install MiniConda3 on an old 32bit machine running Linux Mint19. But I keep getting the following error:
Miniconda3-latest-Linux-x86.sh: line 358: 2191 Illegal instruction
(core dumped) "$PREFIX/pkgs/python-3.7.0-hc3d631a_0/bin/python" -E -s
"$PREFIX"/pkgs/.install.py $INST_OPT --root-prefix="$PREFIX" --link-dist="$1"
Is this a permissions thing or a compatibility issue?
Thanks for any help provided
I want to use QEMU to debug my compiled kernel linux-4.13.4 on Ubuntu 16.04.3 LTS
I follow the following steps:
1 install qemu
sudo apt-get install qemu
2 run qemu
qemu-system-x86_64 -s -S -kernel /home/wxf/kernelSources/linux-4.13.4/arch/x86_64/boot/bzImage -initrd /boot/initrd.img-4.13.4
Note:
-s shorthand for -gdb tcp::1234
-S freeze CPU at startup (use 'c' to start execution)
But I get the following warning:
warning: TCG doesn't support requested feature: CPUID.01H:ECX.vmx [bit 5]
The terminal stops there and I cannot input other commands.
The QEMU window pops up when I run it but it is stopped.
So, my question is
How to eliminate the warning and is it normal(since it is not an error information)?
Frankly speaking, I don't know how to handle that warning, can it be ignored or have you to do something with it. But I suppose the main problem is that you cannot run the VM. If so, you need to properly determine where to enter that c to start the VM. :)
QEMU has several graphical interfaces (and AFAIK can even be run in plain console). Suppose we have identical defaults for which UI to use (probably, the GTK one). When I run similar command (qemu-system-x86_64 -s -S -kernel ...), I can switch to the monitor console of QEMU by pressing Ctrl+Alt+2 (just 2, not F2). There I press c (and Enter, it seems to behave like regular terminal) and then switch to the VM display by Ctrl+Alt+1.
I had this problem, or something very similar. It gave the same warning and, while it would then boot, it was unusably slow.
I fixed it it by adding -machine ubuntu,accel=kvm to the qemu-system-x86_64 command line.
You missed out giving the RAM size to be used by the VM. The default RAM allocated by qemu is 128M, which in your case was not sufficient, I guess. Try passing
-m 512
Source
I am trying to install xen on Centos 7 following this guide.
When I run the command "xl info" the following error appears:
xc: error: Could not obtain handle on privileged command interface (2 = No such file or directory): Internal error
libxl: error: libxl.c:116:libxl_ctx_alloc: cannot open libxc handle: No such file or directory
cannot init xl context
In the followed guide it says that I should have the following line in module 2 and in mine is not present even thought it clearly says it's a bug on Centos 6.I don't know if this is related or not.
title CentOS (3.4.46-8.el6.centos.alt.x86_64)
root (hd0,0)
kernel /xen.gz dom0_mem=1024M,max:1024M loglvl=all guest_loglvl=all
module /vmlinuz-3.4.46-8.el6.centos.alt.x86_64 ro root=/dev/mapper/vg_xen01-lv_root rd_LVM_LV=vg_xen01/lv_swap rd_NO_LUKS KEYBOARDTYPE=pc KEYTABLE=uk rd_NO_MD LANG=en_GB rd_LVM_LV=vg_xen01/lv_root SYSFONT=latarcyrheb-sun16 crashkernel=auto rd_NO_DM rhgb quiet
module /initramfs-3.4.46-8.el6.centos.alt.x86_64.img
Thank you for your help.
Is the server booted into the Xen kernel? If you run uname -a you should see something like 3.4.46-8.el6.centos.alt.x86_64. (The 'alt' indicates the Xen kernel.)
Apparently it requires mutiboot2 which RH aren't including because of security issues.
Google your message. You'll find it.
I have Ubuntu 11.04
I am trying to install Xvfb and CutyCapt in order to take a snapshot of webpage
I followed a instruction https://github.com/jaequery/cutycapt-installer-script-on-ubuntu/blob/master/install
and I executed last line and it gives me an error
xvfb-run: error:Xvfb failed to start
Any solution for that?
Thank you in advance
I was getting this error "xvfb-run: error: Xvfb failed to start" on Ubuntu 14.04, where previously my script had run without problems on Ubuntu 12.04.
My scripts were running calling xvfb-run multiple times, but I was seeing fails due to the error "Server is already active for display 99"
It seemed that the Xvfb wasn't ending when the xvfb-run command returned.
My solution was to use "xvfb-run -a [mycommand]" so xvfb uses another display if 99 is in use.
Had the same issue, solved it by running this instead:
xvfb-run --auto-servernum --server-num=1 [your script]
--auto-servernum : Try to get a free server number, starting at 99, or the argument to --server-num
Run xvfb-run -e /dev/stdout [mycommand] as #wumpus suggested.
I received the server lock message:
Fatal server error:
Could not create server lock file: /tmp/.X99-lock
xvfb-run:
error: Xvfb failed to start
Using sudo resolved the issue for me:
sudo xvfb-run -e /dev/stdout [mycommand]
Found the problem There is hanging process in system with name
Xvfb
I killed it and work fine. I newer found it earlier beacuse I used to try to find process with 'xvfb' name
I came across this error when running a bash script on Mac OS. Opening XQuartz before running the script solved my problem.