Maker Pro
Maker Pro

VirtualBox beware

M

MooseFET

My computer is almost working again after installing VirtualBox.

Make sure you back up and have a second way to boot before installing
it onto a Linux box. It plugs in a kernal mod. that seems not to work
on my machine.
 
J

JeffM

MooseFET said:
My computer is almost working again after installing VirtualBox.

Make sure you back up and have a second way to boot
before installing it onto a Linux box.
It plugs in a kernal mod. that seems not to work on my machine.

What was the original reason for the addition
and what (if anything) will you try instead?
 
M

MooseFET

I don't know MooseFET's reason for installing it. He should
have said what Linux kernel or distribution he installed it
against and what the kernel mod was related to, and what op
system he installed virtually, if he got that far. (I've seen,
but not read, some complaints apparently re VirtualBox with Vista.)

Yes I should have said all those things but I was tired, upset and
generally POed.

SuSE 10.1 64 bit on an x86-64

The kernal module that says "VirtualBox" as it is starting up was the
guy that seemed to be the main problem. It would get that far on a
boot and stop at that point. I "had to" upgrade my OS to SuSE-10.3 64
bit to get the machine working again.

I sort of have it working. There was a trick to getting it so that I
could wathc www.youtube.com videos that I did on the earlier version
that I wish I could remember. That is the one thing that is still not
really working right.


My purpose was to boot a windows 98 program and have it be able to
work with the serial ports. I use bochs all the time to run Win98
stuff and those things that don't need to get to the serial ports work
just fine if a bit slow.

For DOS stuff I use "dosemu". My dos programs can get to the serial
port and don't even know anything funny is going on. Unfortunately,
the serial port stuff in bochs is not as good as dosemu.

If I wasn't doing anything else, I might solve some of these problems
but right now I have other software to work on.



Back in March I installed InnoTek VirtualBox 1.5.6 on my Fedora
Core 7 system (which already has Xen in the distribution) with
no problems at all. I'd gotten tired of keeping an old Windows
system around to run tax software on. I created a 10 GB virtual
drive, a 567 MB virtual memory, and installed Windows 2000 and
Turbotax and some other software, with few problems. (An error in
MS W2K disk drivers requires a minor workaround.) All in all it
runs faster and far better this way than the old used-once-a-year
W2K system did. There's a webpage athttp://digg.com/linux_unix
[1] that has a few comments on virtual systems.
-jiw

[1]http://digg.com/linux_unix/5_reasons_why_you_should_use_VirtualBox_in...
 
J

JosephKK

I don't know MooseFET's reason for installing it. He should
have said what Linux kernel or distribution he installed it
against and what the kernel mod was related to, and what op
system he installed virtually, if he got that far. (I've seen,
but not read, some complaints apparently re VirtualBox with Vista.)

Yes I should have said all those things but I was tired, upset and
generally POed.

SuSE 10.1 64 bit on an x86-64

The kernal module that says "VirtualBox" as it is starting up was the
guy that seemed to be the main problem. It would get that far on a
boot and stop at that point. I "had to" upgrade my OS to SuSE-10.3 64
bit to get the machine working again.

I sort of have it working. There was a trick to getting it so that I
could wathc www.youtube.com videos that I did on the earlier version
that I wish I could remember. That is the one thing that is still not
really working right.


My purpose was to boot a windows 98 program and have it be able to
work with the serial ports. I use bochs all the time to run Win98
stuff and those things that don't need to get to the serial ports work
just fine if a bit slow.

For DOS stuff I use "dosemu". My dos programs can get to the serial
port and don't even know anything funny is going on. Unfortunately,
the serial port stuff in bochs is not as good as dosemu.

If I wasn't doing anything else, I might solve some of these problems
but right now I have other software to work on.



Back in March I installed InnoTek VirtualBox 1.5.6 on my Fedora
Core 7 system (which already has Xen in the distribution) with
no problems at all. I'd gotten tired of keeping an old Windows
system around to run tax software on. I created a 10 GB virtual
drive, a 567 MB virtual memory, and installed Windows 2000 and
Turbotax and some other software, with few problems. (An error in
MS W2K disk drivers requires a minor workaround.) All in all it
runs faster and far better this way than the old used-once-a-year
W2K system did. There's a webpage athttp://digg.com/linux_unix
[1] that has a few comments on virtual systems.
-jiw

[1]http://digg.com/linux_unix/5_reasons_why_you_should_use_VirtualBox_in...

AFAIK suse 10.0 and 10.1 are really flaky. Clone your system out and
get it running right, then upgrade the clone to 10.2 or 10.3.
Stabilize again if needed. Notice: the at install upgrades are huge
now >1GB.
 
M

MooseFET

Yes I should have said all those things but I was tired, upset and
generally POed.
SuSE 10.1 64 bit on an x86-64
The kernal module that says "VirtualBox" as it is starting up was the
guy that seemed to be the main problem. It would get that far on a
boot and stop at that point. I "had to" upgrade my OS to SuSE-10.3 64
bit to get the machine working again.
I sort of have it working. There was a trick to getting it so that I
could wathcwww.youtube.comvideos that I did on the earlier version
that I wish I could remember. That is the one thing that is still not
really working right.
My purpose was to boot a windows 98 program and have it be able to
work with the serial ports. I use bochs all the time to run Win98
stuff and those things that don't need to get to the serial ports work
just fine if a bit slow.
For DOS stuff I use "dosemu". My dos programs can get to the serial
port and don't even know anything funny is going on. Unfortunately,
the serial port stuff in bochs is not as good as dosemu.
If I wasn't doing anything else, I might solve some of these problems
but right now I have other software to work on.
Back in March I installed InnoTek VirtualBox 1.5.6 on my Fedora
Core 7 system (which already has Xen in the distribution) with
no problems at all. I'd gotten tired of keeping an old Windows
system around to run tax software on. I created a 10 GB virtual
drive, a 567 MB virtual memory, and installed Windows 2000 and
Turbotax and some other software, with few problems. (An error in
MS W2K disk drivers requires a minor workaround.) All in all it
runs faster and far better this way than the old used-once-a-year
W2K system did. There's a webpage athttp://digg.com/linux_unix
[1] that has a few comments on virtual systems.
-jiw
[1]http://digg.com/linux_unix/5_reasons_why_you_should_use_VirtualBox_in...

AFAIK suse 10.0 and 10.1 are really flaky. Clone your system out and
get it running right, then upgrade the clone to 10.2 or 10.3.
Stabilize again if needed. Notice: the at install upgrades are huge
now >1GB.


I have upgraded to 10.3 64 bit and now have just about everything
working again. I just have to make it so that virmidi loads at boot
and I'll even have my playing of midi music in steam explosions
working again.
 
J

JosephKK

My computer is almost working again after installing VirtualBox.
Make sure you back up and have a second way to boot before installing it
onto a Linux box. It plugs in a kernal mod. that seems not to work on my
machine.
What was the original reason for the addition and what (if anything)
will you try instead?
I don't know MooseFET's reason for installing it. He should
have said what Linux kernel or distribution he installed it
against and what the kernel mod was related to, and what op
system he installed virtually, if he got that far. (I've seen,
but not read, some complaints apparently re VirtualBox with Vista.)
Yes I should have said all those things but I was tired, upset and
generally POed.
SuSE 10.1 64 bit on an x86-64
The kernal module that says "VirtualBox" as it is starting up was the
guy that seemed to be the main problem. It would get that far on a
boot and stop at that point. I "had to" upgrade my OS to SuSE-10.3 64
bit to get the machine working again.
I sort of have it working. There was a trick to getting it so that I
could wathcwww.youtube.comvideos that I did on the earlier version
that I wish I could remember. That is the one thing that is still not
really working right.
My purpose was to boot a windows 98 program and have it be able to
work with the serial ports. I use bochs all the time to run Win98
stuff and those things that don't need to get to the serial ports work
just fine if a bit slow.
For DOS stuff I use "dosemu". My dos programs can get to the serial
port and don't even know anything funny is going on. Unfortunately,
the serial port stuff in bochs is not as good as dosemu.
If I wasn't doing anything else, I might solve some of these problems
but right now I have other software to work on.
Back in March I installed InnoTek VirtualBox 1.5.6 on my Fedora
Core 7 system (which already has Xen in the distribution) with
no problems at all. I'd gotten tired of keeping an old Windows
system around to run tax software on. I created a 10 GB virtual
drive, a 567 MB virtual memory, and installed Windows 2000 and
Turbotax and some other software, with few problems. (An error in
MS W2K disk drivers requires a minor workaround.) All in all it
runs faster and far better this way than the old used-once-a-year
W2K system did. There's a webpage athttp://digg.com/linux_unix
[1] that has a few comments on virtual systems.
-jiw

AFAIK suse 10.0 and 10.1 are really flaky. Clone your system out and
get it running right, then upgrade the clone to 10.2 or 10.3.
Stabilize again if needed. Notice: the at install upgrades are huge
now >1GB.


I have upgraded to 10.3 64 bit and now have just about everything
working again. I just have to make it so that virmidi loads at boot
and I'll even have my playing of midi music in steam explosions
working again.

Cool, so ring back after a few months with a reliability report.
 
M

MooseFET

My computer is almost working again after installing VirtualBox.
Make sure you back up and have a second way to boot before installing it
onto a Linux box. It plugs in a kernal mod. that seems not to work on my
machine.
What was the original reason for the addition and what (if anything)
will you try instead?
I don't know MooseFET's reason for installing it. He should
have said what Linux kernel or distribution he installed it
against and what the kernel mod was related to, and what op
system he installed virtually, if he got that far. (I've seen,
but not read, some complaints apparently re VirtualBox with Vista.)
Yes I should have said all those things but I was tired, upset and
generally POed.
SuSE 10.1 64 bit on an x86-64
The kernal module that says "VirtualBox" as it is starting up was the
guy that seemed to be the main problem. It would get that far on a
boot and stop at that point. I "had to" upgrade my OS to SuSE-10.3 64
bit to get the machine working again.
I sort of have it working. There was a trick to getting it so that I
could wathcwww.youtube.comvideosthat I did on the earlier version
that I wish I could remember. That is the one thing that is still not
really working right.
My purpose was to boot a windows 98 program and have it be able to
work with the serial ports. I use bochs all the time to run Win98
stuff and those things that don't need to get to the serial ports work
just fine if a bit slow.
For DOS stuff I use "dosemu". My dos programs can get to the serial
port and don't even know anything funny is going on. Unfortunately,
the serial port stuff in bochs is not as good as dosemu.
If I wasn't doing anything else, I might solve some of these problems
but right now I have other software to work on.
Back in March I installed InnoTek VirtualBox 1.5.6 on my Fedora
Core 7 system (which already has Xen in the distribution) with
no problems at all. I'd gotten tired of keeping an old Windows
system around to run tax software on. I created a 10 GB virtual
drive, a 567 MB virtual memory, and installed Windows 2000 and
Turbotax and some other software, with few problems. (An error in
MS W2K disk drivers requires a minor workaround.) All in all it
runs faster and far better this way than the old used-once-a-year
W2K system did. There's a webpage athttp://digg.com/linux_unix
[1] that has a few comments on virtual systems.
-jiw
[1]http://digg.com/linux_unix/5_reasons_why_you_should_use_VirtualBox_in...
AFAIK suse 10.0 and 10.1 are really flaky. Clone your system out and
get it running right, then upgrade the clone to 10.2 or 10.3.
Stabilize again if needed. Notice: the at install upgrades are huge
now >1GB.
I have upgraded to 10.3 64 bit and now have just about everything
working again. I just have to make it so that virmidi loads at boot
and I'll even have my playing of midi music in steam explosions
working again.

Cool, so ring back after a few months with a reliability report.

I will.
That's if the wife doesn't shoot me for playing my Ennio Morricone
music through my now working virmidi. :)
 
Top