Hi Adam, Very true - but in my case I needed to dedicate individual NICs to virtual machines, and also had a PCMCIA device that the virtual machines needed dedicated access to. Seem like a "virtual machine" hypervisor needs to address real hardware access - just like mainframe VM does. Providing "access to a network" is not the same as attaching a dedicated NIC.
Still not sure why they don't support PCMCIA devices - it doesn't seem like that should be so hard. Just build a pipe between the virtual machine and the hardware and let the host pass through all of the I/O's. Michael Coffin, VM Systems Programmer Internal Revenue Service - Room 6030 1111 Constitution Avenue, N.W. Washington, D.C. 20224 Voice: (202) 927-4188 FAX: (202) 622-6726 [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> -----Original Message----- From: Adam Thornton [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 30, 2003 11:35 AM To: [EMAIL PROTECTED] Subject: Re: z/VM and VMware On Tue, 2003-09-30 at 10:30, Coffin Michael C wrote: > I looked at VMWare and liked it, I liked it a lot - but it doesn't > "really" present a virtual machine with virtual hardware like > mainframe VM does, at least not 100%. Among the problems (which were > significant for my intended use of it) are the fact that there is NO > support for PCMCIA devices, and a NIC cannot be dedicated to a > "virtual machine". Networking is handled by having the hose own the > NIC, run TCP/IP, and set up a private LAN between the virtual machines > and the host's TCP/IP. It can also provide a transparent bridge mode, where your VMWare guest looks like it's on the same subnet as the host. This is usually good enough, although there's some MAC madness that can be a bit confusing. Adam
