Linux host / XP guest = Bridged network = Hard freeze

Hey there. I am running Gentoo linux host and an XP pro guest. The system is extremely stable. Compiles kde from scratch ect... Until you enable bridged networking on the guest. 30 seconds after it boots the computer will hard freeze and you will have to pull the power cable to reset it. I have narrowed it down to bridged networking by disabling everything and then adding it back one thing at a time. The guest will run all night without bridged networking. Enable it and the system will lock up about 30 seconds after the XP guest boots. Host only networking works fine, just not bridged. I have worked with this for days, it is consistent.

I really need to make bridged networking "work" so I can have internet access in the guest. Any ideas or pointers I can try?

System is:
Dell Power edge 1800, Dual Xeon 3ghz, 4 gig of ecc ram, 4 satas on an adaptec raid controller

2.6.23 kernel

Parallels WS 2204 with the Patch for PW for Linux on 2.6.22+ Kernels

 

Well, I have wrestled this thing for a week alone. The emails I sent in were never answered. Basically parallels ws 2204 locks up under the 2.6.23 kernel no matter what I do. The patch here did get it to install but it locks the host machine. I downgraded the kernel in my machine to 2.6.18 and the hard freeze stopped but it would "seize" for 30 seconds at a time... like it was going to freeze but would come back. Unusable. Also using the mem=4096 kernel line caused my system to use 3 of the 4 gig of ram. Parallels support takes a full week to answer an email... That's a long time when dealing with an issue. At this point I feel I wasted my $50. I thought it had support with it.

After not being able to resolve this I just installed VirtualBox. Surprisingly it works flawlessly with the 2.6.23 kernel, see's my full 4 gig of ram without the mem line and it is free.... And the seamless feature is just to nice. Go OS. Thank you parallels for a great looking product. I will keep an eye on your software and hope you fix it... But the lack of support after purchase makes you look really bad. Can you really have so much email it takes weeks to answer?

 

Hello,

did you try to install the latest build? You can find all information here.

Best regards,
Stacey

 

Had hope there for a moment. It installed nice, parallels-config ran nice... but then when I launched parallels from the command line it just silently dies. Gives no error, just runs a moment and exits. No windows pop up. The old would at least launch ;-)

 

Hello,

did you try to re-unstall Parallels?

Best regards,
Stacey

 

Well, I did the following:

* Ran the uninstall script and removed the old.
* Deleted the /usr/lib/parallels folder
* Deleted the /root/.parallels folder
* Deleted the parallels-config file from /root
* Downloaded: http://download.parallels.com/en/GA/Parallels-2.2.2222-lin.tgz
* Extracted it and ran the install script
* Restarted the machine to unload any leftover things in memory.
* Ran parallels-config as root and let it load the modules
* Ran parallels from the command line.

It sat there for 15 seconds, nothing came up, then gave me the prompt back. Silently failed to do anything... After this I checked /var/log/messages for clues and found this, the only thing from parallels in any log file:

/////////////////////////////////////////////////////////////////////
hypervisor: module license 'unspecified' taints kernel.
[ 8620] Device /dev/hypervisor registered with 10.60
[ 8620] parallels Hypervisor 2.2-2222 initialized.
[ 8635] Device /dev/vm-main registered with 10.59
[ 8635] Parallels Workstation 2.2-2222 Main module initialized.
udev-net.sh: /etc/init.d/net.vnic0: does not exist or is not executable
prl_dhcpd[8689]: Parallels DHCP daemon is starting
prl_dhcpd[8689]: Parallels DHCP daemon at vnic0 scope: 10.37.129.1-10.37.129.254(255.255.255.0)
prl_dhcp[8690]: Parallels DHCP server for virtual NIC started.
prl_dhcp[8690]: Parallels DHCP server for virtual NIC reading configuration.
prl_dhcp[8690]: prl_dhcp: Error getting current address for adapter vnic0 (Cannot assign requested address)
RTNL: assertion failed at net/core/dev.c (2595)
[<c043b080>] __dev_set_promiscuity+0x3f/0xb2
[<c043b3ac>] dev_set_promiscuity+0x10/0x24
[<f887b4c1>] prlnet_ioctl+0x3a1/0x3c0 [vm_bridge]
[<c0176cbc>] do_ioctl+0x4c/0x62
[<c0176f02>] vfs_ioctl+0x230/0x242
[<c016c203>] do_sys_open+0xbb/0xc5
[<c0176f47>] sys_ioctl+0x33/0x4c
[<c0106eae>] sysenter_past_esp+0x6b/0xa1
[<c04b0000>] vlan_dev_change_mtu+0x0/0x25
=======================
device vnic0 entered promiscuous mode
//////////////////////////////////////////////////////////////////////////

 

I am having the same issue on Mandriva 2008.0 - kernel 2.6.22.18-server-1mdv. Using Gnome.

Installation goes well (no errors), but starting the application is unsuccessful. Same issue of running from the command line, a pause for 10 seconds, then nothing...back to the command prompt. I ps -aux right after I issue the parallels command and see some action, but it silently exits. No additional errors in /var/log/messages.

I too receive the vnic0 error on bootup:

kernel: [ 3986] Device /dev/hypervisor registered with 10.60
kernel: [ 3986] parallels Hypervisor 2.2-2222 initialized.
kernel: [ 4006] Device /dev/vm-main registered with 10.59
kernel: [ 4006] Parallels Workstation 2.2-2222 Main module initialized.
prl_dhcpd[4057]: Parallels DHCP daemon is starting
prl_dhcpd[4057]: Parallels DHCP daemon at vnic0 scope: 10.37.129.1-10.37.129.254(255.255.255.0)
prl_dhcp[4080]: Parallels DHCP server for virtual NIC started.
prl_dhcp[4080]: Parallels DHCP server for virtual NIC reading configuration.
prl_dhcp[4080]: prl_dhcp: Error getting current address for adapter vnic0 (Cannot assign requested address)
avahi-daemon[3910]: Joining mDNS multicast group on interface vnic0.IPv4 with address 10.37.129.2.
kernel: device vnic0 entered promiscuous mode
kernel: audit(1203292027.899:2): dev=vnic0 prom=256 old_prom=0 auid=4294967295
avahi-daemon[3910]: New relevant interface vnic0.IPv4 for mDNS.
avahi-daemon[3910]: Registering new address record for 10.37.129.2 on vnic0.IPv4.


I too have tried uninstalling, re-installing and rebooting. Any other thoughts?


Cheers,
Jim