[PATCH][3/5] Don't delete qemu-dm.debug on make clean, but install it separately

[PATCH][3/5] Don't delete qemu-dm.debug on make clean, but install it separately

[Arun Sharma]

Don't delete qemu-dm.debug on make clean (Fixed by Keir already). But
install qemu-dm.debug so people can do useful things with it in a
development environment.

Signed-off-by: Arun Sharma <arun.sharma@intel.com>

diff -r be004ea3a553 -r 1c9d6ba65696 tools/ioemu/target-i386-dm/Makefile
--- a/tools/ioemu/target-i386-dm/Makefile	Thu Jun 30 20:29:39 2005
+++ b/tools/ioemu/target-i386-dm/Makefile	Thu Jun 30 20:42:39 2005
@@ -386,6 +386,7 @@
 	if [ ! -d $(DESTDIR)$(configdir) ];then mkdir -p $(DESTDIR)$(configdir);fi
 ifneq ($(PROGS),)
 	install -m 755 -s $(PROGS) "$(INSTALL_DIR)"
+	install -m 755 -s qemu-dm.debug "$(INSTALL_DIR)"
 endif
 	install -m 755 qemu-ifup "$(DESTDIR)$(configdir)"
 	gunzip -c qemu-vgaram-bin.gz >qemu-vgaram-bin 

Re: [PATCH][3/5] Don't delete qemu-dm.debug on make clean, but install it separately

[Keir Fraser]

On 1 Jul 2005, at 19:57, Arun Sharma wrote:

> Don't delete qemu-dm.debug on make clean (Fixed by Keir already). But
> install qemu-dm.debug so people can do useful things with it in a
> development environment.
>
> Signed-off-by: Arun Sharma <arun.sharma@intel.com>

qemu-dm.debug looks like it is supposed to be target for debug build of 
qemu-dm. So please pick a better name. :-)

Also the qemu-dm.debug has ended up getting deleted, so please send us 
a patch that reincludes the script with a better name, and adds the 
install line to the Makefile.

  Thanks,
  Keir

Re: Re: [PATCH][3/5] Don't delete qemu-dm.debug on make clean, but install it separately

[Keir Fraser]

> 
> On 1 Jul 2005, at 19:57, Arun Sharma wrote:
> 
> > Don't delete qemu-dm.debug on make clean (Fixed by Keir already). But
> > install qemu-dm.debug so people can do useful things with it in a
> > development environment.
> >
> > Signed-off-by: Arun Sharma <arun.sharma@intel.com>
> 
> qemu-dm.debug looks like it is supposed to be target for debug build of 
> qemu-dm. So please pick a better name. :-)
> 
> Also the qemu-dm.debug has ended up getting deleted, so please send us 
> a patch that reincludes the script with a better name, and adds the 
> install line to the Makefile.

I changed my mind, since qemu-dm.debug came back to life (due to a
merge bug in mercurial). This being the case, I've applied your
original patch, so qemu-dm.debug now gets installed by 'make install'.

I guess it's an okay name really. I can't think of a much better
one. :-) 

 -- Keir

Question about network-route

[wei huang]

Hi,

I saw in file /etc/xen/xend-config.sxp that I also have the choice to use
network-route to configure the network. I have troubles using veth0 so I
would like to give it a shot.

I saw some of instruction given in the mailing list:
http://lists.xensource.com/archives/html/xen-devel/2005-01/msg00368.html

I strictly follow it: modify the xend-config.sxp, configuration script and
start domu. (I didn't change the network-route and vif-route scripts
though)

But it seems that DomU is still trying to get ip from dhcp. It stops at
determine eth0 ip address for quite a long time and quits with fail.
Do I have to change something at /etc/sysconfig/network-script/ifcfg-eth0
in my domU disk image? If so, I guess it should not be booted with dhcp.
But what should my static ip, netmask, default gateway be?

Here I tried to change the static ip to "1.2.3.4" (what ever I specify in
the script) and mask to be 255.255.255.255 but leave the gateway blank.
Now DomU got its ip during boot time cannot connect outside.

I check dom0's route table after domU boots, it seems that 1.2.3.4 is
there:
Kernel IP routing table
tination     Gateway         Genmask         Flags Metric Ref    Use Iface
1.2.3.4         *               255.255.255.255 UH    0      0      0 vif1.0
9.2.72.0        *               255.255.255.128 U     0      0      0 eth0
169.254.0.0     *               255.255.0.0     U     0      0      0 eth0
default         lab001.watson.i 0.0.0.0         UG    0      0      0 eth0

And DomU's routing table:
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
169.254.0.0     *               255.255.0.0     U     0      0        0 eth0
default         *               0.0.0.0         U     0      0        0 eth0

Dom0 can ping 1.2.3.4 but cannot ssh. DomU cannot access outside, even use
ping.

Am I miss something here? I really got stuck here so any suggestions will
be helpful.

Thank you very much!

Regards,
Wei Huang