VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (529 - 531 of 16363)

Ticket Resolution Summary Owner Reporter
#4923 fixed 64-bit OpenSolaris not working on Linux host (VMX invalid guest state guru) -> retry with 3.0.10 Pawel Biernacki
Description

As in summary: I've 32 bit Linux host and want to try some 64bit OS'es. Other Linux'es, all BSD's and Windows 7 x64 works great. Only 64-bit guest have some problems (32-bit version just works). Few seconds after staring the virtual machine message box with guru appears and announce crash. VBox.log included.

#2394 obsolete 64-bit Opensolaris guest boot errors on 64-bit OpenSolaris host running NIS bqbauer
Description

I have three host installations of 64-bit OpenSolaris 2008.05 running VB 2.0.2 (amd64). On most I have no problems installing 64-bit guests, including OpenSolaris 2008.05 as a guest. However, if the OpenSolaris 64-bit HOST is running as an NIS client, then the OpenSolaris 64-bit GUEST, including LiveCD, boots extremely slowly and with the following errors, no matter if the guest machine has been configured with or without these options: network card (none), audio card (none), serial (none).

Guest Errors (repeated):

Method "/usr/sbin/avahi-daemon-bridge-dsd -D" failed with exit status 255. Method "/lib/svc/method/inetd-updatde start" failed due to signal KILL. gdm-binary....WARNING: Failed to start X server several times in a short time period...

The errors are not present if VT is disabled and therefore 32-bit OpenSolaris is used. ACPI has been enabled in all tests, and mixtures of the other two settings have also been tested.

The two computers used to test NIS were a Dell Precision 380 with 8GB memory and Pentium D 3GHz, the next was a Thinkpad Z61p with a core2Duo and 2GB memory that had been working with OpenSolaris as a host AND guest. I made the Thinkpad an NIS client, and then this problem materialized both with the installed version and with a LiveCD guest, just as described above. A third system that has never seen NIS runs OpenSolaris as a 64-bit host and guest perfectly (It is a Shuttle SX38P2 Pro).

OpenSolaris runs NIS as a client fine and I don't think it is an OpenSolaris issue since this happens with a raw LiveCD boot with no networking in the guest whatsoever. It is this mix of OpenSolaris 64-bit GUEST on an OpenSolaris 64-bit HOST running NIS that makes the GUEST fail to boot properly.

Although I've not been able to track down the settings that most influence this problem, I have found that having in your HOST's /etc/nsswitch.conf the "bad" entries below seems also to help manifest the VB problem, but the "good" entries do not. In both situations, NIS must actually be running and working for this to have an impact. Recall that this is in spite of the fact that your guest can be configured without a network card and the problems still occur.

BAD: hosts: files nis dns GOOD: hosts: files dns nis

BAD: aliases: files nis GOOD: aliases: nis files

Sorry to be so verbose, but it can be difficult to describe the specifics of how & when this manifests, but it has only happened in the situations described.

#10514 worksforme 64-bit Ubuntu guest won't start - hardware acceleration "not operational" Andrew Schulman
Description

Host is 64-bit Ubuntu Maverick, guest is 64-bit Ubuntu Precise. The guest won't start, coming up with the dreaded error dialog:

VT-x/AMD-V hardware acceleration has been enabled, but is not operational.
Your 64-bit guest will fail to detect a 64-bit CPU and will not be able to boot.

Please ensure that you have enabled VT-x/AMD-V properly in the BIOS of your
host computer.

AMD-V is available in the CPU:

$ grep -c ' svm ' /proc/cpuinfo
3

and I've checked that it's enabled in the BIOS. Motherboard is a Gigabyte GA-MA790XT-UD4P, CPU is AMD Phenom II X3 720.

I'm attaching VBox.log. Note the following excerpts:

00:00:00.846 Mnemonic - Description                 = guest (host)
00:00:00.846 SVM - AMD VM Extensions                = 0 (1)

This seems to show that SVM is available in the host, but not the guest.

Virtualbox seems to claim that the error is because SVM is already in use:

00:00:00.962 HWACCM: No VT-x or AMD-V CPU extension found. Reason VERR_SVM_IN_USE

But AFAICT that's not the case. No KVM is installed, and lsmod confirms that none is loaded. I don't see any virtualization modules loaded apart from vboxdrv, vboxnet, etc.

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy