WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Error: Error creating domain: (22, 'Invalid argument')

To: Andrew Turnbull <abturnbull@xxxxxxxxx>
Subject: Re: [Xen-users] Error: Error creating domain: (22, 'Invalid argument')
From: Tarmo Tänav <tarmo@xxxxxxxx>
Date: Mon, 21 Nov 2005 20:46:56 +0200
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 21 Nov 2005 18:47:07 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <bff20ae20511211029h1d841c6fp@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <bff20ae20511211029h1d841c6fp@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hi,

I had a similiar problem, seemed to be related to networking,
because disabling it made things work well.
After getting the invalid message the domain appeared to be
in paused state, as shown by "xm list", just running "xm unpause domid"
made it work.

--
Tarmo Tänav

On E, 2005-11-21 at 18:29 +0000, Andrew Turnbull wrote:
> Hi there
> 
> I get the following error message when i try to "xm create <domid>"
> 
> Error: Error creating domain: (22, 'Invalid argument')
> 
> I have included everything i can think of
> 
> Thanks
> 
> 
> The DomU config is
> 
> kernel = "/boot/vmlinuz-2.6.12-xenU"
> ramdisk = "/boot/initrd-2.6.12.6-xenU.img"
> memory = 128
> name = "xen01"
> nics=1
> disk = [ 'phy:/dev/xensys01/xen01,sda1,w', 
> 'phy:/dev/xensys01/xen01swap,sda2,w']
> root = "/dev/sda1 ro"
> 
> My xm dmesg is
> 
>  http://www.cl.cam.ac.uk/netos/xen
>  University of Cambridge Computer Laboratory
> 
>  Xen version 3.0-devel (root@(none)) (gcc version 3.4.4 20050721 (Red
> Hat 3.4.4-2)) Sun Nov 20 17:49:04 GMT 2005
>  Latest ChangeSet: Sat Nov 19 09:37:14 2005 +0100 7901:aad88a902892
> 
> (XEN) Physical RAM map:
> (XEN)  0000000000000000 - 000000000009fc00 (usable)
> (XEN)  000000000009fc00 - 00000000000a0000 (reserved)
> (XEN)  00000000000e0000 - 0000000000100000 (reserved)
> (XEN)  0000000000100000 - 00000000e8100000 (usable)
> (XEN)  00000000efff0000 - 00000000effff000 (ACPI data)
> (XEN)  00000000effff000 - 00000000f0000000 (ACPI NVS)
> (XEN)  00000000fee00000 - 00000000fee01000 (reserved)
> (XEN)  00000000fff80000 - 0000000100000000 (reserved)
> (XEN)  0000000100000000 - 0000000400000000 (usable)
> (XEN) System RAM: 16000MB (16384636kB)
> (XEN) Xen heap: 9MB (10124kB)
> (XEN) PAE enabled, limit: 16 GB
> (XEN) found SMP MP-table at 000ff780
> (XEN) DMI 2.3 present.
> (XEN) Using APIC driver default
> (XEN) ACPI: RSDP (v000 AMI                                   ) @ 0x000ff900
> (XEN) ACPI: RSDT (v001 RCC    GCHE     0x00000001 MSFT 0x01000000) @ 
> 0xefff0000
> (XEN) ACPI: FADT (v001 RCC    GCHE     0x00000001 MSFT 0x01000000) @ 
> 0xefff0030
> (XEN) ACPI: MADT (v001 RCC    GCHE     0x00000001 MSFT 0x01000000) @ 
> 0xefff00b0
> (XEN) ACPI: DSDT (v001    RCC     GCHE 0x00000100 MSFT 0x0100000d) @ 
> 0x00000000
> (XEN) ACPI: Local APIC address 0xfee00000
> (XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
> (XEN) Processor #0 15:2 APIC version 20
> (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
> (XEN) Processor #1 15:2 APIC version 20
> (XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
> (XEN) Processor #2 15:2 APIC version 20
> (XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
> (XEN) Processor #3 15:2 APIC version 20
> (XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x00] disabled)
> (XEN) ACPI: LAPIC (acpi_id[0x05] lapic_id[0x00] disabled)
> (XEN) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x00] disabled)
> (XEN) ACPI: LAPIC (acpi_id[0x07] lapic_id[0x00] disabled)
> (XEN) ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
> (XEN) IOAPIC[0]: apic_id 8, version 17, address 0xfec00000, GSI 0-15
> (XEN) ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[16])
> (XEN) IOAPIC[1]: apic_id 9, version 17, address 0xfec01000, GSI 16-31
> (XEN) ACPI: IOAPIC (id[0x0a] address[0xfec02000] gsi_base[32])
> (XEN) IOAPIC[2]: apic_id 10, version 17, address 0xfec02000, GSI 32-47
> (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
> (XEN) ACPI: IRQ0 used by override.
> (XEN) ACPI: IRQ2 used by override.
> (XEN) Enabling APIC mode:  Flat.  Using 3 I/O APICs
> (XEN) Using ACPI (MADT) for SMP configuration information
> (XEN) Initializing CPU#0
> (XEN) Detected 1993.586 MHz processor.
> (XEN) Using scheduler: Simple EDF Scheduler (sedf)
> (XEN) CPU: Trace cache: 12K uops, L1 D cache: 8K
> (XEN) CPU: L2 cache: 512K
> (XEN) CPU: L3 cache: 1024K
> (XEN) CPU: Hyper-Threading is disabled
> (XEN) CPU0: Intel(R) Xeon(TM) MP CPU 2.00GHz stepping 05
> (XEN) Booting processor 1/1 eip 90000
> (XEN) Initializing CPU#1
> (XEN) CPU: Trace cache: 12K uops, L1 D cache: 8K
> (XEN) CPU: L2 cache: 512K
> (XEN) CPU: L3 cache: 1024K
> (XEN) CPU: Hyper-Threading is disabled
> (XEN) CPU1: Intel(R) Xeon(TM) MP CPU 2.00GHz stepping 05
> (XEN) Booting processor 2/2 eip 90000
> (XEN) Initializing CPU#2
> (XEN) CPU: Trace cache: 12K uops, L1 D cache: 8K
> (XEN) CPU: L2 cache: 512K
> (XEN) CPU: L3 cache: 1024K
> (XEN) CPU: Hyper-Threading is disabled
> (XEN) CPU2: Intel(R) Xeon(TM) MP CPU 2.00GHz stepping 05
> (XEN) Booting processor 3/3 eip 90000
> (XEN) Initializing CPU#3
> (XEN) CPU: Trace cache: 12K uops, L1 D cache: 8K
> (XEN) CPU: L2 cache: 512K
> (XEN) CPU: L3 cache: 1024K
> (XEN) CPU: Hyper-Threading is disabled
> (XEN) CPU3: Intel(R) Xeon(TM) MP CPU 2.00GHz stepping 05
> (XEN) Total of 4 processors activated.
> (XEN) ENABLING IO-APIC IRQs
> (XEN) ..TIMER: vector=0x31 pin1=2 pin2=-1
> (XEN) ..MP-BIOS bug: 8254 timer not connected to IO-APIC
> (XEN) ...trying to set up timer (IRQ0) through the 8259A ...  failed.
> (XEN) ...trying to set up timer as Virtual Wire IRQ... works.
> (XEN) checking TSC synchronization across 4 CPUs: passed.
> (XEN) Platform timer is 1.193MHz PIT
> (XEN) Brought up 4 CPUs
> (XEN) mtrr: v2.0 (20020519)
> (XEN) *** LOADING DOMAIN 0 ***
> (XEN) Xen-ELF header found:
> 'GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=3.0,VIRT_BASE=0xC0000000,PAE=yes,LOADER=generic'
> (XEN) PHYSICAL MEMORY ARRANGEMENT:
> (XEN)  Dom0 alloc.:   0000000007800000->0000000008000000 (129024 pages
> to be allocated)
> (XEN) VIRTUAL MEMORY ARRANGEMENT:
> (XEN)  Loaded kernel: c0100000->c06205e4
> (XEN)  Init. ramdisk: c0621000->c06c2800
> (XEN)  Phys-Mach map: c06c3000->c0743000
> (XEN)  Start info:    c0743000->c0744000
> (XEN)  Page tables:   c0744000->c074d000
> (XEN)  Boot stack:    c074d000->c074e000
> (XEN)  TOTAL:         c0000000->c0800000
> (XEN)  ENTRY ADDRESS: c0100000
> (XEN) Initrd len 0xa1800, start at 0xc0621000
> (XEN) Scrubbing Free RAM:
> ....................................................................................................................................................................done.
> (XEN) Xen trace buffers: disabled
> (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch
> input to Xen).
> (XEN) mtrr: type mismatch for fb000000,1000000 old: write-back new:
> write-combining
> (XEN) microcode: CPU1 updated from revision 0x13 to 0x2a, date = 08112004
> (XEN) microcode: CPU2 updated from revision 0x13 to 0x2a, date = 08112004
> (XEN) microcode: CPU3 updated from revision 0x13 to 0x2a, date = 08112004
> (XEN) microcode: CPU0 updated from revision 0x13 to 0x2a, date = 08112004
> 
> My Xend.log
> 
> [2005-11-21 18:27:20 xend.XendDomainInfo] DEBUG (XendDomainInfo:178)
> XendDomainInfo.create(['vm', ['name', 'xen01'], ['memory', '128'],
> ['image', ['linux', ['kernel', '/boot/vmlinuz-2.6.12-xenU'],
> ['ramdisk', '/boot/initrd-2.6.12.6-xenU.img'], ['root', '/dev/sda1
> ro'], ['args', '4'], ['vcpus', '1'], ['vcpus', '1'], ['boot', 'c']]],
> ['device', ['vbd', ['uname', 'phy:/dev/xensys01/xen01'], ['dev',
> 'sda1'], ['mode', 'w']]], ['device', ['vbd', ['uname',
> 'phy:/dev/xensys01/xen01swap'], ['dev', 'sda2'], ['mode', 'w']]],
> ['device', ['vif']]])
> [2005-11-21 18:27:20 xend.XendDomainInfo] DEBUG (XendDomainInfo:283)
> parseConfig: config is ['vm', ['name', 'xen01'], ['memory', '128'],
> ['image', ['linux', ['kernel', '/boot/vmlinuz-2.6.12-xenU'],
> ['ramdisk', '/boot/initrd-2.6.12.6-xenU.img'], ['root', '/dev/sda1
> ro'], ['args', '4'], ['vcpus', '1'], ['vcpus', '1'], ['boot', 'c']]],
> ['device', ['vbd', ['uname', 'phy:/dev/xensys01/xen01'], ['dev',
> 'sda1'], ['mode', 'w']]], ['device', ['vbd', ['uname',
> 'phy:/dev/xensys01/xen01swap'], ['dev', 'sda2'], ['mode', 'w']]],
> ['device', ['vif']]]
> [2005-11-21 18:27:20 xend.XendDomainInfo] DEBUG (XendDomainInfo:337)
> parseConfig: result is {'ssidref': None, 'uuid': None, 'on_crash':
> None, 'on_reboot': None, 'image': ['linux', ['kernel',
> '/boot/vmlinuz-2.6.12-xenU'], ['ramdisk',
> '/boot/initrd-2.6.12.6-xenU.img'], ['root', '/dev/sda1 ro'], ['args',
> '4'], ['vcpus', '1'], ['vcpus', '1'], ['boot', 'c']], 'on_poweroff':
> None, 'name': 'xen01', 'backend': [], 'vcpus': 1, 'cpu_weight': None,
> 'vcpu_avail': None, 'memory': 128, 'device': [('vbd', ['vbd',
> ['uname', 'phy:/dev/xensys01/xen01'], ['dev', 'sda1'], ['mode',
> 'w']]), ('vbd', ['vbd', ['uname', 'phy:/dev/xensys01/xen01swap'],
> ['dev', 'sda2'], ['mode', 'w']]), ('vif', ['vif'])], 'bootloader':
> None, 'cpu': None, 'maxmem': None}
> [2005-11-21 18:27:20 xend.XendDomainInfo] DEBUG (XendDomainInfo:1065)
> XendDomainInfo.construct: None 0
> [2005-11-21 18:27:20 xend.XendDomainInfo] DEBUG (XendDomainInfo:1097)
> XendDomainInfo.initDomain: 6 1.0
> [2005-11-21 18:27:20 xend] INFO (image:132) buildDomain os=linux dom=6 vcpus=1
> [2005-11-21 18:27:20 xend] DEBUG (image:170) dom            = 6
> [2005-11-21 18:27:20 xend] DEBUG (image:171) image          =
> /boot/vmlinuz-2.6.12-xenU
> [2005-11-21 18:27:20 xend] DEBUG (image:172) store_evtchn   = 1
> [2005-11-21 18:27:20 xend] DEBUG (image:173) console_evtchn = 2
> [2005-11-21 18:27:20 xend] DEBUG (image:174) cmdline        = 
> root=/dev/sda1 ro 4
> [2005-11-21 18:27:20 xend] DEBUG (image:175) ramdisk        =
> /boot/initrd-2.6.12.6-xenU.img
> [2005-11-21 18:27:20 xend] DEBUG (image:176) vcpus          = 1
> [2005-11-21 18:27:20 xend.XendDomainInfo] ERROR (XendDomainInfo:190)
> Domain construction failed
> Traceback (most recent call last):
>   File 
> "/root/xen-unstable/dist/install/usr/lib/python/xen/xend/XendDomainInfo.py",
> line 183, in create
>     vm.initDomain()
>   File 
> "/root/xen-unstable/dist/install/usr/lib/python/xen/xend/XendDomainInfo.py",
> line 1118, in initDomain
>     channel_details = self.image.createImage()
>   File "/root/xen-unstable/dist/install/usr/lib/python/xen/xend/image.py",
> line 115, in createImage
>     return self.createDomain()
>   File "/root/xen-unstable/dist/install/usr/lib/python/xen/xend/image.py",
> line 134, in createDomain
>     result = self.buildDomain()
>   File "/root/xen-unstable/dist/install/usr/lib/python/xen/xend/image.py",
> line 183, in buildDomain
>     ramdisk        = self.ramdisk)
> error: (22, 'Invalid argument')
> [2005-11-21 18:27:20 xend.XendDomainInfo] DEBUG (XendDomainInfo:1183)
> XendDomainInfo.destroy: domid=6
> [2005-11-21 18:27:20 xend.XendDomainInfo] DEBUG (XendDomainInfo:1191)
> XendDomainInfo.destroyDomain(6)
> [2005-11-21 18:27:20 xend] ERROR (SrvBase:87) Request create failed.
> Traceback (most recent call last):
>   File "/root/xen-unstable/dist/install/usr/lib/python/xen/web/SrvBase.py",
> line 85, in perform
>     return op_method(op, req)
>   File 
> "/root/xen-unstable/dist/install/usr/lib/python/xen/xend/server/SrvDomainDir.py",
> line 82, in op_create
>     raise XendError("Error creating domain: " + str(ex))
> XendError: Error creating domain: (22, 'Invalid argument')
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users


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