Linux - Virtualization and CloudThis forum is for the discussion of all topics relating to Linux Virtualization and Linux Cloud platforms. Xen, KVM, OpenVZ, VirtualBox, VMware, Linux-VServer and all other Linux Virtualization platforms are welcome. OpenStack, CloudStack, ownCloud, Cloud Foundry, Eucalyptus, Nimbus, OpenNebula and all other Linux Cloud platforms are welcome. Note that questions relating solely to non-Linux OS's should be asked in the General forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am using centos 6.2 vmdk templet downloaded from : http://stacklet.com/.
It is 10 gb machine.
When I am increasing to 20 gb using fdisk /dev/sda command.
It successfully increase the harddisk size to 20 gb.
But when i zip that virtual machine and reuse it it does not give the IP address.
I check all networking file,it is proper.
When i am restart network it gives me this error eth0 is not present delaying initialisation.
What will be the problem.
If you have a /etc/udev/rules.d/70-persistent-net.rules (the number may vary between distros -- that is for Slackware 13.1) you could try deleting it and rebooting.
Lookup UDEV rules as well on the above. Running through the above commands could reveal more clues. If it doesn't help, it could move you closer to the root cause.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.