Tag Info

New answers tagged

0

FYI. Here is where i messed up. In the dom0 ./interfaces, i initialize the physical interface as manual. I initialize the bridge as static and add the physical interface to it. The bridge was created with a static IP assigned - the same one the domU claimed with, a different virtual mac address though. Long story short, tcpdump showed both the bridge ...


1

You can set up Dom0 to auto-start specific virtual machines when the server boots up. Domain0 will still be available, but the users using the virtual machine will not see this. I assume this is what the client wants. The phrases "Wants to install hypervisor" and "Like its not a VM" are contradictory and don't really make sense.


2

Hope this helps anyone looking at this problem in the future. We've experienced this issue in a similar environment: Ubuntu 14.04 3.13.0 Kernel QEMU KVM environment Our Splunk cluster master was issuing these warnings on average every five minutes. CPU load would go up to 35% routinely, and the warnings would list splunkd or python as the process most ...


0

Docker can run on any hypervisor, AFAIK. I'm running Docker on an Ubuntu VM running on my XenServers at home. I also have an Ubuntu VM on my laptop running Docker within Virtualbox. Also, if you're interested in Docker, I would look at CoreOS, which offers Docker features in a clustered form. As far as choosing a hypervisor to work with, pick the one your ...


0

The answers in this post have grown dated. Although more recent, my answer is a summary from barely skimming the surface of this topic. Hopefully it will jumpstart updates to the thread and I have marked it Community Wiki in hopes that it evolves to better content. XCP -> XenServer As I have dug into this, I am increasingly finding that what was XCP has ...


0

Xen HVM is the only type of Xen that will support a different OS. KVM will run anything of course. As for which to choose, that's offtopic on SF.net


0

The latter. For normal workloads there is nothing you can only do with one or another. If you come from OpenVZ I would suggest KVM since it's architecture is more similar to what you know. Xen is a completely different concept.


1

Couple of observations: You are running a very old device/driver (mthca) on a relatively new OS (Ubuntu 14.04). Unless somebody corrects me, I don't believe that anyone has really tested this. Where did you get the driver from? Which OFED version is it? The test is killed by the oom-killer, which means that you have ran out of memory. That MTT stuff is ...


3

The first VM is running in PVHVM mode, so QEMU is working with Xen to virtualize the hardware behind the VM. This mode is for OS that does not support Xen paravirtualization in general, like Windows and FreeBSD. The second one is from a VM running in PV mode. In this mode, everything is paravirtualized. So there's no emulated BIOS. The booting process is ...


1

Memory for the dom0 is probably limited via kernel cmdline. You can check that by looking into: cat /proc/cmdline If there is something like: dom0_mem=min:1024M,max:1024M, then that's the reason for unexpected RAM readings.


1

From the information you provided, my impression is that Volume group is created out of 4 partitions sd[abcd]2 and not from md1 raid array. You should run pvdisplay and/or pvs to confirm that. If that's correct, the way to proceed would be to remove LV, VG and PVS from sd[abcd]2, rebuild RAID 10, and pvcreate /dev/md1; vgcreate ...


1

A volume group can have multiple physical disks (or in your case, partitions). First you need to have place on your larger disk (/dev/sda). You didn't wrote anything, where you can had that, but based on your question I assumed an unnamed partition. Name this to /dev/sdaX . EXTENSION AFTER UPDATE: You need to make place on your /dev/sda. I your place I ...



Top 50 recent answers are included