On Fri, 25 Jan 2013 20:36:03 +0000, Larsed wrote:
> First of all: Thank you both wolfi and Jim Henderson for all your help
> and kind suggestions! I really appreciate it!
No problem, Lars. 
> I’m sorry about my misunderstanding of rpm -qi, you see I never had used
> it before and only had met “i” in connection with install. When I tried
> it on an ordinary package, for instance emacs I saw the amount of
> information I could get.
The switch is position sensitive. -i first means "install’ and if -q is
first, then it’s a modifier to the query command.
> I hesitate to download and install it once again from the repo you
> suggested Jim, not that I do not think that you don’t mean well and know
> what you talk about!! I stress that. You see I’ve got so many
> indications that my processor-MoBo doesn’t supply virtualization.
That certainly is possible - in which case it seems that 64-bit guests
are not going to be possible in your setup.
> The only confirmation I have concerning the architecture is the one I’ve
> got from rpm -qa that said
> VirtualBox-4.2-4.2.6_82870_openSUSE114-1.x86_64 and the fact that I
> downloaded it from the “amd64” link and still have got it in my /home.
> Your suggestion should in a way propose that Sun/Oracle doesn’t know how
> they name their software. Of course that is possible.
Either I missed that you had downloaded from their amd64 link, or that is
new information. My goal was to ensure that you had indeed installed a
x86_64 release of the software rather than the i686 release.
> So, probably my hardware isn’t able to supply hardware 64-bit
> virtualization. If it wasn’t for my experience with VMWorkstation 6.01
> in openSUSE10.3_x86-64 on my twin machine:question:?? Still running BTW
> and capable of creating 64-bit virtual guest?? On machinery that should
> make it impossible?
Virtualization can be implemented in a number of ways, so it is certainly
possible that VMware has implemented something where you’re not getting
full paravirtualization but something implemented in software that’s not
implemented in VirtualBox.
> So Jim, this my full explanation to why I hesitate to give Virtualbox
> one more try, it’s not unthankfulness! -I think there is a difference
> between Sun/Oracle’s VirtualBox and VMWare’s applications. At least
> concerning this problem.
No problem, it was unclear to me that you were looking for advice on
switching to VMware as well. I have used VMware extensively and do
really like it - but the price tag on VirtualBox is hard to beat for
personal use, and as my VMware workstation licenses were tied to a former
employer, I switched as I couldn’t afford the workstation license and
needed multiple-snapshot functionality that Player doesn’t provide.
> Again I must say I am very grateful for your sharing these problems with
> me! You really helped me think and continue trying, even if not with
> Virtualbox.
In the end, that you got a working solution is the important thing. And
I’m glad you did.
Jim
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
On Fri, 25 Jan 2013 20:36:03 +0000, Larsed wrote:
> First of all: Thank you both wolfi and Jim Henderson for all your help
> and kind suggestions! I really appreciate it!
>
> I’m sorry about my misunderstanding of rpm -qi, you see I never had used
> it before and only had met “i” in connection with install. When I tried
> it on an ordinary package, for instance emacs I saw the amount of
> information I could get.
>
> A few answers to wolfi
>> You got “Virtualbox is not installed” because it’s spelled VirtualBox
> I know;), I think I mentioned no matter how I spelled it (including
> VirtualBox). And to Jim as well:
> The reason I got “no reply” from rpm -qi could be that the Oracle
> package doesn’t contain any information that responds to “i”.
> The only confirmation I have concerning the architecture is the one I’ve
> got from rpm -qa that said
> VirtualBox-4.2-4.2.6_82870_openSUSE114-1.x86_64 and the fact that I
> downloaded it from the “amd64” link and still have got it in my /home.
> Your suggestion should in a way propose that Sun/Oracle doesn’t know how
> they name their software. Of course that is possible.
>
> I hesitate to download and install it once again from the repo you
> suggested Jim, not that I do not think that you don’t mean well and know
> what you talk about!! I stress that. You see I’ve got so many
> indications that my processor-MoBo doesn’t supply virtualization. wolfi
> as one above, I have no doubt he knows his processor and it
> capabilities. But parallell I had another thread up in
> forums.virtualbox, and the answers from there indicate that as long as I
> don’t have the svm- or amd-v- flags on my processor it doesn’t support
> hardware virtualization. -I made one more excavation in my two BIOSes
> and could still find no Virtualization setting no where. And made one
> more excursion on the internet to search for information regarding my
> two identical processors. Found very little more than I wrote initially
> but found that Athlon 64 3000+ socket 939 is a very insufficient
> information:
> The Athlon 3000+ had many revisions, somewhere I read that the ones
> after “D” should have hardware virtualization. But I can’t find out what
> model or release year that one should have.
> When I scrolled down the Wikipedia-list I’m almost certain that the
> ‘Venice’ release with socket 939 are the ones I’ve got in my two “twin”
> machines and according to ‘Newegg.com - AMD Athlon 64 3000+ Venice
> 1.8GHz Socket 939 Single-Core Processor ADA3000BPBOX’
> (http://www.newegg.com/Product/Product.aspx?Item=N82E16819103537) it
> doesn’t support virtualization. The first one I found that does support
> virtualization is the ‘Orleans’ release with socket AM2.
>
> So, probably my hardware isn’t able to supply hardware 64-bit
> virtualization. If it wasn’t for my experience with VMWorkstation 6.01
> in openSUSE10.3_x86-64 on my twin machine:question:?? Still running BTW
> and capable of creating 64-bit virtual guest?? On machinery that should
> make it impossible?
>
> From wolfi above, and also from virtualbox forum I got the suggestions
> to try VMWare Player (that I previously thought only could “play”
> prefabricated VM’s. How wrong I was). I thought I should give that a
> final try. I only had struggled with this problem for four days:|.
>
> And what do you know, it works!! With VMWare Player I can install and
> run virtual 64-bit guests. Tried both Ubuntu12.10_x86-64 and
> linuxMint14_x86-64. Both installed and smothly with Player on the same
> OS and hardware that earlier with VirtualBox reported “This kernel
> requires an x86-64 CPU, but only detected an i686 CPU…”
>
> Well it’s a mystery, but consistent with my previous experiences with
> VMWare’s Workstation 6.01 in openSUSE on the same hardware as my present
> openSUSE12.2_x86-64.
>
> So Jim, this my full explanation to why I hesitate to give Virtualbox
> one more try, it’s not unthankfulness! -I think there is a difference
> between Sun/Oracle’s VirtualBox and VMWare’s applications. At least
> concerning this problem.
>
> Again I must say I am very grateful for your sharing these problems with
> me! You really helped me think and continue trying, even if not with
> Virtualbox.
>
> My best regards
>
> Lars
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
