Xen users - Nov 2012 - OpenSuSE 10.3 domU install hangs on CentOS 5.6 xen 3.03

I''m trying to install OpenSuSE 10.3 as a domU on a CentOS 5.6 system
running xen 3.0.3.

It starts to load and then hangs:

ata0 master: QEMU HARDDISK ATA-7 Hard-Disk (20480 MBytes)
ata0  slave: Unknown device
ata1 master: QEMU CD-ROM ATAPI-4 CD-Rom/DVD-Rom
ata1  slave: Unknown device

Booting from CD-Rom...
ISOLINUX 3.31 0x46f43c1e  Copyright (C) 1994-2005 H. Peter Anvin
Loading...


In /var/log/xen/qemu-dm.14238.log I see:

domid: 25
qemu: the number of cpus is 2
Using file  in read-write mode
Using file  in read-only mode
Watching /local/domain/25/logdirty/next-active
Watching /local/domain/0/device-model/25/command
xs_read(): vncpasswd get error.
/vm/5a3cc077-477c-062d-26dd-85cba747ebbc/vncpasswd.
char device redirected to /dev/pts/3
qemu_map_cache_init nr_buckets = 10000
shared page at pfn 3ffff
buffered io page at pfn 3fffd
xs_read(/vm/5a3cc077-477c-062d-26dd-85cba747ebbc/rtc/timeoffset): read error
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
Triggered log-dirty buffer switch

There are no errors that I can see in the /var/log/xen/xend.log

Any ideas on how to debug this further?

Thanks,

	Andy

Hello.

El 05/11/12 15:28, Andy Howell escribió:
> I''m trying to install OpenSuSE 10.3 as a domU on a CentOS 5.6
system
> running xen 3.0.3.
>
> It starts to load and then hangs:
>
> ata0 master: QEMU HARDDISK ATA-7 Hard-Disk (20480 MBytes)
> ata0  slave: Unknown device
> ata1 master: QEMU CD-ROM ATAPI-4 CD-Rom/DVD-Rom
> ata1  slave: Unknown device
Can you please post your DomU''s config and describe the storage you are
using (file, LVM, etc.)?
Maybe there is something defined in a wrong way.

-- 
Alexandre Kouznetsov

On 11/05/2012 03:38 PM, Alexandre Kouznetsov wrote:
> Hello.
>
> El 05/11/12 15:28, Andy Howell escribió:
>> I''m trying to install OpenSuSE 10.3 as a domU on a CentOS 5.6
system
>> running xen 3.0.3.
>>
>> It starts to load and then hangs:
>>
>> ata0 master: QEMU HARDDISK ATA-7 Hard-Disk (20480 MBytes)
>> ata0  slave: Unknown device
>> ata1 master: QEMU CD-ROM ATAPI-4 CD-Rom/DVD-Rom
>> ata1  slave: Unknown device
>
> Can you please post your DomU''s config and describe the storage
you are using (file, LVM,
> etc.)?
> Maybe there is something defined in a wrong way.
>
Alexandre,

	The configuration was made with the Virtual Machine Manager via libvirt.
I''m using an iso
image as the install media. The storage is file based. Here is the configuration
from
/etc/xen/suse10-3

name = "suse10-3"
uuid = "5a3cc077-477c-062d-26dd-85cba747ebbc"
maxmem = 1024
memory = 1024
vcpus = 2
builder = "hvm"
kernel = "/usr/lib/xen/boot/hvmloader"
boot = "c"
pae = 1
acpi = 1
apic = 1
localtime = 0
on_poweroff = "destroy"
on_reboot = "restart"
on_crash = "restart"
device_model = "/usr/lib64/xen/bin/qemu-dm"
sdl = 0
vnc = 1
vncunused = 1
keymap = "en-us"
disk = [ "file:/virtual3/suse-10_3_root.img,hda,w",
",hdc:cdrom,r" ]
vif = [ "mac=00:16:3e:cf:b7:d4,bridge=virbr0,script=vif-bridge" ]
parallel = "none"
serial = "pty"

Thanks,

	Andy

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