[ale] XenServer 7.x problem - anyone else using it?

[Beddingfield, Allen]

Yes, a valid subscription.  
To clarify the problem is with the Citrix/XenServer virtualization host - no in the VM.  XenServer creates an LVM logical volume for each VM's disk, and that is what is having the problem.  The output is from the XenServer console.  SLES is just running on the guest that won't power on (because it can't access the storage).
To sum it up, if I power off the VM, the logical volume goes into this state.
--
Allen Beddingfield
Systems Engineer
Office of Information Technology
The University of Alabama
Office 205-348-2251
allen at ua.edu

________________________________________
From: ale-bounces at ale.org [ale-bounces at ale.org] on behalf of Niel Bornstein [nbornstein at gmail.com]
Sent: Friday, August 05, 2016 3:48 PM
To: Atlanta Linux Enthusiasts
Subject: Re: [ale] XenServer 7.x problem - anyone else using it?

So, first (dumb) question: do you have a SLES subscription or is this a
trial?

On 08/05/2016 04:33 PM, Beddingfield, Allen wrote:
> I have a PowerEdge R815 with XenServer 7 installed.  I am using the internal storage for VM storage (just a standalone server).
> I've created a SLES 12 SP1 VM (using the template provided).  Everything goes fine, I can load up the OS, patch it, do whatever with no problems.  However, if I power the VM down, I can't start it back.
> I get "The SR failed to complete the operation".
> If I ssh into the Xen server and run "lvdisplay", it shows the status as "NOT available" - see below:
>
> [root at xentest01 ~]# lvdisplay
>   --- Logical volume ---
>   LV Path                /dev/VG_XenStorage-bebcb0ae-252f-5c52-ca61-9e66b0aa5869/MGT
>   LV Name                MGT
>   VG Name                VG_XenStorage-bebcb0ae-252f-5c52-ca61-9e66b0aa5869
>   LV UUID                Cz6tVV-rCJp-Acu9-zC0T-PEo3-5tT3-2WLzsa
>   LV Write Access        read/write
>   LV Creation host, time xentest01, 2016-08-05 10:22:13 -0500
>   LV Status              available
>   # open                 0
>   LV Size                4.00 MiB
>   Current LE             1
>   Segments               1
>   Allocation             inherit
>   Read ahead sectors     auto
>   - currently set to     256
>   Block device           253:0
>
>   --- Logical volume ---
>   LV Path                /dev/VG_XenStorage-bebcb0ae-252f-5c52-ca61-9e66b0aa5869/VHD-9ebd5bf6-4613-4fc6-9aa0-738496dae1c9
>   LV Name                VHD-9ebd5bf6-4613-4fc6-9aa0-738496dae1c9
>   VG Name                VG_XenStorage-bebcb0ae-252f-5c52-ca61-9e66b0aa5869
>   LV UUID                vOZwtO-vuCF-WM26-hz3P-hghQ-dlsx-k5ZOvZ
>   LV Write Access        read/write
>   LV Creation host, time xentest01, 2016-08-05 14:08:25 -0500
>   LV Status              NOT available
>   LV Size                20.05 GiB
>   Current LE             5132
>   Segments               1
>   Allocation             inherit
>   Read ahead sectors     auto
>
> [root at xentest01 ~]#
>
> When I try to activate it, I get the following:
>
> [root at xentest01 ~]# vgchange -a y
>   Operation prohibited while global/metadata_read_only is set.
>   Operation prohibited while global/metadata_read_only is set.
>   1 logical volume(s) in volume group "VG_XenStorage-bebcb0ae-252f-5c52-ca61-9e66b0aa5869" now active
> [root at xentest01 ~]#
>
> Anyone have any idea what is going on? I've never had this issue with previous XenServer installs, but this is my first with 7.x.  FYI, I can readily reproduce this.  EVERY time I load a server and try this, I get the exact same result.
>
> Thanks.
> Allen B.
>
_______________________________________________
Ale mailing list
Ale at ale.org
http://mail.ale.org/mailman/listinfo/ale
See JOBS, ANNOUNCE and SCHOOLS lists at
http://mail.ale.org/mailman/listinfo