Re: [Fedora-xen] libxl driver issue with console/virt-viewer

[Dario Faggioli]

[adding _the correct_ Fedora Xen mailing list to Cc (sorry!)]

On gio, 2013-05-09 at 16:50 -0600, Jim Fehlig wrote:
>  Dario Faggioli wrote:
>  > Hi Jim, everyone,
>  >
>  > I'm having an issue using the libvirt's libxl driver while installing a
>  > Fedora 18 (via netinstall) on both Fedora 18 or rawhide host.
>  >
>  > So, what happens is, basically, that I do not see the output from the
>  > installer at all, neither in the virt-viewer instance that virt-install
>  > does pop-up automatically, nor trying to manually connect to the VM
>  > (either with virt-viewer or VNC). So, when I do:
>  >
>  > [xen@zhaman ~]$ sudo virt-install --paravirt --name f18-i386 --ram
>  > 2048 --vcpus 2 -f /dev/vms/f18_i386 --network bridge=virbr0 --location
>  > http://mirrors.rit.edu/fedora/linux//releases/18/Fedora/i386/os/
>  > Starting install...
>  > Retrieving file .treeinfo...                    | 2.4 kB  00:00:00 !!!
>  > Retrieving file vmlinuz-PAE...                  | 9.3 MB  00:00:33 !!!
>  > Retrieving file initrd-PAE.img...               |  52 MB  00:04:11 !!!
>  > Creating domain...
>  >
>  > And then, in the virt-viewer window, I see a black screen and all it
>  > says is "serial0 console". using `xl console f18-i386' gives me some
> of
>  > the textual output of the installer (but nothing graphical, of course).
>  >   
>  
>  Hmm, do you see things like /local/domain/0/backend/console/-1 in
>  xenstore 
>  
Not really, no:

[xen@zhaman ~]$ sudo xenstore-ls -f| grep console| grep "\-1"

>  instead of /local/domain/0/backend/console/<vm-id>?
>   
Well, as a mater of fact, I _do_
see /local/domain/0/backend/console/<vm-id> stuff:

[xen@zhaman ~]$ sudo xenstore-ls -f| grep console
/local/domain/0/console = ""
/local/domain/0/console/limit = "1048576"
/local/domain/0/console/type = "xenconsoled"
/local/domain/0/backend/console = ""
/local/domain/0/backend/console/1 = ""
/local/domain/0/backend/console/1/0 = ""
/local/domain/0/backend/console/1/0/frontend = "/local/domain/1/console"
/local/domain/0/backend/console/1/0/frontend-id = "1"
/local/domain/0/backend/console/1/0/online = "1"
/local/domain/0/backend/console/1/0/state = "1"
/local/domain/0/backend/console/1/0/domain = "f18"
/local/domain/0/backend/console/1/0/protocol = "vt100"
/local/domain/1/console = ""
/local/domain/1/console/backend = "/local/domain/0/backend/console/1/0"
/local/domain/1/console/backend-id = "0"
/local/domain/1/console/limit = "1048576"
/local/domain/1/console/type = "xenconsoled"
/local/domain/1/console/output = "pty"
/local/domain/1/console/port = "2"
/local/domain/1/console/ring-ref = "1198695"
/local/domain/1/console/tty = "/dev/pts/2"
/local/domain/1/console/vnc-port = "5900"
/local/domain/1/console/vnc-listen = "127.0.0.1"

>  I think you need this patch
>  
>
> http://xenbits.xen.org/gitweb/?p=xen.git;a=commit;h=5420f26507fc5c9853eb1...
>   
Still think that is the problem, even given the above? Also, how come
I'm the only one seeing this?!?! :-/

Thanks and Regards,
Dario

-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)


-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)