problem with linux 2.6.16

algor: that's a bit few info, isn't it?! none can help with that :P

anyways, same problem here. but to be precise: the drivers DO compile, but insmod fails:
Code: 
     Compiling Parallels Workstation 2.1 drivers...
     Drivers have been compiled successfully.
     Installing drivers...
     Starting drivers...
hex: start offset no good
Loading Parallels Workstation 2.1 hypervisor ...
Loading Parallels Workstation 2.1 vm-main ...
insmod: error inserting '/usr/lib/parallels/drivers/drv_main/vm-main.o': -1 Operation not permitted
 Can not load vm-main module.
Parallels Workstation drivers were successfully configured
and compiled but cannot be started (insmod command failed).
Run 'dmesg' command for more information.

dmesg spits out this:
Code: 
[29822] Device /dev/hypervisor registered with 10.60
[29822] parallels Hypervisor 2.1-1670 initialized.
[29831] No salt specified! (/usr/lib/parallels/drivers/drv_main/vmmain.c:55)
the hypervisor.o loaded fine.
 
edit:

damn... absolutely same problem with 2.6.15.7... i start to think this is not a kernel problem... so some info about this system if it helps:
Portage 2.1_pre7-r3 (default-linux/x86/2006.0, gcc-3.4.5, glibc-2.3.6-r3, 2.6.15-archck7 i686)
=================================================================
System uname: 2.6.15-archck7 i686 AMD Athlon(tm) XP 1800+
Gentoo Base System version 1.12.0_pre16
ccache version 2.3 [enabled]
dev-lang/python: 2.4.2-r1
sys-apps/sandbox: 1.2.17
sys-devel/autoconf: 2.13, 2.59-r7
sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1
sys-devel/binutils: 2.16.1-r1
sys-devel/libtool: 1.5.22
virtual/os-headers: 2.6.11-r3
ACCEPT_KEYWORDS="x86 ~x86"
AUTOCLEAN="yes"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-march=athlon-xp -O2 -pipe -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
..rest is only gentoo specific
Click to expand...
 
Not to criticise intensions here, but keeping up with incremental kernel changes is not as easy as it used to be - so be a little patient. You folks have two of the fastest kernel replacement distros around, and SuSE modifies them a lot to boot. The meaning of a 2.6.xx has changed a lot from say 2.4.xx in that serious changes are done that can interfere with virtualizers. It has just about wiped Win4Lin out of existence trying to keep up. I depend on compatibility with Parallels, so I turn down kernel upgrades to SuSE 10. I have no idea why they are upgrading, and they don't really tell without forcing me to interpret a long list of detailed patches.
 
Please run
$ head -c 16 /dev/urandom
and
$ head -c 16 /dev/urandom | hexdump -sb
and paste here the result
 
Last edited:
this problem appears with esr-hexdump only

there are two ways you may fix this bug
1) install util-linux with more traditional hexdump
2) remove -sb parameter from hexdump in /usr/lib/parallels/autostart/drivers_start
 
tgrogan: I partly agree. If this where a production system i wouldn't update the kernel as soon a new version hits kernel.org.. NTARS it would be then. But as said, it turned out it hadn't been a kernel problem

Negative said:
this problem appears with esr-hexdump only

there are two ways you may fix this bug
1) install util-linux with more traditional hexdump
2) remove -sb parameter from hexdump in /usr/lib/parallels/autostart/drivers_start
Click to expand...

thx Negative!
1) hasn't been the way to go as i didn't change my util-linux version for the last 3 months or something, but 2) indeed fixed it ;)
No idea why that error occured now, i had parallels up and running a month ago and no changes to util linux since then

Regards!
 
algor said:
I can't compile the modules with linux 2.6.16 (suse 10.1 beta 8)
Click to expand...

Suse beta 8 has its own bugs! It is still in beta for a good reason!

Go to the novell site and navigate to the open suse site, they have the known bugs listed.

don
 
You must log in or register to reply here.
Back
Top