XenServer Local SR: Need another pair of eyes

[travisdh1]

@Kelly Well, bother.

xe sr-create host-uuid=uuidofhost shared=false type=lvm content-type=user device-config:device=/dev/sda1 name-label="blah"

Should work. You've stumped me for the day at least.

[momurda]

Thats weird. pvdisplay/vgdisplay should give you a list of physical devices (pvdisplay) and vgdisplay should show you the logical volumes of your physical disks.

[Kelly]

@travisdh1 said in XenServer Local SR: Need another pair of eyes:

@Kelly Well, bother.

xe sr-create host-uuid=uuidofhost shared=false type=lvm content-type=user device-config:device=/dev/sda1 name-label="blah"

Should work. You've stumped me for the day at least.

Does the order of the elements after sr-create matter?

[travisdh1]

@Kelly said in XenServer Local SR: Need another pair of eyes:

@travisdh1 said in XenServer Local SR: Need another pair of eyes:

@Kelly Well, bother.

xe sr-create host-uuid=uuidofhost shared=false type=lvm content-type=user device-config:device=/dev/sda1 name-label="blah"

Should work. You've stumped me for the day at least.

Does the order of the elements after sr-create matter?

It shouldn't, but xe can be a bit of an oddball at times. Could be as simple as a space where one shouldn't be.

[Kelly]

Ok, so I decided to step through xe sr-create until it stopped complaining. It created the SR with just this:

xe sr-create name-label="VM Storage" type=lvm host-uuid=uuid device-config:device=/dev/sda

I only entered a parameter when it specifically asked for it. I'm wondering if there is an undocumented change in one of the parameters.

[Kelly]

And the same command worked on the second host in the pool as well (different uuid).

[momurda]

curious what the output of 'xe sr-list' shows for content-type on your new SRs since you didnt specify when creating.

[Kelly]

@momurda said in XenServer Local SR: Need another pair of eyes:

curious what the output of 'xe sr-list' shows for content-type on your new SRs since you didnt specify when creating.

Hmm...

content-type ( RO):

[momurda]

Hmm indeed. can you use the new SRs? Boot a vm on them, add a disk from one to an existing vm?

[Kelly]

@momurda said in XenServer Local SR: Need another pair of eyes:

Hmm indeed. can you use the new SRs? Boot a vm on them, add a disk from one to an existing vm?

The pbd was marked as read-only. I'm going to try adding in content-type to my above command.

[momurda]

I am not clear about this, but i think the results of xe sr-list

the RO/RW parts refer to the parameters themselves, not necessarily the SR.
For instance, you cant change uuid of an sr so it is RO.
You can change the name-label, name-description parameters, so they are RW

[Kelly]

@momurda said in XenServer Local SR: Need another pair of eyes:

I am not clear about this, but i think the results of xe sr-list

the RO/RW parts refer to the parameters themselves, not necessarily the SR.
For instance, you cant change uuid of an sr so it is RO.
You can change the name-label, name-description parameters, so they are RW

Hmm, perhaps it wasn't read only, but I couldn't install to it. I removed the SR and PBD and then redid it with the content-type defined and I'm now able to install to it.

Final command:

xe sr-create name-label="VM Storage" type=lvm content-type=user host-uuid=uuid device-config:device=/dev/sda

[momurda]

Nice. Also Ive only been using XS for a few months, so i could be wrong about the xe sr-list command output

[travisdh1]

@Kelly It doesn't help that most of us have to use the xe sr-create command once every 4-5 years.