Login
[x]
Log in using an account from:
Fedora Account System
Red Hat Associate
Red Hat Customer
Or login using a Red Hat Bugzilla account
Forgot Password
Login:
Hide Forgot
Create an Account
Red Hat Bugzilla – Attachment 889324 Details for
Bug 1091011
Console session doesn't opens to VM over Spice, during HE installation process.
[?]
New
Simple Search
Advanced Search
My Links
Browse
Requests
Reports
Current State
Search
Tabular reports
Graphical reports
Duplicates
Other Reports
User Changes
Plotly Reports
Bug Status
Bug Severity
Non-Defaults
|
Product Dashboard
Help
Page Help!
Bug Writing Guidelines
What's new
Browser Support Policy
5.0.4.rh83 Release notes
FAQ
Guides index
User guide
Web Services
Contact
Legal
This site requires JavaScript to be enabled to function correctly, please enable it.
HE configuration that was done during HE deploy.
HE config (text/plain), 18.34 KB, created by
Nikolai Sednev
on 2014-04-24 15:21:40 UTC
(
hide
)
Description:
HE configuration that was done during HE deploy.
Filename:
MIME Type:
Creator:
Nikolai Sednev
Created:
2014-04-24 15:21:40 UTC
Size:
18.34 KB
patch
obsolete
>[root@master-vds10 ~]# hosted-engine --deploy >[ INFO ] Stage: Initializing > Continuing will configure this host for serving as hypervisor and create a VM where you have to install oVirt Engine afterwards. > Are you sure you want to continue? (Yes, No)[Yes]: yes > It has been detected that this program is executed through an SSH connection without using screen. > Continuing with the installation may lead to broken installation if the network connection fails. > It is highly recommended to abort the installation and run it inside a screen session using command "screen". > Do you want to continue anyway? (Yes, No)[No]: yes >[ INFO ] Generating a temporary VNC password. >[ INFO ] Stage: Environment setup > Configuration files: [] > Log file: /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20140424163254.log > Version: otopi-1.2.0 (otopi-1.2.0-1.el6ev) >[ INFO ] Hardware supports virtualization >[ INFO ] Bridge rhevm already created >[ INFO ] Stage: Environment packages setup >[ INFO ] Stage: Programs detection >[ INFO ] Stage: Environment setup >[ INFO ] Waiting for VDSM hardware info >[ INFO ] Waiting for VDSM hardware info >[ INFO ] Waiting for VDSM hardware info >[ INFO ] Stage: Environment customization > > --== STORAGE CONFIGURATION ==-- > > During customization use CTRL-D to abort. > Please specify the storage you would like to use (nfs3, nfs4)[nfs3]: nfs3 > Please specify the full shared storage connection path to use (example: host:/path): 10.35.160.108:/RHEV/nsednev > The specified storage location already contains a data domain. Is this an additional host setup (Yes, No)[Yes]? no >[ INFO ] Installing on first host > > --== SYSTEM CONFIGURATION ==-- > > > --== NETWORK CONFIGURATION ==-- > > iptables was detected on your computer, do you wish setup to configure it? (Yes, No)[Yes]: > Please indicate a pingable gateway IP address [10.35.64.254]: > > --== VM CONFIGURATION ==-- > > Please specify the device to boot the VM from (cdrom, disk, pxe) [cdrom]: pxe > The following CPU types are supported by this host: > - model_Westmere: Intel Westmere Family > - model_Nehalem: Intel Nehalem Family > - model_Penryn: Intel Penryn Family > - model_Conroe: Intel Conroe Family > Please specify the CPU type to be used by the VM [model_Westmere]: model_Penryn > Please specify the number of virtual CPUs for the VM [Defaults to minimum requirement: 2]: > Please specify the disk size of the VM in GB [Defaults to minimum requirement: 25]: > You may specify a MAC address for the VM or accept a randomly generated default [00:16:3e:60:c0:38]: > Please specify the memory size of the VM in MB [Defaults to minimum requirement: 4096]: > Please specify the console type you would like to use to connect to the VM (vnc, spice) [vnc]: spice > > --== HOSTED ENGINE CONFIGURATION ==-- > > Enter the name which will be used to identify this host inside the Administrator Portal [hosted_engine_1]: > Enter 'admin@internal' user password that will be used for accessing the Administrator Portal: > Confirm 'admin@internal' user password: > Please provide the FQDN for the engine you would like to use. > This needs to match the FQDN that you will use for the engine installation within the VM. > Note: This will be the FQDN of the VM you are now going to create, > it should not point to the base host or to any other existing machine. > Engine FQDN: hosted_engine.qa.lab.tlv.redhat.com >[WARNING] Failed to resolve hosted_engine.qa.lab.tlv.redhat.com using DNS, it can be resolved only locally > Please provide the name of the SMTP server through which we will send notifications [localhost]: > Please provide the TCP port number of the SMTP server [25]: > Please provide the email address from which notifications will be sent [root@localhost]: > Please provide a comma-separated list of email addresses which will get notifications [root@localhost]: >[ INFO ] Stage: Setup validation > > --== CONFIGURATION PREVIEW ==-- > > Engine FQDN : hosted_engine.qa.lab.tlv.redhat.com > Bridge name : rhevm > SSH daemon port : 22 > Firewall manager : iptables > Gateway address : 10.35.64.254 > Host name for web application : hosted_engine_1 > Host ID : 1 > Image size GB : 25 > Storage connection : 10.35.160.108:/RHEV/nsednev > Console type : qxl > Memory size MB : 4096 > MAC address : 00:16:3e:60:c0:38 > Boot type : pxe > Number of CPUs : 2 > CPU Type : model_Penryn > > Please confirm installation settings (Yes, No)[No]: yes >[ INFO ] Generating answer file '/etc/ovirt-hosted-engine/answers.conf' >[ INFO ] Stage: Transaction setup >[ INFO ] Stage: Misc configuration >[ INFO ] Stage: Package installation >[ INFO ] Stage: Misc configuration >[ INFO ] Configuring libvirt >[ INFO ] Configuring VDSM >[ INFO ] Starting vdsmd >[ INFO ] Waiting for VDSM hardware info >[ INFO ] Waiting for VDSM hardware info >[ INFO ] Waiting for VDSM hardware info >[ INFO ] Connecting Storage Domain >[ INFO ] Connecting Storage Pool >[ INFO ] Verifying sanlock lockspace initialization >[ INFO ] sanlock lockspace already initialized >[ INFO ] sanlock metadata already initialized >[ INFO ] Creating VM Image >[ INFO ] Disconnecting Storage Pool >[ INFO ] Start monitoring domain >[ INFO ] Configuring VM >[ INFO ] Updating hosted-engine configuration >[ INFO ] Stage: Transaction commit >[ INFO ] Stage: Closing up >[ INFO ] Creating VM > You can now connect to the VM with the following command: > /usr/bin/remote-viewer --spice-ca-file=/etc/pki/vdsm/libvirt-spice/ca-cert.pem spice://localhost?tls-port=5901 --spice-host-subject="O=qa.lab.tlv.redhat.com, CN=10.35.64.85" > Use temporary password "0971htCx" to connect to spice console. > Please note that in order to use remote-viewer you need to be able to run graphical applications. > This means that if you are using ssh you have to supply the -Y flag (enables trusted X11 forwarding). > Otherwise you can run the command from a terminal in your preferred desktop environment. > If you cannot run graphical applications you can connect to the graphic console from another host or connect to the console using the following command: > virsh -c qemu+tls://10.35.64.85/system console HostedEngine > If you need to reboot the VM you will need to start it manually using the command: > hosted-engine --vm-start > You can then set a temporary password using the command: > hosted-engine --add-console-password > The VM has been started. Install the OS and shut down or reboot it. To continue please make a selection: > > (1) Continue setup - VM installation is complete > (2) Reboot the VM and restart installation > (3) Abort setup > > (1, 2, 3)[1]:
<b>You cannot view the attachment while viewing its details because your browser does not support IFRAMEs. <a href="attachment.cgi?id=889324">View the attachment on a separate page</a>.</b>
View Attachment As Raw
Actions:
View
Attachments on
bug 1091011
: 889324