I am trying to run a new server with centos + xen using centos xen packages. After installation, we had to install a hardware raid card (areca) on the machine, and thus reload the os. It so happens the drivers shipped aren''t compatible with xen kernel, so i was forced to compile xen from source to compile areca drivers. Now with system running under compiled xen, i cannot boot my old domU image :( Here is the error i get xm create aaa Using config file "./aaa". Error: (22, ''Invalid argument'') Here is the config file # Automatically generated xen config file name = "aaa" memory = "2048" disk = [ ''tap:aio:/home/xen/aaa,xvda,w'', ] vif = [ ''mac=00:16:3e:12:34:a9, bridge=xenbr0'', ] vfb = ["type=vnc,vncunused=1"] uuid = "bee5f62b-7193-a454-e37e-a151a5be8f44" bootloader="/usr/bin/pygrub" vcpus=7 Also the Virtual Machine Manager under centos has stopped working. Does this mean i need to recreate these domU''s ? Really confused here on how to go about it since the old domU has a lot of data in it, which is required and now the machine is down :( P.S. : Is there a way to compile the areca drivers under the centos xen kernel ? I see the only kernel-xen source is available is under centosplus repository called kernel-xen-devel-2.6.18-8.1.14.el5.centos.plus. I don''t see any targets in the areca driver Makefile even, so don''t know how it will be compiled as well :( Any help on this will be really appreciated. -- regards, Anand Gupta _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Anand Gupta schrieb:> I am trying to run a new server with centos + xen using centos xen packages. > > After installation, we had to install a hardware raid card (areca) on > the machine, and thus reload the os. It so happens the drivers shipped > aren''t compatible with xen kernel, so i was forced to compile xen from > source to compile areca drivers.I''m no expert at centos, but since a while the areca driver has found it''s way into the mainline kernel. I can''t remember any distribution shipping a kernel without it. I would recommend you to check your dom0''s initrd.img and eventually rebuild it, as I assume the areca driver is build as a module. btw. If your dom0 kernel doesn''t support the raidcontroller, you''re in no case forced to recompile your whole xen. Just pick a recent, xen-enabled distro kernel from a distro you like. My favorite is the 2.6.22-14-xen out of the ubuntu gutsy repo, but your mileage may vary. greetings Stephan _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 10/16/07, Stephan Seitz <s.seitz@netz-haut.de> wrote:> > I''m no expert at centos, but since a while the areca driver has found it''s > way into the mainline kernel. > I can''t remember any distribution shipping a kernel without it. > > I would recommend you to check your dom0''s initrd.img and eventually > rebuild > it, as I assume the areca driver is build as a module.That is strange, i am installing centos5 from dvd image downloaded from centos site. The default install with all updates doesn''t recognize the areca card at all. The main problem is my /root also recides on the raid, so if the driver is not loaded i get a kernel panic. btw. If your dom0 kernel doesn''t support the raidcontroller, you''re in no> case forced to recompile your whole xen. Just pick a recent, xen-enabled > distro kernel from a distro you like. My favorite is the 2.6.22-14-xen out > of > the ubuntu gutsy repo, but your mileage may vary. >Thanks, but i already compiled xen on centos. Now the main problem i am facing is how to boot the existing domU. -- regards, Anand Gupta _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Thanks for the quick response Artur.
The reason there is nothing in the config file about the kernel is because
of pygrub and centos''s way to put the kernel inside the domU (atleast
thats
what i had learnt by reading the thread on this list)
I cannot mount the domU image file since it contains LVM volumes in it. Here
is the partition structure of the image file aaa.
Disk aaa: 0 MB, 0 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
aaa1 * 1 13 104391 83 Linux
aaa2 14 1300 10337827+ 8e Linux LVM
Partition 2 has different physical/logical endings:
phys=(1023, 254, 63) logical=(1299, 254, 63)
I tried to use lvm tools to recognise the volume as well, however
doesn''t
work. For this, i used the following
losetup /dev/loop0 /home/xen/aaa
Now the entire image is present as /dev/loop0. However when i try to run
vgscan, it doesn''t recognise the lvm volume at all.
On 10/16/07, Artur Mücke <muecke@tyntec.biz>
wrote:>
> Anand Gupta wrote:
> >
> > Also the Virtual Machine Manager under centos has stopped working.
Does
> this
> > mean i need to recreate these domU''s ? Really confused here
on how to go
> > about it since the old domU has a lot of data in it, which is required
> and
> > now the machine is down :(
>
> There''s nothing about your new kernel in your domU-Configuration.
There
> should be something like:
> kernel = ''/boot/vmlinuz-2.6.18-5-xen-686''
> poniting on the new compiled kernel.
>
> Moreover you should copy the new kernel modules to e.g. /lib/modules/.
>
> Dont worry about your data in the domU. You can mount your Image or the
> according partition like this:
>
> Partition:
> =========> mount /dev/XdaX /mnt
>
> Image:
> =====> mount -o loop /yourfolder/vm_disk.img /mnt
>
> Maybe the best would be to create a new VM with xen-create-image.
>
> Hope thats gonna help you a bit.
>
> Cheers,
>
> Artur
>
>
> --
> "There are 10 kinds of people in the world, those who understand
binary
> math, and those who don''t."
>
--
regards,
Anand Gupta
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Hi there,> I am trying to run a new server with centos + xen using centos xen > packages.OK. From what you''ve said I guess this is CentOS 5.0, so it''s come with Xen support, libvirt, virt-manager, etc.> After installation, we had to install a hardware raid card (areca) on the > machine, and thus reload the os. It so happens the drivers shipped aren''t > compatible with xen kernel, so i was forced to compile xen from source to > compile areca drivers. > > Now with system running under compiled xen, i cannot boot my old domU image > > :( > > Here is the error i get > > xm create aaa > Using config file "./aaa". > Error: (22, ''Invalid argument'')Hmmm, not a very helpful error message! The contents of /var/log/xen/xend.log may yield more helpful hints. Out of interest, did you uninstall your old Xen before building a new one? Sometimes the code of different Xen versions conflicts, which can mess things up unless the previous copy was properly uninstalled. This is especially a problem with the tools.> Also the Virtual Machine Manager under centos has stopped working. Does > this mean i need to recreate these domU''s ? Really confused here on how to > go about it since the old domU has a lot of data in it, which is required > and now the machine is down :(I''m not sure exactly why virtual machine manager would have failed at this point; but I''m guessing that you''ve installed a newer version of Xen to that which CentOS and RHEL 5 shipped. The Xen control interface changed, so your version of virt-manager doesn''t understand it. CentOS / RHEL 5 ship Xen 3.0.3, with a Xen 3.1 release being planned for their 5.1 update.> P.S. : Is there a way to compile the areca drivers under the centos xen > kernel ? I see the only kernel-xen source is available is under centosplus > repository called kernel-xen-devel-2.6.18-8.1.14.el5.centos.plus. I don''t > see any targets in the areca driver Makefile even, so don''t know how it > will be compiled as well :(The package kernel-xen-devel should have the stuff required to build modules against the CentOS / RHEL Xenified kernels. If you could use this to build your module then you''d be able to go back to using the stardard Xen / XenLinux packages; you''ll get a newer version of Xen when it''s added to the next OS increment release.> Any help on this will be really appreciated.Hope that helps. Daniel: I hope you don''t mind, but I''ve added you to the cc list in case you had any more specific insights / suggestions here. Cheers, Mark -- Dave: Just a question. What use is a unicyle with no seat? And no pedals! Mark: To answer a question with a question: What use is a skateboard? Dave: Skateboards have wheels. Mark: My wheel has a wheel! _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tue, Oct 16, 2007 at 08:42:50PM +0100, Mark Williamson wrote:> Hi there, > > > I am trying to run a new server with centos + xen using centos xen > > packages. > > OK. From what you''ve said I guess this is CentOS 5.0, so it''s come with Xen > support, libvirt, virt-manager, etc. > > > After installation, we had to install a hardware raid card (areca) on the > > machine, and thus reload the os. It so happens the drivers shipped aren''t > > compatible with xen kernel, so i was forced to compile xen from source to > > compile areca drivers. > > > > Now with system running under compiled xen, i cannot boot my old domU image > > > > :( > > > > Here is the error i get > > > > xm create aaa > > Using config file "./aaa". > > Error: (22, ''Invalid argument'') > > Hmmm, not a very helpful error message! The contents of /var/log/xen/xend.log > may yield more helpful hints.Yep, Xen 3.0.3 wasn''t great at reporting errors. This one basically means you used a bogus guest kernel - eg - A non-PAE 32-bit kernel - A bare metal kernel in a paravirt config - Wrong architecture kernel (eg 32 on 64, or 64 on 32) Dan -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Mark, On 10/17/07, Mark Williamson <mark.williamson@cl.cam.ac.uk> wrote:> > Hi there, > > > I am trying to run a new server with centos + xen using centos xen > > packages. > > OK. From what you''ve said I guess this is CentOS 5.0, so it''s come with > Xen > support, libvirt, virt-manager, etc.Yes correct. Its centos 5.0, comes with xen, libvirt, virt-manager etc.> After installation, we had to install a hardware raid card (areca) on the > > machine, and thus reload the os. It so happens the drivers shipped > aren''t > > compatible with xen kernel, so i was forced to compile xen from source > to > > compile areca drivers. > > > > Now with system running under compiled xen, i cannot boot my old domU > image > > > > :( > > > > Here is the error i get > > > > xm create aaa > > Using config file "./aaa". > > Error: (22, ''Invalid argument'') > > Hmmm, not a very helpful error message! The contents of > /var/log/xen/xend.log > may yield more helpful hints.Sorry my mistake. Here is the /var/log/xen/xend.log file snippet [2007-10-17 16:05:09 xend.XendDomainInfo 4529] DEBUG (XendDomainInfo:190) XendDomainInfo.create([''vm'', [''name'', ''aaa''], [''memory'', ''2048''], [''vcpus'', 7], [''uuid'', ''bee5f62b-7193-a454-e37e-a151a5be8f44''], [''bootloader'', ''/usr/bin/pygrub''], [''image'', [''linux'', [''ramdisk'', ''/var/run/xend/boot/boot_ramdisk.aXA4NQ''], [''kernel'', ''/var/run/xend/boot/boot_kernel.u8QNnA''], [''args'', ''ro root=/dev/VolGroup00/LogVol00'']]], [''device'', [''tap'', [''uname'', ''tap:aio:/home/xen/aaa''], [''dev'', ''xvda''], [''mode'', ''w'']]], [''device'', [''vif'', [''bridge'', ''xenbr0''], [''mac'', ''00:16:3e:12:34:a9'']]], [''device'', [''vkbd'']], [''device'', [''vfb'', [''vncunused'', ''1''], [''type'', ''vnc''], [''xauthority'', ''/root/.Xauthority'']]]]) [2007-10-17 16:05:09 xend.XendDomainInfo 4529] DEBUG (XendDomainInfo:296) parseConfig: config is [''vm'', [''name'', ''aaa''], [''memory'', ''2048''], [''vcpus'', 7], [''uuid'', ''bee5f62b-7193-a454-e37e-a151a5be8f44''], [''bootloader'', ''/usr/bin/pygrub''], [''image'', [''linux'', [''ramdisk'', ''/var/run/xend/boot/boot_ramdisk.aXA4NQ''], [''kernel'', ''/var/run/xend/boot/boot_kernel.u8QNnA''], [''args'', ''ro root=/dev/VolGroup00/LogVol00'']]], [''device'', [''tap'', [''uname'', ''tap:aio:/home/xen/aaa''], [''dev'', ''xvda''], [''mode'', ''w'']]], [''device'', [''vif'', [''bridge'', ''xenbr0''], [''mac'', ''00:16:3e:12:34:a9'']]], [''device'', [''vkbd'']], [''device'', [''vfb'', [''vncunused'', ''1''], [''type'', ''vnc''], [''xauthority'', ''/root/.Xauthority'']]]] [2007-10-17 16:05:09 xend.XendDomainInfo 4529] DEBUG (XendDomainInfo:397) parseConfig: result is {''shadow_memory'': None, ''start_time'': None, ''uuid'': ''bee5f62b-7193-a454-e37e-a151a5be8f44'', ''on_crash'': None, ''on_reboot'': None, ''localtime'': None, ''image'': [''linux'', [''ramdisk'', ''/var/run/xend/boot/boot_ramdisk.aXA4NQ''], [''kernel'', ''/var/run/xend/boot/boot_kernel.u8QNnA''], [''args'', ''ro root=/dev/VolGroup00/LogVol00'']], ''on_poweroff'': None, ''bootloader_args'': None, ''cpus'': None, ''name'': ''aaa'', ''backend'': [], ''vcpus'': 7, ''cpu_weight'': None, ''features'': None, ''vcpu_avail'': None, ''memory'': 2048, ''device'': [(''tap'', [''tap'', [''uname'', ''tap:aio:/home/xen/aaa''], [''dev'', ''xvda''], [''mode'', ''w'']]), (''vif'', [''vif'', [''bridge'', ''xenbr0''], [''mac'', ''00:16:3e:12:34:a9'']]), (''vkbd'', [''vkbd'']), (''vfb'', [''vfb'', [''vncunused'', ''1''], [''type'', ''vnc''], [''xauthority'', ''/root/.Xauthority'']])], ''bootloader'': ''/usr/bin/pygrub'', ''cpu'': None, ''maxmem'': None} [2007-10-17 16:05:09 xend.XendDomainInfo 4529] DEBUG (XendDomainInfo:1264) XendDomainInfo.construct: None [2007-10-17 16:05:09 xend.XendDomainInfo 4529] ERROR (XendDomainInfo:202) Domain construction failed Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 194, in create vm.construct() File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 1268, in construct handle = uuid.fromString(self.info[''uuid''])) Error: (22, ''Invalid argument'') [2007-10-17 16:05:09 xend.XendDomainInfo 4529] DEBUG (XendDomainInfo:1463) XendDomainInfo.destroy: domid=None [2007-10-17 16:05:09 xend 4529] ERROR (xmlrpclib2:184) (22, ''Invalid argument'') Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/xen/util/xmlrpclib2.py", line 162, in _marshaled_dispatch response = self._dispatch(method, params) File "/usr/lib/python2.4/SimpleXMLRPCServer.py", line 406, in _dispatch return func(*params) File "/usr/lib/python2.4/site-packages/xen/xend/server/XMLRPCServer.py", line 64, in domain_create info = XendDomain.instance().domain_create(config) File "/usr/lib/python2.4/site-packages/xen/xend/XendDomain.py", line 228, in domain_create dominfo = XendDomainInfo.create(config) File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 194, in create vm.construct() File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 1268, in construct handle = uuid.fromString(self.info[''uuid''])) Error: (22, ''Invalid argument'') Out of interest, did you uninstall your old Xen before building a new one?> Sometimes the code of different Xen versions conflicts, which can mess > things > up unless the previous copy was properly uninstalled. This is especially > a > problem with the tools.Nope, i didn''t uninstall the old version. I thought the new compile would overwrite them anyways. Moreover i wanted to try out the virt-manager and see if it works with new xen compile.> Also the Virtual Machine Manager under centos has stopped working. Does > > this mean i need to recreate these domU''s ? Really confused here on how > to > > go about it since the old domU has a lot of data in it, which is > required > > and now the machine is down :( > > I''m not sure exactly why virtual machine manager would have failed at this > point; but I''m guessing that you''ve installed a newer version of Xen to > that > which CentOS and RHEL 5 shipped. The Xen control interface changed, so > your > version of virt-manager doesn''t understand it.Even if virt-manager doesn''t understand it, atleast xm create aaa should have worked. I am hoping looking at the log snippet you can provide more help. CentOS / RHEL 5 ship Xen 3.0.3, with a Xen 3.1 release being planned for> their > 5.1 update.That would be nice. I hope centos/rhel does more frequent updates and sync with frequent xen releases.> P.S. : Is there a way to compile the areca drivers under the centos xen > > kernel ? I see the only kernel-xen source is available is under > centosplus > > repository called kernel-xen-devel-2.6.18-8.1.14.el5.centos.plus. I > don''t > > see any targets in the areca driver Makefile even, so don''t know how it > > will be compiled as well :( > > The package kernel-xen-devel should have the stuff required to build > modules > against the CentOS / RHEL Xenified kernels. If you could use this to > build > your module then you''d be able to go back to using the stardard Xen / > XenLinux packages; you''ll get a newer version of Xen when it''s added to > the > next OS increment release.I looked for the kernel-xen-devel and found it only in the plus repository. This is what i did to compile the areca drivers. 1. Copied the directory to drivers/scsi/areca 2. Edited drivers/scsi/Kconfig as per areca instructions 3. Copied the config file from /boot to the kernel directory 4. make oldconfig [it then asks me what to do about the areca drivers, which i choose as a module, the only option there] 5. then i issue a make, which gives the following error make scripts/kconfig/conf -s arch/i386/Kconfig CHK include/linux/version.h CHK include/linux/utsrelease.h make[1]: *** No rule to make target `init/main.o'', needed by `init/built- in.o''. Stop. make: *** [init] Error 2 If i issue make ARCH=xen, then it complains about no makefile inside /usr/src/kernels/2.6.18-8.1.14.el5.centos.plus-xen-i686/arch/xen/Makefile. I could be doing some real wrong / stupid here, will appreciate if you can guide me to the proper direction.> Any help on this will be really appreciated. > > Hope that helps.Thanks. Atleast your reply helped in understanding the problem in a better manner. I hope i can resolve this and stick with the centos/ rhel xen packages. -- regards, Anand Gupta _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Mark, On 10/17/07, Mark Williamson <mark.williamson@cl.cam.ac.uk> wrote:> > Out of interest, did you uninstall your old Xen before building a new one? > Sometimes the code of different Xen versions conflicts, which can mess > things > up unless the previous copy was properly uninstalled. This is especially > a > problem with the tools. >When i tried to boot any domU on the newly compiled xen 3.1, it won''t boot either, giving the same error. This time i took your advise and removed the previous xen rpm''s. And yes as you mentioned that removed the error. However it removed virt-manager and all other stuff as well, guess i can''t use them without the xen 3.0.3. Nowever even trying to boot my old domU, it won''t give me that error, however it won''t boot as well. When tried, it will show me the grub screen, and the countdown to boot, however once the countdown is finished, it will just hang there. Here is the /var/log/xen/xend.log snippet when the domU was tried to be booted. [2007-10-18 15:48:44 5091] DEBUG (XendDomainInfo:84) XendDomainInfo.create([''vm'', [''name'', ''aaa''], [''memory'', ''2048''], [''vcpus'', 7], [''on_xend_start'', ''ignore''], [''on_xend_stop'', ''ignore''], [''uuid'', ''bee5f62b-7193-a454-e37e-a151a5be8f44''], [''bootloader'', ''/usr/bin/pygrub''], [''bootloader_args'', ''''], [''image'', [''linux'']], [''device'', [''tap'', [''uname'', ''tap:aio:/home/xen/aaa''], [''dev'', ''xvda''], [''mode'', ''w'']]], [''device'', [''vif'', [''bridge'', ''xenbr0''], [''mac'', ''00:16:3e:12:34:a9'']]], [''device'', [''vkbd'']], [''device'', [''vfb'', [''vncunused'', ''1''], [''type'', ''vnc''], [''xauthority'', ''/root/.Xauthority'']]]]) [2007-10-18 15:48:44 5091] DEBUG (XendDomainInfo:1506) XendDomainInfo.constructDomain [2007-10-18 15:48:44 5091] DEBUG (balloon:116) Balloon: 2101656 KiB free; need 2048; done. [2007-10-18 15:48:44 5091] DEBUG (XendDomain:434) Adding Domain: 3 [2007-10-18 15:48:44 5091] DEBUG (XendDomainInfo:1560) XendDomainInfo.initDomain: 3 256 [2007-10-18 15:48:45 5816] DEBUG (XendBootloader:100) Launching bootloader as [''/usr/bin/pygrub'', ''--output=/var/run/xend/boot/xenbl.17290'', ''/home/xen/aaa'']. [2007-10-18 15:48:49 5091] DEBUG (XendDomainInfo:1591) _initDomain:shadow_memory=0x0, memory_static_max=0x80000000, memory_static_min=0x0. [2007-10-18 15:48:49 5091] DEBUG (balloon:116) Balloon: 2101656 KiB free; need 2097152; done. [2007-10-18 15:48:49 5091] INFO (image:128) buildDomain os=linux dom=3 vcpus=7 [2007-10-18 15:48:49 5091] DEBUG (image:197) domid = 3 [2007-10-18 15:48:49 5091] DEBUG (image:198) memsize = 2048 [2007-10-18 15:48:49 5091] DEBUG (image:199) image /var/run/xend/boot/boot_kernel.OK6AAj [2007-10-18 15:48:49 5091] DEBUG (image:200) store_evtchn = 1 [2007-10-18 15:48:49 5091] DEBUG (image:201) console_evtchn = 2 [2007-10-18 15:48:49 5091] DEBUG (image:202) cmdline = ro root=/dev/VolGroup00/LogVol00 [2007-10-18 15:48:49 5091] DEBUG (image:203) ramdisk /var/run/xend/boot/boot_ramdisk.dCoRrz [2007-10-18 15:48:49 5091] DEBUG (image:204) vcpus = 7 [2007-10-18 15:48:49 5091] DEBUG (image:205) features [2007-10-18 15:48:49 5091] INFO (XendDomainInfo:1409) createDevice: vkbd : {''uuid'': ''243c924b-24c7-384f-3bec-e5a89f3477cb''} [2007-10-18 15:48:49 5091] DEBUG (DevController:117) DevController: writing {''protocol'': ''x86_32-abi'', ''state'': ''1'', ''backend-id'': ''0'', ''backend'': ''/local/domain/0/backend/vkbd/3/0''} to /local/domain/3/device/vkbd/0. [2007-10-18 15:48:49 5091] DEBUG (DevController:119) DevController: writing {''frontend-id'': ''3'', ''domain'': ''aaa'', ''frontend'': ''/local/domain/3/device/vkbd/0'', ''state'': ''1'', ''online'': ''1''} to /local/domain/0/backend/vkbd/3/0. [2007-10-18 15:48:49 5091] INFO (XendDomainInfo:1409) createDevice: vfb : {''vncunused'': ''1'', ''other_config'': {''vncunused'': ''1'', ''type'': ''vnc'', ''xauthority'': ''/root/.Xauthority''}, ''type'': ''vnc'', ''xauthority'': ''/root/.Xauthority'', ''uuid'': ''30b64ea4-fbf9-7e91-ab5a-4b25f22c6f8e''} [2007-10-18 15:48:49 5091] DEBUG (DevController:117) DevController: writing {''protocol'': ''x86_32-abi'', ''state'': ''1'', ''backend-id'': ''0'', ''backend'': ''/local/domain/0/backend/vfb/3/0''} to /local/domain/3/device/vfb/0. [2007-10-18 15:48:49 5091] DEBUG (DevController:119) DevController: writing {''vncunused'': ''1'', ''domain'': ''aaa'', ''frontend'': ''/local/domain/3/device/vfb/0'', ''xauthority'': ''/root/.Xauthority'', ''state'': ''1'', ''online'': ''1'', ''frontend-id'': ''3'', ''type'': ''vnc'', ''uuid'': ''30b64ea4-fbf9-7e91-ab5a-4b25f22c6f8e''} to /local/domain/0/backend/vfb/3/0. [2007-10-18 15:48:49 5091] DEBUG (vfbif:66) No VNC passwd configured for vfb access [2007-10-18 15:48:49 5091] INFO (XendDomainInfo:1409) createDevice: tap : {''bootable'': 1, ''uname'': ''tap:aio:/home/xen/aaa'', ''mode'': ''w'', ''dev'': ''xvda'', ''uuid'': ''71a7f5d3-8bca-b973-4238-a239959ddda1''} [2007-10-18 15:48:49 5091] DEBUG (DevController:117) DevController: writing {''virtual-device'': ''51712'', ''device-type'': ''disk'', ''protocol'': ''x86_32-abi'', ''backend-id'': ''0'', ''state'': ''1'', ''backend'': ''/local/domain/0/backend/tap/3/51712''} to /local/domain/3/device/vbd/51712. [2007-10-18 15:48:49 5091] DEBUG (DevController:119) DevController: writing {''domain'': ''aaa'', ''frontend'': ''/local/domain/3/device/vbd/51712'', ''uuid'': ''71a7f5d3-8bca-b973-4238-a239959ddda1'', ''dev'': ''xvda'', ''state'': ''1'', ''params'': ''aio:/home/xen/aaa'', ''mode'': ''w'', ''online'': ''1'', ''frontend-id'': ''3'', ''type'': ''tap''} to /local/domain/0/backend/tap/3/51712. [2007-10-18 15:48:49 5091] INFO (XendDomainInfo:1409) createDevice: vif : {''bridge'': ''xenbr0'', ''mac'': ''00:16:3e:12:34:a9'', ''uuid'': ''b639cf50-bec7-3793-254a-9df4b3e6a5c4''} [2007-10-18 15:48:49 5091] DEBUG (DevController:117) DevController: writing {''mac'': ''00:16:3e:12:34:a9'', ''handle'': ''0'', ''protocol'': ''x86_32-abi'', ''backend-id'': ''0'', ''state'': ''1'', ''backend'': ''/local/domain/0/backend/vif/3/0''} to /local/domain/3/device/vif/0. [2007-10-18 15:48:49 5091] DEBUG (DevController:119) DevController: writing {''bridge'': ''xenbr0'', ''domain'': ''aaa'', ''handle'': ''0'', ''uuid'': ''b639cf50-bec7-3793-254a-9df4b3e6a5c4'', ''script'': ''/etc/xen/scripts/vif-bridge'', ''state'': ''1'', ''frontend'': ''/local/domain/3/device/vif/0'', ''mac'': ''00:16:3e:12:34:a9'', ''online'': ''1'', ''frontend-id'': ''3''} to /local/domain/0/backend/vif/3/0. [2007-10-18 15:48:49 5091] DEBUG (XendDomainInfo:2067) Storing VM details: {''on_xend_stop'': ''ignore'', ''shadow_memory'': ''0'', ''uuid'': ''bee5f62b-7193-a454-e37e-a151a5be8f44'', ''on_reboot'': ''restart'', ''start_time'': ''1192702729.98'', ''on_poweroff'': ''destroy'', ''on_xend_start'': ''ignore'', ''on_crash'': ''restart'', ''xend/restart_count'': ''0'', ''vcpus'': ''7'', ''vcpu_avail'': ''127'', ''image'': "(linux (kernel ) (notes (FEATURES ''writable_page_tables|writable_descriptor_tables|auto_translated_physmap|pae_pgdir_above_4gb|supervisor_mode_kernel'') (VIRT_BASE 3221225472) (GUEST_VERSION 2.6) (PADDR_OFFSET 3221225472) (GUEST_OS linux) (HYPERCALL_PAGE 3225423872) (LOADER generic) (PAE_MODE yes) (ENTRY 3225419776) (XEN_VERSION xen-3.0)))", ''name'': ''aaa''} [2007-10-18 15:48:49 5091] DEBUG (XendDomainInfo:907) Storing domain details: {''console/ring-ref'': ''1421365'', ''image/entry'': ''3225419776'', ''console/port'': ''2'', ''cpu/3/availability'': ''online'', ''store/ring-ref'': ''1421366'', ''image/loader'': ''generic'', ''image/features/writable-page-tables'': ''1'', ''vm'': ''/vm/bee5f62b-7193-a454-e37e-a151a5be8f44'', ''control/platform-feature-multiprocessor-suspend'': ''1'', ''cpu/2/availability'': ''online'', ''cpu/1/availability'': ''online'', ''image/features/writable-descriptor-tables'': ''1'', ''image/virt-base'': ''3221225472'', ''memory/target'': ''2097152'', ''image/guest-version'': ''2.6'', ''image/features/supervisor-mode-kernel'': ''1'', ''cpu/4/availability'': ''online'', ''image/pae-mode'': ''yes'', ''image/guest-os'': ''linux'', ''console/limit'': ''1048576'', ''image/paddr-offset'': ''3221225472'', ''image/hypercall-page'': ''3225423872'', ''cpu/5/availability'': ''online'', ''cpu/0/availability'': ''online'', ''image/features/pae-pgdir-above-4gb'': ''1'', ''cpu/6/availability'': ''online'', ''image/features/auto-translated-physmap'': ''1'', ''name'': ''aaa'', ''domid'': ''3'', ''image/xen-version'': ''xen-3.0'', ''store/port'': ''1''} [2007-10-18 15:48:50 5091] DEBUG (DevController:117) DevController: writing {''protocol'': ''x86_32-abi'', ''state'': ''1'', ''backend-id'': ''0'', ''backend'': ''/local/domain/0/backend/console/3/0''} to /local/domain/3/device/console/0. [2007-10-18 15:48:50 5091] DEBUG (DevController:119) DevController: writing {''domain'': ''aaa'', ''protocol'': ''vt100'', ''uuid'': ''b9f1a7cd-6775-9210-c156-c6b6b5370cab'', ''frontend'': ''/local/domain/3/device/console/0'', ''state'': ''1'', ''location'': ''2'', ''online'': ''1'', ''frontend-id'': ''3''} to /local/domain/0/backend/console/3/0. [2007-10-18 15:48:50 5091] DEBUG (DevController:150) Waiting for devices vif. [2007-10-18 15:48:50 5091] DEBUG (DevController:155) Waiting for 0. [2007-10-18 15:48:50 5091] DEBUG (XendDomainInfo:991) XendDomainInfo.handleShutdownWatch [2007-10-18 15:48:50 5091] DEBUG (DevController:577) hotplugStatusCallback /local/domain/0/backend/vif/3/0/hotplug-status. [2007-10-18 15:48:50 5091] DEBUG (DevController:577) hotplugStatusCallback /local/domain/0/backend/vif/3/0/hotplug-status. [2007-10-18 15:48:50 5091] DEBUG (DevController:591) hotplugStatusCallback 1. [2007-10-18 15:48:50 5091] DEBUG (DevController:150) Waiting for devices usb. [2007-10-18 15:48:50 5091] DEBUG (DevController:150) Waiting for devices vbd. [2007-10-18 15:48:50 5091] DEBUG (DevController:150) Waiting for devices irq. [2007-10-18 15:48:50 5091] DEBUG (DevController:150) Waiting for devices vkbd. [2007-10-18 15:48:50 5091] DEBUG (DevController:155) Waiting for 0. [2007-10-18 15:48:50 5091] DEBUG (DevController:577) hotplugStatusCallback /local/domain/0/backend/vkbd/3/0/hotplug-status. Any recommendations on how to go about this now ? Thanks. -- regards, Anand Gupta _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Thanks for the reply Daniel. On 10/17/07, Daniel P. Berrange <berrange@redhat.com> wrote:> > > > Here is the error i get > > > > > > xm create aaa > > > Using config file "./aaa". > > > Error: (22, ''Invalid argument'') > > > > Hmmm, not a very helpful error message! The contents of > /var/log/xen/xend.log > > may yield more helpful hints. > > Yep, Xen 3.0.3 wasn''t great at reporting errors. This one basically means > you used a bogus guest kernel - eg > > - A non-PAE 32-bit kernel > - A bare metal kernel in a paravirt config > - Wrong architecture kernel (eg 32 on 64, or 64 on 32) >This error was received under xen 3.1 and not under 3.0.3. The image i am trying to boot was created using virt-manager / rhel tools. The domain created was paravirtualized, and NOT fully virtualized. However later the error was resolved, as pointed by Mark, it was caused by having both xen 3.0.3 and xen 3.1 installed. Once old xen rpm was removed, the error went off, however now when trying to boot the old image with the old xen config file, results in screen hangup just after the pygrub kernel choice screen. The server is basically a Quad Core Xeon 1.86Ghz with 4GB Ram, Areca Raid Card with Raid 1 on 160 X 2 Drives. Any ideas on how this problem can be resolved ? Thanks. -- regards, Anand Gupta _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
For what its worth, i got the image to boot finally by adding the below lines in the config file vnc = 0 nographic = 1 serial = ''pty'' stdvga = 1 Very strange, since i haven''t found the above options anywhere and were given to me by a friend of mine also working on xen + centos5. Without the above lines, the image keeps on giving the error, and won''t boot. Just wondering why these lines aren''t required when using centos5 xen packages. -- regards, Anand Gupta _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Anand Gupta wrote:> For what its worth, i got the image to boot finally by adding the > below lines in the config file > > vnc = 0 > nographic = 1 > serial = ''pty'' > stdvga = 1 > > Very strange, since i haven''t found the above options anywhere and > were given to me by a friend of mine also working on xen + centos5. > Without the above lines, the image keeps on giving the error, and > won''t boot. > > Just wondering why these lines aren''t required when using centos5 xen > packages. > > --Poor documentation of the system defaults or the available options is a problem for a *lot* of software. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Sun October 28 2007 6:28:03 am Anand Gupta wrote:> Very strange, since i haven''t found the above options anywhere and were > given to me by a friend of mine also working on xen + centos5. Without the > above lines, the image keeps on giving the error, and won''t boot.Try looking for xmexample.hvm: /etc/xen/examples/xmexample.hvm in SuSE, /etc/xen/xmexample.hvm in fedora. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Sun, Oct 28, 2007 at 03:58:03PM +0530, Anand Gupta wrote:> For what its worth, i got the image to boot finally by adding the below > lines in the config file > > vnc = 0 > nographic = 1 > serial = ''pty'' > stdvga = 1 > > Very strange, since i haven''t found the above options anywhere and were > given to me by a friend of mine also working on xen + centos5. Without the > above lines, the image keeps on giving the error, and won''t boot. > > Just wondering why these lines aren''t required when using centos5 xen > packages.They''re not required, because they''re not required. That combo of lines happens to setup the guest in text mode with a serial console, but that''s just one of many ways of configuring a guest. Certain badly behaved guest OS require a specific combo of options, but most don''t care at all. Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 10/28/07, Daniel P. Berrange <berrange@redhat.com> wrote:> > They''re not required, because they''re not required. That combo of lines > happens to setup the guest in text mode with a serial console, but that''s > just one of many ways of configuring a guest. Certain badly behaved guest > OS require a specific combo of options, but most don''t care at all.How can you say the guest is badly setup ? I used virt-manager to install a fresh centos5 pv domain using file based image, gave it the installation CD to use. It installed perfectly fine and was working also fine. Unless virt-manager itself creates a badly behaved guest ? And then once i remove centos5 xen packages, virt-manager, compile xen 3.1.1, the image stopped booting. Once i add those lines, it starts to work again. wondering... -- regards, Anand Gupta _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 10/28/07, jim burns <jim_burn@bellsouth.net> wrote:> > On Sun October 28 2007 6:28:03 am Anand Gupta wrote: > > Very strange, since i haven''t found the above options anywhere and were > > given to me by a friend of mine also working on xen + centos5. Without > the > > above lines, the image keeps on giving the error, and won''t boot. > > Try looking for xmexample.hvm: /etc/xen/examples/xmexample.hvm in SuSE, > /etc/xen/xmexample.hvm in fedora. >Since i don''t have access to either of them, i can''t look at them. Moreover i installed a PV domain, using virt-manager in centos. -- regards, Anand Gupta _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Anand Gupta wrote:> On 10/28/07, *Daniel P. Berrange* <berrange@redhat.com > <mailto:berrange@redhat.com>> wrote: > > They''re not required, because they''re not required. That combo of > lines > happens to setup the guest in text mode with a serial console, but > that''s > just one of many ways of configuring a guest. Certain badly > behaved guest > OS require a specific combo of options, but most don''t care at all. > > > How can you say the guest is badly setup ? I used virt-manager to > install a fresh centos5 pv domain using file based image, gave it the > installation CD to use. It installed perfectly fine and was working > also fine. Unless virt-manager itself creates a badly behaved guest ? > > And then once i remove centos5 xen packages, virt-manager, compile xen > 3.1.1, the image stopped booting. Once i add those lines, it starts to > work again. > > wondering...Switching from a compiled configuration for *one* version of Xen, namely 3.0.x for CentOS 5, to another verson of Xen, namely 3.1.1, is sort of asking for backwards compatibility trouble. I''m afraid such problems are likely to recur with hand-implemented Xen migrations to more recent releases, at least until RedHat has decided to update to it. And that''s unlikely for RHEL 5: the stability of such OS version sis a big selling point for RedHat. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> > Try looking for xmexample.hvm: /etc/xen/examples/xmexample.hvm in SuSE, > > /etc/xen/xmexample.hvm in fedora. > > Since i don''t have access to either of them, i can''t look at them. Moreover > i installed a PV domain, using virt-manager in centos.Well, they''re available in CentOS too - the location is the same as on Fedora. It''s actually quite handy to look at the various xmexample files for details of the syntax and the options available. Even though I work on Xen all the time, I still do it occasionally when trying out new features. Anyhow, possibly the difference is that before you were using a CentOS-customised Xen kernel which had certain preset defaults compiled in. virt-manager is primarily a RHEL / CentOS / Fedora tool, so perhaps it assumes these defaults and doesn''t create entries for them? Since you''re using 3rd party (i.e. XenSource) provided kernels, they probably provide different defaults which therefore need overriding with those options. Cheers, Mark -- Dave: Just a question. What use is a unicyle with no seat? And no pedals! Mark: To answer a question with a question: What use is a skateboard? Dave: Skateboards have wheels. Mark: My wheel has a wheel! _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 10/30/07, Mark Williamson <mark.williamson@cl.cam.ac.uk> wrote:> > > > Try looking for xmexample.hvm: /etc/xen/examples/xmexample.hvm in > SuSE, > > > /etc/xen/xmexample.hvm in fedora. > > > > Since i don''t have access to either of them, i can''t look at them. > Moreover > > i installed a PV domain, using virt-manager in centos. > > Well, they''re available in CentOS too - the location is the same as on > Fedora. > It''s actually quite handy to look at the various xmexample files for > details > of the syntax and the options available. Even though I work on Xen all > the > time, I still do it occasionally when trying out new features.Thanks will look up. Anyhow, possibly the difference is that before you were using a> CentOS-customised Xen kernel which had certain preset defaults compiled > in. > virt-manager is primarily a RHEL / CentOS / Fedora tool, so perhaps it > assumes these defaults and doesn''t create entries for them? > > Since you''re using 3rd party (i.e. XenSource) provided kernels, they > probably > provide different defaults which therefore need overriding with those > options. >No i am not using xensource kernel. I have compiled the kernel as well. I downloaded and compiled xen 3.1.1, with kernel 2.6.18. -- regards, Anand Gupta _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Found the below parameters in xmexample.hvm vnc = 0 nographic = 1 serial = ''pty'' stdvga = 1 What surprises me is that the domU i am using is a PV image, why would it have an effect from any of the hvm settings. -- regards, Anand Gupta _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users