Tuesday Nov 18, 2008

VMware: Cannot find VMnet0, starting disconnected

So I can't start my virtual machines for VMware:

Nov 18 09:52:25.157: vcpu-0| [msg.vnet.getLastMessage] VMnet0: The system cannot find the file specified
Nov 18 09:52:25.157: vcpu-0| [msg.device.startdisconnected] Virtual device Ethernet0 will start disconnected.

But this time I know what has to be going on. Recently I upgraded my 6.5 installation and I turned my machine off while I was out of town. And of course when I came back, the keyboard did not work (error 39?). It turned out that VMware installs a shim on top of the keyboard driver and I think the uninstall hosed me. I followed the directions at code 39 keyboard win XP. Let me tell you, entering text into regedit32 with a dead keyboard is a challenge. But the entry by Bas13 does walk you through it.

I also deleted the network configurations.

So I searched for the error messages today and mostly turned up Linux related questions.

I decided to reinstall the latest VMware upgrade and when I was prompted, I selected Repair as an option. That fixed the issue for me.

Originally posted on Kool Aid Served Daily
Copyright (C) 2008, Kool Aid Served Daily

Tuesday Sep 30, 2008

Some new bugs filed

So I filed two bugs with my experiences with VirtualBox 2.0.2 last week:

6753569 Virtual Box running causes assertion failed: afd->a_fd[i] == -1
Basically, when I start the VirtualBox up to install a new OS, it provides this core dump.
6753564 Installation of virtual box should update the boot archive
After I installed VirtualBox 2.0.2 and had the above panic, the fact that the boot archive had not been updated dropped me down into maintenance mode.

If you search the Bug Database for 6753564, it returns 6753569. If you try to go there directly with the URL I provided, then you get bug not found. Ahh, the first match happens because I mention 6753564 in other bug. Well, the link exists in 6753569 and I'm sure the bug will be opened up for public viewing sooner or later.

Originally posted on Kool Aid Served Daily
Copyright (C) 2008, Kool Aid Served Daily

Sunday Sep 28, 2008

I think I've been making the new Networking Configuration too difficult

You'll notice in Bag of links about VirtualBox configurations that I have collected a lot of articles about how to configure VirtualBox networking. And if you look in the VirtualBox 2.0.2 User Manual you will see that the Linux section has about 9 pages and the Solaris one (6.9 on page 87) has 1 paragraph.

Perhaps Sun has greatly simplified the code with respect to running on OpenSolaris?

Okay, armed with the pithy User Manual. I'm going to try to configure Host Interface Networking on VirtualBoxes with a OpenSolaris host. First I need to find where to configure the networking:

(Click to zoom in)

Pretty easy, it is in the Details tab. Okay, I select Network and now it has to be difficult, right?

No, all I have to do is select the Attached to: and change NAT to Host Interface:

And look, I can select the Generate button to the right of the MAC Adress: field to generate a new one.

While I'd like to automate all of this (and a scan of the VirtualBox 2.0.2 User Manual suggests that i could easily do so), I'm going to bank on ZFS cloning to avoid most of this. All I will need to be able to do is automatically change the id of the storage:

VBoxManage internalcommands setvdiuuid vdifilename

and mac up a new MAC:

VBoxManage modifyvm -macaddress1 

I believe the first is undocumented and the second is ripped right out of the VirtualBox 2.0.2 User Manual.

Originally posted on Kool Aid Served Daily
Copyright (C) 2008, Kool Aid Served Daily

Saturday Sep 27, 2008

Bag of links about Virtual Box configurations

Just some links I've stumbled across on my odyssey with VirtualBox:

Solaris Cluster on a laptop using VirtualBox, iSCSI and a quorum server
VirtualBox 1.6.2 configuration with jumpstarting done via JET
Building a Solaris Cluster Express cluster in a VirtualBox on OpenSolaris
VirtualBox 1.6.2 configuration to build a cluster and using iSCSI from ZFS
Host Interface Networking in Sun xVM VirtualBox
VirtualBox 2.0.0 configuration of Host Interface Networking. Actually installing OpenSolaris on Ubuntu
VirtualBox meets JET...
Must be Virtual Box 1.6.\* -- using JET and flar to manage quick setup of VMs. Hmm, he installs a OpenSolaris vbox on a Windows machine, puts JET on it, and then uses that machine to jumpstart others. Sweet article!
Configuring host networking for VirtualBox
Again a VirtualBox 1.6.\* release, another 4150 with four dual-core CPUs and 8Gb RAM. Use /usr/lib/vna, which appears gone from Virtual Box 2.0.2.
Famous Quote:
Here's my script. No, I didn't use SMF. I'm old school. Bite me.

I'll add more as I collect them:

VirtualBox Buzz
How can any collection of links on VirtualBox be complete without this?

Originally posted on Kool Aid Served Daily
Copyright (C) 2008, Kool Aid Served Daily

Saturday Mar 29, 2008

Using Crossbow to get a host interface network for VirtualBox

Okay, my snv 73 box is now a snv 85 box. Everything is working except for my punchin, but only because I need to bypass my Sun Ray 1G (and the Sun Ray Server 4.0 was dead easy to install). But the vnic_setup.sh script is still not working:

# ./vnic_setup.sh 0:1:4a:f2:31:34
Invalid link name: LINK
# LD_LIBRARY_PATH=/opt/VirtualBox:/opt/VirtualBox/qtgcc/lib:. ; export LD_LIBRARY_PATH
# ./vnic_setup.sh 0:1:4a:f2:31:34
Invalid link name: LINK
# ./vnic_setup.sh 0:1:4a:f2:31:34 vnic1
# ifconfig -a
lo0: flags=2001000849 mtu 8232 index 1
	inet netmask ff000000 
bge0: flags=201000843 mtu 1500 index 2
	inet netmask ffffff00 broadcast
	ether 0:a:e4:34:2f:da 
lo0: flags=2002000849 mtu 8252 index 1
	inet6 ::1/128 

Well the VirtualBox manual tells me how to do it manually:

# /usr/lib/vna bge0 0:1:4a:f2:31:34
# ifconfig vnic0 plumb
# ifconfig -a 
lo0: flags=2001000849 mtu 8232 index 1
	inet netmask ff000000 
bge0: flags=201000843 mtu 1500 index 2
	inet netmask ffffff00 broadcast
	ether 0:a:e4:34:2f:da 
vnic0: flags=201000842 mtu 1500 index 3
	inet netmask 0 
	ether 0:1:4a:f2:31:34 
lo0: flags=2002000849 mtu 8252 index 1
	inet6 ::1/128 
#  /usr/lib/vna bge0 0:1:4a:f2:31:36
# /usr/lib/vna bge0 0:1:4a:f2:31:38
# ifconfig vnic1 plumb
# ifconfig vnic2 plumb
# ifconfig vnic0 destination netmask up
# ifconfig vnic1 destination  netmask up
# ifconfig vnic2 destination netmask up
# ifconfig -a
lo0: flags=2001000849 mtu 8232 index 1
	inet netmask ff000000 
bge0: flags=201000843 mtu 1500 index 2
	inet netmask ffffff00 broadcast
	ether 0:a:e4:34:2f:da 
vnic0: flags=201000851 mtu 1500 index 3
	inet --> netmask ffffff00 
	ether 0:1:4a:f2:31:34 
vnic1: flags=201000851 mtu 1500 index 4
	inet --> netmask ffffff00 
	ether 0:1:4a:f2:31:36 
vnic2: flags=201000851 mtu 1500 index 5
	inet --> netmask ffffff00 
	ether 0:1:4a:f2:31:38 
lo0: flags=2002000849 mtu 8252 index 1
	inet6 ::1/128 

And when the system comes up, it has an IP of And I can't ping any of the 3.

It looks like I need to learn the CLI for VirtualBox. Here is a related article: Internal network does not work for OpenSolaris guests

Originally posted on Kool Aid Served Daily
Copyright (C) 2008, Kool Aid Served Daily

Friday Mar 28, 2008

Installing a host network for VirtualBox

As mentioned, I have a minimal install for my OpenSolaris test machines. Evidently I am missing something quite important for getting a host network up and running:

# ./vnic_setup.sh 0:1:4a:f2:31:34
./vnic_setup.sh: line 42: /usr/lib/vna: No such file or directory

Hmm, I can either load the iso and get the real files or learn how to work with the NAT mode.So either I do a complete reinstall or I figure how to get just a couple of files over. Sounds like I should learn about NAT anyway.

With two machines and NAT, they are both getting the same address. I could use the Internal Network option, but I'm still going to have to reinstall. Hmm, when I do a machine, I select Core Configure and add the following:

BIND DNS Name server and tools
BIND Name server Manifest
Freeware Compression Tools
Perl-Compatible Regular Expressions
Freeware shells
Freeware Other Utilities
XCU4 Utilities
GNU Autotools
Secure Shell
GNU which
gcmn - Common GNU package
Lint Libraries (root)
Lint Libraries (usr)
GNU binutils
GNU diffutils
Perl 5.6.1 (core)
Perl 5.6.1 (non-core)
GNU textinfo
Get all of System and Network Admin
Live Upgrade Software
MDB (root)
Programming Tools
resource pool (root)
Resource Pools in core software for resource pools
Solaris Zones
Vi IMproved
Kerberos V5 KDC (root)
Kerberos V5 Master KDC (root)
Kerberos Version 5 support (kernel)
NIS Server for Solaris (root)
NIS Server for Solaris (usr)
Interprocess Communication

Time to find what I need to add. First we need to look in the ISO image:

[tdh@warlock ~]> sudo lofiadm -a /zoo/isos/x86/snv85/solarisdvd.iso 
[tdh@warlock ~]> sudo mount -F hsfs /dev/lofi/1 /mnt
[tdh@warlock Product]> cd /mnt/Solaris_11/Product/
[tdh@warlock Product]> grep lib/vna \*/pkgmap
SUNWcsu/pkgmap:1 f none usr/lib/vna 0555 root bin 12592 13767 1204942578

Hmm, wait, I need to find that on my host system and not the guest machine. D'Oh!

[tdh@warlock lib]> uname -a
SunOS warlock 5.11 snv_73 i86pc i386 i86pc
[tdh@warlock lib]> sudo lofiadm -d /zoo/isos/x86/snv7

I have the DVD, but 73 is ancient! But I'll check:

[tdh@warlock Product]> grep lib/vna SUNWcsu/pkgmap
[tdh@warlock Product]> 

Ugh, the biggest hassle is that I use this machine as a Sun Ray Server. Okay, time for a reinstall!

Originally posted on Kool Aid Served Daily
Copyright (C) 2008, Kool Aid Served Daily

Do not need to get qt libaries with beta of VirtualBox

RTFM - at least the one which comes with the distribution. I think the online one does not have OpenSolaris support. And, I am right it does not.

Anyway, you do not need to retrieve the qt libraries and build, as I just did, it is supplied for you.

cd /opt/VirtualBox
LD_LIBRARY_PATH=/opt/VirtualBox:/opt/VirtualBox/qtgcc/lib:. ./VirtualBox

Originally posted on Kool Aid Served Daily
Copyright (C) 2008, Kool Aid Served Daily

Inital interactions with VirtualBox

Downloading and installing VirtualBox on my OpenSolaris box was a snap. Running and installing on it was a bit harder. First off, you need qt installed. Easy instructions are at VirtualBox on OpenSolaris. Then you need to tell it that something other than Right-Ctrl is your host key - you need to do this because Sun keyboards do not have that key . I chose my Right-Meta key. Imagine VirtualBox has your mouse and keyboard, your screensaver kicks in, and you can't get the system to understand you want to bring it to life.

Telling the tool how to load my OpenSolaris iso image was a bit counterintuitive. But the biggest problem I ended up having was only giving 8M to my graphics card. The Developer's install seemed okay with that, but the normal graphical install would puke on it. I was able to do a text install, until the point the install decided I was doing a NFS install and did not like the path I was giving. It also would not see the attached iso as a cdrom.

Kicking both tyres together - VirtualBox and Indiana was very helpful for this issue, Alan casually mentions you need 32M of Video Ram. I gave the system that and could then do the graphical install. And it correctly identified the iso as a cdrom. I'll bring that value down once I finish the install. I'm not going to install a GUI on this machine.

Originally posted on Kool Aid Served Daily
Copyright (C) 2008, Kool Aid Served Daily

Wednesday Dec 12, 2007

Adding a Damn Small Linux VM

I should be sleeping, but instead I created a Damn Small Linux VM. At first I downloaded a VMware image, but I eventually created a virtual disk and installed on it. I followed the directions at both HD Install :: How to Install DSL in VMware 6 and Installing to the Hard Disk.

Make sure that when you create the virtual disk, you select IDE and not SCSI! This means changing away from the default. If you do chose SCSI, cfdisk will not see the disk. You can fix that by:

  • Halting the VM, you can do that from the VMware console.
  • That gets you to the Summary View.
  • Select 'Edit Virtual Machine settings'.
  • Click on the 'Hard Disk' and then select 'Remove'.
  • Then click on 'Add' and select 'Hard Disk'->'Next'->'Create a new virtual disk'.
  • Switch 'Virtual Disk Type' to be 'IDE' instead of 'SCSI'.
  • And follow the normal steps to finish it off.
  • Restart the VM and now cfdisk should work.

After the dsl-hdinstall script reboots the VM, it will ask you to configure your X server. Do not accept the default value of USB mouse. You need to instead select IMPS/2 as the mouse. If you select the USB mouse, your mouse will not do anything. Follow these steps to fix it:

  • Hit CTRL-ALT-BKSP to get you out of the window manager.
  • This drops you back into your login terminal.
  • Run /usr/sbin/xsetup.sh, which will redo the setup.
  • You can run startx to get back into the window manager, but it didn't come up for me all the way.
  • Instead I rebooted - hey it comes back really quick.

You shouldn't have to worry about permissions just then, after all, you just gave new passwords for root and dsl. If needed, you can use sudo to get access.

I also followed the steps to rename my VM (Changing the Hostname) and to set it to use static IP (How can I enter and save my static IP settings?). And that is it for now...

Originally posted on Kool Aid Served Daily
Copyright (C) 2007, Kool Aid Served Daily

Tuesday Dec 11, 2007

Added scrolling to my VMs

Wow, I'm on a roll today. My mouse was not scrolling in my VMWare Workstation VMs. I went so far as looking into the manual - no luck. I couldn't find any options in the configuration files.

Time for google! Hmm, this one worked: Mouse wheel scroll not working in 6.10. It was in an Ubuntu forum and my Linux VM is Ubuntu. I went with the last answer from Mahmoud, who was quoting VMware Tools breaks mouse wheel on Ubuntu Edgy Eft guest.

Anyway, he said:

Change ps/2 to IMPS/2 in /etc/X11/xorg.conf and restart X
This solution worked for me.

Well it worked for both Ubuntu and Solaris!

Originally posted on Kool Aid Served Daily
Copyright (C) 2007, Kool Aid Served Daily

2nd VMWare Disk Hosed for my ZFS pool

In ZFS disks, VMWare, and WinXP disk management I talked about how I took my physical drives out of the VMWare Workstation configuration in order to clone a Solaris VM. That was a mistake. I've never got the ZFS pool back online. I get this:

# zpool import
  pool: tank
    id: 5099778507182773508
 state: UNAVAIL
status: One or more devices are missing from the system.
action: The pool cannot be imported. Attach the missing
        devices and try again.
   see: http://www.sun.com/msg/ZFS-8000-6X

        tank        UNAVAIL  missing device
          c2d0      ONLINE

        Additional devices are known to be part of this pool, though their
        exact configuration cannot be determined.

And format is very informative:

# format
Searching for disks...done

       0. c1t0d0 
       1. c2d0 
       2. c2d1 

c2d1 is not being recognized as a VMware drive. BTW: My backup policy sucks right now. I need to get at that data.

I went into the VM configuration and noticed that Physical drive 1 was 190G. It should be 233G like the other drive. Okay, the only drive I have that small is my WinXP one. Oh crap, is that what killed my root MBR? I'll find out when I reboot. :-> Anyway:

# format
Searching for disks...done

       0. c1t0d0 
       1. c2d0 
       2. c2d1 
# zpool import
  pool: tank
    id: 5099778507182773508
 state: ONLINE
action: The pool can be imported using its name or numeric identifier.

        tank        ONLINE
          c2d0      ONLINE
          c2d1      ONLINE

And I'm able to import it with '-f' and the band went crazy. Now to back up that data!

Originally posted on Kool Aid Served Daily
Copyright (C) 2007, Kool Aid Served Daily

Monday Dec 10, 2007

Just lost my root MBR on my game desktop

Today is not my day - the accident last night, the falling branches (really mini-trees) on the house due to ice, and the roaming brown-outs. I decided to turn off my WinXP desktop. When I turned it back on, it wouldn't load the OS. It would boot off of the DVD drive, but not off of the disk. Well, every tool I used told me that the partition was bad.

Now I'm in a quandary with the machine - I'm ready to go to a Linux distro except for the facts that:

  • I just paid for VMWare Workstation for Windows.
  • I'm not too sure that I'd like the gaming performance under VMWare Workstation for Linux.

As much as it pains me, I can't have Solaris as the main OS - the system is designed for gaming first and foremost. It is a nice home desktop as well.

The good news is that I was ready for this to happen. I had been toying with getting more memory to push me past 4G and running Vista as the host OS. I just couldn't choke down all of the reviews I've read on Vista. But, I had made backups of everything I cared for - except those two Dan Hart Christmas songs I got two nights ago.

I'm also suspicious about whether or not I had an IM virus on the machine. Every night a IM chat window would pop open with some XML looking code in it. My virus scans and spy ware scans turned up nothing.

So I'm ready to put the full power of virtualization to use to protect my system. I'll run pidgin from inside an Ubuntu VM.

Originally posted on Kool Aid Served Daily
Copyright (C) 2007, Kool Aid Served Daily

Thursday Dec 06, 2007

ZFS disks, VMWare, and WinXP disk management

In VMWare and 4 physical hard drives I talked about how I couldn't get VMWare Server to use the 4 physical drives I had my ZFS pool on. I ended up archiving the contents (which was mainly blowing away duplicate copies or previous archives to get to the core of what I needed) and recreating the pool on 2 drives.

I wanted to clone my build 77 Solaris image, but I didn't have enough space. Since I had a couple of extra disks sitting there in my system, I thought I would go ahead and move my virtual machines to all of that free space. And there the problems started.

If we look at the Disk Management snapin under WinXP, we can first see that VMWare must be capping the physical drives at 128G:

Not shown

Okay, I can live with that for right now, but why can't I right-click on either of the two free drives and do anything? Anything at all!

If you look carefully, you will see that the disks are labeled as 'Healthy (GPT Protective Partition)'. And that is what is keeping me from doing anything with them. Microsoft has this to say about Windows and GPT FAQ. And wiki defines GPT as GUID Partition Table. But I found both of these much later. And I only found this Microsoft TechNet note now: Change a GUID partition table disk into a master boot record disk.

In short, the Disk Management snapin is not going to be able to do anything with these GPT disks.

I tried to use QTParted off of a Knoppix live disk to fix the problem, but Knoppix refused to see the disks. So I booted into a nevada b77 dvd and selected a single user shell. I then used fdisk to blow away the partitions on the two disks. Finally, I rebooted and the Disk Management snapin could manipulate the disks:

Not shown

I then started off a copy of the VMWare simulators to the new disk area.

Originally posted on Kool Aid Served Daily
Copyright (C) 2007, Kool Aid Served Daily

Friday Nov 09, 2007

VMWare and 4 physical hard drives

For someone who develops cutting edge system software, I'm actually a late adopter of technology. I fought GUI mail clients forever (or perhaps it was just Microsoft Exchange I was fighting) - I stayed with elm and mutt long past their shelf lives. (And I still prefer mail spools which can be grepped.) But now I use Thunderbird on every system I own.

I finally broke down and bought VMWare Server. And it was a snap to configure and install Ubuntu (I need a Linux NFSv4 test machine) and Solaris Nevada 77. With the first one, I installed Ubuntu off of a DVD. With the Solaris install, I did it off of an ISO.

And I got to thinking, why do I need to dual boot at all? I've got WinXP and Nevada 77 dual booting, and why waste that additional space for Solaris. And, I already love how ZFS lets me preserve my data across Solaris re-installations. My plan is to nuke the raw Nevada partition and run my home directories straight off of the ZFS pools I have created.

The four disks are totally committed to ZFS. And I'm able to add them one at a time to the VMWare Workstation virtual machine. Until I get to the last one that is!

I just checked, it doesn't seem to be something specific with the 4th drive. I added the 4th drive okay as the 3rd drive in the system, but when I tried to add the 3rd drive as the 4th one in the system, I got the very mysterious "Fatal Application Error: reason unknown (type unknown)".

A quick search on google.com didn't reveal the issue. Perhaps I'll have to rephrase my query. Anyway, more to come as it develops.

Originally posted on Kool Aid Served Daily
Copyright (C) 2007, Kool Aid Served Daily



« July 2016