Christophe Baegert
2013-Jun-13 14:56 UTC
Dom0 crashes when Linux DomU started with WIN 2008 R2 DomU already up
Hi,
I installed several Linux guests on a Xen 4.1 (4.1.4-3+deb7u1 exacty)
with XL toolstack, on Debian Wheezy, on a 2x8 cores Opteron server
(mainboard Supermicro H8DGU-F with latest Bios 3.0b).
It worked fine with these guests for several weeks. Then I tried to
install a Windows 2008 R2 Standard SP1 guest with HVM. The install
begins fine, it copies the files, then reboots, then finishes the
installation, then reboots again, and then, instead of the normal setup
interface, it hangs for a last 10 minutes, with no VNC output, no Xen
state reported, after that it displays indefinitely an horizontal moving
ray of light (see http://pixoa.net/win2008.jpg).
If I try to launch the other Linux DomU at this moment, after 3 or 5
seconds, the physical server reboots, without any information.
Even with safe mode, my Win guest can''t finish the boot. It stops after
loading drivers.
I don''t know if there are 2 problems (windows hang + physical reboot),
or if the reason of these 2 problems is common.
I already try to disable C1E in the BIOS. My clocksource is "xen". I
see
NOTHING in the logs, nor when Windows hang, nor when the Dom0 reboots of
course. I already worked for 2 full days on this problem, but now I''m
stuck.
Any idea ?
Regards,
Christophe
------------------------------------------------
This is my windows DomU.cfg :
kernel = "/usr/lib/xen-4.1/boot/hvmloader"
builder=''hvm''
shadow_memory = 8
name = "rp61"
acpi = 1
apic = 1
device_model = ''/usr/lib/xen-4.1/bin/qemu-dm''
boot="c"
sdl=0
vnc=1
vncdisplay=1
vncconsole=1
vncviewer=0
vnclisten=''Dom0 IP''
usbdevice=''tablet''
vcpus = ''2''
memory = ''4096''
disk = [
''phy:/dev/etherd/e6.1,ioemu:hda,w'',
''file:/home/myuser/win2008.iso,ioemu:hdb:cdrom,r''
]
vif = [
''type=ioemu,vifname=vif0.rp61,ip=DOMU2_PUBLICIP,mac=00:16:3E:E4:BD:06,bridge=xenbr0'',''type=ioemu,vifname=vif1.rp61,ip=DOMU2_PRIVATEIP
,mac=00:16:3E:E4:B0:06,bridge=xenbr8'', ]
on_poweroff = ''destroy''
on_reboot = ''destroy''
on_crash = ''restart''
------------------------------------------------------
This is my Linux DomU .cfg (which works well)
kernel = ''/boot/vmlinuz-3.2.0-4-amd64''
ramdisk = ''/boot/initrd.img-3.2.0-4-amd64''
vcpus = ''2''
maxvcpus = ''8''
memory = ''16384''
maxmem = ''32768''
root = ''/dev/xvda2 ro''
disk = [
''phy:/dev/etherd/e4.1,xvda2,w'',
''phy:/dev/etherd/e4.2,xvda1,w'',
''phy:/dev/etherd/e4.3,xvda3,w'',
''phy:/dev/mapper/mirrorssd1-postgres1--postgres,xvdb1,w'',
]
name = ''postgres1''
vif = [ ''vifname=vif0.postgres1,ip=DOMU1_PUBLICIP
,mac=00:16:3E:E4:BD:04,bridge=xenbr0'',''vifname=vif1.postgres1,ip=DOMU1_PRIVATEIP,mac=00:16:3E:E4:B0:04,bridge=xenbr8'',
]
on_poweroff = ''destroy''
on_reboot = ''restart''
on_crash = ''restart''
------------------------------------------------------
My xend-config.sxp
(vif-script vif-bridge)
(dom0-min-mem 196)
(enable-dom0-ballooning yes)
(total_available_memory 0)
(dom0-cpus 0)
(vnc-listen ''DOM0_PUBLICIP'')
--------------------------------------------------------------
xen-hotplug.log :
RTNETLINK answers: Operation not supported
RTNETLINK answers: Operation not supported
RTNETLINK answers: Operation not supported
RTNETLINK answers: Operation not supported
RTNETLINK answers: Operation not supported
RTNETLINK answers: Operation not supported
RTNETLINK answers: Operation not supported
RTNETLINK answers: Operation not supported
RTNETLINK answers: Operation not supported
---------------------------------------------------------------------
xl-rp61.log (line displayed at the VM boot)
Waiting for domain rp61 (domid 2) to die [pid 3973]
---------------------------------------------------------------------
/var/log/xen/qemu-dm-rp61.log
domid: 2
-videoram option does not work with cirrus vga device model. Videoram
set to 4M.
Using file /dev/etherd/e6.1 in read-write mode
Strip off blktap sub-type prefix to /home/chris/win2008.iso (drv
''aio'')
Using file /home/myuser/win2008.iso in read-only mode
Watching /local/domain/0/device-model/2/logdirty/cmd
Watching /local/domain/0/device-model/2/command
Watching /local/domain/2/cpu
char device redirected to /dev/pts/2
qemu_map_cache_init nr_buckets = 10000 size 4194304
shared page at pfn feffd
buffered io page at pfn feffb
Guest uuid = 0d87a931-67ad-461d-ace4-2656a86b1607
populating video RAM at ff000000
mapping video RAM from ff000000
Register xen platform.
Done register platform.
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw
state.
xs_read(/local/domain/0/device-model/2/xen_extended_power_mgmt): read error
xs_read(): vncpasswd get error.
/vm/0d87a931-67ad-461d-ace4-2656a86b1607/vncpasswd.
medium change watch on `hdb'' (index: 1): aio:/home/myuser/win2008.iso
Log-dirty: no command yet.
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
vcpu-set: watch node error.
xs_read(/local/domain/2/log-throttling): read error
qemu: ignoring not-understood drive `/local/domain/2/log-throttling''
medium change watch on `/local/domain/2/log-throttling'' - unknown
device, ignored
I/O request not ready: 0, ptr: 0, port: e9, data: 20, count: 1, size: 1
cirrus vga map change while on lfb mode
mapping vram to f0000000 - f0400000
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw
state.
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro
state.
Time offset set 3600, added offset 3600 <------- APPEARS ONLY ONE
TIME, EVEN IF I GET SEVERAL HANGS AND SEVERAL REBOOTS
Roger Pau Monné
2013-Jun-13 15:55 UTC
Re: Dom0 crashes when Linux DomU started with WIN 2008 R2 DomU already up
On 13/06/13 16:56, Christophe Baegert wrote:> Hi, > > I installed several Linux guests on a Xen 4.1 (4.1.4-3+deb7u1 exacty) > with XL toolstack, on Debian Wheezy, on a 2x8 cores Opteron server > (mainboard Supermicro H8DGU-F with latest Bios 3.0b). > > It worked fine with these guests for several weeks. Then I tried to > install a Windows 2008 R2 Standard SP1 guest with HVM. The install > begins fine, it copies the files, then reboots, then finishes the > installation, then reboots again, and then, instead of the normal setup > interface, it hangs for a last 10 minutes, with no VNC output, no Xen > state reported, after that it displays indefinitely an horizontal moving > ray of light (see http://pixoa.net/win2008.jpg). > > If I try to launch the other Linux DomU at this moment, after 3 or 5 > seconds, the physical server reboots, without any information. > > Even with safe mode, my Win guest can''t finish the boot. It stops after > loading drivers. > > I don''t know if there are 2 problems (windows hang + physical reboot), > or if the reason of these 2 problems is common. > > I already try to disable C1E in the BIOS. My clocksource is "xen". I see > NOTHING in the logs, nor when Windows hang, nor when the Dom0 reboots of > course. I already worked for 2 full days on this problem, but now I''m stuck. > > Any idea ?Hello, I guess you already have a serial cable connected to the server, and you see no output there before the reboot? Could you try to install latest Xen from the unstable repository? http://xenbits.xen.org/gitweb/?p=xen.git;a=summary Or at least recompile your version of Xen with debugging enabled? (I guess the version shipped on Debian doesn''t come with debugging enabled). Also add "noreboot=true" to the Xen boot parameters, so the hypervisor doesn''t automatically reboot.