VirtualBox

Ticket #4179 (closed defect: fixed)

Opened 5 years ago

Last modified 2 weeks ago

Windows Guests cause non-recoverable (reboot only) machine freeze (hang) with AMD VT extensions enabled => blacklist acer_wmi

Reported by: tiras_dude Owned by:
Priority: major Component: VMM/HWACCM
Version: VirtualBox 3.0.6 Keywords:
Cc: Guest type: Windows
Host type: Linux

Description (last modified by ramshankar) (diff)

After a few confirmed cases on the board, we decided to do a bug report

History here:  http://forums.virtualbox.org/viewtopic.php?f=7&t=17617&start=0

Machine: Acer Asprire 4530 Build 6823 AMD QL-62 Nvidia GeForce 9100m G BIOS 3335 (3334)

System: Ubuntu Jaunty 9.04 AMD64 Kernel 2.6.28-11-generic X-org 1.6.0 version 11 Nvidia 180.60 drivers Virtual Box 2.2.4 PUEL (Virtual Box 2.2.2 OSE)

Problem:

When Windows guest are allowed to use AMD-V extensions the system would hang (freeze) either during boot or during program execution (not necessarily program start). The freeze is recoverable only after hard reboot, but on certain occasions the host system was able to recover on it's on by going down to run-level 3 (longing out and restarting x-server).

The amount of ram allocated to the guest does not seem to matter. System hangs anywhere from 256 to 2048 mb RAM and 12-128 VRAM

Running System Monitor Applet seems to improve stability (machine runs longer before dying)

Vbox logs are attached

Please advise on what to do or what other info you will need.

Attachments

VBox.log_XPsp3_2.txt Download (37.9 KB) - added by tiras_dude 5 years ago.
VBox-3.0.6-PUEL-XPsp3-Jaunty-2-6-28-25-generic.log Download (37.2 KB) - added by tiras_dude 5 years ago.
No 3d with AMD-V
dump_file.rar Download (22.0 KB) - added by tiras_dude 4 years ago.
file 1 of the windows crash report
sysdata.rar Download (10.5 KB) - added by tiras_dude 4 years ago.
2nd file of windows crash report
problems.txt Download (336 bytes) - added by tiras_dude 4 years ago.
copy of the windows crash report dialog window
BSOD.jpg Download (90.3 KB) - added by tiras_dude 4 years ago.
Photo of the BSOD

Change History

Changed 5 years ago by tiras_dude

comment:2 Changed 5 years ago by sandervl73

Does turning off 3d support in the VM settings help? If it does, then try to find updates for your NVidia drivers.

comment:3 Changed 5 years ago by tiras_dude

3D support does not seem to make any difference in my case.

Ditto on shutdown freeze with XP

comment:6 follow-up: ↓ 7 Changed 5 years ago by wilbur.harvey@…

I have a similar problem. My host system is a Shuttle X48, 8GB Ram, Intel Core 2 Quad Q9650 CPU. Ubuntu 64-bit host. Hardware virtualization support is enabled in the BIOS. Whenever VT-x is enabled, the entire system instantly freezes with a black screen as soon as Virtualbox starts. If in the CPU options in the BIOS, I allow code space memory to not be write protected, then the same thing happens, except the screen doesn't go black. I have tried various versions of Nvidia drivers, VBox from V2.2 and now 3.02, I upgraded from Jaunty 9.04 to 9.10, nothing has any effect on the problem. I upgraded the BIOS as well. I am pretty sure that back < v2.0 of virtual box it would work. I Have tried enabling/disabling the 3D options. I typically have about 1GB of ram assigned to the guest, with 64MB or 128MB of ram for the video display.

comment:7 in reply to: ↑ 6 Changed 5 years ago by tiras_dude

Getting Worse!

Well 3.0.0 and 3.0.2 only worsened the situation. The 32 bit XP was very stable on this platform with 2.2.4 Guest Additions. Reinstalling 3.0.0 Guest additions returned the hardware virtualization freeze.

In addition in the 3.0.x series 64 bit XP and Win 7 refuse to run at all.

I tried adding "nohz=off" to the end of the "kernel" line in "/boot/grub/menu.lst" but that did absolutely nothing.

Interestingly enough this problem is specific to Acer 4530 hardware and Jaunty. Tried running VBox 3.0.2 PUEL on a AMD Athlon X2 5200 desktop system running Ubuntu 8.10 x64. X64 XP Guest and Win 7 x64 ran like a charm. Very Stable. Soon to upgrade desktop machine to Jaunty, will update with observations when it happens.

comment:8 Changed 5 years ago by frank

Is there any difference if you disable nested paging for the VM?

comment:16 Changed 5 years ago by adhisimon

I confirm this bug. Machine: Acer Asprire 4530 Host: Fedora 11 x86_64 Virtualbox version: 3.0.2 and 3.0.4

I've tried windows xp and vista, 32 bit and 64 bit guest. All have freeze my host.

comment:17 Changed 5 years ago by sandervl73

adhisimon: VBox.log please. If you don't have one, please tell me which AMD CPU you have.

comment:23 Changed 5 years ago by tiras_dude

Update. The problem continues on the 3.0.6 beta1. 32 bit XP runs untill total collapse either under Photoshop, or on shutdown signal (AMD-V, and Nested Paging, or without Nested Paging). 64 bit XP runs VDI's created on other systems, but cannot setup or run a 64 bit setup program. Additionally sending shutdown signal to a 64 bit xp vm causes system wide freeze, and irreparable damage to a VDI file (BSOD, FAT destruction, etc).

On machine that has a different amd cpu (VBOX 3.0.4), I am experiencing BSOD on XP 64 after serious system update or software install. Turning of the host (not loging out) and restarting vm seems to solve that problem by itself.

Let me know what info do you guys need to rectify the problem.

comment:24 Changed 5 years ago by sandervl73

  • Host type changed from other to Linux
  • Version changed from VirtualBox 2.2.4 to VirtualBox 3.0.6

comment:25 follow-up: ↓ 26 Changed 5 years ago by sandervl73

tiras_dude: try to disable 3d support in the VM settings. If that doesn't help, then please attach a log of the VM with 3.0.6 PUEL (please don't use your own compiled build to rule out any problems there).

Changed 5 years ago by tiras_dude

No 3d with AMD-V

comment:26 in reply to: ↑ 25 Changed 5 years ago by tiras_dude

Hello,

Still the same issue. I attached the VBox-3.0.6-PUEL-XPsp3-Jaunty-2-6-28-25-generic.log. Died within minutes of boot.

BTW running 3d without AMD-V works ok, except for Solidworks 2008 (video issues, but no system stability problems).

Still can not run 64 bit windows successfully at all.

comment:27 Changed 5 years ago by frank

  • Component changed from other to VMM/HWACCM

comment:28 Changed 5 years ago by sandervl73

Sounds like a BIOS problem to me. Try to find an update. There are known errata for AMD cpus and BIOSes must be updated to implement workarounds. For a similar ticket see #4988.

comment:29 Changed 5 years ago by sandervl73

A good thing to check is if there are similar reports for Windows 7/XP Compatibility mode & VirtualPC for the same hardware.

comment:30 Changed 5 years ago by tiras_dude

sandervl73 - I would tend to disagree

  1. I have the newest BIOS from acer on the machine.
  1. I have tested vmware and parallels on the same machine and had no stability issues. VBox is much faster.
  1. 3.0.8 is a whole lot more stable. I am cautiously going to say that XP32 issue is gone.

XP 64 (and the same for linuxes amd64) do occasionally freeze but this is an exception rather than the rule as previously.

In addition, I have been testing ubuntu karmic with 2.6.31 kernel with Vbox 3.0.8 and have not noticed any issues at all yet. Keeping my fingers crossed.

If the improvement continues in 3.1.0 and above, this would be the most awesome virtualization product out there. (And if we could run snow leopard as guest (as on can do now in VMWare) with additions, without telling mr. jobs there will be no equal to this product =)

comment:31 follow-up: ↓ 32 Changed 5 years ago by sandervl73

VMWare nor Parallels use AMD-V by default as far as I know.

There were no fixes in 3.0.8 to address your issue, so something else might have contributed to the improvement. Perhaps the Ubuntu update, but it sounds like the problem is still there.

comment:32 in reply to: ↑ 31 Changed 4 years ago by tiras_dude

sandervl73 - I may have spoken too soon, the new Jaunty -16 kernel is unstable again with VBox.

Do you have links to known errata for AMD Hyper-V cpu issue so I can forward the info to ACER to see if they can get a bug fix bios release for our machine?

comment:33 Changed 4 years ago by tiras_dude

Now, I don't know who should be fixing this (amd is definitely not doing it =(

But this document has something that I think is related  http://support.amd.com/us/Processor_TechDocs/41788.pdf

In Particular:

"246 Breakpoint Due to An Instruction That Has an Interrupt Shadow May Be Delivered to the Hypervisor

Description

A #DB exception occurring in guest mode may be delivered in the host context under the following conditions: • A trap-type #DB exception is generated in guest mode during execution of an instruction with an interrupt shadow, and • The instruction that generated the exception is immediately followed by an instruction resulting in #VMEXIT.

Potential Effect on System Unpredictable results due to an unexpected #DB exception.

Suggested Workaround The hypervisor should have a valid interrupt gate in the IDT of the #DB handler entry and the handler must be able to determine that this event has occurred. If the event is detected, the handler should execute an IRET back to the hypervisor; one method that could be used to evaluate for this condition is to compare the RIP pushed on the stack to the RIP of the instruction following VMRUN, if they are equivalent then this event has occurred.

Fix Planned No"

Now given that our hypervison is VBox, may be somebody from V-Box team can implement this adjustment in to the code in the future release.

If it's not the area for v-box please advise and I will go bug Acer or Ubuntu kernel team.

comment:34 Changed 4 years ago by tiras_dude

problem continues 3.0.8, 3.0.10, 3.1.0 Beta 1

comment:35 Changed 4 years ago by sandervl73

Can you find anything with google about your machine & Windows 7 (xp comp mode) or Virtual PC?

comment:36 Changed 4 years ago by tiras_dude

nothing on the net, but I am trying to install win7 rc to see if i get the same problems in virtual pc.

why in the world can you not run windows from a usb drive? arrrr. hate that company.

comment:37 Changed 4 years ago by tiras_dude

I have installed windows 7 x64 with xp mode / virtual pc. So far no issues, installing same soft as in my xp guest as of the moment. Is there any particular tests you want me to run while this thing is installed? I will keep this os on my machine untill tomorow, please let me know asap.

comment:38 Changed 4 years ago by sandervl73

How did you use the xp mode? I had to install an additional piece of software (from MSDN) here. Only then will it show up in the menu and you can start the XP VM.

comment:39 Changed 4 years ago by tiras_dude

Here is an update:

To get to use xp vm I had to go here:  http://www.microsoft.com/windows/virtual-pc/download.aspx and install both the xp-vm and virtual pc (the first is the actual xp vm build and the later being the hypervisor as I understand).

I set the memory and everything else to mach as closely to my VBox as I could.

Eventually I did manage to break it to get consistent BSOD's. By default XP-VM does not shut down, but hibernates. As soon as I forced it to shudtown, I got BSOD. I am attaching windows dump data, I don't know if it will help or not.

Called Acer, and forced them to post a BIOS update to version 1.3336 on their  website (If the link does not work go www.support.acer.com and use driver download script)

Unfortunately, update did not solve the problem. I will be trying to talk to level II techs today, once they wake up, but so far I am dealing with level I and it is terrible.

If you have any suggestions on what I should tell them, please post, I still have the Win 7 installed, and probably keep it untill the weekend or untill issue is resolved.

Changed 4 years ago by tiras_dude

file 1 of the windows crash report

Changed 4 years ago by tiras_dude

2nd file of windows crash report

Changed 4 years ago by tiras_dude

copy of the windows crash report dialog window

Changed 4 years ago by tiras_dude

Photo of the BSOD

comment:40 Changed 4 years ago by tiras_dude

Got through to level II tech at ACER today. Highlighted the AMD errata and our forum thread there. The issue has been forward to engineering. Hopefully the answer will come sooner than later.

sandervl73 - if you know what needs to be done by ACER tech, please post here, my guess they will be reading this soon.

Cheers

comment:41 Changed 4 years ago by tiras_dude

Guess Acer does not care about hardware support: because virtual pc is not supposed to run on windows home premium (original os of the Acer 4530) they will not provide support for it, or issue a bios patch.

Got to love cop-outs. "And its also not a hardware issue."

Anyway, if any other 4530 owners want to bug Acer, you can reference case 1-5N1FZA, but I am really disappointed in such a stance from the company.

sandervl73 - if your team can do something on your side to resolve it, you would be awesome, otherwise I guess I can forget about hardware virtualization on this system.

comment:42 Changed 4 years ago by tiras_dude

sandrvl, got an e-mail from the Acer tech guy, guess they do have some good people working there, he sent me this link:

 http://www.faultwire.com/solutions_bsod/A_clock_interrupt_was_not_received_on_a_secondary_0x00000101-1254.html (in particular the slew of links to msnd issues at the bottom). Apparetly some of the similar bsod's are indeed software related. I am digging through to see if there is anything particular to amd, so far mostly intel xeon issues.

Just an FYI

comment:43 Changed 4 years ago by sandervl73

BSOD 0x101 is just a generic one. It would be interesting if there are more reports from 4530 owners about similar problems.

comment:44 Changed 4 years ago by sandervl73

#4988 is a similar issue with a Dell laptop for instance. (and there are a lot of reports on the internet/dell support forums) Not quite the same CPU as you've got, but it looks like a similar issue.

There are known errata for certain AMD CPU models that require BIOS workarounds. That's all I can say unfortunately (NDA).

From my end without access to such a machine it's rather difficult to provide further assistance.

comment:45 Changed 4 years ago by tiras_dude

sandrvl73 are you US based? If so, I am willing to send you this thing in the name of science =) for a week or so. If this is acceptable, e-mail me privately just add hotmail to the user name for e-mail.

comment:46 Changed 4 years ago by sandervl73

We're all in Europe, so that would be difficult (customs, danger to hardware) unfortunately. Thanks for the offer though.

Do you have the same stability issues with linux guests (e.g. DSL bootable iso)?

comment:47 Changed 4 years ago by tiras_dude

The issue is pretty much for windows (xp,7) guests (and select sofware [photoshop cs3 is notorious for killing the guest and host {zoom, clone tool}]/happens always/, or operations (installation, shutdown, file transfer)/happens ocasionally, except for windows7 x64 install wich fails all the time/. Also, the install environment on xp64 likes to take out the system.

Unix derivatives: Linux (Ubuntu, Suse, Fedora), BSD, or Solaris guests run fine (x32/x64) exept for Moblin and OSX. I do get a freeze on start-up onece in a blue moon, but that is usualy due to faulty settings or oddball occurence (can't replicate it).

comment:48 Changed 4 years ago by nmcbride

Well, I suppose I don't really have much to add that is different. Same system, same problems.

*nix based guest installs seem to work fine. Windows based guest installs, well I can't actually get it installed. XP freezes my entire box (archlinux x86_64) when it copies the install files to start the install.

I wish I found this before I wiped my box thinking it was the encrypted drive setup I did. Atleast now I know I can redo that.

I read one guy who said he installed even a newer bios than was available on Acer's site and still is having the problems. I actually haven't updated my bios and was wandering which one I should update to?

comment:49 follow-up: ↓ 50 Changed 4 years ago by zosX

I've had the same problem here for a while. Same machine, except I am running a windows 7 x64 host and the linux guest causes a bsod on the host. Running 1.334 bios here. 1.336 seemed to have some issues. I wonder if a software workaround could be found, as the issue seems related to the bios and acer doesn't seemed to be all that inclined to figure out why someone might want to use the AMD VT and fix it for them. XP Mode completely kills my system, usually before it even gets to boot, though I did get it to go to the desktop once before dying. Also older versions of vbox seemed more stable on this machine, with the BSOD only occuring when IOAPIC was enabled. Now just enabling AMD VT and nothing else at all on a single core will cause a pretty immediate BSOD, so clearly stability is going south. I am using the latest stable 3.14 version. I just reinstalled to Windows 7 Ultimate from the RC and was pretty disappointed that XP Mode had this problem and then really sad that vbox was the same way. Clearly it is the hardware and not windows 7 or anything since it does the same thing on linux hosts. I guess you will just have to accept that the acer 4530 is pretty broken when it comes to virtualization and hope that perhaps acer will actually get around to implementing it properly, which may or may not be possible to be honest, since they may have taken shortcuts, hence the incompatibilities. I've submitted a few bug reports on this and this one is actually the most active I've seen. It seems the turion processors have a commonality in some bioses (dell, acer) that keep their VT feature from working properly. There is a working dell bios for one of the machines, so maybe some crazy bios hacker could digg into it a bit and figure out exactly what they changed.......

comment:50 in reply to: ↑ 49 Changed 4 years ago by Brainy142

Same machine same issue, oddly I had it working then It just freezes, I have tried different versions of 7 and cant run any in a vm in linux, it will freeze everything and will make me do a force shutdown to go back to normal.

comment:51 in reply to: ↑ description Changed 4 years ago by weinter

Can we do a orchestrated approach to demand a fix from Acer? Can we start a thread on Microsoft Technet make the same complain to Microsoft and Acer at the same time. Quote 1 case so we will be bring up the same case when we complain to Acer on the BIOS Fix. I can modify the BIOS but I do not know what changes the Dell Guys did.

comment:52 Changed 4 years ago by tiras_dude

weinter

Sorry for not getting back on this quicker. A. I definitely support the class action approach to the fix. We should start compiling a list of people affected by this bug on Acer machines, and then when we have a hundred or so, do a mass call in one day to the tech support or something. It should get their attention.

With regards to a DIY fix, let me know how I can help you did out the info. It may be possible to contact Dell directly (their linux team) and they may help.

May be even VBox people may give us clues.

Get in touch with me offline my username @ hotmail and we can disscuss more solution strategies.

Cheers,

T

comment:53 Changed 4 years ago by weinter

I contacted them. Those retards kept giving me generic replies and told me I needed to pay as it was not underwarranty. I was extremely pissed because the issue is inherent in all laptops and clearly it was lousy firmware implementation and we needed to pay for a proper bug free firmware? I bet 10 bucks those script reading *tard don't even know what is hardware virtualisation. Pathetic. I am considering a class action toward them IF it is what it actually takes to wake those *tards up. Seriously Acer should hire people with more brains.

comment:54 Changed 4 years ago by zosX

here is what i find interesting. after searching for a while, it appears that users running linux hosts have no problems after they enable the nohz=off option to the kernel at boot. Can anyone confirm this is still the case with newer bioses? It seems like there has to be some sort of software workaround. I mean I guess that you would have to figure out why the cpu timers weren't synchronizing on the host in the first place. My problem is that I'm trying to virtualize linux from windows and I don't know if they could easily place a workaround there as vt/hyper-v is causing the windows kernel to BSOD. It is certainly something with the timing. It seems as one core starts locking up and waiting for the other. Like if you are playing an mp3 on the host, it will just stutter (a sure sign a BSOD is about to happen) as the sound chip has nothing new entering the buffer. The other thing is that the guest OS usually installs fine, its just when you install and enable the virtualbox additions that things start going south. Its not just virtualbox. I could run the XP Compatability mode in windows 7 for about a hold minute before I got a BSOD. I think I got a desktop and open IE6 once....

Anyways, suing acer won't make a damned bit of difference. They aren't legally obligated to support a laptop they no longer make nor sell. It would be a big waste of money. If they were willing to perhaps support you for a fee, then I don't see that as unreasonable. They never advertised the machine as being Hyper-V compatible, so they have no real obligation to make it so. I mean look at their choice of OS: 32-bit Vista Home Premium. That should say a lot about these machines' target market. I doubt many customers are looking to storm their doors with torches and pitchforks, so I doubt that they have any interest in fixing this issue at all. I guess next time make sure that something works before you buy it if it is a huge critical issue. That being said, it seems that a lot of laptops have issues with VT/Hyper-V, even though they contain processors that are certainly capable and even report with testing tools that they are compatible. Since the problems purely arise in the bios implementations that are broken, isn't there some kind of software workaround that could be done? Its certainly a timing issue, isn't there some way to massage the timing of the guest so cores aren't locking against each other? The BSOD I get in windows refers to a timer hanging on core 0. In previous flavors of virtualbox I could at least get Hyper-V enabled on a single core, but enabling the IO APIC and multi-core always resulted in a BSOD. Now just enabling Hyper-V thrashes the whole thing. I would say that stability is really going south. Does anyone have any clue what is so broken about these bioses? they are award bioses. i believe that dell uses the same implementation or a similar one, and that they have fixed their issues with amd chips, at least on certain models. If anyone knows anything about bios dumps and would like to see what they changed between bioses, I'll see if I can dig that message I read about the dells. I think it was their studio laptops. I think they only have one line with amd processors, and they should also have changelogs with their bioses.

comment:55 Changed 4 years ago by weinter

Since when are laptops advertised as Hyper-V compatible. If it is a feature enabled in the BIOS it better work. If not they should disable it in the BIOS in the first place not leaving the feature half baked out. Is there a clause saying they are not obligated to support it after no production? Moreover some people who bought the 3 year warranty is still eligible for a fix. It is very difficult to reverse engineer the dell bios moreover it is all assembly code. You will have more luck bricking the laptop than fixing it. And the Dell line is a Latitude AMD Laptop line.

comment:56 Changed 4 years ago by johnwarde

Possible similar bug  #6509

comment:57 in reply to: ↑ description Changed 4 years ago by lookingforaossjob

Hello everyone,

First of all, screw Acer and their buggy BIOS and their lack of support. I've been a fan for years but I'm really disappointed at how they've treated this issue. My next notebook is going to be a Dell since they were very helpful towards their users that had this exact same problem.

But this doesn't change the fact that we're stuck with this Acer 4530 that can't do AMD-V. Since we can't force Acer to fix this, we my friends, must take the matter to our own hands.

Implementing such a fix on a BIOS is impossible without the right datasheets and tools, however, remember the processor is defective, but a software workaround exists. After reading AMD's errata, I understood that some exceptions generated in the guest are being passed to the host, which cause the freeze. So I figured out the workaround doesn't necessarily need to be at the BIOS level, even if that would be the best fix. If we can make sure these exceptions never reach the host's bios, no more freezes will happen.

Looking for ways to do this, I noticed my Linux host was using a suspicious module: acer_wmi.

I tried removing and blacklisting this module, and to my surprise the freezes are gone.

Here's the complete workaround:

  • Type modprobe -r acer_wmi
  • Edit /etc/modprobe.d/blacklist.conf
  • Add to the end of the list "blacklist acer_wmi" without the quotes
  • Start your virtual machines with AMD-V enabled.
  • Enjoy your AMD-V without the freezes!

Replying to tiras_dude:

After a few confirmed cases on the board, we decided to do a bug report

History here:  http://forums.virtualbox.org/viewtopic.php?f=7&t=17617&start=0

Machine: Acer Asprire 4530 Build 6823 AMD QL-62 Nvidia GeForce 9100m G BIOS 3335 (3334)

System: Ubuntu Jaunty 9.04 AMD64 Kernel 2.6.28-11-generic X-org 1.6.0 version 11 Nvidia 180.60 drivers Virtual Box 2.2.4 PUEL (Virtual Box 2.2.2 OSE)

Problem:

When Windows guest are allowed to use AMD-V extensions the system would hang (freeze) either during boot or during program execution (not necessarily program start). The freeze is recoverable only after hard reboot, but on certain occasions the host system was able to recover on it's on by going down to run-level 3 (longing out and restarting x-server).

The amount of ram allocated to the guest does not seem to matter. System hangs anywhere from 256 to 2048 mb RAM and 12-128 VRAM

Running System Monitor Applet seems to improve stability (machine runs longer before dying)

Vbox logs are attached

Please advise on what to do or what other info you will need.

comment:58 Changed 4 years ago by tiras_dude

Dear lookingfor...!

Many thanks indeed. I can confirm that the fix is working here on lucid amd64 machine. =))))) You just made my day!!!

Small update instruction update for newbies on Ubuntu (or similar gnome based distros):

  1. Start terminal (Applications > Accessories > Terminal)
  2. Type or paste this line first (Shift+CTRL+V):
    sudo modprobe -r acer_wmi
    
  3. Than paste or type this line:
    sudo gedit /etc/modprobe.d/blacklist.conf
  4. In the newly opened window, scroll to the bottom and type or paste this line (CTRV+V)
    blacklist acer_wmi
    
  5. Click Save and close the window
  6. Type exit in the terminal window
  7. Enjoy (you can reboot if you want)

and for newbies on Kubuntu (or similar KDE based distros):

  1. Start terminal (Applications Tab> System > Terminal (Konsole))
  2. Type or paste this line first (Shift+CTRL+V):
    sudo modprobe -r acer_wmi
    
  3. Than paste or type this line:
    sudo kate /etc/modprobe.d/blacklist.conf
    
  4. In the newly opened window, scroll to the bottom and type or paste this line (CTRV+V)
    blacklist acer_wmi
    
  5. Click Save and close the window
  6. Type exit in the terminal window
  7. Enjoy (you can reboot if you want)

Cheers all!

comment:59 Changed 4 years ago by frank

  • Summary changed from Windows Guests (XP, Vista, 7 32 or 64 bit) cause non-recoverable (reboot only) machine freeze (hang) with AMD VT extensions enabled. to Windows Guests cause non-recoverable (reboot only) machine freeze (hang) with AMD VT extensions enabled => blacklist acer_wmi

comment:60 Changed 4 years ago by frank

Thank you guys for adding these findings!

comment:61 Changed 4 years ago by sandervl73

  • Status changed from new to closed
  • Resolution set to fixed

comment:62 Changed 2 years ago by razamatan

  • Status changed from closed to reopened
  • Resolution fixed deleted

what's the fix for windows hosts and linux guests?

comment:63 Changed 2 years ago by Technologov

In some cases updating BIOS helps. (BIOS updates AMD CPU microcode)

Sometimes only disabling VT helps.

-Technologov

comment:64 Changed 2 weeks ago by ramshankar

  • Status changed from reopened to closed
  • Resolution set to fixed
  • Description modified (diff)
Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use