Sponsored Content
Operating Systems Solaris Compatible NICs for Solaris 9 (9/05) x86 Post 302070417 by Godmode on Tuesday 4th of April 2006 03:32:18 PM
Old 04-04-2006
Buy realtek or 3com nic
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Print Servers compatible with Solaris

Does anyone have any advice on what print servers to use with Solaris I used to use intel but they dicontinued the model we used. I would just use lpadmin to set them up . Any advice on this would be very helpful. (2 Replies)
Discussion started by: xmildx
2 Replies

2. UNIX for Dummies Questions & Answers

Solaris 8 x86

Hi There, I search a lot across the board but didn't find answer... first of all... I installed the Companion CD. So Kde is supposed to work... I ran the script to have it in my login screen, and it's there... but when I enter it, it only kicks me to the login screen once... (1 Reply)
Discussion started by: Erythro73
1 Replies

3. Solaris

solaris on x86

hi, need help! i've installed solaris 9 on my x86 box...problems with kdmconfig. here what i have: 1- Dell 17" Flat monitor ( 31kHz-80kHz horizontal and 56 Hz-76Hz Vertical) 2- Matrox Millenium G550 card what choices do i have to made? best regards thank you in advance (1 Reply)
Discussion started by: hmaiida
1 Replies

4. UNIX for Dummies Questions & Answers

Running Solaris Sparc Apps on X86 Solaris

I know that Sun make s a version of Solaris for Sparc platforms and also an x86 (Intel/AMD) release of Solaris. Can an application that runs on Solaris/Sparc also run on a PC running the x86 release of Solaris? Would a different release be required or any re-compling of the application? jim (1 Reply)
Discussion started by: stocksj
1 Replies

5. Solaris

UFS on solaris 10, compatible with solaris 8?

we have a server runnning solaris 10 (sparc) this server is attached the a SAN (HP EVA) we created 23 LUN's and filled them with data. the we unmounted them and tried to attach the LUN's to a solaris 8 system. this is where thing get strange... when we just mount the LUN's it works... (9 Replies)
Discussion started by: robsonde
9 Replies

6. UNIX for Advanced & Expert Users

solaris 8 libraries compatible solaris 10

Hello, For a company I have to check if it is possible to migrate there environment from a solaris 8 to solaris 10. Is there a tool with which I can check if the libraries running now on the 8 are compatible with the 10? Kind regards (3 Replies)
Discussion started by: chelle007
3 Replies

7. Shell Programming and Scripting

Is tcsh 100% compatible with the plain-old csh [on Solaris 9]

Hi folks There are about 200 csh scripts (I didn't wrote them). Do all those scripts run with tcsh without modification? Is tcsh 100% compatible with the plain-old csh? $ which csh /usr/bin/csh $ which tcsh /usr/bin/tcsh $ uname -a SunOS purzelse 5.9 Generic_117171-07 sun4u sparc... (2 Replies)
Discussion started by: slashdotweenie
2 Replies

8. Solaris

Solaris: clnt_create fails on solaris x86

Hi, I am facing an issue with Solaris x86 machine Machine Details: uname -a SunOS sol10-64 5.10 Generic_137138-09 i86pc i386 i86pc .............................. Description: I am trying to register a programm with proramm ID 300760 with version number 1, and tryint to create a... (0 Replies)
Discussion started by: DivakarAdari
0 Replies

9. Solaris

is there an veritas volume manager version compatible with solaris x86 machine?

i heard some where veritas volume manager wont work on solaris x86. i have installed vmware into my 32bit xp machine. i am planning to learn veritas.. is there an veritas volume manager version compatible with solaris x86 machine? (2 Replies)
Discussion started by: chidori
2 Replies
VDEQ(1) 						      General Commands Manual							   VDEQ(1)

NAME
vdeq - Virtual Distributed Ethernet wrapper for QEMU/KVM virtual machines SYNOPSIS
vdeq qemu [ --mod octalmode ] QEMU_OPTIONS -net vde[,vlan=n][,sock=socketpath][,port=n] QEMU_OPTIONS vdeq kvm [ --mod octalmode ] KVM_OPTIONS -net vde[,vlan=n][,sock=socketpath][,port=n] KVM_OPTIONS vde{qemu_name} [ --mod octalmode ] QEMU_OPTIONS -net vde[,vlan=n][,sock=socketpath][,port=n] QEMU_OPTIONS OLD SYNOPSIS
vdeq qemu [ --mod octalmode ] [ -sock socketpath [ ,socketpath [ ,... ] ] ] [ qemu_args ] vde{qemu_name} [ -sock socketpath [ ,socketpath [ ,... ] ] ] [ qemu_args ] DESCRIPTION
vdeq is a wrapper to start a QEMU/KVM virtual machine connected to a VDE network. It uses the qemu/kvm -tun-fd parameter to set up the connection with a vde_switch. The command vdeq qemu -b c -hda=sampledisk starts a qemu machine which boots from the sampledisk image and has a ne2000 ethernet interface connected to the standard vde_switch. The command vdeq kvm -b c -hda=sampledisk starts a kvm machine which boots from the sampledisk image and has a ne2000 ethernet interface connected to the standard vde_switch. It is also possible to create symbolic links to the vdeq executable to have a simpler command. If the link has a name that begins with vde the remaining part of the name is taken as the qemu command. For example if vdeq is linked to vdeqemu: vdeqemu -b c -hda=sampledisk starts qemu as above. If vdeq is linked to vdekvm: vdekvm -b c -hda=sampledisk starts kvm with the same parameters. The new syntax is consistent with the new Qemu 0.8.0 network parameters. Using vdeq is possible to specify a vde interface in the same way as user,tap or socket interfaces. The sock= parameter can be used to use a specific socket. Please note that what qemu names as vlan is not related to the 802.1q VLAN managed by the vde_switch. port= can be used to specify the port of the switch, otherwise the first allo- catable port is assigned. The following command run a qemu VM with two ethernet interface connected to the standard switch and to the switch with local socket "/tmp/my.ctl", port 10, respectively vde qemu -net nic,vlan=0 -net nic,vlan=1 -net vde,vlan=0 -net vde,vlan=1,sock=/tmp/my.ctl,port=10 vdeqemu -net nic,vlan=0 -net nic,vlan=1 -net vde,vlan=0 -net vde,vlan=1,sock=/tmp/my.ctl,port=10 The following command run a kvm VM with two ethernet interface connected to the standard switch and to the switch with local socket "/tmp/my.ctl", port 10, respectively vde kvm -net nic,vlan=0 -net nic,vlan=1 -net vde,vlan=0 -net vde,vlan=1,sock=/tmp/my.ctl,port=10 vdekvm -net nic,vlan=0 -net nic,vlan=1 -net vde,vlan=0 -net vde,vlan=1,sock=/tmp/my.ctl,port=10 The old syntax can be used with Qemu 0.8.0 but all the vde interfaces are assigned to vlan 0. vdeq qemu -sock /tmp/vde.ctl,/tmp/my.ctl -b c -hda=sampledisk vdeqemu -sock /tmp/vde.ctl,/tmp/my.ctl -b c -hda=sampledisk both start qemu with one ethernet interface connected both to the standard switch and to the switch with local socket "/tmp/my.ctl". OPTIONS
--mod octalmode, specify the mode for comm socket. -sock socketpath, specify the UNIX socket to be used by local programs for joining the VDE. The default value is "/tmp/vde.ctl" It is also possible to indicate several socketpath (comma separated, no blanks): in this case several interfaces are defined. The first socketpath is connected to the first ne2k interface and so on. -h, -help, --help print a Usage help. NOTE
Qemu has changed its syntax for networking (cvs Nov.15 2005). As a temporary solution use vdeoq and vdeoqemu instead of vdeq and vdeqemu if you are running a qemu with the old syntax. By default qemu uses the same MAC address for every virtual machine, so if you plan to use several instances of qemu be sure to explicitly set a different MAC address for each virtual machine. While generating your address beware to not use broadcast/multicast reserved MACs, ethernet rules say: the multicast bit is the low-order bit of the first byte, which is "the first bit on the wire". For example 34:12:de:ad:be:ef is an unicast address, 35:12:de:ad:be:ef is a multicast address (see ETHERNET MULTICAST ADDRESSES section in http://www.iana.org/assignments/ethernet-numbers for more informations). NOTICE
Virtual Distributed Ethernet is not related in any way with www.vde.com ("Verband der Elektrotechnik, Elektronik und Informationstechnik" i.e. the German "Association for Electrical, Electronic & Information Technologies"). SEE ALSO
vde_switch(1), vde_plug(1), vde_plug2tap(1), dpipe(1). AUTHOR
VDE is a project by Renzo Davoli <renzo@cs.unibo.it> Virtual Distributed Ethernet December 6, 2006 VDEQ(1)
All times are GMT -4. The time now is 06:13 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy