On Nov 3, 2005, at 10:50 AM, Phil Smith III wrote:
Has anyone successfully moved data on a SCSI disk from a Linux
guest under z/VM to an Intel machine simply by redefining the LUN?
That is, if you have the right Shark and the right kinds of
connections to both the zSeries and an Intel machine
data. This will cause things to break.
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Phil Smith III
Sent: Thursday, November 03, 2005 8:50 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Moving SCSI disk on z/VM to Intel
Has anyone successfully moved data
Presumably, z/VM can use the volume as an EDEV without having a
VOL1 label or allocmap. If that does work, then it could be
ATTACHed to a Linux guest as a 9336. Certainly a real 9336
can be ATTACHed to a guest without having a label or allocmap.
I DO KNOW, and can tell you this works,
]
Sent: Friday, February 22, 2002 5:01 AM
Subject: Re: VM for Intel?
[...] The shocked look on their young faces combined with a further
half-hour discussion on the
subject served as ample evidence that these members of the VMware team
were certainly not inspired
by the pre-existence of mainframe
A couple of days ago, IBM gave two presentations to some of the staff here.
The first presentation was on Linux and they mentioned VM on Intel. There
was nothing mentioned on the differences between it and VM on a zSeries.
The second presentation was on VM. I asked the VM presenter about
We need a Lingua Franca for hypervisors.
Consider the command
hcp attach F200-F202 mylinux
Makes perfect sense, though the handle is a zSeries I/O range.
What would that mean to INTeL? Might look more like
Did I miss something? That address range is valid on
on 390 Port [mailto:[EMAIL PROTECTED]] On Behalf Of
Paul Kaufman
Sent: Thursday, February 21, 2002 9:10 AM
To: [EMAIL PROTECTED]
Subject: VM for Intel
A couple of days ago, IBM gave two presentations to some of the staff
here.
The first presentation was on Linux and they mentioned VM on Intel
On Thu, Feb 21, 2002 at 10:12:32AM -0600, cmead wrote:
Actually z/VM (at least in the 2.3 release) IS available on Intel.
The trick is that the Intel box must be running the Flex/ES code
which
provides emulation of a 390 box on an Intel platform. Then any IBM
operating system including VM,
We need a Lingua Franca for hypervisors.
Consider the command
hcp attach F200-F202 mylinux
Makes perfect sense, though the handle is a zSeries I/O range.
What would that mean to INTeL? Might look more like
Did I miss something? That address range is
It sure would be nice, if in their presentations, IBM pointed out
the benefits of zSeries. Why don't they?
Paul:
A very good point. We have come to assume that our mainframe customers
are familiar with our partitioning capability, so that we don't talk
about it much. Don't forget that neither
/2002 07:57 AM ---
Jim Elliott [EMAIL PROTECTED]@VM.MARIST.EDU on 02/19/2002
08:50:15 PM
Please respond to Linux on 390 Port [EMAIL PROTECTED]
Sent by:Linux on 390 Port [EMAIL PROTECTED]
To:[EMAIL PROTECTED]
cc:
Subject:Re: VM for Intel?
But that was my
I apologize for not following the whole thread here, but in case it has not
been mentioned, the following should be pointed out to further
differentiate z from x as far as virtualization goes: The zSeries
architecture and hardware design contains facilities not found in the Inel
machine.
Mark:
Conceptually, there are bound to be similarities. From a code base point
of view, there is no feasible means of integration, if only because z/VM
is Assembler and PL/X. Of course, the architectural differences present a
much more significant barrier to having any commonality in the code
for the converse.
Mark Post
-Original Message-
From: David Goodenough [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 19, 2002 3:59 PM
To: [EMAIL PROTECTED]
Subject: Re: VM for Intel?
But VMware and z/VM are entirely separate. They both do much the same
thing, in fact one could almost say
: Tuesday, February 19, 2002 3:59 PM
To: [EMAIL PROTECTED]
Subject: Re: VM for Intel?
But VMware and z/VM are entirely separate. They both do much the same
thing, in fact one could almost say that z/VM and its ancestors inspired
VMware, but VMware is not produced by IBM, rather - as the item says
This makes me again suggest that we have a
forum for discussing an open specification for hypervisor interaction.
There was at one time a FreeVM-L discussion list. The purpose was
not to produce any code (at least, not specifically any hypervisor
code) but rather form a specification
16 matches
Mail list logo
