> Anyway, I've been running Plan 9 servers on ESX 3.5 for a year or so.
> It is ESX 3.5.0, 153875, not ESXi though.
I've been running on ESXi for about as long. But a CPU server, not a
workstation.
++L
>> if this is the case, it seems simple enough to fix. can anyone confirm?
>
> Yes, I saw that problem as well.
Too long ago, I didn't keep notes. But it's certainly possible.
++L
> interesting. i just tried it and it works. the admin tool
> (lab manager) wont allow the cd drive to be removed
> but assigning a .iso to it works as well.
>
> i wonder why?
probablly a problem with sdata.c.
- erik
> but assigning a .iso to it works as well.
I don't know if this is related to the empty CD-ROM drive problem or not,
but ESX3.5 FDD is painfuly slow. It takes a long time for a cpu
server to boot from floppy.
The booting process looked almost hanged up.
--
On Mon, Oct 5, 2009 at 3:38 PM, Skip
> On Sun, Oct 4, 2009 at 10:30 PM, erik quanstrom wrote:
>>> Do you have the CD-ROM drive attached to the VM while you boot it?
>>>
>>> I remember Plan 9 didn't start when you have an empty CD-ROM drive
>>> connected to the VM on ESX 3.5. So I removed the CD-ROM drive from VM's
>>
>> if this is t
On Sun, Oct 4, 2009 at 10:30 PM, erik quanstrom wrote:
>> Do you have the CD-ROM drive attached to the VM while you boot it?
>>
>> I remember Plan 9 didn't start when you have an empty CD-ROM drive
>> connected to the VM on ESX 3.5. So I removed the CD-ROM drive from VM's
>
> if this is the case,
> Do you have the CD-ROM drive attached to the VM while you boot it?
>
> I remember Plan 9 didn't start when you have an empty CD-ROM drive
> connected to the VM on ESX 3.5. So I removed the CD-ROM drive from VM's
if this is the case, it seems simple enough to fix. can anyone confirm?
- erik
On Sat, Oct 3, 2009 at 1:35 AM, Skip Tavakkolian <9...@9netics.com> wrote:
> the installation completed but it is unable to get past fossil
> startup;
Do you have the CD-ROM drive attached to the VM while you boot it?
I remember Plan 9 didn't start when you have an empty CD-ROM drive
connected to
> Somehow my laptop gets by using 32-bit IP addresses regardless of
> whether it's on my home Ethernet, a dialup connection (rare these
> days in the U.S., still sometimes useful overseas), or on a
> wireless LAN.
>
> My landline phone and my cellular phone both use base-10 digits,
> and even the
> Plan 9 does not work with either of the SCSI controllers in ESX(i) 3.5
> or less. Plan 9 does run on IDE drives just fine in ESX(i) 4. Plan 9
> panicks if you give it more than 2 CPUs on any of them. If you have
> any questions about getting Plan 9 to run in ESX(i) 4, let me know;
> I've done it.
> Which version of ESX are you using? ESX 3.5 provides two types of
> SCSI controllers.
> One is BusLogic and the other is LSI Logic which is the default. If
> you change the
> controller type to BusLogic, Plan 9 should install on ESX without problems.
yes, switching to BusLogic did the trick.
Plan 9 does not work with either of the SCSI controllers in ESX(i) 3.5
or less. Plan 9 does run on IDE drives just fine in ESX(i) 4. Plan 9
panicks if you give it more than 2 CPUs on any of them. If you have
any questions about getting Plan 9 to run in ESX(i) 4, let me know;
I've done it. But you w
> the address of a scsi device will have depends on the protocol
> used for disk access.
Somehow my laptop gets by using 32-bit IP addresses regardless of
whether it's on my home Ethernet, a dialup connection (rare these
days in the U.S., still sometimes useful overseas), or on a
wireless LAN.
My
Hi,
>> vmware esx only supports scsi virtual drives.
Which version of ESX are you using? ESX 3.5 provides two types of
SCSI controllers.
One is BusLogic and the other is LSI Logic which is the default. If
you change the
controller type to BusLogic, Plan 9 should install on ESX without problems
> Run in fear.
>
> Despite having a number which is just a wee bit higher than the
> things supported by the existing Plan 9 NCR/LSI SCSI driver,
> this is an utterly different beast, based on LSI's "Fusion"
> architecture, which in theory simplifies things vastly for the
> host over the old seque
> 1000/0030 LSI53C1020/1030 PCI-X to Ultra320 SCSI Controller
Run in fear.
Despite having a number which is just a wee bit higher than the
things supported by the existing Plan 9 NCR/LSI SCSI driver,
this is an utterly different beast, based on LSI's "Fusion"
architecture, which in theory s
On Thu, 2009-10-01 at 16:30 -0700, Skip Tavakkolian 9nut-at-9netics.com
|9fans| wrote:
> vmware esx only supports scsi virtual drives.
What makes you think that? According to the first page of
http://www.../pdf/vsphere4/r40/vsp_40_config_max.pdf
IDE controllers per virtual machine: 1
IDE
vmware esx only supports scsi virtual drives. it appears to be:
1000/0030 LSI53C1020/1030 PCI-X to Ultra320 SCSI Controller
so a new kernel with scsi support and a new cd image should fix it;
anything else to consider?
fyi, here's the pci output:
http://docs.google.com/View?id=ddxpv6x5_
18 matches
Mail list logo
