On 08/10/11 10:00, William A. Mahaffey III wrote:


.... New to this list & definitely new to virtualization :-/ .... I am trying to setup a 64-bit CentOS 5.6 VM on a 64-bit FC14 server host, all patched up as of a couple of weeks ago. uname -a on the host shows:


[wam@Q6600, CFD, 9:24:23am] 540 % uname -a
Linux Q6600 2.6.35.11-83.fc14.x86_64 #1 SMP Mon Feb 7 07:06:44 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
[wam@Q6600, CFD, 9:52:43am] 541 %


I access the server by ssh on my LAN. I was working on this last Sunday & got stuck, see below. I posted this question to a couple of other lists & had no takers, so here I am here. The server runs in runlevel 3 & has no gfx card onboard, so I am working from the command line. I had a couple of abortive attempts at setup, which got as far as initializing my disk storage for the VM, then the following:



[root@Q6600:/etc, Sun Aug 07, 05:08 PM] 1339 # virt-install   -n CentOS-5.6-64bitVM  -r 2048  --arch=x86_64  --cpu core2duo,disable=vmx  --vcpus=1,maxvcpus=1,sockets=1,cores=2,threads=1  --os-type=linux  --os-variant=rhel5  --disk path=/home/VMs/CentOS.5.6-64bit-VM/disk.img,size=50  --cdrom /home/ISOs/CentOS-5.6/64bit/CentOS-5.6-x86_64-bin-DVD-1of2.iso  --autostart  --prompt
This will overwrite the existing path '/home/VMs/CentOS.5.6-64bit-VM/disk.img'
Do you really want to use this disk (yes or no)
yes

Starting install...
Creating domain...                                                                                     |    0 B     00:00
Gtk-Message: Failed to load module "pk-gtk-module": libpk-gtk-module.so: cannot open shared object file: No such file or directory
Gtk-Message: Failed to load module "canberra-gtk-module": libcanberra-gtk-module.so: cannot open shared object file: No such file or directory

(virt-viewer:20165): Pango-WARNING **: failed to choose a font, expect ugly output. engine-type='PangoRenderFc', script='latin'
Domain installation still in progress. You can reconnect to
the console to complete the installation process.
[root@Q6600:/etc, Sun Aug 07, 05:14 PM] 1339 # virsh --connect qemu:///system
Welcome to virsh, the virtualization interactive terminal.

Type:  'help' for help with commands
       'quit' to quit

virsh # list
 Id Name                 State
----------------------------------
 11 CentOS-5.6-64bitVM   running

virsh # help


The install began OK, right after the 'Pango-WARNING' message, in a separate window, quite readable, started booting & scrolling text past *FAST*, for about 15 sec., then hung, right after a line about 'serial port ....' (I couldn't click-&-drag to capture text from the VM window, going from memory). I let it sit for about 5 min. to be sure it was really hung, then clicked the VM window out, whereupon the message about 'installation still in progress' & the rest appeared. I poked around in virsh a bit as you can see, but couldn't figure anything out. I tried (re)connecting to the console of the VM & that hung, I had to kill the virsh command from another window. I attach syslog output from the proceedings. I am *sure* this is pilot error, but I am stuck for now. Any assistance appreciated :-) ....



_______________________________________________ libvirt-users mailing list libvirt-users@redhat.com https://www.redhat.com/mailman/listinfo/libvirt-users




Update here, I did a full yum upgrade this A.M., & rebooted. On a lark, I decided to retry the VM install and .... it worked. I am logged in there now, trying to get it setup the way I want, & I am stuck on something new. The VM can't see anything on the host machine, let alone the rest of the network. I tried automounting the host's exports, & I can see that a directory is exported, but can't view it. What I really need is to access the install ISO to install more software (gcc & other libraries for compiling code), but I am stuck there for now .... Any assistance appreciated :-) ....


-- 

	William A. Mahaffey III

 ----------------------------------------------------------------------

	"The M1 Garand is without doubt the finest implement of war
	 ever devised by man."
                           -- Gen. George S. Patton Jr.