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?
I wonder how do you have played with Haiku 7 years ago, the project started in late-2001 AFAIK 
It was called BeOS back then.
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 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.
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?
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.
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.
Awesome, that’s the driver! Thanks for pointing this out, Urias. Looks like I’ve got some testing to do when I get home…
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
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
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 ;) )
[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.1sits 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.
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!
VMware Workstation supports bridging existing host network adapters and share physical disk drives and USB devices with a virtual machine.In addition,it can simulate disk drives.It can mount an existing ISO image file into a virtual optical disc drive so that the virtual machine sees it as a real one.
http://www.passforsure.co/VCP5-DCV.html
http://www.pass4suredumps.com/70-410.html
I just the VMware certification exam with full marks and now am doing my nest exam Cisco exam 640-911 and want to certified myself in both VMware and cisco .
http://dumps4free.com/640-911-exam-questions-pdf-vce.html