ccollinscj Posted March 23, 2017 Share Posted March 23, 2017 The newer version of 6-6.3 breaks Citrix Netscaler 11 VPX. Ever since I upgraded the Netscaler does not work. The KVM VM RAW or qcow2 file and XML file that is you download from Citix. It is on verison 9.0 BSD, and it boots up, however I have tried every NIC available and none is recognized by the the VM os. Now when I use the same VM configuration on Centos KVM it works just fine with virtio drivers for the disk and nic. Is there something proprietary with Lime Techs version of KVM? Quote Link to comment
1812 Posted March 24, 2017 Share Posted March 24, 2017 you should post your comment/question here: and also be more specific about how it does not work, what errors you are getting, or how it is behaving. Quote Link to comment
ccollinscj Posted March 24, 2017 Author Share Posted March 24, 2017 10 minutes ago, 1812 said: you should post your comment/question here: and also be more specific about how it does not work, what errors you are getting, or how it is behaving. Do you really believe that this is a Lime Tech OS upgrade issue....This a integration issue with using a newer version of KVM/QEMU....there isn't any Lime Tech logs be because the adapter is not binding in side the VM. So my questions is to the KVM community and not the upgrade folks, unless they can tell me that there are some hooks inside Lime Tech that is changing how KVM / Qemu is operating. Since this works on Fedora 25 and Centos 7.3 KVM/Qemu. Quote Link to comment
1812 Posted March 24, 2017 Share Posted March 24, 2017 What I can tell you is that a few of my vm's started acting differently after upgrading from 6.2.4 to 6.3.2, and there are new errors occurring that were not there before. And the upgrade has caused issues on some servers changing everything from cpu numbering to issues with network adapters. So, what I do believe is that if your question is about how LT is using KVM and the specifics on how they implement it in 6.3 vs pervious versions, then you should ask in the 6.3 thread which appears to receive more immediate attention from LT official vs the KVM subform. Or you can wait around here, maybe get lucky tonight! Quote Link to comment
Soft-Man Posted March 25, 2021 Share Posted March 25, 2021 Any upgrades to this topic ? I have still the same issue with Citrix Netscaler, latest release, on Unraid 6.9.1 Any good news highy aprecciated 🙂 Regards Quote Link to comment
fa2k Posted May 8, 2021 Share Posted May 8, 2021 i compared the results of dmesg between a unraid netscaler vpx and a ubuntu netscaler vpx . i guess the problem is that the netscaler dont "see" its running in kvm. Unraid VM: platform: Manufacturer QEMU platform: serial number format error platform: sysid 3567 - DEFAULT Ubuntu VM: NSXN: NetScaler running over Virtual Platform platform: KVM platform: NetScaler Virtual Appliance 450070 (38), manufactured at 9/22/2012 platform: serial HE2JV262E4 platform: sysid 450070 - NetScaler Virtual Appliance the problem is that netscaler dont detect its running under kvm and disable the virtio drivers. tried the last days to get it working but without success. Any ideas why its detect QEMU and not kvm? if i run ubuntu under unraid and install qemu-kvm into, netscaler detects kvm Quote Link to comment
fa2k Posted May 9, 2021 Share Posted May 9, 2021 (edited) got it working..finally you can use virtio and virtio-net as disk type and network interface Edit the XML and add after </devices> (between </devices> and </domain> )following: <qemu:commandline> <qemu:arg value='-cpu'/> <qemu:arg value='Skylake-Client,kvm=on,vendor=GenuineIntel'/> </qemu:commandline> i guess it dont care which cpu model you use, but there are a list if needed at https://manpages.ubuntu.com/manpages/disco/man7/qemu-cpu-models.7.html Edited May 9, 2021 by fa2k smbios information isnt needed Quote Link to comment
Sander007 Posted May 24, 2021 Share Posted May 24, 2021 Hello fa2k how did you get it to start i get this error: nsnetsvc: BOOT FAILURE: One or more packet engines failed to start Quote Link to comment
fa2k Posted May 25, 2021 Share Posted May 25, 2021 maybe your cpu is older than what you try to emulate. Try Penryn from the list. Here is my whole xml file as reference: <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>UVPX1</name> <uuid>b71b7d12-e665-b7c4-843f-16f7d7e50c9c</uuid> <description>NetScaler VPX</description> <metadata> <vmtemplate xmlns="unraid" name="FreeBSD" icon="citrix1.png" os="freebsd"/> </metadata> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>4194304</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>2</vcpu> <cputune> <vcpupin vcpu='0' cpuset='7'/> <vcpupin vcpu='1' cpuset='17'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-5.1'>hvm</type> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='2' threads='1'/> <cache mode='passthrough'/> </cpu> <clock offset='utc'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='writeback'/> <source file='/mnt/SSD/VMs/UVPX1/NSVPX-KVM-13.0-79.64_nc_64.qcow2'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </disk> <controller type='pci' index='0' model='pci-root'/> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <interface type='bridge'> <mac address='52:54:00:de:b4:c7'/> <source bridge='br0'/> <model type='virtio-net'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='de'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </memballoon> </devices> <qemu:commandline> <qemu:arg value='-cpu'/> <qemu:arg value='Skylake-Client,kvm=on,vendor=GenuineIntel'/> </qemu:commandline> </domain> Quote Link to comment
Sander007 Posted May 25, 2021 Share Posted May 25, 2021 Thank you for your XML, i still get the error: i have this processor: Intel® Core™ i5-8259U CPU @ 2.30GHz Quote Link to comment
fa2k Posted May 26, 2021 Share Posted May 26, 2021 hmm. try to start VM then go to Tools -> System Logs and scroll down. The error message there should provide more informations whats the problem Quote Link to comment
Sander007 Posted June 4, 2021 Share Posted June 4, 2021 Thanks for your help it works if you make any change with de GUI you have to add the lines to the XML. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.