patrice-xen@breton.org
2006-Oct-27 01:20 UTC
[Xen-users] Kernel 2.2.18 to 2.2.25 as HVM on xen 3.0.3 freeze every 28s or less
Hi, For various bad reasons I must run a kernel 2.2.X and I tried to get it running on Xen 3.0.3. The virtual machine freeze every 28s (or less) for 1-3 secs which makes it unusable as demonstrated by: # while true; do date; sleep 1; done Thu Oct 26 18:03:36 PDT 2006 <missing> Thu Oct 26 18:03:38 PDT 2006 or # ping my-xen 64 bytes from 172.21.1.102: icmp_seq=0 ttl=255 time=8.5 ms 64 bytes from 172.21.1.102: icmp_seq=1 ttl=255 time=2313.7 ms 64 bytes from 172.21.1.102: icmp_seq=2 ttl=255 time=1314.0 ms 64 bytes from 172.21.1.102: icmp_seq=3 ttl=255 time=314.2 ms 64 bytes from 172.21.1.102: icmp_seq=4 ttl=255 time=5.7 ms Any idea what could be wrong ? I tried default or bvt schedulers (some people reported better overhaul behavior for hvm with bvt), I tried with or without any graphical interface (sdl). It does not boot at all with 2 vcpus so could not try that. Any idea ? Patrice _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi I setup xen-3.0.2 on two nodes , and modify the xend-config.sxp but when I try to migrate a vm from one node to a other , error arises: Error: (104, ''Connection reset by peer'') Is there something wrong with the xend-config.sxp or something else needed to be instored or modified to make the migrate work well could anyone give a help Thanks in advance xend-config.sxp: # # Xend configuration file. # # This example configuration is appropriate for an installation that # utilizes a bridged network configuration. Access to xend via http # is disabled. # Commented out entries show the default for that entry, unless otherwise # specified. #(logfile /var/log/xend.log) #(loglevel DEBUG) #(xend-http-server no) #(xend-unix-server no) #(xend-tcp-xmlrpc-server no) #(xend-unix-xmlrpc-server yes) #(xend-relocation-server no) (xend-relocation-server yes) #(xend-unix-path /var/lib/xend/xend-socket) # Port xend should use for the HTTP interface, if xend-http-server is set. #(xend-port 8000) # Port xend should use for the relocation interface, if xend-relocation-server # is set. (xend-relocation-port 8002) # Address xend should listen on for HTTP connections, if xend-http-server is # set. # Specifying ''localhost'' prevents remote connections. # Specifying the empty string '''' (the default) allows all connections. 1,1 ??? #(xend-address '''') #(xend-address localhost) # Address xend should listen on for relocation-socket connections, if # xend-relocation-server is set. # Meaning and default as for xend-address above. (xend-relocation-address '''') # The hosts allowed to talk to the relocation port. If this is empty (the # default), then all connections are allowed (assuming that the connection # arrives on a port and interface on which we are listening; see # xend-relocation-port and xend-relocation-address above). Otherwise, this # should be a space-separated sequence of regular expressions. Any host with # a fully-qualified domain name or an IP address that matches one of these # regular expressions will be accepted. # # For example: # (xend-relocation-hosts-allow ''^localhost$ ^.*\.example\.org$'') # (xend-relocation-hosts-allow '''') #(xend-relocation-hosts-allow ''^localhost$'') # The limit (in kilobytes) on the size of the console buffer #(console-limit 1024) ## # To bridge network traffic, like this: # # dom0: fake eth0 -> vif0.0 -+ # | # bridge -> real eth0 -> the network # | # domU: fake eth0 -> vifN.0 -+ # # use # # (network-script network-bridge) # # Your default ethernet device is used as the outgoing interface, by default. # To use a different one (e.g. eth1) use # # (network-script ''network-bridge netdev=eth1'') # # The bridge is named xenbr0, by default. To rename the bridge, use # # (network-script ''network-bridge bridge=<name>'') #(network-script ''network-bridge netdev=eth1 bridge=xenbr0'') (network-script my-network-bridge) # # It is possible to use the network-bridge script in more complicated # scenarios, such as having two outgoing interfaces, with two bridges, and # two fake interfaces per guest domain. To do things like this, write # yourself a wrapper script, and call network-bridge from it, as appropriate. # (network-script network-bridge) # The script used to control virtual interfaces. This can be overridden on a # per-vif basis when creating a domain or a configuring a new vif. The # vif-bridge script is designed for use with the network-bridge script, or # similar configurations. # # If you have overridden the bridge name using # (network-script ''network-bridge bridge=<name>'') then you may wish to do the # same here. The bridge name can also be set when creating a domain or # configuring a new vif, but a value specified here would act as a default. # # If you are using only one bridge, the vif-bridge script will discover that, # so there is no need to specify it explicitly. # (vif-script vif-bridge) ## Use the following if network traffic is routed, as an alternative to the # settings for bridged networking given above. #(network-script network-route) #(vif-script vif-route) ## Use the following if network traffic is routed with NAT, as an alternative # to the settings for bridged networking given above. #(network-script network-nat) #(vif-script vif-nat) # Dom0 will balloon out when needed to free memory for domU. # dom0-min-mem is the lowest memory level (in MB) dom0 will get down to. # If dom0-min-mem=0, dom0 will never balloon out. (dom0-min-mem 196) # In SMP system, dom0 will use dom0-cpus # of CPUS # If dom0-cpus = 0, dom0 will take all cpus available (dom0-cpus 0) # Whether to enable core-dumps when domains crash. #(enable-dump no) _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi, my xend-config.sxp config id: (xend-http-server yes) (xend-relocation-server yes) (xend-port 8000) (xend-relocation-port 8002) (xend-relocation-address '''') ### (xend-relocation-hosts-allow '''') and live migration is OK. You can probed modify your config. luck. 2006/10/27, tgh <tianguanhua@ncic.ac.cn>:> > Hi > I setup xen-3.0.2 on two nodes , and modify the xend-config.sxp > > but when I try to migrate a vm from one node to a other , error arises: > Error: (104, ''Connection reset by peer'') > > Is there something wrong with the xend-config.sxp or something else > needed to be instored or modified to make the migrate work well > could anyone give a help > > Thanks in advance > > xend-config.sxp: > > > # > # Xend configuration file. > # > > # This example configuration is appropriate for an installation that > # utilizes a bridged network configuration. Access to xend via http > # is disabled. > > # Commented out entries show the default for that entry, unless otherwise > # specified. > > #(logfile /var/log/xend.log) > #(loglevel DEBUG) > > #(xend-http-server no) > #(xend-unix-server no) > #(xend-tcp-xmlrpc-server no) > #(xend-unix-xmlrpc-server yes) > #(xend-relocation-server no) > (xend-relocation-server yes) > > #(xend-unix-path /var/lib/xend/xend-socket) > > # Port xend should use for the HTTP interface, if xend-http-server is set. > #(xend-port 8000) > > # Port xend should use for the relocation interface, if > xend-relocation-server > # is set. > (xend-relocation-port 8002) > > # Address xend should listen on for HTTP connections, if xend-http-server > is > # set. > # Specifying ''localhost'' prevents remote connections. > # Specifying the empty string '''' (the default) allows all connections. > > 1,1 ??? > #(xend-address '''') > #(xend-address localhost) > > # Address xend should listen on for relocation-socket connections, if > # xend-relocation-server is set. > # Meaning and default as for xend-address above. > (xend-relocation-address '''') > > # The hosts allowed to talk to the relocation port. If this is empty (the > # default), then all connections are allowed (assuming that the connection > # arrives on a port and interface on which we are listening; see > # xend-relocation-port and xend-relocation-address above). Otherwise, this > # should be a space-separated sequence of regular expressions. Any host > with > # a fully-qualified domain name or an IP address that matches one of these > # regular expressions will be accepted. > # > # For example: > # (xend-relocation-hosts-allow ''^localhost$ ^.*\.example\.org$'') > # > (xend-relocation-hosts-allow '''') > #(xend-relocation-hosts-allow ''^localhost$'') > > # The limit (in kilobytes) on the size of the console buffer > #(console-limit 1024) > > ## > # To bridge network traffic, like this: > # > # dom0: fake eth0 -> vif0.0 -+ > # | > # bridge -> real eth0 -> the network > # | > # domU: fake eth0 -> vifN.0 -+ > # > # use > # > # (network-script network-bridge) > # > # Your default ethernet device is used as the outgoing interface, by > default. > # To use a different one (e.g. eth1) use > # > # (network-script ''network-bridge netdev=eth1'') > # > # The bridge is named xenbr0, by default. To rename the bridge, use > # > # (network-script ''network-bridge bridge=<name>'') > #(network-script ''network-bridge netdev=eth1 bridge=xenbr0'') > (network-script my-network-bridge) > # > # It is possible to use the network-bridge script in more complicated > # scenarios, such as having two outgoing interfaces, with two bridges, and > # two fake interfaces per guest domain. To do things like this, write > # yourself a wrapper script, and call network-bridge from it, as > appropriate. > # > (network-script network-bridge) > > # The script used to control virtual interfaces. This can be overridden on > a > # per-vif basis when creating a domain or a configuring a new vif. The > # vif-bridge script is designed for use with the network-bridge script, or > # similar configurations. > # > # If you have overridden the bridge name using > # (network-script ''network-bridge bridge=<name>'') then you may wish to > do the > # same here. The bridge name can also be set when creating a domain or > # configuring a new vif, but a value specified here would act as a > default. > # > # If you are using only one bridge, the vif-bridge script will discover > that, > # so there is no need to specify it explicitly. > # > (vif-script vif-bridge) > > > ## Use the following if network traffic is routed, as an alternative to > the > # settings for bridged networking given above. > #(network-script network-route) > #(vif-script vif-route) > > > ## Use the following if network traffic is routed with NAT, as an > alternative > # to the settings for bridged networking given above. > #(network-script network-nat) > #(vif-script vif-nat) > > > # Dom0 will balloon out when needed to free memory for domU. > # dom0-min-mem is the lowest memory level (in MB) dom0 will get down to. > # If dom0-min-mem=0, dom0 will never balloon out. > (dom0-min-mem 196) > > # In SMP system, dom0 will use dom0-cpus # of CPUS > # If dom0-cpus = 0, dom0 will take all cpus available > (dom0-cpus 0) > > # Whether to enable core-dumps when domains crash. > #(enable-dump no) > > > > > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >-- .~. ( 0 0 ) / V \ // \\ Power by Debian /(( _ ))\ oo0 0oo A greeting, Javier. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Thank you for your advise, but it does not work, sereval days later, I have succeeded in migrating vm live from one node to the other ,then one of my classmates modified some device driver part of linux kernel on one node ,and he deleted xen by mistake , of course he reinstall xen ,but now migrating can not work well, on one node A ,vm could be migrated to the node A itself,but on the other node B it can not ,and error arises : [root@gdnode003 xen]# xm migrate test 192.168.100.3 --live Error: [Errno 32] Broken pipe and from node A to B ,it can`t migrate with the error : Error: (104, ''Connection reset by peer'') from node B to A, vm could be migrated to A, that is , vm disappares from B ,and to xm list ,we can see vm in the list on node A,but it doesn`t complete migrating successfully,when we xm console vm, the screen stops ,the last some line on the screen as follows: esi: 00000000 edi: 00000104 ebp: cfc39edc esp: cfc39ed4 ds: 007b es: 007b ss: 0069 Process suspend (pid: 1794, threadinfo=cfc38000 task=cfae1580) Stack: <0>fffffff4 00000000 cfc39efc c013b9a1 c03dd0c0 00000020 00000000 04000002 00000104 c0361040 cfc39f20 c0247648 00000104 c024ad70 00000000 c02edcda 00000000 00000000 00007ff0 cfc39f5c c024acf8 00000002 c024ad70 00000000 Call Trace: [<c01056ed>] show_stack_log_lvl+0xcd/0x100 [<c01058c9>] show_registers+0x1a9/0x230 [<c0105a6a>] die+0x11a/0x240 [<c0105c28>] do_trap+0x98/0xe0 [<c01064a0>] do_invalid_op+0xa0/0xb0 [<c01051b3>] error_code+0x2b/0x30 [<c013b9a1>] request_irq+0x61/0xb0 [<c0247648>] bind_evtchn_to_irqhandler+0x58/0xa0 [<c024acf8>] xencons_ring_init+0x58/0xc0 [<c024ad68>] xencons_resume+0x8/0x10 [<c02484cd>] __do_suspend+0x36d/0x440 [<c0131425>] kthread+0xc5/0xf0 [<c0102b45>] kernel_thread_helper+0x5/0x10 Code: 00 00 00 83 e8 01 8b 5c 82 14 89 02 b8 00 e0 ff ff 89 f1 21 e0 8b 50 10 0f <0>invalid opcode: 0000 [#2] SMP Modules linked in: CPU: 0 EIP: 0061:[<c0159c40>] Not tainted VLI EFLAGS: 00010246 (2.6.16-xenU #2) EIP is at kmem_cache_alloc+0x60/0x90 eax: 00000000 ebx: cfeb4000 ecx: 00000000 edx: fbf8d000 esi: 00000000 edi: 00000001 ebp: cfc4fea8 esp: cfc4fea0 ds: 007b es: 007b ss: 0069 Process initlog (pid: 591, threadinfo=cfc4e000 task=cfb25a50) Stack: <0>cfc4ff6c fffffff4 cfc4fec8 c016d9b9 c03cb2c0 000000d0 cfb25b78 cfc4ff6c cfc4fefc 00000001 cfc4fee8 c016f88c 08052310 ffffffff ffffff9c cfc4ff6c cfc4fefc 00000003 cfc4ff48 c01682d2 cfc4fefc cfc4ff1c c01418b1 00000038 Call Tra could you give me some advise about how to mend xen ,or could some one give me some help? thanks in advance Javier Terceiro ??:> Hi, > > my xend-config.sxp config id: > > (xend-http-server yes) > (xend-relocation-server yes) > (xend-port 8000) > (xend-relocation-port 8002) > (xend-relocation-address '''') > ### (xend-relocation-hosts-allow '''') > > and live migration is OK. You can probed modify your config. > > luck. > > > 2006/10/27, tgh <tianguanhua@ncic.ac.cn <mailto:tianguanhua@ncic.ac.cn>>: > > Hi > I setup xen-3.0.2 on two nodes , and modify the xend-config.sxp > > but when I try to migrate a vm from one node to a other , error > arises: > Error: (104, ''Connection reset by peer'') > > Is there something wrong with the xend-config.sxp or something else > needed to be instored or modified to make the migrate work well > could anyone give a help > > Thanks in advance > > xend-config.sxp: > > > # > # Xend configuration file. > # > > # This example configuration is appropriate for an installation that > # utilizes a bridged network configuration. Access to xend via http > # is disabled. > > # Commented out entries show the default for that entry, unless > otherwise > # specified. > > #(logfile /var/log/xend.log) > #(loglevel DEBUG) > > #(xend-http-server no) > #(xend-unix-server no) > #(xend-tcp-xmlrpc-server no) > #(xend-unix-xmlrpc-server yes) > #(xend-relocation-server no) > (xend-relocation-server yes) > > #(xend-unix-path /var/lib/xend/xend-socket) > > # Port xend should use for the HTTP interface, if xend-http-server > is set. > #(xend-port 8000) > > # Port xend should use for the relocation interface, if > xend-relocation-server > # is set. > (xend-relocation-port 8002) > > # Address xend should listen on for HTTP connections, if > xend-http-server is > # set. > # Specifying ''localhost'' prevents remote connections. > # Specifying the empty string '''' (the default) allows all connections. > > 1,1 ??? > #(xend-address '''') > #(xend-address localhost) > > # Address xend should listen on for relocation-socket connections, if > # xend-relocation-server is set. > # Meaning and default as for xend-address above. > (xend-relocation-address '''') > > # The hosts allowed to talk to the relocation port. If this is > empty (the > # default), then all connections are allowed (assuming that the > connection > # arrives on a port and interface on which we are listening; see > # xend-relocation-port and xend-relocation-address above). > Otherwise, this > # should be a space-separated sequence of regular expressions. Any > host with > # a fully-qualified domain name or an IP address that matches one > of these > # regular expressions will be accepted. > # > # For example: > # (xend-relocation-hosts-allow ''^localhost$ ^.*\.example\.org$'') > # > (xend-relocation-hosts-allow '''') > #(xend-relocation-hosts-allow ''^localhost$'') > > # The limit (in kilobytes) on the size of the console buffer > #(console-limit 1024) > > ## > # To bridge network traffic, like this: > # > # dom0: fake eth0 -> vif0.0 -+ > # | > # bridge -> real eth0 -> the network > # | > # domU: fake eth0 -> vifN.0 -+ > # > # use > # > # (network-script network-bridge) > # > # Your default ethernet device is used as the outgoing interface, by > default. > # To use a different one (e.g. eth1) use > # > # (network-script ''network-bridge netdev=eth1'') > # > # The bridge is named xenbr0, by default. To rename the bridge, use > # > # (network-script ''network-bridge bridge=<name>'') > #(network-script ''network-bridge netdev=eth1 bridge=xenbr0'') > (network-script my-network-bridge) > # > # It is possible to use the network-bridge script in more complicated > # scenarios, such as having two outgoing interfaces, with two > bridges, and > # two fake interfaces per guest domain. To do things like this, write > # yourself a wrapper script, and call network-bridge from it, as > appropriate. > # > (network-script network-bridge) > > # The script used to control virtual interfaces. This can be > overridden on a > # per-vif basis when creating a domain or a configuring a new vif. The > # vif-bridge script is designed for use with the network-bridge > script, or > # similar configurations. > # > # If you have overridden the bridge name using > # (network-script ''network-bridge bridge=<name>'') then you may wish to > do the > # same here. The bridge name can also be set when creating a domain or > # configuring a new vif, but a value specified here would act as a > default. > # > # If you are using only one bridge, the vif-bridge script will > discover > that, > # so there is no need to specify it explicitly. > # > (vif-script vif-bridge) > > > ## Use the following if network traffic is routed, as an > alternative to the > # settings for bridged networking given above. > #(network-script network-route) > #(vif-script vif-route) > > > ## Use the following if network traffic is routed with NAT, as an > alternative > # to the settings for bridged networking given above. > #(network-script network-nat) > #(vif-script vif-nat) > > > # Dom0 will balloon out when needed to free memory for domU. > # dom0-min-mem is the lowest memory level (in MB) dom0 will get > down to. > # If dom0-min-mem=0, dom0 will never balloon out. > (dom0-min-mem 196) > > # In SMP system, dom0 will use dom0-cpus # of CPUS > # If dom0-cpus = 0, dom0 will take all cpus available > (dom0-cpus 0) > > # Whether to enable core-dumps when domains crash. > #(enable-dump no) > > > > > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com <mailto:Xen-users@lists.xensource.com> > http://lists.xensource.com/xen-users > > > > > -- > .~. > ( 0 0 ) > / V \ > // \\ Power by Debian > /(( _ ))\ > oo0 0oo > > A greeting, > > Javier. > ------------------------------------------------------------------------ > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users