VirtualBox

Ticket #5407 (closed defect: fixed)

Opened 4 years ago

Last modified 6 months ago

SUSE Linux 9.1 guest refuses to load with VT-x enabled

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

Description (last modified by frank) (diff)

Host: Windows 7, 64-bit, VBox 3.0.10, Core 2 Q6600.

Guest: SUSE Linux 9.1, 32-bit guest fails to load from CD, when VT-x enabled; works fine when I disable VT-x.

NOTE: I think it may be bootloader related, rather than kernel related, because I *can* load the system with VT-x when booting with "shift" key pressed, bypassing graphical bootloader.

SUSE Linux 9.1 Personal Edition is freeware, so I can send you the ISO for testing.

Steps to reproduce:

  1. insert CD
  1. choose "install" option

-Technologov, 6.nov.2009.

Attachments

SUSE Linux 9.1 32-bit-2009-11-06-21-56-42.log Download (49.4 KB) - added by Technologov 4 years ago.

Change History

Changed 4 years ago by Technologov

comment:1 Changed 4 years ago by Technologov

This bug looks similar to bug #3317

Let me know, if you need SUSE 9.1 ISO.

-Technologov

comment:2 Changed 4 years ago by Technologov

Also, This bug looks similar to bug #2865

-Technologov

comment:3 Changed 4 years ago by Technologov

Also, This bug looks similar to bug #4249

-Technologov

comment:4 Changed 4 years ago by ppgrainbow

Do you have Intel VT-x/AMD-v turned off?

comment:5 Changed 4 years ago by Technologov

Host: Windows 7, 64-bit, VBox 3.0.10, Core 2 Q6600.

Again:

SUSE Linux 9.1 works with VT-x = off (software virtualization)

SUSE Linux 9.1 doesn't works with VT-x = on (hardware virtualization)

-Technologov

comment:6 Changed 4 years ago by frank

  • Component changed from VMM to VMM/HWACCM

comment:7 Changed 4 years ago by Technologov

Also, This bug looks similar to bug #4295

-Technologov

comment:8 Changed 4 years ago by Technologov

Same problem with SUSE Linux 10.0 (aka openSUSE 10.0)

-Technologov

comment:9 Changed 3 years ago by Technologov

Bug still exists in VBox 4.0.4.

Happens only with basic VMX, Unrestricted VMX works fine. (on Intel Core i7 2600K CPU)

-Technologov

comment:10 Changed 6 months ago by frank

  • Status changed from new to closed
  • Resolution set to fixed
  • Description modified (diff)

Please reopen if still relevant with VBox 4.3.2.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use