[adamvs]

I have a iMac I use for Fusion 360 and would like to install a copy of Path Pilot on this machine to use as a backplot test before I take gcode to the shop. I installed the latest VirtualBox; when I went to install Ubuntu and PP for the disk .. it would not recognize it as a boot-able disk?! The optical drive was the first search in the boot list on VirtualBox. The weird thing was when I went to BootChamp to restart in Windows ( this machine runs Bootcamp ) .. it started the Ubuntu boot sequence - the CD was stolen the optical drive.

Any ideas? Would sure like to get this working.

[cbyrd]

You need to make sure that the virtual box has the cd drive capture. You could also make an ISO of the disk and then capture that ISO.

[dharmic]

VirtualBox can be a right pain in the tit when it comes to device sharing. You have to make sure that it gives the guest 'ownership' of the CD-ROM instead of the host, and make sure it's looking at the physical drive instead of a virtual ISO drive (which I think is the default config). It can get very confusing and annoying.

If you can't get it to work, another option is to create an ISO rip of the PP CD-ROM (plenty of instructionals out in goggle land), and load that into VB as the virtual CD drive.

:edit: hah, beaten by a whisker.

[adamvs]

OK, got past this speed bump .. but there is another! When I start the VM the boot is extremely slow takes about 3 minutes to boot! It's got 3 GB of ram, about 50GB of virtual hard drive .. I only gave one CPU out of four.. Is that a problem.

edit: Got it .. I installed 'guest additions' and it's working great now, thanks!

[dharmic]

Good to hear you got it working.

I would have installed guest additions just for the screen resolution etc anyway. Kinda surprised that it made a difference on boot times though.

VMs are a lot nicer than working off bootcamp or multiple machines most of the time, but they have their downsides. And, good as VirtualBox is (especially for the price!) it isn't perfect by a long way. I ended up buying VMware Fusion 7 for my Mac but I run Windows and Xubuntu guests all the time for work, and it was worth it - so much smoother integration for just about everything. Version 8, not so much - I ended up spitting the dummy, getting a refund and rolling back to 7.

[adamvs]

Well, it *almost* working . I can see my shared folders on the PP 'file' tab , but I can't see anything in them! Been on the virtual box forum and tried:
sudo adduser operator vboxsf .. and
sudo adduser tormach vboxsf
But nothing! The forum said the 'guest' login name works here, but not sure what that is?

Also tried:

chown operator[colon]operator /media/sf_nc

but still nothing.


I used to use Parallels on the Mac .. it worked pretty well initially, then every 'update' seemed to carry more problems than benefit so I went to BootCamp.

[dharmic]

Are these your normal shared folders or did you create them within virtualbox?

I never had any issues getting those connected up before

[adamvs]

These folders reside on the mac; I just shared them for 'System Preferences' from the Host ( iMac ), figuring that they needed to be shared from the host side. They are also set as shared folders from within VB. I know permissions on the Mac are trickier .. I can see the folder but not the contents. Grrr.. getting close tho.

[dharmic]

From memory, they don't need to be shared from the Mac.

If you set them up as shared to the VirtualBox guest from within the VB machine config, I have a suspicion they can be got at through the file manager on the linux guest. I can't remember whether you have to do it as a network share connection from within Linux though, or whether they automatically appear inside the mount directory as volumes.

:edit: if you can see the shared folder but not the files within, though, I'd hazard a guess that it's a permissions thing on the Mac. That the VirtualBox account (whatever user it's pretending to be) for some reason is getting blocked from the directory listing.

[wtopace]

I would check a few things in this order:

From PathPilot:

1. "df -h" - Did Virtualbox mount the mapped folder share?
   
   • If it's not mounted, mount it from within the guest as root ("mount -t vboxsf sharename mountpoint")
   
   
2. "sudo -i" - Try to ls the directory as root.
   
   • If you can do this, did you assign the correct permissions to the operator user? ("usermod -G vboxsf operator")
   
   

These commands are off the top of my head and may not work =) Best of luck with the Mac, I never have been able to get used to it since the old Mac 2 days when it was a real OS and not a bloated x-window manager that was hard to navigate.

I'm guessing your NIC isn't showing up in your guest - I had to custom compile the kernel mode drivers for the NICs to get them to work from within a VM (both VMware and Virtualbox). If you're a Linux guy, it's no problem at all. If not, it's just a matter of reading a few directions online. The kernel source module is already installed because of the realtime OS.

[adamvs]

OK, got it...finally. Thanks to everybody for helping.
So it's convoluted but basically:
1) the shared folder is mapped into the file system in the '/media' folder.
2) you need to 'sudo ls -l /media/<mapped folder name>. You will see it's owned by root and access from group 'vboxsf'.
3) Add 'operator' to vboxsf with: sudo usermod -a -G vboxsf operator
4) bingo! you now have access to the files in your shared directory.

I'm not a unix/linux guy so hopefully that made sense .. but will be forgotten the moment the 'Reply' button is hit.
'df -h' was a great help because you could see indeed the shared folder was mapped in.

[Tkamsker]

osx is unix - so you are already a unix guy ,..


Gesendet von iPad mit Tapatalk

[adamvs]

osx is unix - so you are already a unix guy ,..

Gesendet von iPad mit Tapatalk

Ha! true! .. and hence, know just enough unix to be dangerous!

[adamvs]

Best of luck with the Mac, I never have been able to get used to it since the old Mac 2 days when it was a real OS.

The 68020 was such a great processor architecture in it's day. Any CS or EE just had to be shaking their head at the x86 architecture of the time.. I mean what a f*ing kludge. Clear case of 'installed base' wins over 'better tech, or way better tech', most of the time. But pre OS X - no threading! OS7 has this hokey deferred task manager, where you could sort of things on about a 10ms boundary .. 'about' being the operative word.

I'm guessing your NIC isn't showing up in your guest - I had to custom compile the kernel mode drivers for the NICs to get them to work from within a VM (both VMware and Virtualbox). If you're a Linux guy, it's no problem at all. If not, it's just a matter of reading a few directions online. The kernel source module is already installed because of the realtime OS.

No NIC yet .. thanks for the heads up, I'll get that going when needed.