The VM starts, but..

[mka@…]

Only via NAT ... In the past Time i write a help to the Forum. (Sorry i found my own articles not)

My VM on zentyal (2.2.3) starts only whit NAT. if i change the networksettings to only local network - zentyal brings up a errormsg. whit a link to trac.zentyal.

/var/log/zentyal.log - last msg:

2011/11/10 08:22:38 INFO> GlobalImpl?.pm:653 EBox::GlobalImpl::saveAllModules - Changes saved successfully 2011/11/10 08:23:08 ERROR> Sudo.pm:213 EBox::Sudo::_rootError - root command /var/lib/zentyal/machines/xpklon/manage.sh start failed. Error output: error: Failed to create domain from /var/lib/zentyal/machines/xpklon/domain.xml

error: Network not found: no network with matching name 'xpklon'

Command output: . Exit value: 1 2011/11/10 08:25:45 INFO> Service.pm:716 EBox::Module::Service::restartService - Restarting service for module: firewall

thanks a lot...

[jamor@…]

Hello Mka,

recently we had a problem similar with virtual machines having spaces or non-ascii charecter on their names. What is the name of your VM?

[mka@…]

sorry for late answer..

if i call up the URL (https://trac.zentyal.org/) from this Msg. i have a error whit firefox (Fehlercode: ssl_error_handshake_failure_alert)

iceweasel says in german: Fehler beim Lesen der Daten aus dem TLS-Socket: Ein fataler TLS-Alarm wurde empfangen.

 http://trac.zentyal.org/report/1 without security - no problems to se the side.

the second issue on this machine is: i see the machine in zentyal.cloud. and the dyndns service (zentyal.me) works also. i can lookup the ip (eg. ping on name gives the IP back) but i dont have ssh or https access to the machine. (i think its a problem on the netgear firewall - on different hardware) i go tomorrow to the customer, to solve this problem. and i change the settings of the VM from NAT to "LAN Only"

the (NetBIOS) name of the VM is always lower case whiteout spaces or else. for example: xpklon (for a Win XP VM) ntklon (for a Win NT VM)

[jacalvo@…]

(In [23699]) NN: + Internal networks now work in KVM (closes #3465)

+ Optimize check status operation in KVM using domstate command + Start VNC proxies only when necessary, this also avoids wrong alerts