solusvm xen虛擬機offline無法遠程

創建的VG為 xenLVg1,
查看
 vgdisplay
有
======================================
--- Volume group ---
  VG Name               xenLVg1
  System ID            
  Format                lvm2
.
.
.
=====================================
創建的虛擬機為LVM
產看LVM
lvdisplay
===============================
--- Logical volume ---
  LV Name                /dev/xenLVg1/vm101_img
  VG Name                xenLVg1
  LV UUID                TzrbBV-o3dr-fJ52-jVle-5d2y-8ZXd-CjCt9u
  LV Write Access        read/write
  LV Status              available
  # open                 0
  LV Size                30.00 GB
  Current LE             7680
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:0
  
  --- Logical volume ---
  LV Name                /dev/xenLVg1/vm101_swap
  VG Name                xenLVg1
  LV UUID                6YUot1-2uv2-c4ls-zBgQ-dHfp-rgOY-36Ifvx
  LV Write Access        read/write
  LV Status              available
  # open                 0
  LV Size                1000.00 MB
  Current LE             250
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:1

==================================
虛擬機創建在 /dev/xenLVg1/vm101_img 里面
虛擬機的配置文件在/home/xen/vm101/vm101.cfg
/home/xen/vm101/ 下還有ifcfg-eth0，以及mnt文件夾

手動啟動虛擬機：
 xm create /home/xen/vm101/vm101.cfg
錯誤：
Error: Kernel image does not exist: /boot/solus-vmlinuz

還需要：
All set! needed to run: php /usr/local/solusvm/includes/xenkernel.php

===================================================
php /usr/local/solusvm/includes/xenkernel.php
PHP Warning:  PHP Startup: Unable to load dynamic library '/usr/lib/php/modules/dbase.so' - /usr/lib/php/modules/dbase.so: cannot open shared object file: No such file or directory in Unknown on line 0

Making SolusVM initrd...

Modulefile is /etc/modprobe.conf
Setting kernel links...

Kernel setup completed.
================================================================================

在solusvm里 Boot 虛擬機就可以了。

無法遠程 ssh

進入 console 查看IP：
系統啟動不起來
ERROR opening /dev/console: No such file or directory
Trying to use fd 0 instead.
WARNING: can't access (null)
exec of init ((null)) failed!!!: Bad address
Kernel panic - not syncing: Attempted to kill init!

查看vm101.cfg
===========================
less vm101.cfg
kernel     = '/boot/solus-vmlinuz'
ramdisk    = '/boot/solus-initrd.img'
#bootloader = '/usr/bin/pygrub'
extra      = ''
memory     = 512
hostname   = 'Centos'
cpu_weight = 256
name       = 'vm101'
vif        = ['ip=173.231.59.83, vifname=vifvm101.0, mac=00:16:3e:ed:d6:76']
vnc        = 0
vcpus      = 4
vncviewer  = 0
serial     = 'pty'
disk       = ['phy:/dev/xenLVg1/vm101_img,sda1,w', 'phy:/dev/xenLVg1/vm101_swap,sda2,w']
root       = '/dev/sda1 ro'
vm101.cfg (END)
=========================================================================

看到一個問題，0 字節的template
到 slave 的/home/solusvm/xen/template 看到與maste同名的系統 CentOS-XX.tar.gz 為0字節
手動下載，改為與maste同名。
在solusvm面板中重裝系統試試。
console 可以連得上了。
遠程依然不行。

在console 中看到 IP是正確綁定的。

在xen的主機，即slave查看IP信息
================================================

ifconfig
eth0      Link encap:Ethernet  HWaddr XXXX
          inet addr:X.X.X.X  Bcast:X.X.X.  Mask:255.255.255.248
          inet6 addr: X::X:X:X:X/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:3974 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3591 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:512181 (500.1 KiB)  TX bytes:779228 (760.9 KiB)

lo        Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:8 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:560 (560.0 b)  TX bytes:560 (560.0 b)

peth0     Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF 
          inet6 addr: X::X:X:X:X/64 Scope:Link
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:119923 errors:0 dropped:0 overruns:0 frame:0
          TX packets:89809 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:139299326 (132.8 MiB)  TX bytes:9798431 (9.3 MiB)
          Interrupt:16 Memory:fb5e0000-fb600000

vifvm101.0 Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF 
          inet6 addr: X::X:X:X:X/64 Scope:Link
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:13 errors:0 dropped:0 overruns:0 frame:0
          TX packets:566 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:500
          RX bytes:580 (580.0 b)  TX bytes:29432 (28.7 KiB)

vif0.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF 
          inet6 addr: X::X:X:X:X/64 Scope:Link
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:89737 errors:0 dropped:0 overruns:0 frame:0
          TX packets:119902 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:9791693 (9.3 MiB)  TX bytes:139234160 (132.7 MiB)

virbr0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF 
          inet addr:192.168.122.1  Bcast:192.168.122.255  Mask:255.255.255.0
          inet6 addr: X::X:X:X:X/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:13 errors:0 dropped:0 overruns:0 frame:0
          TX packets:31 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:580 (580.0 b)  TX bytes:6582 (6.4 KiB)

xenbr0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF 
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:1989 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:651213 (635.9 KiB)  TX bytes:0 (0.0 b)
==========================================================================
經查知：xenbr0默認應該是和eth0綁定
/etc/xen/scripts/network-bridge start bridge=xenbr0 netdev=eth0 vifnum=0

 虛擬機里的 防火墻？ 查證，關了

xm list               #查看各個域狀態
xm shutdown web_001   #關閉web_001這個虛擬機
xm console web_001    連接web_001控制臺,連接到虛擬機上面可以用組合鍵  ctrl + ] 鍵切換到物理機

XM命令:
    xm create vm1 #其中vm1 為虛擬機的配置文件，位于/etc/xen/vm/vm1
    xm create -c vm1 #如果需要啟動控制臺，則可以運行命令
    xm list #可以列出所有的虛擬機
    xm console <domid> #可以顯示某虛擬機的控制臺
    xm reboot|shutdown <domid> #可以重起和關閉id 為domid 的虛擬機
    xm destroy <domid> #可以銷毀id 為domid 的虛擬機
    xm console fc5 #從終端或控制臺登錄正在運行的虛擬操作系統
    xm save <DomId> <File> # 存儲正在運行的虛擬操作系統的狀態
    xm restore <File> # 喚醒虛擬操作系統
    xm pause <DomId> #停止正在運行的虛擬操作系統
    xm unpause <DomId> #激活停止的虛擬操作系統
    xm mem-set <DomId> <Mem> #調整虛擬平臺/虛擬操作系統的占用內存
    xm shutdown 虛擬操作系統的Name或DomID #關閉被虛擬的系統
    xm destroy <DomId> #立即停止虛擬的系統 （重要）;
    xm vcpu-set <DomId> <VCPUs> #調整虛擬平臺及虛擬操作系統的虛擬CPU個數
    xm top 或 xentop # 查看虛擬系統運行的狀態
    xm save VM1 VM1.chk # stop the domain and save its current state into a file called VM1.chk
    xm restore VM1.chk #resume execution of this domain

ISO 上傳到  solusvm的
master 和 slave 的  /home/solusvm/xen/iso下。