I think that things in the boot loader (initrd-default.img), because as soon as it starts to import the core files, monitor the "thin client" is turned off. Other VMs on the network is not, and the server Openqrm too. Or are all the same problems in a "thin client"? HELP.
Thahks.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I changed the thin client. Video no longer disappear. Now, after an error message "New resource detected! Adding to the openQRM-server at 192.168.0.2"
Error: Could not reach the openQRM-Server at 192.168.0.2!
bash: cannot set terminal process group (-1): Inappropriate ioctl for device
bash: no job control in this shell
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
would you please check that the network interface of the pxe booting system is correctly detected during the last stage of initrd ?
Strange is that it seemed to be able to connect to the openQRM server because it was added as new resource.
The message from bash "no job control + inap. ioctl" you can simply ignore.
many thanks and have a nice day,
Matt Rechenburg
Project Manager openQRM
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello!
But my problem is not solved, three days ago I read your forum.
Openqrm 4.9 installed on Ubuntu 10,4 with "HOW to ..".
Chose KVM - the hypervisor.
"Lifted" VM (windows 7-64) on the KVM-Host.
I have access to the VM from the server via VNC OpenQRM
And when I want to start up VM to "thin client", he finds dhcpd, tftp!
But when it starts to import the core files, turned off the monitor with the message that there is no video signal. * (
Ping IP obtained via DHCP runs.
Thank you.
PS Sorry for my english
Hi,
this means your VM is booted into "idle" mode and you can now start to deploy it.
strange about the missing video signal. Is the VM still pingable ?
many thanks and have a nice day,
Matt Rechenburg
Project Manager openQRM
Hi.
I think that things in the boot loader (initrd-default.img), because as soon as it starts to import the core files, monitor the "thin client" is turned off. Other VMs on the network is not, and the server Openqrm too. Or are all the same problems in a "thin client"? HELP.
Thahks.
up
I changed the thin client. Video no longer disappear. Now, after an error message "New resource detected! Adding to the openQRM-server at 192.168.0.2"
Error: Could not reach the openQRM-Server at 192.168.0.2!
bash: cannot set terminal process group (-1): Inappropriate ioctl for device
bash: no job control in this shell
up
Hi again,
would you please check that the network interface of the pxe booting system is correctly detected during the last stage of initrd ?
Strange is that it seemed to be able to connect to the openQRM server because it was added as new resource.
The message from bash "no job control + inap. ioctl" you can simply ignore.
many thanks and have a nice day,
Matt Rechenburg
Project Manager openQRM