Julian Hagenauer
2006-Jul-19 09:55 UTC
[Xen-users] xen 3.0.2 does fail without configuration file.
Hi,
i am running debian sarge with selfcompiled xen 3.0.2.
I can easily start and halt domains, if i create them woith a
configurationfile...
/etc/xen/vm01:
name="vm01"
kernel="/boot/vmlinuz-2.6-xenU"
root="/dev/hda1"
memory=64
disk=[''file:/vserver/images/vm01.img,hda1,w'']
# network
vif = [ '''' ]
dhcp="off"
ip="192.168.1.4"
netmask="255.255.255.0"
gateway="192.168.1.1"
hostname=""
extra="3"
I run ''xm create vm01'','' xm console
vm01'','' xm shutdown vm01''... Works
pretty.
Than i tried to start a vm without a configurationfile by running ''xm
create "/dev/null" kernel="/boot/vmlinuz-2.6.16-xenU"
name=test
memory=64 disk=[''file:/vserver/images/base.img,hda1,w'']
root="/dev/hda1"
extra=3''.
Unfortunately this returns:
Using config file "/dev/null".
Error: Device 769 (vbd) could not be connected. Hotplug scripts not working.
xend.log:
[2006-07-19 11:53:49 xend.XendDomainInfo] DEBUG (XendDomainInfo:178)
XendDomainInfo.create([''vm'', [''name'',
''test''], [''memory'', 64],
[''vcpus'', 1], [''image'',
[''linux'', [''kernel'',
''/boot/vmlinuz-2.6.16-xenU''], [''root'',
''/dev/hda1''], [''args'',
''3'']]], [''device'', [''vbd'',
[''uname'', ''[file:/vserver/images/base.img''],
[''dev'', ''hda1''], [''mode'',
''w]'']]]])
[2006-07-19 11:53:50 xend.XendDomainInfo] DEBUG (XendDomainInfo:284)
parseConfig: config is [''vm'', [''name'',
''test''], [''memory'', 64],
[''vcpus'', 1], [''image'',
[''linux'', [''kernel'',
''/boot/vmlinuz-2.6.16-xenU''], [''root'',
''/dev/hda1''], [''args'',
''3'']]], [''device'', [''vbd'',
[''uname'', ''[file:/vserver/images/base.img''],
[''dev'', ''hda1''], [''mode'',
''w]'']]]]
[2006-07-19 11:53:50 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-xenU''], [''root'',
''/dev/hda1''], [''args'',
''3'']], ''on_poweroff'': None,
''cpus'': None, ''name'':
''test'', ''backend'': [],
''vcpus'': 1, ''cpu_weight'': None,
''vcpu_avail'': None, ''memory'': 64,
''device'': [(''vbd'', [''vbd'',
[''uname'', ''[file:/vserver/images/base.img''],
[''dev'', ''hda1''], [''mode'',
''w]'']])], ''bootloader'': None,
''cpu'': None, ''maxmem'': None}
[2006-07-19 11:53:50 xend.XendDomainInfo] DEBUG (XendDomainInfo:1164)
XendDomainInfo.construct: None 0
[2006-07-19 11:53:50 xend.XendDomainInfo] DEBUG (XendDomainInfo:1196)
XendDomainInfo.initDomain: 11 1.0
[2006-07-19 11:53:50 xend] DEBUG (balloon:126) Balloon: free 178; need 65; done.
[2006-07-19 11:53:50 xend] INFO (image:135) buildDomain os=linux dom=11 vcpus=1
[2006-07-19 11:53:50 xend] DEBUG (image:173) dom = 11
[2006-07-19 11:53:50 xend] DEBUG (image:174) image =
/boot/vmlinuz-2.6.16-xenU
[2006-07-19 11:53:50 xend] DEBUG (image:175) store_evtchn = 1
[2006-07-19 11:53:50 xend] DEBUG (image:176) console_evtchn = 2
[2006-07-19 11:53:50 xend] DEBUG (image:177) cmdline = root=/dev/hda1 3
[2006-07-19 11:53:50 xend] DEBUG (image:178) ramdisk =
[2006-07-19 11:53:50 xend] DEBUG (image:179) vcpus = 1
[2006-07-19 11:53:50 xend] DEBUG (image:180) features =
[2006-07-19 11:53:50 xend] DEBUG (DevController:103) DevController: writing
{''virtual-device'': ''769'',
''backend-id'': ''0'',
''state'': ''1'', ''backend'':
''/local/domain/0/backend/vbd/11/769''} to
/local/domain/11/device/vbd/769.
[2006-07-19 11:53:50 xend] DEBUG (DevController:105) DevController: writing
{''domain'': ''test'',
''frontend'':
''/local/domain/11/device/vbd/769'', ''dev'':
''hda1'', ''state'': ''1'',
''params'': ''/vserver/images/base.img'',
''mode'': ''w]'',
''frontend-id'': ''11'',
''type'': ''[file''} to
/local/domain/0/backend/vbd/11/769.
[2006-07-19 11:53:50 xend.XendDomainInfo] DEBUG (XendDomainInfo:671) Storing VM
details: {''ssidref'': ''0'',
''uuid'':
''0a43fd07-d274-54f3-5428-9dee355c39a1'',
''on_reboot'': ''restart'',
''start_time'': ''1153302830.36'',
''on_poweroff'': ''destroy'',
''name'': ''test'', ''vcpus'':
''1'', ''vcpu_avail'': ''1'',
''memory'': ''64'',
''on_crash'': ''restart'',
''image'': ''(linux (kernel /boot/vmlinuz-2.6.16-xenU)
(root /dev/hda1) (args 3))'', ''maxmem'':
''64''}
[2006-07-19 11:53:50 xend.XendDomainInfo] DEBUG (XendDomainInfo:696) Storing
domain details: {''console/ring-ref'':
''62464'', ''console/port'':
''2'', ''name'': ''test'',
''console/limit'': ''1048576'',
''vm'':
''/vm/0a43fd07-d274-54f3-5428-9dee355c39a1'',
''domid'': ''11'',
''cpu/0/availability'': ''online'',
''memory/target'': ''65536'',
''store/ring-ref'': ''62465'',
''store/port'': ''1''}
[2006-07-19 11:53:50 xend.XendDomainInfo] DEBUG (XendDomainInfo:877)
XendDomainInfo.handleShutdownWatch
[2006-07-19 11:53:50 xend] DEBUG (DevController:132) Waiting for devices vif.
[2006-07-19 11:53:50 xend] DEBUG (DevController:132) Waiting for devices usb.
[2006-07-19 11:53:50 xend] DEBUG (DevController:132) Waiting for devices vbd.
[2006-07-19 11:53:50 xend] DEBUG (DevController:138) Waiting for 769.
[2006-07-19 11:53:50 xend] DEBUG (DevController:403) hotplugStatusCallback
/local/domain/0/backend/vbd/11/769/hotplug-status.
[2006-07-19 11:54:00 xend.XendDomainInfo] DEBUG (XendDomainInfo:1327)
XendDomainInfo.destroy: domid=11
[2006-07-19 11:54:00 xend.XendDomainInfo] DEBUG (XendDomainInfo:1335)
XendDomainInfo.destroyDomain(11)
[2006-07-19 11:54:00 xend] DEBUG (DevController:403) hotplugStatusCallback
/local/domain/0/backend/vbd/11/769/hotplug-status.
[2006-07-19 11:54:00 xend] DEBUG (DevController:403) hotplugStatusCallback
/local/domain/0/backend/vbd/11/769/hotplug-status.
The xen-installscript copied the dist-files for hotpluged-systems, so i
should not mind udev, should i?
Why does xen behave different when passing configuration via commandline?
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Jerry Amundson
2006-Jul-19 13:10 UTC
Re: [Xen-users] xen 3.0.2 does fail without configuration file.
On Wed July 19 2006 04:55, Julian Hagenauer wrote:> /etc/xen/vm01: > name="vm01" > kernel="/boot/vmlinuz-2.6-xenU" > root="/dev/hda1" > memory=64 > disk=[''file:/vserver/images/vm01.img,hda1,w'']> Than i tried to start a vm without a configurationfile by running > ''xm create "/dev/null" kernel="/boot/vmlinuz-2.6.16-xenU" name=test > memory=64 disk=[''file:/vserver/images/base.img,hda1,w''] > root="/dev/hda1" extra=3''.> Why does xen behave different when passing configuration via > commandline?Could be the different img files : vm01.img vs. base.img jerry _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users