Solved Get Large Disk Images on XenServer 6.5 on Local Filesystem?
-
I wonder how the conversion would go for EXT3 to QCOW, along with the VM conversion.....
-
Right, doesn't have to be VHDX, just anything that supports larger than 2TB.
-
@scottalanmiller said in Get Large Disk Images on XenServer 6.5 on Local Filesystem?:
Is there a simple way to make a QCOW based file that XS will use?
Only stuff I can find is converting from qcow2 to VHD or the other way around.
I found a good utility to convert from
.xvato.img, then just used qemu to convert the.imgto.qcow2. Sadly that doesn't help us here haha. -
Is there a limit to how many 2TB VDs you can span?
-
@BRRABill 16 in XS.
-
@DustinB3403 said
@BRRABill 16 in XS.
That answer confuses me.
Do you mean you can only have 16 VDs for a VM in XS?
-
@ntoxicator said in Get Large Disk Images on XenServer 6.5 on Local Filesystem?:
Still no reason for folks to run ProxMox in Business environment? I know I got hit over the head before making this mention
I can't imagine any reason for it. It's got a few basic issues that will never go away...
- It's an endemically evil company that you don't want to associate with
- The core idea is bad - mashing two different virtualization solutions together on one box
- They just make the GUI, not the products, so they themselves likely know nothing special about it
- It's non-standard so getting assistance or support is hard
- It has no real benefits to offset the negatives.
-
You can have 16 vDisk per VM in XS.
Yes
-
@DustinB3403 said in Get Large Disk Images on XenServer 6.5 on Local Filesystem?:
I wonder how the conversion would go for EXT3 to QCOW, along with the VM conversion.....
EXT4 -> XFS
VHD -> QCOW
-
@DustinB3403 said in Get Large Disk Images on XenServer 6.5 on Local Filesystem?:
@BRRABill 16 in XS.
Applies To: Windows 7, Windows Server 2008 R2
A spanned volume is a dynamic volume consisting of disk space on more than one physical disk. If a simple volume is not a system volume or boot volume, you can extend it across additional disks to create a spanned volume, or you can create a spanned volume in unallocated space on a dynamic disk.
You need at least two dynamic disks in addition to the startup disk to create a spanned volume. You can extend a spanned volume onto a maximum of 32 dynamic disks.So can Span 16 disk, as 16 is limit with XS
-
@scottalanmiller said in Get Large Disk Images on XenServer 6.5 on Local Filesystem?:
@DustinB3403 said in Get Large Disk Images on XenServer 6.5 on Local Filesystem?:
I wonder how the conversion would go for EXT3 to QCOW, along with the VM conversion.....
EXT4 -> XFS
VHD -> QCOW
Yes... thanks... lol... I meant I'm curious how the process to upgrade an existing system would actually perform...
-
@DustinB3403 said
You can have 16 vDisk per VM in XS.
Yes
is there any limit on the Windows side? (I've never had to span that many disks, was just wondering.)
-
Thanks.
-
@BRRABill said in Get Large Disk Images on XenServer 6.5 on Local Filesystem?:
@DustinB3403 said
You can have 16 vDisk per VM in XS.
Yes
is there any limit on the Windows side? (I've never had to span that many disks, was just wondering.)
@ntoxicator said in
Applies To: Windows 7, Windows Server 2008 R2
A spanned volume is a dynamic volume consisting of disk space on more than one physical disk. If a simple volume is not a system volume or boot volume, you can extend it across additional disks to create a spanned volume, or you can create a spanned volume in unallocated space on a dynamic disk.
You need at least two dynamic disks in addition to the startup disk to create a spanned volume. You can extend a spanned volume onto a maximum of 32 dynamic disks.So can Span 16 disk, as 16 is limit with XS
-
We are all typing too damn fast.
-
We're just SPANNING away. Full speed ahead!
bahaha...
-
Time to break out the electric spanner!
-
@ntoxicator said in Get Large Disk Images on XenServer 6.5 on Local Filesystem?:
@Scale computing nodes...... same limitations I presume?
Sorry for taking a week to see the mention. Thanks for thinking of us.
No, the limitation does not exist on the Scale HC3 clusters. We do not have artificial size limitations. We have tested VMs much larger than 2TB without issue.
