KVM support on suse

 
Thread Tools Search this Thread
Special Forums UNIX and Linux Applications KVM support on suse
# 1  
Old 04-26-2013
KVM support on suse

Is KVM supported on suse SLES10
Login or Register to Ask a Question

Previous Thread | Next Thread

1 More Discussions You Might Find Interesting

1. SuSE

How do I enable 3D support and change the bass and treble in SuSE 9.2?

I have a ATI Radeon 9600 Pro gfx card and was trying to figure out how to enable 3d support in linux. I had downloaded the ATI driver before and installed it and I ended up having to reinstall linux because it told me I was supposed to do something to some file that I didn't do so it restarted and... (3 Replies)
Discussion started by: CTroxtell21
3 Replies
Login or Register to Ask a Question
IFCFG-VLAN(5)						       Network configuration						     IFCFG-VLAN(5)

NAME
ifcfg-vlan - virtual LAN interface configuration SYNOPSIS
/etc/sysconfig/network/ifcfg-vlan* Virtual LANs (802.1q) To setup a vlan interface you need a configuration file that contains at least the mandatory ETHERDEVICE variable with the real interface used for the virtual LAN. Further, it may contain the optional VLAN_ID variable that specifies the VLAN ID. By default and when the VLAN_ID variable is not set, the number at the end of the interface name is the VLAN ID. Preferably the interface name and the configuration file follow the VLAN interface name scheme (type), that is either: ifcfg-vlan<VLAN-ID> (e.g. ifcfg-vlan42) or ifcfg-name.<VLAN-ID> (e.g. ifcfg-eth0.42) The VLAN-ID can be also 0-padded (e.g. ifcfg-vlan0042 or ifcfg-eth0.0042). Also in case of custom names, trailing digits are interpreted as VLAN-ID by default (e.g. ifcfg-dmz42). When VLAN_ID is set in the config, the interface name have any name (e.g. ifcfg-foobar). Note: The drawback of custom interface names and VLAN_ID usage is, that a rename of the interface is required and that they violate the name scheme. The real interface will be set UP automatically and doesn't need a config file in case of a physical interface. But without a config file YaST will consider this interface as unused, if will not follow hotplug events and you're unable to apply any settings, e.g. ETH- TOOL_OPTIONS. To avoid that, provide an config file with at least STARTMODE='auto'. The rest of the VLAN interface IP and routes configuration do not differ from ordinary interfaces. See also man ifcfg and man routes for details. EXAMPLES
Sets up vlan3 vlan interface on top of eth0: ifcfg-vlan3 STARTMODE='auto' ETHERDEVICE='eth0' IPADDR='192.168.3.27/24' Sets up eth0.3 vlan interface on top of eth0: ifcfg-eth0.3 STARTMODE='auto' ETHERDEVICE='eth0' IPADDR='192.168.3.27/24' Sets up lan1 vlan interface with ID 42 on top of eth0: ifcfg-lan1 STARTMODE='auto' ETHERDEVICE='eth0' VLAN_ID='42' IPADDR='192.168.3.27/24' BUGS
Please report bugs at <http://www.suse.de/feedback> AUTHOR
Christian Zoz <zoz@suse.de> Michal Svec <msvec@suse.cz> Bjoern Jacke Mads Martin Joergensen <mmj@suse.de> Michal Ludvig <mludvig@suse.cz> Marius Tomaschewski <mt@suse.de> SEE ALSO
routes(5), ifcfg(5), ifup(8). sysconfig August 2004 IFCFG-VLAN(5)