Battled with disk space limits on that Ubuntu VM tho..resolved them by extending LVM partition. Great instruction set here.
Showing posts with label vmware fusion. Show all posts
Showing posts with label vmware fusion. Show all posts
Sunday, December 01, 2024
popOS on Ubuntu 64-bit ARM server
I love PopOS. However, there isn't an installer for the ARM architecture of my Mac M2 Pro.
Cyberknife on devtooler.com got a vm working for me on VMware Fusion for my ARM-based Mac. Thanks Cyberknife!
Saturday, March 07, 2009
upgrading my macbook pro system drive
Lately, I've been preparing a talk on Linux video production in linux that I will be giving at the end of April. More or less, it will be a technology demo that shows how to accomplish various video related tasks in Linux:
-capturing a video (acquisition)
-importing the output from the camera via firewire
-basics of file formats
-editing
-rendering
-scripting
-saving to a final destination (iPod/DVD/Vimeo)
So there will be a lot of ground to cover in the hour or so I will be speaking. I considered the mechanics of my presentation and first thought it would be cool to use my JVC HD10U to capture video of the conference which I'd then edit in Cinelerra. I had Fedora 10 already running in a virtual machine via VMware Fusion on my MacBook Pro 2.33Ghz Intel Core 2 Duo.
This method posed one big hurdle: VMware does not support firewire. VMware supports USB, but my camera only transmits high def video over firewire. Thus, I would not be able to capture live video from the camera during the talk. Conceivably, I could use a USB camera, but the quality would be so piss poor as to be embarrassing. So the VMware solution was nixed. The best solution was to dual boot my MacBook. I had my marching orders: I had to figure out how to dual boot my MacBook.
As expected, I hit a few speed bumps along the way, as the TechAnswerGuy always does. And as usual, you get to learn from my mistakes. Here we go..
Summary
Here was the high level plan:
1) upgrade my system drive to a 320GB 7200RPM Seagate Momentus
I was running out of space on the original 120GB drive, so this would be fun.
2) partition that fat new system drive to have a 240GB partition for Mac OSX and leave the 60GB unused space for Fedora
3) use SuperDuper to backup all important files to the Mac partition
4) use either Boot Camp or rEFIt to present a nice dual boot menu when the MacBook boots
5) configure the Fedora 10, x86-64 instance with a working copy of Cinelerra, dvgrab and all the media goodies necessary to make a slam-bang presentation come alive
Devil in the Details
In order to upgrade my system drive, I needed to migrate the data from the old drive to the new drive. Lucky for Mac users, David Nanian has written a wonderfully simple app called SuperDuper that creates bootable backups of Mac system drives. I prefer the word clone, as it refers to the fact that the backup also makes the drive bootable. Semantics aside, the result is the same.
Since my system drive is the drive that came installed in the MacBook, I needed to hook up the new 320GB Seagate I had bought. This was done using a very neat little device, a non enclosed disk enclosure called the Thermaltake BlacX eSATA Hard Drive Docking Station
that I had bought at the same time for this express purpose.
Thermaltake BlacX..Sweet!
What a simple, easy little device to use! It is like a little USB disk drive bucket for both 2.5" and 3.5" disks. You just insert a disk connector side down into this bad boy, plug it in via USB into your PC or MAC, turn it on and voila, instant access to your storage! No fussing with screws or metal sleeves. It's cheap too, low $40s. After using enclosures for years, it is nice to not have to pick up a screwdriver to get access to my storage.
Once I plugged in the new drive into the BlacX and turned it on, it was time to 1) partition the empty drive and 2) do the SuperDuper backup. Partitioning the drive with the OSX Disk Utility was fairly easy. I accepted the defaults for the partition:
* Mac OS Extended partition (Journaled)
* install Mac OS 9 drivers
Partition Hell
Of the 300GB usable out of the drive, I allocated 240GB in the Mac partition and 60GB Free Space to land my Fedora 10 system. One very important thing that I needed to select is under Options:
select GUID Partition Table. Initially, I had taken the defaults settings and the defaults create a drive that uses the older Apple Partition Map drive partitioning scheme:
Do NOT use APM because you will get errors in both Boot Camp and rEFIt. The Boot Camp error went something like this:
Startup disk cannot be partitioned or restored to a single partition.
Backup the disk and use Disk Utility to format it as a single Mac OS Extended (Journaled) Volume.
The above error is very misleading, because when you look at the format of your partition, the partition is formatted in the correct way. But at the bottom of Disk Utility's Partition screen for the drive, the information about the drive will be listed and the key piece is "Partition Map Scheme". If Apple Partition Map is there, you won't be able to use Boot Camp or rEFIt. In my case, I had to repartition the new drive again to create a partition that had a Partition Map Scheme of GUID Partition Table. Here's a short guide that explains how to convert a drive from APM to GUID.
Long story short, you'll have to blow away whatever is on the disk to do the conversion. So be advised.
SooperDooper Indeed!
Once I had resolved the Partition Map problem, I moved onto backing up my sensitive data to the new drive with SuperDuper. There are a number of guides out there and SuperDuper is really easy to use. It took about three hours to copy 100GB of data from my currently internal old system drive to the new 320GB, 7200RPM hard drive that was plugged into the Thermaltake.
Quid Pro Quo
The next step was to take apart the MacBook and switch out the old drive for the new. This was non-trivial, required a delicate touch and took about an hour.
http://www.extremetech.com/article2/0,2845,2119529,00.asp
rEFIt
As I am all for open source solutions, I decided to use rEFIt as my boot manager. rEFIt also provides a clean way to install another OS. In point of fact, you don't need rEFIt to boot into a second operating system on your MacBook. Simply hold down the Option button as your MacBook is booting, and you will see OSX's built in system volume chooser.
Once I installed rEFIt, I rebooted the system and I saw the rEFIt boot manager appear. I booted a second time and inserted my Fedora 10, x86-64 install DVD and when the rEFIt boot manager appeared, I now had a second choice appear in the menu. That of Tux!
Familiar Territory
After that, the Fedora install process was the usual. One note: make sure to look at the disk properties in the disk configuration section of the install. Even though Fedora deselects any Mac partitions, it is good to double check this. The Fedora installer make good choices for the partitioning, given that my newly installed system disk in the Mac was found as /dev/sda:
* Fedora automatically deselected the first two partitions in /dev/sda as they were Mac partitions
* Fedora correctly assigned /dev/sda3 as the boot partition
Nice. After confirming Fedora's correct selected defaults for the partitioning layout, I then selected the base installation plus Developer Tools. This selection, plus the dependencies for Cinelerra build resulted in about 5.1GB used on the disk. Not too porky. I went to breakfast and the install finished in about 30 minutes.
After the system restarted, I found some troubles with the Mac's touchpad. I resolved them with the synaptics driver and some xorg.conf config, but I will detail that in a second post.
I will try to fill in some of the details of this long winded post with pictures to break up the monotony of the text.
TAG
Other References
http://www.macgeekery.com/tips/cli/nondestructively_resizing_volumes
http://ubuntuforums.org/archive/index.php/t-766172.html
http://www.shirt-pocket.com/forums/showthread.php?t=3282
http://forum.onmac.net/showthread.php?t=2793
-capturing a video (acquisition)
-importing the output from the camera via firewire
-basics of file formats
-editing
-rendering
-scripting
-saving to a final destination (iPod/DVD/Vimeo)
So there will be a lot of ground to cover in the hour or so I will be speaking. I considered the mechanics of my presentation and first thought it would be cool to use my JVC HD10U to capture video of the conference which I'd then edit in Cinelerra. I had Fedora 10 already running in a virtual machine via VMware Fusion on my MacBook Pro 2.33Ghz Intel Core 2 Duo.
This method posed one big hurdle: VMware does not support firewire. VMware supports USB, but my camera only transmits high def video over firewire. Thus, I would not be able to capture live video from the camera during the talk. Conceivably, I could use a USB camera, but the quality would be so piss poor as to be embarrassing. So the VMware solution was nixed. The best solution was to dual boot my MacBook. I had my marching orders: I had to figure out how to dual boot my MacBook.
As expected, I hit a few speed bumps along the way, as the TechAnswerGuy always does. And as usual, you get to learn from my mistakes. Here we go..
Summary
Here was the high level plan:
1) upgrade my system drive to a 320GB 7200RPM Seagate Momentus
I was running out of space on the original 120GB drive, so this would be fun.
2) partition that fat new system drive to have a 240GB partition for Mac OSX and leave the 60GB unused space for Fedora
3) use SuperDuper to backup all important files to the Mac partition
4) use either Boot Camp or rEFIt to present a nice dual boot menu when the MacBook boots
5) configure the Fedora 10, x86-64 instance with a working copy of Cinelerra, dvgrab and all the media goodies necessary to make a slam-bang presentation come alive
Devil in the Details
In order to upgrade my system drive, I needed to migrate the data from the old drive to the new drive. Lucky for Mac users, David Nanian has written a wonderfully simple app called SuperDuper that creates bootable backups of Mac system drives. I prefer the word clone, as it refers to the fact that the backup also makes the drive bootable. Semantics aside, the result is the same.
Since my system drive is the drive that came installed in the MacBook, I needed to hook up the new 320GB Seagate I had bought. This was done using a very neat little device, a non enclosed disk enclosure called the Thermaltake BlacX eSATA Hard Drive Docking Station
that I had bought at the same time for this express purpose.Thermaltake BlacX..Sweet!
What a simple, easy little device to use! It is like a little USB disk drive bucket for both 2.5" and 3.5" disks. You just insert a disk connector side down into this bad boy, plug it in via USB into your PC or MAC, turn it on and voila, instant access to your storage! No fussing with screws or metal sleeves. It's cheap too, low $40s. After using enclosures for years, it is nice to not have to pick up a screwdriver to get access to my storage.
Once I plugged in the new drive into the BlacX and turned it on, it was time to 1) partition the empty drive and 2) do the SuperDuper backup. Partitioning the drive with the OSX Disk Utility was fairly easy. I accepted the defaults for the partition:
* Mac OS Extended partition (Journaled)
* install Mac OS 9 drivers
Partition Hell
Of the 300GB usable out of the drive, I allocated 240GB in the Mac partition and 60GB Free Space to land my Fedora 10 system. One very important thing that I needed to select is under Options:
select GUID Partition Table. Initially, I had taken the defaults settings and the defaults create a drive that uses the older Apple Partition Map drive partitioning scheme:
Do NOT use APM because you will get errors in both Boot Camp and rEFIt. The Boot Camp error went something like this:
Startup disk cannot be partitioned or restored to a single partition.
Backup the disk and use Disk Utility to format it as a single Mac OS Extended (Journaled) Volume.
The above error is very misleading, because when you look at the format of your partition, the partition is formatted in the correct way. But at the bottom of Disk Utility's Partition screen for the drive, the information about the drive will be listed and the key piece is "Partition Map Scheme". If Apple Partition Map is there, you won't be able to use Boot Camp or rEFIt. In my case, I had to repartition the new drive again to create a partition that had a Partition Map Scheme of GUID Partition Table. Here's a short guide that explains how to convert a drive from APM to GUID.
Long story short, you'll have to blow away whatever is on the disk to do the conversion. So be advised.
SooperDooper Indeed!
Once I had resolved the Partition Map problem, I moved onto backing up my sensitive data to the new drive with SuperDuper. There are a number of guides out there and SuperDuper is really easy to use. It took about three hours to copy 100GB of data from my currently internal old system drive to the new 320GB, 7200RPM hard drive that was plugged into the Thermaltake.
Quid Pro Quo
The next step was to take apart the MacBook and switch out the old drive for the new. This was non-trivial, required a delicate touch and took about an hour.
http://www.extremetech.com/article2/0,2845,2119529,00.asp
rEFIt
As I am all for open source solutions, I decided to use rEFIt as my boot manager. rEFIt also provides a clean way to install another OS. In point of fact, you don't need rEFIt to boot into a second operating system on your MacBook. Simply hold down the Option button as your MacBook is booting, and you will see OSX's built in system volume chooser.
Once I installed rEFIt, I rebooted the system and I saw the rEFIt boot manager appear. I booted a second time and inserted my Fedora 10, x86-64 install DVD and when the rEFIt boot manager appeared, I now had a second choice appear in the menu. That of Tux!
Familiar Territory
After that, the Fedora install process was the usual. One note: make sure to look at the disk properties in the disk configuration section of the install. Even though Fedora deselects any Mac partitions, it is good to double check this. The Fedora installer make good choices for the partitioning, given that my newly installed system disk in the Mac was found as /dev/sda:
* Fedora automatically deselected the first two partitions in /dev/sda as they were Mac partitions
* Fedora correctly assigned /dev/sda3 as the boot partition
Nice. After confirming Fedora's correct selected defaults for the partitioning layout, I then selected the base installation plus Developer Tools. This selection, plus the dependencies for Cinelerra build resulted in about 5.1GB used on the disk. Not too porky. I went to breakfast and the install finished in about 30 minutes.
After the system restarted, I found some troubles with the Mac's touchpad. I resolved them with the synaptics driver and some xorg.conf config, but I will detail that in a second post.
I will try to fill in some of the details of this long winded post with pictures to break up the monotony of the text.
TAG
Other References
http://www.macgeekery.com/tips/cli/nondestructively_resizing_volumes
http://ubuntuforums.org/archive/index.php/t-766172.html
http://www.shirt-pocket.com/forums/showthread.php?t=3282
http://forum.onmac.net/showthread.php?t=2793
Sunday, February 22, 2009
extending a logical volume in Fedora
I have a Fedora 10, x86-64 installation running under VMware Fusion on my Mac. Today, I ran out of disk space on my root partition. My root partition sits on a logical volume. In the "df" output below, note that I only have 92MB left on my / drive:
[root@ogre ~]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00 5.7G 5.4G 92M 99% /
/dev/sda1 190M 30M 151M 17% /boot
tmpfs 543M 0 543M 0% /dev/shm
/dev/sr0 96M 96M 0 100% /media/GParted-live
Oh no!
Research Necessary
Now, I haven't worked with logical volumes in quite some time, so I had to do a bunch of reading to figure out what the heck to do. These documents were of immeasurable help:
A Beginner's Guide to LVM
VMware Fusion - Expanding a Disk
Resizing LVM Volumes in Linux
Summary
In a nutshell, here are the steps necessary to expand the amount of space in your logical volume on Fedora. The first step is the allocation of new space in the context of VMware, but you could easily substitute the installation of a new hard drive:
1) In VMware Fusion, under Virtual Machine -> Settings -> Hard Disk, expand the size of your disk to the desired amount. I increased my disk space allocation from 8GB to 10GB:
2) Make a new partition using unallocated space
3) Create a new physical volume from the new partition that was just created
4) Extend the volume group into the new physical volume that was just created
5) Note the amount of free space in the volume group
6) Extend the amount of space in the logical volume using the value of free space
7) Resize the filesystem on the logical volume
8) Note the increased available space in the filesystem on the logical volume
9) Drink beer, you've earned it!
Details
##########
#2) MAKE A NEW PARTITION USING UNALLOCATED SPACE
##########
[root@ogre ~]# parted
GNU Parted 1.8.8
Using /dev/sda
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
Model: VMware, VMware Virtual S (scsi)
Disk /dev/sda: 10.7GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 32.3kB 206MB 206MB primary ext3 boot
2 206MB 8587MB 8382MB primary lvm
(parted) mkpart primary 8588 10700
(parted) print
Model: VMware, VMware Virtual S (scsi)
Disk /dev/sda: 10.7GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 32.3kB 206MB 206MB primary ext3 boot
2 206MB 8587MB 8382MB primary lvm
3 8587MB 10.7GB 2113MB primary
(parted) quit
Information: You may need to update /etc/fstab.
##########
#3) CREATE A NEW PHYSICAL VOLUME FROM THE NEW PARTITION THAT WAS JUST CREATED
##########
[root@ogre ~]# lvm
lvm> pvcreate /dev/sda3
Physical volume "/dev/sda3" successfully created
lvm> pvs
PV VG Fmt Attr PSize PFree
/dev/sda2 VolGroup00 lvm2 a- 7.78G 32.00M
/dev/sda3 lvm2 -- 1.97G 1.97G
##########
#4) EXTEND THE VOLUME GROUP INTO THE NEW PHYSICAL VOLUME THAT WAS JUST CREATED
##########
lvm> vgextend VolGroup00 /dev/sda3
Volume group "VolGroup00" successfully extended
lvm> pvs
PV VG Fmt Attr PSize PFree
/dev/sda2 VolGroup00 lvm2 a- 7.78G 32.00M
/dev/sda3 VolGroup00 lvm2 a- 1.94G 1.94G
##########
#5) NOTE THE AMOUNT OF FREE SPACE IN THE VOLUME GROUP
##########
lvm> vgdisplay VolGroup00
--- Volume group ---
VG Name VolGroup00
System ID
Format lvm2
Metadata Areas 2
Metadata Sequence No 4
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 2
Open LV 2
Max PV 0
Cur PV 2
Act PV 2
VG Size 9.72 GB
PE Size 32.00 MB
Total PE 311
Alloc PE / Size 248 / 7.75 GB
Free PE / Size 63 / 1.97 GB
VG UUID H89xDs-yTqE-y2YZ-ORVq-idgW-HdGf-hHU8m3
##########
#6) EXTEND THE AMOUNT OF SPACE IN THE LOGICAL VOLUME USING THE VALUE OF FREE SPACE
##########
lvm> lvextend -l+63 /dev/VolGroup00/LogVol00
Extending logical volume LogVol00 to 7.75 GB
Logical volume LogVol00 successfully resized
lvm> lvs
LV VG Attr LSize Origin Snap% Move Log Copy% Convert
LogVol00 VolGroup00 -wi-ao 7.75G
LogVol01 VolGroup00 -wi-ao 1.97G
lvm> quit
Exiting.
##########
#7) RESIZE THE FILESYSTEM ON THE LOGICAL VOLUME
##########
[root@ogre ~]# resize2fs /dev/VolGroup00/LogVol00
resize2fs 1.41.3 (12-Oct-2008)
Filesystem at /dev/VolGroup00/LogVol00 is mounted on /; on-line resizing required
old desc_blocks = 1, new_desc_blocks = 1
Performing an on-line resize of /dev/VolGroup00/LogVol00 to 2031616 (4k) blocks.
The filesystem on /dev/VolGroup00/LogVol00 is now 2031616 blocks long.
##########
#8) NOTE THE INCREASED AVAILABLE SPACE IN THE FILESYSTEM ON THE LOGICAL VOLUME
##########
[root@ogre ~]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
7.7G 5.4G 2.0G 74% /
/dev/sda1 190M 30M 151M 17% /boot
tmpfs 543M 0 543M 0% /dev/shm
/dev/sr0 96M 96M 0 100% /media/GParted-live
##########
#9) DRINK BEER!
##########
Hooray! Now I won't run out of space in my VM!
TAG
[root@ogre ~]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00 5.7G 5.4G 92M 99% /
/dev/sda1 190M 30M 151M 17% /boot
tmpfs 543M 0 543M 0% /dev/shm
/dev/sr0 96M 96M 0 100% /media/GParted-live
Oh no!
Research Necessary
Now, I haven't worked with logical volumes in quite some time, so I had to do a bunch of reading to figure out what the heck to do. These documents were of immeasurable help:
A Beginner's Guide to LVM
VMware Fusion - Expanding a Disk
Resizing LVM Volumes in Linux
Summary
In a nutshell, here are the steps necessary to expand the amount of space in your logical volume on Fedora. The first step is the allocation of new space in the context of VMware, but you could easily substitute the installation of a new hard drive:
1) In VMware Fusion, under Virtual Machine -> Settings -> Hard Disk, expand the size of your disk to the desired amount. I increased my disk space allocation from 8GB to 10GB:
2) Make a new partition using unallocated space
3) Create a new physical volume from the new partition that was just created
4) Extend the volume group into the new physical volume that was just created
5) Note the amount of free space in the volume group
6) Extend the amount of space in the logical volume using the value of free space
7) Resize the filesystem on the logical volume
8) Note the increased available space in the filesystem on the logical volume
9) Drink beer, you've earned it!
Details
##########
#2) MAKE A NEW PARTITION USING UNALLOCATED SPACE
##########
[root@ogre ~]# parted
GNU Parted 1.8.8
Using /dev/sda
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
Model: VMware, VMware Virtual S (scsi)
Disk /dev/sda: 10.7GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 32.3kB 206MB 206MB primary ext3 boot
2 206MB 8587MB 8382MB primary lvm
(parted) mkpart primary 8588 10700
(parted) print
Model: VMware, VMware Virtual S (scsi)
Disk /dev/sda: 10.7GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 32.3kB 206MB 206MB primary ext3 boot
2 206MB 8587MB 8382MB primary lvm
3 8587MB 10.7GB 2113MB primary
(parted) quit
Information: You may need to update /etc/fstab.
##########
#3) CREATE A NEW PHYSICAL VOLUME FROM THE NEW PARTITION THAT WAS JUST CREATED
##########
[root@ogre ~]# lvm
lvm> pvcreate /dev/sda3
Physical volume "/dev/sda3" successfully created
lvm> pvs
PV VG Fmt Attr PSize PFree
/dev/sda2 VolGroup00 lvm2 a- 7.78G 32.00M
/dev/sda3 lvm2 -- 1.97G 1.97G
##########
#4) EXTEND THE VOLUME GROUP INTO THE NEW PHYSICAL VOLUME THAT WAS JUST CREATED
##########
lvm> vgextend VolGroup00 /dev/sda3
Volume group "VolGroup00" successfully extended
lvm> pvs
PV VG Fmt Attr PSize PFree
/dev/sda2 VolGroup00 lvm2 a- 7.78G 32.00M
/dev/sda3 VolGroup00 lvm2 a- 1.94G 1.94G
##########
#5) NOTE THE AMOUNT OF FREE SPACE IN THE VOLUME GROUP
##########
lvm> vgdisplay VolGroup00
--- Volume group ---
VG Name VolGroup00
System ID
Format lvm2
Metadata Areas 2
Metadata Sequence No 4
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 2
Open LV 2
Max PV 0
Cur PV 2
Act PV 2
VG Size 9.72 GB
PE Size 32.00 MB
Total PE 311
Alloc PE / Size 248 / 7.75 GB
Free PE / Size 63 / 1.97 GB
VG UUID H89xDs-yTqE-y2YZ-ORVq-idgW-HdGf-hHU8m3
##########
#6) EXTEND THE AMOUNT OF SPACE IN THE LOGICAL VOLUME USING THE VALUE OF FREE SPACE
##########
lvm> lvextend -l+63 /dev/VolGroup00/LogVol00
Extending logical volume LogVol00 to 7.75 GB
Logical volume LogVol00 successfully resized
lvm> lvs
LV VG Attr LSize Origin Snap% Move Log Copy% Convert
LogVol00 VolGroup00 -wi-ao 7.75G
LogVol01 VolGroup00 -wi-ao 1.97G
lvm> quit
Exiting.
##########
#7) RESIZE THE FILESYSTEM ON THE LOGICAL VOLUME
##########
[root@ogre ~]# resize2fs /dev/VolGroup00/LogVol00
resize2fs 1.41.3 (12-Oct-2008)
Filesystem at /dev/VolGroup00/LogVol00 is mounted on /; on-line resizing required
old desc_blocks = 1, new_desc_blocks = 1
Performing an on-line resize of /dev/VolGroup00/LogVol00 to 2031616 (4k) blocks.
The filesystem on /dev/VolGroup00/LogVol00 is now 2031616 blocks long.
##########
#8) NOTE THE INCREASED AVAILABLE SPACE IN THE FILESYSTEM ON THE LOGICAL VOLUME
##########
[root@ogre ~]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
7.7G 5.4G 2.0G 74% /
/dev/sda1 190M 30M 151M 17% /boot
tmpfs 543M 0 543M 0% /dev/shm
/dev/sr0 96M 96M 0 100% /media/GParted-live
##########
#9) DRINK BEER!
##########
Hooray! Now I won't run out of space in my VM!
TAG
vmware tools install in Fedora 10
Here are some quick notes to installing VMware Tools in Fedora 10 in Fusion. My particular architecture is x86-64, but these should work for regular x86 installs:
1) yum groupinstall "Development Tools"
2) yum install kernel-devel* kernel-headers*
3) run ./vmware-install.pl as root
Also, I had one problem where the kernel-devel* and kernel-headers* package did not match my kernel, which was one revision lower than my installed kernel. The vmware-install.pl program told me this when I tried to run it. The solution to this was to simply update my kernel:
yum install kernel
TAG
1) yum groupinstall "Development Tools"
2) yum install kernel-devel* kernel-headers*
3) run ./vmware-install.pl as root
Also, I had one problem where the kernel-devel* and kernel-headers* package did not match my kernel, which was one revision lower than my installed kernel. The vmware-install.pl program told me this when I tried to run it. The solution to this was to simply update my kernel:
yum install kernel
TAG
Sunday, February 15, 2009
100% cpu on vmware fusion 2.0.2 with Mac OSX 10.5.6
This weekend, I installed Fusion 2.0.2 on my MacBook Pro 17" (dual core 2.4Ghz, 2GB RAM) running OSX 10.5.6. I was running an XP SP2 VM using one processor and 512MB. The one dedicated CPU would spike to 100% and my mouse disappeared. Thus, I had to control XP via the keyboard, always an exciting task. Of course, the display was really sluggish as others in this thread have reported. I did try the reinstall of VMware Tools, but that didn't work. Two things in conjunction did work:
1) under Settings -> Sharing -> Shared Applications, I disabled "Allow your Mac to open applications in the virtual machine"
2) in the same dialog box, select "Never" for "Show running virtual machine applications in the dock". This essentially disables Unity mode for that option.
Update 2009/02/16
Shutdown your vm and restart Fusion to make sure the changes are effective.
*** end update ***
Update 2009/02/18
I should clarify that my MacBook was upgraded to OSX 10.5 Leopard recently. I believe the DVD upgraded it to 10.5.4, and then I did another interim upgrade via Internet download to 10.5.6
*** end update ***
When you read the list of caveats in the VMware Fusion Release Notes, it is quite a litany of troubles. I guess this is where complexity gets us..too many combinations of guest and host OS versions for the company to adequately QA their products.
Unfortunately, it cost me at least two hours of my time today.
TAG
References:
Beginner's Guide to VMware Fusion
Power User's Guide to VMware Fusion
Resizing Virtual Disks with Step-by-Step Instructions
Run a Virtual Machine at Boot
Workstation 6 Manual
Modifying Fusion's Network Settings
1) under Settings -> Sharing -> Shared Applications, I disabled "Allow your Mac to open applications in the virtual machine"
2) in the same dialog box, select "Never" for "Show running virtual machine applications in the dock". This essentially disables Unity mode for that option.
Update 2009/02/16
Shutdown your vm and restart Fusion to make sure the changes are effective.
*** end update ***
Update 2009/02/18
I should clarify that my MacBook was upgraded to OSX 10.5 Leopard recently. I believe the DVD upgraded it to 10.5.4, and then I did another interim upgrade via Internet download to 10.5.6
*** end update ***
When you read the list of caveats in the VMware Fusion Release Notes, it is quite a litany of troubles. I guess this is where complexity gets us..too many combinations of guest and host OS versions for the company to adequately QA their products.
Unfortunately, it cost me at least two hours of my time today.
TAG
References:
Beginner's Guide to VMware Fusion
Power User's Guide to VMware Fusion
Resizing Virtual Disks with Step-by-Step Instructions
Run a Virtual Machine at Boot
Workstation 6 Manual
Modifying Fusion's Network Settings
Thursday, December 13, 2007
MacBook Pro: six month review
I've had my MacBook Pro 2.33Ghz Intel Core 2 Duo for over six months now and thought I'd give a quick review and impressions. Disclaimer: This review will be from the standpoint of a guy who uses the box mainly to connect to his corporate network, surf the web and do some occasional live video importing using iMovie HD.
Stability
It is pretty bulletproof and does not hang, until you start playing with HDV. Then things slow down or in some very rare situations, have hung the box. Thus, a restart is necessary.
Networking
Wi-Fi and hardwired ethernet setup are a breeze. At home, WiFi performance to my NetGear WGT624 is excellent and works from the first floor in my loft, through metal studded walls up to the router which is upstairs in the loft roughly twenty feet away. I have had no trouble connecting to WiFi networks in hotels or conference centers.
Connectivity
In order to logon to other boxes at my home and corp networks, I run Microshaft Terminal Services and Chicken of the VNC. This is our peak season at work, so when I am home, I will log in over Cisco VPN to my workstation at work via MS RDP and keep the connection up as long as possible. Cisco VPN has been connected for as long as fourteen days with no downtime. Microsoft RDP occasionally hangs and I will have to restart the box. Figures..the times I have had to restart a Mac is because of a Microsoft product. Finally, built in BSD Unix gives you all the Unix tools plus ssh/scp for other connectivity options.
OS Alternatives
I don't run Boot Camp; instead, I run VMware Fusion (VMware's answer to Parallels) and have XP and Fedora running in virtual machines on the MacBook. Parallels works for some people; however, I encountered problems with a kernel panic when I installed Fedora. Since we use VMware at work, I just opted to use VMware Fusion.
XP and Fedora performance in Fusion is good, but not great for things like editing video. However, at least you have the capability of running an alternate OS without fear of the virtual PC going down. VMware allows you to assign one or more processors to a VM, so that is an additional performance boost.
I know folks who do run Boot Camp without issue if you want to go down that route.
Applications
I haven't used the Mac apps other than Safari/TextEdit/Preview/IMovie HD/iTunes. But those programs seem really intuitive. Kudos to Jobs for enforcing ease of use. On certain websites. there is squirrely-ness with Safari and some form fields. I suspect this is due to those sites' coders not doing a good job of testing. For those websites, I run Firefox and that usually will get around these problems.
Battery Life
Multimedia will suck the juice out of this thing. I probably get only 1 1/2 to 2 hours of battery life if I am viewing YouTube or watching a DVD. However, if I use non-multimedia apps, I get quite a bit more usable batt time. For instance, I was able to use Microsoft Word on a plane for about 4.5 hours straight before the box died.
All in all, I am a man for all seasons: PC for noodling about or raw firepower and the Mac for "it just works"
sodo
Stability
It is pretty bulletproof and does not hang, until you start playing with HDV. Then things slow down or in some very rare situations, have hung the box. Thus, a restart is necessary.
Networking
Wi-Fi and hardwired ethernet setup are a breeze. At home, WiFi performance to my NetGear WGT624 is excellent and works from the first floor in my loft, through metal studded walls up to the router which is upstairs in the loft roughly twenty feet away. I have had no trouble connecting to WiFi networks in hotels or conference centers.
Connectivity
In order to logon to other boxes at my home and corp networks, I run Microshaft Terminal Services and Chicken of the VNC. This is our peak season at work, so when I am home, I will log in over Cisco VPN to my workstation at work via MS RDP and keep the connection up as long as possible. Cisco VPN has been connected for as long as fourteen days with no downtime. Microsoft RDP occasionally hangs and I will have to restart the box. Figures..the times I have had to restart a Mac is because of a Microsoft product. Finally, built in BSD Unix gives you all the Unix tools plus ssh/scp for other connectivity options.
OS Alternatives
I don't run Boot Camp; instead, I run VMware Fusion (VMware's answer to Parallels) and have XP and Fedora running in virtual machines on the MacBook. Parallels works for some people; however, I encountered problems with a kernel panic when I installed Fedora. Since we use VMware at work, I just opted to use VMware Fusion.
XP and Fedora performance in Fusion is good, but not great for things like editing video. However, at least you have the capability of running an alternate OS without fear of the virtual PC going down. VMware allows you to assign one or more processors to a VM, so that is an additional performance boost.
I know folks who do run Boot Camp without issue if you want to go down that route.
Applications
I haven't used the Mac apps other than Safari/TextEdit/Preview/IMovie HD/iTunes. But those programs seem really intuitive. Kudos to Jobs for enforcing ease of use. On certain websites. there is squirrely-ness with Safari and some form fields. I suspect this is due to those sites' coders not doing a good job of testing. For those websites, I run Firefox and that usually will get around these problems.
Battery Life
Multimedia will suck the juice out of this thing. I probably get only 1 1/2 to 2 hours of battery life if I am viewing YouTube or watching a DVD. However, if I use non-multimedia apps, I get quite a bit more usable batt time. For instance, I was able to use Microsoft Word on a plane for about 4.5 hours straight before the box died.
All in all, I am a man for all seasons: PC for noodling about or raw firepower and the Mac for "it just works"
sodo
Sunday, September 02, 2007
setting the screen resolution in Fedora under VMware Fusion
I was having trouble locking the screen resolution of Fedora as it ran under VMware Fusion on my MacBook Pro 2.33Ghz Intel Core 2 Duo. Initially, I set the screen resolution using Administration -> Display. For a reason unknown to me, setting the resolution of 1440x900 always reverted to 1680x1000. Playing around for a half an hour, I finally figured out that Display was not going to work. I then used Preferences -> Screen Resolution:
This widget successfully set my Fedora Core 6 desktop resolution to the exact screen size of my MacBook, a lovely widescreen 1440x900.
Nice!
'sodo
This widget successfully set my Fedora Core 6 desktop resolution to the exact screen size of my MacBook, a lovely widescreen 1440x900.
Nice!
'sodo
Sunday, July 01, 2007
VMware Fusion Unity mode
I'll start this post with a question: what is wrong with this picture?
If you guessed that there are Windows apps running on my MacBook Pro's desktop, you'd be right! Of course, if you are a true Mac devotee, there's nothing "right" about that at all! In fact, it's all wrong!!
Seriously though, VMware Fusion's Unity mode (like Parallels Coherence mode) is a really nice piece of work. If you ever wanted to run Mac and Windows applications side by side on the same desktop, this is the program for you! I have Fusion running on my MacBook Pro using an XP Professional virtual guest OS and Unity is very sweet. There is a bit of a visual hiccup for the first couple of seconds while you switch from Single Window or Full Screen mode to Unity mode (look under Fusion's "View" menu to switch):
The Mac and Windows desktops then cohere together for a couple of seconds, but after that, Windows apps run right along side the native Mac applications. It was very cool to see and hear a video running in Windows Media Player on the Mac desktop. Now that's quite a feat of engineering! Thanks VMware! This will help ease the transition from PC to Mac for a lot of people. I will mention it to the powers that be at work.
A couple notes:
1) to have access to Unity mode, make sure you have the latest and greatest version of VMware Fusion Beta found here:
http://www.vmware.com/products/desktop/fusion.html
2) to enable the feature, make sure you have the latest version of VMware Tools installed in your guest operating system
3) if you are using XP Service Pack 2, a nice performance boost for the display is to utilize DirectX 8.1 acceleration features. So go to the Display menu under your XP virtual machines' Settings:
Cool!
If you guessed that there are Windows apps running on my MacBook Pro's desktop, you'd be right! Of course, if you are a true Mac devotee, there's nothing "right" about that at all! In fact, it's all wrong!!
Seriously though, VMware Fusion's Unity mode (like Parallels Coherence mode) is a really nice piece of work. If you ever wanted to run Mac and Windows applications side by side on the same desktop, this is the program for you! I have Fusion running on my MacBook Pro using an XP Professional virtual guest OS and Unity is very sweet. There is a bit of a visual hiccup for the first couple of seconds while you switch from Single Window or Full Screen mode to Unity mode (look under Fusion's "View" menu to switch):
The Mac and Windows desktops then cohere together for a couple of seconds, but after that, Windows apps run right along side the native Mac applications. It was very cool to see and hear a video running in Windows Media Player on the Mac desktop. Now that's quite a feat of engineering! Thanks VMware! This will help ease the transition from PC to Mac for a lot of people. I will mention it to the powers that be at work.
A couple notes:
1) to have access to Unity mode, make sure you have the latest and greatest version of VMware Fusion Beta found here:
http://www.vmware.com/products/desktop/fusion.html
2) to enable the feature, make sure you have the latest version of VMware Tools installed in your guest operating system
3) if you are using XP Service Pack 2, a nice performance boost for the display is to utilize DirectX 8.1 acceleration features. So go to the Display menu under your XP virtual machines' Settings:
Cool!
Monday, April 16, 2007
Fedora Core 6 in Parallels on a MacBook Pro blowup
I've been away at Web2.0 in San Francisco, but I thought I'd drop a quick entry regarding my experience with Parallels Desktop for Mac (Intel Mac) and my new MacBook Pro. In order to run Cinelerra, I installed Parallels on my brand spanking new MacBook Pro and wouldn't you know it, I got this lovely message when the new install of Core 6 booted up:
(0)Kernel panic - not syncing: Attempted to kill init!
I briefly googled that message, but you know, when you just need to get something working and are tired of doing the research, fall back on the tried and true. In that vein, I found that VMware's Fusion product was available in beta for the Mac. Oooh. Beta..that might not be so good. But since I already had a Fedora Core 6 installation that had everything I needed already running in VMware Server, I thought I'd give it a try. Here's the URL for the beta download..you'll have to register first:
http://register.vmware.com/content/beta/fusion/registration.html
Once I downloaded and installed fusion, I needed to bring over my 8GB Core 6 virtual machine from my PC. I zipped up the entire VM directory and found that zip very kindly reduced the size of the VMDK file from 8GB to 2.8GB. Cool! As I copied the zip over the network, I noticed it was taking a very, very long time. So I stopped the transfer, unplugged my network connections from my PC and Mac and wired them together with a crossover cable. Wired in this way, I increased my download speed from 500Kbps to 5400Kbps! Sweet!
Once the zip file had copied to the Mac, I unzipped it to my home directory and then created a new virtual machine from my pre-existing VM.
This process was a bit confusing at first. But what you need to do to utilize an existing VMware virtual machine is to select "Use an Existing virtual disk" under the Advanced Disk Options on the Virtual Hard Disk step of the create new virtual machine process:
Once I figured that little tricky bit out, I was good to go! I clicked Start on my newly created virtual machine et Voila! She came up! I turned off debugging as this seemed to slow things down a bit and made sure to install VMware tools for better mouse and graphic behavior.
Long live VMware!
(0)Kernel panic - not syncing: Attempted to kill init!
I briefly googled that message, but you know, when you just need to get something working and are tired of doing the research, fall back on the tried and true. In that vein, I found that VMware's Fusion product was available in beta for the Mac. Oooh. Beta..that might not be so good. But since I already had a Fedora Core 6 installation that had everything I needed already running in VMware Server, I thought I'd give it a try. Here's the URL for the beta download..you'll have to register first:
http://register.vmware.com/content/beta/fusion/registration.html
Once I downloaded and installed fusion, I needed to bring over my 8GB Core 6 virtual machine from my PC. I zipped up the entire VM directory and found that zip very kindly reduced the size of the VMDK file from 8GB to 2.8GB. Cool! As I copied the zip over the network, I noticed it was taking a very, very long time. So I stopped the transfer, unplugged my network connections from my PC and Mac and wired them together with a crossover cable. Wired in this way, I increased my download speed from 500Kbps to 5400Kbps! Sweet!
Once the zip file had copied to the Mac, I unzipped it to my home directory and then created a new virtual machine from my pre-existing VM.
This process was a bit confusing at first. But what you need to do to utilize an existing VMware virtual machine is to select "Use an Existing virtual disk" under the Advanced Disk Options on the Virtual Hard Disk step of the create new virtual machine process:
Once I figured that little tricky bit out, I was good to go! I clicked Start on my newly created virtual machine et Voila! She came up! I turned off debugging as this seemed to slow things down a bit and made sure to install VMware tools for better mouse and graphic behavior.
Long live VMware!
Subscribe to:
Posts (Atom)