Virtual Switch networking could not be started.

OK, guys, it's my turn!

;-)

Virtual PC is currently not (fully) compatible with Mac OS X 10.4.x.
I speculate that Microsoft have to incorporate some changes to make
the product work with Apple's latest operating system release.

Check back at Microsoft's Mactopia site for news regarding any resolution
to incompoatibility issues with Mac OS X 10.4.


wrote in message

 > After installing Virtual PC for Mac 7.0.1 on a Mac Mini with OS 10.4
 > upgraded from 10.3, the message "Virtual Switch networking could not be
 > started." appears, saying "Permissions for the support files were set
 > properly, but Virtual Switch failed to load. Please report this problem
 > to Microsoft (Code: A1004). Virtual PC for Mac will run without Virtual
 > Switch networking." What is wrong and how do I fix it, without spending
 > hours on the phone with Microsoft?
 >
 >> Stay informed about: Virtual Switch networking could not be started. 

Getting a little tired of Virtual Switch and Tiger, Steve??
 >> Stay informed about: Virtual Switch networking could not be started. 

On 21 May 2005 14:11:05 -0700, "Paul Power"
wrote:

 >Getting a little tired of Virtual Switch and Tiger, Steve??

Well, I wouldn't want to sound snide, but it does get a little
frustrating when there are several relatively active threads with
nearly the same subject as this, or even more specific subjects...


--
Cheers,
Steve Jain, Virtual Machine MVP
Website: <a rel="nofollow" style='text-decoration: none;' href="http://www.essjae.com" target="_blank">http://www.essjae.com</a>
"This posting is provided "AS IS" with
no warranties, and confers no rights.
You assume all risk for your use.
I am not am employee of Microsoft."
 >> Stay informed about: Virtual Switch networking could not be started. 

  > >** We are working on an update to make VPC 7 compatible with Tiger.
  > >This will be a free update and will be available on this site within
  > >the next few months. "

A few months? They're kidding but what can u expect, eh...
 >> Stay informed about: Virtual Switch networking could not be started. 

I'll be shocked if it takes that long...
 >> Stay informed about: Virtual Switch networking could not be started. 

Tell me now how long it would take you to completely re-design the core
emulation of Virtual PC so as to compensate for the fact that the G5
processor is a quite different animal than the G4, and compensate for
the fact that the G4 processor had "on hardware little-endian
emulation" and the G5 processor does not? Now let's factor in that they
likely were working on VPC 7.0 before Panther was released and
therefore were also coding for a moving Host OS target. Finally, let's
factor in that VPC is different than just about every application on
the Mac, and is likely a much more difficult beast to code for.

Oh, wait... you also left out that Apple released 10.4.1 less than
three weeks after 10.4 came out.

Tell ya what, give me an address to send some crow to when this comes
out long before the August date that everyone seems to be predicting.
I'll do the same...
 >> Stay informed about: Virtual Switch networking could not be started. 

I'll be shocked if it doesn't take longer.

Tell me again how long MS the VPC dev team has had the Tiger prerelease and
why they couldn't implement core virtual switching prior to Tiger's release?

A month has now passed. Ample time to engineer and distribute a fix.



On 5/26/05 8:27 PM, in article
1117153645.214589.161170.DeleteThis@o13g2000cwo.googlegroups.com, "Unseelie"
wrote:

 > I'll be shocked if it takes that long...
 >
 >> Stay informed about: Virtual Switch networking could not be started. 

In article ,
"Gomberg, Jeffrey G." <gomberg DeleteThis @synair.com> wrote:

 > I'll be shocked if it doesn't take longer.
 >
 > Tell me again how long MS the VPC dev team has had the Tiger prerelease and
 > why they couldn't implement core virtual switching prior to Tiger's release?
 >
 > A month has now passed. Ample time to engineer and distribute a fix.

They said it would be several months. Maybe they don't consider it a
critical product, so they just haven't assigned any resources to it.
Once they start I don't expect it will take very long, but if no one is
working on it then it won't get done.

--
Barry Margolin, barmar DeleteThis @alum.mit.edu
Arlington, MA
 >> Stay informed about: Virtual Switch networking could not be started. 

Considering that it's the exact same development team (check the
credits), I suspect it would have taken about the same amount of time.
 >> Stay informed about: Virtual Switch networking could not be started. 

In article ,
Barry Margolin wrote:



 >
  > > I'll be shocked if it doesn't take longer.
  > >
  > > Tell me again how long MS the VPC dev team has had the Tiger prerelease and
  > > why they couldn't implement core virtual switching prior to Tiger's release?
  > >
  > > A month has now passed. Ample time to engineer and distribute a fix.
 >
 > They said it would be several months. Maybe they don't consider it a
 > critical product, so they just haven't assigned any resources to it.
 > Once they start I don't expect it will take very long, but if no one is
 > working on it then it won't get done.

Yeah, they're only the biggest and richest software company in the
world...I wonder how long the previous owners would've taken to have it
ready for both the G5 & 10.4...
 >> Stay informed about: Virtual Switch networking could not be started. 

In article ,
Unseelie wrote:

 > Considering that it's the exact same development team (check the
 > credits), I suspect it would have taken about the same amount of time.
 >

Well if thats the case with the same development team then one could
assume they'd would've taken longer as they now have the full resources
of Microcrap to help them...
 >> Stay informed about: Virtual Switch networking could not be started. 

In article ,
witt <me.DeleteThis@home.on.the.net> wrote:



 >
  > > Considering that it's the exact same development team (check the
  > > credits), I suspect it would have taken about the same amount of time.
  > >
 >
 > Well if thats the case with the same development team then one could
 > assume they'd would've taken longer as they now have the full resources
 > of Microcrap to help them...

Have any of you actually worked in a software development organization?
Unless you're dealing with an emergency, you don't typically get people
from other development groups helping you. All those resources are busy
with their own projects.

Does anyone know if the people maintaining VPC for Mac are also doing
VPC for Windows? Since the latter actually has serious competition
(VMWare), I'd expect that MS would consider it more important to enhance.

--
Barry Margolin, barmar.DeleteThis@alum.mit.edu
Arlington, MA
 >> Stay informed about: Virtual Switch networking could not be started. 

There is a kernel extension that - as all Panther kext fail to load on Tiger

Got to wait for Microsoft to fix it. No other way around.


PowerBook:~ root# ll /Library/StartupItems/VirtualPCOSServices
total 16
0 drwxr-xr-x 4 root wheel 136 Oct 22 2004 .
0 drwxr-xr-x 7 root wheel 238 Jun 14 20:53 ..
8 -rw-r--r-- 1 root wheel 443 Oct 22 2004 StartupParameters.plist
8 -rwxr-xr-x 1 root wheel 807 Oct 22 2004 VirtualPCOSServices


PowerBook:~ root# kextload /Library/Extensions/VirtualPCOSServices.kext
kld(): Undefined symbols:
_convert_port_to_processor
_host_info
_host_kernel_version
_host_priv_self
_host_processors
_host_self
_host_statistics
_kernel_pmap_store
_kmem_alloc_contig
_kmem_alloc_wired
_per_proc_info
kextload: kld_load_from_memory() failed for module /Library/Extensions/VirtualPCOSServices.kext/Contents/MacOS/VirtualPCOSServices
kextload: a link/load error occured for kernel extension /Library/Extensions/VirtualPCOSServices.kext
load failed for extension /Library/Extensions/VirtualPCOSServices.kext
(run kextload with -t for diagnostic output)
 >> Stay informed about: Virtual Switch networking could not be started.