人気ブログランキング | 話題のタグを見る

Metaphorical Dream

ESX4.0 SerialConsole接続を断念2

んで、結論としては、
ESX4.0起動時のLoggingやらDeubugを
SerialConsole上に表示させることはできたんだけど、
その後は止まってしまい、CLI操作はできなかった。

(上の方の出力は省略。)
0:00:02:27.441 cpu0:4096)VMNIX: Logger: 475: sysboot: Loading VMkernel Module 'cbt'
0:00:02:27.568 cpu2:4106)Loading module cbt ...
0:00:02:27.617 cpu2:4106)Elf: 2320: symbols tagged as
0:00:02:27.705 cpu1:4106)FDS: 211: cbt
0:00:02:27.745 cpu1:4106)Mod: 2892: Initialization for cbt succeeded with module ID 53.
0:00:02:27.837 cpu1:4106)cbt loaded successfully.

0:00:02:27.894 cpu0:4096)VMNIX: Logger: 475: sysboot: iommu ...
0:00:02:27.960 cpu0:4096)VMNIX: Logger: 475: sysboot: Executing 'esxcfg-init -m'
0:00:02:28.135 cpu0:4096)VMNIX: Logger: 475: sysboot: resource-groups ...
0:00:02:28.212 cpu0:4096)VMNIX: Logger: 475: sysboot: Executing 'esxcfg-resgrp -r'
0:00:02:28.332 cpu0:4096)VMNIX: Logger: 475: sysboot: aslr ...
0:00:02:28.398 cpu0:4096)VMNIX: Logger: 475: sysboot: Executing 'esxcfg-advcfg -s 1262807599 /UserMem/UserMemASRandomSeed'
0:00:02:28.559 cpu1:4106)Config: 289: "UserMemASRandomSeed" = 1262807599, Old Value: 796023369, (Status: 0x0)
0:00:02:28.674 cpu0:4096)VMNIX: Logger: 475: sysboot: store-logs ...
0:00:02:28.746 cpu0:4096)VMNIX: Logger: 475: sysboot: Executing 'mkdir -p /vmfs/volumes/4adf452d-5cb2fabb-457a-002481e1b552/esxconsole-4adf447f-1a80-cbc6-1400-001b21413ad7/
0:00:02:28.926 cpu0:4096)VMNIX: Logger: 475: logs'
0:00:02:29.011 cpu0:4096)VMNIX: Logger: 475: sysboot: Executing 'cp /var/log/sysboot-vmkernel-boot.log /vmfs/volumes/4adf452d-5cb2fabb-457a-002481e1b552/esxconsole-4adf447f
0:00:02:29.190 cpu0:4096)VMNIX: Logger: 475: -1a80-cbc6-1400-001b21413ad7/logs/sysboot-vmkernel-boot.log'
0:00:02:29.803 cpu0:4096)VMNIX: Logger: 475: sysboot: Executing 'cp /var/log/sysboot-dmesg-boot.log /vmfs/volumes/4adf452d-5cb2fabb-457a-002481e1b552/esxconsole-4adf447f-1a
0:00:02:29.982 cpu0:4096)VMNIX: Logger: 475: 80-cbc6-1400-001b21413ad7/logs/sysboot-dmesg-boot.log'
0:00:02:30.561 cpu0:4096)VMNIX: Logger: 475: sysboot: Executing 'cp /proc/vmware/log /vmfs/volumes/4adf452d-5cb2fabb-457a-002481e1b552/esxconsole-4adf447f-1a80-cbc6-1400-00
0:00:02:30.740 cpu0:4096)VMNIX: Logger: 475: 1b21413ad7/logs/sysboot-vmkernel-late.log'
0:00:02:31.269 cpu0:4096)VMNIX: Logger: 475: sysboot: Executing 'dmesg > "/vmfs/volumes/4adf452d-5cb2fabb-457a-002481e1b552/esxconsole-4adf447f-1a80-cbc6-1400-001b21413ad7/
0:00:02:31.448 cpu0:4096)VMNIX: Logger: 475: logs/sysboot-dmesg-late.log" 2> /dev/null'
0:00:02:32.027 cpu0:4096)VMNIX: Logger: 475: sysboot: Executing 'umount /sysroot'
0:00:02:32.113 cpu0:4096)VMNIX: Logger: 475: sysboot: Executing 'mount -o rw /sysroot'
0:00:02:32.227 cpu0:4096)VMNIX: Logger: 475: sysboot: Executing 'cp /sysroot/etc/vmware/esx.conf /sysroot/etc/vmware/esx.conf.old'
0:00:02:32.423 cpu0:4096)VMNIX: Logger: 475: sysboot: Executing 'cp /etc/vmware/esx.conf /sysroot/etc/vmware/esx.conf'
0:00:02:32.862 cpu0:4096)VMNIX: Logger: 475: sysboot: Executing 'umount /sysroot'
0:00:02:33.060 cpu0:4096)VMNIX: Logger: 475: sysboot: Executing 'mount -o ro /sysroot'
0:00:02:33.174 cpu0:4096)VMNIX: Logger: 475: sysboot: status-term ...
0:00:02:33.246 cpu0:4096)VMNIX: Logger: 475: sysboot: Executing 'esxcfg-init --set-boot-progress done'
0:00:02:33.444 cpu0:4096)VMNIX: Logger: 475: sysboot: Executing '/usr/lib/vmware/bin/vmdumper -g Boot Successful'
0:00:02:33.564 cpu0:4096)Boot Successful
0:00:02:33.606 cpu0:4096)VMNIX: Logger: 475: sysboot: switchroot ...
0:00:02:33.680 cpu0:4096)VMNIX: Logger: 475: sysboot: Executing 'cp /messages.log /vmfs/volumes/4adf452d-5cb2fabb-457a-002481e1b552/esxconsole-4adf447f-1a80-cbc6-1400-001b2
0:00:02:33.860 cpu0:4096)VMNIX: Logger: 475: 1413ad7/logs/sysboot.log'
0:00:02:34.409 cpu0:4096)VMNIX: Logger: 475: sysboot: Executing 'umount /vmfs'
0:00:02:34.492 cpu0:4096)VMNIX: Logger: 475: sysboot: Executing 'umount /sys'
0:00:02:34.574 cpu0:4096)VMNIX: Logger: 475: sysboot: Executing 'umount /dev/pts'
0:00:02:34.661 cpu0:4096)VMNIX: Logger: 475: sysboot: Switching root
0:00:02:34.732 cpu0:4096)VMNIX: Logger: 475: sysboot: Executing 'mount -o bind /dev /sysroot/dev'
0:00:02:34.857 cpu0:4096)VMNIX: Logger: 475: sysboot: Executing 'chmod 0755 /sysroot/dev'
0:00:02:34.950 cpu0:4096)VMNIX: Logger: 475: sysboot: Executing 'mount -t proc proc /sysroot/proc'
0:00:02:35.064 cpu0:4096)VMNIX: Logger: 475: sysboot: Executing 'mount -t sysfs sys /sysroot/sys'
0:00:02:37.460 cpu1:4097)NMP: nmp_CompleteCommandForPath: Command 0x12 (0x4100040464c0) to NMP device "mpx.vmhba2:C0:T0:L0" failed on physical path "vmhba2:C0:T0:L0" H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
0:00:02:37.683 cpu1:4097)ScsiDeviceIO: 747: Command 0x12 to device "mpx.vmhba2:C0:T0:L0" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
0:00:02:37.844 cpu2:4098)NMP: nmp_CompleteCommandForPath: Command 0x12 (0x4100040464c0) to NMP device "mpx.vmhba2:C0:T0:L0" failed on physical path "vmhba2:C0:T0:L0" H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
0:00:02:38.068 cpu2:4098)ScsiDeviceIO: 747: Command 0x12 to device "mpx.vmhba2:C0:T0:L0" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
0:00:02:38.609 cpu0:4096)CosCommon: 2224: irq 6 vector 0x31 (host 0x59)
0:00:02:38.683 cpu0:4096)IDT: 1038: 0x31 for host
0:00:02:38.736 cpu0:4096)IOAPIC: 1320: 0x31 retriggerred
0:00:02:41.817 cpu0:4096)CosCommon: 2156: irq 6 vector 0x31 (host 0x59)
0:00:02:44.739 cpu0:4096)Uplink: 8098: Setting capabilities 0x300 for device vmnic0
0:00:02:44.825 cpu0:4096)Uplink: 8098: Setting capabilities 0x3c002b for device vmnic0
0:00:02:48.878 cpu1:4105)Net: 1489: Enabling NIC in the shadow vmkernel tcpip stack
0:00:02:48.964 cpu1:4105)Tcpip_Vmk: 69: Opening COSSharedPort port = 0x4100018dcb00
0:00:02:49.052 cpu1:4105)Tcpip_Vmk: 312: txDisp 0x4100b8029180, rxDisp 0x4100b801f080
0:00:02:49.144 cpu1:4105)Tcpip_Interface: 834: No NIC support for TSO
0:00:02:49.218 cpu1:4105)Tcpip_Interface: 841: No NIC support for checksum offloading
0:00:02:49.308 cpu1:4105)Tcpip_Interface: 847: No NIC support for Scatter-Gather DMA
0:00:02:49.398 cpu1:4105)Tcpip_Vmk: 186: vmk0: Ethernet address: 00:50:56:4e:96:f9
0:00:02:49.485 cpu1:4105)Tcpip_Interface: 902: ether attach complete
0:00:02:53.630 cpu0:4096)Tcpip_Socket: 979: index = 100094024, ip_addr = 0x500ba8c0, netmask = 0xffffff
0:00:02:53.738 cpu0:4096)Tcpip_Vmk: 167: TcpipUpdateCOSInetAddr: (ifidx=4) added 192.168.11.80/255.255.255.0 status 0x0
0:00:02:53.863 cpu0:4096)Tcpip_Socket: 1087: add dstAddr=0xba8c0, netMask=0xffffff, gwAddr=0x4 ifName=0xb8033830, ifNameLen=4
0:00:02:53.995 cpu0:4096)Tcpip_Vmk: 353: (0xbad0005) IPv4 COSShadow route update failed: op 0 dst=192.168.11.0/255.255.255.0 gw= ifp=vmk0
0:00:02:54.193 cpu0:4096)Tcpip_Socket: 1087: add dstAddr=0x0, netMask=0x0, gwAddr=0xfe0ba8c0 ifName=0x0, ifNameLen=0
0:00:02:54.313 cpu0:4096)Tcpip_Vmk: 353: (0x0) IPv4 COSShadow route update succeeded: op 0 dst=0.0.0.0/0.0.0.0 gw=192.168.11.254 ifp=
0:00:02:54.462 cpu0:4096)Tcpip_Socket: 1087: add dstAddr=0xfea9, netMask=0xffff, gwAddr=0x4 ifName=0xb8033830, ifNameLen=4
0:00:02:54.589 cpu0:4096)Tcpip_Vmk: 353: (0x0) IPv4 COSShadow route update succeeded: op 0 dst=169.254.0.0/255.255.0.0 gw= ifp=vmk0
0:00:02:57.678 cpu1:4106)World: vm 4223: 1098: Starting world vobd with flags 4
0:00:02:58.189 cpu2:4107)Loading module vmfs2 ...
0:00:02:58.241 cpu2:4107)Elf: 2320: symbols tagged as
0:00:02:58.331 cpu1:4107)FSS: 571: Registered fs vmfs2, module 36, fsTypeNum 0xf520
0:00:02:58.417 cpu1:4107)Mod: 2892: Initialization for vmfs2 succeeded with module ID 54.
0:00:02:58.512 cpu1:4107)vmfs2 loaded successfully.

0:00:02:58.805 cpu2:4105)FSS: 3647: No FS driver claimed device '4adf451c-44169a27-5348-002481e1b552': Not supported
0:00:03:02.920 cpu2:4105)Loading module pclassify ...
0:00:03:02.975 cpu2:4105)Elf: 2320: symbols tagged as
0:00:03:03.069 cpu1:4105)Mod: 2892: Initialization for pclassify succeeded with module ID 55.
0:00:03:03.166 cpu1:4105)pclassify loaded successfully.

0:00:03:03.474 cpu1:4105)World: vm 4231: 1098: Starting world vmware-vmkauthd with flags 4
0:00:03:04.727 cpu0:4096)VMNIX: VGA: 462: 1
0:00:03:04.775 cpu0:4096)VMNIX: VGA: 462: 2
0:00:03:04.825 cpu0:4096)VMNIX: VGA: 462: 3
0:00:03:04.871 cpu0:4096)VMNIX: VGA: 462: 4
0:00:03:04.934 cpu0:4096)VMNIX: VGA: 462: 5
0:00:03:30.516 cpu2:4107)Config: 289: "VMOverheadGrowthLimit" = -1, Old Value: -1, (Status: 0x0)
0:00:03:30.682 cpu2:4098)NMP: nmp_CompleteCommandForPath: Command 0x12 (0x410004136400) to NMP device "mpx.vmhba2:C0:T0:L0" failed on physical path "vmhba2:C0:T0:L0" H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
0:00:03:30.906 cpu2:4098)ScsiDeviceIO: 747: Command 0x12 to device "mpx.vmhba2:C0:T0:L0" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

んまぁでも、LoggingやDebugをゴリゴリ表示させる方法は理解できたかなと。。。
あんま意味ないけど(涙)

by mdesign21 | 2009-10-24 15:48 | IT系