Re: [Xen-users] OpenSuSE 10.3 domU install hangs on CentOS 5.6 xen 3.03

[Alexandre Kouznetsov <alk@xxxxxxxxxx>]

Hello.

There are some points that worth checking in your troubleshooting:

El 05/11/12 16:09, Andy Howell escribió:
> boot = "c"
Unless you select the boot media in a interactive way (??), it probably 
should be boot = "d", until your virtual HDD is booteable. I can see 
from your log that the DomU still tries to boot from CDROM. IMHO, it's 
better to define the boot device in a very specific way, instead of 
relaying on some automatic setting.
> vnc = 1
> vncunused = 1
I have noted that when HVM DomU switches video modes, it disconnects the 
VNC session (you watch your DomU console via VNC, isn't it?). From 
spectator's point of view, it looks like a hang. In this case, a quick 
re-connect solves the thing. If your installer plays with Frame Buffer 
(I believe CentOS likes nice pictures), that might be triggering this.
Personally, I prefer to configure the VNC server settings in a more 
specific way:
vfb = [
'type=vnc,keymap=es,vnclisten=0.0.0.0,vncdisplay=11,vncpasswd=XXXXXXXX'
]
This causes VNS server to listen on port 5911. Works in Xen 4.0, not 
sure about 3.0.3. If the VNC client is on the same machine, 127.0.0.1 is 
better than 0.0.0.0.
> disk = [ "file:/virtual3/suse-10_3_root.img,hda,w", ",hdc:cdrom,r" ]
The definition of the CDROM lacks the filename (or block device) 
specification. Are you attaching it to the DomU somehow after boot?
This is an example from a config file I use for HVM boot:
'file:/path/to/image.iso,ioemu:hdc:cdrom,r'

Don't know if double or single quotes make any difference. Probably not. 
I guess, /virtual3/suse-10_3_root.img exists in your filesystem and is 
accessible.
Another thing, is that there is no flag "ioemu", that could be 
necessarily in order to allow your installer's kernel to see the virtual 
CDROM.

--
Alexandre Kouznetsov


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users