Prev: multi-threaded data access
Next: change the address of ld.linux-so in a dynamically linked process
From: Barry Margolin on 23 Dec 2009 21:14
In article <hgt3a2$2jd$1(a)news.xmission.com>,
gazelle(a)shell.xmission.com (Kenny McCormack) wrote:

> (Meta note: Please, no guff to the effect that I "should" have posted
> this in the other thread. I have my reasons for starting a new thread.)
>
> OK, so I found the GUI control panel for changing the network settings.
> Basically, it gives these options for configuring the device (en0):
> 1) Manual
> 2) DHCP
> 3) DHCP with manual address
> 4) BOOTP
> 5) Off
>
> Now, the problem is this: I am running a virtual machine, using VmWare
> Fusion, and I want the VM to connect to my cable modem. The point, of
> course, is that only one machine can be connected to the cable modem,
> and there is a race condition between the VM and the real machine to see
> who gets the attention of the cable modem. That is, who gets attention first.
>
> Unfortunately, lately, the Mac seems to be winning the race (before, it
> was working correctly -> the VM was winning). Nothing changed to cause
> this to change, but obviously something did (if you see what I mean...)

I don't understand how the VM ever won the race in the first place.
Doesn't the Mac get its IP while it's booting? But the VM isn't started
up until after the Mac is booted, you login, and then start the VMWare
application. That's probably at least a minute later.

--
Barry Margolin, barmar(a)alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***
*** PLEASE don't copy me on replies, I'll read them in the group ***
From: Mario Vega on 23 Dec 2009 21:28
On Dec 23, 7:43 am, gaze...(a)shell.xmission.com (Kenny McCormack)
wrote:
>     1) To leave it as DHCP, but a way to temporarily disable the DHCP
>         seeking behavior.  And then to re-enable it later.
>         I.e., I want the equivalent of doing "ipconfig /release" in
>         Windows.  And then, of course, "ipconfig /renew".


http://superuser.com/questions/86956
From: Golden California Girls on 24 Dec 2009 00:28
Barry Margolin wrote:
>
> I don't understand how the VM ever won the race in the first place.
> Doesn't the Mac get its IP while it's booting? But the VM isn't started
> up until after the Mac is booted, you login, and then start the VMWare
> application. That's probably at least a minute later.

Well, the Mac does get an IP for its netboot. Then it takes the interface down,
powered down I believe, later in the boot. It runs a script to bring it back
up. That's how the race happens. I'm sure he is also starting VM in a script.
Add or subtract a startup item and the order changes. To insure the order he
wants he is going to have to get into the Mac boot scripts and make sure the
interface is powered on and negotiated hardware protocalls, start VM and wait
for it to come up -- this assumes VM can be started here -- then continue the
rest of the Mac script getting the DHCP. A considerable hack.
From: Golden California Girls on 24 Dec 2009 00:33
Barry Margolin wrote:
>
> I don't understand how the VM ever won the race in the first place.
> Doesn't the Mac get its IP while it's booting? But the VM isn't started
> up until after the Mac is booted, you login, and then start the VMWare
> application. That's probably at least a minute later.

Well, the Mac does get an IP for its netboot. Then it takes the interface down,
powered down I believe, later in the boot. It runs a script to bring it back
up. That's how the race happens. I'm sure he is also starting VM in a script.
Add or subtract a startup item and the order changes. To insure the order he
wants he is going to have to get into the Mac boot scripts and make sure the
interface is powered on and negotiated hardware protocalls, start VM and wait
for it to come up -- this assumes VM can be started here -- then continue the
rest of the Mac script getting the DHCP. A considerable hack.

From: Barry Margolin on 24 Dec 2009 01:49
In article <hguue5$hdv$1(a)aioe.org>,
Golden California Girls <gldncagrls(a)aol.com.mil> wrote:

> Barry Margolin wrote:
> >
> > I don't understand how the VM ever won the race in the first place.
> > Doesn't the Mac get its IP while it's booting? But the VM isn't started
> > up until after the Mac is booted, you login, and then start the VMWare
> > application. That's probably at least a minute later.
>
> Well, the Mac does get an IP for its netboot.

Did I miss him mentioning that he's using netboot? Was it in the other
thread, which I mostly didn't read?

> Then it takes the interface
> down,
> powered down I believe, later in the boot. It runs a script to bring it back
> up. That's how the race happens. I'm sure he is also starting VM in a
> script.
> Add or subtract a startup item and the order changes. To insure the order
> he
> wants he is going to have to get into the Mac boot scripts and make sure the
> interface is powered on and negotiated hardware protocalls, start VM and wait
> for it to come up -- this assumes VM can be started here -- then continue the
> rest of the Mac script getting the DHCP. A considerable hack.

--
Barry Margolin, barmar(a)alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***
*** PLEASE don't copy me on replies, I'll read them in the group ***
First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4 5
Prev: multi-threaded data access
Next: change the address of ld.linux-so in a dynamically linked process