[best viewed with fixed-width font]
Hello,
I''am installing my first Xen on a server.
Using online docs, wiki, reading this list... I installed a debian sarge
+ Xen3, and finally have dom0 and one domU (minimal - a dbootstrap) running.
My laboratory has a public 129.175.252.0/21 net (call it N1), and for
domU I use a private 192.168.21.0 net (call it N2). Administrators of N1
have setup routing + gateway, and N1 <=> N2 pinging works in both
directions.
Now, for domU installation and management, I need an Internet access
(dbootstrap is really minimal). As I use private network N2, I''m trying
to setup a second interface eth1 on domU, with corresponding NAT on
dom0, used for external Internet access.
<== domU ==><================ dom0 =======================>
(meodie) (psaume)
eth0--------->vif1.0-----+ peth0
| |
+----psbridge--------------eth0
| |
vif0.0 |
|
|
eth1--------->vif1.1--------------(NAT)---------------+
[ For my understanding, what are peth0 / vif0.0 usage, and what
pseudo-interface is connected to dom0 eth0 ? ]
Now, it seem I have routing problems or Xen understanding problems...
Here are my configuration files/tables and final result:
On dom0 (psaume)
===============psaume:~# cat /etc/xen/xend-config.sxp
------------------------
...
(network-script ''network-bridge bridge=psbridge
netdev=eth0'')
(vif-script vif-bridge)
...
psaume:~# cat /etc/xen/melodie.cfg
--------------------
name="melodie"
memory=256
kernel="/boot/xen-linux-2.6.12.6-xen-domu"
vif = [''mac=AA:00:00:00:44:01, script=vif-bridge,
bridge=psbridge'',
''mac=AA:00:00:00:44:02, script=vif-nat'']
hostname = ''melodie''
disk=[''phy:stockagevg/meloswap,sda1,w'',
''phy:stockagevg/melosys,sda2,w'',
''phy:stockagevg/melodata,sda3,w'']
root="/dev/sda2 ro"
psaume:~# cat /proc/sys/net/ipv4/ip_forward
---------------------------------
1
psaume:~# ifconfig
--------
eth0 Lien encap:Ethernet HWaddr 00:13:D3:32:77:D4
inet adr:129.175.157.73 Bcast:129.175.159.255
Masque:255.255.248.0
adr inet6: fe80::213:d3ff:fe32:77d4/64 Scope:Lien
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:41984 errors:0 dropped:0 overruns:0 frame:0
TX packets:1507 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:0
RX bytes:3874972 (3.6 MiB) TX bytes:172931 (168.8 KiB)
lo [removed in post]
peth0 Lien encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
adr inet6: fe80::fcff:ffff:feff:ffff/64 Scope:Lien
UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:42209 errors:0 dropped:0 overruns:0 frame:0
TX packets:1567 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:1000
RX bytes:4418794 (4.2 MiB) TX bytes:188320 (183.9 KiB)
Adresse de base:0x3000 Mémoire:d0120000-d0140000
psbridge Lien encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
adr inet6: fe80::200:ff:fe00:0/64 Scope:Lien
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:39945 errors:0 dropped:0 overruns:0 frame:0
TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:0
RX bytes:3133556 (2.9 MiB) TX bytes:378 (378.0 b)
vif0.0 Lien encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
adr inet6: fe80::fcff:ffff:feff:ffff/64 Scope:Lien
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1507 errors:0 dropped:0 overruns:0 frame:0
TX packets:41985 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:0
RX bytes:172931 (168.8 KiB) TX bytes:3875062 (3.6 MiB)
vif1.0 Lien encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
adr inet6: fe80::fcff:ffff:feff:ffff/64 Scope:Lien
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:54 errors:0 dropped:0 overruns:0 frame:0
TX packets:26330 errors:0 dropped:1701 overruns:0 carrier:0
collisions:0 lg file transmission:0
RX bytes:3646 (3.5 KiB) TX bytes:2397969 (2.2 MiB)
vif1.1 Lien encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet adr:10.0.1.129 Bcast:0.0.0.0 Masque:255.255.255.255
adr inet6: fe80::fcff:ffff:feff:ffff/64 Scope:Lien
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:14 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:5 overruns:0 carrier:0
collisions:0 lg file transmission:0
RX bytes:666 (666.0 b) TX bytes:0 (0.0 b)
[note Xen NAT script has given 10.0.1.129 address to vif1.1]
psaume:~# iptables -L
-----------
Chain INPUT (policy ACCEPT) target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-in
vif1.0
ACCEPT all -- 10.0.0.0/16 anywhere PHYSDEV match --physdev-in
vif1.1
ACCEPT udp -- anywhere anywhere PHYSDEV match --physdev-in
vif1.1 udp spt:bootpc dpt:bootps
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
[there seem to be rules for vif1.1, is this NAT]
On domU (melodie)
================
melodie:~# cat /etc/network/interfaces
---------------------------
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static
address 192.168.21.10
netmask 255.255.255.0
network 192.168.21.0
gateway 192.168.21.254
dns-search limsi.fr
dns-nameservers 129.175.152.136 129.175.152.129
auto eth1
iface eth1 inet static
address 192.168.21.11
netmask 255.255.255.0
network 192.168.21.0
up route add -host 192.168.21.254 eth0
up route add -net 129.175.152.0 netmask 255.255.248.0 eth0
[ the two up routes make N1 accessible from domU ]
melodie:~# ifconfig
--------
eth0 Link encap:Ethernet HWaddr AA:00:00:00:44:01
inet addr:192.168.21.10 Bcast:192.168.21.255
Mask:255.255.255.0
inet6 addr: fe80::a800:ff:fe00:4401/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:29896 errors:0 dropped:0 overruns:0 frame:0
TX packets:58 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2758293 (2.6 MiB) TX bytes:3774 (3.6 KiB)
eth1 Link encap:Ethernet HWaddr AA:00:00:00:44:02
inet addr:192.168.21.11 Bcast:192.168.21.255
Mask:255.255.255.0
inet6 addr: fe80::a800:ff:fe00:4402/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:794 (794.0 b)
lo [removed for post]
melodie:~# route -n
--------
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.21.254 0.0.0.0 255.255.255.255 UH 0 0 0 eth0
192.168.21.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
192.168.21.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
129.175.152.0 0.0.0.0 255.255.248.0 U 0 0 0 eth0
0.0.0.0 192.168.21.254 0.0.0.0 UG 0 0 0 eth0
[ Now, I setup a route to the default laboratory gateway. ]
melodie:~# route add 129.175.152.252 eth1
[ And make this gateway the default route for unkown ones. ]
melodie:~# route add default gw 129.175.152.252
[ Nice, but still fail (this works under dom0, with same target). ]
melodie:~# apt-get update
Err ftp://debian.ens-cachan.fr stable/main Packages
Could not connect to debian.ens-cachan.fr:21 (138.231.176.11). -
connect (113 No route to host)
What am-I missing (note pinging N1<==>N2 still work) ?
Thanks a lot.
Laurent.
--
Laurent POINTAL
CNRS-LIMSI dépt. CHM, groupes AMI et PS
Courriel: laurent.pointal@limsi.fr (prof)
laurent.pointal@laposte.net (perso)
Ouebe: http://www.limsi.fr/Individu/pointal/
Tél. 01 69 85 81 06 (prof)
Fax. 01 69 85 80 88
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
I tried to remove default route using eth0 too:
route del default gw 192.168.21.254
Which make following routing table:
melodie:~# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
129.175.152.252 0.0.0.0 255.255.255.255 UH 0 0 0 eth1
192.168.21.254 0.0.0.0 255.255.255.255 UH 0 0 0 eth0
192.168.21.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
192.168.21.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
129.175.152.0 0.0.0.0 255.255.248.0 U 0 0 0 eth0
0.0.0.0 129.175.152.252 0.0.0.0 UG 0 0 0 eth1
I still can ping domU<==>dom0, but can''t go to the Net.
--
Laurent POINTAL
CNRS-LIMSI dépt. CHM, groupes AMI et PS
Courriel: laurent.pointal@limsi.fr (prof)
laurent.pointal@laposte.net (perso)
Ouebe: http://www.limsi.fr/Individu/pointal/
Tél. 01 69 85 81 06 (prof)
Fax. 01 69 85 80 88
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Anoher test...
On dom0:
=======psaume:~# tcpdump -i vif1.1
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on vif1.1, link-type EN10MB (Ethernet), capture size 96 bytes
10:34:03.872301 arp who-has 129.175.152.252 tell 192.168.21.11
10:34:04.872208 arp who-has 129.175.152.252 tell 192.168.21.11
10:34:05.872141 arp who-has 129.175.152.252 tell 192.168.21.11
10:34:06.882084 arp who-has 129.175.152.252 tell 192.168.21.11
10:34:07.882011 arp who-has 129.175.152.252 tell 192.168.21.11
10:34:08.881942 arp who-has 129.175.152.252 tell 192.168.21.11
On domU:
=======melodie:~# apt-get update
Err ftp://debian.ens-cachan.fr stable/main Packages
Could not connect to debian.ens-cachan.fr:21 (138.231.176.11). -
connect (113 No route to host)
0% [Connecting to http.us.debian.org (64.50.238.52)] [Connecting to
security.deb
So can''t go throught vif1.1 to join my N1 public network, try another
route...
On domU:
=======melodie:~# route del default gw 129.175.152.252
melodie:~# route add default gw 192.168.21.11
melodie:~# apt-get update
Err ftp://debian.ens-cachan.fr stable/main Packages
Could not connect to debian.ens-cachan.fr:21 (138.231.176.11). -
connect (113 No route to host)
0% [Connecting to debian.ens-cachan.fr (138.231.176.11)] [Connecting to
http.us.
Corresponding to dom0:
=====================psaume:~# tcpdump -i vif1.1
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on vif1.1, link-type EN10MB (Ethernet), capture size 96 bytes
10:36:58.400877 arp who-has webb.ens-cachan.fr tell 192.168.21.11
10:36:58.407876 arp who-has debian-mirror.cs.umn.edu tell 192.168.21.11
10:36:58.654101 arp who-has mirrors1.kernel.org tell 192.168.21.11
10:36:59.400794 arp who-has webb.ens-cachan.fr tell 192.168.21.11
10:36:59.400794 arp who-has debian-mirror.cs.umn.edu tell 192.168.21.11
10:36:59.400795 arp who-has mirrors1.kernel.org tell 192.168.21.11
10:37:00.400699 arp who-has webb.ens-cachan.fr tell 192.168.21.11
10:37:00.400700 arp who-has debian-mirror.cs.umn.edu tell 192.168.21.11
10:37:00.400715 arp who-has mirrors1.kernel.org tell 192.168.21.11
10:37:01.410641 arp who-has webb.ens-cachan.fr tell 192.168.21.11
10:37:01.410642 arp who-has klecker.debian.org tell 192.168.21.11
10:37:01.410642 arp who-has rama.progeny.com tell 192.168.21.11
10:37:02.410574 arp who-has webb.ens-cachan.fr tell 192.168.21.11
10:37:02.410574 arp who-has klecker.debian.org tell 192.168.21.11
10:37:02.410575 arp who-has rama.progeny.com tell 192.168.21.11
10:37:03.410506 arp who-has webb.ens-cachan.fr tell 192.168.21.11
10:37:03.410507 arp who-has klecker.debian.org tell 192.168.21.11
10:37:03.410508 arp who-has rama.progeny.com tell 192.168.21.11
10:37:13.119928 aa:00:00:00:44:02 > Broadcast, ethertype Unknown
(0x88a2), length 32:
0x0000: 1000 ffff ff01 0000 0000 0000 0000 0000 ................
0x0010: 0000 ..
10:38:13.115997 aa:00:00:00:44:02 > Broadcast, ethertype Unknown
(0x88a2), length 32:
0x0000: 1000 ffff ff01 0000 0000 0000 0000 0000 ................
0x0010: 0000 ..
20 packets captured
20 packets received by filter
0 packets dropped by kernel
--
Laurent POINTAL
CNRS-LIMSI dépt. CHM, groupes AMI et PS
Courriel: laurent.pointal@limsi.fr (prof)
laurent.pointal@laposte.net (perso)
Ouebe: http://www.limsi.fr/Individu/pointal/
Tél. 01 69 85 81 06 (prof)
Fax. 01 69 85 80 88
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Yet another test...
On domU:
=======
melodie:~# route del default gw 192.168.21.11
melodie:~# route add default eth1
melodie:~# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
129.175.152.252 0.0.0.0 255.255.255.255 UH 0 0 0 eth1
192.168.21.254 0.0.0.0 255.255.255.255 UH 0 0 0 eth0
192.168.21.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
192.168.21.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
129.175.152.0 0.0.0.0 255.255.248.0 U 0 0 0 eth0
0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 eth1
melodie:~# apt-get update
Err ftp://debian.ens-cachan.fr stable/main Packages
Could not connect to debian.ens-cachan.fr:21 (138.231.176.11). -
connect (113 No route to host)
Err ftp://debian.ens-cachan.fr stable/main Release
Could not connect to debian.ens-cachan.fr:21 (138.231.176.11). -
connect (113 No route to host)
Err http://security.debian.org stable/updates/main Packages
Could not connect to security.debian.org:80 (128.101.80.133). -
connect (113 No route to host) [IP: 128.101.80.133 80]
Err ftp://debian.ens-cachan.fr stable/main Sources
Could not connect to debian.ens-cachan.fr:21 (138.231.176.11). -
connect (113 No route to host)
Err ftp://debian.ens-cachan.fr stable/main Release
Could not connect to debian.ens-cachan.fr:21 (138.231.176.11). -
connect (113 No route to host)
Err http://http.us.debian.org stable/main Packages
Could not connect to http.us.debian.org:80 (64.50.238.52). - connect
(113 No route to host) [IP: 64.50.238.52 80]
0% [Connecting to http.us.debian.org (128.101.80.133)] [Connecting to
security.d
And corresponding tcpdump on dom0:
=================================
psaume:~# tcpdump -i vif1.1
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on vif1.1, link-type EN10MB (Ethernet), capture size 96 bytes
11:00:36.147902 arp who-has klecker.debian.org tell 192.168.21.11
11:00:36.155867 arp who-has debian-mirror.cs.umn.edu tell 192.168.21.11
11:00:36.156858 arp who-has webb.ens-cachan.fr tell 192.168.21.11
11:00:37.147778 arp who-has klecker.debian.org tell 192.168.21.11
11:00:37.147779 arp who-has debian-mirror.cs.umn.edu tell 192.168.21.11
11:00:37.147795 arp who-has webb.ens-cachan.fr tell 192.168.21.11
11:00:38.147716 arp who-has klecker.debian.org tell 192.168.21.11
11:00:38.147716 arp who-has debian-mirror.cs.umn.edu tell 192.168.21.11
11:00:38.147717 arp who-has webb.ens-cachan.fr tell 192.168.21.11
11:00:39.157652 arp who-has tartini.debian.org tell 192.168.21.11
11:00:39.157653 arp who-has mirrors1.kernel.org tell 192.168.21.11
11:00:39.157672 arp who-has webb.ens-cachan.fr tell 192.168.21.11
11:00:40.157584 arp who-has tartini.debian.org tell 192.168.21.11
11:00:40.157585 arp who-has mirrors1.kernel.org tell 192.168.21.11
11:00:40.157601 arp who-has webb.ens-cachan.fr tell 192.168.21.11
11:00:41.157517 arp who-has tartini.debian.org tell 192.168.21.11
11:00:41.157518 arp who-has mirrors1.kernel.org tell 192.168.21.11
11:00:41.157535 arp who-has webb.ens-cachan.fr tell 192.168.21.11
11:00:42.167507 arp who-has debian-mirror.cs.umn.edu tell 192.168.21.11
11:00:42.167508 arp who-has rama.progeny.com tell 192.168.21.11
11:00:42.167509 arp who-has webb.ens-cachan.fr tell 192.168.21.11
11:00:43.167388 arp who-has debian-mirror.cs.umn.edu tell 192.168.21.11
11:00:43.167389 arp who-has rama.progeny.com tell 192.168.21.11
11:00:43.167389 arp who-has webb.ens-cachan.fr tell 192.168.21.11
11:00:44.167322 arp who-has debian-mirror.cs.umn.edu tell 192.168.21.11
11:00:44.167322 arp who-has rama.progeny.com tell 192.168.21.11
11:00:44.167323 arp who-has webb.ens-cachan.fr tell 192.168.21.11
Why doesn''t packets start going throught domU eth1 ???
--
Laurent POINTAL
CNRS-LIMSI dépt. CHM, groupes AMI et PS
Courriel: laurent.pointal@limsi.fr (prof)
laurent.pointal@laposte.net (perso)
Ouebe: http://www.limsi.fr/Individu/pointal/
Tél. 01 69 85 81 06 (prof)
Fax. 01 69 85 80 88
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
I am trying to start a DomU using yast2 on Suse-10 which autogenerates
this file and starts it up:
disk = [ ''file:/var/lib/xen/images/domain1/hda,hda,w'' ]
memory = 256
kernel = "/var/lib/xen/images/domain1/vmlinuz-2.6.13-15-xen"
ramdisk = "/var/lib/xen/images/domain1/inst-initrd"
name = "domain1"
dhcp = "dhcp"
extra = ""
root = ""
..............after few startup messages ,the kernel hangs as you can
see below
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Initializing Cryptographic API
vesafb: abort, cannot ioremap video memory 0x0 @ 0x0
vesafb: probe of vesafb.0 failed with error -5
PNP: No PS/2 controller found. Probing ports directly.
i8042.c: No controller found.
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
RAMDISK driver initialized: 16 RAM disks of 64000K size 1024 blocksize
loop: loaded (max 8 devices)
Xen virtual console successfully installed as tty1
Event-channel device installed.
Neither TPM-BE Domain nor INIT domain!
xen_blk: Initialising virtual block device driver
Registering block device major 3
hda:
------------------------------------------hangs here
xend.log last few lines are:
linux:/etc/xen # tail -f /var/log/xend.log
[2006-02-10 15:35:50 xend] DEBUG (image:261) flags = 0
[2006-02-10 15:35:50 xend] DEBUG (image:262) vcpus = 1
[2006-02-10 15:35:51 xend] INFO (XendRoot:141) EVENT> xend.domain.create
[''domain1'', 3]
[2006-02-10 15:35:51 xend] INFO (xsobj:326) DBMap>introduceDomain> 3
129175 <EventChannel dom1:0:16
dom2:3:1> /domain/adada41b-22b1-4ac9-b095-c338c2470cb7
[2006-02-10 15:35:51 xend] DEBUG (XendDomainInfo:698) writing key
availability=online to path /cpu/0 in store
[2006-02-10 15:35:51 xend] WARNING (XendDomainInfo:1100) Unknown config
field boot
[2006-02-10 15:35:51 xend] WARNING (XendDomainInfo:1100) Unknown config
field display
[2006-02-10 15:35:51 xend] ERROR (process:37) [block-file] ioctl:
LOOP_SET_FD: Device or resource busy
[2006-02-10 15:35:51 xend] ERROR (XendDomainInfo:443) [''vif'',
[''mac'',
''aa:00:00:4a:57:ab'']]
[2006-02-10 15:35:51 xend] INFO (XendRoot:141) EVENT>
xend.domain.unpause [''domain1'', 3]
----------------------------------------------------
xend-debug.log last few lines are:
linux:/etc/xen # tail -f /var/log/xend-debug.log
Blkctl.block(''unbind'',
devdb[''type''].getData(),
File "/usr/lib/python2.4/site-packages/xen/xend/xenstore/xsobj.py",
line 425, in __getitem__
v = self.readChildDB(k)
File "/usr/lib/python2.4/site-packages/xen/xend/xenstore/xsobj.py",
line 518, in readChildDB
if self.__db__ and (k in self.__db__.ls()):
File "/usr/lib/python2.4/site-packages/xen/xend/xenstore/xsnode.py",
line 462, in ls
return self.store.ls(self.path)
File "/usr/lib/python2.4/site-packages/xen/xend/xenstore/xsnode.py",
line 217, in ls
return self.getxs().ls(path)
RuntimeError: (2, ''No such file or directory'')
**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely for
the use of the addressee(s). If you are not the intended recipient, please
notify the sender by e-mail and delete the original message. Further, you are
not to copy, disclose, or distribute this e-mail or its contents to any other
person and any such actions are unlawful. This e-mail may contain viruses.
Infosys has taken every reasonable precaution to minimize this risk, but is not
liable for any damage you may sustain as a result of any virus in this e-mail.
You should carry out your own virus checks before opening the e-mail or
attachment. Infosys reserves the right to monitor and review the content of all
messages sent to or from this e-mail address. Messages sent to or from this
e-mail address may be stored on the Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Hi Digvijoy, On Feb 10, 2006 08:11 AM, Digvijoy Chatterjee <digvijoy_chatterjee@infosys.com> wrote:> > I am trying to start a DomU using yast2 on Suse-10 which autogenerates > this file and starts it up: > > disk = [ ''file:/var/lib/xen/images/domain1/hda,hda,w'' ] > memory = 256 > kernel = "/var/lib/xen/images/domain1/vmlinuz-2.6.13-15-xen" > ramdisk = "/var/lib/xen/images/domain1/inst-initrd" > name = "domain1" > dhcp = "dhcp" > extra = "" > root = ""Edit the file above and make the following changes: disk = [ ''file:/var/lib/xen/images/domain1/hda,xvda,w'' ] extra = "TERM=xterm textmode=1 install=nfs://servername/path_to_source_dir" restart = "never" Then open an xterm and type: xm create -c domain1 You should see linuxrc start inside the xterm. When the instalation finishes you should change the line ramdisk = "/var/lib/xen/images/domain1/inst-initrd" to contain the initrd for a running system instead of the installation one. Hopefully you can safely use "/boot/initrd-xen" Also you''ll need to change the root line to: root = "/dev/xvda1" (or xvda2, depending in how partitioning was performed during install) And finaly: restart = "onreboot" Now start domain1 again from an xterm and you should be able to finish the installation. Another option is to use the option "Installation into directory" from YaST and then use that directory as the image for xen. rgrds, Braulio Gergull _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Digvijoy, On Feb 10, 2006 08:11 AM, Digvijoy Chatterjee <digvijoy_chatterjee@infosys.com> wrote:> > I am trying to start a DomU using yast2 on Suse-10 which autogenerates > this file and starts it up: > > disk = [ ''file:/var/lib/xen/images/domain1/hda,hda,w'' ] > memory = 256 > kernel = "/var/lib/xen/images/domain1/vmlinuz-2.6.13-15-xen" > ramdisk = "/var/lib/xen/images/domain1/inst-initrd" > name = "domain1" > dhcp = "dhcp" > extra = "" > root = ""Edit the file above and make the following changes: disk = [ ''file:/var/lib/xen/images/domain1/hda,xvda,w'' ] extra = "TERM=xterm textmode=1 install=nfs://servername/path_to_source_dir" restart = "never" Then open an xterm and type: xm create -c domain1 You should see linuxrc start inside the xterm. When the instalation finishes you should change the line ramdisk = "/var/lib/xen/images/domain1/inst-initrd" to contain the initrd for a running system instead of the installation one. Hopefully you can safely use "/boot/initrd-xen" Also you''ll need to change the root line to: root = "/dev/xvda1" (or xvda2, depending in how partitioning was performed during install) And finaly: restart = "onreboot" Now start domain1 again from an xterm and you should be able to finish the installation. Another option is to use the option "Installation into directory" from YaST and then use that directory as the image for xen. rgrds, Braulio Gergull _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I observed the same thing on SLES 10 Beta1. On Fri, 2006-02-10 at 15:41 +0530, Digvijoy Chatterjee wrote:> I am trying to start a DomU using yast2 on Suse-10 which autogenerates > this file and starts it up: > > disk = [ ''file:/var/lib/xen/images/domain1/hda,hda,w'' ] > memory = 256 > kernel = "/var/lib/xen/images/domain1/vmlinuz-2.6.13-15-xen" > ramdisk = "/var/lib/xen/images/domain1/inst-initrd" > name = "domain1" > dhcp = "dhcp" > extra = "" > root = "" > > > ..............after few startup messages ,the kernel hangs as you can > see below > Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) > Initializing Cryptographic API > vesafb: abort, cannot ioremap video memory 0x0 @ 0x0 > vesafb: probe of vesafb.0 failed with error -5 > PNP: No PS/2 controller found. Probing ports directly. > i8042.c: No controller found. > io scheduler noop registered > io scheduler anticipatory registered > io scheduler deadline registered > io scheduler cfq registered > RAMDISK driver initialized: 16 RAM disks of 64000K size 1024 blocksize > loop: loaded (max 8 devices) > Xen virtual console successfully installed as tty1 > Event-channel device installed. > Neither TPM-BE Domain nor INIT domain! > xen_blk: Initialising virtual block device driver > Registering block device major 3 > hda: > ------------------------------------------hangs here > xend.log last few lines are: > > linux:/etc/xen # tail -f /var/log/xend.log > [2006-02-10 15:35:50 xend] DEBUG (image:261) flags = 0 > [2006-02-10 15:35:50 xend] DEBUG (image:262) vcpus = 1 > [2006-02-10 15:35:51 xend] INFO (XendRoot:141) EVENT> xend.domain.create > [''domain1'', 3] > [2006-02-10 15:35:51 xend] INFO (xsobj:326) DBMap>introduceDomain> 3 > 129175 <EventChannel dom1:0:16 > dom2:3:1> /domain/adada41b-22b1-4ac9-b095-c338c2470cb7 > [2006-02-10 15:35:51 xend] DEBUG (XendDomainInfo:698) writing key > availability=online to path /cpu/0 in store > [2006-02-10 15:35:51 xend] WARNING (XendDomainInfo:1100) Unknown config > field boot > [2006-02-10 15:35:51 xend] WARNING (XendDomainInfo:1100) Unknown config > field display > [2006-02-10 15:35:51 xend] ERROR (process:37) [block-file] ioctl: > LOOP_SET_FD: Device or resource busy > [2006-02-10 15:35:51 xend] ERROR (XendDomainInfo:443) [''vif'', [''mac'', > ''aa:00:00:4a:57:ab'']] > [2006-02-10 15:35:51 xend] INFO (XendRoot:141) EVENT> > xend.domain.unpause [''domain1'', 3] > > ---------------------------------------------------- > xend-debug.log last few lines are: > > linux:/etc/xen # tail -f /var/log/xend-debug.log > Blkctl.block(''unbind'', devdb[''type''].getData(), > File "/usr/lib/python2.4/site-packages/xen/xend/xenstore/xsobj.py", > line 425, in __getitem__ > v = self.readChildDB(k) > File "/usr/lib/python2.4/site-packages/xen/xend/xenstore/xsobj.py", > line 518, in readChildDB > if self.__db__ and (k in self.__db__.ls()): > File "/usr/lib/python2.4/site-packages/xen/xend/xenstore/xsnode.py", > line 462, in ls > return self.store.ls(self.path) > File "/usr/lib/python2.4/site-packages/xen/xend/xenstore/xsnode.py", > line 217, in ls > return self.getxs().ls(path) > RuntimeError: (2, ''No such file or directory'') > > > > > **************** CAUTION - Disclaimer ***************** > This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely for the use of the addressee(s). If you are not the intended recipient, please notify the sender by e-mail and delete the original message. Further, you are not to copy, disclose, or distribute this e-mail or its contents to any other person and any such actions are unlawful. This e-mail may contain viruses. Infosys has taken every reasonable precaution to minimize this risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. Infosys reserves the right to monitor and review the content of all messages sent to or from this e-mail address. Messages sent to or from this e-mail address may be stored on the Infosys e-mail system. > ***INFOSYS******** End of Disclaimer ********INFOSYS*** > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >-- Regards, David F Barrera Linux Technology Center Systems and Technology Group, IBM "The wisest men follow their own direction. " Euripides _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Braulio,
Heres the new file:
disk = [ ''file:/var/lib/xen/images/domain1/hda,xvda,w'' ]
memory = 256
kernel = "/var/lib/xen/images/domain1/vmlinuz-2.6.13-15-xen"
ramdisk = "/var/lib/xen/images/domain1/inst-initrd"
name = "domain1"
dhcp = "dhcp"
extra = "TERM=xterm textmode=1
install=nfs://172.25.243.135/var/Suse-10"
restart= "never"
root = ""
i issue :
linux:~ # xm create -c domain1
---------------------------normal bootup
Initializing Cryptographic API
vesafb: abort, cannot ioremap video memory 0x0 @ 0x0
vesafb: probe of vesafb.0 failed with error -5
PNP: No PS/2 controller found. Probing ports directly.
i8042.c: No controller found.
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
RAMDISK driver initialized: 16 RAM disks of 64000K size 1024 blocksize
loop: loaded (max 8 devices)
Xen virtual console successfully installed as tty1
Event-channel device installed.
Neither TPM-BE Domain nor INIT domain!
xen_blk: Initialising virtual block device driver
Registering block device major 202
xvda:
======================hanging up
--------------------------------------------------------------
xend.log says this:linux:~ # tail -f /var/log/xend.log
[2006-02-13 12:08:33 xend] DEBUG (image:260) ramdisk
= /var/lib/xen/images/domain1/inst-initrd
[2006-02-13 12:08:33 xend] DEBUG (image:261) flags = 0
[2006-02-13 12:08:33 xend] DEBUG (image:262) vcpus = 1
[2006-02-13 12:08:34 xend] INFO (xsobj:326) DBMap>introduceDomain> 1
129175 <EventChannel dom1:0:16
dom2:1:1> /domain/e2cb5734-dbdd-4f55-a771-d4f9f897ebdc
[2006-02-13 12:08:34 xend] DEBUG (XendDomainInfo:698) writing key
availability=online to path /cpu/0 in store
[2006-02-13 12:08:34 xend] WARNING (XendDomainInfo:1100) Unknown config
field boot
[2006-02-13 12:08:34 xend] WARNING (XendDomainInfo:1100) Unknown config
field display
[2006-02-13 12:08:34 xend] DEBUG (blkif:24) exception looking up device
number for xvda: [Errno 2] No such file or directory:
''/dev/xvda''
[2006-02-13 12:08:35 xend] ERROR (XendDomainInfo:443) [''vif'',
[''mac'',
''aa:00:00:1c:54:40'']]
[2006-02-13 12:08:35 xend] INFO (XendRoot:141) EVENT>
xend.domain.unpause [''domain1'', 1]
--------------------------------------------------------------------------
xend-debug.log says
linux:~ # tail -f /var/log/xend-debug.log
info.cleanup()
File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py",
line 755, in cleanup
self.release_devices()
File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py",
line 803, in release_devices
for d in t.list("vif"):
File
"/usr/lib/python2.4/site-packages/xen/xend/xenstore/xstransact.py",
line
110, in list
ret.extend(self._list(key))
File
"/usr/lib/python2.4/site-packages/xen/xend/xenstore/xstransact.py",
line
103, in _list
return map(lambda x: key + "/" + x, xshandle().ls(path))
RuntimeError: (2, ''No such file or directory'')
I tried googling /searching mailing lists ,but couldnt figure out much
Regards
Digz
On Fri, 2006-02-10 at 15:09 -0200, Bráulio Gergull
wrote:> Hi Digvijoy,
>
> On Feb 10, 2006 08:11 AM, Digvijoy Chatterjee
> <digvijoy_chatterjee@infosys.com> wrote:
>
> >
> > I am trying to start a DomU using yast2 on Suse-10 which autogenerates
> > this file and starts it up:
> >
> > disk = [
''file:/var/lib/xen/images/domain1/hda,hda,w'' ]
> > memory = 256
> > kernel = "/var/lib/xen/images/domain1/vmlinuz-2.6.13-15-xen"
> > ramdisk = "/var/lib/xen/images/domain1/inst-initrd"
> > name = "domain1"
> > dhcp = "dhcp"
> > extra = ""
> > root = ""
>
> Edit the file above and make the following changes:
>
> disk = [ ''file:/var/lib/xen/images/domain1/hda,xvda,w'' ]
>
> extra = "TERM=xterm textmode=1
> install=nfs://servername/path_to_source_dir"
>
> restart = "never"
>
> Then open an xterm and type:
>
> xm create -c domain1
>
> You should see linuxrc start inside the xterm.
>
> When the instalation finishes you should change the line
>
> ramdisk = "/var/lib/xen/images/domain1/inst-initrd"
>
> to contain the initrd for a running system instead of the installation
> one. Hopefully you can safely use "/boot/initrd-xen"
>
> Also you''ll need to change the root line to:
>
> root = "/dev/xvda1"
>
> (or xvda2, depending in how partitioning was performed during install)
>
> And finaly:
>
> restart = "onreboot"
>
> Now start domain1 again from an xterm and you should be able to finish
> the installation.
>
> Another option is to use the option "Installation into directory"
from
> YaST and then use that directory as the image for xen.
>
> rgrds,
> Braulio Gergull
>
**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely for
the use of the addressee(s). If you are not the intended recipient, please
notify the sender by e-mail and delete the original message. Further, you are
not to copy, disclose, or distribute this e-mail or its contents to any other
person and any such actions are unlawful. This e-mail may contain viruses.
Infosys has taken every reasonable precaution to minimize this risk, but is not
liable for any damage you may sustain as a result of any virus in this e-mail.
You should carry out your own virus checks before opening the e-mail or
attachment. Infosys reserves the right to monitor and review the content of all
messages sent to or from this e-mail address. Messages sent to or from this
e-mail address may be stored on the Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Hi Digvijoy, Em Seg, 2006-02-13 às 12:12 +0530, Digvijoy Chatterjee escreveu:> Hi Braulio, > > Heres the new file: > > disk = [ ''file:/var/lib/xen/images/domain1/hda,xvda,w'' ] > memory = 256 > kernel = "/var/lib/xen/images/domain1/vmlinuz-2.6.13-15-xen" > ramdisk = "/var/lib/xen/images/domain1/inst-initrd" > name = "domain1" > dhcp = "dhcp" > extra = "TERM=xterm textmode=1 install=nfs://172.25.243.135/var/Suse-10" > restart= "never" > root = "" > > i issue : > linux:~ # xm create -c domain1 > ---------------------------normal bootup > Initializing Cryptographic API > vesafb: abort, cannot ioremap video memory 0x0 @ 0x0 > vesafb: probe of vesafb.0 failed with error -5 > PNP: No PS/2 controller found. Probing ports directly. > i8042.c: No controller found. > io scheduler noop registered > io scheduler anticipatory registered > io scheduler deadline registered > io scheduler cfq registered > RAMDISK driver initialized: 16 RAM disks of 64000K size 1024 blocksize > loop: loaded (max 8 devices) > Xen virtual console successfully installed as tty1 > Event-channel device installed. > Neither TPM-BE Domain nor INIT domain! > xen_blk: Initialising virtual block device driver > Registering block device major 202 > xvda: > ======================hanging up >The kernel is not recognizing the block-device. Maybe yast didn''t generate inst-initrd correctly. You can try the following: - Install package install-initrd; - Generate a new inst-initrd image: mkinstallinitrd inst-initrd.custom You can also choose which modules to include, "mkinstallinitrd -h" will help you. Then change the ramdisk line to the newly created inst-initrd.custom Also, there was a kernel update from SuSE last week. It corrected many bugs related to xen, besides some security fixes. You should upgrade your kernel anyway. You can use Yast online update to do it. I''m running the latest SuSE kernel and it''s working fine. rgrds, Bráulio Gergull _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users