I've installed VirtualBox from YaST, specifically the packages: virtualbox-ose virtualbox-ose-guest-tools virtualbox-ose-kmp-default (This is the default kernel) xorg-x11-driver-virtualbox-ose (Mouse & Video driver) Calling 'virtualbox' at a terminal does nothing. I do not find anything that looks like an executable for this program, so something seems to be missing. Besides two additional kernels of the same size as the default ("debug" and "trace"), there is another, much smaller "kernel" called virtualbox-ose-kmp- pae, and maybe that is what is missing. But if someone can confirm that, I would feel much easier in making the experiment. The descriptions of these files in the Software Manager are less helpful than usual. -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 07 February 2009 10:14:24 Stan Goodman wrote:
I've installed VirtualBox from YaST, specifically the packages: virtualbox-ose virtualbox-ose-guest-tools virtualbox-ose-kmp-default (This is the default kernel) xorg-x11-driver-virtualbox-ose (Mouse & Video driver)
Calling 'virtualbox' at a terminal does nothing. I do not find anything that looks like an executable for this program, so something seems to be missing.
I use the 'closed' version of VirtualBox so things might be different, but see what happens when you open a terminal and type: "VirtualBox -h." The virtualization engine is located in /usr/bin. HTH -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 07 February 2009 17:14:24 Stan Goodman wrote:
Calling 'virtualbox' at a terminal does nothing. I do not find anything that looks like an executable for this program, so something seems to be missing.
Note that the executable is called VirtualBox, with a capital V and B
Besides two additional kernels of the same size as the default ("debug" and "trace"), there is another, much smaller "kernel" called virtualbox-ose-kmp- pae, and maybe that is what is missing. But if someone can confirm that, I would feel much easier in making the experiment. The descriptions of these files in the Software Manager are less helpful than usual.
Those aren't kernels, they are kernel modules (kmp = kernel module package) and you need to have the one installed that matches your running kernel. Anders -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 07 February 2009 20:31:11 Anders Johansson wrote:
On Saturday 07 February 2009 17:14:24 Stan Goodman wrote:
Calling 'virtualbox' at a terminal does nothing. I do not find anything that looks like an executable for this program, so something seems to be missing.
Note that the executable is called VirtualBox, with a capital V and B
Besides two additional kernels of the same size as the default ("debug" and "trace"), there is another, much smaller "kernel" called virtualbox-ose-kmp- pae, and maybe that is what is missing. But if someone can confirm that, I would feel much easier in making the experiment. The descriptions of these files in the Software Manager are less helpful than usual.
Those aren't kernels, they are kernel modules (kmp = kernel module package) and you need to have the one installed that matches your running kernel.
The default module works. A bit of googling has established that one called
PEA is a physical address extension needed for HD address space larger than
4GB, which, at the moment, I will not need.
What threw me about the case of the executable file is that there are a
number of other related virtualbox files in all lower case, and I jumped at
the fallacious conclusion that the executable would be like that too. Mea
Culpa, some day I'll learn.
When the introductory screen came up, it informed me of that a new release
had been issued, v2.1.2. But I know that this is the release number of the
commercial version; are they saying that it has now been released as a
freebie?
I've made a virtual Win2k. When it comes up, it displays an error message:
On Saturday 07 February 2009 12:35:07 Stan Goodman wrote:
I've made a virtual Win2k. When it comes up, it displays an error message:
What does it want?
When you state that you made a 'virtual Win2k,' do you mean that you used thte VirtualBox manager to create a Win2k config file, or did you create a virtual disk image (vdi) file in which you can install the OS? I'm guessing that you created the virtual disk, but didn't install the OS into it yet. You do have the installer disks, don't you? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 07 February 2009 23:24:34 Jay C Vollmer wrote:
On Saturday 07 February 2009 12:35:07 Stan Goodman wrote:
I've made a virtual Win2k. When it comes up, it displays an error message:
What does it want?
When you state that you made a 'virtual Win2k,' do you mean that you used thte VirtualBox manager to create a Win2k config file, or did you create a virtual disk image (vdi) file in which you can install the OS?
I wish I could answer that question. The mechanics of this program are still very foggy to me. It asked me what virtual machine I wanted to make, and I filled in the blanks, mainly how much RAM I wanted, whether dynamically sized or fixed, and how much HD space. I don't remember a question like the one you ask.
I'm guessing that you created the virtual disk, but didn't install the OS into it yet. You do have the installer disks, don't you?
Disks? You mean Windows disk? But from reading about the program I understood that VB is an emulator, and doesn't require Windows disks, but uses a set of translation tables to convert Windows calls to go through the host machine. That's why it can support only a small set of guest machines. Have I misunderstood this? -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
I wish I could answer that question. The mechanics of this program are still very foggy to me. It asked me what virtual machine I wanted to make, and I filled in the blanks, mainly how much RAM I wanted, whether dynamically sized or fixed, and how much HD space. I don't remember a question like the one you ask.
I'm guessing that you created the virtual disk, but didn't install the OS into it yet. You do have the installer disks, don't you?
Disks? You mean Windows disk? But from reading about the program I understood that VB is an emulator, and doesn't require Windows disks, but uses a set of translation tables to convert Windows calls to go through the host machine. That's why it can support only a small set of guest machines. Have I misunderstood this?
Completely. VirtualBox is not Wine... you're mixing them up. Wine provides the mapping for the Windows api to Linux. VirtualBox provides you a virtual computer. If you set up a Win2K image, you still need to install Windows 2000 from your master disks into that virtual machine. A virtual machine like VirtualBox, VMWare, MS Virtual PC and so on, are all basically a software implementation of a real computer. It allows you to emulate the _hardware_ of a real computer and install a supported OS onto that emulated hardware. So, in that VirtualBox, you can install Win2k, WinXP, Vista, pretty much any Linux variation, OpenSolaris and a few other OS types. You must install from the master disks or ISOs, just as if you were installing on a real machine. Does that clear it up a bit? C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Stan Goodman pecked at the keyboard and wrote:
On Saturday 07 February 2009 23:24:34 Jay C Vollmer wrote:
I've made a virtual Win2k. When it comes up, it displays an error message:
What does it want? When you state that you made a 'virtual Win2k,' do you mean that you used
On Saturday 07 February 2009 12:35:07 Stan Goodman wrote: thte VirtualBox manager to create a Win2k config file, or did you create a virtual disk image (vdi) file in which you can install the OS?
I wish I could answer that question. The mechanics of this program are still very foggy to me. It asked me what virtual machine I wanted to make, and I filled in the blanks, mainly how much RAM I wanted, whether dynamically sized or fixed, and how much HD space. I don't remember a question like the one you ask.
I'm guessing that you created the virtual disk, but didn't install the OS into it yet. You do have the installer disks, don't you?
Disks? You mean Windows disk? But from reading about the program I understood that VB is an emulator,
I emulates the hardware _not_ the software, *you* need to supply the software. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 07 February 2009 14:28:15 Stan Goodman wrote:
Disks? You mean Windows disk? But from reading about the program I understood that VB is an emulator, and doesn't require Windows disks, but uses a set of translation tables to convert Windows calls to go through the host machine. That's why it can support only a small set of guest machines. Have I misunderstood this?
VB isn't an 'emulator,' it's virtualization software. It creates a virtual computer in software on the host system (Linux in this case) the guest OS (Windows in this case) thinks that the virtual system is real and interacts with it as if it were. The hypervisor software on the host talks to the real hardware and makes the virtual machine behave as though it were real. To make this work, you must create a virtual disk and virtual network interfaces, a virtual sound card and a virtual video controller. The setup wizard in VB steps you though these. You'll recall that you were asked to select the size of the virtualized RAM and the size of the virtual hard disk. The others are assigned default settings. Once the virtual machine is created by the wizard, you must install the guest OS into it as though it were a real computer. HTH -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
For Stan's convenience, here are detailed instructions: (This is assuming that VirtualBox is already installed.) 1) Add the users who will be using the virtual machine to the vboxusers group either by using YaST, groupmod, or by editing the /etc/group file. 2) create the virtual system profile by starting the VB Manager and completing the following steps: 2a) click the "New" button. This will start the wizard which will guide you through the process. In the wizard window, click the "Next" button. 2b) Give the profile for the virtual machine a name and set its OS type and version. When finished, click the "Next" button. 2c) Set the memory size of the virtual machine by adjusting the slider in the wizard. When finished, click the "Next" button. 2d) Set the location and size of the virtual disk (vdi file.) When finished, click the "Next" button. 2e) Check the "Summary" window for errors and if all is correct, click the "Finish" button. 3) At this point, all the setup is completed and the guest OS (Win2K in this case) may be installed. Place the installer CD or DVD into the CD/DVD drive (If desired, iso images may be used in place of actual CDs or DVDs.) Start the installation process by Opening the VB manager again, selecting the profile you've created, and clicking on the "Start" button. Continue the normal installation into the virtual disk as though the virtual machine were real. 4) When installation is complete 'reboot' the virtual machine. 5) If desired, set up your 'shared folders' in the VB manager and map them into your newly installed virtual machine. 6) In order to improve the integration of the virtual machine with your host system, install the 'guest additions' onto your virtual disk. I think that this procedure is complete, but I welcome corrections from the regulars - and even the irregulars ;-P -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 07 February 2009 12:35:07 Stan Goodman wrote:
I've made a virtual Win2k. When it comes up, it displays an error message:
Stan : "Windows 2000" is just name -- it means nothing. Think of it like you just purchased a new computer that has "Windows 2000" logo without an operating system (OS), and now it is your job to install an OS. There is very good (but old) article on VirtualBox for openSUSE users (Susers): http://forgeftp.novell.com/lfl/.html/virtualbox.html -- -Alexey Eromenko "Technologov" -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 07 February 2009 23:56:55 Alexey Eremenko wrote:
On Saturday 07 February 2009 12:35:07 Stan Goodman wrote:
I've made a virtual Win2k. When it comes up, it displays an error message:
Stan : "Windows 2000" is just name -- it means nothing. Think of it like you just purchased a new computer that has "Windows 2000" logo without an operating system (OS), and now it is your job to install an OS.
There is very good (but old) article on VirtualBox for openSUSE users (Susers): http://forgeftp.novell.com/lfl/.html/virtualbox.html
-- -Alexey Eromenko "Technologov"
Буду прочитать его завтра утром. Спасибо. -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
I've installed VirtualBox from YaST, specifically the packages: virtualbox-ose virtualbox-ose-guest-tools virtualbox-ose-kmp-default (This is the default kernel) xorg-x11-driver-virtualbox-ose (Mouse & Video driver)
Calling 'virtualbox' at a terminal does nothing. I do not find anything that looks like an executable for this program, so something seems to be missing.
Besides two additional kernels of the same size as the default ("debug" and "trace"), there is another, much smaller "kernel" called virtualbox-ose-kmp- pae, and maybe that is what is missing. But if someone can confirm that, I would feel much easier in making the experiment. The descriptions of these files in the Software Manager are less helpful than usual.
-- Stan Goodman Qiryat Tiv'on Israel I could not get the ose version of VirtualBox to behave itself so installed
Hi Stan, On Saturday 07 February 2009 16:14:24 Stan Goodman wrote: the version from here. http://www.virtualbox.org/ This installs easy. I only had to use Yast to make sure the default kernel was installed. Then used the Start Button/System/Emulator and VirtualBox is there. You must also run this from the command line. /etc/init.d/vboxdrv setup Now you should be able to use VirtualBox -- Clive. http://homepage.ntlworld.com/c.rogers/ Fighting for darker skies. From 52:26ºN 01:27ºW (Coventry, UK) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 07 February 2009 22:34:22 Clive Rogers wrote:
Hi Stan,
On Saturday 07 February 2009 16:14:24 Stan Goodman wrote:
I've installed VirtualBox from YaST, specifically the packages: virtualbox-ose virtualbox-ose-guest-tools virtualbox-ose-kmp-default (This is the default kernel) xorg-x11-driver-virtualbox-ose (Mouse & Video driver)
Calling 'virtualbox' at a terminal does nothing. I do not find anything that looks like an executable for this program, so something seems to be missing.
Besides two additional kernels of the same size as the default ("debug" and "trace"), there is another, much smaller "kernel" called virtualbox-ose-kmp- pae, and maybe that is what is missing. But if someone can confirm that, I would feel much easier in making the experiment. The descriptions of these files in the Software Manager are less helpful than usual.
-- Stan Goodman Qiryat Tiv'on Israel
I could not get the ose version of VirtualBox to behave itself so installed the version from here.
This installs easy. I only had to use Yast to make sure the default kernel was installed. Then used the Start Button/System/Emulator and VirtualBox is there.
You must also run this from the command line. /etc/init.d/vboxdrv setup Now you should be able to use VirtualBox
Oh, that's something new. If it's necessary, it's apparently meant to be a secret from users. I was able to get VB installed automatically; as you may have read, I was unable to run it afterward until I got the case right. But even now, it's unable to run the virtual Win2k that I made, because it can't find a boot drive (which appears to be yet another secret). It's late now, after midenight, but in the morning I will look to see if the setup file exists here.
-- Clive.
http://homepage.ntlworld.com/c.rogers/
Fighting for darker skies. From 52:26ºN 01:27ºW (Coventry, UK)
-- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hi Stan, On Saturday 07 February 2009 20:18:14 Stan Goodman wrote:
On Saturday 07 February 2009 22:34:22 Clive Rogers wrote: <snip>
I could not get the ose version of VirtualBox to behave itself so installed the version from here.
This installs easy. I only had to use Yast to make sure the default kernel was installed. Then used the Start Button/System/Emulator and VirtualBox is there.
You must also run this from the command line. /etc/init.d/vboxdrv setup Now you should be able to use VirtualBox
Oh, that's something new. If it's necessary, it's apparently meant to be a secret from users.
No its not a secret. As you run VB it will come up on screen in an information box.
I was able to get VB installed automatically; as you may have read, I was unable to run it afterward until I got the case right. But even now, it's unable to run the virtual Win2k that I made, because it can't find a boot drive (which appears to be yet another secret).
As to your Win2K. Have you installed Windows 2000 ? You must have the disk to install the operating system once you have set up the virtual (vdi). Once you tell VB what OS you want to install then put in the cd and it should now start to read and install the OS just as though you were doing a normal install. -- Clive. http://homepage.ntlworld.com/c.rogers/ Fighting for darker skies. From 52:26ºN 01:27ºW (Coventry, UK) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 09 February 2009 12:20:54 Clive Rogers wrote:
Hi Stan,
On Saturday 07 February 2009 20:18:14 Stan Goodman wrote:
On Saturday 07 February 2009 22:34:22 Clive Rogers wrote:
<snip>
I could not get the ose version of VirtualBox to behave itself so installed the version from here.
This installs easy. I only had to use Yast to make sure the default kernel was installed. Then used the Start Button/System/Emulator and VirtualBox is there.
You must also run this from the command line. /etc/init.d/vboxdrv setup Now you should be able to use VirtualBox
Oh, that's something new. If it's necessary, it's apparently meant to be a secret from users.
It had not come up here. Following your suggestion: Poblano:/usr/bin # /etc/init.d/vboxdrv setup Stopping VirtualBox kernel module done Removing old VirtualBox netflt kernel module done Removing old VirtualBox kernel module done Recompiling VirtualBox kernel module failed (Look at /var/log/vbox-install.log to find out what went wrong) Poblano:/usr/bin # cd /var/log Poblano:/var/log # vi vbox-install.log ***** Here is what the log says: Makefile:170: *** Error: unable to find the include directory for your current Linux kernel. Specify KERN_INCL=<directory> and run Make again. Stop. ***** What exactly does the above want me to do?
No its not a secret. As you run VB it will come up on screen in an information box.
I was able to get VB installed automatically; as you may have read, I was unable to run it afterward until I got the case right. But even now, it's unable to run the virtual Win2k that I made, because it can't find a boot drive (which appears to be yet another secret).
As to your Win2K. Have you installed Windows 2000 ?
I have a disk, but have not yet installed it.
You must have the disk to install the operating system once you have set up the virtual (vdi).
Once you tell VB what OS you want to install then put in the cd and it should now start to read and install the OS just as though you were doing a normal install.
That's clear. I hope I get to the point where I need to do that. So far, I am doubtful.
-- Clive.
http://homepage.ntlworld.com/c.rogers/
Fighting for darker skies. From 52:26ºN 01:27ºW (Coventry, UK)
-- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2009-02-09 at 12:26 +0200, Stan Goodman wrote:
It had not come up here. Following your suggestion:
Poblano:/usr/bin # /etc/init.d/vboxdrv setup Stopping VirtualBox kernel module done Removing old VirtualBox netflt kernel module done Removing old VirtualBox kernel module done Recompiling VirtualBox kernel module failed (Look at /var/log/vbox-install.log to find out what went wrong) Poblano:/usr/bin # cd /var/log Poblano:/var/log # vi vbox-install.log
***** Here is what the log says: Makefile:170: *** Error: unable to find the include directory for your current Linux kernel. Specify KERN_INCL=<directory> and run Make again. Stop. *****
What exactly does the above want me to do?
Do you have package kernel-source installed, and have it initialized? - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkmQIvcACgkQtTMYHG2NR9XbkgCggkWNm+n+1w3mY6KkwBQSSgvf avkAoJekjDt+UL01taKrx1hydcRtsmlZ =wjA4 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Stan Goodman schreef: (snip)
It had not come up here. Following your suggestion:
Poblano:/usr/bin # /etc/init.d/vboxdrv setup Stopping VirtualBox kernel module done Removing old VirtualBox netflt kernel module done Removing old VirtualBox kernel module done Recompiling VirtualBox kernel module failed (Look at /var/log/vbox-install.log to find out what went wrong) Poblano:/usr/bin # cd /var/log Poblano:/var/log # vi vbox-install.log
***** Here is what the log says: Makefile:170: *** Error: unable to find the include directory for your current Linux kernel. Specify KERN_INCL=<directory> and run Make again. Stop. *****
What exactly does the above want me to do?
Install the kernel sources. Apparently the installation tries to recompile the kernel modules and in order to do that it needs the kernel source. The instruction "Specify ... etc" erroneously supposes you already did that and put them in a non-standard spot. Stupid computers ... :-) -- Jos van Kan registered Linux user #152704 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 09 February 2009 14:35:01 Jos van Kan wrote:
Stan Goodman schreef: (snip)
It had not come up here. Following your suggestion:
Poblano:/usr/bin # /etc/init.d/vboxdrv setup Stopping VirtualBox kernel module done Removing old VirtualBox netflt kernel module done Removing old VirtualBox kernel module done Recompiling VirtualBox kernel module failed (Look at /var/log/vbox-install.log to find out what went wrong) Poblano:/usr/bin # cd /var/log Poblano:/var/log # vi vbox-install.log
***** Here is what the log says: Makefile:170: *** Error: unable to find the include directory for your current Linux kernel. Specify KERN_INCL=<directory> and run Make again. Stop. *****
What exactly does the above want me to do?
Install the kernel sources. Apparently the installation tries to recompile the kernel modules and in order to do that it needs the kernel source. The instruction "Specify ... etc" erroneously supposes you already did that and put them in a non-standard spot. Stupid computers ... :-)
I am not dense enough to blame my own ignorance on the "stupid computer". Knowing that an automatic update replaced my kernel only a few days ago, I chose to d/l kernel-source. YaST then asked for the installation disk, and installed from there. I did not notice that there was anything about downloading and applying incremental changes, and I can only hope that it did this and I didn't notice. Does this sound to be what should have happened, and it is safe to retry the integration of the VB kernel modules? YaST says the installed kernel-source is now 2.6.27.7-9.1.
-- Jos van Kan registered Linux user #152704
-- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Stan Goodman schreef: (snip)
Knowing that an automatic update replaced my kernel only a few days ago, I chose to d/l kernel-source. YaST then asked for the installation disk, and installed from there. I did not notice that there was anything about downloading and applying incremental changes, and I can only hope that it did this and I didn't notice. Does this sound to be what should have happened, and it is safe to retry the integration of the VB kernel modules? YaST says the installed kernel-source is now 2.6.27.7-9.1.
-- Jos van Kan registered Linux user #152704
Do from the command line 1) uname -a (this gives you the current kernel version) then 2) ls -l /usr/src/linux (this gives you the version of the source you have) and check if the two versions are the same. If not, update the source to the right version. If they are, retry the integration of the VB modules. -- Jos van Kan registered Linux user #152704 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 09 February 2009 16:02:46 Jos van Kan wrote:
Stan Goodman schreef: (snip)
Knowing that an automatic update replaced my kernel only a few days ago, I chose to d/l kernel-source. YaST then asked for the installation disk, and installed from there. I did not notice that there was anything about downloading and applying incremental changes, and I can only hope that it did this and I didn't notice. Does this sound to be what should have happened, and it is safe to retry the integration of the VB kernel modules? YaST says the installed kernel-source is now 2.6.27.7-9.1.
-- Jos van Kan registered Linux user #152704
Do from the command line 1) uname -a
(this gives you the current kernel version) then
2) ls -l /usr/src/linux
stan@Poblano:~> uname -a Linux Poblano 2.6.27.7-9-default #1 SMP 2008-12-04 18:10:04 +0100 x86_64 x86_64 x86_64 GNU/Linux stan@Poblano:~> stan@Poblano:~> ls -l /usr/src/linux lrwxrwxrwx 1 root root 16 2009-02-09 12:11 /usr/src/linux -> linux-2.6.27.7-9 stan@Poblano:~> They are both the same. YaST, however, shows that the installed kernel files (including kernel-source) are 2.6.27.7-9.1, which is not quite the same.
(this gives you the version of the source you have) and check if the two versions are the same. If not, update the source to the right version.
If they are, retry the integration of the VB modules.
-- Jos van Kan registered Linux user #152704
-- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Stan Goodman schreef: (snip)
stan@Poblano:~> uname -a Linux Poblano 2.6.27.7-9-default #1 SMP 2008-12-04 18:10:04 +0100 x86_64 x86_64 x86_64 GNU/Linux stan@Poblano:~> stan@Poblano:~> ls -l /usr/src/linux lrwxrwxrwx 1 root root 16 2009-02-09 12:11 /usr/src/linux -> linux-2.6.27.7-9 stan@Poblano:~>
They are both the same. YaST, however, shows that the installed kernel files (including kernel-source) are 2.6.27.7-9.1, which is not quite the same.
Hm. Strange. Maybe there are more sources in /usr/src? Anyway, the symlink "linux" is pointing to the right directory, so I'd say: go for it. -- Jos van Kan registered Linux user #152704 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Clive Rogers said the following on 02/09/2009 05:20 AM:
As to your Win2K. Have you installed Windows 2000 ? You must have the disk to install the operating system once you have set up the virtual (vdi).
It would be nice if that wasn't the case. Disks, I mean. If you have a dual-boot system the instead of installing a _virtual_ disk you just point at the already installed partition that holds the Windows. -- "Motivation is always in direct proportion to the level of expectation." -- Denis Waitley -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
* Anton Aylward
It would be nice if that wasn't the case. Disks, I mean.
If you have a dual-boot system the instead of installing a _virtual_ disk you just point at the already installed partition that holds the Windows.
Is it possible to point it to a networked computer? tks, -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://counter.li.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, 10 Feb 2009 00:07:45 Anton Aylward wrote:
Clive Rogers said the following on 02/09/2009 05:20 AM:
As to your Win2K. Have you installed Windows 2000 ? You must have the disk to install the operating system once you have set up the virtual (vdi).
It would be nice if that wasn't the case. Disks, I mean.
If you have a dual-boot system the instead of installing a _virtual_ disk you just point at the already installed partition that holds the Windows.
With VMWare it is possible to have it run Windows from a physical partition (i.e. an existing installation) rather than a VM, but I don't know about VirtualBox. Somewhere on the VMWare site (from memory, perhaps buried amongst the FAQ's) there are instructions on how to do this. It requires some manual manipulation of both VMWare and Windows. The biggest thing is that the Windows hal.dll is probably the wrong one for VMware, particularly if you normally run the multiprocessor hal (e.g. for an SMP box or for a Core2 Duo/Quad processor like my laptop) or a non-Intel processor. VMWare normally emulates a single-core Intel CPU. You need to: 1. Unpack the appropriate hal.dll from the .cab file on the installation disk (renaming it to avoid overwriting the currently installed hal.dll) 2. Modify boot.ini to always show the boot menu when booting Windows 3. Add an additional boot line and add parameters to each boot line to specify which hal.dll to load. You then need to remember which hal.dll is the right one to load when booting Windows normally or via VMWare. YMMV. I know the steps but I haven't actually gotten around to trying it out yet. I'm told that it does work but it hasn't exactly been high on my list of priorities to test... -- =================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au ===================================================
Stan Goodman wrote:
I've installed VirtualBox from YaST, specifically the packages: virtualbox-ose virtualbox-ose-guest-tools virtualbox-ose-kmp-default (This is the default kernel) xorg-x11-driver-virtualbox-ose (Mouse & Video driver)
Calling 'virtualbox' at a terminal does nothing. I do not find anything that looks like an executable for this program, so something seems to be missing.
Besides two additional kernels of the same size as the default ("debug" and "trace"), there is another, much smaller "kernel" called virtualbox-ose-kmp- pae, and maybe that is what is missing. But if someone can confirm that, I would feel much easier in making the experiment. The descriptions of these files in the Software Manager are less helpful than usual.
I also use the download from the virtualbox site. Never had any problems and it works great. Direct downloads i586/x86_64: 11.0 http://download.virtualbox.org/virtualbox/2.1.2/VirtualBox-2.1.2_41885_openS... http://download.virtualbox.org/virtualbox/2.1.2/VirtualBox-2.1.2_41885_openS... 11.0 http://download.virtualbox.org/virtualbox/2.1.2/VirtualBox-2.1.2_41885_openS... http://download.virtualbox.org/virtualbox/2.1.2/VirtualBox-2.1.2_41885_openS... -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
I use this script of mine to get virtual box started on Suse 10.3 khawar@linux-suse:/mnt/320_2/bin> cat atrc_virtual_box.sh #!/bin/sh modprobe vboxdrv sleep 1 chmod 777 /dev/vboxdrv khawar@linux-suse:/mnt/320_2/bin> I hope this helps. Khawar David C. Rankin wrote:
Stan Goodman wrote:
I've installed VirtualBox from YaST, specifically the packages: virtualbox-ose virtualbox-ose-guest-tools virtualbox-ose-kmp-default (This is the default kernel) xorg-x11-driver-virtualbox-ose (Mouse & Video driver)
Calling 'virtualbox' at a terminal does nothing. I do not find anything that looks like an executable for this program, so something seems to be missing.
Besides two additional kernels of the same size as the default ("debug" and "trace"), there is another, much smaller "kernel" called virtualbox-ose-kmp- pae, and maybe that is what is missing. But if someone can confirm that, I would feel much easier in making the experiment. The descriptions of these files in the Software Manager are less helpful than usual.
I also use the download from the virtualbox site. Never had any problems and it works great. Direct downloads i586/x86_64:
11.0
http://download.virtualbox.org/virtualbox/2.1.2/VirtualBox-2.1.2_41885_openS... http://download.virtualbox.org/virtualbox/2.1.2/VirtualBox-2.1.2_41885_openS...
11.0
http://download.virtualbox.org/virtualbox/2.1.2/VirtualBox-2.1.2_41885_openS... http://download.virtualbox.org/virtualbox/2.1.2/VirtualBox-2.1.2_41885_openS...
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
David C. Rankin pecked at the keyboard and wrote:
Stan Goodman wrote:
I've installed VirtualBox from YaST, specifically the packages: virtualbox-ose virtualbox-ose-guest-tools virtualbox-ose-kmp-default (This is the default kernel) xorg-x11-driver-virtualbox-ose (Mouse & Video driver)
Calling 'virtualbox' at a terminal does nothing. I do not find anything that looks like an executable for this program, so something seems to be missing.
Besides two additional kernels of the same size as the default ("debug" and "trace"), there is another, much smaller "kernel" called virtualbox-ose-kmp- pae, and maybe that is what is missing. But if someone can confirm that, I would feel much easier in making the experiment. The descriptions of these files in the Software Manager are less helpful than usual.
I also use the download from the virtualbox site. Never had any problems and it works great. Direct downloads i586/x86_64:
11.0
http://download.virtualbox.org/virtualbox/2.1.2/VirtualBox-2.1.2_41885_openS... http://download.virtualbox.org/virtualbox/2.1.2/VirtualBox-2.1.2_41885_openS...
11.0
http://download.virtualbox.org/virtualbox/2.1.2/VirtualBox-2.1.2_41885_openS... http://download.virtualbox.org/virtualbox/2.1.2/VirtualBox-2.1.2_41885_openS...
Also change the usbfs line in /etc/fstab to the following if you want to use the usb sybsystem. xxxx=(vboxusers gid number) mine is 1000. usbfs /proc/bus/usb usbfs noauto,mode=664,gid=xxxx 0 0 -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 08 February 2009 16:11:33 Ken Schneider wrote:
David C. Rankin pecked at the keyboard and wrote:
I also use the download from the virtualbox site. Never had any problems and it works great. Direct downloads i586/x86_64:
Since several have recommended installing from the VirtualBox website, I uninstalled the VB-oce that I had installed previously, and downloaded (v2.1.2) from there. Although it seems that nobody else has experienced any glitch with this, =;-/8, things did not go quite as smoothly here. The installation was aborted because of a failed dependency, namely "pam-devel", which I have no clue how to find. YaST knows nothing about it. If someone knows what and where it is, please raise your hand. -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 02/09/2009 02:12 AM, Stan Goodman wrote:
Since several have recommended installing from the VirtualBox website, I uninstalled the VB-oce that I had installed previously, and downloaded (v2.1.2) from there.
Although it seems that nobody else has experienced any glitch with this, =;-/8, things did not go quite as smoothly here. The installation was aborted because of a failed dependency, namely "pam-devel", which I have no clue how to find. YaST knows nothing about it. If someone knows what and where it is, please raise your hand.
Perhaps your subject is a typo. You are looking for pam-devel, which I show as being in the DVD. Yast should find it with no problems. -- Joe Morris Registered Linux user 231871 running openSUSE 11.1 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 08 February 2009 22:24:54 Joe Morris wrote:
On 02/09/2009 02:12 AM, Stan Goodman wrote:
Since several have recommended installing from the VirtualBox website, I uninstalled the VB-oce that I had installed previously, and downloaded (v2.1.2) from there.
Although it seems that nobody else has experienced any glitch with this, =;-/8, things did not go quite as smoothly here. The installation was aborted because of a failed dependency, namely "pam-devel", which I have no clue how to find. YaST knows nothing about it. If someone knows what and where it is, please raise your hand.
Perhaps your subject is a typo. You are looking for pam-devel, which I show as being in the DVD. Yast should find it with no problems.
-- Joe Morris Registered Linux user 231871 running openSUSE 11.1 x86_64
In fact I found it by googling, and installed it without difficulty. VirtualBox is now installed, and I can read Alexey's article to learn how to go further. Thanks, All... -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Stan Goodman pecked at the keyboard and wrote:
On Sunday 08 February 2009 16:11:33 Ken Schneider wrote:
David C. Rankin pecked at the keyboard and wrote:
I also use the download from the virtualbox site. Never had any problems and it works great. Direct downloads i586/x86_64:
Since several have recommended installing from the VirtualBox website, I uninstalled the VB-oce that I had installed previously, and downloaded (v2.1.2) from there.
Although it seems that nobody else has experienced any glitch with this, =;-/8, things did not go quite as smoothly here. The installation was aborted because of a failed dependency, namely "pam-devel", which I have no clue how to find. YaST knows nothing about it. If someone knows what and where it is, please raise your hand.
It is on the install DVD and on the oss community repo. Perhaps you mis-typed your search string in Yast, try again. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Ken Schneider wrote
11.0
http://download.virtualbox.org/virtualbox/2.1.2/VirtualBox-2.1.2_41885_openS... http://download.virtualbox.org/virtualbox/2.1.2/VirtualBox-2.1.2_41885_openS...
11.0
http://download.virtualbox.org/virtualbox/2.1.2/VirtualBox-2.1.2_41885_openS... http://download.virtualbox.org/virtualbox/2.1.2/VirtualBox-2.1.2_41885_openS...
Also change the usbfs line in /etc/fstab to the following if you want to use the usb sybsystem. xxxx=(vboxusers gid number) mine is 1000.
usbfs /proc/bus/usb usbfs noauto,mode=664,gid=xxxx 0 0
Ken: Just out of curiosity - do I have it right? This was already existing in my fstab. none /proc/bus/usb usbfs devgid=109,devmode=664 0 0 Do I need to add the line you added as well? -- kai www.perfectreign.com || www.filesite.org bis zum bitteren Ende -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Kai Ponte pecked at the keyboard and wrote:
Ken Schneider wrote
11.0
http://download.virtualbox.org/virtualbox/2.1.2/VirtualBox-2.1.2_41885_openS... http://download.virtualbox.org/virtualbox/2.1.2/VirtualBox-2.1.2_41885_openS...
11.0
http://download.virtualbox.org/virtualbox/2.1.2/VirtualBox-2.1.2_41885_openS... http://download.virtualbox.org/virtualbox/2.1.2/VirtualBox-2.1.2_41885_openS...
Also change the usbfs line in /etc/fstab to the following if you want to use the usb sybsystem. xxxx=(vboxusers gid number) mine is 1000.
usbfs /proc/bus/usb usbfs noauto,mode=664,gid=xxxx 0 0
Ken:
Just out of curiosity - do I have it right? This was already existing in my fstab.
none /proc/bus/usb usbfs devgid=109,devmode=664 0 0
Do I need to add the line you added as well?
No. Which group does 109 point to? It needs to point to the vboxusers group for usb devices to show up. This is with the version from Sun, the ose version does not support usb. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Am Samstag 07 Februar 2009 17:14:24 schrieb Stan Goodman:
I've installed VirtualBox from YaST, specifically the packages: virtualbox-ose virtualbox-ose-guest-tools virtualbox-ose-kmp-default (This is the default kernel) xorg-x11-driver-virtualbox-ose (Mouse & Video driver)
You need virtualbox-ose and virtualbox-ose-kmp-default (or another kmp depending from your kernel) for the the host machine. Install virtualbox-ose using yast or zypper and the right kmp RPM will be chosen automatically. The other RPMs are for openSUSE guest machines only and are optional.
Calling 'virtualbox' at a terminal does nothing. I do not find anything that looks like an executable for this program, so something seems to be missing.
The executeable is VirtualBox with big V and B.
Besides two additional kernels of the same size as the default ("debug" and "trace"), there is another, much smaller "kernel" called virtualbox-ose-kmp- pae, and maybe that is what is missing. But if someone can confirm that, I would feel much easier in making the experiment. The descriptions of these files in the Software Manager are less helpful than usual.
No experiments with kmps neccessary, when you use yast or zypper for installation. Herbert -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (17)
-
Alexey Eremenko -
Anders Johansson -
Anton Aylward -
Carlos E. R. -
Clayton -
Clive Rogers -
David C. Rankin -
Herbert Graeber -
Jay C Vollmer -
Joe Morris -
Jos van Kan -
Kai Ponte -
Ken Schneider -
Khawar Nehal -
Patrick Shanahan -
Rodney Baker -
Stan Goodman