Linux disable by bios

Arch Linux

i just finished the basic installation of Arch Linux on My Acer Aspire V5 Netbook. After the basic installation , I installed the X Display Server , ATI Video Card Driver , XFCE Desktop Environment and LightDM Display Manager. Now I reboot my netbook , I get this error telling «kvm disabled by the bios» and everything halts. On Googling ,some suggested to turn «Virtualization» on from the BIOS set up. But I don’t see any such option in the F2 setup screen. So please help!

#2 2013-12-13 13:07:56

Re: KVM Disabled by BIOS

you have it at 1:48 (but I really don’t think that halts your system.

“The future has already arrived. It’s just not evenly distributed yet.”
― William Gibson

#3 2013-12-13 14:34:22

Re: KVM Disabled by BIOS

Hi! Thanks for the reply! But I don’t have such advanced options in my BIOS screen. All I have is Information,Main,Security,Boot,Exit. I did not have any problem initially ,I was able to install Arch Linux successfully and reboot the laptop..I was able to login as root and everything worked fine. Why am I not able to do that now ?

The system didn’t halt actually. I used Alt-F2 and was able to login as root in another screen. But if I press Alt-F2 again , I go back to the screen where I get the problem «kvm disabled by the BIOS»

Last edited by thegyro (2013-12-13 14:37:18)

#4 2013-12-13 15:22:10

Mr.Elendig #archlinux@freenode channel op From: The intertubes Registered: 2004-11-07 Posts: 4,084

Re: KVM Disabled by BIOS

Contact acer support and ask then how to enable it?

Evil #archlinux@libera.chat channel op and general support dude.
. files on github, Screenshots, Random pics and the rest

#5 2013-12-13 15:29:38

Re: KVM Disabled by BIOS

But why didn’t I get a similar error as soon as I finished installing Arch on it ?

#6 2013-12-13 15:46:12

Mr.Elendig #archlinux@freenode channel op From: The intertubes Registered: 2004-11-07 Posts: 4,084

Re: KVM Disabled by BIOS

Probably because the kvm module is not being loaded.

Evil #archlinux@libera.chat channel op and general support dude.
. files on github, Screenshots, Random pics and the rest

#7 2013-12-14 17:47:27

Re: KVM Disabled by BIOS

(but I really don’t think that halts your system.

I have seen the error in past but arch would run fine.

#8 2013-12-15 10:31:07

Re: KVM Disabled by BIOS

Probably because the kvm module is not being loaded.

My Arch is running fine ,though the error KVM disabled is still there at the back . Is this a problem I should worry about or can I just neglect it ? What is the purpose of this module ?

#9 2013-12-15 13:36:05

Re: KVM Disabled by BIOS

if you’re not using virtualization it probably doesn’t matter

#10 2013-12-15 14:50:07

Re: KVM Disabled by BIOS

I’ve seen this message many, many times on different machines, and it’s never caused any problems. The KVM module is in the stock Arch kernel; unless you have the vendor-specific virtualization stuff enabled in the BIOS/EFI setup menu, the KVM module won’t load. The message is just telling you you can’t use KVM on your system, which only matters if you really, really want to use KVM on your system.

EDIT—@OP: Since this is a new installation, have you ensured that you’re booting into the correct target/runtime?

Last edited by ANOKNUSA (2013-12-15 15:21:08)

#11 2013-12-15 16:31:22

Re: KVM Disabled by BIOS

I’ve seen this message many, many times on different machines, and it’s never caused any problems. The KVM module is in the stock Arch kernel; unless you have the vendor-specific virtualization stuff enabled in the BIOS/EFI setup menu, the KVM module won’t load. The message is just telling you you can’t use KVM on your system, which only matters if you really, really want to use KVM on your system.

EDIT—@OP: Since this is a new installation, have you ensured that you’re booting into the correct target/runtime?

I am sorry but what does booting into the correct target/runtime mean ? Which is the correct one and how do I check it ?

#12 2013-12-15 16:59:29

Re: KVM Disabled by BIOS

By default, the system boots into multi-user.target, dropping the user at the command line after boot. If you’re trying to boot into LightDM and log in from there, you’ll need to enable lightdm.service (if you haven’t already) and set systemd to boot into graphical.target instead. It may be the case that systemd is starting lightdm.service (if you enabled it), but booting into multi-user.target; hence the blank screen on TTY1, but login prompt on other TTYs.

#13 2013-12-15 17:01:06

Re: KVM Disabled by BIOS

If you are at all familiar with the old SysV way of doing things, then the target would be equivalent to /etc/inittab’s runlevels. Use the search engine of your choice to learn more about systemd targets (and systemd units in general). Of course, systemd has great documentation as well, so you could reference the man pages too.

Basically what everyone is trying to tell you here is that the error, which you seem to have concluded is the root of your issue here, most likely has nothing to do with your inability to boot. You need to access the system’s journal and see if you can determine what exactly is preventing the machine from coming up properly.

Источник

Что означает kvm: disabled by bios

Что это значит? Может ли быть это причиной того, что иногда у меня линукс «зависает» и перезагружается?

вряд ли это причина зависаний, но можно либо включить это в биосе, либо объяснить линуксу не грузить модуль askubuntu.com/questions/263179/get-rid-of-kvm-disabled-by-bios

Это означает, что при загрузке модуля kvm он жалуется, что апппаратная виртуализация поддерживается процессором, но выключена в BIOS.

Нет, это не может быть причиной зависаний. Это может лишь вызвать ошибки в эмуляторах типа virtualbox.

Причиной зависаний быть не должно, подобное скорее бывает от нехватки памяти (сожрал браузер), кривого ядра (чему в kali я бы не удивился) или кривого железа/фирмвари (и это, особенно последнее, тоже не редкость).

1 ответ 1

Это сообщение значит — модул для поддержки виртуализации на уровне ядра KVMобнаружил, что виртуализация выключена в BIOS. В меню установок в BIOS пункт «Virtualization Technology >Disabled

Похожие

Подписаться на ленту

Для подписки на ленту скопируйте и вставьте эту ссылку в вашу программу для чтения RSS.

Дизайн сайта / логотип © 2023 Stack Exchange Inc; пользовательские материалы лицензированы в соответствии с CC BY-SA . rev 2023.7.13.43531

Нажимая «Принять все файлы cookie» вы соглашаетесь, что Stack Exchange может хранить файлы cookie на вашем устройстве и раскрывать информацию в соответствии с нашей Политикой в отношении файлов cookie.

Источник

How can I get rid of the message «kvm: disabled by BIOS»?

after upgrading my kernel to 3.8.x. I’ve never installed the KVM package. Neither I can enable virtualization from my BIOS, because of a BIOS bug. I just want to get rid of this weird message. Tried removing any kernel module using modprobe but it didn’t work.

I don’t agree that this is a duplicate. This question specifically asks how to suppress the message given that the BIOS arbitrarily disables virtualisation, and is focused on keeping virtualisation disabled. The other question is (implicitly) asking how to enable virtualisation, with the error message being a symptom of the problem, rather than the problem itself. So although I agree that the questions are related, I don’t think they’re the same. In fact, they might even be considered opposites.

It’s not a dupe but it is a question seeking a workaround for a bug and so should be closed as off-topic instead.

It’s a BIOS bug, not an Ubuntu bug, for which a workaround is being sought. I don’t think this fits with the spirit of the off-topicness of bugs, since a BIOS bug doesn’t generally belong on Launchpad either, really.

@RobieBasak we do not care who’s fault is the bug, it’s a bug and needs to be fixed by the one that develops them. Is simple. If the bug-tracker isn’t LP then look for it, bugs are bugs and hence off-topic independently what part of the software/hardware/firmware has it.

Источник

VMX (outside TXT) : disabled by bios

This message means actually what it says: VMX is disabled in BIOS.

VMX stands for Virtual Machine Extensions and it is a virtualization technology. More info here.

There is one quick way (workaround) to remove the message: Go to your BIOS settings and enable the virtualization technology. This article has some screenshots of how to do it in an Asus BIOS for both Intel and AMD processors.

More about the issue

The reason you probably didn’t see this message up until now is that the logging of it got into a quite recent Linux kernel and it is an ‘error’ in journal. Apparently this annoys other people as well, there is a bug report on it already:

I found the solution for you here

If you feel that enabling a processor feature that you don’t use just to make an error message go away is wrong then read on.

The reason why this issue is happening

Based on the discussion on the above mentioned SUSE thread and my other findings, it seems that this virtualization technology is used by the so called KVM (Kernel-based Virtual Machine) which is built into the Linux kernel.

Upon boot, this generates an error in the logs that it cannot be initialized because the hardware capabilities are disabled in BIOS.

Proper (not yet known) solution

Now if KVM itself is disabled in some way than I think that would also make this error message go away because the kernel would not even bother trying to load it. (Second commit above and mailing list discussion about it

I really did my homework and searched how to disable this kernel feature yet I could not find any relevant information how to do it and I am really not sure that it is a good idea to disable «ad hoc» kernel features just because they are unable to load themselves because of disabled hardware features.

Источник