I had to get my hands dirty recently to migrate some Solaris boxes. While I’m not totally unfamiliar with Solaris zones, the commands slipped my mind since I don’t use it on a day to day basis.
zonecfg -z zonename
select net address=x.x.x.x (where x.x.x.x is the current address)
set address=y.y.y.y (where y.y.y.y is the new address)
end
verify
commit
exit
That’s it. Another quick reference and addition to my own F(**king)M(anual).
While updating my iPhone 3GS to iOS 4, I encountered an error on iTunes saying that my iPhone could not be updated. My phone went into recovery mode after that. This is not the first time I’m doing restore and update with Vmware, so I’m pretty surprise why the update process failed.
A peek into dmesg shows the following -
[52420.444795] usb 2-2: usbfs: interface 2 claimed by ipheth while ‘vmware-vmx’ sets config #4
[52420.460159] usb 2-2: usbfs: process 9345 (vmware-vmx) did not claim interface 2 before use
[52420.460222] usb 2-2: usbfs: process 9345 (vmware-vmx) did not claim interface 2 before use
Linux is now capable of detecting the iPhone over USB natively and automatically via the iPhone for tethering and direct access to the underlying filesystem, so it’s hogging the USB port on the iPhone and denying Vmware of accessing it.
Anyway the solution is simple. Just run
# rmmod ipheth
# dmesg
[52445.922401] usbcore: deregistering interface driver ipheth
[52445.964038] ipheth 2-2:4.2: Apple iPhone USB Ethernet now disconnected
[52491.228075] usb 2-2: reset high speed USB device using ehci_hcd and address 21
[52491.524073] usb 2-2: reset high speed USB device using ehci_hcd and address 21
Linux releases the iPhone. On Vmware, disconnect and connect the iPhone again.
The need for speed is never satiable. I was running Windows XP in Virtualbox with 1 VCPU all these while. Speed was acceptable for me to do my office related stuff like Exchange and Office.
My CPU was a Core2Duo with HyperThread. So technically, I have 4 VCPU to play with. So I decided I could spare another 1 core for my Windows XP installation. The result – Terrible.
Windows XP booting took more than 5 mins as compared to about 1.5mins previously. Ran top and saw that Virtualbox was using 198% CPU. Normal circumstances with 1 VCPU, it would be at 98%. Switched back to 1 VCPU, things became normal again.
I’m not too sure if it’s Virtualbox that’s not handling the job scheduling correctly, but if anyone runs into this problem of having slow performance in Virtualbox, this could be the solution.