Now that v11.0 is out, I’m looking at going all out and upgrading to 64 bit and XEN.
Is it worth it?
Am I buying more trouble?
Are there any problems with running 32bit apps?
I’m particularly interested in virtualizing WinXP so that my wife can have her photo editor available without a reboot.
X86-64 is proven 20 % faster all around and makes better use of your memory.
At the install, Yast > filter > Patterns > load the 32-bit Runtime Library and you have both.
And you can compile 32-bit apps too.
“Am I buying more trouble?”
Only a few, and there are work-arounds to get them running. Someone is sure to help.
XEN – Sorry I’m not up on that feature
Virtualizing – Try Vmware Server and/or VirtualBox; both work well. With VirtualBox don’t use the rpms; get the non-OSE version from VirtualBox download & get full use of the usb hub.
Hope that helps:)
I run 64-bit openSUSE and don’t have much problems running 32-bit apps. I had a little trouble compiling wine, but I found a helpful guide on their wiki that straitened that out.
I notice that the OS is much snappier and responsive and can’t believe I haven’t been using it!
I run OS11_x64 as well just as F9_x64 mainly because I can and I like the challenge (it used to be) to make it work. Truth be told I hardly notice any performance gain at all in using x64 on my laptop just memory hungry apps / photo / video editing could theoretically be faster on the down end x64 does use more memory then the same x86 install.
In comparison my Arch_x86 install is WAY faster then F9/OS11 on x64 so much performance is gained in tuning the system.
that being said I think x64 these days is just as easy as x86 with near to none hassles or drawbacks. FF3 works out of the box and x86 apps are easily installed (i do like fedora’s multi architecture way of doing this and running different versions of the same app next to eachother).
as for virtualisation I would second going for Virtualbox 6.0.2 if it is just for running windows locally. it is fast, great, small, lightweight and free. It just uses NAT networking.
stefan
LGLisle schrieb:
> Now that v11.0 is out, I’m looking at going all out and upgrading to 64
> bit and XEN.
>
> Is it worth it?
In my experience, the only advantage of a 64 bit system is that it can
use more than 2 GB of RAM properly. If you don’t have that much RAM,
you won’t notice much difference.
> I’m particularly interested in virtualizing WinXP so that my wife can
> have her photo editor available without a reboot.
I found VirtualBox much easier to handle than XEN for that purpose.
HTH
T.
–
Tilman Schmidt
Phoenix Software GmbH
Bonn, Germany
snakedriver wrote:
> LGLisle;1820805 Wrote:
>> Now that v11.0 is out, I’m looking at going all out and upgrading to 64
>> bit and XEN.
>>
>> Is it worth it?
>> Am I buying more trouble?
>> Are there any problems with running 32bit apps?
>>
>>
>> I’m particularly interested in virtualizing WinXP so that my wife can
>> have her photo editor available without a reboot.
>
> X86-64 is proven 20 % faster all around and makes better use of
> your memory.
>
> At the install, Yast > filter > Patterns > load the 32-bit Runtime
> Library and you have both.
> And you can compile 32-bit apps too.
>
> “Am I buying more trouble?”
> Only a few, and there are work-arounds to get them running. Someone is
> sure to help.
>
> XEN – Sorry I’m not up on that feature
>
> Virtualizing – Try Vmware Server and/or VirtualBox; both work well.
> With VirtualBox don’t use the rpms; get the non-OSE version from
> VirtualBox download & get full use of the usb hub.
>
> Hope that helps:)
>
>
Do you mean “don’t use the rpms [from openSuSE]” ?
After a problem trying to install the VB non-OSE rpm on 10.3 a while
back, I used the openSuse OSE version. On installing openSuSE 11.0, I
installed the OSE (1.5.6) version, then removed it, downloaded and
installed the VB closed-source openSuSE 10.3 (1.6.2) rpm version, which
appears to be running fine without any editing. I haven’t tried
anything serious nor accessing a USB device though, as I haven’t
migrated anything yet - just have a test VM.
–
PeeGee
Asus M2V-MX SE, AMD 64X2 3800+, openSuSE 10.3 x86-64/XP Home dual boot
Asus M2NPV-VM, AMD LE1640, openSuSE 11.0 x86-64/XP Home dual boot
I’m on 64bit as well. If you’re also interested in multimedia, especially encoding and stuff, 64bit can be 15% faster than 32 bit.
I’ve been using 64 bit Open SuSE for over a year. I have not encountered any problems related to being in 64 bit.
Just been using OpenSuse 11 x64 for a few weeks and work great no problems at all
PeeGee schrieb:
> snakedriver wrote:
>>
>> Virtualizing – Try Vmware Server and/or VirtualBox; both work well.
>> With VirtualBox don’t use the rpms; get the non-OSE version from
>> VirtualBox download & get full use of the usb hub.
>
> Do you mean “don’t use the rpms [from openSuSE]” ?
Yep, that’s what he meant.
> After a problem trying to install the VB non-OSE rpm on 10.3 a while
> back, I used the openSuse OSE version. On installing openSuSE 11.0, I
> installed the OSE (1.5.6) version, then removed it, downloaded and
> installed the VB closed-source openSuSE 10.3 (1.6.2) rpm version, which
> appears to be running fine without any editing. I haven’t tried
> anything serious nor accessing a USB device though, as I haven’t
> migrated anything yet - just have a test VM.
Accessing USB devices connected to the host from the VM is the most
important feature distinguishing the non-OSE from the OSE version.
As long as you don’t need that, you’ll probably be fine with the OSE
version from Sun.
A serious drawback of the openSUSE RPM wrt those from Sun (both OSE
and non-OSE) is that it deliberately disables the possibility to
recompile the kernel module via “/etc/init.d/vboxdrv setup”. So if you
ever want to use a non-SUSE kernel, the SUSE RPM is not for you.
HTH
T.
–
Tilman Schmidt t.schmidt@phoenixsoftware.de
Phoenix Software GmbH www.phoenixsoftware.de
Adolf-Hombitzer-Str. 12 Amtsgericht Bonn HRB 2934
53227 Bonn, Germany Geschäftsführer: W. Grießl