|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [OSSTEST Nested PATCH v11 6/7] Compose the main recipe of nested test job
> > >
> > > Thinking about this leads me to ask another question. Suppose that a
> > > bug causes the l1 to lock up completely. ts-logs-capture will attempt
> > > to hard reboot a locked-up host. If it can't fetch any logs, it calls
> > > target_reboot_hard($ho);
> > >
> > > What will that do if $ho refers to the l1 ? It relies on the power
> > > method. Does your nested l1 "host" have a power method ?
> > I'm afraid l1 won't like normal hosts has power cycle operations. Maybe
> > we need to simulate it?
>
> Perhaps arrange for an appropriate PowerMethod for "hosts which are
> actually guests"?
>
Update.
I think maybe we need to refactor 'power_cycle' function in TestSupport.pm. I
have not try it, something like below?
sub power_cycle ($) {
my ($ho) = @_;
+ if (guest_var($ho,"enable_nestedhvm",'') =~ m/true/) {
+ guest_destroy($ho);
+ guest_create($ho);
+ guest_await_dhcp_tcp($ho,300);
+ guest_check_up($ho);
+ } else {
$mjobdb->host_check_allocated($ho);
die "refusing to set power state for host $ho->{Name}".
" possibly shared with other jobs\n"
if $ho->{SharedMaybeOthers};
power_state($ho, 0);
power_cycle_sleep($ho);
power_state($ho, 1);
+ }
}
> Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |