XenServer 7 has launched!
-
NFSv4 is available now too, but like SMB, don't use it. NFSv3 is the leader in file storage for things like VM storage.
-
I know there has been a lot of discussion about relocating log files and swap files/partitions if you boot off of USB.
How do you think this new version, having separate partitions for these tasks, will affect this?
-
@BRRABill said in XenServer 7 has launched!:
I know there has been a lot of discussion about relocating log files and swap files/partitions if you boot off of USB.
How do you think this new version, having separate partitions for these tasks, will affect this?
We will have to see how the installer handles it, but in theory it is going to make this very easy.
-
@BRRABill the increased root partition is to make life easier to manage log files.
Ideally you'd still want to push your log files to a different medium entirely so that your boot device isn't consumed with read/write events.
-
@DustinB3403 said in XenServer 7 has launched!:
@BRRABill the increased root partition is to make life easier to manage log files.
Ideally you'd still want to push your log files to a different medium entirely so that your boot device isn't consumed with read/write events.
That's one of the new features. Separate log device for the logs.
-
One suck part.
-
@DustinB3403 is that a feature that it had before? And really, isn't that something you would want outside of XS, not inside of it?
-
@scottalanmiller I would want to be able to manage the DRAC from within XS if at all possible.
One less interface to have to jump through to manage the hardware. But I have a general idea of why it isn't able to control the host.
-
@DustinB3403 said in XenServer 7 has launched!:
@scottalanmiller I would want to be able to manage the DRAC from within XS if at all possible.
but the point of out of band management is to be out of band. Just use in band management from inside of XS.
-
I know I get it, but at the same time.. lol
-
Another cool function is that you can have an AV agent like BitDefender's GravityZone and still protect the VM's as if there was an AV agent installed directly to the guest!
-
Looks like you can updates directly from XenCenter now. Sorry @olivier
-
@aaronstuder said in XenServer 7 has launched!:
Looks like you can updates directly from XenCenter now. Sorry @olivier
That's because the functionality was released by Citrix for XC to everyone. No reason to not have it built in this version either.
-
@aaronstuder said
Looks like you can updates directly from XenCenter now. Sorry @olivier
That's actually been around for a while now.
I was looking for the "windows-like way" of updating and found it.
-
@DustinB3403 said
Ideally you'd still want to push your log files to a different medium entirely so that your boot device isn't consumed with read/write events.
Or the cells on the thumb drive torched, which is probably the bigger concern, right?
-
@scottalanmiller said
That's one of the new features. Separate log device for the logs.
They had that in 6.5, too.
Though it didn't turn off local logging as well.
Are you saying with XS7, you can totally turn off local logging?
-
Just a "Jeopardy Knowledge" question...
Can someone explain the difference between these two things? Is one (7.0.1) only provided to paying support customers?
"Note: This issue occurs only on the original copy of XenCenter (v7.0.0) included on the XenServer 7.0 Base Installation ISO. Installing XenCenter v7.0.1, available to download from the XenServer 7.0 Product Download page, resolves this issue"
-
@DustinB3403 said in XenServer 7 has launched!:
The root partition is now 18GB!
Damn!
Now I don't feel bad using that 32GB for my production system.
Actually, reading through the install guide, it says this... So it looks like 32GB isn't even enough!!
ā¢ 18GB XenServer host control domain (dom0) partition
ā¢ 18GB backup partition
ā¢ 4GB logs partition
ā¢ 1GB swap partition
ā¢ 0.5GB UEFI boot partitionCustomers installing XenServer 7.0 with the new partition layout described above should ensure they have a disk that is at least 46GB in size.
Customers who would like to install XenServer 7.0 on smaller devices, that is devices with more than 12GB but less than 46GB disk space, can perform a clean installation of XenServer 7.0 using the legacy DOS partition layout.
-
@olivier said
I'm not sure. I discovered a lot about the upgrade process just today. I'd love to have more input/doc from Citrix before the D-day, but you know, it's hard to be in the plans of a big corp
Here is the answer for the VDIs on the local SR.
During the upgrade process, the RPU wizard checks for VDIs on the local SR. If there are any virtual disks (VDIs)
present during the upgrade process, the wizard prompts you to move the VDI. You should move VDIs on the
local SR to a shared SR and then restart the upgrade process in order to continue with the new layout. If, for any
reason, the VDIs cannot be moved, or if there is insufficient space (less than 46GB) on the local SR, the upgrade
will proceed with the old partition layout and allocates 0.5GB of disk space from the dom0 partition to UEFI boot. -
Do any of you have recommendations for USB sticks to run the hypervisor on?
