I am running VirtualBox under F19, and I wanted to try F20 in a VM, but I can't get it to install. With both the Live ISO and the full DVD iso, if I point the virtual DVD drive at the ISO, it boots into the main syslinux/Anaconda menu, but as soon as I select "Install Fedora", the screen goes black and nothing ever happens. Has anyone installed F20 into a VirtualBox VM?
Thanks, --Greg
On Dec 19, 2013, at 4:50 PM, Greg Woods woods@ucar.edu wrote:
I am running VirtualBox under F19, and I wanted to try F20 in a VM, but I can't get it to install. With both the Live ISO and the full DVD iso, if I point the virtual DVD drive at the ISO, it boots into the main syslinux/Anaconda menu, but as soon as I select "Install Fedora", the screen goes black and nothing ever happens. Has anyone installed F20 into a VirtualBox VM?
Yes albeit it was on OS X. On Fedora I use virsh / virt-manager or Gnome Boxes.
Chris Murphy
On 12/20/13 07:50, Greg Woods wrote:
I am running VirtualBox under F19, and I wanted to try F20 in a VM, but I can't get it to install. With both the Live ISO and the full DVD iso, if I point the virtual DVD drive at the ISO, it boots into the main syslinux/Anaconda menu, but as soon as I select "Install Fedora", the screen goes black and nothing ever happens. Has anyone installed F20 into a VirtualBox VM?
Yes. Been installing and testing F20 on a VM for a while now.
But make sure you're running VirtualBox 4.3.6
On Fri, 2013-12-20 at 08:04 +0800, Ed Greshko wrote:
Yes. Been installing and testing F20 on a VM for a while now.
But make sure you're running VirtualBox 4.3.6
Thanks for the tip, I was on 4.3.4 . So I upgraded to 4.3.6, installed the extension pack, and... I still get a black screen after selecting "install Fedora 20" from the Anaconda/syslinux boot menu.
--Greg
On Thu, 2013-12-19 at 18:26 -0700, Greg Woods wrote:
On Fri, 2013-12-20 at 08:04 +0800, Ed Greshko wrote:
Yes. Been installing and testing F20 on a VM for a while now.
But make sure you're running VirtualBox 4.3.6
Thanks for the tip, I was on 4.3.4 . So I upgraded to 4.3.6, installed the extension pack, and... I still get a black screen after selecting "install Fedora 20" from the Anaconda/syslinux boot menu.
I wanted to use VB because I have been using it since forever and I have a couple of existing VMs that I want to keep using (as well as some management scripts I've written). For the F20 install, it's just temporary, so I decided to try just doing one in KVM, and that seems to be working so far.
At some point I'd like to move away from depending on Oracle, so I may look into what it would take to convert a Windows VM under VirtualBox to running under KVM/libvirt instead.
--Greg
On Thu, Dec 19, 2013 at 10:44 PM, Greg Woods woods@ucar.edu wrote:
At some point I'd like to move away from depending on Oracle
You might want to remove all the Oracle contributed patches to the Linux kernel too, and btrfs, and OpenJDK... *rolleyes* http://goo.gl/u3dOk7
FC
On 12/20/13 09:26, Greg Woods wrote:
On Fri, 2013-12-20 at 08:04 +0800, Ed Greshko wrote:
Yes. Been installing and testing F20 on a VM for a while now.
But make sure you're running VirtualBox 4.3.6
Thanks for the tip, I was on 4.3.4 . So I upgraded to 4.3.6, installed the extension pack, and... I still get a black screen after selecting "install Fedora 20" from the Anaconda/syslinux boot menu.
That is odd.....
FWIW, my F19 host is 64bit and I'm using the rpmfusion nVidia stuff to drive the host system video. Also, I've only installed/tested F20 in 64 bit.
When I select Install the screen goes black for about 5 seconds, then goes white for about 10 seconds and then black with scrolling messages.
You have verified the checksums of the downloaded ISO's?
On Fri, 2013-12-20 at 09:53 +0800, Ed Greshko wrote:
On 12/20/13 09:26, Greg Woods wrote:
On Fri, 2013-12-20 at 08:04 +0800, Ed Greshko wrote:
Yes. Been installing and testing F20 on a VM for a while now.
But make sure you're running VirtualBox 4.3.6
Thanks for the tip, I was on 4.3.4 . So I upgraded to 4.3.6, installed the extension pack, and... I still get a black screen after selecting "install Fedora 20" from the Anaconda/syslinux boot menu.
That is odd.....
FWIW, my F19 host is 64bit and I'm using the rpmfusion nVidia stuff to drive the host system video. Also, I've only installed/tested F20 in 64 bit.
Same for me on all counts.
When I select Install the screen goes black for about 5 seconds, then goes white for about 10 seconds and then black with scrolling messages.
That is what I see when I create a VM in virt-manager instead of VirtualBox, but under VB, the screen goes black and never recovers.
You have verified the checksums of the downloaded ISO's?
Yes, and the same ISO works fine under virt-manager. I actually got an install completed. So I'm going to concentrate now on moving away from VB altogether, which will require converting a couple of Windows VMs to run under KVM instead of VB. I only used VB in the first place because KVM really wasn't ready for prime time when Red Hat first started supplying it. Performance was horrible. Now it's much better as a lot of work has been done on it since then.
--Greg
Am 20.12.2013 00:50, schrieb Greg Woods:
I am running VirtualBox under F19, and I wanted to try F20 in a VM, but I can't get it to install. With both the Live ISO and the full DVD iso, if I point the virtual DVD drive at the ISO, it boots into the main syslinux/Anaconda menu, but as soon as I select "Install Fedora", the screen goes black and nothing ever happens. Has anyone installed F20 into a VirtualBox VM?
Thanks, --Greg
I had success with VirtualBox and F20 on two machines, after initially having this very black screen on several trials. So please don't mind my question: When creating the new VM in VBox Manager, did you choose the correct version of Fedora? I clicked on "Fedora" and I missed that there was an entry "Fedora (64bit)" ...
On 12/20/2013 11:28 AM, Klaus-Peter Schrage wrote:
Am 20.12.2013 00:50, schrieb Greg Woods:
I am running VirtualBox under F19, and I wanted to try F20 in a VM, but I can't get it to install. With both the Live ISO and the full DVD iso, if I point the virtual DVD drive at the ISO, it boots into the main syslinux/Anaconda menu, but as soon as I select "Install Fedora", the screen goes black and nothing ever happens. Has anyone installed F20 into a VirtualBox VM?
Thanks, --Greg
I had success with VirtualBox and F20 on two machines, after initially having this very black screen on several trials. So please don't mind my question: When creating the new VM in VBox Manager, did you choose the correct version of Fedora? I clicked on "Fedora" and I missed that there was an entry "Fedora (64bit)" ...
It worked for me when I selected "Red Hat (64 bit)" as the OS type.
Am 20.12.2013 18:43, schrieb Steven Stern:
On 12/20/2013 11:28 AM, Klaus-Peter Schrage wrote:
Am 20.12.2013 00:50, schrieb Greg Woods:
I am running VirtualBox under F19, and I wanted to try F20 in a VM, but I can't get it to install. With both the Live ISO and the full DVD iso, if I point the virtual DVD drive at the ISO, it boots into the main syslinux/Anaconda menu, but as soon as I select "Install Fedora", the screen goes black and nothing ever happens. Has anyone installed F20 into a VirtualBox VM?
Thanks, --Greg
I had success with VirtualBox and F20 on two machines, after initially having this very black screen on several trials. So please don't mind my question: When creating the new VM in VBox Manager, did you choose the correct version of Fedora? I clicked on "Fedora" and I missed that there was an entry "Fedora (64bit)" ...
It worked for me when I selected "Red Hat (64 bit)" as the OS type.
Yes, but the distinction 32bit - 64bit seems to be crucial.
On 12/20/2013 10:48 AM, Joe Zeff issued this missive:
On 12/20/2013 09:43 AM, Steven Stern wrote:
It worked for me when I selected "Red Hat (64 bit)" as the OS type.
Don't ask why, but when I first saw that I read it as "Red Bull (64 bit)" and wondered how an energy drink got into the list.
(tongue planted firmly in cheek...)
Crikey! Can't they just leave it at extreme sports and Formula One racing? Now they have to stick their fingers into OSes? Who do they think they are....Google?! ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@alldigital.com - - AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 - - - - Is it progress if a cannibal uses a knife and fork? - - -- Stanislaw J. Lec - ----------------------------------------------------------------------
On Fri, 2013-12-20 at 11:43 -0600, Steven Stern wrote:
On 12/20/2013 11:28 AM, Klaus-Peter Schrage wrote:
my question: When creating the new VM in VBox Manager, did you choose the correct version of Fedora? I clicked on "Fedora" and I missed that there was an entry "Fedora (64bit)" ...
It worked for me when I selected "Red Hat (64 bit)" as the OS type.
Something may be more fundamentally wrong than I thought. I don't see "64 bit" as a choice anywhere in Vbox Manager. When I look at the settings for the VM, I can't find anywhere that tells me if it's 32 bit or 64 bit.
I did check, and the VirtualBox RPM does say it's x86_64. I did get an F20 VM installed in KVM, but it's so slow that it's worthless.
The host machine is a quad core Haswell (i7) so I believe it has the necessary hardware virtualization stuff, and it's turned on in the BIOS.
--Greg
On 12/21/2013 09:54 PM, Greg Woods wrote:
On Fri, 2013-12-20 at 11:43 -0600, Steven Stern wrote:
On 12/20/2013 11:28 AM, Klaus-Peter Schrage wrote:
my question: When creating the new VM in VBox Manager, did you choose the correct version of Fedora? I clicked on "Fedora" and I missed that there was an entry "Fedora (64bit)" ...
It worked for me when I selected "Red Hat (64 bit)" as the OS type.
Something may be more fundamentally wrong than I thought. I don't see "64 bit" as a choice anywhere in Vbox Manager. When I look at the settings for the VM, I can't find anywhere that tells me if it's 32 bit or 64 bit.
I did check, and the VirtualBox RPM does say it's x86_64. I did get an F20 VM installed in KVM, but it's so slow that it's worthless.
The host machine is a quad core Haswell (i7) so I believe it has the necessary hardware virtualization stuff, and it's turned on in the BIOS.
--Greg
Which repo is your virtualbox from? I'm using the one from the Oracle repo at https://www.virtualbox.org/wiki/Linux_Downloads, http://download.virtualbox.org/virtualbox/rpm/fedora/virtualbox.repo
On Sat, 2013-12-21 at 22:41 -0600, Steven Stern wrote:
Something may be more fundamentally wrong than I thought. I don't see "64 bit" as a choice anywhere in Vbox Manager.
Which repo is your virtualbox from?
I'm not using a repo for it, I just downloaded it from the virtualbox.org web site, using the link provided by VirtualBox Manager. Which eventually points to https://www.virtualbox.org/wiki/Linux_Downloads . Then I install the extension pack once the Vbox software has been updated.
The RPM I have installed is VirtualBox-4.3-4.3.6_91406_fedora18-1.x86_64 (they don't seem to have one for Fedora 19).
--Greg
On 12/22/13 22:53, Greg Woods wrote:
The RPM I have installed is VirtualBox-4.3-4.3.6_91406_fedora18-1.x86_64 (they don't seem to have one for Fedora 19).
Yes, but the download is labeled for "Fedora 18 ("Spherical Cow") / 19 ("Schrödingers Cat")"
On 12/22/2013 5:27 PM, Ed Greshko wrote:
On 12/22/13 22:53, Greg Woods wrote:
The RPM I have installed is VirtualBox-4.3-4.3.6_91406_fedora18-1.x86_64 (they don't seem to have one for Fedora 19).
Yes, but the download is labeled for "Fedora 18 ("Spherical Cow") / 19 ("Schrödingers Cat")"
Fedora does not support Virtualbox at all. But that package works anyway. The user that provides them is not a volunteer. And if it did not work it would not install.
This has gone on so long That I forget just who asked about what in this thread.
Someone in this thread was asking about VM's. *After* you install the rpm and *after* you install the Guest-additions you make a blank VM.
From the Menu > New > 'enter the name you want' > next line "Type" means
select an OS" (you chose Linux, Windows, whatever) > Next line "Version" pick the distribution and the Arch for a p reconfigured setup up or 'write your own'.
Think of this VM as a *real computer* and put the disk (configuration) in the drive and boot it and install.
You guys are making this much, much more difficult than it is.
On 12/23/13 06:40, David wrote:
You guys are making this much, much more difficult than it is.
Not really.
The OP is using VBox from the Oracle site on F19 and is wanting to run F20 in a VM and he can't get it to install. Others, including myself, have had no problems. So.....trying to help find the reason.
On 12/22/2013 6:07 PM, Ed Greshko wrote:
On 12/23/13 06:40, David wrote:
You guys are making this much, much more difficult than it is.
Not really.
The OP is using VBox from the Oracle site on F19 and is wanting to run F20 in a VM and he can't get it to install. Others, including myself, have had no problems. So.....trying to help find the reason.
I had, Fedora 19 is gone, running Virtualbox with a VM of what was rawhide (the now Fedora 20) running for a long time. When rawhide split to Fedora 20 and Fedora 21 (rahide they bot still worked fine.
Two possibilities. PEBCAC or his hardware. My guess would be the first. Newbie stuff.
Virtualbox is the most thoroughly documented program I have ever since. Ever. The "Help File" is a searchable PDF. If 'your system' can read a PDF and if 'you' can read and comprehend all will be revealed.
I 'helped' an over 80 Year OLd lady do this by email. Me in Seattle and her in London. Took about a week.
On 12/22/2013 6:07 PM, Ed Greshko wrote:
On 12/23/13 06:40, David wrote:
You guys are making this much, much more difficult than it is.
Not really.
The OP is using VBox from the Oracle site on F19 and is wanting to run F20 in a VM and he can't get it to install. Others, including myself, have had no problems. So.....trying to help find the reason.
Hi Ed,
I did not mean to be 'nasty' here. But? I often see people that *think* that they know a lot or people that actually *do* know a lot confuse Newbies, either to Linux in general or some program, with all kinds of (he ducks under the desk here) *Geek Speak!* Do this!!. Try this!! Try that!! All written in *Geek Speak!* to a Newbie. IMHO? Sometimes, many times, the *Geek Speak!* folks make things too hard. Think about it.
Two possibilities. PEBCAC or his hardware. My guess would be the first. Newbie stuff. Whic is in now way bad. Everyone has to start somewhere. But First question? user experience? Second? What hardware? there are others. They depend on the answers to the first ones.
Virtualbox is the most thoroughly documented program I have ever since ever. The "Help File" is a searchable PDF. If 'your system' can read a PDF and if 'you' can read and comprehend all will be revealed. But? Once again it is written in *Geek Speak!*.
Honest. Read the 'help me' question. Is it a Newbie or 'knida Newbie' or 'I think I know what I am doing' question. And then> Don' everyon jump on him/er with tons of suggestions.
Ya' think?
On 12/23/13 07:58, David wrote:
On 12/22/2013 6:07 PM, Ed Greshko wrote:
On 12/23/13 06:40, David wrote:
You guys are making this much, much more difficult than it is.
Not really.
The OP is using VBox from the Oracle site on F19 and is wanting to run F20 in a VM and he can't get it to install. Others, including myself, have had no problems. So.....trying to help find the reason.
Hi Ed,
I did not mean to be 'nasty' here. But? I often see people that *think* that they know a lot or people that actually *do* know a lot confuse Newbies, either to Linux in general or some program, with all kinds of (he ducks under the desk here) *Geek Speak!* Do this!!. Try this!! Try that!! All written in *Geek Speak!* to a Newbie. IMHO? Sometimes, many times, the *Geek Speak!* folks make things too hard. Think about it.
Two possibilities. PEBCAC or his hardware. My guess would be the first. Newbie stuff. Whic is in now way bad. Everyone has to start somewhere. But First question? user experience? Second? What hardware? there are others. They depend on the answers to the first ones.
Virtualbox is the most thoroughly documented program I have ever since ever. The "Help File" is a searchable PDF. If 'your system' can read a PDF and if 'you' can read and comprehend all will be revealed. But? Once again it is written in *Geek Speak!*.
Honest. Read the 'help me' question. Is it a Newbie or 'knida Newbie' or 'I think I know what I am doing' question. And then> Don' everyon jump on him/er with tons of suggestions.
Ya' think?
The OP is not a newbie. He has stated that he has run VBox "since forever" and that F20 works fine in virt-manager.
The last significant post from the OP would indicate he has it running under virt-manager and is not concentrating on trying to find a method to convert VBox VM's to run under virt-manager.
On 12/23/13 09:57, Ed Greshko wrote:
The last significant post from the OP would indicate he has it running under virt-manager and is not concentrating on trying to find a method to convert VBox VM's to run under virt-manager
Should read....
The last significant post from the OP would indicate he has it running under virt-manager and is NOW concentrating on trying to find a method to convert VBox VM's to run under virt-manager
On 12/22/2013 9:01 PM, Ed Greshko wrote:
On 12/23/13 09:57, Ed Greshko wrote:
The last significant post from the OP would indicate he has it running under virt-manager and is not concentrating on trying to find a method to convert VBox VM's to run under virt-manager
Should read....
The last significant post from the OP would indicate he has it running under virt-manager and is NOW concentrating on trying to find a method to convert VBox VM's to run under virt-manager
I see.
Well then I stand corrected Ed. The OP has solved his problem, the original question, to his satisfaction at the moment, and the 'list noise' in only the echos of the 'try this it might work' helpers? Typical
But good for him. Most of the "try this - it might work" help from here was crap. I was going to suggest that he try the Virtualbox forum or mailing list where the developers actually land. The user that packages the Fedora Virtualbox package .rpm is there too.
Too late now... Have a good day Ed.
On Mon, 2013-12-23 at 09:57 +0800, Ed Greshko wrote:
The OP is not a newbie. He has stated that he has run VBox "since forever" and that F20 works fine in virt-manager.
The last significant post from the OP would indicate he has it running under virt-manager and is not concentrating on trying to find a method to convert VBox VM's to run under virt-manager.
Just to clarify: I am not a newbie, I have been a Unix sysadmin for almost 30 years, and been a Linux sysadmin for almost 15 years. I also run Xen virtualization systems at work that implement critical services such as DNS and authentication, so I am not new to the concept of virtualization either. I use VirtualBox at home just to run a couple of Windows VMs. All that said, it still often happens that someone else will think of something that I have not, or have a piece of knowledge that I lack, so even very experienced people may occasionally ask for help on a mailing list. I am not afraid to do that and I have often received very helpful advice.
I started this thread because I was trying to install an F20 VM under VirtualBox on an F19 system. I do know how to use VB to connect the DVD ISO to the VM and install an OS. The problem is that when I do this with the F20 ISO, syslinux boots and the first Anaconda selection screen comes up. I select "Install Fedora", and I get nothing but a black screen after that. I still have not solved this problem.
As a workaround, I attempted to install F20 on a VM under KVM. The install works, but the VM runs dog slow (so slow that it's useless).
So as of now, I still do not have a usable F20 VM. But I have moved on to other projects, since this wasn't something that was critically important. And this thread has now degenerated into something that is no longer related to the actual topic.
--Greg
On 12/23/2013 9:11 AM, Greg Woods wrote:
On Mon, 2013-12-23 at 09:57 +0800, Ed Greshko wrote:
The OP is not a newbie. He has stated that he has run VBox "since forever" and that F20 works fine in virt-manager.
The last significant post from the OP would indicate he has it running under virt-manager and is not concentrating on trying to find a method to convert VBox VM's to run under virt-manager.
Just to clarify: I am not a newbie, I have been a Unix sysadmin for almost 30 years, and been a Linux sysadmin for almost 15 years. I also run Xen virtualization systems at work that implement critical services such as DNS and authentication, so I am not new to the concept of virtualization either. I use VirtualBox at home just to run a couple of Windows VMs. All that said, it still often happens that someone else will think of something that I have not, or have a piece of knowledge that I lack, so even very experienced people may occasionally ask for help on a mailing list. I am not afraid to do that and I have often received very helpful advice.
I started this thread because I was trying to install an F20 VM under VirtualBox on an F19 system. I do know how to use VB to connect the DVD ISO to the VM and install an OS. The problem is that when I do this with the F20 ISO, syslinux boots and the first Anaconda selection screen comes up. I select "Install Fedora", and I get nothing but a black screen after that. I still have not solved this problem.
As a workaround, I attempted to install F20 on a VM under KVM. The install works, but the VM runs dog slow (so slow that it's useless).
So as of now, I still do not have a usable F20 VM. But I have moved on to other projects, since this wasn't something that was critically important. And this thread has now degenerated into something that is no longer related to the actual topic.
--Greg
I stand corrected. My bad. Sorry.
I have never had this problem but I see several users post about it. As I recall it the suggestions were 'to install in text mode' or to 'set the resolution' in the boot.
I do *not* know if these work, I never needed to try it.
Good luck.
On Mon, 2013-12-23 at 12:37 -0500, David wrote:
On 12/23/2013 9:11 AM, Greg Woods wrote:
I started this thread because I was trying to install an F20 VM under VirtualBox on an F19 system. I do know how to use VB to connect the DVD ISO to the VM and install an OS. The problem is that when I do this with the F20 ISO, syslinux boots and the first Anaconda selection screen comes up. I select "Install Fedora", and I get nothing but a black screen after that. I still have not solved this problem.
I have never had this problem but I see several users post about it. As I recall it the suggestions were 'to install in text mode'
Thanks for that idea. It didn't work, but it did tell me what's wrong. Somehow, the version of VirtualBox that I have doesn't actually support 64-bit VMs, even though it comes from an x86_64 RPM:
# rpm -qa | fgrep VirtualBox VirtualBox-4.3-4.3.6_91406_fedora18-1.x86_64
But when I do start the install in text mode (and erase "quiet" from the kernel command line), the error message is that it's a 32-bit CPU and I'm trying to boot a 64-bit kernel. Is it actually possible to install a 64-bit VM in VirtualBox, and if so, where do I get a version that supports it? The one I got came straight from the Downloads page at virtualbox.org, and when creating the VM by pressing the New button, it doesn't give any "64 bit" choices, just "Fedora".
--Greg
On 12/24/13 09:31, Greg Woods wrote:
On Mon, 2013-12-23 at 12:37 -0500, David wrote:
On 12/23/2013 9:11 AM, Greg Woods wrote:
I started this thread because I was trying to install an F20 VM under VirtualBox on an F19 system. I do know how to use VB to connect the DVD ISO to the VM and install an OS. The problem is that when I do this with the F20 ISO, syslinux boots and the first Anaconda selection screen comes up. I select "Install Fedora", and I get nothing but a black screen after that. I still have not solved this problem.
I have never had this problem but I see several users post about it. As I recall it the suggestions were 'to install in text mode'
Thanks for that idea. It didn't work, but it did tell me what's wrong. Somehow, the version of VirtualBox that I have doesn't actually support 64-bit VMs, even though it comes from an x86_64 RPM:
# rpm -qa | fgrep VirtualBox VirtualBox-4.3-4.3.6_91406_fedora18-1.x86_64
But when I do start the install in text mode (and erase "quiet" from the kernel command line), the error message is that it's a 32-bit CPU and I'm trying to boot a 64-bit kernel. Is it actually possible to install a 64-bit VM in VirtualBox, and if so, where do I get a version that supports it? The one I got came straight from the Downloads page at virtualbox.org, and when creating the VM by pressing the New button, it doesn't give any "64 bit" choices, just "Fedora".
FWIW..... On my F19 system....
[egreshko@meimei ~]$ rpm -qa | fgrep VirtualBox VirtualBox-4.3-4.3.6_91406_fedora18-1.x86_64 [egreshko@meimei ~]$ uname -a Linux meimei 3.12.5-200.fc19.x86_64 #1 SMP Tue Dec 17 22:21:14 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
On the F20 VM .....
[egreshko@f20f ~]$ uname -a Linux f20f.greshko.com 3.12.5-302.fc20.x86_64 #1 SMP Tue Dec 17 20:42:32 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
So, with the same rpm from Oracle that you have, I have no problem.....
I guess you're 100% certain your host system is running a 64bit F19? :-) :-) Or, maybe, there is a bug in VBox running on your F19 system that fails to detect your hardware/OS is 64 bit?
F20 as a guest, so ~/.VirtualBox/VBoxVMs/<guest>/Logs/VBox.log https://www.virtualbox.org/wiki/Bugtracker
poma
On Tue, 2013-12-24 at 09:41 +0800, Ed Greshko wrote:
FWIW..... On my F19 system....
[egreshko@meimei ~]$ rpm -qa | fgrep VirtualBox VirtualBox-4.3-4.3.6_91406_fedora18-1.x86_64 [egreshko@meimei ~]$ uname -a Linux meimei 3.12.5-200.fc19.x86_64 #1 SMP Tue Dec 17 22:21:14 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
$ uname -a Linux mongoliad.gregandeva.net 3.11.10-200.fc19.x86_64 #1 SMP Mon Dec 2 20:28:03 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux $ rpm -qa | fgrep VirtualBox VirtualBox-4.3-4.3.6_91406_fedora18-1.x86_64
maybe, there is a bug in VBox running on your F19 system that fails to detect your hardware/OS is 64 bit?
That's certainly what it looks like. I may also try an older version of VB, or update my kernel to the most recent version.
--Greg
On 12/24/13 13:27, Greg Woods wrote:
On Tue, 2013-12-24 at 09:41 +0800, Ed Greshko wrote:
FWIW..... On my F19 system....
[egreshko@meimei ~]$ rpm -qa | fgrep VirtualBox VirtualBox-4.3-4.3.6_91406_fedora18-1.x86_64 [egreshko@meimei ~]$ uname -a Linux meimei 3.12.5-200.fc19.x86_64 #1 SMP Tue Dec 17 22:21:14 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
$ uname -a Linux mongoliad.gregandeva.net 3.11.10-200.fc19.x86_64 #1 SMP Mon Dec 2 20:28:03 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux $ rpm -qa | fgrep VirtualBox VirtualBox-4.3-4.3.6_91406_fedora18-1.x86_64
maybe, there is a bug in VBox running on your F19 system that fails to detect your hardware/OS is 64 bit?
That's certainly what it looks like. I may also try an older version of VB, or update my kernel to the most recent version.
I guess I'd be interested in the output of
cat /proc/cpuinfo
On 12/24/13 14:06, Ed Greshko wrote:
I guess I'd be interested in the output of
cat /proc/cpuinfo
And maybe
lshw -C processor | grep width lscpu | grep "CPU op-mode"
for completeness. :-)
Who knows how VBox goes about making its decisions.
BTW, everything worked fine for me on earlier F19 kernels.
On Tue, 2013-12-24 at 14:40 +0800, Ed Greshko wrote:
On 12/24/13 14:06, Ed Greshko wrote:
I guess I'd be interested in the output of
cat /proc/cpuinfo
8 repetitions of:
processor : 7
vendor_id : GenuineIntel cpu family : 6 model : 60 model name : Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz stepping : 3 microcode : 0x16 cpu MHz : 800.000 cache size : 8192 KB physical id : 0 siblings : 8 core id : 3 cpu cores : 4 apicid : 7 initial apicid : 7 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 fma cx16 xtpr pdcm pcid sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm ida arat epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid bogomips : 6995.85 clflush size : 64 cache_alignment : 64 address sizes : 39 bits physical, 48 bits virtual power management:
And maybe
lshw -C processor | grep width lscpu | grep "CPU op-mode"
[root@mongoliad mythtv]# lshw -C processor | grep width width: 64 bits [root@mongoliad mythtv]# lscpu | grep "CPU op-mode" CPU op-mode(s): 32-bit, 64-bit
--Greg
On 12/24/13 23:59, Greg Woods wrote:
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 fma cx16 xtpr pdcm pcid sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm ida arat epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid bogomips : 6995.85 clflush size : 64 cache_alignment : 64 address sizes : 39 bits physical, 48 bits virtual power management:
And maybe
lshw -C processor | grep width lscpu | grep "CPU op-mode"
[root@mongoliad mythtv]# lshw -C processor | grep width width: 64 bits [root@mongoliad mythtv]# lscpu | grep "CPU op-mode" CPU op-mode(s): 32-bit, 64-bit
Time to file a "bugzilla" with Oracle. :-)
-
Chris Murphy -
David -
Ed Greshko -
Fernando Cassia -
Greg Woods -
Joe Zeff -
Klaus-Peter Schrage -
poma -
Rick Stevens -
SternData