Hi, Vaishali,
Removing read-only-rootfs changes stuff in here:
https://github.com/OpenXT/xenclient-oe/blob/master/classes/openxt-image.bbclass#L31-L52
There may be a difference between /etc/ssh/sshd_config_readonly_argo
and /etc/ssh/sshd_config_argo or the respective ssh key generation.
dom0 /var/log/messages should show something about either sshd-argo
failing to generate keys or start up, or the connection being refused.
Alternatively, you can take a read-only rootfs, and make it read-write
at runtime. You need to change the xenmgr vm configuration to have a
writable "w" disk. Maybe also clear the disk sha1sum and toggle
measured to false - otherwise you may get a measurement failure which
causes the computer to shutdown.
Then you boot the VM and sshargo in. Then you type `rw` and the disk
is remounted read-write. (You can toggle back to read-only with
`ro`.)
You might be able to do the above disk changes and then add "rw" to
the `cmd-line` and have it boot read-write, but I haven't tested that.
Regards,
Jason