From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper Subject: Re: HVMs terminating as (null) Date: Sat, 23 Nov 2013 16:18:43 +0000 Message-ID: <5290D563.6010504@citrix.com> References: <5290D480.1000804@crc.id.au> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6179810288634630732==" Return-path: In-Reply-To: <5290D480.1000804@crc.id.au> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Steven Haigh Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org --===============6179810288634630732== Content-Type: multipart/alternative; boundary="------------050802060601010407030506" --------------050802060601010407030506 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit 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 --------------050802060601010407030506 Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit 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

--------------050802060601010407030506-- --===============6179810288634630732== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel --===============6179810288634630732==--