Jump to content
SolusVM Community

All Activity

This stream auto-updates     

  1. Yesterday
  2. Last week
  3. Rescue Mode not starting for KVM

    Hi, How are you booting the VPS into the rescue mode? Can you share more details on this that would be helpful to identify what exactly you are doing, so guys here can advise you more clearly..
  4. Windows Server 2016 + KVM Template = Not Working

    Hi, What issue you are getting while creating the KVM template? can you paste the output of the template creation here.
  5. resize not working on own templates

    Hi, Did you perform any custom partitioning inside the VM? You can create a VM with no swap partition and then try creating template from it..
  6. Create Template

    Hi, You can create a VPS with a template, configure it as you want, shutdown the VPS, and then from the SolusVM panel, you can use the create template feature provided by SolusVm. Check the below screenshot url: Screnshot
  7. Not enough available disk space left on node

    Hi, I can see that you have utilized all the available space and no more space is left for virtualization use. You did not mention what type of virutalization technology you are using on this server, but the partitioning is not proper and LVM for /home should be umounted and removed because for KVM and Xen, you should have Volume group with free space. so if you created all the LVM from it, then there is no space for the VPS to be deployed.. # umount /dev/mapper/volume-home # lvremove /dev/volume/home Once you do this, you will free space in volume group using below command: # vgdisplay The above is for KVM and Xen. If you are using OpenVZ, use below: # umount /dev/volume/home # mount /dev/volume/home /vz
  8. I have space, I'm using LVM, but it does not create the cloud. [root@localhost ~]# fdisk -l Disk /dev/sda: 1000.2 GB, 1000204886016 bytes, 1953525168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk label type: dos Disk identifier: 0x0004c3c6 Device Boot Start End Blocks Id System /dev/sda1 * 2048 2099199 1048576 83 Linux /dev/sda2 2099200 123226111 60563456 8e Linux LVM /dev/sda3 123226112 1953523711 915148800 8e Linux LVM Disk /dev/mapper/centos-root: 53.7 GB, 53687091200 bytes, 104857600 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/mapper/centos-swap: 8321 MB, 8321499136 bytes, 16252928 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/mapper/volume-home: 937.1 GB, 937108176896 bytes, 1830289408 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes
  9. Earlier
  10. Create Template

    Sorry, couldn't find exactly what I was looking for. I have openvz. I am taking a fully installed Debian 9 or Ubuntu 16.04 container and creating a template. I do everything required to add it to the template list I install on a new machine, and the machine just doesn't start. What am I missing here, something stupid? Happens every time. Thanks
  11. SolusVM module

    Hi, I installed WHMCS and SolusVM, but I'm unable to find SolusVM module in the installed WHMCS, I contacted with WHMCS support they said that I need to contact to SolusVM support. You may also verify from the attached screen shot, Please guide us 93.157.63.65 - SolusVM Enterprise Monthly License - 802409 (Active - Next Due Date: 2018-04-19)
  12. I am trying to create a Windows Server 2016 template but since the default cpu type of KVM is not supported by Windows Server 2016 the template I created is not working. I have to change the CPU type of the VM I am made with the template to 'Host Model' for get it working. The VM is being created from WHMCS. Can someone help?
  13. I've created debian generation 2 templates several times. But enlarging or reducing the DIsk vda1 does not work. The drive itself is changed to the desired size, but the primary drives are not. The debian installation has a size of 10GB, including 8GB for vda1 and 2GB for swap vda2. What do I have to keep in mind so that the resizing works correctly? The TDN templates centos 6 and 7 work fine with the resizing but debian and ubuntu not.
  14. Like described in the title... The Rescue Mode will not start for the KVM. It only reboots the virtual machine but not into rescue mode. is there any config made for the slave host?
  15. i got some trouble with the templates from tdn.solusvom.com eg the debian 9 and the ubuntu template I download the templates and add them to solusvm. Next, I install debian 9 or ubuntu from this template and the KVM does start but after the automatic update the kvm boots again and stops with message "crng init done" What is the error and how can I fix it? Is the Slave Host misconfigured? should i change something in the config? EDIT: The CentOS 6/7 templates work without problems
  16. Shared storage?

    All, is there a common setup for VPS hosting, especially regarding storage? Do you use shared storage to move virtual machines? Are you using NFS or iSCSI? Is ceph superior to "hardware" SAN? BTW: Is there any forum or mailing list for hosting providers? webhostingtalk seems to be more interesting for their clients. Only view have blogs and information about their infrastructure. - Chris
  17. meaning of slave and master

    Hello, You can deploy OpenVZ containers on the same server as your master control panel. If you want to deploy KVM VPS, you will need to have a 2nd server to host the VPS on.
  18. Problems with Xen xl on Centos 7

    This log information here suggests the bridge issue. You will have to get the bridge reconfigured again. It should be ONBOOT.
  19. Please try using a IP range that is used by other VM that is working with it.. You can follow up with your DC to check for IP routing.
  20. Oh I see, thanks!
  21. meaning of slave and master

    no one is there?
  22. Hello, I have talked with live chat but I am not able to understand their commercial language. Can anyone please tell me what is the concept? I want to create kvm, openvz vps'. Does it require 2 dedicated server? If yes then why? And if I engage 2 servers for solusvm then do I need to add another dedicated server for creating vps'? Thank you in advance to clearing my doubts.
  23. Please remove Solved at support.
  24. Hi, That partition looks to okay. Remember, you don't have to create LVM in the partition, so you can just create 3 main partition and keep the rest as it is. The 3 partitions are; /boot -> 1 GB / -> 50-80 GB swap -> same as RAM. Keep the rest unpartitioned, so later on you can create Volume group that can be used for LVM creation by solusvm..
  25. Every time I set up a new slave server I need support to do something to make it work. I was hoping I could get this going correctly from the start. Even though the support is great of course. I'm just stuck on the CentOS installer when it asks to add the Volume Group Name and LVM. The SolusVM instructions "https://documentation.solusvm.com/display/DOCS/KVM+on+RHEL+(CentOS)+7+Hypervisor+Installer" doesn't specify what to put in several boxes that are required. I attached an image with my guesses of what to add. Please let me know if it will work. Like /lvm2 for the partition and groupvol01 for the Volume Group Name. The image shows all the settings. Thanks! Charley
  26. Creating container on slave node issue

    Hello, I am creating the nodes manually/direct through the solusvm admin panel. The VPS is created successfully and running but the IP does not seem to resolve to the container... I have tried creating on both the master and the slave and tried all available IP blocks (other IP's in the range that I setup VPS for a few months ago work fine). Old VPS's created on both the master and slave work fine.
  27. Problems with Xen xl on Centos 7

    i have the same problem. has it been solved? [root@localhost network-scripts]# ifconfig eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether 54:04:a6:4f:c7:fa txqueuelen 1000 (Ethernet) RX packets 297315 bytes 42073699 (40.1 MiB) RX errors 0 dropped 4470 overruns 0 frame 0 TX packets 73096 bytes 7133006 (6.8 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 18 memory 0xfb700000-fb720000 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1 (Local Loopback) RX packets 1538 bytes 133734 (130.5 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1538 bytes 133734 (130.5 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255 ether 52:54:00:f9:9a:87 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 xenbr0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 10.1.21.185 netmask 255.255.255.0 broadcast 10.1.21.255 inet6 fe80::5604:a6ff:fe4f:c7fa prefixlen 64 scopeid 0x20<link> ether 54:04:a6:4f:c7:fa txqueuelen 1000 (Ethernet) RX packets 292809 bytes 35850595 (34.1 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 73100 bytes 6771870 (6.4 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vi ifcfg-eno1 TYPE="Ethernet" IPV6INIT="yes" IPV6_AUTOCONF="yes" IPV6_DEFROUTE="yes" NBOOT="yes" DEVICE="eno1" BRIDGE=xenbr0 vi ifcfg-xenbr0 DEVICE=xenbr0 TYPE=Bridge BOOTPROTO=static BROADCAST=10.1.21.255 IPADDR=10.1.21.185 NETMASK=255.255.255.0 NETWORK=10.1.21.0 ONBOOT=yes
  28. I've had solusvm up and running fine for a few years, I hadn't created a new VM in a few months... today I went to create a new VM and everything seems to go fine but I am unable to SSH into the new VM and when trying to access the IP address it just times out. I have a master and slave, both with working VM's running fine. the new container is created, I can see it fine in /vz/private/ the new container shows status of running. Maybe IP address is not routing properly? (I have several IP blocks available and other VM's are working fine with these neighboring IP addresses.. i have tested creating new containers on several IP's on both the master and slave nodes with no luck ) Any tips for testing if the IP is routed properly? it really looks like the container is created and running... just the IP is not resolving too it.
  1. Load more activity
×