Re: [Xen-users] Xen 4.2 on CentOS 6.4 - domU's became (null) after reboot

[Wei Liu <wei.liu2@xxxxxxxxxx>]

On Mon, Sep 09, 2013 at 02:55:57PM +1100, ÐÐÐÑÑÐ ÐÐÑÑÐÐÐÑ wrote:
> Hello,
> 
> I use centos 6.4 for dom0 and Ubuntu Server 12.04 for my domU's.
> Recently, there
> was a need to restart the few domU's after some updates via "apt-get upgrade".
> I connected to one of the domU's (called "logs01") via command "xl
> vncviewer <domain_id>" and made "reboot". After that, I looked up a list of
> domains and saw logs01 became (null):
> 
> *[root@dom0 ~]# xl list
> Name                                        ID   Mem VCPUs      State
> Time(s)
> Domain-0                                     0  4096    24     r-----
> 48374.8
> (null)                                      12     0     1     --psrd
> 2970.1*
> ...
> ...

This means the domain is being destroyed but there's resource that
cannot be freed.

Your config file looks normal to me. What version of Xen are you using?
If it is Xen4CentOS you can also post to Centos list for help.

Wei.

> 
> The same situation has repeated with one more domU, and I can't destroy it
> with command "xl destroy <domain_id>":
> 
> *[root@dom0 ~]# xl destroy 12
> libxl: error: libxl_dm.c:1245:libxl__destroy_device_model: could not find
> device-model's pid for dom 12
> libxl: error: libxl.c:1414:libxl__destroy_domid:
> libxl__destroy_device_model failed for 12*
> 
> Post logs01.hvm config-file:
> 
> *# =====================================================================
> # Example HVM guest configuration
> # =====================================================================
> #
> # This is a fairly minimal example of what is required for an
> # HVM guest. For a more complete guide see xl.cfg(5)
> 
> # This configures an HVM rather than PV guest
> builder = "hvm"
> 
> # Guest name
> name = "logs01.hvm"
> 
> # 128-bit UUID for the domain as a hexadecimal number.
> # Use "uuidgen" to generate one if required.
> # The default behavior is to generate a new UUID each time the guest is
> started.
> #uuid = "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX"
> 
> # Enable Microsoft Hyper-V compatibile paravirtualisation /
> # enlightenment interfaces. Turning this on can improve Windows guest
> # performance and is therefore recommended
> #viridian = 1
> 
> # Initial memory allocation (MB)
> memory = 512
> 
> # Maximum memory (MB)
> # If this is greater than `memory' then the slack will start ballooned
> # (this assumes guest kernel support for ballooning)
> #maxmem = 512
> 
> # Number of VCPUS
> vcpus = 1
> 
> # Network devices
> # A list of 'vifspec' entries as described in
> # docs/misc/xl-network-configuration.markdown
> vif = [ 'bridge=xenbr40' ]
> 
> # Disk Devices
> # A list of `diskspec' entries as described in
> # docs/misc/xl-disk-configuration.txt
> disk = [
>         '/dev/vg_pcam_0/logs01_root,raw,xvda,rw',
>         '/dev/vg_pcam_0/logs01_swap,raw,xvdb,rw',
>         '/usr/local/distr/ubuntu-12.04.2-server-amd64.iso,,xvdc,cdrom']
> 
> # Guest VGA console configuration, either SDL or VNC
> #sdl = 1
> vnc = 1
> *
> 
> Does anyone know how to fix it? Thanks in advance.

> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxx
> http://lists.xen.org/xen-users


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users