Thank you ,Carlos. I just rest all the nic in the same cluster and now it back to normal.
On Thu, Dec 5, 2013 at 12:31 PM, Carlos Reátegui <create...@gmail.com>wrote: > Hi Peter > I experienced a similar problem. I believe it is due to interface renaming > that happens at boot. Unfortunately I don't have access to my machines so I > can't check the specific thing you need to do but do a search for > "XenServer interface rename" and hopefully you'll get enough pointers. If I > remember correctly I had to edit a file that is used by the rename process > to set it to my original nic. Eg eth1 had been turned into eth13. This > happened with 5 of my 8 nics. After putting them all back, I rebooted and > was back in business. > > Hope this helps > Carlos > > > On Dec 5, 2013, at 3:15 PM, Peter Zhai <peter.z...@gmail.com> wrote: > > > > Hello, > > > > My cloudstack 4.02 environment has 10 Xen 6.0 hosts ,i did not change > > anything lately but start from last week ,many of my Xen hosts will lost > > NIC after reboot ,which caused the VM instance on those hosts are not > able > > to start also. > > > > I guess it is not pool master issue because some of the slave host still > > function . I installed all the Xen server hotfix i can found but it did > not > > help at all . > > > > There is still enough disk space on host . > > > > Any one met the same issue before on Xen host ?? or KVM is more stable > > than Xen ? > > > > > > Peter >
