Best VM for running Windows Apps in Knoppix

[koolb]

I have been running win7/winXP as a guest (for my day job) with the 32bit (CDs) knoppix kernels just fine for quite a few years.

Due to one box with 6GB, I have been recently been copying the DVD 64-bit /lib/modules into my /lib/modules area of mounted knoppix-data.img to run the 64-bit kernels with the CD iso's.
(messing with grub's knoppix_dir, knoppix_name, kernel and initrd params to help with many knoppix versions in one decent sized boot partition).

For example eg 6.7 is /lib/modules/3.0.4-64 so I can run a the CD's 64 bit kernel with a copy of the DVD's 3.0.4-64 module dir.

To be able to apt-get install any virtualbox requires (for building the dkms parts with linux-headers):

- add the virtualbox-repo to sources.list and ensure the standard knoppix alioth is apt-updated.
- downloading the specific headers for that kernel note that linux-headers-3.0.4-64 is available for 6.7:
apt-get install linux-headers-3.0.4-64

Which has the two need files to modules_prepare the *source*:
/usr/src/linux-headers-3.0.4-64/{.config,Module.symvers}

Yes, you need to build the *source* - this is where I deviated from vbox docs as RTFM didnt work:

- cd /usr/src && apt-get install linux-source-3.0.4
- tar xvf linux-source-3.0.4.*
- cp linux-headers-3.0.4-64/{.config,Module-symvers} linux-source-3.0.4
- mv linux-source-3.0.4 linux-source.3.0.4-64 # not needed - just for consistency
- cd !$ && make oldconfig && make prepare && make modules_prepare
- ln -s linux-source.3.0.4-64 /lib/modules/3.0.4-64/build

This causes a successful install of any 32 bit versions, eg:
apt-get install virtualbox-4.2

And it runs up to starting the VM and you get the dreaded -1912 error because you need a
x86_64 virtualbox-4.2 to go with a 64 bit kernel (their amd64 == x86_64):

dpkg -i virtualbox-4.2_4.2.4-81684~Debian~squeeze_amd64.deb # gives:

Preparing to replace virtualbox-4.2 4.2.4-81684~Debian~squeeze (using virtualbox-4.2_4.2.4-81684~Debian~squeeze_amd64.deb) ...
Stopping VirtualBox kernel modules:.
Unpacking replacement virtualbox-4.2 ...
dpkg: dependency problems prevent configuration of virtualbox-4.2:
 virtualbox-4.2 depends on libc6 (>= 2.6).
 virtualbox-4.2 depends on libcurl3-gnutls (>= 7.16.2-1).
 virtualbox-4.2 depends on libgcc1 (>= 1:4.1.1).
 virtualbox-4.2 depends on libpng12-0 (>= 1.2.13-4).
 virtualbox-4.2 depends on libpython2.6 (>= 2.6).
 virtualbox-4.2 depends on libqt4-network (>= 4:4.5.3).
 virtualbox-4.2 depends on libqt4-opengl (>= 4:4.5.3).
 virtualbox-4.2 depends on libqtcore4 (>= 4:4.6.1).
 virtualbox-4.2 depends on libqtgui4 (>= 4:4.6.2).
 virtualbox-4.2 depends on libsdl1.2debian (>= 1.2.10-1).
 virtualbox-4.2 depends on libssl0.9.8 (>= 0.9.8m-1).
 virtualbox-4.2 depends on libstdc++6 (>= 4.4.0).
 virtualbox-4.2 depends on libx11-6.
 virtualbox-4.2 depends on libxcursor1 (>> 1.1.2).
 virtualbox-4.2 depends on libxext6.
 virtualbox-4.2 depends on libxinerama1.
 virtualbox-4.2 depends on libxml2 (>= 2.7.4).
 virtualbox-4.2 depends on libxmu6.
 virtualbox-4.2 depends on libxt6.
 virtualbox-4.2 depends on zlib1g (>= 1:1.1.4).
 
dpkg: error processing virtualbox-4.2 (--install):
 dependency problems - leaving unconfigured

So my system is 99.9% i386 and I *need* the 64 bit virtualbox to run with my 64-bit kernel.

for kicks I did a dpkg -i -force-depends # as above

And it installs perfectly but of course virtualbox even execute with all the depends missing.
It's a red file that just wont run...

Looks like I am going to need another 64-bit chroot jail and install all those deps unless someone has a better idea. Dont want another 4GB iso to run a 4GB windows to run Citrix - and the new Windows only "security" app to go with it (I have been using straight linux Citrix until a new company windows only proggie is required to log in).

Help!

[kl522]

I have been running win7/winXP as a guest (for my day job) with the 32bit (CDs) knoppix kernels just fine for quite a few years.

Due to one box with 6GB, I have been recently been copying the DVD 64-bit /lib/modules into my /lib/modules area of mounted knoppix-data.img to run the 64-bit kernels with the CD iso's.
(messing with grub's knoppix_dir, knoppix_name, kernel and initrd params to help with many knoppix versions in one decent sized boot partition).

For example eg 6.7 is /lib/modules/3.0.4-64 so I can run a the CD's 64 bit kernel with a copy of the DVD's 3.0.4-64 module dir.

To be able to apt-get install any virtualbox requires (for building the dkms parts with linux-headers):

- add the virtualbox-repo to sources.list and ensure the standard knoppix alioth is apt-updated.
- downloading the specific headers for that kernel note that linux-headers-3.0.4-64 is available for 6.7:
apt-get install linux-headers-3.0.4-64

Which has the two need files to modules_prepare the *source*:
/usr/src/linux-headers-3.0.4-64/{.config,Module.symvers}

Yes, you need to build the *source* - this is where I deviated from vbox docs as RTFM didnt work:

- cd /usr/src && apt-get install linux-source-3.0.4
- tar xvf linux-source-3.0.4.*
- cp linux-headers-3.0.4-64/{.config,Module-symvers} linux-source-3.0.4
- mv linux-source-3.0.4 linux-source.3.0.4-64 # not needed - just for consistency
- cd !$ && make oldconfig && make prepare && make modules_prepare
- ln -s linux-source.3.0.4-64 /lib/modules/3.0.4-64/build

This causes a successful install of any 32 bit versions, eg:
apt-get install virtualbox-4.2

And it runs up to starting the VM and you get the dreaded -1912 error because you need a
x86_64 virtualbox-4.2 to go with a 64 bit kernel (their amd64 == x86_64):

dpkg -i virtualbox-4.2_4.2.4-81684~Debian~squeeze_amd64.deb # gives:

Preparing to replace virtualbox-4.2 4.2.4-81684~Debian~squeeze (using virtualbox-4.2_4.2.4-81684~Debian~squeeze_amd64.deb) ...
Stopping VirtualBox kernel modules:.
Unpacking replacement virtualbox-4.2 ...
dpkg: dependency problems prevent configuration of virtualbox-4.2:
 virtualbox-4.2 depends on libc6 (>= 2.6).
 virtualbox-4.2 depends on libcurl3-gnutls (>= 7.16.2-1).
 virtualbox-4.2 depends on libgcc1 (>= 1:4.1.1).
 virtualbox-4.2 depends on libpng12-0 (>= 1.2.13-4).
 virtualbox-4.2 depends on libpython2.6 (>= 2.6).
 virtualbox-4.2 depends on libqt4-network (>= 4:4.5.3).
 virtualbox-4.2 depends on libqt4-opengl (>= 4:4.5.3).
 virtualbox-4.2 depends on libqtcore4 (>= 4:4.6.1).
 virtualbox-4.2 depends on libqtgui4 (>= 4:4.6.2).
 virtualbox-4.2 depends on libsdl1.2debian (>= 1.2.10-1).
 virtualbox-4.2 depends on libssl0.9.8 (>= 0.9.8m-1).
 virtualbox-4.2 depends on libstdc++6 (>= 4.4.0).
 virtualbox-4.2 depends on libx11-6.
 virtualbox-4.2 depends on libxcursor1 (>> 1.1.2).
 virtualbox-4.2 depends on libxext6.
 virtualbox-4.2 depends on libxinerama1.
 virtualbox-4.2 depends on libxml2 (>= 2.7.4).
 virtualbox-4.2 depends on libxmu6.
 virtualbox-4.2 depends on libxt6.
 virtualbox-4.2 depends on zlib1g (>= 1:1.1.4).
 
dpkg: error processing virtualbox-4.2 (--install):
 dependency problems - leaving unconfigured

So my system is 99.9% i386 and I *need* the 64 bit virtualbox to run with my 64-bit kernel.

for kicks I did a dpkg -i -force-depends # as above

And it installs perfectly but of course virtualbox even execute with all the depends missing.
It's a red file that just wont run...

Looks like I am going to need another 64-bit chroot jail and install all those deps unless someone has a better idea. Dont want another 4GB iso to run a 4GB windows to run Citrix - and the new Windows only "security" app to go with it (I have been using straight linux Citrix until a new company windows only proggie is required to log in).

Help!

I have tried doing what you wanted to do before but I finally gave up, because the amount of libraries needed are just too many, may as well start off with a true 64 bit OS.

If I have such a need, I would run a true 64 bit OS.

If my memory serves me right, VMware will have less problem in this aspect. I don't remember exactly why it was less painful, but I vaguely remember it is able to install 32 bit VMware on 64bit knoppix and run 64 bit guest or something like that.

My preferred choice of virtualization is VirtualBox but I noticed that VirtualBox is weak in a few area. So I also have VMware installed side by side with VirtualBox.