Virtual Pc Nightmare!

Printable View

06-11-2005, 06:48 AM
Israel

Virtual Pc Nightmare!

Ok, I'm having problems multiply trying to get the net set-up on Virtual PC. I just talked with my ISP cause my internet connection would crash on Windoze as I'm setting up Knoppix....which isn't a big deal, but of course there's no net on the Linux side either. My Isp said they were detecting 2 devices! 2 completely different MAC addresses. So I understand why they shut my down (that's one way to "uncap" a cable connection, run 2 two modems together which is illegal) Problem is I'm not using two modems and I don't know how to get Knoppix to have the same Mac address as Windoze so my provider won't cut me off.

My other problem is I go into "Knoppix-Configure-Create a Persistent Image" and it says Knoppix can't be saved to disk. I tried the Command Line Instructions I found in the e-book I'm using and they didn't work either:

"knoppix@ttyp0[knoppix]$ /usr/sbin/mkpersistenthome"

Now my net keeps crashing on Windoze when I'm not running VM or trying to configure Knoppix. I just talked with my ISP and they seem to think there's something wrong with my network card now. Which would make sense, now that the whole PC seem to sporadically crash on occasion. I wonder if this isn't from where I tried to configure the network card on Knoppix? What a nightmare, I really like the features I've seen on the live-cd, but I'm begining to wonder if this is even worth it now.
06-11-2005, 07:01 AM
Harry Kuhman

Re: Virtual Pc Nightmare!

Quote:

Originally Posted by Israel

and I don't know how to get Knoppix to have the same Mac address as Windoze so my provider won't cut me off.

The same thing that will solve 90% of all networking problems posted here, and a lot of other problems too. Use an inexpensive DSL/cable router. It presents one MAC adddress to the cable company. You can set it's MAC address on the cable company side to match the MAC address of your Windows machine, so they don't even know that you switched it in. You then can run several computers that all share the cable connection (Google search on NAT if you want details). You also get the benefit of a herdware firewall, important when you run Windows, and a 4 port ethernet switch, and frequently wireless capability as well. I paid over $100 for my first wired 4 port router about 5 years ago. You can now frequently get wireless ones for $10 or less after rebate (I saw two diferent wireless ones including a Linksys in major chains for $5 Memorial Day Weekend).
06-11-2005, 07:14 AM
Israel

I actually have a Belkin Wireless Router on lay-away right now. But I'm pretty broke so it's going to be a while. So...., have you actually acomplished this with Virtual PC? It seems like VMware has more bugs than my back-yard....
06-11-2005, 04:13 PM
Harry Kuhman

Quote:

Originally Posted by Israel

I actually have a Belkin Wireless Router on lay-away right now. But I'm pretty broke so it's going to be a while. So...., have you actually acomplished this with Virtual PC? It seems like VMware has more bugs than my back-yard....

No experience with VPC. I can tell you a good router will resolve the mac address problem.

Unfortunately, there are a couple of issues with your lay-away: One is that it prevents you from buying elsewhere or other items when a better deal shows up (Like the $5 Linksys last week at Best Buy). Why lay-away at all, did you think all the routers were going to be sold? Would have been far better to save your money and buy when you had enough saved. But the bigger problem is that, of the seven or eight routers I've tried, the only one that would not DHCP handshake with Knoppix, and the only one that kept disconnecting from my DSL provider, is a Belkin. I hope your Belkin doesn't end up doing the same, but I can't get Belkin to live up to the Warranty and I do not recommend Belkin routers.
06-12-2005, 07:30 AM
Israel

I have a Belkin on lay-away cause:
A.- There's no Best Buy here for about an hour and fifteen minutes drive. ...And by the time I shell out the gas for a 2 and a half hour drive(there and back) its no longer a 5 dollar router.

B.- I like Belkin better and I've read their reviews, their new routers are supposed to be way faster, and reach a lot farther than any Lynksys. Really they've been in the wireless game longer too. They developed those first Bluetooth adapters where you could actually use dail-up through your cell phone before Lynksys ever made wireless. And even now those old bluetooth cellphones can reach farther than the Lynksys routers.(30ft. vs. 15ft) I don't know, I would rather by something once than get a 5 dollar router and then want a better one.

But if it was down the street I'd probably think about it.

I have a different ISP too, but if I do run into the same problems then I'll just take the router back to Wal-mart and try to hitch a ride to Best Buy I guess...until then I'll just take my chances. Are you talking about a $5 802.11A?, 802.11B?, or 802.11G?
06-12-2005, 09:45 PM
tbielawa

Quote:

Ok, I'm having problems multiply trying to get the net set-up on Virtual PC. I just talked with my ISP cause my internet connection would crash on Windoze as I'm setting up Knoppix....which isn't a big deal, but of course there's no net on the Linux side either. My Isp said they were detecting 2 devices! 2 completely different MAC addresses. So I understand why they shut my down (that's one way to "uncap" a cable connection, run 2 two modems together which is illegal) Problem is I'm not using two modems and I don't know how to get Knoppix to have the same Mac address as Windoze so my provider won't cut me off.

This is not a problem with Knoppix or with Windows. This is a problem with the way in which you have configured your virtual machine. You have set the network adpater in your virtual machine to use the network card in your physical machine. Under this setting it will look to your ISP as if you have two machines connected together with a hub. If you try to change the MAC address of the virtual machine to match the physical machine, your problems with your ISP will go away, however you will likely break your network connection completely. The correct solution is to change the virtual network adpater setting to NAT. This will cause the virtual network adpater to be connected through a NAT server to the physical adpater, solving the problems with your ISP. With this setting your virtual and physical machines will be unable to see each other however. If you need to enable networking between the two machines, then you will have to go back to the original setting and get a NAT enabled router.
06-13-2005, 12:18 AM
Harry Kuhman

Quote:

Originally Posted by tbielawa

.... Under this setting it will look to your ISP as if you have two machines connected together with a hub. .....

Interesting. I understand now wnat is happening and hope that your fix solves the problem. It does seem to confirm my original belief that a good router that works with Linux would have resolved the problem too, it would have seen the 2 mac system as a hub and served both macs fine. Where does Virtual PC come up with a MAC address for the virtual system though, does it just generate one randomly?
06-13-2005, 12:35 AM
tbielawa

Quote:

Originally Posted by Harry Kuhman

Where does Virtual PC come up with a MAC address for the virtual system though, does it just generate one randomly?

I don't know how they are generated. I have been working with dozens of virtual machines in the last week, and all of the MAC addresses have been of the form 00:03:FF:XX:D8:27 where XX started at 0 an incremented for each new machine. Two machines even had the same MAC address (ethernet didn't work on either if they were both running at the same time), but that may have been my own fault as I deleted one machine than manually put it back again.
06-14-2005, 11:48 AM
Israel

Quote:

The correct solution is to change the virtual network adpater setting to NAT

Ok....I'm new to Virtual PC, where is that?

By the way, I can't get Knoppix to save it's configuration to the Virtual drive the way it would to a real drive. I've read how to do it on a regular machine, but it just won't save that way on Virtual PC. Any tips for that???
06-14-2005, 04:45 PM
tbielawa

Quote:

Originally Posted by Israel

Quote:

The correct solution is to change the virtual network adpater setting to NAT

Ok....I'm new to Virtual PC, where is that?

There is only one page of settings for each virtual machine you create. The settings on each virtual machine are independent of one another. To get to the settings page click on the machine you want to setup in the Virtual PC Console and click the Settings button. Network settings are about 3/4 of the way down the page. I suggest you read the Virtual PC documentation completely as you can do some pretty powerful things between the settings page and the Virtual Disk Wizard. You can have between 0 and 3 hard drives and between 0 and 4 network adapters. People new to Virtual PC seem to have a hard time grasping how you can add or remove a network adapter or a hard drive from a completely a virtual computer with the click of a radio button.

Quote:

Originally Posted by Israel

By the way, I can't get Knoppix to save it's configuration to the Virtual drive the way it would to a real drive. I've read how to do it on a regular machine, but it just won't save that way on Virtual PC. Any tips for that???

Vritual PC works just like a real machine. No tricks here. My guess is that either you didn’t install a virtual hard drive (the Virtual Machine Wizard makes you install one, so this isn’t too likely), you removed the virtual hard drive (if you didn’t know where to find the network settings, this doesn’t sound too likely), or you have installed the hard drive, but did not partition and/or format it. If the hard drive is installed, partitioned and formatted it will act just like a “real drive” on a “regular machine,” so check that, and then make sure you didn’t miss a step in the instructions.
06-14-2005, 04:48 PM
tbielawa

Virtual PC and Knoppix 3.8.1 and up

I can see the question comming, so here's the real answer.

Knoppix 3.8.1 and up (3.9 is current as of this writing) does not work properly with Virtual PC. Knoppix incorrectly detects the network adapter as a D-Link adapter, and installs the wrong networking drivers causing the virtual machine to crash. If you search for the solution to this problem you will find: “If networking crashes you machine, don’t use networking then,” which is just not a good solution. The correct solution is as follows.

1.Boot Knoppix with the nodhcp cheatcode. This prevents Knoppix from trying to access the network adapter and crashing before you have a chance to fix things
2. As root (of course), execute the following commands:
3. modprobe –r de4x5
4. modprobe tulip
5. ifconfig eth0 up
6. pump –i eth0
7. Enjoy network access.
06-15-2005, 10:03 AM
Israel

Thanks for the advice, I actually don't have a book for Virtual PC (the software was given to me). But I do think I have a good grasp on saving a Virtual Drive. I've installed Linux Mepis and Suse on Virtual drives and no problems saving them what so ever. I'm at work, but I'll let you know how it goes. Thanks!
06-15-2005, 03:59 PM
tbielawa

Quote:

Originally Posted by Israel

I actually don't have a book for Virtual PC

The complete documentation for Virtual PC is available from the help menu.
06-17-2005, 08:45 AM
Israel

Ok...., I should've got that one. My bad, I'm always working 3rd shift when I post these so you'll have to forgive my brain runs a little slower at these hours.

I'm still having trouble with the saving part. I have a book by O'Reily that say to save your configuration to disk normally you just go to
"Knoppix-Configure-Save Knoppix Configuration" or go to the Konsole and type:

Code:

/usr/sbin/saveconfig

I tried both of these a couple times and never could get it to save. Any tips?
06-17-2005, 02:24 PM
tbielawa

Are you getting any error messaages? If so post those here. I still suspect that the drive is not formatted. Make sure you can mount the partition that you're trying to save to.
06-19-2005, 08:50 AM
Israel

All it said was:

Quote:

The KNOPPIX Configuration could NOT be saved:

Nothing more...Nothing less....
06-19-2005, 04:02 PM
tbielawa

You still haven't said if you can mount the partion.
06-21-2005, 11:23 AM
Israel

Ok, as if you couldn't tell....I'm a noob. But I'm not really sure how you would mount the partition. (Nor, the entirity of what that means, other than creating a partion you would "mount" to the real hardrive?) With all the other versions of Linux I tried installing they took the first time, no tweeks or fixes. I'll take it then, since I don't know for sure, I probably haven't done that. How would you go about that in Knoppix or with VM?
06-21-2005, 04:41 PM
tbielawa

Before you can use a disk you must partition it, then format the partitions (create filesystems on the partitions), and then mount the filesystems. Knoppix doesn’t do any of these steps for you, because it is intended to be run as a Live CD, and it doesn’t touch the hard drives in the process (except for SWAP partitions).

Partitioning the disk means just what it says; you break the disk into smaller pieces, which are usually independent of each other. When you partition the disk, you usually provide a rough idea of what the filesystem type will be. Partitioning can be performed with cfdisk, but it sounds like you already understand this part.

Next you need to format the partitions. Formatting the partitions creates a filesystem on the partitions that the OS can read and write. My guess is that you skipped from here stright to the last step. To create a filesystem in Linux, use the mkfs command. Ext2 is the most common filesystem in Linux, and although Ext3 is newer and better, Ext2 will cause you fewer problems if you don’t know what you’re doing (I don’t think all versions of Knoppix have a kernel with built in Ext3 support, so you can’t use bootfrom=/dev/hda1 if hda1 has an Ext3 filesystem). To format hda1 with an Ext3 filesystem the command would be “mkfs.ext3 /dev/hda1”.

Finally you need to mount the filesystem before you can use it. Mounting a filesystem is basically the process by which you tell the OS that you want to use a particular filesystem, and you give it a name that you can refer to it by. In Windows this is where you assign a drive letter like D: to a filesystem. In Linux it will be something like /mnt/hda1. To mount /dev/hda1 the command would be “mount /dev/hda1 /mnt/hda1” assuming that the directory /mnt/hda1 exists. Filesystems can also be mounted in Knoppix by clicking on the icon of the partition that the filesystem exists on, on the KDE Desktop.

Once the filesystem is mounted, you can access it at the mount point, in this example /mnt/hda1.