Pxe boot vdi


I have vdi on hyperv 2008r2 env
Can anyone say reason why people need to use pxe boot for vm.Is it a design requirement for performance...hyper v needs some legacy nic for this which is just 100 Mbps and that's a bottleneck..
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

PXE is used either for deployment of OS to a brand new computer, or for diskless systems.
It is not needed for VMs that are already setup on their own harddisks.
Your VDI solution may be trying to save disk space by using VMs without disks and just booting off the network.
Other VDI solutions use base/delta images and not PXE.  Basically the base image is the installed OS but without identity.  Each VM is given a delta disk which stores any changes the VM writes to the disk (like identity and other customizations) which is linked to the base image.  When the VM reads from the disk it first searches for the sectors on the delta disk, if not there finds them on the base.
Sukku13Author Commented:
Is it better to boot using pxe or use what you termed delta disk..will it effect login time
Dirk KotteSECommented:
citrix use PXE with the provisioning services (PVS).
PVS boot the VM diskless. Means you have to maintain the Image at the PVS.
There are different options:
1. Different devices connect this image as Harddisk.  PVS change (on the fly) Hostnames, SID's,... so every device keeps unique.
Differences are cached at different places (memory,Server,local HDD) and discarded while rebooting the Virtual-device.
2. Different devices connect this image as HDD like variant 1 but the differences are written to a personal-Vdisk and not discarded
3. every device has it's own vdisk at the PVS and writes the differences directly to this file

the other way (without PVS) uses the Machine creation Service (MCS)
here you have a master-Image and the devices store the differences at a second connected disk.

the big differences are within the storage environment, LAN infrastructure, maintenance requirements.
- PVS devices boots very fast; MCS need some time to create the devices and/or disks while booting
- PVS devices freeze and wait if the PVS server is lost and no second server is available  ...

if the virtual device is ready booted the logon time for the user should be the same.
the best solution depends on your environment and requirements.
If you want faster then delta disk is faster since the virtual computer is already setup and stored.  Using PXE based solutions the servers always have to rum a part of setup since they all boot from the same disk but must be unique on the network.
Also some user information can be persisted on the delta disks rather than relying entirely on roaming profiles.
Dirk KotteSECommented:
the adjustments don't need noticeable time.
but with PXE you can have a fresh, fast system with every boot.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.