Sponsored Content
Full Discussion: Jumpstart Issues Solaris 10
Operating Systems Solaris Jumpstart Issues Solaris 10 Post 302265092 by DukeNuke2 on Friday 5th of December 2008 03:16:22 PM
Old 12-05-2008
do you have more than one network interfaces? maybe you try to boot from the wrong nic... test this with:

Code:
ok show-nets
ok cd /path/to/your/nic
ok .properties

and check the mac you find with .properties with the one in your ethers file. also check the obp setting for local-mac is set to "true".
 

9 More Discussions You Might Find Interesting

1. Solaris

jumpstart Solaris 10 on Solaris 9 server

I just built a jumpstart server on a Solaris 9 sun box and have had no problems jumpstarting other sol9 boxes using the custom rules. I've also copied a Solaris 10 image onto that same solaris 9 server and have had problems loading Solaris 10. These boxes will go directly to the manual OS install... (5 Replies)
Discussion started by: salty
5 Replies

2. Solaris

Jumpstart solaris

Hi all , I am trying to jumpstart ( webstart) solaris 9 on E2900 ( client) using the DVD of a V440 server ( jumstart server). I did the setup for the V440 as follows : cleaning up preexisting install client "XXXXXXX" removing XXXXXXXfrom bootparams removing /etc/bootparams, since it is... (14 Replies)
Discussion started by: ppass
14 Replies

3. Solaris

Jumpstart Issues

Hi all, I'm having an issue with jumpstart that I haven't seen before. After booting the server and selecting F12 to boot it from the network it finds the jumpstart profile that has been set up for it and proceeds with the build until I get the following error: SunOS Release 5.10 Version... (4 Replies)
Discussion started by: Chains
4 Replies

4. Solaris

Jumpstart issues, help please.

1.I wish to perform a Jumpstart installation, the client being Ultra 5 Sparc and jumpstart Server being ultra 20 AMD system. 2.I think i have done all the procedures right, like putting the mac address of Sparc 1 to /etc/ethers, creating sysidcfg file, and profile file: 3.When I issued the boot... (7 Replies)
Discussion started by: saagar
7 Replies

5. Solaris

Jumpstart Solaris 10

Hello everyone, I tried to install solaris 10 using the command # boot net - install. I take the image correctly but when you start installing the Operating system installation takes a long (4 hours I have left and not advancing but not send me any errors), it can be seen from the following: ... (7 Replies)
Discussion started by: yflores
7 Replies

6. Solaris

Issue after jumpstart with Solaris 10 u7

I am performing this installation on a Sun T5220. There is an aftermarket Adaptec StorageTek raid controller card installed. I have created the raid array, and it is referred to as c1t0d0. Here is the profile I have created: install_type initial_install system_type server cluster SUNWCXall... (4 Replies)
Discussion started by: msarro
4 Replies

7. Solaris

Jumpstart Issues With T5220

I'm trying to use a V210 (sun4u) configured as a jumpstart server to flash install a number of T5220's (sunv4). The Facts: V210 - Solaris 10 (September 2010 Release / not patched) T5220's - Archive's created using prior (unknown) version of solaris 10. Flar -i <archive name> shows the... (6 Replies)
Discussion started by: Celtic_Monkey
6 Replies

8. Solaris

Jumpstart Solaris 10

I have a laptop and need to build an Oracle Linux kickstart server and a Solaris Jumpstart server that can build sparc and x86 systems. Is the best way to create a dual boot from grub for Oracle Linux and Solaris x86? Can the Oracle Kickstart be used as a Jumpstart to build both Solaris 10... (2 Replies)
Discussion started by: Gian
2 Replies

9. Solaris

Solaris 10 JumpStart Server

Hello, Can anyone share a good online article/tutorial on how to properly set up JumpStart server for Solaris 10? Thanks, Regards. (3 Replies)
Discussion started by: NewSolarisSquad
3 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 04:27 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy