On 23/11/13 16:14, Steven Haigh wrote:
> Hi all,
>
> Running Xen 4.2.3 with all the current XSA fixes.
>
> Whenever I shutdown / reboot a Windows HVM DomU, it ends up
going into a
> (null) state - which I can't seem to kill / destroy / clean
up from.
>
> # xl list
> Name ID Mem
VCPUs State
> Time(s)
> Domain-0 0 1579
2 r-----
> 322927.2
> (null) 1 0
1 --psrd
> 14075.9
> (null) 2 0
1 --psrd
> 58467.6
> (null) 3 0
0 --ps-d
> 11604.8
> (null) 4 0
2 --p--d
> 24186.1
> (null) 5 0
2 --ps-d
> 22831.0
>
> The config is very simple:
> # cat /etc/xen/remotedesktop.vm
> name = "remotedesktop.vm"
> memory = 1536
> vcpus = 2
> cpus = "1-3"
> cpu_weight = 128
> disk = [
'phy:/dev/vg_raid1/remotedesktop.vm,hda,w' ,
> 'file:/root/win7x86.iso,hdc:cdrom,r' ]
> vif = [ 'mac=98:95:00:07:07:07, bridge=br203,
vifname=vm.rdp' ]
> builder = "hvm"
> usbdevice = "tablet"
> vnc = 1
> vnclisten = "10.1.1.1"
> vncdisplay = 1 # port 5901
> vncpasswd = ''
> localtime = 1
> viridian = 1
> xen_platform_pci= 1
>
> It seems that this happens no matter what I do.
>
> Has anyone come across this before?
When you have a system in this state, can you run
xl debug-keys q
xl dmesg > xen-dmesg.log
And provide the log file.
Most likely, there will be one unfreed page keeping the domain
around as a zombie.
~Andrew
|
