Hi,
xend work fine now :) YAHOO
I''m trying to install Win2003 on xen 3.1 64Bits with this tutorial :
http://www.xensource.com/files/xen_install_windows.pdf
All is fine except at the end :(
xm create /etc/xen/available/win2003.hvm
Error: (22, ''Invalid argument'')
# /var/log/xen/xend.log
# ====================[2007-06-19 12:43:27 xend.XendDomainInfo 19284] DEBUG
(XendDomainInfo:190)
XendDomainInfo.cr
[2007-06-19 12:43:27 xend.XendDomainInfo 19284] DEBUG (XendDomainInfo:296)
parseConfig: conf
[2007-06-19 12:43:27 xend.XendDomainInfo 19284] DEBUG (XendDomainInfo:395)
parseConfig: resu
[2007-06-19 12:43:27 xend.XendDomainInfo 19284] DEBUG
(XendDomainInfo:1262) XendDomainInfo.c
[2007-06-19 12:43:27 xend.XendDomainInfo 19284] ERROR (__init__:1021)
Domain construction fa
Traceback (most recent call last):
File "/usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py",
line
194, in create
vm.construct()
File "/usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py",
line
1266, in construc
handle = uuid.fromString(self.info[''uuid'']))
Error: (22, ''Invalid argument'')
[2007-06-19 12:43:27 xend.XendDomainInfo 19284] DEBUG
(XendDomainInfo:1458) XendDomainInfo.d
[2007-06-19 12:43:27 xend 19284] ERROR (__init__:1021) (22, ''Invalid
argument'')
Traceback (most recent call last):
File "/usr/lib/python2.5/site-packages/xen/util/xmlrpclib2.py", line
162, in _marshaled_di
response = self._dispatch(method, params)
File "SimpleXMLRPCServer.py", line 415, in _dispatch
return func(*params)
File
"/usr/lib/python2.5/site-packages/xen/xend/server/XMLRPCServer.py",
line 64, in domai
info = XendDomain.instance().domain_create(config)
File "/usr/lib/python2.5/site-packages/xen/xend/XendDomain.py", line
228, in domain_create
dominfo = XendDomainInfo.create(config)
File "/usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py",
line
194, in create
vm.construct()
File "/usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py",
line
1266, in construc
handle = uuid.fromString(self.info[''uuid'']))
Error: (22, ''Invalid argument'')
win2003.hvm is a copy of xmexample.hvm
# win2003.hvm
# ==========import os, re
arch = os.uname()[4]
if re.search(''64'', arch):
arch_libdir = ''lib64''
else:
arch_libdir = ''lib''
kernel = "/usr/lib/xen/boot/hvmloader"
builder=''hvm''
memory = 1024
name = "windows2003"
vif = [ ''type=ioemu, bridge=xenbr0'' ]
disk = [ ''phy:vg00/windows2003,ioemu:hda,w'' ]
cdrom="/media/iso_images/windows_2003_standard.iso"
boot="d"
sdl=1
vnc=0
stdvga=0
Regards
Franck
--
http://www.linuxpourtous.com
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
> -----Original Message----- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Franck > Sent: 19 June 2007 11:51 > To: xen-users@lists.xensource.com > Subject: [Xen-users] Xen and Windows > > Hi, > > xend work fine now :) YAHOO > > I''m trying to install Win2003 on xen 3.1 64Bits with this tutorial : > http://www.xensource.com/files/xen_install_windows.pdf > > All is fine except at the end :( > xm create /etc/xen/available/win2003.hvm > Error: (22, ''Invalid argument'') >Don''t think the xend-log is useful here... The error message indicates that your config file is "brokened".> > win2003.hvm is a copy of xmexample.hvm > > # win2003.hvm > # ==========> import os, re > arch = os.uname()[4] > if re.search(''64'', arch): > arch_libdir = ''lib64'' > else: > arch_libdir = ''lib'' > > kernel = "/usr/lib/xen/boot/hvmloader" > builder=''hvm'' > memory = 1024 > name = "windows2003" > vif = [ ''type=ioemu, bridge=xenbr0'' ] > disk = [ ''phy:vg00/windows2003,ioemu:hda,w'' ] > cdrom="/media/iso_images/windows_2003_standard.iso"I''m not sure if 3.1 accepts the "cdrom=" statement. Better to use the new model of adding something like this on the "disk=" line: "file:some-filename-with-path,hdc:cdrom,r" You should also have a line for the device model: device_model=''/usr/'' + arch_libdir + ''/xen/bin/qemu-dm" No guarantees, other subtle errors have been known to cause problems... -- Mats> boot="d" > sdl=1 > vnc=0 > stdvga=0 > > Regards > > Franck > -- > http://www.linuxpourtous.com >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> > >> -----Original Message----- >> From: xen-users-bounces@lists.xensource.com >> [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Franck >> Sent: 19 June 2007 11:51 >> To: xen-users@lists.xensource.com >> Subject: [Xen-users] Xen and Windows >> >> Hi, >> >> xend work fine now :) YAHOO >> >> I''m trying to install Win2003 on xen 3.1 64Bits with this tutorial : >> http://www.xensource.com/files/xen_install_windows.pdf >> >> All is fine except at the end :( >> xm create /etc/xen/available/win2003.hvm >> Error: (22, ''Invalid argument'') >> > > Don''t think the xend-log is useful here... The error message indicates > that your config file is "brokened".yes, i''m sure but perhaps someone has been the same problem>> win2003.hvm is a copy of xmexample.hvm >> >> # win2003.hvm >> # ==========> import os, re >> arch = os.uname()[4] >> if re.search(''64'', arch): >> arch_libdir = ''lib64'' >> else: >> arch_libdir = ''lib'' >> >> kernel = "/usr/lib/xen/boot/hvmloader" >> builder=''hvm'' >> memory = 1024 >> name = "windows2003" >> vif = [ ''type=ioemu, bridge=xenbr0'' ] >> disk = [ ''phy:vg00/windows2003,ioemu:hda,w'' ] >> cdrom="/media/iso_images/windows_2003_standard.iso" > > I''m not sure if 3.1 accepts the "cdrom=" statement. Better to use the > new model of adding something like this on the "disk=" line: > "file:some-filename-with-path,hdc:cdrom,r"disk = [ ''phy:vg00/windows2003,ioemu:hda,w'', '',hdc:cdrom,r'' ]> You should also have a line for the device model: > device_model=''/usr/'' + arch_libdir + ''/xen/bin/qemu-dm"Yes, i''ve this ... Results are the same :( Franck -- http://www.linuxpourtous.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> -----Original Message----- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Franck > Sent: 19 June 2007 12:43 > To: xen-users@lists.xensource.com > Subject: RE: [Xen-users] Xen and Windows > > > > > > > >> -----Original Message----- > >> From: xen-users-bounces@lists.xensource.com > >> [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Franck > >> Sent: 19 June 2007 11:51 > >> To: xen-users@lists.xensource.com > >> Subject: [Xen-users] Xen and Windows > >> > >> Hi, > >> > >> xend work fine now :) YAHOO > >> > >> I''m trying to install Win2003 on xen 3.1 64Bits with this > tutorial : > >> http://www.xensource.com/files/xen_install_windows.pdf > >> > >> All is fine except at the end :( > >> xm create /etc/xen/available/win2003.hvm > >> Error: (22, ''Invalid argument'') > >> > > > > Don''t think the xend-log is useful here... The error > message indicates > > that your config file is "brokened". > > yes, i''m sure but perhaps someone has been the same problem > > >> win2003.hvm is a copy of xmexample.hvm > >> > >> # win2003.hvm > >> # ==========> import os, re > >> arch = os.uname()[4] > >> if re.search(''64'', arch): > >> arch_libdir = ''lib64'' > >> else: > >> arch_libdir = ''lib'' > >> > >> kernel = "/usr/lib/xen/boot/hvmloader" > >> builder=''hvm'' > >> memory = 1024 > >> name = "windows2003" > >> vif = [ ''type=ioemu, bridge=xenbr0'' ] > >> disk = [ ''phy:vg00/windows2003,ioemu:hda,w'' ] > >> cdrom="/media/iso_images/windows_2003_standard.iso" > > > > I''m not sure if 3.1 accepts the "cdrom=" statement. Better > to use the > > new model of adding something like this on the "disk=" line: > > "file:some-filename-with-path,hdc:cdrom,r" > > disk = [ ''phy:vg00/windows2003,ioemu:hda,w'', '',hdc:cdrom,r'' ]I suppose you REALLY have something (sensible) between "''" and "," before hdc above, right? Ah, and also try giving an absolute path for the first part, such as "phy:/dev/vg00..." (check that this is really the right path, of course). I don''t think "ioemu:" is necessary either, so you can remove that for 3.1. That''s probably not helping, but it''s worth a try. -- Mats> > > You should also have a line for the device model: > > device_model=''/usr/'' + arch_libdir + ''/xen/bin/qemu-dm" > > Yes, i''ve this ... > > Results are the same :( > > Franck > -- > http://www.linuxpourtous.com > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
>> >> # win2003.hvm >> >> # ==========> import os, re >> >> arch = os.uname()[4] >> >> if re.search(''64'', arch): >> >> arch_libdir = ''lib64'' >> >> else: >> >> arch_libdir = ''lib'' >> >> >> >> kernel = "/usr/lib/xen/boot/hvmloader" >> >> builder=''hvm'' >> >> memory = 1024 >> >> name = "windows2003" >> >> vif = [ ''type=ioemu, bridge=xenbr0'' ] >> >> disk = [ ''phy:vg00/windows2003,ioemu:hda,w'' ] >> >> cdrom="/media/iso_images/windows_2003_standard.iso" >> > >> > I''m not sure if 3.1 accepts the "cdrom=" statement. Better >> to use the >> > new model of adding something like this on the "disk=" line: >> > "file:some-filename-with-path,hdc:cdrom,r" >> >> disk = [ ''phy:vg00/windows2003,ioemu:hda,w'', '',hdc:cdrom,r'' ] > > I suppose you REALLY have something (sensible) between "''" and "," > before hdc above, right? > > Ah, and also try giving an absolute path for the first part, such as > "phy:/dev/vg00..." (check that this is really the right path, of > course). I don''t think "ioemu:" is necessary either, so you can remove > that for 3.1. That''s probably not helping, but it''s worth a try.it''s very strange that''s the example is broken ? If i test ONLY with xmexample.hvm without changes, the result is the same :( Error 22 Franck -- http://www.linuxpourtous.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> Hi, > > xend work fine now :) YAHOO > > I''m trying to install Win2003 on xen 3.1 64Bits with this tutorial : > http://www.xensource.com/files/xen_install_windows.pdf > > All is fine except at the end :( > xm create /etc/xen/available/win2003.hvm > Error: (22, ''Invalid argument'')the problem is not with the windows config file because, i''m testing with debian installation and the result is the same : ERROR 22 Perhaps with UUID ? Franck -- http://www.linuxpourtous.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> Hi, > > xend work fine now :) YAHOO > > I''m trying to install Win2003 on xen 3.1 64Bits with this tutorial : > http://www.xensource.com/files/xen_install_windows.pdf > > All is fine except at the end :( > xm create /etc/xen/available/win2003.hvm > Error: (22, ''Invalid argument'')the problem is not with the windows config file because, i''m testing with debian installation and the result is the same : ERROR 22 Perhaps with UUID ? Franck -- http://www.linuxpourtous.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Can you post the COMPLETE configuration file? -- Mats> -----Original Message----- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Franck > Sent: 19 June 2007 13:50 > To: xen-users@lists.xensource.com > Subject: Re: [Xen-users] Xen and Windows > > > > Hi, > > > > xend work fine now :) YAHOO > > > > I''m trying to install Win2003 on xen 3.1 64Bits with this tutorial : > > http://www.xensource.com/files/xen_install_windows.pdf > > > > All is fine except at the end :( > > xm create /etc/xen/available/win2003.hvm > > Error: (22, ''Invalid argument'') > > the problem is not with the windows config file because, i''m > testing with > debian installation and the result is the same : ERROR 22 > > Perhaps with UUID ? > > Franck > -- > http://www.linuxpourtous.com > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> Can you post the COMPLETE configuration file?# -*- mode: python; -*- #===========================================================================# Python configuration setup for ''xm create''. # This script sets the parameters used when a domain is created using ''xm create''. # You use a separate script for each domain you want to create, or # you can set the parameters for the domain on the xm command line. #=========================================================================== import os, re arch = os.uname()[4] if re.search(''64'', arch): arch_libdir = ''lib64'' else: arch_libdir = ''lib'' #---------------------------------------------------------------------------- # Kernel image file. kernel = "/usr/lib/xen/boot/hvmloader" # The domain build function. HVM domain uses ''hvm''. builder=''hvm'' # Initial memory allocation (in megabytes) for the new domain. # # WARNING: Creating a domain with insufficient memory may cause out of # memory errors. The domain needs enough memory to boot kernel # and modules. Allocating less than 32MBs is not recommended. memory = 1024 # Shadow pagetable memory for the domain, in MB. # Should be at least 2KB per MB of domain memory, plus a few MB per vcpu. # shadow_memory = 8 # A name for your domain. All domains must have different names. name = "qualitatif" # 128-bit UUID for the domain. The default behavior is to generate a new UUID # on each call to ''xm create''. #uuid = "06ed00fe-1162-4fc4-b5d8-11993ee4a8b9" #----------------------------------------------------------------------------- # The number of cpus guest platform has, default=1 #vcpus=1 # Enable/disable HVM guest PAE, default=1 (enabled) #pae=1 # Enable/disable HVM guest ACPI, default=1 (enabled) #acpi=1 #acpi=0 # Enable/disable HVM APIC mode, default=1 (enabled) # Note that this option is ignored if vcpus > 1 #apic=1 #apic=1 # List of which CPUS this domain is allowed to use, default Xen picks #cpus = "" # leave to Xen to pick #cpus = "0" # all vcpus run on CPU0 #cpus = "0-3,5,^1" # run on cpus 0,2,3,5 # Optionally define mac and/or bridge for the network interfaces. # Random MACs are assigned if not given. #vif = [ ''type=ioemu, mac=00:16:3e:00:00:11, bridge=xenbr0, model=ne2k_pci'' ] # type=ioemu specify the NIC is an ioemu device not netfront vif = [ ''type=ioemu, bridge=xenbr0'' ] #---------------------------------------------------------------------------- # Define the disk devices you want the domain to have access to, and # what you want them accessible as. # Each disk entry is of the form phy:UNAME,DEV,MODE # where UNAME is the device, DEV is the device name the domain will see, # and MODE is r for read-only, w for read-write. #disk = [ ''phy:hda1,hda1,r'' ] #disk = [ ''file:/var/images/min-el3-i386.img,hda,w'', '',hdc:cdrom,r'' ] disk = [ ''phy:/dev/vg00/windows2003,ioemu:hda,w'', '',hdc:cdrom,r'' ] #---------------------------------------------------------------------------- # Configure the behaviour when a domain exits. There are three ''reasons'' # for a domain to stop: poweroff, reboot, and crash. For each of these you # may specify: # # "destroy", meaning that the domain is cleaned up as normal; # "restart", meaning that a new domain is started in place of the old # one; # "preserve", meaning that no clean-up is done until the domain is # manually destroyed (using xm destroy, for example); or # "rename-restart", meaning that the old domain is not cleaned up, but is # renamed and a new domain started in its place. # # The default is # # on_poweroff = ''destroy'' # on_reboot = ''restart'' # on_crash = ''restart'' # # For backwards compatibility we also support the deprecated option restart # # restart = ''onreboot'' means on_poweroff = ''destroy'' # on_reboot = ''restart'' # on_crash = ''destroy'' # # restart = ''always'' means on_poweroff = ''restart'' # on_reboot = ''restart'' # on_crash = ''restart'' # # restart = ''never'' means on_poweroff = ''destroy'' # on_reboot = ''destroy'' # on_crash = ''destroy'' #on_poweroff = ''destroy'' #on_reboot = ''restart'' #on_crash = ''restart'' #=========================================================================== # New stuff device_model = ''/usr/'' + arch_libdir + ''/xen/bin/qemu-dm'' #cdrom="/media/iso_images/windows_2003_standard.iso" #cdrom="dev/cdrom" #----------------------------------------------------------------------------- # boot on floppy (a), hard disk (c), Network (n) or CD-ROM (d) # default: hard disk, cd-rom, floppy #boot="cda" boot="d" #----------------------------------------------------------------------------- # write to temporary files instead of disk image files #snapshot=1 #---------------------------------------------------------------------------- # enable SDL library for graphics, default = 0 sdl=1 #---------------------------------------------------------------------------- # enable VNC library for graphics, default = 1 vnc=0 #---------------------------------------------------------------------------- # address that should be listened on for the VNC server if vnc is set. # default is to use ''vnc-listen'' setting from /etc/xen/xend-config.sxp #vnclisten="127.0.0.1" #---------------------------------------------------------------------------- # set VNC display number, default = domid #vncdisplay=1 #---------------------------------------------------------------------------- # try to find an unused port for the VNC server, default = 1 #vncunused=1 #---------------------------------------------------------------------------- # enable spawning vncviewer for domain''s console # (only valid when vnc=1), default = 0 #vncconsole=0 #---------------------------------------------------------------------------- # set password for domain''s VNC console # default is depents on vncpasswd in xend-config.sxp vncpasswd='''' #---------------------------------------------------------------------------- # no graphics, use serial port #nographic=0 #---------------------------------------------------------------------------- # enable stdvga, default = 0 (use cirrus logic device model) stdvga=0 #----------------------------------------------------------------------------- # serial port re-direct to pty deivce, /dev/pts/n # then xm console or minicom can connect serial=''pty'' #----------------------------------------------------------------------------- # Qemu Monitor, default is disable # Use ctrl-alt-2 to connect #monitor=1 #----------------------------------------------------------------------------- # enable sound card support, [sb16|es1370|all|..,..], default none #soundhw=''sb16'' #----------------------------------------------------------------------------- # set the real time clock to local time [default=0 i.e. set to utc] #localtime=1 #----------------------------------------------------------------------------- # set the real time clock offset in seconds [default=0 i.e. same as dom0] #rtc_timeoffset=3600 #----------------------------------------------------------------------------- # start in full screen #full-screen=1 #----------------------------------------------------------------------------- # Enable USB support (specific devices specified at runtime through the # monitor window) #usb=1 # Enable USB mouse support (only enable one of the following, `mouse'' for # PS/2 protocol relative mouse, `tablet'' for # absolute mouse) #usbdevice=''mouse'' #usbdevice=''tablet'' #----------------------------------------------------------------------------- # Set keyboard layout, default is en-us keyboard. #keymap=''ja''> > -- > Mats > >> -----Original Message----- >> From: xen-users-bounces@lists.xensource.com >> [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Franck >> Sent: 19 June 2007 13:50 >> To: xen-users@lists.xensource.com >> Subject: Re: [Xen-users] Xen and Windows >> >> >> > Hi, >> > >> > xend work fine now :) YAHOO >> > >> > I''m trying to install Win2003 on xen 3.1 64Bits with this tutorial : >> > http://www.xensource.com/files/xen_install_windows.pdf >> > >> > All is fine except at the end :( >> > xm create /etc/xen/available/win2003.hvm >> > Error: (22, ''Invalid argument'') >> >> the problem is not with the windows config file because, i''m >> testing with >> debian installation and the result is the same : ERROR 22 >> >> Perhaps with UUID ? >> >> Franck >> -- >> http://www.linuxpourtous.com >> >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users >> >> >> > > >-- http://www.linuxpourtous.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users