Information
To get Power Panel working for virtual machines (VM) hosted on Parallels Hypervisor (Parallels Cloud Server / Parallels Server Bare Metal), all of the following conditions must be met:
The Power Panel component of PVA Agent should be installed on the host server, with Container #1 running.
Verify that the
pva-pp
package is installed and that Port 4643 is listened to.Example:
[root@pcs ~]# rpm -qa pva-pp pva-pp-6.0-1351.510.noarch [root@pcs ~]# vzlist 1 CTID NPROC STATUS IP_ADDR HOSTNAME 1 3 running 192.168.216.28 - [root@pcs ~]# netstat -antp | egrep ':4643\>.*LISTEN' tcp 0 0 0.0.0.0:4643 0.0.0.0:* LISTEN 738180/init tcp 0 0 :::4643 :::* LISTEN 738180/init
The VM should be assigned with static IP addresses explicitly, not using DHCP or by setting IP addresses from the VM.
Check that the virtual machine has a static IP in the configuration file.
Example:
[root@pcs ~]# prlctl list testvm --info | egrep '^Home:' Home: /var/parallels/testvm.pvm/ [root@pcs ~]# sed -r '/<NetworkAdapter/,/<\/NetworkAdapter/ !d; /Enabled|VirtualNetworkID|StaticAddress|NetAddress|DefaultGateway/ !d ' '/var/parallels/testvm.pvm/config.pvs' <NetworkAdapter AdapterType_patch="1" id="1" dyn_lists="NetAddress DnsIPAddress SearchDomain"> <Enabled>1</Enabled> <VirtualNetworkID>Bridged</VirtualNetworkID> <StaticAddress>0</StaticAddress> <NetAddress>10.39.81.69/255.255.0.0</NetAddress> <NetAddress>10.39.81.84/255.255.0.0</NetAddress> <DefaultGateway>10.39.1.1</DefaultGateway> <DefaultGatewayIPv6></DefaultGatewayIPv6> <Enabled>0</Enabled>
Offline management should be enabled for the VM, and vzpp offline service should be configured.
Check that the virtual machine has these services in its configuration file.
Example:
[root@pcs ~]# prlctl list testvm --info | egrep 'Offline|services' Offline management: (+) services: 'vzpp-desktop' [root@pcs ~]# prlctl list testvm --info | egrep ^EnvID EnvID: 2139439666 [root@pcs ~]# awk '$2==2139439666' /proc/vz/veip 10.39.81.69 2139439666 10.39.81.84 2139439666
The VM and the host server should have the same gateway accessible via the same interface, i.e., the virtual machine should be connected to the virtual network attached to the primary interface of the node.
Verify that the virtual network is attached to the primary node interface and that the virtual network router is accessible via the Hardware Node default adapter.
Example:
[root@pcs ~]# vznetcfg net list | grep Bridged Bridged active eth0 vme6d4304c9.0,vme6592c3b9.0,vme65e9f1ff.0,vme56d3845f.0,vme62df2db9.0,vme7bf2b025.0,vme496492cc.0,vme7947aaac.0 [root@pcs ~]# ip route list | grep ^default default via 192.168.55.1 dev eth0 [root@pcs ~]# ping -c2 192.168.55.1 >/dev/null [root@pcs ~]# arp -an | grep 192.168.55.1 ? (192.168.55.1) at 90:e2:ba:49:1d:4c [ether] on eth0
NOTE: If any of the above conditions is not met, Power Panel will not function correctly.
Additional information
Also see:
- Power Panel (VZPP) issues troubleshooting
- VNC console does not work: "Network error: Socket is not connected"