@olivierlambert thanks for your answer
i didn't see the accessibility button. I can click on the virtual keyboard
sorry for the post.
Pierre
@olivierlambert thanks for your answer
i didn't see the accessibility button. I can click on the virtual keyboard
sorry for the post.
Pierre
Hi,
can I someone tell me how can get in audit mode on windows 10 installation?
I'm using latest xen-orchestra. Normally, Windows goes in audit mode on installation using the CTRL+SHIFT+F3
I've tried the keys in console with xen-orchestra or directly with xcp-ng center 20.04.01
thanks for the answer.
Pierre
Thanks, the problem came from the switch.
Thanks for your support.
Pierre
@darkbeldin
If it's true, i've no idea what is wrong.
The VM on the different hosts are on the same network.
Could RDP be blocked by host itself ?
the classic error. RDP could not open because
I've already tried. I'm using mremote-ng or windows RDP client to access my VMs, and it's the same. If the VM is stored on xcp-college => not working, and xen-college => working
Actually, i've made a backup of VM-Admin stored on xcp-college host and have restored it on xen-college host.
When it's working, in Xcp-ng Center, in the Console tab, i have RDP connexion like screenshot.
On the xcp-college host, if i click on "Switch to Remote Desktop", it does nothing
If i shutdown VM-Admin on xcp-college, and start it on xen-college host, it's working.
thanks for your answer
I don't think it's related to licenses.
The same VM is working fine on my old xcp-ng 8.1 host with RDP and not on the new hypervisor xcp-ng 8.2.
I've tried new VM (win7 and win10) client, it's the same. So i've concluded that the problem is not specific to the client but specific to the host or hardware?
Can someone confirm that? and how fix that?
thanks
Pierre
Hi,
i've decided to post because i'm going crazy.
I had an old hypervisor running xcp-ng 8.1 and several VMs (win7 and win10) clients on it.
The RDP was working fine.
Last month, i've built a new server with xcp-ng 8.2 and move these VMs on the new server. Now, Remote Desktop doesn't anymore.
I thought it came from antivirus kaspersky and made some changes on VMs but it doesn't work.
So i've tried to move one VM from the new xcp-ng to the old xcp-ng, and it works! RDP works!
I've checked my firewall rules but i haven't found specific rules related to my old xcp-ng allowing RDP port 3389.
Can someone have some ideas as i'm going crazy.
I'm missing something?
thanks
Pierre
@stormi
As Xcp-center reports that agent is not installed, i was afraid that it wouldn't work as expected.
I don't want to have low performances on that VM which will be the internet gateway.
yes, they are renaming the network interfaces (like red0, green0, blue0) and perhaps it's the problem.
So the agent should work as expected in PVHVM ? My previous VM it was only in PV.
thanks for your answer
So i've made a mistake? the VM has an IPv4 address in local network but no gateway yet
@stormi
Thanks
Now, the OS seems to be detected
Here is the content of /var/cache/xe-linux-distribution
[root@ipfire-test ~]# cat /var/cache/xe-linux-distribution
os_distro="ipfire"
os_majorver="2"
os_minorver="unknown"
os_uname="5.10.55-ipfire"
os_name="IPFire 2.27 (x86_64) - core160"
[root@ipfire-test ~]#
I still don't know why xcp-center doesn't detect the agent management and if it would work as expected
I also change the xe-linux-distribution in /etc/init.d because the function action is not available in ipfire. I don't know what is the best way.
Is there anything to change?
thanks
Pierre
Hi @stormi
I've tried to modify the xe-linux-distribution file but i definitly don't have the skills to modify it. I don't understand the sed commands to identify
Can someone help me with that?
thanks in advance
Pierre
Hi @stormi
Thanks for your answer
Hi @Pierre-Briec,
If Ipfire is based on LFS, I suppose there's no RPM nor DEB package management. In this case you can use the .tgz tarball and install it manually, and make sure to install enable the
xe-linux-distribution
service (using the provided initscript or the systemd unit). But maybe there's a way to install a RPM or a DEB package through some compatibility tool, in which case you may try them.
That's true. There is only a package management pakfire for the addons. I will look at the tgz if i can install it.
Ipfire is using SysVinit script. I'm not very familiar with that and if someone can help me with that.
You may also have to tweak the
xe-linux-distribution
file to make it recognize your distro. If it has a/etc/os-release
file, then future versions ofxe-linux-distribution
, not released yet, will recognize it automatically.
I can provide this file /etc/os-release
NAME="IPFire"
VERSION="2.27"
ID=ipfire
VERSION_ID=2
PRETTY_NAME="IPFire 2.27 (x86_64) - core160"
ANSI_COLOR="0:31"
hope it helps
Ideally, it would be nice to work towards pushing the tools directly in the distro, so that you could install them from their repositories when needed. We can provide some help if a packager gets it touch with us or if you want to try to contribute them yourself.
The IPFire is a german project so it's not easy for me to communicate with the team. I can make tests and even provide a remote access to a VM test through XO if need.
thanks
Pierre
Hi @stormi ,
I have an Ipfire fresh VM which is not detected by the installer. How can I add support for this distro which seems to be LFS (linux from scratch) based.
I would like to have the guest-tools installed on it.
Can you help me please or tell me how can i add it manually?
I can provide all information you want.
thanks in advance
Pierre