Tag Info

New answers tagged

1

With Failover Clustering, each Hyper-V host would be connected to the same LUN. You would then create a Cluster Shared Volume from that LUN. The virtual hard disks for the virtual machines would "live" on the CSV and the virtual machines would "run" from one Hyper-V host or the other. In the event of a failure of one of the Hyper-V hosts, the virtual ...


1

You will need to have some sort of hypervisor installed before you can run a virutal machine. For the use case you are proposing you sound more like you're asking to netboot your workstation. There are apps that will let you do either, although it's not easy to netboot Windows unless you're using Windows PE.


0

People like to hate on OVZ for some reason but seem to forget that LXC is a derivative of OVZ. If OVZ is such old tech then why is it's DNA in brand new tech? Other than doing something with cgroups, I don't see OVZ going away any time soon. There is cross polination with LXC and if and when LXC is a drop in replacement for OVZ then OVZ can go away. It's ...


1

With a few exceptions, such as classic VMware on the guest, it's not possible to nest virtualization within virtualization. Although this would be a convenience for you, you'll have to attack it from another angle. Perhaps look into exporting a machine image from Virtualbox and then importing to Azure. However, I did find somebody doing just what you ask: ...


2

In Icehouse and later you can convert Cinder volume to Glance image with upload-to-image command: cinder upload-to-image <volume> <image-name>


0

The issue it sounds like you are facing is that your VHDs are not ready to be used with Hyper-V. There is no boot loader in the VHDs taken by Windows Backup. You're correct that you need to to a physical to virtual (P2V) conversion on them before you work through the article you've linked to. System Center Virtual Machine Manager achieves this but unless ...


1

Currently there is no complete GPU acceleration support for OpenStack. There is a proposal to add support for GPU-accelrated machines as an alternative machine type in OpenStack. The target release for this is Grizzly. You can check out a functional prototype here. Successful openstack deployemnt with CUDA support. cg1.xlarge instance type and NVIDIA Fermi ...


0

You have a dedicated server with OVH. By default these boot an OVH-provided kernel from the network, not the kernel installed on your server. You need to change the configuration of your server, in your OVH account management web pages, to boot from the hard drive.


2

It sounds like you're not provisioning your virtual disks with enough capacity to begin with. Windows in particular tends to grow the base OS footprint quite a bit due to hotfixes over the course of several years. The newest versions of Windows (8.1/2012 R2) mitigate this to a certain extent with some default scheduled tasks that cleanup superseded update ...


0

ifconfig eth0 promisc is the correct command to enable promiscuous mode for an interface. If that didn't work try adding this line to /etc/rc.local and reboot. ifconfig eth0 up ifconfig eth0 promisc


1

I'm not 100% sure, But based on my own experiences, this should work: Here are the steps to follow: Create a virtual machine in Hyper-V and attach the Windows Server Backup VHD file Boot the Hyper-V machine to WinPE Launch Regedit Highlight HKLM and click Load Hive Depending on the configuration of the system partition, navigate to ...


6

From the appropriately named (and fairly SEO-friendly) TechNet article "What is Sysprep?": [...] Sysprep also enables you to prepare an image to be delivered to a customer. When the customer boots Windows, Windows Welcome starts. Then, follows a general notice about appropriate usage: Sysprep must be used only to configure new installations of ...


0

if you could export an aws instance / image to openstack, for instance, bezos would be losing money..... the whole concept of the cloud is that instances are ephemeral and conf mgmt (puppet, salt, etc) is what makes them do what they do. data volumes are a different however, and that is obviously possible. to actually boot an aws instance on your local ...


0

Yes, I was looking too for the answer, and recently I found that Amazon ec2 cannot tolerate importing instances created first time with ec2 hyper-visor. What you can do is migrate the content of the VM to another placement, a reserved instance more cheaper for example, by creating a snapshot of an ebs boot partition in order to recreate the same vm. ...


0

Since the desired state is 0.1 processing unit and 1 virtual processor, this is what you get, 1 virtual processor with 0.1 real processor. Since the maximum state is 1.0 processing unit with 4 virtual processors, this is what you get. 4 virtual processors sharing 1 processing unit. What don't you understand? You get what you ask for if the system has the ...


0

I agree with the first answer, but in general, with a Microsoft CRM Database that is over 100 GB in size, I'd recommend having more RAM than 12 GB on the SQL Server, and would prefer seeing at least 32 GB of RAM for a Microsoft CRM database of this size. To be more specific about finding out the cause of what's contributing to your SQL Server performance ...


0

This has been solved using two internal networks with VirtualBox. The network security device (Security Onion) has two interfaces, one interface for each network. It has IP forwarding enabled so it can route. The Kali machine sets its default gateway to the Security Onion box's IP address for its interface that has the network it shares with Kali ...


4

I'd use option #1, more host manageability. I'd focus other efforts on making your remote sites more resilient... Power is not difficult to protect in the branch office scenario. Buy batteries with extended-run capacity. E.g. my customers in volatile Los Angeles power conditions have between 60 and 240 minutes of battery runtime. In the case of a ...



Top 50 recent answers are included