Hi everyone, I´m new to Xen and I stuck in a problem which I´m not able to solve. When I try to start an instance on My Debian Lenny, it get´s immediately canceled and I can see the following output in the xend-debug.log: (all the other logs are not changed) Traceback (most recent call last): File "/usr/lib/xen-3.2-1/lib/python/xen/web/httpserver.py", line 140, in process resource = self.getResource() File "/usr/lib/xen-3.2-1/lib/python/xen/web/httpserver.py", line 172, in getResource return self.getServer().getResource(self) File "/usr/lib/xen-3.2-1/lib/python/xen/web/httpserver.py", line 351, in getResource return self.root.getRequestResource(req) File "/usr/lib/xen-3.2-1/lib/python/xen/web/resource.py", line 39, in getRequestResource return findResource(self, req) File "/usr/lib/xen-3.2-1/lib/python/xen/web/resource.py", line 26, in findResource next = resource.getPathResource(pathElement, request) File "/usr/lib/xen-3.2-1/lib/python/xen/web/resource.py", line 49, in getPathResource val = self.getChild(path, request) File "/usr/lib/xen-3.2-1/lib/python/xen/web/SrvDir.py", line 71, in getChild val = self.get(x) File "/usr/lib/xen-3.2-1/lib/python/xen/xend/server/SrvDomainDir.py", line 52, in get return self.domain(x) File "/usr/lib/xen-3.2-1/lib/python/xen/xend/server/SrvDomainDir.py", line 44, in domain dom = self.xd.domain_lookup(x) File "/usr/lib/xen-3.2-1/lib/python/xen/xend/XendDomain.py", line 523, in domain_lookup raise XendInvalidDomain(str(domid)) XendInvalidDomain: <Fault 3: ''i-443D0865''> Anyone has an idea and can maybe help me? Thanks! _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Dear list,
I have a problem connecting to my domU instance from the network.
My domU instance is running on a node and the bridge is set up
node0:~# virsh list
Id Name State
----------------------------------
0 Domain-0 running
1 i-4BBF088C idle
node0:~# brctl show
bridge name bridge id STP enabled interfaces
eth0 8000.20cf30c34407 no peth0
vif1.0
The dom0 has the IP address 192.168.0.2 and the domU gets 192.168.0.4.
node0:~# ifconfig
eth0 Link encap:Ethernet Hardware Adresse 20:cf:30:c3:44:07
inet Adresse:192.168.0.2 Bcast:192.168.0.255
Maske:255.255.255.0
inet6-Adresse: fe80::22cf:30ff:fec3:4407/64
Gültigkeitsbereich:Verbindung
UP BROADCAST RUNNING MULTICAST MTU:1500 Metrik:1
RX packets:9642 errors:0 dropped:0 overruns:0 frame:0
TX packets:8484 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:0
RX bytes:2701535 (2.5 MiB) TX bytes:3415253 (3.2 MiB)
lo Link encap:Lokale Schleife
inet Adresse:127.0.0.1 Maske:255.0.0.0
inet6-Adresse: ::1/128 Gültigkeitsbereich:Maschine
UP LOOPBACK RUNNING MTU:16436 Metrik:1
RX packets:6032 errors:0 dropped:0 overruns:0 frame:0
TX packets:6032 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:0
RX bytes:1010387 (986.7 KiB) TX bytes:1010387 (986.7 KiB)
peth0 Link encap:Ethernet Hardware Adresse 20:cf:30:c3:44:07
inet Adresse:192.168.0.4 Bcast:192.168.0.255
Maske:255.255.255.0
inet6-Adresse: fe80::22cf:30ff:fec3:4407/64
Gültigkeitsbereich:Verbindung
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metrik:1
RX packets:9642 errors:0 dropped:0 overruns:0 frame:0
TX packets:8596 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:1000
RX bytes:2839977 (2.7 MiB) TX bytes:3433899 (3.2 MiB)
Interrupt:17 Basisadresse:0xc000
vif1.0 Link encap:Ethernet Hardware Adresse fe:ff:ff:ff:ff:ff
inet6-Adresse: fe80::fcff:ffff:feff:ffff/64
Gültigkeitsbereich:Verbindung
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metrik:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:278 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:32
RX bytes:0 (0.0 B) TX bytes:88958 (86.8 KiB)
When I ping or try to connect to the instance on 192.168.0.4 from a
cloud manager which is
a seperate pc and which has ip 192.168.0.1, I´m always arriving at the
192.168.0.2 dom0,
which means the bridge is not working correctly, i think.
Same happens when I try to connect from dom0 to domU.
Anyone has an idea what to do or which files to check?
Greetings
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users