双/多线路需要增加 原路返回路由 /bin/ip route flush table 100 /bin/ip route add default via 电信网关 dev 电信网卡设备名称 src 电信IP table 100 prio 50 /bin/ip rule add from 电信IP table 100 /bin/ip route flush table 200 /bin/ip route add default via 联通网关 dev 联通网卡设备名称 src  联通IP table 200 prio 50 /bin/ip rule add from 联通IP table 200  修改上面对应的IP，网关和设备名称，将上面内容写入/etc/rc.local开机执行

Linux下网通、电信、教育多出口策略路由配置详解 一、处理流量分割的问题；二、解决双线负载均衡的问题。原文如下：1、流量分割首先是如何保证：回应来自某一个ISP的数据包时，仍然使用相同的ISP。让我们先定义一些符号。令第一块网卡的名字叫eth1，而第二块网卡叫做eth2；然后设置网卡1的IP地址为221.200.0.2（CNC分配网址），网卡2 的IP地址为58.56.0.2（CTC分配网址）；ISP1（联通）网关地址为221.200.0.1，ISP2（电信）网关地址为58.56.0.1；最后，ISP1（联通）的网络地址为211.200.0.0/30，ISP2（电信）的网络地址为58.56.0.0/30。额外创建两个路由表，T1 和T2 ，加入到/etc//iproute2/rt_tables中。然后如下设置两个路由表中的路由：ip route add 211.200.0.0/30 dev eth1 src 221.200.0.2 table T1ip route add default via 221.200.0.1 table T1ip route add 58.56.0.0/30 dev eth2 src 58.56.0.2 table T2ip route add default via 58.56.0.1 table T2没什么大不了的，不过是建立了通向该网关的一台路由，并使之成为默认网关，分别负责一个单独的上行流，并且为这两个ISP都作这样的配置。要指出的是，那条网络路由是必要条件，因为它能让我们找到那个子网内的...

JSP环境集成包一键配置(JspStudy)软件简介JspStudy集成JDK+tomcat+Apache+mysql，JSP环境配置一键启动。无需修改任何配置即可迅速搭建支持JSP的服务器运行环境。纯绿色解压即可，支持系统服务和非服务两种启动方式，自由切换。控制面板更加有效直观地进行控制程序的启停。JspStudy将复杂的JSP环境配置简单化。JspStudy集成以下组件：JDK 1.7_51Tomcat 7.0.50MySQL 5.5.36Apache 2.4.7PHP 5.4.26&5.2.17SQL-Front 5.1Xdebug 2.2.3mysql-connector-java-5.1.28-bin.jarjstl-1.2.jarMySQL数据库用户名：root，密码root，安装后请重新设置密码。自带mysql驱动mysql-connector-java-5.1.28-bin.jar放在tomcat/lib下。特别注意1. 为了减少出错安装路径不得有汉字、空格及特殊符号等；注册服务时如有防火墙拦截，请选择全部允许。2. 端口问题无法启动时，请使用菜单『环境端口检测』进行端口检测。3. 可通过菜单『卸载相关服务』进行卸载相关服务。4. 在『启动』、『停止』、『重启』三个启停按钮上右键可以有选择地进行启停，左键将控制全部的启停。5. 此为JSP环境集成包，需要php集成包的请到www.phpstudy.net下载phpStudy。6. a...

在生产环境中，从centos6.0以来，kvm虚拟机时钟配置这块，都使用的是localtime，工作很正常。123456  <clock offset='localtime'>    <timer name='rtc' tickpolicy='catchup' track='guest'>      <catchup threshold='123' slew='120' limit='10000'/>    </timer>    <timer name='pit' tickpolicy='delay'/>  </clock>但是在升级到centos6.5以后，发现虚拟机启动以后，时间和宿主机相差8个小时，折腾了一段时间，后来将时区强制设置成timezone方式，解决了这个问题。123  <clock offset="timezone" timezone="China/Shanghai">     <timer name='rtc' tickpolicy='catchup' track='guest'/>  </clock>

Quick Start Guide 目录 [隐藏] 1 介绍1.1 安装要求1.1.1 oVirt Engine的要求1.1.2 主机/节点 (oVirt 节点, Fedora主机, CentOS 主机)1.1.3 存储和网络1.1.4 支持的虚拟机操作系统2 安装 oVirt2.1 安装 oVirt Engine 到(Fedora / Red Hat Enterprise Linux / CentOS)2.2 安装主机/节点2.2.1 安装 oVirt Node（节点）2.2.2 在Fedora 或 CentOS的主机中安装3 访问 oVirt Engine3.1 登录到管理员门户4 配置 oVirt4.1 配置数据中心4.2 配置集群4.3 配置网络4.4 配置主机4.4.1 配置 oVirt 节点的主机4.4.2 加入 Fedora 或 CentOS 的主机4.5 配置存储4.5.1 创建NFS 数据域4.5.2 创建iSCSI 数据域4.5.3 创建 FCP 数据域4.5.4 附加 ISO 域4.5.5 上传 ISO 镜像5 创建虚拟机5.1 创建一个安装Fedora的虚拟机5.1.1 创建安装Windows 7 的虚拟机5.1.1.1 使用VirtIO磁盘的安装方式5.1.1.2 通过IDE硬盘安装5.1.2 后续步骤Post Install Additions5.1.2.1 驱动5.2 使用模板5.2.1 创建基于Fedora的模板5.2.2 复制 Red Hat Enterprise Linux 虚拟机5.2.3 创建基于Windows 的模板5.2...

The oVirt Project is pleased to announce the availability of its sixth formal release, oVirt 3.5.oVirt is an open source alternative to VMware vSphere, and provides an excellent KVM management interface for multi-node virtualization.To find out more about features which were added in previous oVirt releases, check out the oVirt 3.4 release notes, oVirt 3.3 release notes, oVirt 3.2 release notes and oVirt 3.1 release notes. For a general overview of oVirt, read the oVirt 3.0 feature guide and the about oVirt page.Contents [hide] 1 oVirt 3.5 Release Notes1.1 Live Merge1.2 Import Storage Domain1.3 Advanced Foreman Integration1.4 Enhanced Authentication, Authorization and Accounting Support1.5 New PatternFly Interface1.6 Advanced Scheduling with Optaplanner1.7 Other Enhancements1.7.1 Infra1.7.2 Networking1.7.3 Integration1.8 Install / Upgrade from Previous Versions1.8.1 Fedora / CentOS / RHEL1.9 oVirt Live1.10 oVirt Node1.11 [Click to Show/Hide]Known Issues1.12 [Click to Show/H...

Example using SPICE and QXL for improved Graphics experience in the guest This example is based on qemu-kvm (0.15.0) as installed in Fedora 15.Will first show how to do this manually, and second how to do it using the virt-manager tool.For extensive details on SPICE, visit http://spice-space.org Manually, using qemu-kvm command line directly The simplest part is adding the qxl graphics device to the guest. By adding -vga qxl:# /usr/bin/qemu-kvm -m 1024 -name f15 -drive file=/images/f15.img,if=virtio -vga qxl You'll see a normal SDL window pop up, and if you poke inside the guest you'll find that X is using the qxl device to display:$ lspci ... 00:02.0 VGA compatible controller: Red Hat, Inc. Device 0100 (rev 03) $ grep QXL /var/log/Xorg.0.log [ 15.878] (II) qxl: Driver for QXL virtual graphics: QXL 1 However, this is not enough to use SPICE. We need to enable the spice server in qemu-kvm. We also need a client to view the guest. So first be sure the client is installed...

We are pleased to announce the first release of KVMGT project. KVMGT is the implementation of Intel GVT-g technology, a full GPU virtualization solution. Under Intel GVT-g, a virtual GPU instance is maintained for each VM, with part of performance critical resources directly assigned. The capability of running a native graphics driver inside a VM, without hypervisor intervention in performance critical paths, achieves a good balance of performance, feature, and sharing capability. KVMGT is still in the early stages:Basic functions of full GPU virtualization works; guests can see a full-featured vGPU.We ran several 3D workloads such as lightsmark, nexuiz, urbanterror and warsow.Only Linux guests are supported so far, and PPGTT must be disabled in guest through a kernel parameter(see README.kvmgt in QEMU).This drop also includes some Xen specific changes, which will be cleaned up later.Our end goal is to upstream both XenGT and KVMGT, which shares ~90% logic for vGPU devi...

�����ڵ�����Ȩ�鿴����־

�����ڵ�����Ȩ�鿴����־