Hi everyone, I just set up a opensolaris dom0 yesterday (off the latest repositories, snv_121). I''m trying to set up a fedora domU, but this problem pertains to anything I try via paravirt. The network card can ping / reply to pings very quickly, but anything that invovles TCP hangs for a long time. telnet''ing to google.com, for example, takes 2 minutes before the connection is established. After it''s established, nothing is transmitted nor received either. If i do fully virtualized (like boot off an ubuntu liveCD), everything works perfectly. Any tips on how to try to solve this problem? Thanks, Stephen -- This message posted from opensolaris.org
On 1 Sep 2009, at 11:30pm, Stephen Kou wrote:> I just set up a opensolaris dom0 yesterday (off the latest > repositories, snv_121). I''m trying to set up a fedora domU, but > this problem pertains to anything I try via paravirt. The network > card can ping / reply to pings very quickly, but anything that > invovles TCP hangs for a long time. telnet''ing to google.com, for > example, takes 2 minutes before the connection is established. > After it''s established, nothing is transmitted nor received either. > > If i do fully virtualized (like boot off an ubuntu liveCD), > everything works perfectly. > > Any tips on how to try to solve this problem?What NIC does the dom0 have?
Hi David, Thanks for the reply; I was worried that no one would reply! The dom0 has a realtek network card. The name is rge0 on the machine. There''s an on-motherboard NIC that''s made by attansic, but it seems OSol at this time doesnt have out-of-the-box support for this card. I''ve found alpha drivers online, but I don''t trust them yet. Thanks! -- This message posted from opensolaris.org
On 3 Sep 2009, at 11:50pm, Stephen Kou wrote:> The dom0 has a realtek network card. The name is rge0 on the machine.Some Realtek devices have broken checksum offload. Try disabling checksum offload in the guest domain (using ''ethtool'') and see if things improve.
I see, okay. So, I figure that I must do the OS install first as a fully virtualized guest, and then "convert" it into a xen kernel afterwards, and then tell the dom0 to then change the domU from fully virtualized into paravirutalized; as the install program does not have ethtool nor an option to drop into a terminal with ethtool (fedora net install). I created a fully virtualized VM for the install; and everything regarding the network (and performance) is great. However, right when it tries to access the virtual disk I created, it will hang there and not move. (It''s trying to format it to create the FS, which usually takes like 5-10 seconds). I''ve let it sit there for 30 minutes already. I''ve tried creating the disk using phy/zvol, as well as the default vmdk flat file. Neither of them seem to allow the VM to access it without hanging it. Any ideas for this new problem? Thanks, stephen -- This message posted from opensolaris.org