Network Problems in Parallel XP on Ubuntu

Discussion in 'Windows Guest OS Discussion' started by CanadianNorth, Oct 28, 2007.

  1. CanadianNorth

    CanadianNorth

    Messages:
    5
    Help!

    I am trying to get my network/internet working in XP (in Parallels) on a Ubuntu 7.10 system. I have tried everything I can think of.

    Does anyone have any suggestions?
     
  2. cbs

    cbs

    Messages:
    3
    Yes, same problem here. I had it on feisty, and it worked, upgraded to gusty, reinstalled parallels, and parallels tools, everything works but xp will NOT grab an IP. What gives?
     
  3. CanadianNorth

    CanadianNorth

    Messages:
    5
    I didn't mention it - but that is my exact situation.

    I am working with a dell 640m. I had installed 7.04, and Parallels was fine, now NADA.
    It makes no sense, is it some sort of permissions issue in 7.10, that won't allow access to the network?????
     
  4. CanadianNorth

    CanadianNorth

    Messages:
    5
  5. Stacey M

    Stacey M Parallels Team

    Messages:
    916
    Hello,

    could you please do the following?
    Go Start -> Settings -> Network Connections. Do you have any Local Area Connection there?
    And please specify how exactly you cannot connect to the Internet?

    Best regards,
    Stacey
     
  6. CanadianNorth

    CanadianNorth

    Messages:
    5
    Hi

    it does say I have a local network, on the "parallels network adapter" it gives an IP address:

    Physical Address: 00-77-1F-**-**-**

    IP Address: 169.254.128.244

    Subnet Mask: 255.255.0.0

    Default Gateway:

    DNS Server:

    WINS Server:

    it says the address type is "Automatic Private Address".

    Parallels is set to 'Bridged Ethernet; default'
    I can access my shared folders on the ubuntu system, but cannot gain access to the internet, outside IP's, etc.

    As mentioned, this setup has worked perfectly in ubuntu 7.04, but not in 7.10
     
  7. Stacey M

    Stacey M Parallels Team

    Messages:
    916
    Hello,

    try to change the Network Adapter Options in your VM. Please go to Configuration Editor and check Bridged Ethernet and not default Network Adapter.

    Best regards,
    Stacey
     
  8. CanadianNorth

    CanadianNorth

    Messages:
    5
    Hi there,

    I tried changing the bridged ethernet to both eth0 and eth1, rebooting each time, and also to the 'host only' settings. Still no-go.
     
  9. Stacey M

    Stacey M Parallels Team

    Messages:
    916
    Hello,

    please go to Terminal and perform the following command:
    sudo /etc/init.d/networking restart
    Please send me via PM the output of this restart.
    After that run ifconfig in Terminal. The results of it please send me too.

    Best regards,
    Stacey
     
  10. ingo

    ingo

    Messages:
    64
    Same here:

    all was perfectly working under Ubutu Feisty as Host, but networking seems broken under Gusty.
    Have installed latest version 'Parallels-2.2.2164-lin-en.deb'. Also 'parallels-config' executes without any problems. Guest OS ist OS/2 Warp 4.5.

    But when trying to communicate with the host-system by:

    a) NFS-mounts (to buils shared folders)
    b) printing with 'lpd' protocol

    None of the above works. Under Feisty all was perfect. After a while Gusty begins to slow down, network applications crash and finally the whole system freezes. Only a 'hard reset' helps.

    Here is the relevant fraction from '/var/log/messages' when trying to print:

    root@pp:/home/ingo# tail /var/log/messages
    Nov 3 12:50:18 pp kernel: [ 5657.392000] [ 7427] svm_support_on(): SVM mode activated
    Nov 3 12:50:18 pp kernel: [ 5657.396000] device eth0 entered promiscuous mode
    Nov 3 12:50:18 pp kernel: [ 5657.396000] audit(1194090618.284:8): dev=eth0 prom=256 old_prom=0 auid=4294967295
    Nov 3 12:50:32 pp kernel: [ 5671.704000] rtc: lost 1 interrupts
    Nov 3 12:51:55 pp cups-lpd[7448]: Connection from valf.home (IPv4 192.168.0.21)
    Nov 3 12:51:55 pp cups-lpd[7448]: Receive print job for Queue
    Nov 3 12:52:46 pp cups-lpd[7448]: Closing connection
    Nov 3 12:53:01 pp kernel: [ 5820.900000] device eth0 left promiscuous mode
    Nov 3 12:53:01 pp kernel: [ 5820.900000] audit(1194090781.793:9): dev=eth0 prom=0 old_prom=256 auid=4294967295
    Nov 3 12:53:01 pp kernel: [ 5820.900000] [ 7427] svm_support_off(): SVM mode deactivated.

    After that the system gradually slows down and even the root-filesystem is corrupted after a while when system freezes.

    Best regards,
    Ingo
     
    Last edited: Nov 3, 2007
  11. cbs

    cbs

    Messages:
    3
    To answer stacy's last request:

    eth0 Link encap:Ethernet HWaddr 00:13:A9:60:74:8A
    UP BROADCAST MULTICAST MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
    Interrupt:17

    eth1 Link encap:Ethernet HWaddr 00:18:DE:8D:89:5A
    inet addr:10.10.10.102 Bcast:10.10.10.255 Mask:255.255.255.0
    inet6 addr: fe80::218:deff:fe8d:895a/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:7298 errors:34 dropped:209 overruns:0 frame:0
    TX packets:5507 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:5358713 (5.1 MB) TX bytes:932463 (910.6 KB)
    Interrupt:18 Base address:0xe000 Memory:cc000000-cc000fff

    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    inet6 addr: ::1/128 Scope:Host
    UP LOOPBACK RUNNING MTU:16436 Metric:1
    RX packets:1359 errors:0 dropped:0 overruns:0 frame:0
    TX packets:1359 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:407370 (397.8 KB) TX bytes:407370 (397.8 KB)

    vnic0 Link encap:Ethernet HWaddr 00:01:23:45:BE:EF
    inet addr:10.37.129.2 Bcast:10.37.129.255 Mask:255.255.255.0
    inet6 addr: fe80::201:23ff:fe45:beef/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:27 errors:0 dropped:0 overruns:0 frame:0
    TX packets:27 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:4851 (4.7 KB) TX bytes:4851 (4.7 KB)
     
  12. ingo

    ingo

    Messages:
    64
    Here my output for Stacy from proposed actions (no Parallels VM started yet after booting):

    -----------------
    ingo@pp:~$ sudo /etc/init.d/networking restart
    [sudo] password for ingo:
    * Reconfiguring network interfaces... [ OK ]
    --------------------
    ingo@pp:~$ ifconfig
    eth0 Protokoll:Ethernet Hardware Adresse 00:18:F3:D1:1A:E5
    inet Adresse:192.168.0.11 Bcast:192.168.0.255 Maske:255.255.255.0
    inet6 Adresse: fe80::218:f3ff:fed1:1ae5/64 Gültigkeitsbereich:Verbindung
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:28063 errors:0 dropped:0 overruns:0 frame:0
    TX packets:12175 errors:0 dropped:0 overruns:0 carrier:0
    Kollisionen:0 Sendewarteschlangenlänge:1000
    RX bytes:14177300 (13.5 MB) TX bytes:1900393 (1.8 MB)
    Interrupt:17 Basisadresse:0x2000

    lo Protokoll:Lokale Schleife
    inet Adresse:127.0.0.1 Maske:255.0.0.0
    inet6 Adresse: ::1/128 Gültigkeitsbereich:Maschine
    UP LOOPBACK RUNNING MTU:16436 Metric:1
    RX packets:70 errors:0 dropped:0 overruns:0 frame:0
    TX packets:70 errors:0 dropped:0 overruns:0 carrier:0
    Kollisionen:0 Sendewarteschlangenlänge:0
    RX bytes:5232 (5.1 KB) TX bytes:5232 (5.1 KB)

    vnic0 Protokoll:Ethernet Hardware Adresse 00:01:23:45:BE:EF
    inet Adresse:10.37.129.2 Bcast:10.37.129.255 Maske:255.255.255.0
    inet6 Adresse: fe80::201:23ff:fe45:beef/64 Gültigkeitsbereich:Verbindung
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:46 errors:0 dropped:0 overruns:0 frame:0
    TX packets:46 errors:0 dropped:0 overruns:0 carrier:0
    Kollisionen:0 Sendewarteschlangenlänge:1000
    RX bytes:5454 (5.3 KB) TX bytes:5454 (5.3 KB)
     
  13. ingo

    ingo

    Messages:
    64
    Meanwhile I did try some more things to solve the problem in Gusty:

    a) downgraded the kernel to 2.6.20-16 (the one of Feisty)
    b) upgrading CUPS from 1.3.2 to 1.3.4

    neither solved the problem in Gusty. Printing to cups-lpd of the host-PC after a while results total freezing of the system, only a hard reset helps. I had to downgrade to Feisty again where all is perfect.
     
    Last edited: Nov 5, 2007
  14. Crischan

    Crischan

    Messages:
    3
    Network does also not work on SuSE 10 (maybe only 10.3)

    Hi,

    I just wanted to try Parallels Workstation on SuSE Linux 10.3 with a Window$ XP Guest and have the same problem.
    I am able to ping my host, but nothing else. Network and routing settings seem ok, tried different configuration but with no luck (btw I am occupied as an programmer and network/internet expert so I am supposed to know what I do :) )

    Any new Ideas?

    Greetings from Hamburg, Germany
    Crischan
     
  15. Stacey M

    Stacey M Parallels Team

    Messages:
    916
    Hello,

    thank you for your feedback. We will investigate your problems.

    Best regards,
    Stacey
     
  16. ingo

    ingo

    Messages:
    64
    If SUSE 10.3 shows the same difficulties as Ubuntu Gusty, it is probably due to the new feature of kernel 2.6.22, which is called 'tickless kernel'. It is intended to save some energy, because it does not wake-up at every timer-tick?

    Best regards,
    Ingo
     
  17. Crischan

    Crischan

    Messages:
    3
    Ingo,
    I disabled the tickless kernel with the kernel boot option nohz=off, but no difference.

    Maybe I have these problems because my device eth1, which I am trying to use for bridged ethernet, is not real ethernet, but WLAN.
    The kernel says that eth1 switched to promiscuous mode, but I cannot tell if the WLAN driver works this way. BTW it's the Intel WLAN chipset, the module used is ipw3945.

    I tried to ping from the guest to the host, and this works.
    Pinging from the host to the guest will give no result (timeout).

    Can anyone tell if WLAN (instead of real ethernet) is probably the reason for my problem?
    However, networking with my WLAN is no problem with VMWare or VirtualBox.

    Thanks very much
    Crischan
     
  18. Stacey M

    Stacey M Parallels Team

    Messages:
    916
    Hello,

    ingo,
    try to perform these steps in order to configure your network in OS/2.

    cbs and Crischan,
    Bridged Ethernet networking allows VMs to access a physical network, but then the VM will be seen as individual PC in your sub network.
    cbs, as I can see from your messages, the IP-address in Windows is 169.254.128.244. That means that none of the DHCP-servers can provide your Windows VM with an IP-address. Try to contact your network administrator.
    Crischan, what type of connection are you using in VMWare?

    Best regards,
    Stacey
     
    Last edited: Nov 13, 2007
  19. Crischan

    Crischan

    Messages:
    3
    Hi Stacey,

    I think with VMWare, it's the NAT setting with the 'vmnet8' interface.
    So the VM does not have an IP of the real network, but it's OK because all I want is to reach the Internet with it. I don't care about which IP the VM is using.

    I think there is nothing like NAT in Parallels, is it? If I understood it right, the Host-based networking does not at all route to a network, does it?

    Thank you,
    Crischan
     
  20. Stacey M

    Stacey M Parallels Team

    Messages:
    916
    Crischan,
    unfortunately, the current version of Parallels Workstation does not have Shared Network and does not support NAT, but this feature will be available in future updates.
    But you can try to use the solution I suggested to cbs.

    Best regards,
    Stacey
     

Share This Page