Preface
Let me ask one question here: Why would -I to create a dual boot configuration or multi, if I'm the hardware to run a bare metal hypervisor?
a pilot for a bare metal hypervisor is that you can run almost any OS on top of this thin piece of code without suffering huge performance degradation. So performance is not a valid reason for the need to still be able to sometimes start without an OS to run on top of a bare metal hypervisor. It is probably fair to say that a multi-booting configuration is pretty much something people required technology - such as myself for wired configurations and case engineering and the use of testing
An important reason for me is the networking. I'm an old type of networking and protocol analysis done for years, every time something goes wrong, I tend to run Wireshark to capture network traffic. To do this, the network adapter must be attached to the cable and set in promiscuous mode, which is a bit complicated using a virtualized operating system. Another reason is flashing firmware for routers or cell phones using USB or serial com in specific patterns can be difficult too.
Again, for only in OS and applications and even high demanding XenClient Games will do the job well, I bet most users would not notice a performance difference at all anyway
What is the approach
If you have dealt with the installation of XenClient, you may have noticed.?; a new default install XenClient take the entire hard drive. However, if you looked in the PXE configuration, you can actually specify the partition, choose to let the OEM partition intact and where XenClient should have been installed.
One possible way is to ensure that there is already a XenClient installation, so the installation will point to use this partition (just need a group of local volumes named XenClient )
Before You begin
- Before we begin, I would spend some time to think about what operating system needs how many space ... Sounds logical, but how long do you partition a disk and finally found a partition is full, while another is almost empty
- Install Windows first, it is easier because of windows 7 generally want to create that 100MB boot / partition bitlocker
And btw. I did the partitioning always live separated, but Steven Tyler posted a quick guide on the XenClient support forum using fdisk during installation that makes it even faster and easier!
Step by Step
I'll do in this example a multi-boot configuration with Windows 7, XenClient and Linux
install windows (or shrink an existing installation) so that you have some space left on your. harddrive
After the Windows installation is complete, start the installer XenClient - boot from the CD, memory stick or PXE boot and on the home screen press ALT + F3 to switch to a (user name root / no password) shell.
now start partitioning your drive with fdisk and write the information down to install the further steps.
- "fdisk" will print all disk partition table
- "fdisk / dev / sda" will start partitioning your first hard drive
- once you have started using fdisk "m" for options such as "P" will print the current configuration
Now create your partition XenClient ; make sure it is a primary partition and the ID is set to "bd".
- "n" Create a new partition
- "p" Choose primary
- "3" partition number 3 (1 and 2 taken by Windows 7)
- "Enter" to begin with the first free cylinder
- "+ 0000m" to create a 0GB partition
- "t" + "3" + "bd" will define the bd ID
- Check by pressing the "p" (print)
- If everything looks good press "w" for writing
" fdisk "now looks like the image below:
now we can create the volume and volume group and assign the name XenClient to it.
- "-y -ff pvcreate / dev / sda3" prepares the physical disk to use with LVM
- "XenClient vgcreate / dev / sda3" creates the volume group
I will install Ubuntu furthermore, I'm going another primary partition on the disk and simply fill the empty space.
now, go back to the installer by pressing ALT + F1 and select Advanced installation. The Setup recognizes the "installation" and existing offer to crush the partition.
Once installation is complete your system XenClient is expected to start directly after the restart. Wont install Linux now but keep the reserved partition, so I'll add the bot XenClient and Windows in the boot loader configuration.
Open a terminal once started XenClient or use ssh if remote access is granted.
Add a menu entry in the /boot/system/grub/grub.cfg file using vi.
menuentry "Microsoft Windows 7" {set root = (hd0,1) chainloader +1} This is referred to the second partition hard fist.
Reboot XenClient and press ESC during the startup screen to display the Start menu, select "Microsoft Windows 7" and press Enter.
You're all set!
Enjoy XenClient and as usual excuse for typos!
questions and comments here on the forums or just drop me an email: walter.hofstetter [at] eu.citrtix.com
Sincerely, Walter
PS .. If you come to Synergy Barcelona, there is still a chance to get into one of XenClient hands on labs that I'm simply showing 30 minutes before beginning the lab (Room 134) - Even if sold out, there is still no show!
0 Komentar