thr3ads.net - Xen users - [Xen-users] error starting second domU [Apr 2006]

If this information is useful, please help other people find it:
Share via:

Anand Gupta

2006-Apr-19 22:03 UTC

[Xen-users] error starting second domU

xen-3.0.2-2

I already have a domU up and running in a routed configuration. When i try
to run the second domU i get the error "Error: Device 0 (vif) could not be
connected. Backend device not found."

Looking at xend.log, i found the following:

[2006-04-20 03:02:16 xend] DEBUG (blkif:24) exception looking up device
number for sda1: [Errno 2] No such file or directory:
''/dev/sda1''
[2006-04-20 03:02:16 xend] DEBUG (blkif:24) exception looking up device
number for sda2: [Errno 2] No such file or directory:
''/dev/sda2''

I checked the image, /dev/sda1 and /dev/sda2 exists and its the same image i
am using for the first domU which is working. Even though  thinking it
won''t
make a difference i created /dev/sda on the dom0 using MAKEDEV sda.
Strangely the above error dissapeared, however the domU still doesn''t
boot
up and i recieve the same error "Error: Device 0 (vif) could not be
connected. Backend device not found."

Here is my xen3 config file

kernel = "/boot/vmlinuz-2.6.16-xen-xencp"
ramdisk = "/boot/initrd-2.6.16-xen-xencp.img"
memory = 128
name = "xen3"
vif = [''mac=AA:00:00:28:98:FC, ip=y.y.y.y, vifname=vm03'']
ip="y.y.y.y"
netmask="255.255.255.240"
gateway="x.x.x.x"
extra="selinux=0"
disk
[''phy:/dev/xendisk001/xen3-fun,sda1,w'',''phy:/dev/xendisk001/xen3-fun-swap,sda2,w'']
root = "/dev/sda1 ro"


Here is the xend.log extract

[2006-04-20 03:08:03 xend.XendDomainInfo] DEBUG (XendDomainInfo:178)
XendDomainInfo.create([''vm'', [''name'',
''xen3''], [''memory'', 128],
[''vcpus'',
1], [''image'', [''linux'',
[''kernel'', ''/boot/vmlinuz-2.6.16-xen''],
[''ramdisk'',
''/boot/initrd-2.6.16-xen.img''], [''ip'',
''y.y.y.y:
1.2.3.4:x.x.x.x:255.255.255.240::eth0:off''], [''root'',
''/dev/sda1 ro''],
[''args'', ''selinux=0'']]],
[''device'', [''vbd'',
[''uname'',
''phy:/dev/xendisk001/xen3-fun''], [''dev'',
''sda1''], [''mode'', ''w'']]],
[''device'', [''vbd'',
[''uname'',
''phy:/dev/xendisk001/xen3-fun-swap''],
[''dev'',
''sda2''], [''mode'', ''w'']]],
[''device'', [''vif'', [''ip'',
''y.y.y.y''], [''mac'',
''AA:00:00:28:98:FC''], [''vifname'',
''vm03'']]]])
[2006-04-20 03:08:03 xend.XendDomainInfo] DEBUG (XendDomainInfo:284)
parseConfig: config is [''vm'', [''name'',
''xen3''], [''memory'', 128],
[''vcpus'',
1], [''image'', [''linux'',
[''kernel'', ''/boot/vmlinuz-2.6.16-xen''],
[''ramdisk'',
''/boot/initrd-2.6.16-xen.img''], [''ip'',
''y.y.y.y:
1.2.3.4:x.x.x.x:255.255.255.240::eth0:off''], [''root'',
''/dev/sda1 ro''],
[''args'', ''selinux=0'']]],
[''device'', [''vbd'',
[''uname'',
''phy:/dev/xendisk001/xen3-fun''], [''dev'',
''sda1''], [''mode'', ''w'']]],
[''device'', [''vbd'',
[''uname'',
''phy:/dev/xendisk001/xen3-fun-swap''],
[''dev'',
''sda2''], [''mode'', ''w'']]],
[''device'', [''vif'', [''ip'',
''y.y.y.y''], [''mac'',
''AA:00:00:28:98:FC''], [''vifname'',
''vm03'']]]]
[2006-04-20 03:08:03 xend.XendDomainInfo] DEBUG (XendDomainInfo:380)
parseConfig: result is {''ssidref'': None,
''uuid'': None, ''on_crash'': None,
''on_reboot'': None, ''image'':
[''linux'', [''kernel'',
''/boot/vmlinuz-2.6.16-xen''],
[''ramdisk'', ''/boot/initrd-2.6.16-xen.img''],
[''ip'', ''y.y.y.y:
1.2.3.4:x.x.x.x:255.255.255.240::eth0:off''], [''root'',
''/dev/sda1 ro''],
[''args'', ''selinux=0'']],
''on_poweroff'': None, ''cpus'': None,
''name'': ''xen3'',
''backend'': [], ''vcpus'': 1,
''cpu_weight'': None, ''vcpu_avail'': None,
''memory'':
128, ''device'': [(''vbd'',
[''vbd'', [''uname'',
''phy:/dev/xendisk001/xen3-fun''],
[''dev'', ''sda1''], [''mode'',
''w'']]), (''vbd'', [''vbd'',
[''uname'',
''phy:/dev/xendisk001/xen3-fun-swap''],
[''dev'', ''sda2''], [''mode'',
''w'']]),
(''vif'', [''vif'', [''ip'',
''y.y.y.y''], [''mac'',
''AA:00:00:28:98:FC''], [''vifname'',
''vm03'']])], ''bootloader'': None,
''cpu'': None, ''maxmem'': None}
[2006-04-20 03:08:03 xend.XendDomainInfo] DEBUG (XendDomainInfo:1164)
XendDomainInfo.construct: None 0
[2006-04-20 03:08:03 xend.XendDomainInfo] DEBUG (XendDomainInfo:1196)
XendDomainInfo.initDomain: 16 1.0
[2006-04-20 03:08:03 xend] DEBUG (balloon:126) Balloon: free 362; need 129;
done.
[2006-04-20 03:08:03 xend] INFO (image:135) buildDomain os=linux dom=16
vcpus=1
[2006-04-20 03:08:03 xend] DEBUG (image:173) dom            = 16
[2006-04-20 03:08:03 xend] DEBUG (image:174) image          = /boot/vmlinuz-
2.6.16-xen
[2006-04-20 03:08:03 xend] DEBUG (image:175) store_evtchn   = 1
[2006-04-20 03:08:03 xend] DEBUG (image:176) console_evtchn = 2
[2006-04-20 03:08:03 xend] DEBUG (image:177) cmdline        =  ip=y.y.y.y:
1.2.3.4:x.x.x.x:255.255.255.240::eth0:off root=/dev/sda1 ro selinux=0
[2006-04-20 03:08:03 xend] DEBUG (image:178) ramdisk        = /boot/initrd-
2.6.16-xen.img
[2006-04-20 03:08:03 xend] DEBUG (image:179) vcpus          = 1
[2006-04-20 03:08:03 xend] DEBUG (image:180) features       [2006-04-20 03:08:04
xend] DEBUG (DevController:103) DevController: writing
{''virtual-device'': ''2049'',
''backend-id'': ''0'',
''state'': ''1'', ''backend'':
''/local/domain/0/backend/vbd/16/2049''} to
/local/domain/16/device/vbd/2049.
[2006-04-20 03:08:04 xend] DEBUG (DevController:105) DevController: writing
{''domain'': ''xen3'',
''frontend'':
''/local/domain/16/device/vbd/2049'', ''dev'':
''sda1'', ''state'': ''1'',
''params'': ''/dev/xendisk001/xen3-fun'',
''mode'': ''w'',
''frontend-id'': ''16'',
''type'': ''phy''} to
/local/domain/0/backend/vbd/16/2049.
[2006-04-20 03:08:04 xend] DEBUG (DevController:103) DevController: writing
{''virtual-device'': ''2050'',
''backend-id'': ''0'',
''state'': ''1'', ''backend'':
''/local/domain/0/backend/vbd/16/2050''} to
/local/domain/16/device/vbd/2050.
[2006-04-20 03:08:04 xend] DEBUG (DevController:105) DevController: writing
{''domain'': ''xen3'',
''frontend'':
''/local/domain/16/device/vbd/2050'', ''dev'':
''sda2'', ''state'': ''1'',
''params'': ''/dev/xendisk001/xen3-fun-swap'',
''mode'':
''w'', ''frontend-id'': ''16'',
''type'': ''phy''} to
/local/domain/0/backend/vbd/16/2050.
[2006-04-20 03:08:04 xend] DEBUG (DevController:103) DevController: writing
{''backend-id'': ''0'', ''mac'':
''AA:00:00:28:98:FC'', ''handle'':
''0'', ''state'': ''1'',
''backend'':
''/local/domain/0/backend/vif/16/0''} to
/local/domain/16/device/vif/0.
[2006-04-20 03:08:04 xend] DEBUG (DevController:105) DevController: writing
{''domain'': ''xen3'',
''handle'': ''0'', ''script'':
''/etc/xen/scripts/vif-route2'',
''ip'': ''y.y.y.y'', ''state'':
''1'', ''frontend'':
''/local/domain/16/device/vif/0'',
''mac'': ''AA:00:00:28:98:FC'',
''vifname'': ''vm03'',
''frontend-id'': ''16''} to
/local/domain/0/backend/vif/16/0.
[2006-04-20 03:08:04 xend.XendDomainInfo] DEBUG (XendDomainInfo:671) Storing
VM details: {''ssidref'': ''0'',
''uuid'':
''fe8ba127-14ea-2e00-58b7-920b9fc78824'',
''on_reboot'': ''restart'',
''start_time'': ''1145482684.14'',
''on_poweroff'':
''destroy'', ''name'': ''xen3'',
''vcpus'': ''1'',
''vcpu_avail'': ''1'',
''memory'': ''128'',
''on_crash'': ''restart'',
''image'': "(linux (kernel /boot/vmlinuz-2.6.16-xen)
(ramdisk /boot/initrd-2.6.16-xen.img) (ip y.y.y.y:
1.2.3.4:x.x.x.x:255.255.255.240::eth0:off) (root ''/dev/sda1
ro'') (args
''selinux=0''))", ''maxmem'':
''128''}
[2006-04-20 03:08:04 xend.XendDomainInfo] DEBUG (XendDomainInfo:696) Storing
domain details: {''console/ring-ref'':
''85124'', ''console/port'':
''2'', ''name'':
''xen3'', ''console/limit'':
''1048576'', ''vm'':
''/vm/fe8ba127-14ea-2e00-58b7-920b9fc78824'',
''domid'': ''16'',
''cpu/0/availability'': ''online'',
''memory/target'': ''131072'',
''store/ring-ref'':
''85125'', ''store/port'':
''1''}
[2006-04-20 03:08:04 xend.XendDomainInfo] DEBUG (XendDomainInfo:877)
XendDomainInfo.handleShutdownWatch
[2006-04-20 03:08:04 xend] DEBUG (DevController:132) Waiting for devices
vif.
[2006-04-20 03:08:04 xend] DEBUG (DevController:138) Waiting for 0.
[2006-04-20 03:08:04 xend] DEBUG (DevController:403) hotplugStatusCallback
/local/domain/0/backend/vif/16/0/hotplug-status.
[2006-04-20 03:08:06 xend] DEBUG (DevController:403) hotplugStatusCallback
/local/domain/0/backend/vif/16/0/hotplug-status.
[2006-04-20 03:08:06 xend] DEBUG (DevController:417) hotplugStatusCallback
2.
[2006-04-20 03:08:06 xend.XendDomainInfo] DEBUG (XendDomainInfo:1327)
XendDomainInfo.destroy: domid=16
[2006-04-20 03:08:06 xend.XendDomainInfo] DEBUG (XendDomainInfo:1335)
XendDomainInfo.destroyDomain(16)


Any help on this will be appreciated.

--
regards,

Anand Gupta


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Anand Gupta

2006-Apr-19 22:24 UTC

head link

[Xen-users] Re: error starting second domU

While waiting for replies, i did a small test.

Shutdown xen1 domU.
Change its config file to use the new images created for xen3 domU.
Boot it up.

The above boots up the domU from the newly create image. There is no
difference between the config of xen1 and xen3 except for the ip and logical
volume name change.

Can anyone tell me what am i doing wrong here and what is causing the error
?

--
regards,

Anand Gupta


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Anand Gupta

2006-Apr-20 06:55 UTC

head link

[Xen-users] Re: error starting second domU

Ok i got the domU booting up now however the problem was nailed down only
when i commented out the ramdisk line from the config file.

Can''t 2 domU''s share the same initrd image ? Or i have to
create copies of
the image for each domU i create ?

--
regards,

Anand Gupta


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Anand Gupta

2006-Apr-20 08:23 UTC

head link

[Xen-users] Re: error starting second domU

Strangely the error still persisted. The error was a result of using an ip
route add command i had inserted inside the vif-route script. I wanted an
additional route add for an ip i had added for a domU. After removing the
additional route add, the second domU boots up properly. I perhaps need to
find another way to add the route.

On 4/20/06, Anand Gupta <xen.mails@gmail.com>
wrote:>
> Ok i got the domU booting up now however the problem was nailed down only
> when i commented out the ramdisk line from the config file.
>
> Can''t 2 domU''s share the same initrd image ? Or i have to
create copies of
> the image for each domU i create ?
>
> --
> regards,
>
> Anand Gupta
>

--
regards,

Anand Gupta

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Xen users - Apr 2006 - error starting second domU

[Xen-users] error starting second domU

[Xen-users] Re: error starting second domU

[Xen-users] Re: error starting second domU

[Xen-users] Re: error starting second domU