configuration problem

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

configuration problem

Stephan Böni
My domU does not start. The xend.log file reports:
[2005-10-14 17:58:20 xend] DEBUG (blkif:24) exception looking up device number for hda1: [Errno 2] No such file or directory: '/dev/hda1'
 
In my configuration file i've defined:
disk = [ 'phy:xenvg/inhouse-root,hda1,w' ]
 
But the logical volume exists:
# lvdisplay /dev/xenvg/inhouse-root
  --- Logical volume ---
  LV Name                /dev/xenvg/inhouse-root
  VG Name                xenvg
  LV UUID                Sdw1tM-wzEl-m1Ae-xpYK-q4le-E8DV-pImOzU
  LV Write Access        read/write
  LV Status              available
  # open                 0
  LV Size                1,00 GB
  Current LE             32
  Segments               1
  Allocation             inherit
  Read ahead sectors     0
  Block device           253:17
 
And i can mount it in dom0 without any problems. It's a reiser filesystem, which i've filled up with all suff needed for booting as i know from Xen2. Is there a difference to Xen3 that i should to know?
 
Stephan
 
 
 

_______________________________________________
Xen-devel mailing list
[hidden email]
http://lists.xensource.com/xen-devel
Reply | Threaded
Open this post in threaded view
|

Re: configuration problem

Stephan Böni
Ha, that was easy: touch /etc/hda1
 
But now the next error makes crashing my domU:
 
[2005-10-14 18:25:00 xend] ERROR (XendDomainInfo:443) ['vif', ['mac', 'aa:00:00:00:00:11'], ['bridge', 'xenbr0']]
 
 
# brctl show
bridge name     bridge id               STP enabled     interfaces
xenbr0          8000.feffffffffff       no              vif0.0
                                                        peth0
# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:14:5E:0A:53:04
          inet addr:192.168.1.51  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::214:5eff:fe0a:5304/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:5330 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4609 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:467911 (456.9 Kb)  TX bytes:641690 (626.6 Kb)
 
lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
 
peth0     Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING NOARP MULTICAST  MTU:1500  Metric:1
          RX packets:5324 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4609 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:501107 (489.3 Kb)  TX bytes:661136 (645.6 Kb)
          Interrupt:16
 
vif0.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:4609 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5331 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:641690 (626.6 Kb)  TX bytes:468001 (457.0 Kb)
 
xenbr0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1054 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:134510 (131.3 Kb)  TX bytes:378 (378.0 b)
 
 
What should i do now?
 
Stephan
 
-----Ursprüngliche Nachricht-----
Von: Stephan Böni
Gesendet: Freitag, 14. Oktober 2005 18:13
An: xen-devel; [hidden email]
Betreff: [Xen-devel] configuration problem

My domU does not start. The xend.log file reports:
[2005-10-14 17:58:20 xend] DEBUG (blkif:24) exception looking up device number for hda1: [Errno 2] No such file or directory: '/dev/hda1'
 
In my configuration file i've defined:
disk = [ 'phy:xenvg/inhouse-root,hda1,w' ]
 
But the logical volume exists:
# lvdisplay /dev/xenvg/inhouse-root
  --- Logical volume ---
  LV Name                /dev/xenvg/inhouse-root
  VG Name                xenvg
  LV UUID                Sdw1tM-wzEl-m1Ae-xpYK-q4le-E8DV-pImOzU
  LV Write Access        read/write
  LV Status              available
  # open                 0
  LV Size                1,00 GB
  Current LE             32
  Segments               1
  Allocation             inherit
  Read ahead sectors     0
  Block device           253:17
 
And i can mount it in dom0 without any problems. It's a reiser filesystem, which i've filled up with all suff needed for booting as i know from Xen2. Is there a difference to Xen3 that i should to know?
 
Stephan
 
 
 

_______________________________________________
Xen-devel mailing list
[hidden email]
http://lists.xensource.com/xen-devel