Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Virtualizor Bugs - Page 2
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Virtualizor Bugs

24

Comments

  • NexHostNexHost Member
    edited August 2015

    Look how shit the support is this is all they respond with

     Hi,
    
     There seems to be some issue with vps.
     Can you reboot the main node once ?
    

    What after I reboot the node 3 days ago? That caused one of my clients to go mat at me on a Public Forum and now it has left a VM OFFLINE all Night. and that is all they can respond with.

    Comon everyone switch to Virtualizor and have to reboot your Production nodes every couple of days as that is what the support tell you to do.

  • I have found adding them on Skype, sometimes gets your issue resolved a lot quicker than going back and forwards via the ticket system.

    Have they resolved your issue now?

  • Skype: virtualizor

  • NexHostNexHost Member
    edited August 2015

    @AshleyUk said:
    I have found adding them on Skype, sometimes gets your issue resolved a lot quicker than going back and forwards via the ticket system.

    Have they resolved your issue now?

    I have them on Skype and it's being looked at but given the reply to reboot the node. is unacceptable. The Node was rebooted the other day to perform a Bios Upgrade. Now that there is a newer kernel version a bug occurs again. resulting in having to downgrade or wait for Virtualizor to fix it. Cannot just reboot the node it will annoy the customers.

     [14:14:43] Dave: panel
     [14:14:48] Dave: hhas left a customers vm offline all night
     [14:15:18] Dave: nope
     [14:15:20] Dave: I submit a ticket
     [14:15:25] Dave: still unanswered still unresolved
     [14:15:30] Dave: and my clients vm is still down
     [14:15:38] Dave: The VPS failed to start
     error: Failed to create domain from /etc/libvirt/qemu/v1127.xml
     error: An error occurred, but the cause is unknown
    
  • jazz1611jazz1611 Member
    edited August 2015

    @jmckeag12 when start that VM, what error show? can you send file xml to me?

  • Move to solus. Manually.

  • AshleyUkAshleyUk Member
    edited August 2015

    @jmckeag12 said:
    error: An error occurred, but the cause is unknown

    What is outputted when you run :

    virsh define /etc/libvirt/qemu/v1127.xml

    &

    virsh start v1127

    within SSH?

  • @jazz1611 said:
    jmckeag12 when start that VM, what error show? can you send file xml to me?

     Last login: Tue Aug 18 15:43:42 2015 from triband-mum-120.62.**.**.mtnl.net.in
     root@kvm-hdd-lax01:~# virsh create /etc/libvirt/qemu/v1127.xml
     error: Failed to create domain from /etc/libvirt/qemu/v1127.xml
     error: An error occurred, but the cause is unknown
    
  • NexHostNexHost Member
    edited August 2015

    @AshleyUk said:

     root@kvm-hdd-lax01:~# virsh define /etc/libvirt/qemu/v1127.xml
     Domain v1127 defined from /etc/libvirt/qemu/v1127.xml
    
     root@kvm-hdd-lax01:~# virsh start v1127
     error: Domain is already active
    

    And everything is working now. not sure if that helped or Virtualizor have fixed it.

    Ah nvm the VM just auto shuts down after a while.

     2015-08-18 13:53:52.292+0000: 12028: error : printVar:273 : internal error: Buffer too small to print variable 'IP' into
     2015-08-18 13:54:34.504+0000: 12028: warning : qemuDomainObjTaint:1628 : Domain       id=77 name='v1127' uuid=882fe42c-f4f9-46f3-8471-354f3d289b15 is tainted: host-cpu
     2015-08-18 13:56:09.672+0000: 12030: warning : qemuDomainObjTaint:1628 : Domain id=78 name='v1127' uuid=882fe42c-f4f9-46f3-8471-354f3d289b15 is tainted: host-cpu
     2015-08-18 13:57:37.876+0000: 12030: error : printVar:273 : internal error: Buffer too small to print variable 'IP' into
     2015-08-18 13:58:37.088+0000: 12028: warning : qemuDomainObjTaint:1628 : Domain id=80 name='v1127' uuid=882fe42c-f4f9-46f3-8471-354f3d289b15 is tainted: host-cpu
    
  • jazz1611jazz1611 Member
    edited August 2015

    @jmckeag12 maybe same <uuid>xxxx</uuid> with other VM

  • Seems for some reason Virtualizor couldn't start the VM, weather its failing to define the QEMU XML file first before trying to start now sure.

    Glad you have got it running now, if Virtualizor GUI ever fails, you can always run the above two commands to get a VM at least up and running / see any errors with the XML config.

  • @jazz1611 said:
    jmckeag12 maybe same <uuid>xxxx</uuid> with other VM

    The bug is to do with IPv6 when it's applied to the VPS. that is what is causing it to fail to start. that is what one of the developers just told me.

  • jazz1611jazz1611 Member
    edited August 2015

    @jmckeag12 Domain id 78 vs 80 was same UUID. Please look it or change different UUID by yourself. maybe it will solved issues.

  • @jmckeag12 said:

    it seems there is a issue with your xml syntax in that file as determined by:

    qemuDomainObjTaint:1628 : Domain id=80 name='v1127' uuid=882fe42c-f4f9-46f3-8471-354f3d289b15 is tainted: host-cpu

    I would recommend to go manually into that file with nano or your favorite command line editor and check that out as I had issues like that, that I went into the xml file manually and fixed the issue and didn't have a problem since.

  • NexHostNexHost Member
    edited August 2015

    @jazz1611 said:
    jmckeag12 Domain id 78 vs 80 was same UUID. Please look it or change different UUID by yourself. maybe it will solved issues.

    There is no domain ID 78 or 80. that seems to be entry logs by the looks of it. and it goes up by number or something.

    Domain ID is 1045 with the vm id being v1127

    The issue is resolved anyway. Thank you everyone on LET for your assistance. :)

    Thanked by 1AshleyUk
  • what problems are you having with IPv6 ? I'm having some fun with assigning subnets.

    a /128 works, but a /112 doesn't unless I also have a /128. waiting for solution from virtualizor

  • NexHostNexHost Member
    edited August 2015

    @Bruce said:
    what problems are you having with IPv6 ? I'm having some fun with assigning subnets.

    a /128 works, but a /112 doesn't unless I also have a /128. waiting for solution from virtualizor

    I have the same issue as you are experiencing also. /112 works fine but anything else does not work. allocating from a /48 IPv6 subnet block.

    Does not work: 2604:d180:0009:0577:0000:0000:000d:0c33

    How ever this will work so is there no DHCPv6?

    2604:d180:0009:270c:0000:0000:0000:0020

  • /112 does work? for me, it isn't.

  • NexHostNexHost Member
    edited August 2015

    @Bruce said:
    /112 does work? for me, it isn't.

    The address provided above does not work. if I manually adjust the config on the VPS and use say 2604:d180:0009:270c:0000:0000:0000:0033 it will work here is a example. give me sometime I'll update this post with a example.

     [root@solusvm ~]# ping6 ipv6.google.ccom
     unknown host
    
     inet6 addr: 2604:d180:9:577::13d:6ed5/64 Scope:Global
    
     IPV6ADDR=2604:d180:0009:0577:0000:0000:013d:6ed5/64
    

    If I modify the /64 to a /48 IPv6 works fine. I thought I had allocated a single address not a subnet. as it's not possible to route several /64s as I don't handle the routing. Using a Juniper EX3300 been told that it's not good at handling L3 so I have to let my upstream provider route it as a single /48 or a single /64 won't route any more IPv6 subnets unless we grow and purchase more rackspace.

     [root@solusvm network-scripts]# ping6 ipv6.google.com
     PING ipv6.google.com(lax02s21-in-x0e.1e100.net) 56 data bytes
     64 bytes from lax02s21-in-x0e.1e100.net: icmp_seq=1 ttl=50 time=11.1 ms
     64 bytes from lax02s21-in-x0e.1e100.net: icmp_seq=2 ttl=50 time=8.30 ms
    
  • trying to work out exactly what virtualizor does with bridging. makes my brain hurt. they don't include the IP info in the libvirt xml files, so presumably it's dhcp from viifbr0

  • NexHostNexHost Member
    edited September 2015

    OK so after I made this thread. again run into a issue. Because they have a bugged multivirt product. I have had to SLAB the containers for another customer. How ever the slabbed filled up the entire VM and I had to extend the partition.

    How ever now Virtualior are giving me bullshit responses again. and have left this particular node offline now for 12 + hours. and it's going to bypass the 24 hour mark soon. I have asked them multiple times to help resolve the ebtables issue. So the tech on Skype said he is sorting it and he just logs off for the night. and has left it offline...

  • jmckeag12 said: ebtables

    What exact eatables problems were you having? I had a run the other day with the entire nodes networking to just stop, unless the server was rebooted.

  • NexHostNexHost Member
    edited September 2015

    @OnraHost said:
    What exact eatables problems were you having? I had a run the other day with the entire nodes networking to just stop, unless the server was rebooted.

    It's blocking the slab from binding the IPs to each container. so there is no networking. Virtualizor have restored it until the staff that are on shift tomorrow start. as they are the only ones who are capable of fixing it apparently.

    I would never run a SLAB myself but it was required. to get around the fact that all the KVM VPS on the multivirt node had issues booting.

  • 5 + Days now and no resolution.

  • jmckeag12 said: 5 + Days now and no resolution.

    You say this like it's something they're going to fix quickly. You're cute; it's most likely going to be weeks or months. I don't really know what they do with their release/testing cycles, but they don't seem to have any sort of validation process in place.

  • @jmckeag12 said:
    5 + Days now and no resolution.

    I have 1 month now and so resolution keep telling they fix in next update which never happens...

  • NexHostNexHost Member
    edited October 2015

    Another day another issue

     root@s3:/home# virsh create /etc/libvirt/qemu/v1002.xml
     error: Failed to create domain from /etc/libvirt/qemu/v1002.xml
     error: An error occurred, but the cause is unknown
    
     2015-10-02 11:30:44.021+0000: starting up
     LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin       QEMU_AUDIO_DRV=none /usr/bin/kvm -name v1002 -S -machine pc-i440fx-   trusty,accel=kvm,usb=off -cpu host -m 1536 -realtime mlock=off -smp    2,sockets=2,cores=1,threads=1 -uuid 0dda3fb3-cbf3-4c64-a433-1644ca968a1b -no-      user-config -nodefaults -chardev     socket,id=charmonitor,path=/var/lib/libvirt/qemu/v1002.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -boot o      rder=c,menu=on,strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/dev/s3-vg/vsv1002-0ix3-fzvambm1re9oips4,if=none,id=drive-virtio-disk0,format=raw,cache=none,aio=native -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0 -netdev tap,fd=25,id=hostnet0,vhost=on,vhostfd=34 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=00:16:3e:79:6d:29,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -device usb-tablet,id=input0 -vnc 104.255.227.146:2,password -k en-us -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-micro,id=sound0-codec0,bus=sound0.0,cad=0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6
     Domain id=45 is tainted: host-cpu
     char device redirected to /dev/pts/3 (label charserial0)
    qemu: terminating on signal 15 from pid 2162
    2015-10-03 03:48:23.924+0000: shutting down
    2015-10-03 03:48:53.208+0000: shutting down
    2015-10-03 03:49:00.479+0000: shutting down
    2015-10-03 03:49:14.708+0000: shutting down
    2015-10-03 04:10:16.769+0000: shutting down
    2015-10-03 04:11:17.959+0000: shutting down
    2015-10-03 04:11:31.239+0000: shutting down
    2015-10-03 04:12:35.080+0000: shutting down
    2015-10-03 04:12:41.425+0000: shutting down
    2015-10-03 04:12:51.359+0000: shutting down
    2015-10-03 04:13:16.253+0000: shutting down
    2015-10-03 04:15:31.392+0000: shutting down
    2015-10-03 04:16:39.872+0000: shutting down
    

    I am getting sick and tired of this now. constantly having to submit tickets and nodes being rebooted by their support.

  • NexHostNexHost Member
    edited October 2015

    So virtualizor tech via skype told me to reboot a Production node that it would fix it. exactly as I thought reboot is what they would tell me to do. reboot a node that was up for 50 days when there was no need to reboot it in the first place!

    Exactly as I thought.

  • @jmckeag12 said:
    So virtualizor tech via skype told me to reboot a Production node that it would fix it. exactly as I thought reboot is what they would tell me to do. reboot a node that was up for 50 days when there was no need to reboot it in the first place!

    Exactly as I thought.

    In the past i never had any issues still dont do but the last few releases are quite buggy
    i submitted them some bugs themselves which i found and they solved them fast.

    So make sure you are on stable release of virtualizor and up to date.

Sign In or Register to comment.