Vmware 5 workstation Network Driver?

Forum thread started by lucas.clemente on Wed, 2006-04-19 11:53

I got Haiku installed on Vmware workstation 5!

It's good to see this again. Last time I played with haiku was in college. (7 years ago).

One little issue,,, are there any network drivers for Haiku in VMware 5?

‹ IRQ conflict Beos R5 Boot CD for BeOS R5 pe? ›

Comments

Vmware 5 workstation Network Driver?

by jeanmarc - 2006-04-19 13:25

I wonder how do you have played with Haiku 7 years ago, the project started in late-2001 AFAIK :)

Vmware 5 workstation Network Driver?

by lucas.clemente - 2006-04-19 13:29

It was called BeOS back then.

Vmware 5 workstation Network Driver?

by umccullough - 2006-04-19 14:34
lucas.clemente wrote:
It was called BeOS back then.

As long as you understand that Haiku is a BeOS-community re-creation of BeOS, and not written by the same corporation... Welcome back!

Currently the netcard in VMWare is unsupported to my knowledge.

If someone wants to step up and write one, I'm sure it would be greatly appreciated by MANY people who are testing Haiku in VMWare these days ;)

Vmware 5 workstation Network Driver?

by imre - 2006-04-19 14:51

VMWare uses by default PCNet II driver and this one is unsupported.

However vmware workstation 5.5 comes also with intel e1000 virtual device that haiku has driver for.

for that you have to modify your *.vmx file manually by adding line:
ethernet0.virtualDev = "e1000"

note that i haven't got network wokring though. It KDL-s w/ recursive_lock_lock error.

Vmware 5 workstation Network Driver?

by j_freeman - 2006-04-19 15:12
imre wrote:
However vmware workstation 5.5 comes also with intel e1000 virtual device that haiku has driver for.

I was having hope for the e1000, but where's the driver? Is it already bundled with Haiku or do I need to grab it off of BeBits?

Vmware 5 workstation Network Driver?

by umccullough - 2006-04-19 15:30
imre wrote:
VMWare uses by default PCNet II driver and this one is unsupported.

However vmware workstation 5.5 comes also with intel e1000 virtual device that haiku has driver for.

for that you have to modify your *.vmx file manually by adding line:
ethernet0.virtualDev = "e1000"

note that i haven't got network wokring though. It KDL-s w/ recursive_lock_lock error.

You should log that at http://haiku-os.org/bugzilla

The SiS900 driver does the same thing on Haiku as I have logged:

http://www.haiku-os.org/bugzilla/show_bug.cgi?id=349

I suspect that if more people knew that VMware supported a network chipset that a driver existed for - that bug would get resolved in a HURRY!

Point out the same information about VMWare possibly being usable with this option when you log the bug, and get a screenshot of the stack crawl to attach it. Once the bug is there - we'll see what happens.

Vmware 5 workstation Network Driver?

by umccullough - 2006-04-19 15:35
j_freeman wrote:
imre wrote:
However vmware workstation 5.5 comes also with intel e1000 virtual device that haiku has driver for.

I was having hope for the e1000, but where's the driver? Is it already bundled with Haiku or do I need to grab it off of BeBits?

i would guess it is this one:

http://svn.berlios.de/viewcvs/haiku/haiku/trunk/src/add-ons/kernel/drivers/network/ipro1000/

and therefore it's probably included in the haiku image.

Vmware 5 workstation Network Driver?

by j_freeman - 2006-04-19 17:41

Awesome, that's the driver! Thanks for pointing this out, Urias. Looks like I've got some testing to do when I get home...

Vmware 5 workstation Network Driver?

by imre - 2006-04-19 17:56

that's correct. 

ifconfig ipro10000 192.168.1.111 up

route add default 192.168.1.254

ping 192.168.1.254

(crash)

i'll file the bug report when i get more time

Vmware 5 workstation Network Driver?

by umccullough - 2006-04-19 18:06
imre wrote:
that's correct. 

ifconfig ipro10000 192.168.1.111 up

route add default 192.168.1.254

ping 192.168.1.254

(crash)

i'll file the bug report when i get more time

oh, Ping doesn't work anyway, ICMP is broke. Try netpositive instead.

I don't think ping is causing the recursive_lock_lock issue, however

pingish

by johndrinkwater - 2006-04-19 22:59
umccullough wrote:
oh, Ping doesn't work anyway, ICMP is broke. Try netpositive instead.

worksforme, so I say kinda broke:
ping 192.168.2.1 sits there waiting forever. If I Ctrl+C, it returns infomation about one packet! 

ping -f 192.168.2.1
.

causes the terminal to flicker as it updates a full stop showing activity. Ctrl+C ing gives me all the packets sent, and stats ( 400 packets, 0% loss ;) )

Re: pingish

by umccullough - 2006-04-19 23:08
[Beta wrote:
"]
umccullough wrote:
oh, Ping doesn't work anyway, ICMP is broke. Try netpositive instead.

worksforme, so I say kinda broke:
ping 192.168.2.1 sits there waiting forever. If I Ctrl+C, it returns infomation about one packet! 

ping -f 192.168.2.1
.

causes the terminal to flicker as it updates a full stop showing activity. Ctrl+C ing gives me all the packets sent, and stats ( 400 packets, 0% loss ;) )

Yes, there's the bug about Ping blocking after first packet - I dont' know if it's ping or ICMP actually...Ill assume ICMP since it hasn't been fixed yet ;)

http://www.haiku-os.org/bugzilla/show_bug.cgi?id=60

So, the recursive_lock_lock issue appears to be something in the kernel - looking at the backtrace from #349 that the SiS900 driver is running into in "get_memory_map"... I believe it's similar for the intel.

ipro1000 works now

by umccullough - 2006-05-01 01:15

If anyone's still wondering - axeld fixed the get_memory_map() function in the kernel so that drivers that rely on this during interrupts can use it without crashing again.

This was resolved in rev 17280 and should allow the ipro1000 and sis900 drivers to work again.

I tested the ipro1000 in vmware, and ping no longer causes KDL. it does hang without receiving a packet, but that is a problem with ping/icmp - not the driver.

I will load netpositive (and maybe firefox) onto a vmware image and try it later... :)

have fun kids!