Lech Karol Pawłaszek
2007-Oct-19 12:11 UTC
[Xen-users] Intel''s fault? HVM domUs freezes at boot time.
Hello,
I''ve encountered a very weird problem. Some isos (Linux installers)
freeze HVM dom0 and it is not possible to continue installation.
dom0 runs on Debian unstable (it ran Debian Etch, but there was Xen
3.0.3 and I was sugested to upgrade to Xen 3.1 which is in unstable) and
I have sucesfully created a few paravirtualized domU domains. I even
sucesfully created HVM domain using debian netinstaller and I am able to
boot it and use it. However recently I was told to install Fedora7 in
fully virtualized environment and I failed. I''ve tried for two days and
this is what I''ve found:
It freezes at random manner. I''ve made a few snapshots which clearly
show that sometimes i can see a line or two before it freezes
completly[1]. The first two snapshots are taken when I was trying to
boot R.I.P. liveCD distribution. The third one shows that debian-netiso
works flawlessy - I am able to type boot commands and perform whole
installation.
[1] - http://kni.univ.szczecin.pl/~ike/xen
After some search I''ve found that others have similar problems[2][3].
[2] -
http://lists.xensource.com/archives/html/xen-users/2007-01/msg01340.html
[3] -
http://lists.xensource.com/archives/html/xen-users/2007-09/msg00443.html
There is info, that it''s "intel''s fault" since intel
doesn''t support
real mode. Pitty since the most (my) servers have Intel chips. But maybe
there is some patch or workaround to create and use HVM on intels?
poligon:~# xm info
host : poligon
release : 2.6.18-4-xen-amd64
version : #1 SMP Fri May 4 02:40:51 UTC 2007
machine : x86_64
nr_cpus : 4
nr_nodes : 1
sockets_per_node : 2
cores_per_socket : 2
threads_per_core : 1
cpu_mhz : 1600
hw_caps :
bfebfbff:20100800:00000000:00000140:0004e33d:00000000:00000001
total_memory : 4094
free_memory : 1
xen_major : 3
xen_minor : 1
xen_extra : -1
xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler : credit
xen_pagesize : 4096
platform_params : virt_start=0xffff800000000000
xen_changeset : unavailable
cc_compiler : gcc version 4.1.3 20070812 (prerelease) (Debian
4.1.2-15)
cc_compile_by : waldi
cc_compile_domain : debian.org
cc_compile_date : Fri Aug 31 08:20:38 UTC 2007
xend_config_format : 4
poligon:~# cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Xeon(R) CPU 5110 @ 1.60GHz
stepping : 6
cpu MHz : 1600.088
cache size : 4096 KB
physical id : 0
siblings : 1
core id : 0
cpu cores : 1
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu tsc msr pae mce cx8 apic mtrr mca cmov pat pse36
clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm constant_tsc
pni monitor ds_cpl vmx tm2 cx16 xtpr lahf_lm
bogomips : 4002.29
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
[...]
poligon:~# cat /etc/xen/hvm.cfg
import os, re
arch = os.uname()[4]
if re.search(''64'', arch):
arch_libdir = ''lib64''
else:
arch_libdir = ''lib''
kernel = ''/usr/lib/xen-default/boot/hvmloader''
builder = ''hvm''
device_model = ''/usr/'' + arch_libdir +
''/xen-default/bin/qemu-dm''
memory = ''512''
disk = [ ''file:/home/xen/domains/ldap-hvm/disk.img,hda,w'',
''file:/home/admin/kamyk/FC-6-i386-disc1.iso,hdb:cdrom,r'' ]
boot = ''d''
vnc = 1
name = ''hvm''
on_poweroff = ''destroy''
on_reboot = ''restart''
on_crash = ''restart''
/var/log/qemu-dm.*.log
domid: 7
qemu: the number of cpus is 1
Watching /local/domain/7/logdirty/next-active
qemu_map_cache_init nr_buckets = 10000
shared page at pfn 1ffff
buffered io page at pfn 1fffd
Time offset set 0
xs_read(): vncpasswd get error.
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
Triggered log-dirty buffer switch
Kind regards,
PS: maybe should i sent it to xen-devel mailing list?
--
Lech Karol Pawłaszek <ike>
"You will never see me fall from grace" [KoRn]
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Stephan Seitz
2007-Oct-19 20:13 UTC
Re: [Xen-users] Intel''s fault? HVM domUs freezes at boot time.
Lech Karol Pawłaszek schrieb:> I''ve encountered a very weird problem. Some isos (Linux installers) > freeze HVM dom0 and it is not possible to continue installation.> There is info, that it''s "intel''s fault" since intel doesn''t support > real mode. Pitty since the most (my) servers have Intel chips. But maybe > there is some patch or workaround to create and use HVM on intels?Hi, if you don''t need a 64bit Xen (or even it''s ability to run 64 and 32p guests concurrently) i would prefer the 32bit-pae xen. I assume the 64bit version has recently become more stable, but in the days of 3.0.3 and early 3.1 64bit it was somewhat painful to use ;) I don''t know your future plans at that machine, but you''ve currently 4G mem installed. With 32bit-pae hypervisor you''ll be able to use up to 16G. We''re using 32bit-pae on every xen-box (mixed processors but about 80% intel), the only problems where a domU segfaults dom0 encountered on setups with a 3.1 hypervisor and a 3.0.3 xenified dom0 kernels. Greetings Stephan> poligon:~# xm info > host : poligon > release : 2.6.18-4-xen-amd64 > version : #1 SMP Fri May 4 02:40:51 UTC 2007 > machine : x86_64> total_memory : 4094> xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 > hvm-3.0-x86_32p hvm-3.0-x86_64_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Lech Karol Pawłaszek
2007-Oct-24 08:00 UTC
Re: [Xen-users] Intel''s fault? HVM domUs freezes at boot time.
Stephan Seitz pisze: [...]> Hi, > if you don''t need a 64bit Xen (or even it''s ability to run 64 and 32p guests > concurrently) i would prefer the 32bit-pae xen. I assume the 64bit version has > recently become more stable, but in the days of 3.0.3 and early 3.1 64bit it was > somewhat painful to use ;) > I don''t know your future plans at that machine, but you''ve currently 4G mem > installed. With 32bit-pae hypervisor you''ll be able to use up to 16G. > We''re using 32bit-pae on every xen-box (mixed processors but about 80% intel), > the only problems where a domU segfaults dom0 encountered on setups with a 3.1 hypervisor > and a 3.0.3 xenified dom0 kernels.[...] Hello again. Problem has been "solved". I was about to reinstall this system and use 32bit instead of 64bit just to test if it is going to work, but I''ve found that there is Xen 3.1.1 in Debian unstable branch. After installation of Xen 3.1.1 it works (at this moment) flawlessy. Thanks for help Stephan. Kind regards, -- Lech Karol Pawłaszek <ike> "You will never see me fall from grace" [KoRn] _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users