Custom Query (16363 matches)
Results (532 - 534 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #14550 | worksforme | 64-bit VM guests are not listed as option and VM's won't start because of VT-x not available. | ||
| Description |
I had several 64-bit guests (Ubuntu desktop, server, and Windows 2012 R2 server) that ran on my system (Windows 7 ultimate OS, i7 CPU w/16 GB RAM host) successfully with VBox 5.0. I upgraded to Windows 10 and everything broke. I am using VBox 5.0.3 test build now and have gotten my network adapters to work again, but now I'm seeing another issue that is preventing my VM's from running. I can not see a 64-bit guest OS listed as an option (Windows server 2012 isn't listed anymore). This is for my old VM's - they are still have that from when they were running on a Win 7 host but if you look at settings it tries to change it to a 32-bit guest OS and you don't have the option to select a 64-bit guest OS if you try to create a new VM. When I try to start any of my VM's I get an error message about no VT-x available: Failed to open a session for the virtual machine Anduril.
VT-x is not available (VERR_VMX_NO_VMX).
Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
|
|||
| #3865 | obsolete | 64-bit Vista Home Premium additions problems/fixed in 3.0.8 | ||
| Description |
I first noticed this with 2.1.4, and it still exists with 2.2.2. 64-bit Vista Ultimate is NOT affected. Everything below applies to a 64-bit Home Premium guest on a 64-bit OpenSolaris 2008.11 host unless otherwise mentioned. With guest additions installed, the guest display won't resize or properly enter seamless or full screen mode. "Auto Resize Guest Display" is enabled. The mouse pointer shows the Vista pointer below my OpenSolaris pointer. 32-bit Vista is not affected, nor are other 32 or 64-bit guests, such as XP (32-bit), Ubuntu 8.x and 9.x, OpenSolaris, or Solaris 10u6. I've recreated the problem on multiple hosts. I've also installed a Vista 64-bit Home Premium guest from scratch with no success. 64-bit Ultimate works perfectly. With 2.2.2 on Home Premium, I noticed that the additions are installing a secondary, inactive, graphics adapter called "(Default Monitor) on VirtualBox Graphics Adapter", but when I enable it, it just flickers endlessly until I shut down the guest. |
|||
| #6976 | invalid | 64-bit Windows 7 guest refuses to finish installation on 64-bit Lucid host | ||
| Description |
Hi, I've got an Ubuntu Lucid 64-bit host and also a CPU with vmx support (Core i7). Motherboard is ASUS P6T Deluxe. kvm modules are not loaded on Ubuntu, and should not interfere with VMX. I'm trying to run a Windows 7 64-bit guest on VirtualBox 3.2.4 r62467. I've tried installing it at least five times. One time it succeeded but after that I just got random errors. I ran memtest86+ inside of the VM and there were no errors reported. I am almost certain this is either a VT-x issue or hard drive controller problem. All the errors I get could have been caused by the VT-x feature or the hard drive controller. One time I got KERNEL_STACK_INPAGE_ERROR and other times I just get messages saying a file is corrupt and the Windows installation has to stop. I have tried with and without nested paging, PAE/NX, 1 cpus, 2 cpus, video memory adjustments, 2d/3d acceleration, Host I/O caching on the cd (booting from an ISO) and hard drive, on an ext4 mdRAID5 and xfs non-raid partition. A SCSI controller. A PIIX4. An ICH6. Nothing fixes it. I obviously haven't tried all permutations of those, but I've tried a lot of things. I tried increasing the RAM from 1024MB to 1536, doesn't fix it. There is nothing in any log that I've seen. The bug is deep down in there somewhere. Why would this be a 64-bit issue? My Windows 7 32-bit guest doesn't have a single error. I've run Windows 7 64-bit guests under VIrtualBox before with no issues (on older Ubuntu hosts, on "Sun VirtualBox" before the Oracle switchover). I did update my BIOS since then, but honestly, I doubt it's this, anyway. My motherboard has been rock solid and every problem I've ever had was a software one. Each time I'm allocating a 40 GB disk dynamically on either ext4(thru MDRAID) or xfs. I then tried allocating a 20 GB fixed disk on my xfs partition, and that also failed. I did not try the patch posted here because I statically allocated my disk and it still happened. Every time I am reading an ISO from disk. I am going to try and burn the ISO and use my actual CD drive. If you want any sort of background on any component in my computer, let me know, but I posted what I felt was pertinent here. I also posted at this forum thread: http://forums.virtualbox.org/viewtopic.php?f=7&t=31192&p=142493#p142493 Thank you for your time. |
|||

