I am having trouble with recovery. Today due to electrical work I
powered down my networks Router / DHCP server.
My Centos 7 host machines lost their DHCP lease (they are actually
static leases). Once I power my Router / DHCP server back up none of my
virtual machine were accessible. It
Take a look at http://wiki.xensource.com/xenwiki/VTdHowTo
Two things in particular about PCI passthrough:
- Only devices with FLR capabilities are supported.
- Some motherboards are buggy. They advertised that they support Vt-d
but do not correctly handle it (those with a broken ACPI DMAR
On 01/12/2011 02:04 PM, Ken Bass wrote:
More info...After comparing my working system with the non-working one.
I notice the non-working ext3 filesystem has an inode size of 256. The
working system 128. Could this be the issue with grub? I see some
ramblings on the Internet about grub
Ed Heron wrote:
I was slightly confused about this thread until I realized you were using
static IP config on your VM's...
Why do people do that?
Why? Because this box sits in an ISP and has official static IP
addresses assigned to the dom0 and each domU.
Christopher Hunt wrote:
Ken,
I think Pasi's on to something there, I bet the GATEWAY command
in ifcfg-eth0 is mistyped or has a syntax error. In the interem,
however, a better hack might be to move the route statement from
rc.local, which only runs at boot, to
I have been trying to figure out why my domU NIC becomes unreachable
(could not even ping) at various times. (Normally when the server was
trying to update clamav from the various busy mirrors at 4am). There
also seemed to be some latency when connecting which I chalked up to it
being a
I have a machine with 8 CPU's (2 quad xeons). (Centos 5.4 currently).
Currently, I am running 2 domUs. One with 4 CPUs and another with 2. 2
remain unused. I am using routed networking.
On the one machine with 4 CPU's, there is a cronjob at 4am which
utilizes the CPU/disk pretty heavily. It is
Christopher G. Stach II wrote:
In high I/O environments or ones with a lot of unpredictable guests, it's a
good idea to pin dom0's CPU(s) to physical cores and exclude those cores from
the guests. I find that dom0 usually only needs one CPU (pinned to one core)
in almost every environment.
Ben M. wrote:
Not trying to take this off-topic, I think it is relevant.
Christopher: When I booted up with dom0-cpus 1, Windows 2008 could not
find its second cpu. However, once up, I can xm or virt-manager it
down to 1 cpu on cup 0 and everything is fine.
Is this a unique issue or do
Christopher G. Stach II wrote:
If you have your guest provisioning set up with scripts or you do it manually
with virt-install, also add --cpuset=pcpus to the arguments.
I use a config file located in /etc/xen that I have symlinked in the
auto directory.
Its been a while since I set it
I just cant get a Centos 5.1 domU to install under Centos 5.1 dom0. It
is maddening! I'm trying to replace a single server that currently uses
simple ethernet aliases (eth0:0, eth0:1, etc) with a new server that
uses Xen virtualization.
Maybe I dont understand bridging properly or something.
My
Kai Schaetzl wrote:
Ken Bass wrote on Mon, 28 Apr 2008 15:08:22 -0400:
In anaconda, I select manual/static IP address. I enter 192.168.139.4
with subnet mask of 255.255.255.255, gateway/ns of 192.168.144.5
AFAIK, there is no route from 192.168.139.4 to 192.168.144.5. You need to
specify
12 matches
Mail list logo
