One of my zone is stuck in down state, not able to boot it or halt it .. not even detach .. is there any way to recover without rebooting the whole system ( global zone ) ? (3 Replies)
Hi All,
I'm preparing to migrate some servers from vscsi to pass-thru NPIV. I am planning to have the SAN team move the exact LUNs from vio1/vio2 to those two VWWN through NPIV.
My question is on the partition itself.. right now, let's say I have hdisk0/1/2/3/4 that are part of datavg. They... (2 Replies)
Hi,
I want to change from vscsi to npiv. Is it possible to use both on the same adapter, so we can change the systems one by one, or must we place a second FC adapter in the VIO servers?
Thanks,
Ronald (2 Replies)
Hello,
I have a VIOS System and would like to do mapping some hdisks, hdisk160 until hdisk165 to a vSCSi Adapter. I try to do this in the oem_setup_env like the following:
for i in $(lspv | grep hdisk* | awk {'print $1'};
do
mkdev -V $i -p vhost20
done
There where a mapping with... (4 Replies)
If you're familiar with vscsi mappings thru a VIO Server, you are probably aware, on an AIX 6.1 Client LPAR, that:
print cvai | kdbcan provide useful information to you.... like VIO Server name & vhost #. But, "cvai" does not appear to be part of the Kernel Debugger in AIX 5.3.
My question is... (3 Replies)
Hello,
When I assigned CDROM from IVM (VIOS) to LPAR and then running cfgmgr i get the following message on the client lpar
#cfgmgr
cfgmgr: 0514-621 WARNING: The following device packages are required for device support but are not currently installed.
devices.vscsi.disk
searching... (0 Replies)
Hi everybody,
I have Power5 server with 4 internal hdisks each of 70Gb.
VIOS server was installed via Virtual I/O Server Image Repository on the HMC.
HMC release - 7.7.0
VIOS rootvg installed on 2 disk(these disks merged to one storage pool during VIOS install process),and 2 others hdisks... (2 Replies)
Discussion started by: Ravil Khalilov
2 Replies
LEARN ABOUT DEBIAN
oss_midiloop
oss_midiloop(7) OSS Devices oss_midiloop(7)NAME
oss_midiloop - Loopback MIDI driver.
DESCRIPTION
The loopback midi driver makes it possible to create special purpose virtual midi devices based on user land server processes.
INTRODUCTION
MIDI loopback devices are like named pipes or pseudo terminals. They are grouped in client and server device pairs. The server side device
must be open before the client side device can be opened.
SERVER SIDE DEVICE
The server side device is used by some special application (such as a software based MIDI synthesizer) to receice MIDI events from the
applications that want to play MIDI.
CLIENT SIDE DEVICE
Client applications such as MIDI players open the client side device when they need to play some MIDI stream (file). The client side device
behaves like any "ordinary" MIDI device. However it cannot be opened when there is no program connected to the server side.
COMPATIBILITY ISSUES
MIDI loopback devices differ from "normal" MIDI devices because an application is needed at the both ends of the loop. The loop device will
return a "Connection reset by peer" error (ECONNRESET) error. Applications designed to be used as loopback based server applications
can/should use this error (returned by read or write) as an end-of-stream indication.
OPTIONS
o midiloop_instances:
Specifies how many loopback client/server MIDI device pairs to be created.
Values: 1-16
Default: 1
KNOWN PROBLEMS
None
FILES
/etc/oss4/conf/oss_midiloop.conf Device configuration file
AUTHOR
4Front Technologies
16 December 2012 oss_midiloop(7)