Can't get VT-X to work on Red Hat Enterprise Linux 4 host
Posted: 2. Mar 2009, 18:00
While my research has not been painstaking, I've googled about a bit and read through the pertinent sections of the the user's manual and VirtualBox's FAQ. I am running VirtualBox 2.1.4 on the 64-bit version of Red Hat Enterprise Linux 4. I have a Core 2 Q6600 processor. I have enabled VT-X in my BIOS, and enabled it for all my virtual machines using the configuration GUI. Yet, when I actually start a VM, VT-X is never enabled - though the machine does function correctly in most other respect.
It might be related that the vboxdrv /dev/ entry has the wrong permissions (as far as I understand what it should be): it is created with the permissions 0600. I also have no other vbox* entries in /dev/ (shouldn't there be entries used by the virtual networking and USB features in there?), and the USB pass-through feature does not work. I'm kind of thinking that udev may be misbehaving, and I've tried poking at vboxdrv's rules file in udev, but that hasn't helped - I'm kind of thankful that I at least didn't seriously break anything. Simply manually chmoding /dev/vboxdrv/ to 0660 (and 0666) has not resolved the issue.
VT-X was working with the version of VirtualBox before 2.0 - I believe my problems started with I upgraded. However, I am aware of the issues with upgrading VirtualBox, and I've tried completely uninstalling and re-installing VirtualBox, and that hasn't helped.
I'm not sure what logs I can supply that would be of any use. I would be more than happy to supply any needed log files, if anyone would be so kind as to help me out.
It might be related that the vboxdrv /dev/ entry has the wrong permissions (as far as I understand what it should be): it is created with the permissions 0600. I also have no other vbox* entries in /dev/ (shouldn't there be entries used by the virtual networking and USB features in there?), and the USB pass-through feature does not work. I'm kind of thinking that udev may be misbehaving, and I've tried poking at vboxdrv's rules file in udev, but that hasn't helped - I'm kind of thankful that I at least didn't seriously break anything. Simply manually chmoding /dev/vboxdrv/ to 0660 (and 0666) has not resolved the issue.
VT-X was working with the version of VirtualBox before 2.0 - I believe my problems started with I upgraded. However, I am aware of the issues with upgrading VirtualBox, and I've tried completely uninstalling and re-installing VirtualBox, and that hasn't helped.
I'm not sure what logs I can supply that would be of any use. I would be more than happy to supply any needed log files, if anyone would be so kind as to help me out.
