Originally posted by: PontiacGeronimo
hello Wouter,
thx for your notes.
I do use virtual ISO repos on VIOS (since many years). Indeed, until now, I only used static mappings client-server vscsi adapters.
I had never need to use physical DVD drive (all do on ISOs, including zero setup of a new sever - installing VIOS from HMC nimol, etc.)
But here is something really strange - I can't explain why newly recreated virtual scsi adapter on server (so completely removed from VIOS - gone from hypervisor configuration, once when created again with the same slot ID is seen still used by old client, which in fact has no vscsi device anymore)
Let's say initially you have:
on VIOS: vhost0 (slot id 100, any/any)
on client LPAR1 (LPAR ID 5): vscsi0 (mapped to VIOS vscsi adapter in slot id 100 on VIOS)
All works fine.
Now, on LPAR1 system I did:
umount virtual drive
rmdev -dl vscsi0 -R
and from HMC dynamicaly unconfigured/removed the virtual (client) scsi adapter) successfully - cfgmgr does not configure vscsi0/cd0 on LPAR1 anymore.
Next, on the VIOS side I did:
unloadopt -release -vtd vtopt0
rmvdev -vtd vtopt0
rmdev -dev vhost0 -recursive
and dynamically unconfigured/removed the VIO server scsi adapter (slot ID 100) from hypervisor (cfgdev -dev vio0 does not configure it anymore - it was vhost0 and is gone)
And now the most interesting is, that when I add new server scsi adapter dynamically (reusing now free slot 100), new vhost0 is configured on VIOS but... is again seen mapped to LPAR ID5 (on lsmap -all) - and it is not true. I expected it is new server scsi adapter VIOS never used yet, besides the client LPAR ID has no VSCSI adapter anymore as was removed before so why VIOS says untruth?
Is it VIO software bug? Something is cheating VIOS?
#AIX-Forum