sometime the VMWare host on linux probably wont recognize the USB devices. this problem didnt happened during my time with previous release of ubuntu (hardy, gutsy).
collected this simple solution through the Ubuntu forum.
sudo gedit /etc/fstab
Then, add this line:
# USB for vmware/vbox
none /proc/bus/usb usbfs devgid=46,devmode=664 0 0
then the usb will be connected like a charm.
just go through
VM>Removable Devices>USB Device.
Showing posts with label ubuntu. Show all posts
Showing posts with label ubuntu. Show all posts
Monday, July 27, 2009
Friday, July 17, 2009
new direction of the blog
i think it is time for me to change the direction for the blog.
from now on i will use it for jotting down my troubleshooting in Linux, Mac or Windows.
the first one will be how to sync the fast pacing seconds in vmware guest in Ubuntu Intrepid host.
Got the solution from another blogger.
basically the kernel send the value of processor time to vm kernel.
in some core 2 duo it will make the seconds go faster than the host itself. It cant be controlled even by the vm tools installed in the vm. Just need to put extra line in the vm setting.
quoting from the blog itself
"Turns out that my processors automatically scale down (Core 2 Quads), and so I needed to edit /etc/vmware/config and add the line host.cpukHz = 2400000 which is the correct one for my 2.4GHz CPU. After this, I restarted the vmware-server service, and the time is perfectly synced.
I was able to confirm the kHz number to use by running burnp6 from the cpuburn package on all four cores and looking at /proc/cpuinfo to see what speed it reached."
from now on i will use it for jotting down my troubleshooting in Linux, Mac or Windows.
the first one will be how to sync the fast pacing seconds in vmware guest in Ubuntu Intrepid host.
Got the solution from another blogger.
basically the kernel send the value of processor time to vm kernel.
in some core 2 duo it will make the seconds go faster than the host itself. It cant be controlled even by the vm tools installed in the vm. Just need to put extra line in the vm setting.
quoting from the blog itself
"Turns out that my processors automatically scale down (Core 2 Quads), and so I needed to edit /etc/vmware/config and add the line host.cpukHz = 2400000 which is the correct one for my 2.4GHz CPU. After this, I restarted the vmware-server service, and the time is perfectly synced.
I was able to confirm the kHz number to use by running burnp6 from the cpuburn package on all four cores and looking at /proc/cpuinfo to see what speed it reached."
Subscribe to:
Posts (Atom)