5 deleted 3838 characters in body
source | link


EDIT:
Per @RichAlloway's suggestion, I tried moving the iso file to the /tmp directory. This moved the situation forward, but still has not resolved the problem. At the moment, the console is locked up 25 minutes after running the following commands:

[root@remote-host ~]# mv /home/some_other_username/CentOS-7-x86_64-Minimal-1611.iso /tmp/
[root@remote-host ~]# ls -al /tmp
total 696332
drwxrwxrwt.  7 root root      4096 Mar 13 13:48 .
dr-xr-xr-x. 24 root root      4096 Mar 13 12:00 ..
-rw-r--r--.  1 qemu qemu 713031680 Dec  5 15:44 CentOS-7-x86_64-Minimal-1611.iso
drwxrwxrwt.  2 root root         6 Mar 12 11:08 .font-unix
drwxrwxrwt.  2 root root         6 Mar 12 11:08 .ICE-unix
-rwx------.  1 root root       813 Mar 12 11:14 ks-script-dVEOgC
drwxrwxrwt.  2 root root         6 Mar 12 11:08 .Test-unix
drwxrwxrwt.  2 root root         6 Mar 12 11:08 .X11-unix
drwxrwxrwt.  2 root root         6 Mar 12 11:08 .XIM-unix
-rw-------.  1 root root         0 Mar 12 11:03 yum.log
[root@remote-host ~]# virt-install --name centos7 --ram 2048 --disk path=/dev/mapper/centos-third,size=242 --vcpus 1 --os-type generic --os-variant generic --network bridge=virbr0 --graphics none --console pty,target_type=serial --cdrom /tmp/CentOS-7-x86_64-Minimal-1611.iso
WARNING  CDROM media does not print to the text console by default, so you likely will not see text install output. You might want to use --location. See the man page for examples of using --location with CDROM media

Starting install...
Creating domain...                                 |    0 B  00:00:00
Connected to domain centos7
Escape character is ^]

Then, I tried the suggestion from the new error message and opened up a separate Putty session to run the following command to create a different guest virtual machine using --location instead of --cdrom so that console output can be printed, but I am getting the following error:

[root@remote-host ~]# virt-install --name centos7b --ram 2048 --disk path=/dev/mapper/centos-fourth,size=242 --vcpus 1 --os-type generic --os-variant generic --network bridge=virbr0 --graphics none --console pty,target_type=serial --location=/tmp/CentOS-7-x86_64-Minimal-1611.iso
ERROR    'NoneType' object is not iterable


PARTIAL RESOLUTION:

When both of the above Putty sessions timed out, I started a third Putty session, and used virsh to discover that the first guest virtual machine had been successfully created, even though the Putty session had been locked up, as shown above.

[root@remote-host ~]# virsh list --all
 Id    Name                           State
----------------------------------------------------
 5     centos7                        running

[root@remote-host ~]# virsh dominfo centos7
Id:             5
Name:           centos7
UUID:           some-very-long-string
OS Type:        hvm
State:          running
CPU(s):         1
CPU time:       1742.1s
Max memory:     2097152 KiB
Used memory:    2097152 KiB
Persistent:     yes
Autostart:      disable
Managed save:   no
Security model: selinux
Security DOI:   0
Security label: system_u:system_r:svirt_t:s0:c654,c992 (enforcing)

[root@remote-host ~]# virsh vcpuinfo centos7
VCPU:           0
CPU:            2
State:          running
CPU time:       1839.3s
CPU Affinity:   yyyy

[root@remote-host ~]#

To resolve this, how can we change the commands above to provide meaningful feedback about success or failure of the virt-install command without having to wait until the session times out and start a separate session?


EDIT:
Per @RichAlloway's suggestion, I tried moving the iso file to the /tmp directory. This moved the situation forward, but still has not resolved the problem. At the moment, the console is locked up 25 minutes after running the following commands:

[root@remote-host ~]# mv /home/some_other_username/CentOS-7-x86_64-Minimal-1611.iso /tmp/
[root@remote-host ~]# ls -al /tmp
total 696332
drwxrwxrwt.  7 root root      4096 Mar 13 13:48 .
dr-xr-xr-x. 24 root root      4096 Mar 13 12:00 ..
-rw-r--r--.  1 qemu qemu 713031680 Dec  5 15:44 CentOS-7-x86_64-Minimal-1611.iso
drwxrwxrwt.  2 root root         6 Mar 12 11:08 .font-unix
drwxrwxrwt.  2 root root         6 Mar 12 11:08 .ICE-unix
-rwx------.  1 root root       813 Mar 12 11:14 ks-script-dVEOgC
drwxrwxrwt.  2 root root         6 Mar 12 11:08 .Test-unix
drwxrwxrwt.  2 root root         6 Mar 12 11:08 .X11-unix
drwxrwxrwt.  2 root root         6 Mar 12 11:08 .XIM-unix
-rw-------.  1 root root         0 Mar 12 11:03 yum.log
[root@remote-host ~]# virt-install --name centos7 --ram 2048 --disk path=/dev/mapper/centos-third,size=242 --vcpus 1 --os-type generic --os-variant generic --network bridge=virbr0 --graphics none --console pty,target_type=serial --cdrom /tmp/CentOS-7-x86_64-Minimal-1611.iso
WARNING  CDROM media does not print to the text console by default, so you likely will not see text install output. You might want to use --location. See the man page for examples of using --location with CDROM media

Starting install...
Creating domain...                                 |    0 B  00:00:00
Connected to domain centos7
Escape character is ^]

Then, I tried the suggestion from the new error message and opened up a separate Putty session to run the following command to create a different guest virtual machine using --location instead of --cdrom so that console output can be printed, but I am getting the following error:

[root@remote-host ~]# virt-install --name centos7b --ram 2048 --disk path=/dev/mapper/centos-fourth,size=242 --vcpus 1 --os-type generic --os-variant generic --network bridge=virbr0 --graphics none --console pty,target_type=serial --location=/tmp/CentOS-7-x86_64-Minimal-1611.iso
ERROR    'NoneType' object is not iterable


PARTIAL RESOLUTION:

When both of the above Putty sessions timed out, I started a third Putty session, and used virsh to discover that the first guest virtual machine had been successfully created, even though the Putty session had been locked up, as shown above.

[root@remote-host ~]# virsh list --all
 Id    Name                           State
----------------------------------------------------
 5     centos7                        running

[root@remote-host ~]# virsh dominfo centos7
Id:             5
Name:           centos7
UUID:           some-very-long-string
OS Type:        hvm
State:          running
CPU(s):         1
CPU time:       1742.1s
Max memory:     2097152 KiB
Used memory:    2097152 KiB
Persistent:     yes
Autostart:      disable
Managed save:   no
Security model: selinux
Security DOI:   0
Security label: system_u:system_r:svirt_t:s0:c654,c992 (enforcing)

[root@remote-host ~]# virsh vcpuinfo centos7
VCPU:           0
CPU:            2
State:          running
CPU time:       1839.3s
CPU Affinity:   yyyy

[root@remote-host ~]#

To resolve this, how can we change the commands above to provide meaningful feedback about success or failure of the virt-install command without having to wait until the session times out and start a separate session?

4 added 1440 characters in body
source | link


PARTIAL RESOLUTION:

When both of the above Putty sessions timed out, I started a third Putty session, and used virsh to discover that the first guest virtual machine had been successfully created, even though the Putty session had been locked up, as shown above.

[root@remote-host ~]# virsh list --all
 Id    Name                           State
----------------------------------------------------
 5     centos7                        running

[root@remote-host ~]# virsh dominfo centos7
Id:             5
Name:           centos7
UUID:           some-very-long-string
OS Type:        hvm
State:          running
CPU(s):         1
CPU time:       1742.1s
Max memory:     2097152 KiB
Used memory:    2097152 KiB
Persistent:     yes
Autostart:      disable
Managed save:   no
Security model: selinux
Security DOI:   0
Security label: system_u:system_r:svirt_t:s0:c654,c992 (enforcing)

[root@remote-host ~]# virsh vcpuinfo centos7
VCPU:           0
CPU:            2
State:          running
CPU time:       1839.3s
CPU Affinity:   yyyy

[root@remote-host ~]#

What elseTo resolve this, how can I trywe change the commands above to provide meaningful feedback about success or failure of the virt-install command without having to wait until the session times out and start a separate session?

What else can I try?


PARTIAL RESOLUTION:

When both of the above Putty sessions timed out, I started a third Putty session, and used virsh to discover that the first guest virtual machine had been successfully created, even though the Putty session had been locked up, as shown above.

[root@remote-host ~]# virsh list --all
 Id    Name                           State
----------------------------------------------------
 5     centos7                        running

[root@remote-host ~]# virsh dominfo centos7
Id:             5
Name:           centos7
UUID:           some-very-long-string
OS Type:        hvm
State:          running
CPU(s):         1
CPU time:       1742.1s
Max memory:     2097152 KiB
Used memory:    2097152 KiB
Persistent:     yes
Autostart:      disable
Managed save:   no
Security model: selinux
Security DOI:   0
Security label: system_u:system_r:svirt_t:s0:c654,c992 (enforcing)

[root@remote-host ~]# virsh vcpuinfo centos7
VCPU:           0
CPU:            2
State:          running
CPU time:       1839.3s
CPU Affinity:   yyyy

[root@remote-host ~]#

To resolve this, how can we change the commands above to provide meaningful feedback about success or failure of the virt-install command without having to wait until the session times out and start a separate session?

3 added 571 characters in body
source | link


EDIT:
Per @RichAlloway's suggestion, I tried moving the iso file to the /tmp directory. This moved the situation forward, but still has not resolved the problem. At the moment, the console is locked up 1025 minutes after running the following commands:

[root@remote-host ~]# mv /home/some_other_username/CentOS-7-x86_64-Minimal-1611.iso /tmp/
[root@remote-host ~]# ls -al /tmp
total 696332
drwxrwxrwt.  7 root root      4096 Mar 13 13:48 .
dr-xr-xr-x. 24 root root      4096 Mar 13 12:00 ..
-rw-r--r--.  1 qemu qemu 713031680 Dec  5 15:44 CentOS-7-x86_64-Minimal-1611.iso
drwxrwxrwt.  2 root root         6 Mar 12 11:08 .font-unix
drwxrwxrwt.  2 root root         6 Mar 12 11:08 .ICE-unix
-rwx------.  1 root root       813 Mar 12 11:14 ks-script-dVEOgC
drwxrwxrwt.  2 root root         6 Mar 12 11:08 .Test-unix
drwxrwxrwt.  2 root root         6 Mar 12 11:08 .X11-unix
drwxrwxrwt.  2 root root         6 Mar 12 11:08 .XIM-unix
-rw-------.  1 root root         0 Mar 12 11:03 yum.log
[root@remote-host ~]# virt-install --name centos7 --ram 2048 --disk path=/dev/mapper/centos-third,size=242 --vcpus 1 --os-type generic --os-variant generic --network bridge=virbr0 --graphics none --console pty,target_type=serial --cdrom /tmp/CentOS-7-x86_64-Minimal-1611.iso
WARNING  CDROM media does not print to the text console by default, so you likely will not see text install output. You might want to use --location. See the man page for examples of using --location with CDROM media

Starting install...
Creating domain...                                                                |    0 B  00:00:00
Connected to domain centos7
Escape character is ^]

Then, I tried the suggestion from the new error message and opened up a separate Putty session to run the following command to create a different guest virtual machine using --location instead of --cdrom so that console output can be printed, but I am getting the following error:

[root@remote-host ~]# virt-install --name centos7b --ram 2048 --disk path=/dev/mapper/centos-fourth,size=242 --vcpus 1 --os-type generic --os-variant |generic --network bridge=virbr0 --graphics 0none B--console pty,target_type=serial 00:00:00--location=/tmp/CentOS-7-x86_64-Minimal-1611.iso
ConnectedERROR to domain centos7
Escape character'NoneType' object is ^]not iterable


EDIT:
Per @RichAlloway's suggestion, I tried moving the iso file to the /tmp directory. This moved the situation forward, but still has not resolved the problem. At the moment, the console is locked up 10 minutes after running the following commands:

[root@remote-host ~]# mv /home/some_other_username/CentOS-7-x86_64-Minimal-1611.iso /tmp/
[root@remote-host ~]# ls -al /tmp
total 696332
drwxrwxrwt.  7 root root      4096 Mar 13 13:48 .
dr-xr-xr-x. 24 root root      4096 Mar 13 12:00 ..
-rw-r--r--.  1 qemu qemu 713031680 Dec  5 15:44 CentOS-7-x86_64-Minimal-1611.iso
drwxrwxrwt.  2 root root         6 Mar 12 11:08 .font-unix
drwxrwxrwt.  2 root root         6 Mar 12 11:08 .ICE-unix
-rwx------.  1 root root       813 Mar 12 11:14 ks-script-dVEOgC
drwxrwxrwt.  2 root root         6 Mar 12 11:08 .Test-unix
drwxrwxrwt.  2 root root         6 Mar 12 11:08 .X11-unix
drwxrwxrwt.  2 root root         6 Mar 12 11:08 .XIM-unix
-rw-------.  1 root root         0 Mar 12 11:03 yum.log
[root@remote-host ~]# virt-install --name centos7 --ram 2048 --disk path=/dev/mapper/centos-third,size=242 --vcpus 1 --os-type generic --os-variant generic --network bridge=virbr0 --graphics none --console pty,target_type=serial --cdrom /tmp/CentOS-7-x86_64-Minimal-1611.iso
WARNING  CDROM media does not print to the text console by default, so you likely will not see text install output. You might want to use --location. See the man page for examples of using --location with CDROM media

Starting install...
Creating domain...                                                                                           |    0 B  00:00:00
Connected to domain centos7
Escape character is ^]


EDIT:
Per @RichAlloway's suggestion, I tried moving the iso file to the /tmp directory. This moved the situation forward, but still has not resolved the problem. At the moment, the console is locked up 25 minutes after running the following commands:

[root@remote-host ~]# mv /home/some_other_username/CentOS-7-x86_64-Minimal-1611.iso /tmp/
[root@remote-host ~]# ls -al /tmp
total 696332
drwxrwxrwt.  7 root root      4096 Mar 13 13:48 .
dr-xr-xr-x. 24 root root      4096 Mar 13 12:00 ..
-rw-r--r--.  1 qemu qemu 713031680 Dec  5 15:44 CentOS-7-x86_64-Minimal-1611.iso
drwxrwxrwt.  2 root root         6 Mar 12 11:08 .font-unix
drwxrwxrwt.  2 root root         6 Mar 12 11:08 .ICE-unix
-rwx------.  1 root root       813 Mar 12 11:14 ks-script-dVEOgC
drwxrwxrwt.  2 root root         6 Mar 12 11:08 .Test-unix
drwxrwxrwt.  2 root root         6 Mar 12 11:08 .X11-unix
drwxrwxrwt.  2 root root         6 Mar 12 11:08 .XIM-unix
-rw-------.  1 root root         0 Mar 12 11:03 yum.log
[root@remote-host ~]# virt-install --name centos7 --ram 2048 --disk path=/dev/mapper/centos-third,size=242 --vcpus 1 --os-type generic --os-variant generic --network bridge=virbr0 --graphics none --console pty,target_type=serial --cdrom /tmp/CentOS-7-x86_64-Minimal-1611.iso
WARNING  CDROM media does not print to the text console by default, so you likely will not see text install output. You might want to use --location. See the man page for examples of using --location with CDROM media

Starting install...
Creating domain...                                 |    0 B  00:00:00
Connected to domain centos7
Escape character is ^]

Then, I tried the suggestion from the new error message and opened up a separate Putty session to run the following command to create a different guest virtual machine using --location instead of --cdrom so that console output can be printed, but I am getting the following error:

[root@remote-host ~]# virt-install --name centos7b --ram 2048 --disk path=/dev/mapper/centos-fourth,size=242 --vcpus 1 --os-type generic --os-variant generic --network bridge=virbr0 --graphics none --console pty,target_type=serial --location=/tmp/CentOS-7-x86_64-Minimal-1611.iso
ERROR    'NoneType' object is not iterable
2 added 1833 characters in body
source | link
1
source | link