Welcome Guest. Please Login or Register  


You are here: Index > Virtualizor - Virtual Server Control Panel > General Support > Topic : Issues by installing and set up Virtualizor

1


Threaded Mode | Print  

 Issues by installing and set up Virtualizor (16 Replies, Read 6372 times)
indy0077
Group: Member
Post Group: Working Newbie
Posts: 90
Status:
I opened this thread just to get some important information about installation and settings of Virtualizor from Virtualizor staff and forum members which will help others by solving similar problems or issues.

The Virtualizor documentation is not detailed enough to solve some issues durring set up new servers and configuration.

IP: --   

Issues by installing and set up Virtualizor
indy0077
Group: Member
Post Group: Working Newbie
Posts: 90
Status:
I installed VIRTUALIZOR for KVM virtualization on a new dedicated server.

The specifications are as follow:

CPU: Intel Xeon E5-1620v2
Cores: 4c/8t
Freq.: 3.7GHz/3.9GHz
RAM: 16GB DDR3 ECC 1333 MHz
Disk: SoftRaid 2x2TB SATA
OS: CentOS 7.3-1611 (64bits)

1 main/server IP
1 additional single IP
2x /29 IP blocks (16 IPs)

After struggling with partitioning (support helped me with) and making the cofiguration like described on the internet in some forums and blogs (the VIRTUALIZOR documentation is very "simple" and short, not detailed, without some examples of configuration and settings) I started to create first KVM VPS. After setting up the parameters of the wanted VPS and creating, I got a lot of errors.

Here is the log of the creation:

Code

Starting Task : 1
Syncing up with Slave
Creating VPS : 1
File descriptor 3 (socket:[801635]) leaked on lvcreate invocation. Parent PID 17424: /usr/local/emps/bin/php
File descriptor 4 (socket:[803810]) leaked on lvcreate invocation. Parent PID 17424: /usr/local/emps/bin/php
File descriptor 5 (socket:[801736]) leaked on lvcreate invocation. Parent PID 17424: /usr/local/emps/bin/php
File descriptor 3 (socket:[801635]) leaked on lvdisplay invocation. Parent PID 17424: /usr/local/emps/bin/php
File descriptor 4 (socket:[803810]) leaked on lvdisplay invocation. Parent PID 17424: /usr/local/emps/bin/php
File descriptor 5 (socket:[801736]) leaked on lvdisplay invocation. Parent PID 17424: /usr/local/emps/bin/php
File descriptor 3 (socket:[801635]) leaked on lvresize invocation. Parent PID 17424: /usr/local/emps/bin/php
File descriptor 4 (socket:[803810]) leaked on lvresize invocation. Parent PID 17424: /usr/local/emps/bin/php
File descriptor 5 (socket:[801736]) leaked on lvresize invocation. Parent PID 17424: /usr/local/emps/bin/php
New size (2560 extents) matches existing size (2560 extents).
sfdisk: Warning: The partition table looks like it was made
for C/H/S=*/4/32 (instead of 1305/255/63).
For this listing I'll assume that geometry.

Checking that no-one is using this disk right now ...
BLKRRPART: Invalid argument
OK
sfdisk: Warning: The partition table looks like it was made
for C/H/S=*/4/32 (instead of 1305/255/63).
For this listing I'll assume that geometry.

Warning: partition 1 does not end at a cylinder boundary
Warning: partition 2 does not start at a cylinder boundary
Warning: partition 2 does not end at a cylinder boundary
Warning: no primary partition is marked bootable (active)
This does not matter for LILO, but the DOS MBR will not boot this disk.
BLKRRPART: Invalid argument
If you created or changed a DOS partition, /dev/foo7, say, then use dd(1)
to zero the first 512 bytes:  dd if=/dev/zero of=/dev/foo7 bs=512 count=1
(See fdisk(8).)
device-mapper: remove ioctl on vg-vsv1001--0kkc--bqmfvb2f19gs0jbi2 failed: Device or resource busy
e2fsck 1.42.9 (28-Dec-2013)
resize2fs 1.42.9 (28-Dec-2013)
Creation Done
Setting Root / Admin Password
setlocale: No such file or directory
Building DHCP
Redirecting to /bin/systemctl restart  dhcpd.service
Starting VPS
setlocale: No such file or directory
setlocale: No such file or directory
Illegal target name 'vmv1001'.
Illegal target name 'vmv1001ARPIN'.
Illegal target name 'vmv1001ARPIN'.
Chain 'vmv1001' doesn't exist.
Chain 'vmv1001ARPIN' doesn't exist.
setlocale: No such file or directory
error: failed to get domain 'v1001'
error: Domain not found: no domain with matching name 'v1001'
Cannot find device "viifv1001"
Cannot find device "viifv1001"
Fetching VPS Status
setlocale: No such file or directory
Errors:

Array
(
[err_start] => There was an error while starting the new VPS
setlocale: No such file or directory
error: Failed to create domain from /etc/libvirt/qemu/v1001.xml
error: internal error: qemu unexpectedly closed the monitor: 2017-07-24T08:27:26.923835Z qemu-kvm: -device Realtek,netdev=hostnet0,id=net0,mac=02:00:00:a6:6c:3c,bus=pci.0,addr=0x3: 'Realtek' is not a valid device model name

)


So it seems, there was deffinitely some misconfiguration from my side.
The support team fixed it, but didn't provide any details what are they changed or fixed. Of course without that information, I cannot create an another VPS or install Virtualizor on another server, if I don't know what's going on.

So the questions. What these errors mean?

  1. File descriptor 3 (socket:[801635]) leaked on lvcreate invocation.
  2. sfdisk: Warning: The partition table looks like it was made for C/H/S=*/4/32 (instead of 1305/255/63). For this listing I'll assume that geometry.
  3. BLKRRPART: Invalid argument
  4. Warning: partition 1 does not end at a cylinder boundary Warning: partition 2 does not start at a cylinder boundary
  5. setlocale: No such file or directory
  6. Illegal target name 'vmv1001'. Illegal target name 'vmv1001ARPIN'.
  7. Chain 'vmv1001' doesn't exist. Chain 'vmv1001ARPIN' doesn't exist.
  8. error: failed to get domain 'v1001' error: Domain not found: no domain with matching name 'v1001'
  9. Cannot find device "viifv1001"
  10. Errors: Array ( [err_start] => There was an error while starting the new VPS setlocale: No such file or directory error: Failed to create domain from /etc/libvirt/qemu/v1001.xml error: internal error: qemu unexpectedly closed the monitor: 2017-07-24T08:27:26.923835Z qemu-kvm: -device Realtek,netdev=hostnet0,id=net0,mac=02:00:00:a6:6c:3c,bus=pci.0,addr=0x3: 'Realtek' is not a valid device model name )

Can someone explain the errors?

Thanks
IP: --   

Issues by installing and set up Virtualizor
jevingala
Group: Virtualizor Team
Post Group: Super Member
Posts: 739
Status:
Hi,

You can ignore errors from 1-9 which are not responsible for errors while creating/starting the vps.

For, Realtek' is not a valid device model name,

>> You can edit the vps and click on save without making any changes and then try to start that vps.
If the vps is created using plan then you will need to edit the plan and click on save without changing anything so that future vpses don't get affected while getting started.


-----------------------
Regards,
Virtualizor Team.
http://virtualizor.com/
IP: --   

Issues by installing and set up Virtualizor
indy0077
Group: Member
Post Group: Working Newbie
Posts: 90
Status:
Quote From : jevingala July 26, 2017, 5:44 am
Hi,

You can ignore errors from 1-9 which are not responsible for errors while creating/starting the vps.

For, Realtek' is not a valid device model name,

>> You can edit the vps and click on save without making any changes and then try to start that vps.
If the vps is created using plan then you will need to edit the plan and click on save without changing anything so that future vpses don't get affected while getting started.



Thank you.
IP: --   

CPU and CPU units
indy0077
Group: Member
Post Group: Working Newbie
Posts: 90
Status:
I read this in one article:

  • KVM VPS will start only if you set "CPU %" to "0" and "CPU units" to "1000" !!! These variables are defined inside VIrtualizor, "VPS Plan" page and VPS configuration editting page. If misconfigured, some VPS will be 99% CPU overloaded or do not start at all.
  • Be careful about "Enable RDP" inside VPS configuration and VPS Plan settings, VPS may not boot.
  • unable to setup more than 18000 MB RAM to a KVM VPS, else it shutdown ~1 min. after boot

Is that true?

IP: --   

Issues by installing and set up Virtualizor
jevingala
Group: Virtualizor Team
Post Group: Super Member
Posts: 739
Status:
Hi,

If the kernel is custom then issues will arise.
Also multivirt can cause issues with shutting down of Kvm vpses .

Regarding RDP, vps booting issue should not arise.


-----------------------
Regards,
Virtualizor Team.
http://virtualizor.com/
IP: --   

CPU and CPU units
indy0077
Group: Member
Post Group: Working Newbie
Posts: 90
Status:
Ok, then what should be set up in "Edit Virtual Server > CPU Units/CPU Cores/CPU %

Thanks
IP: --   

Issues by installing and set up Virtualizor
jevingala
Group: Virtualizor Team
Post Group: Super Member
Posts: 739
Status:
Hi,

Setting cpu units as 1000 , cores as 2 and % to 50 should be fine for average usage in vps with original/stock kernel on your server.


-----------------------
Regards,
Virtualizor Team.
http://virtualizor.com/
IP: --   

Issues by installing and set up Virtualizor
indy0077
Group: Member
Post Group: Working Newbie
Posts: 90
Status:
Quote From : jevingala July 26, 2017, 7:11 am
Hi,

Setting cpu units as 1000 , cores as 2 and % to 50 should be fine for average usage in vps with original/stock kernel on your server.


For each new created VPS server?


IP: --   

Issues by installing and set up Virtualizor
indy0077
Group: Member
Post Group: Working Newbie
Posts: 90
Status:
I followed this tutorial http://www.virtualizor.com/wiki/Install_KVM but the Virtualizor shows 0 GB space. This is the second time I tried to install the KVM and got same issue. Installing OpenVZ with the installation instruction went without any issues. But by KVM I'm still missing the storage. The support fixed it by the first installation and provided to me this information:

Quote

Could you please reinstall your server as per given

Root '/' ---->80-100GB
Swap ---->4Gb+
All remaining space(mounted on) /home


I did, but it didn't work. Then they fixed it and told to me:

Quote
Sir, You partition was mounted on /home partition so we have just unmonuted /home partition and then created vg and added on your panel.

umount /home
pvcreate /dev/md3
vgcreate vg /dev/md3


What is the problem? And where are these things mentionted in the installation tutorial on their site?

Regards



IP: --   

Issues by installing and set up Virtualizor
indy0077
Group: Member
Post Group: Working Newbie
Posts: 90
Status:
So, after following these support steps:



Code
[root@vs ~]# umount /home [root@vs ~]# pvcreate /dev/md3 WARNING: ext4 signature detected on /dev/md3 at offset 1080. Wipe it? [y/n]: y Wiping ext4 signature on /dev/md3. Physical volume "/dev/md3" successfully created. [root@vs ~]# vgcreate vg /dev/md3 Volume group "vg" successfully created [root@vs ~]# reboot




the server is being INACCESSIBLE - no ssh access, no Virtualizor access.



Code
--- 158.69.252.161 ping statistics --- 10 packets transmitted, 0 packets received, +6 errors, 100% packet loss




What now?
IP: --   

Issues by installing and set up Virtualizor
jevingala
Group: Virtualizor Team
Post Group: Super Member
Posts: 739
Status:
Hi,

Was the mount entry for home commented in fstab file ?


-----------------------
Regards,
Virtualizor Team.
http://virtualizor.com/
IP: --   

Issues by installing and set up Virtualizor
indy0077
Group: Member
Post Group: Working Newbie
Posts: 90
Status:
Quote From : jevingala August 18, 2017, 5:48 am
Hi,

Was the mount entry for home commented in fstab file ?


No, it was nont, because as you can see, your support didn't provide this information to us.
IP: --   

Issues by installing and set up Virtualizor
jevingala
Group: Virtualizor Team
Post Group: Super Member
Posts: 739
Status:
Hi,

We assume that you have basic understanding about Linux .
You can enable rescue mode and comment the required entry and then restart and check.

Sorry for the inconvenience caused.


-----------------------
Regards,
Virtualizor Team.
http://virtualizor.com/
IP: --   

Issues by installing and set up Virtualizor
indy0077
Group: Member
Post Group: Working Newbie
Posts: 90
Status:
Quote From : jevingala August 18, 2017, 6:10 am
Hi,

We assume that you have basic understanding about Linux .




Assuming is good, but as you can see, it's not working in such situations. All would be sorted quickly, if you provide a detailed step by step instructions with command examples like the biggest server provider does. If they would assume, that everybody is a Linux expert, then they will probably fail on sales very soon.
IP: --   

« Previous    Next »

Threaded Mode | Print  

1


Jump To :


Users viewing this topic
1 guests, 0 users.


All times are GMT. The time now is March 19, 2024, 9:12 am.

  Powered By AEF 1.0.8 © 2007-2008 Electron Inc.Queries: 11  |  Page Created In:0.029