Archive

Archive for October, 2008

Windows Server 2008 R2 Overview Feature Overview- Hyper V 2

October 28, 2008 Mohamed Fawzi Leave a comment

As the competition between VMware and Microsoft Hyper V getting more and more excited. Now Microsoft start talking about Windows 2008 with Hyper V 2

Hyper-V 2.0

2008 R2 will include Hyper-V R2, it promises to deliver the final pieces for enterprise level OS virtualization (together with SCVMM2008) and to really compete with VMware at that level.

·         Live Migration (utilizing a new Clustered Shared Volumes technology)

·         32 Logical Proc Support

·         Hot Add/Remove Storage

·         Second Level Address Translation – Leveraging new Virtualization technology built into next generation of Intel/AMD chips

·         Dynamic Memory

·         Boot from VHD

·         Networking Improvements

·         Virtualised I/O

You can read more information over at Hypervoria, and more at Bink.nu.

System Center Virtual Machine Manager 2008 RTM’s !!!

October 22, 2008 Mohamed Fawzi Leave a comment

Finally the newest member of the System Center Family ..VMM 2008

System Center Virtual Machine Manager 2008 provides a management solution for the virtualized data center that helps enable centralized management of IT infrastructure, increased server utilization, and dynamic resource optimization across multiple virtualization Read More…

Categories: Virtualization Tags:

[riseup] Global Day of Action against Data Retention

October 17, 2008 Mohamed Fawzi Leave a comment

[en] Global Day of Action against Data Retention
[es] Dia de acción global en contra de la retención de datos
[pt] Dia Mundial de Ação contra a Retenção de Dados
[ru] октября. День глобальных действий против сбора данных

October 11th: Global Day of Action against Data Retention
———————————————————

October 11th, marked a global day of action against Data Retention
[1]. We wish to show our solidarity and support those who are being
forced by the by the E.U. Directive 2006/24/EC to participate in
pre-emptive surveillance of communications infrastructure. ISPs in
Europe are being forced by this Directive to be involuntary agents of
the police, to store your communications data. We wish to voice our
dissent of this attack on privacy and demonstrate our strong support and
solidarity for those who fight against this apalling turn of events.

The communication networks of the coming decades are being built now,
and we have an important decision to make: will the infrastructure of
the future be one that supports freedom or one that is designed to
facilitate surveillance and control?

Currently, our communication systems are being redesigned in order to
build a spectacularly efficient machine for maintaining total social
control. This work is being done by the democratic governments of the
world, and the UN, in the name of law enforcement. These governments
have a problem: the internet and new communication technologies are
undermining their capacity for lawful surveillance. Their solution to
this problem has been to attempt total surveillance of all communication
and to require that every internet server becomes a data gathering arm
of the government.

The new technologies of packet switching, digitization, and encryption
are fundamentally different from the communication technologies of the
past. Where once it was expensive and difficult to gather surveillance
data on a particular person, now one can gather detailed data on
millions of people with the push of a button. At the same time, these
new communication systems can also be designed to make surveillance
almost impossible. Unfortunately, there is no middle ground: either we
build systems that are secure or we build systems that are deeply
flawed, easily abused, and lend themselves to social control.

The old compact with the democratic states is over: there is no longer
an option of limited state surveillance. We must choose between greatly
diminished state surveillance or the capacity of total state
surveillance. This is simply the nature of the new communication
technology.

We demand:

* Freedom of Expression: Everyone must be able to communicate
anonymously and privately. Our computers must not become outsourced
extensions of the state police. We must not be required to gather and
archive the communication data of our users. We must not be required to
allow back-door access to the government to listen in on anyone’s
communication.
* Freedom of Association: Everyone must be able to associate freely
without the government tracking and monitoring the network of whom we
associate with. We must be allowed to use communication tools that do
not reveal the sender and recipient. The government must not be allowed,
legally or technically, to build a map of how our social movements are
organized.

Much of the new surveillance we can fight with the voluntary adoption of
better protocols. Other aspects of the new surveillance we must fight
through political organizing, in the courts, in the streets, and by
active disobedience to the law.

The stakes in this struggle are too high. We must work now to keep open
the ability of social movements to communicate privately and freely. If
we do not, we have surrendered our ability to resist governments,
corporations, and injustice for many years to come.

For more information about the global day of action, see Freedom Not
Fear [1].

[1] http://freedom-not-fear.eu

SCVMM 2008 Step by Step Guide. (Part Two of Many)

October 10, 2008 Mohamed Fawzi Leave a comment

Hardware requirements for System Center Virtual Machine Manager 2008

This is a minimum, single machine configuration. Actual requirements and product functionality will vary based on your system configuration and the features you choose to install and on the number of hosts you manage. For more details and the most up-to-date information, please refer to the documentation at

www.microsoft.com/systemcenter/scvmm

Hardware component

Minimum

Recommended

Processor

X64 architecture–based server with 2.8 GHz or faster processor clock speed and with hardware-assisted virtualization support enabled in the BIOS

Dual-Core Pentium 4 3.2 GHz or greater

RAM

2 GB

4 GB

Hard disk

80 GB

200 GB

Virtual Machine Manager Software Requirements — Single Computer

The following software must be installed prior to installing all Virtual Machine Manager (VMM) components on a single computer:

• Microsoft Windows Server 2008® or later (must include Hyper-V)

• Microsoft .NET Framework 2.0 (included in installation)

• Microsoft .NET Framework 3.0 (included in installation)

• Microsoft SQL Server® 2005 Express Edition with Service Pack 2 (included in installation) or Microsoft SQL Server 2005 Standard or Enterprise Editions with Service Pack 2 (separate installation) .

If you do not specify an existing instance of SQL Server 2005, Setup installs SQL Server Express Edition SP2 on the local computer. This also installs SQL Server 2005 Tools and creates an SQL Server instance named MICROSOFT$VMM$ on the local computer.

• Microsoft Windows PowerShell TM 1.0

http://go.microsoft.com/fwlink/?LinkId=77521.

• Microsoft Windows Remote Management (WinRM)

http://go.microsoft.com/fwlink/?LinkId=84599.

• Microsoft Internet Information Server 7.0 (needed for Self-Service Portal only)

· Update for SCVMM 2008 Beta

Install this update to enable Virtual Machine Manager 2008 Beta (VMM) to function with Release Candidate 1 (RC1) to the Hyper-V role. After you install this update, you may have to restart your computer. Once you have installed this update, it cannot be removed.

Download the Update for Virtual Machine Manager 2008 Beta and place the file on your VMM server.

Install the Update

Installing the update will change the VMM product version on your VMM server to 2.0.3194.1.

To install the update

  1. On the VMM server, stop the Virtual Machine Manager Service.
    1. Click Start, point to Administrative Tools, and then click Services.
    2. Locate Virtual Machine Manager and then click Stop the service.

Note

If you do not stop the service prior to installing the update, you will have to restart your computer after installation.

  1. Double-click vmmServerUpdate.msp to start the installation.
  2. When the installation is complete, restart the Virtual Machine Manager Service.

Known Issues

  • When you reinstall an agent, all of the virtual machines on the host will go into a “Missing” state. When this occurs, restart the Hyper-V Virtual Machine Management service on the host to return the virtual machines to their actual state.
  • When you install an agent, the existing virtual networks on the host are occasionally not found by VMM. To fix this issue, restart the Hyper-V Networking Management service.
Categories: Virtualization Tags:

SCVMM 2008 Step by Step Guide. (Part One of Many)

October 9, 2008 Mohamed Fawzi Leave a comment


System Center Virtual Machine Manager provides centralized administration and management of your virtual machine infrastructure, helps increase physical server utilization, and enables rapid provisioning of new virtual machines by the VMM administrator and authorized end users.

Today I will start the series for explain and configure the most important features and tasks in it.

Components of VMM

VMM has many components with different tasks and scope, the main components are:

  • Virtual Machine Manager Server

  • Virtual Machine Host

  • Virtual Machine Library Server

  • Virtual Machine Manager Administrator Console

  • Virtual Machine Manager Self-Service Portal

  • Virtual Machine Manager Agent

Virtual Machine Manager Server
The VMM server is the main component of any deployment as it is responsible for any communication between the VMM service and the rest of components and VMs.

The VMM server runs the VMM service, which runs commands, transfers files, and controls communications with other VMM components and with all virtual machine hosts and VMM library servers, collectively referred to as managed computers. The VMM service is run through the VMM agents that are installed on the managed computers.

The VMM server also connects to a SQL Server database that stores all VMM configuration information. You can access this information and configure VMM by using the VMM Administrator console.

Virtual Machine Host
A virtual machine host is a physical computer that hosts one or more virtual machines. You can add one or more hosts to VMM by using the Add Hosts Wizard in the VMM Administrator Console. The host can be Hyper-V server, Virtual Server 2005 R2 with Service Pack 1 and ESX server. VMM 2008 support management of VMware infrastructure V3. This is one of the new features introduced in VMM 2008.
When you add a host, VMM automatically installs an agent on the host and in case the host was windows 2008 ® it install Hyper-V role if it is not installed.

Virtual Machine Library Server
The Virtual Machine Manager Library server has a VMM library, which is a catalog of resources that can be used to create and configure virtual machines in VMM. The library contains files stored on library shares, and it can contain file-based resources such as:

  • Virtual hard disks.

  • Virtual floppy disks.

  • ISO images and scripts.

  • Virtual machine templates.

  • Hardware profiles.

  • Guest operating system profiles, which can be used to create virtual machines

  • Stored virtual machines that are not in use.

When you add a library server, VMM automatically installs an agent on the library server.
For more information about library servers, see the “Library” topic in VMM Help (http://go.microsoft.com/fwlink/?LinkId=98640).

Virtual Machine Manager Administrator Console
The VMM Administrator Console is a graphical user interface (GUI) that you use to:

  • Create, deploy, and manage virtual machines.

  • Monitor and manage hosts and library servers.

  • Manage global configuration settings.

VMM Console

VMM Console

Virtual Machine Manager Self-Service Portal
The VMM Self-Service Portal is Web-based component that a VMM administrator can configure to allow end users to create and manage their own virtual machines within a controlled environment.
The VMM administrator defines self-service policies that determine which templates self-service users can use to create virtual machines, how many virtual machines they can deploy, which hosts their virtual machines can run on, and which actions they can take on their virtual machines. For more information about self-service, see the “About Virtual Machine Self-Service” topic in VMM Help (http://go.microsoft.com/fwlink/?LinkId=98644).

Virtual Machine Manager Agent
The VMM agent manages virtual machines on virtual machine hosts and allows hosts and library servers to communicate with, and transfer files to and from, the VMM server.
When you add a virtual machine host or a library server in a trusted domain by using the VMM Administrator Console, VMM automatically installs an agent on that managed computer by using the default settings.
For a host that is on a perimeter network, you must install an agent locally on the host before you can add the host to VMM.

Later we will explain the main features of the VMM 2008 like P2V and pro etc etc…

References,

VMM 2007 documentations

Categories: Virtualization Tags:

Hyper-V Virtual Machines lost Network Configuration after a failover (Updated)

October 8, 2008 Mohamed Fawzi 5 comments

I started my Hyper-V failover cluster about month ago.. We are implementing HMC environment on Hyper-V failover cluster VMs. After a sudden electricity failure I started my cluster node I found that I lost my Network Configuration in all my VMs!!!!!

I had to re attach it manually..I tested that many times and every time I lost the Network Configuration.

John Huang …Microsoft Online Partner Support replied to the same problem with those recommendations.

1. Do you have identically named virtual networks on each cluster host?  Please understand that they need to be identical on both hosts otherwise the issue will happen.

2. Please manually attach the Virtual Network to the Virtual  Machine(network connection is not configured) and see if it could start  successfully.

3. Did you update the configuration of the resources after you changed the  network adapter of the already clustered VM (through the “Refresh Configuration” option in the Failover Cluster Management console)? If not, please try this to see if it can help.
The cluster resources for the VM cache information about the configuration of the VM (including information about the networks used by the VM). This information is used to configure the network on the other nodes of the cluster if the VM is moved to a different node than the VM was originally created on. If you do not refresh this information for a clustered VM after you modified the settings of the that VM through the Hyper-V manager, the Hyper-V clustering is not able to correctly configure the network on the new node and the VM will fail to restore.

Further, please install the hotfix below on each cluster nodes as this
hotifx fixed some issue for Hyper-V :
Increased functionality and virtual machine control in the Windows Server 2008 Failover Cluster Management console for the Hyper-V role
http://support.microsoft.com/kb/951308

Although I did all that tricks before his reply but nothing new..Still had the same problem.

I asked MS PPS to confirm if it is a problem with Hyper-V product or just problem with my servers.

Update: Microsoft Online Partner Support John Huang replied today


Hi Mohamed,

Thank you for your update. I know there is no broken links.

After performing a further research, I would like to confirm the following information with you:

I notice there is a known issue regarding NIC lookup. If you have multiple physical network cards and some of them are not bond to a virtual switch, the failover between cluster nodes will fail due to a known issue in Hyper-V components. Upon failover, this Hyper-V component queries available virtual switch associated with network cards and an error occurs when there is any network card that isn’t bond to virtual switch.

If so, this is known issue  and we have this reported already in our internal database and are working on to fix it.

For now, we could bind all hardware network cards to Hyper-V virtual switch to avoid this exception.

I look forward to your reply.

-regards

-John Huang

Categories: Hyper-V, Virtualization