I have a CentOS 5.3 VM running under VMware on a WIndows XP laptop. Everything works fine when connected to the network. However, removed from the network, most everything in the CentOS VM takes minutes to complete. For instance, starting a new Terminal window takes over 3 minutes. I did an strace, and there are a couple of long waits when trying to open a socket (/tmp/.ICE-unix/XXXXX for instance).
The host and the VM can ping each other fine, but any access to the VM (either external or from within) eventually succeeds, but it takes a long time. First, I thought I'd reduce the default socket timeout (which I believe is set to around 90 seconds), but I can't find where to do that on a system wide level. But I really need to figure out what is causing the problem in the first place. I'm assuming the network is somehow misconfigured, but I don't know how.
Alfred
Alfred von Campe wrote:
I have a CentOS 5.3 VM running under VMware on a WIndows XP laptop. Everything works fine when connected to the network. However, removed from the network, most everything in the CentOS VM takes minutes to complete. For instance, starting a new Terminal window takes over 3 minutes. I did an strace, and there are a couple of long waits when trying to open a socket (/tmp/.ICE-unix/XXXXX for instance).
The host and the VM can ping each other fine, but any access to the VM (either external or from within) eventually succeeds, but it takes a long time. First, I thought I'd reduce the default socket timeout (which I believe is set to around 90 seconds), but I can't find where to do that on a system wide level. But I really need to figure out what is causing the problem in the first place. I'm assuming the network is somehow misconfigured, but I don't know how.
You could do "service network stop" on the CentOS VM when not on the network, or if you need networking between the VM and the hosts, configure for hostonly networking.
Phil
On Jun 16, 2009, at 14:01, Phil Schaffner wrote:
You could do "service network stop" on the CentOS VM when not on the network, or if you need networking between the VM and the hosts, configure for hostonly networking.
I guess I should have mentioned that my user wants to access the files in the CentOS VM from a Samba share on the PC, so turning off the network is not really an option. I will ask him to try it to see if that resolves the issue. But ideally, we want to get this to work with the network running.
Alfred
Alfred von Campe wrote: ...
I guess I should have mentioned that my user wants to access the files in the CentOS VM from a Samba share on the PC, so turning off the network is not really an option. I will ask him to try it to see if that resolves the issue. But ideally, we want to get this to work with the network running.
Hostonly networking should work for access to local files.
Phil
On Tue, 2009-06-16 at 13:50 -0400, Alfred von Campe wrote:
I have a CentOS 5.3 VM running under VMware on a WIndows XP laptop. Everything works fine when connected to the network. However, removed from the network, most everything in the CentOS VM takes minutes to complete. For instance, starting a new Terminal window takes over 3 minutes. I did an strace, and there are a couple of long waits when trying to open a socket (/tmp/.ICE-unix/XXXXX for instance).
--- cat /etc/hosts # Do not remove the following line, or various programs # that require network functionality will fail. ::1 localhost.localdomain localhost
john
Are you running VMWare Workstation or Server? I am running VMWare Workstation under MS Vista with a bunch of Centos guest VMs. I noticed that when my Vista host network connection changes state (becomes unavailable or becomes available for any reason) that the VMWare software switch has real trouble. I often lose my ability to DHCP, for example. Or perhaps DNS is impacted. It is my feeling that their networking code is just not very robust.
Would using shared folders be a viable alternative?
-geoff
--------------------------------- Geoff Galitz Blankenheim NRW, Germany http://www.galitz.org/ http://german-way.com/blog/
On Jun 16, 2009, at 14:38, Geoff Galitz wrote:
Are you running VMWare Workstation or Server?
VMware Workstation.
I am running VMWare Workstation under MS Vista with a bunch of Centos guest VMs. I noticed that when my Vista host network connection changes state (becomes unavailable or becomes available for any reason) that the VMWare software switch has real trouble. I often lose my ability to DHCP, for example. Or perhaps DNS is impacted. It is my feeling that their networking code is just not very robust.
Hmm, interesting points. I'll have to check his settings. Unfortunately, I will be out of the office for the next 1.5 weeks so it may have to wait until I return.
Would using shared folders be a viable alternative?
Shared folders without a network? How does one set that up?
Alfred
Shared folders without a network? How does one set that up?
This is a good link to get you started (it is for Ubuntu, but should work just fine for Centos):
http://www.howtogeek.com/howto/ubuntu/how-to-share-folders-with-your-ubuntu- virtual-machine-guest/
FWIW, I had to start migrating some of my work away from VMWare in favor of Virtualbox due to the lack of good networking support in VMWare Workstation. Your mileage may vary, of course.
--------------------------------- Geoff Galitz Blankenheim NRW, Germany http://www.galitz.org/ http://german-way.com/blog/
Geoff Galitz wrote:
Shared folders without a network? How does one set that up?
This is a good link to get you started (it is for Ubuntu, but should work just fine for Centos):
http://www.howtogeek.com/howto/ubuntu/how-to-share-folders-with-your-ubuntu- virtual-machine-guest/
FWIW, I had to start migrating some of my work away from VMWare in favor of Virtualbox due to the lack of good networking support in VMWare Workstation. Your mileage may vary, of course.
I've mostly used the free VMware server and player, but thought the networking support was about the same as Virtualbox. What have you found that is significantly different? So far I mostly prefer VMware server for the ability to run the console and disconnect/reconnect where with virtualbox you seem to have to decide ahead of time if you want a console or not - but I'm not a big fan of the new web console in the 2.x series.
I've mostly used the free VMware server and player, but thought the networking support was about the same as Virtualbox. What have you found that is significantly different? So far I mostly prefer VMware server for the ability to run the console and disconnect/reconnect where with virtualbox you seem to have to decide ahead of time if you want a console or not - but I'm not a big fan of the new web console in the 2.x series.
There are two major issues I've had with VMWare Workstation that have not occurred in VirtualBox:
1) When the host network connection comes and goes (either intentionally or otherwise) the networking to and from VMWare VMs fail completely and cannot be restored without a host reboot.
2) DHCP via an external system (router/gateway) often fails to the VMs with nothing more than timeout errors in the VM logs.
VirtualBox has issues to, as does most software, so I end up using both to get all of my testing and simulations done.
-geoff
--------------------------------- Geoff Galitz Blankenheim NRW, Germany http://www.galitz.org/ http://german-way.com/blog/
Geoff Galitz wrote:
I've mostly used the free VMware server and player, but thought the networking support was about the same as Virtualbox. What have you found that is significantly different? So far I mostly prefer VMware server for the ability to run the console and disconnect/reconnect where with virtualbox you seem to have to decide ahead of time if you want a console or not - but I'm not a big fan of the new web console in the 2.x series.
There are two major issues I've had with VMWare Workstation that have not occurred in VirtualBox:
- When the host network connection comes and goes (either intentionally or
otherwise) the networking to and from VMWare VMs fail completely and cannot be restored without a host reboot.
I don't think I've ever seen that happen under vmware server - and I've had guests up for at least a year without reboots. With player I've normally stopped the guest before disconnecting from the network. Are you using bridged or NAT?
- DHCP via an external system (router/gateway) often fails to the VMs with
nothing more than timeout errors in the VM logs.
I've never seen a problem with DHCP on bridged connections under any circumstances.
On Jun 16, 2009, at 14:58, JohnS wrote:
Open a terminal window and type cat /etc/hosts and post it.
# cat /etc/hosts # Do not remove the following line, or various programs # that require network functionality will fail. 127.0.0.1 localhost.localdomain localhost 139.68.198.200 fm1185.bose.com
I disabled IPV6 and removed the ::1 line.
Alfred
The fm1185.bose.com is hostname of the host, correct? Try put: === 127.0.0.1 localhost.localdomain localhost fm1185.bose.com ===
[]s ________________________________________________ Renato de Oliveira Diogo
Bacharel em Ciência da Computação UNESP - Bauru
LPIC1 - Linux Professional Institute Certification - Nível 1
renato.diogo@gmail.com renato.diogo@yahoo.com.br
On Tue, Jun 16, 2009 at 16:23, Alfred von Campealfred@von-campe.com wrote:
On Jun 16, 2009, at 14:58, JohnS wrote:
Open a terminal window and type cat /etc/hosts and post it.
# cat /etc/hosts # Do not remove the following line, or various programs # that require network functionality will fail. 127.0.0.1 localhost.localdomain localhost 139.68.198.200 fm1185.bose.com
I disabled IPV6 and removed the ::1 line.
Alfred
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Jun 16, 2009, at 15:30, Renato de Oliveira Diogo wrote:
The fm1185.bose.com is hostname of the host, correct? Try put: === 127.0.0.1 localhost.localdomain localhost fm1185.bose.com
No, it's the name of the Windows XP machine where the VM is running. I always remove the hostname from the localhost line. Too many things break when the actual host name is present on the localhost line.
Alfred
On Tue, 2009-06-16 at 15:33 -0400, Alfred von Campe wrote:
On Jun 16, 2009, at 15:30, Renato de Oliveira Diogo wrote:
The fm1185.bose.com is hostname of the host, correct? Try put: === 127.0.0.1 localhost.localdomain localhost fm1185.bose.com
No, it's the name of the Windows XP machine where the VM is running. I always remove the hostname from the localhost line. Too many things break when the actual host name is present on the localhost line.
Alfred
---Correct: ::1 localhost.localdomain localhost 192.168.0.37 xxxxx0 XP Machine Here 192.168.0.7 xxxxx1 linux vm ---- The machine settings and name can also come from: /etc/sysconfig/networking/profiles/default. No one has mentioned that.
Use "hostname "your_name" to set the hostname.
john
On Tue, 2009-06-16 at 15:23 -0400, Alfred von Campe wrote:
On Jun 16, 2009, at 14:58, JohnS wrote:
Open a terminal window and type cat /etc/hosts and post it.
# cat /etc/hosts # Do not remove the following line, or various programs # that require network functionality will fail. 127.0.0.1 localhost.localdomain localhost 139.68.198.200 fm1185.bose.com
I disabled IPV6 and removed the ::1 line.
Alfred
--- ::1 line
Put it back and have a go at it.
john
On Tue, Jun 16, 2009 at 1:50 PM, Alfred von Campealfred@von-campe.com wrote:
I have a CentOS 5.3 VM running under VMware on a WIndows XP laptop. Everything works fine when connected to the network. However, removed from the network, most everything in the CentOS VM takes minutes to complete. For instance, starting a new Terminal window takes over 3 minutes. I did an strace, and there are a couple of long waits when trying to open a socket (/tmp/.ICE-unix/XXXXX for instance).
The host and the VM can ping each other fine, but any access to the VM (either external or from within) eventually succeeds, but it takes a long time. First, I thought I'd reduce the default socket timeout (which I believe is set to around 90 seconds), but I can't find where to do that on a system wide level. But I really need to figure out what is causing the problem in the first place. I'm assuming the network is somehow misconfigured, but I don't know how.
Alfred
This is a classic sign of DNS query timeouts. When you are connected to the network the system is making DNS queries which respond quickly. When you are not connected, the host makes DNS queries and waits for a response. The timeout is a minute or so, so you will see a long delay in any program that tries to resolve DNS. Many programs use DNS even if it's not entirely obvious why.
You didn't say which virtual network this machine is connected to, but you probably want to use the NAT network and allow the VM to receive the DNS server configuration via DHCP.
Brian Mathis wrote: ...
You didn't say which virtual network this machine is connected to, but you probably want to use the NAT network and allow the VM to receive the DNS server configuration via DHCP.
Can't say for sure without trying it, but it seems to me that getting a config via DHCP is not going to help with the network timeout problems under discussion if the DNS the config is pointing to goes away along with the host network connection.
Phil
Brian is correct...
check the /etc/hosts if your hostname and hostname.hostdomain is registred here. Eg. if a MTA (sendmail) don´t resolv the hostname of the host is gerated a big delay. Put the hostname in loopbak interface (127.0.0.1)...
And is not in VM, in physical host the same "problem"
[]s ________________________________________________ Renato de Oliveira Diogo
Bacharel em Ciência da Computação UNESP - Bauru
LPIC1 - Linux Professional Institute Certification - Nível 1
renato.diogo@gmail.com renato.diogo@yahoo.com.br
On Tue, Jun 16, 2009 at 16:03, Brian Mathisbrian.mathis@gmail.com wrote:
On Tue, Jun 16, 2009 at 1:50 PM, Alfred von Campealfred@von-campe.com wrote:
I have a CentOS 5.3 VM running under VMware on a WIndows XP laptop. Everything works fine when connected to the network. However, removed from the network, most everything in the CentOS VM takes minutes to complete. For instance, starting a new Terminal window takes over 3 minutes. I did an strace, and there are a couple of long waits when trying to open a socket (/tmp/.ICE-unix/XXXXX for instance).
The host and the VM can ping each other fine, but any access to the VM (either external or from within) eventually succeeds, but it takes a long time. First, I thought I'd reduce the default socket timeout (which I believe is set to around 90 seconds), but I can't find where to do that on a system wide level. But I really need to figure out what is causing the problem in the first place. I'm assuming the network is somehow misconfigured, but I don't know how.
Alfred
This is a classic sign of DNS query timeouts. When you are connected to the network the system is making DNS queries which respond quickly. When you are not connected, the host makes DNS queries and waits for a response. The timeout is a minute or so, so you will see a long delay in any program that tries to resolve DNS. Many programs use DNS even if it's not entirely obvious why.
You didn't say which virtual network this machine is connected to, but you probably want to use the NAT network and allow the VM to receive the DNS server configuration via DHCP. _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Jun 16, 2009, at 15:03, Brian Mathis wrote:
This is a classic sign of DNS query timeouts. When you are connected to the network the system is making DNS queries which respond quickly. When you are not connected, the host makes DNS queries and waits for a response. The timeout is a minute or so, so you will see a long delay in any program that tries to resolve DNS. Many programs use DNS even if it's not entirely obvious why.
That's what I thought at first too, but I've ruled that out. For instance, here is some snippets from the strace output when trying to open another Terminal window:
12:45:59 socket(PF_FILE, SOCK_STREAM, 0) = 10 ... 12:45:59 connect(10, {sa_family=AF_FILE, path="/tmp/.ICE-unix/4046"}, 21) = 0 12:45:59 fcntl64(10, F_SETFD, FD_CLOEXEC) = 0 12:45:59 write(10, "\0\1\0\0\0\0\0\0", 8) = 8 12:45:59 read(10, "\0\1\0\0\0\0\0\0", 8) = 8 12:46:43 access("/home/dv15727/.ICEauthority", R_OK) = 0 ... 12:46:43 read(10, "\1\2\0\1\6\0\0\0", 8) = 8 12:48:03 read(10, "%\0\0\0001053b574c2000124517088300000"..., 48) = 48
As you can see, reading from a (local) socket is taking a long time. DNS should not be involved.
You didn't say which virtual network this machine is connected to, but you probably want to use the NAT network and allow the VM to receive the DNS server configuration via DHCP.
I'll have to check when I get back to the office in 1.5 weeks.
Alfred
-
Alfred von Campe -
Brian Mathis -
Geoff Galitz -
JohnS -
Les Mikesell -
Phil Schaffner -
Renato de Oliveira Diogo