XEN 4.1.0 PVOPS设置和启动中遇到的一些问题
2016-08-04 00:46
344 查看
前段时间由于一些特殊的需求,需要使用2.6.39版本的linux内核安装xen,遇到了一些问题,总结一下。
第一步下载内核,www.kernel.org,我当时用的是rc-3版本的内核。解压,OK。
第二步配置内核,进入解压后的内核目录,make menuconfig进入配置界面,具体配置参考
http://wiki.xensource.com/xenwiki/XenParavirtOps
第三步编译内核,修改grub,重启。
好了现在我们使用2.6.39内核启动了.
但此时无法启动xend,很费解。于是查log。
/var/log/xen/xend-debug.log:
cat: /sys/bus/scsi/devices/host0/vendor: No such file or directory
cat: /sys/bus/scsi/devices/host0/model: No such file or directory
cat: /sys/bus/scsi/devices/host0/type: No such file or directory
cat: /sys/bus/scsi/devices/host0/rev: No such file or directory
cat: /sys/bus/scsi/devices/host0/scsi_level: No such file or directory
cat: /sys/bus/scsi/devices/host1/vendor: No such file or directory
cat: /sys/bus/scsi/devices/host1/model: No such file or directory
cat: /sys/bus/scsi/devices/host1/type: No such file or directory
cat: /sys/bus/scsi/devices/host1/rev: No such file or directory
cat: /sys/bus/scsi/devices/host1/scsi_level: No such file or directory
cat: /sys/bus/scsi/devices/host2/vendor: No such file or directory
cat: /sys/bus/scsi/devices/host2/model: No such file or directory
cat: /sys/bus/scsi/devices/host2/type: No such file or directory
cat: /sys/bus/scsi/devices/host2/rev: No such file or directory
cat: /sys/bus/scsi/devices/host2/scsi_level: No such file or directory
cat: /sys/bus/scsi/devices/host3/vendor: No such file or directory
cat: /sys/bus/scsi/devices/host3/model: No such file or directory
cat: /sys/bus/scsi/devices/host3/type: No such file or directory
cat: /sys/bus/scsi/devices/host3/rev: No such file or directory
cat: /sys/bus/scsi/devices/host3/scsi_level: No such file or directory
cat: /sys/bus/scsi/devices/host4/vendor: No such file or directory
cat: /sys/bus/scsi/devices/host4/model: No such file or directory
cat: /sys/bus/scsi/devices/host4/type: No such file or directory
cat: /sys/bus/scsi/devices/host4/rev: No such file or directory
cat: /sys/bus/scsi/devices/host4/scsi_level: No such file or directory
cat: /sys/bus/scsi/devices/host5/vendor: No such file or directory
cat: /sys/bus/scsi/devices/host5/model: No such file or directory
cat: /sys/bus/scsi/devices/host5/type: No such file or directory
cat: /sys/bus/scsi/devices/host5/rev: No such file or directory
cat: /sys/bus/scsi/devices/host5/scsi_level: No such file or directory
cat: /sys/bus/scsi/devices/target2:0:0/vendor: No such file or directory
cat: /sys/bus/scsi/devices/target2:0:0/model: No such file or directory
cat: /sys/bus/scsi/devices/target2:0:0/type: No such file or directory
cat: /sys/bus/scsi/devices/target2:0:0/rev: No such file or directory
cat: /sys/bus/scsi/devices/target2:0:0/scsi_level: No such file or directory
cat: /sys/bus/scsi/devices/target3:0:0/vendor: No such file or directory
cat: /sys/bus/scsi/devices/target3:0:0/model: No such file or directory
cat: /sys/bus/scsi/devices/target3:0:0/type: No such file or directory
cat: /sys/bus/scsi/devices/target3:0:0/rev: No such file or directory
cat: /sys/bus/scsi/devices/target3:0:0/scsi_level: No such file or directory
搜了一下,在启动xend之前需要先通过xencommons进行初始化。
/etc/init.d/xencommons start
于是又出错误:
Starting xenstored…FATAL:Failed to open evtchn device: No such file or directory
...........
Could not start xenstored.
竟然还要先手动加载evtchn模块
modprobe xen-evtchn
再运行xencommons,成功。
启动xend,成功。
P.S. 加载模块的这一步,不一定只有evtchn一个。例如要用grant table 的话,还需要加载xen-gntalloc。等等。
如果还是无法启动,请关闭selinux;
本文出自 “尼古风锁丝愁过” 博客,请务必保留此出处http://smoke520.blog.51cto.com/9256117/1834151
第一步下载内核,www.kernel.org,我当时用的是rc-3版本的内核。解压,OK。
第二步配置内核,进入解压后的内核目录,make menuconfig进入配置界面,具体配置参考
http://wiki.xensource.com/xenwiki/XenParavirtOps
第三步编译内核,修改grub,重启。
好了现在我们使用2.6.39内核启动了.
但此时无法启动xend,很费解。于是查log。
/var/log/xen/xend-debug.log:
cat: /sys/bus/scsi/devices/host0/vendor: No such file or directory
cat: /sys/bus/scsi/devices/host0/model: No such file or directory
cat: /sys/bus/scsi/devices/host0/type: No such file or directory
cat: /sys/bus/scsi/devices/host0/rev: No such file or directory
cat: /sys/bus/scsi/devices/host0/scsi_level: No such file or directory
cat: /sys/bus/scsi/devices/host1/vendor: No such file or directory
cat: /sys/bus/scsi/devices/host1/model: No such file or directory
cat: /sys/bus/scsi/devices/host1/type: No such file or directory
cat: /sys/bus/scsi/devices/host1/rev: No such file or directory
cat: /sys/bus/scsi/devices/host1/scsi_level: No such file or directory
cat: /sys/bus/scsi/devices/host2/vendor: No such file or directory
cat: /sys/bus/scsi/devices/host2/model: No such file or directory
cat: /sys/bus/scsi/devices/host2/type: No such file or directory
cat: /sys/bus/scsi/devices/host2/rev: No such file or directory
cat: /sys/bus/scsi/devices/host2/scsi_level: No such file or directory
cat: /sys/bus/scsi/devices/host3/vendor: No such file or directory
cat: /sys/bus/scsi/devices/host3/model: No such file or directory
cat: /sys/bus/scsi/devices/host3/type: No such file or directory
cat: /sys/bus/scsi/devices/host3/rev: No such file or directory
cat: /sys/bus/scsi/devices/host3/scsi_level: No such file or directory
cat: /sys/bus/scsi/devices/host4/vendor: No such file or directory
cat: /sys/bus/scsi/devices/host4/model: No such file or directory
cat: /sys/bus/scsi/devices/host4/type: No such file or directory
cat: /sys/bus/scsi/devices/host4/rev: No such file or directory
cat: /sys/bus/scsi/devices/host4/scsi_level: No such file or directory
cat: /sys/bus/scsi/devices/host5/vendor: No such file or directory
cat: /sys/bus/scsi/devices/host5/model: No such file or directory
cat: /sys/bus/scsi/devices/host5/type: No such file or directory
cat: /sys/bus/scsi/devices/host5/rev: No such file or directory
cat: /sys/bus/scsi/devices/host5/scsi_level: No such file or directory
cat: /sys/bus/scsi/devices/target2:0:0/vendor: No such file or directory
cat: /sys/bus/scsi/devices/target2:0:0/model: No such file or directory
cat: /sys/bus/scsi/devices/target2:0:0/type: No such file or directory
cat: /sys/bus/scsi/devices/target2:0:0/rev: No such file or directory
cat: /sys/bus/scsi/devices/target2:0:0/scsi_level: No such file or directory
cat: /sys/bus/scsi/devices/target3:0:0/vendor: No such file or directory
cat: /sys/bus/scsi/devices/target3:0:0/model: No such file or directory
cat: /sys/bus/scsi/devices/target3:0:0/type: No such file or directory
cat: /sys/bus/scsi/devices/target3:0:0/rev: No such file or directory
cat: /sys/bus/scsi/devices/target3:0:0/scsi_level: No such file or directory
搜了一下,在启动xend之前需要先通过xencommons进行初始化。
/etc/init.d/xencommons start
于是又出错误:
Starting xenstored…FATAL:Failed to open evtchn device: No such file or directory
...........
Could not start xenstored.
竟然还要先手动加载evtchn模块
modprobe xen-evtchn
再运行xencommons,成功。
启动xend,成功。
P.S. 加载模块的这一步,不一定只有evtchn一个。例如要用grant table 的话,还需要加载xen-gntalloc。等等。
如果还是无法启动,请关闭selinux;
本文出自 “尼古风锁丝愁过” 博客,请务必保留此出处http://smoke520.blog.51cto.com/9256117/1834151
相关文章推荐
- XEN 4.1.0 PVOPS设置和启动中遇到的一些问题
- XEN 4.1.0 PVOPS设置和启动中遇到的一些问题
- 【XEN学习笔记】XEN 4.1.0 PVOPS设置和启动中遇到的一些问题
- Windows XP Embedded (XPE) ramdisk 启动遇到的一些问题和解决方法--part2
- VS2015启动遇到的一些问题和解决方法
- 以前遇到的一些小问题,grub,编译kernel喝mysql的字符设置
- iOS启动图片配置及遇到的一些问题解决
- 自定义控件通过属性设置TextSize时遇到的一些问题
- 关于Flask mega-tutorial遇到的一些问题-三(Flask_mail服务器及邮箱设置)
- mac os x 设置 jenkins开机启动遇到的问题
- eclipse 虚拟机启动参数的一些问题及设置
- Android Studio 之 导入Eclipse项目常见问题及解决方案 在将Eclipse做的Android项目成功导入Android Studio 后,启动生成,遇到一些问题,现总结如下:
- Mysql 启动时遇到的一些问题及解决办法
- xen 4.3.0 创建Guest OS遇到的一些问题
- 有关UISwitch设置大小遇到的一些问题
- Java编译和Tomcat启动遇到的一些问题
- tomcat启动遇到的一些问题 闪退、报错等
- win7 64bits 设置ODBC遇到的一些问题 “未发现数据源…” “驱动程序和应用程序之间体系结构不匹配……”
- ubuntu设置asterisk开机启动遇到的问题
- powerdesigner经常遇到的一些问题及如何设置