In the qemu network, a bridge network is required to connect the Virtual Machine Nic to the real physical network. Generally, the qemu bridging network is implemented by using the tap virtual network card. For details, refer to the relevant documentation. Here only describes how to configure the bridging network:
1. Install the tap-related tools
Sudo apt-Get install UML-utilities
2. Configure the bridge
Sudo VI/etc/Network/interfaces
Modify to the following:
Auto lo
3. Create a tap network Sta
. We just need to put them in a location that qemu expects them to be.
Copy the relevant files to the qemu directory to enable the qemu VM. (PS: If you have installed qemu, you only need to confirm that there are the following two files in the/usr/share/qemu/directory. If not, you have to manually copy the files)
sudo cp pc-bios/vgabios-qxl.bin /usr/share/qemu/sudo cp pc-bios/pxe-e1000.bin /usr/share/qemu/cd ..
Now, qemu with SPICE support is installe
Enhancement
Load-based grouping
E1000 vnic(Virtual network interface controller virtual network card)Enhanced
1.4Availability
Built on Vmware ha(High Availability high availability)Windows failover Cluster
Scalability improvement of VMware ha
Monitor VMware ha healthcheck and running status
VMware Fault Tolerance Enhancement
Drs for VMware ha and fault tolerance(Distributed resource scheduler Distributed Resource Planning)
Enha
, the system already has eth0 information. For this new Nic, udev will automatically name it eth1 (accumulation principle), so after your system starts, the Network Card Name you see in ifconfig is eth1.
Here, eth0 is in/etc/udev/rules.d/70-persistent-net.rulesDefined
# This file was automatically generated by the /lib/udev/write_net_rules# program, run by the persistent-net-generator.rules rules file.## You can modify it, as long as you keep each rule on a single# line, and change only the val
The CentOS system is cloned from VMware and then reset to eth0.
Problem: After cloning CentOS6.4 with VMware, it is found that only eth1 is in the system, and/etc/sysconfig/network-scripts/under only, ifcfg-eth0 file, although can access the Internet, but cannot set static IP.
Ifconfig eth0
Eth1: error fetching interface information: Device not found
Solution: vi/etc/udev/rules. d/70-persistent-net.rules is displayed as follows:
# PCI device 0x8086: 0x100f (
, in the third case above, You have to insert printk printing in the source code to further determine the actual time consumption process.
The Linux kernel startup analysis after my last reduction is as follows:
Total kernel Start Time: 6.188 s
Key time-consuming part:
1) initialization of core components such as 0.652 s-Timer, IRQ, Cache, And Mem Pages2) 0.611 s-kernel and RTC Clock Synchronization3) 0.328 s-calculate the total consumption of Calibrating Delay4 CPU cores)4) 0.144 s-calibration
0
Else
Echo "error: no interface specified"
Exit 1
Fi
4. Create an empty tap network shutdown script (to avoid a warning when the VM is shut down)
Sudo VI/etc/qemu-ifdown
The content is as follows:
#! /Bin/sh
After the configuration is complete, run the following command to start qemu and directly use the bridge without other configuration (filename is the image file path ):
Sudo qemu-system-x86_64-hda$ Filename-Net Nic, model = e1000, ma
bytes of packet headers using the Mac in UDP method. can refer to this articletest drops in a virtual environmentFirst experiment:Iperf Tests whether to drop packets.Iperf (Iperf is a network performance test tool, which is the speed test under Linux), two generotor start to fill traffic at full speed. Then we started to calculate the number of drops per point in Figure 1 based on statistics. The results are as follows:Because the various configurations of table one are different, the total for
My computer is winn7 64-bit. It is difficult to install the vmwarevm and install the Mac lion on it, but it cannot be connected to the network.
I searched the internet and some netizens said I was looking for it. in the vmx file, add ethernet0.virtualdev = "e1000" to it. I found the file and found that there was such a sentence, but I still couldn't access the network.
Some people on the Internet say that Windows 7 cannot set the network connection
Recently, the company has a project to modify Intel's NIC Driver. Because all devices in the company are using newer NICs, take the e1000e part of the kernel for analysis. The e1000 is an old driver used to support older intel Nic devices. For the comparison between the two parts, I have an article on lwn.ArticleFor more information, see http://lwn.net/articles/278016 /.
Kernel version: 3.0.13
Source code Directory: Driver/NET/e1000e/
Linux release
Synchronization3) 0.328 S-computing calibrating delay (total consumption of 4 CPU cores)4) 0.144 S-calibration APIC clock5) 0.312 S-calibration migration cost6) 3.520 S-Intel e1000 Nic Initialization
Next, we will analyze and resolve the above parts one by one.
(3) Next, perform specific optimization.
CELF has already proposed a complete set of startup optimization solutions for Embedded Linux for consumer electronic products. However, due to differe
performances are supported for reference only. We can see that para-receivalized Disk Driver provide a good speedup versus the standard receivalized ide controller. Anyway, both approaches are far behind the native scores.
Net speed now:
In this case the paravirtualized Network Driver makes an huge difference: while it can't touch native speed, it is way ahead of the virtualized e1000 Nic adapter. the rtl8139 was benchmarked for Pure curiosity, and
The latest moblin V2.0 netbook image can be downloaded and tested. This version modifies some bugs and adds new features.
Current download
Http://mirrors.kernel.org/moblin/releases/test/beta/images/moblin-netbook-beta-refresh-20090616-001.img
MD5 Verification Code
Http://repo.moblin.org/moblin/releases/test/beta/images/md5sum.txt
Introduction
Http://moblin.org/documentation/test-drive-moblin/using-moblin-live-image
Problem
Known issues: http://moblin.org/documentation/test-drive-moblin/know
bridging settings. Here, you need to read the documents of the software, which will be of great help.The above is the most basic implementation method of KVM. We hope you can read more documents to learn more and more flexible functions.
BTW:The reason for the poor performance of the original disk has been found. The previous method is to use-hda disk. IMG method to use the virtual disk. Now, after the version is updated,-drive file =/home/lm/KVM/WINXP. IMG, cache = writeback to use virtual dis
tap is the corresponding second partNET Nic: Create a new virtual machine NIC interface, using the method:-net Nic[,vlan=n][,macaddr=mac][,model=type][,name=name][,addr=addr][,vectors=v]Create a new NIC device and connect to the specified VLAN, macaddr to specify the MAC address for itmodel Specifies the type of NIC, QEMU can emulate multiple types of NIC devices, such as the default NIC for e1000 on the VIRTIO,PC architecture, and you can use the qe
192.168.91.100 192.16 8.91.254;cobbler syncsystemctl start dhcpd #启动dhcpManagement distroCobbler Import--path=/misc/cd/--name=centos7.3cobbler distro listSet individual properties of cobblerCp/root/ks7.cfg/var/lib/cobbler/kickstarts/cobbler profile Add--name=centos7.3-x86_64-desktop--distro= centos7.3-x86_64--kickstart=/var/lib/cobbler/kickstarts/ks7.cfgcobbler Profile Listcobbler profile Remove--name= Centos7.3-x86_64Then we create a new virtual machine and select the host mode of a network se
directory, and the properties for creating the file permissions and names of the device files are customizable;Udev has rules files:/etc/udev/rules.d/Modify the network card device name; vim/etc/udev/rules.d/70-persistent-net; to be effective, first uninstall the network card module, in the installation can be, that modprobe-r e1000 in Modprobe e1000uname command:-r: The release number of the kernel;-N: hostname;-A: Displays all information; RAMDisk
The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion;
products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the
content of the page makes you feel confusing, please write us an email, we will handle the problem
within 5 days after receiving your email.
If you find any instances of plagiarism from the community, please send an email to:
info-contact@alibabacloud.com
and provide relevant evidence. A staff member will contact you within 5 working days.