Hello All,
Thanks a lot for your quick and extremely useful responses. Although, I
have not been able to solve the problem but I would like o mention some
things about my configuration setup for the guest domains and the host
domain. As mentioned earlier, I have two nodes running (dmz02 and
dmz03).
DMZ02 is using xen-3.0.3 version which I grabbed from the Xensource
website a couple of days back. The guest domain configuration file has
been setup so as to use DHCP protocol for assigning the IP addresses to
the guest domains. Now one of the problems that I am facing is that the
Xen guest domains are not being able to see the DHCP server on creation.
Therefore, the domains are created in a "blocked" state. That might
explain why things are not working for me.
DMZ03 is using xen-3.0.3-testing.hg source obtained 3-4 weeks back. Can
that be a potential problem too? Now, DMZ-03 is been used by one of my
other colleagues, so it would take some handshaking for me to get the
versions compatible. Also, the guest domains on this node are created in
the "blocked" state.
So, I understand that the guest domains should be in a "running" state
for migration to take place. Is that a safe statement to say? Anyways, I
think my problem is the "blocked" state and the unreachable DHCP server.
I have checked that my /etc/xen/xend.config has been configured properly
on both sides.
Thanks for all your suggestions.
Wish you all a Happy new Year.
Thanks,
Nikhil
-----Original Message-----
From: Adam Seering [mailto:aseering@xxxxxxxxx]
Sent: Friday, December 29, 2006 11:34 AM
To: Keir Fraser
Cc: Ian Pratt; xen-devel@xxxxxxxxxxxxxxxxxxx;
xen-users@xxxxxxxxxxxxxxxxxxx; Bhatia, Nikhil; Nico Kadel-Garcia
Subject: Re: [Xen-users] RE: [Xen-devel] Xen-3.0.3 migration problems
On Dec 29, 2006, at 5:05 AM, Keir Fraser wrote:
> On 28/12/06 5:15 pm, "Adam Seering" <aseering@xxxxxxxxx> wrote:
>
>> I'm having this same problem. The relocation service is enabled on
>> both machines; neither has a firewall (sure, I care about
>> security...), and there is no firewall between them.
>>
>> For a live migration, do the dom0 kernels and the source/target PC's
>> hardware have to be the same? I'm migrating from a stock Debian
>> Etch-
>> based Xen AMD64 system on a Pentium D 8xx (no HVM) to a Fedora Core 6
>> Xen AMD64 system on a Pentium D 9xx, with HVM support enabled.
>
> Migrating to a newer (more capable) processor should work. It's when
> features silently disappear that guests can get upset. The dom0
> kernel does
> not matter but the version of the Xen toolstack might -- did you
> install Xen
> and tools yourself on both boxes from a consistent version?
I did not, actually; I'm using the stock versions from the FC6 /
Debian Etch repo's. I could try that.
One of these machines just lost a hard disk; I'm not eager to try
anything interesting until I can replace it, so I'll play around with
this when the new drive comes in.
A recent e-mail mentioned that migration machines have to be on the
same L2 subnet (I missed that line in the Xen manual). These
machines aren't; they're in different buildings, with IP routing
between them (though the connection speed and latency are very
good). I'll try putting the machines on the same subnet.
> /var/log/xen/xend.log and /var/log/xen/xend-debug.log probably have
> interesting info if things are going wrong (the logs may be big: if
> so it's
> the tail that's interesting).
OK; I'll take a look at those.
Thanks,
Adam
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home