Re: [Xen-devel] [OSSTEST PATCH 26/26] ts-xen-install: networking: Rename `nodhcp' to `ensurebridge'

["Hu, Robert" <robert.hu@xxxxxxxxx>]

> -----Original Message-----
> From: Hu, Robert
> Sent: Thursday, October 22, 2015 10:33 AM
> To: 'Ian Jackson' <ian.jackson@xxxxxxxxxxxxx>;
> 'xen-devel@xxxxxxxxxxxxxxxxxxxx' <xen-devel@xxxxxxxxxxxxxxxxxxxx>
> Cc: 'Ian Campbell' <ian.campbell@xxxxxxxxxx>
> Subject: RE: [OSSTEST PATCH 26/26] ts-xen-install: networking: Rename
> `nodhcp' to `ensurebridge'
> 
> > -----Original Message-----
> > From: Hu, Robert
> > Sent: Thursday, October 15, 2015 5:58 PM
> > To: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>;
> > xen-devel@xxxxxxxxxxxxxxxxxxxx
> > Cc: Ian Campbell <ian.campbell@xxxxxxxxxx>
> > Subject: RE: [OSSTEST PATCH 26/26] ts-xen-install: networking: Rename
> > `nodhcp' to `ensurebridge'
> >
> > > -----Original Message-----
> > > From: Hu, Robert
> > > Sent: Thursday, October 15, 2015 5:39 PM
> > > To: 'Ian Jackson' <ian.jackson@xxxxxxxxxxxxx>;
> > > xen-devel@xxxxxxxxxxxxxxxxxxxx
> > > Cc: Ian Campbell <ian.campbell@xxxxxxxxxx>
> > > Subject: RE: [OSSTEST PATCH 26/26] ts-xen-install: networking: Rename
> > > `nodhcp' to `ensurebridge'
> > >
> > > > -----Original Message-----
> > > > From: Ian Jackson [mailto:ian.jackson@xxxxxxxxxxxxx]
> > > > Sent: Saturday, September 26, 2015 3:15 AM
> > > > To: xen-devel@xxxxxxxxxxxxxxxxxxxx
> > > > Cc: Hu, Robert <robert.hu@xxxxxxxxx>; Ian Campbell
> > > > <ian.campbell@xxxxxxxxxx>; Ian Jackson <ian.jackson@xxxxxxxxxxxxx>;
> > Ian
> > > > Jackson <Ian.Jackson@xxxxxxxxxxxxx>
> > > > Subject: [OSSTEST PATCH 26/26] ts-xen-install: networking: Rename
> > > `nodhcp'
> > > > to `ensurebridge'
> > > >
> > > > This function does not (now) always undo the DHCP configuration.
> > > > Sometimes it leaves it.  Its main function is to ensure that we have
> > > > a bridge for use by guests.
> > > >
> > > > So rename the function.
> > > >
> > > > Signed-off-by: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
> > > > ---
> > > > v14: This patch was previously 4/4 of a miniature series containing
> > > >       a different way of dealing with the Nested HVM L1 DHCP
> > problem.
> > > > ---
> > > >  ts-xen-install |    4 ++--
> > > >  1 file changed, 2 insertions(+), 2 deletions(-)
> > > >
> > > > diff --git a/ts-xen-install b/ts-xen-install
> > > > index d9aa694..3d0f394 100755
> > > > --- a/ts-xen-install
> > > > +++ b/ts-xen-install
> > > > @@ -247,7 +247,7 @@ sub hosts () {
> > > >      });
> > > >  }
> > > >
> > > > -sub nodhcp () {
> > > > +sub ensurebridge () {
> > > >      target_editfile_root($ho, "/etc/network/interfaces",
> > > >                           "etc-network-interfaces", sub {
> > > >          my $physif= get_host_property($ho,'interface
> force',undef);
> > > > @@ -370,6 +370,6 @@ if ($checkmode) {
> > > >      adjustconfig();
> > > >      setupboot();
> > > >      setupinitd();
> > > > -    nodhcp();
> > > > +    ensurebridge();
> > > >      hosts();
> > > >  }
> > > [Hu, Robert]
> > > Not sure if it is caused by this patch, but after Xen installed in L1, 
> > > after L1
> > > reboot,
> > > it boots fail.
> > >
> > > Here is log dumped in L0:
> > > (d53) drive 0x000f6330: PCHS=16383/16/63 translation=lba
> > > LCHS=1024/255/63 s=20480000
> > > (d53) drive 0x000f6360: PCHS=0/0/0 translation=lba LCHS=1024/255/63
> > > s=40960000
> > > (d53) Space available for UMB: ca800-ee800, f5d80-f62d0
> > > (d53) Returned 258048 bytes of ZoneHigh
> > > (d53) e820 map has 6 items:
> > > (d53)   0: 0000000000000000 - 000000000009fc00 = 1 RAM
> > > (d53)   1: 000000000009fc00 - 00000000000a0000 = 2 RESERVED
> > > (d53)   2: 00000000000f0000 - 0000000000100000 = 2 RESERVED
> > > (d53)   3: 0000000000100000 - 00000000bf7ff000 = 1 RAM
> > > (d53)   4: 00000000bf7ff000 - 00000000bf800000 = 2 RESERVED
> > > (d53)   5: 00000000fc000000 - 0000000100000000 = 2 RESERVED
> > > (d53) enter handle_19:
> > > (d53)   NULL
> > > (d53) Booting from DVD/CD...
> > > (d53) Boot failed: Could not read from CDROM (code 0004)
> > > (d53) enter handle_18:
> > > (d53)   NULL
> > > (d53) Booting from Hard Disk...
> > > (d53) Booting from 0000:7c00
> > > (XEN) irq.c:275: Dom53 PCI link 0 changed 5 -> 0
> > > (XEN) irq.c:275: Dom53 PCI link 1 changed 10 -> 0
> > > (XEN) irq.c:275: Dom53 PCI link 2 changed 11 -> 0
> > > (XEN) irq.c:275: Dom53 PCI link 3 changed 5 -> 0
> > > (XEN) traps.c:3287: GPF (0000): ffff82d0801ea213 -> ffff82d080244f4b
> > > (XEN) traps.c:3287: GPF (0000): ffff82d0801ea213 -> ffff82d080244f4b
> > >
> >
> > I'm using latest xen.git master. Will try again with Xen 4.6 release which 
> > we
> > have
> > tested.
> [Hu, Robert]
> After fixed several environment setting issues, I just run OSSTest on Xen 
> 4.6.0
> release code. This issue still exist there, so this is probably the new patch
> which
> introduced this.


[Hu, Robert] 
Seems the failure log shall be this, any idea? I've spent days on debugging 
this:(
(XEN) traps.c:3290: GPF (0000): ffff82d080195082 -> ffff82d080243d9d
(XEN) PCI add device 0000:00:00.0
(XEN) PCI add device 0000:00:01.0
(XEN) PCI add device 0000:00:01.1
(XEN) PCI add device 0000:00:01.2
(XEN) PCI add device 0000:00:01.3
(XEN) PCI add device 0000:00:02.0
(XEN) PCI add device 0000:00:03.0
(XEN) d0: Forcing read-only access to MFN fed00
(XEN) Hardware Dom0 crashed: rebooting machine in 5 seconds.
Issued domain 3 reboot
qemu: terminating on signal 1 from pid 4322

> 
> >
> > >
> > > > --
> > > > 1.7.10.4


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel