Hey, Is it possible to covert a .img to a xva? I have a virtual machine on a xen machine that i would like to run in a xen cloud. I used the xva.py and it gave me a xva + kernel i followed the copy instructions but i get this: [root@box ~]# xe vm-start vm=converted Error code: WARNING: /dev/xvda is not a disk image Error parameters: Traceback (most recent call last):, File "/usr/bin/pygrub", line 746, in ?, raise RuntimeError, "Unable to find partition containing kernel", RuntimeError: Unable to find partition containing kernel, Any pointers on this? Thanks, Peter _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
You have to convert your VM. You can use this tool: http://www.xen.org/files/xva/xva.py Regards, FG Da: xen-users-bounces@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] Per conto di Peter den Hartog Inviato: lunedì 15 novembre 2010 14:36 A: xen-users@lists.xensource.com Oggetto: [Xen-users] [XCP] converting a .img to xva Hey, Is it possible to covert a .img to a xva? I have a virtual machine on a xen machine that i would like to run in a xen cloud. I used the xva.py and it gave me a xva + kernel i followed the copy instructions but i get this: [root@box ~]# xe vm-start vm=converted Error code: WARNING: /dev/xvda is not a disk image Error parameters: Traceback (most recent call last):, File "/usr/bin/pygrub", line 746, in ?, raise RuntimeError, "Unable to find partition containing kernel", RuntimeError: Unable to find partition containing kernel, Any pointers on this? Thanks, Peter _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I did that :-) i used the following line: ~/Scripts/xcp-xva-convert/xva.py --config=xen.cfg --filename=converted.xva It gave me a couple of files and some instructions to SCP stuff, i also did that.. But still those errors while booting. On Mon, Nov 15, 2010 at 2:39 PM, <cluster@xinet.it> wrote:> You have to convert your VM. You can use this tool: > > > > http://www.xen.org/files/xva/xva.py > > > > Regards, > > FG > > > > > > *Da:* xen-users-bounces@lists.xensource.com [mailto: > xen-users-bounces@lists.xensource.com] *Per conto di *Peter den Hartog > *Inviato:* lunedì 15 novembre 2010 14:36 > *A:* xen-users@lists.xensource.com > *Oggetto:* [Xen-users] [XCP] converting a .img to xva > > > > Hey, > > > > Is it possible to covert a .img to a xva? > > I have a virtual machine on a xen machine that i would like to run in a xen > cloud. > > > > I used the xva.py and it gave me a xva + kernel i followed the copy > instructions but i get this: > > > > [root@box ~]# xe vm-start vm=converted > > Error code: WARNING: /dev/xvda is not a disk image > > Error parameters: Traceback (most recent call last):, File > "/usr/bin/pygrub", line 746, in ?, raise RuntimeError, "Unable to find > partition containing kernel", RuntimeError: Unable to find partition > containing kernel, > > > > Any pointers on this? > > > > Thanks, > > Peter >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Mon, Nov 15, 2010 at 8:35 AM, Peter den Hartog <peterdenhartog@gmail.com> wrote:> Hey, > Is it possible to covert a .img to a xva? > I have a virtual machine on a xen machine that i would like to run in a xen > cloud. > I used the xva.py and it gave me a xva + kernel i followed the copy > instructions but i get this: > [root@box ~]# xe vm-start vm=converted > Error code: WARNING: /dev/xvda is not a disk image > Error parameters: Traceback (most recent call last):, File > "/usr/bin/pygrub", line 746, in ?, raise RuntimeError, "Unable to find > partition containing kernel", RuntimeError: Unable to find partition > containing kernel, > Any pointers on this?From: http://www.xen.org/files/xva/README "Report bugs to xen-devel or david.markey@citrix.com" Also, did you read carefully the README for instructions and caveats? The process is not as simple as just running the commands. Hope that helps. Thanks, Todd -- Todd Deshane http://todddeshane.net http://runningxen.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Of course i did ;-) I did it correctly because the script creates the file. I''m now trying the xvda thing, i''ll let you know if it worked or not. Thanks, Peter On Mon, Nov 15, 2010 at 3:52 PM, Todd Deshane <deshantm@gmail.com> wrote:> On Mon, Nov 15, 2010 at 8:35 AM, Peter den Hartog > <peterdenhartog@gmail.com> wrote: > > Hey, > > Is it possible to covert a .img to a xva? > > I have a virtual machine on a xen machine that i would like to run in a > xen > > cloud. > > I used the xva.py and it gave me a xva + kernel i followed the copy > > instructions but i get this: > > [root@box ~]# xe vm-start vm=converted > > Error code: WARNING: /dev/xvda is not a disk image > > Error parameters: Traceback (most recent call last):, File > > "/usr/bin/pygrub", line 746, in ?, raise RuntimeError, "Unable to > find > > partition containing kernel", RuntimeError: Unable to find partition > > containing kernel, > > Any pointers on this? > > From: > http://www.xen.org/files/xva/README > > "Report bugs to xen-devel or david.markey@citrix.com" > > Also, did you read carefully the README for instructions and caveats? > > The process is not as simple as just running the commands. > > Hope that helps. > > Thanks, > Todd > > -- > Todd Deshane > http://todddeshane.net > http://runningxen.com >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi, a small question.. I''m trying to convert a .img from a xen system to a xva for my XCP system. I did the following -> Somebody send me a local copy of the .img including all the needed files (kernel/config). I eddited the xen.conf to point to the correct locations of my files it now looks like this: # Kernel image file. kernel "/home/peter/xcp-convert/centos-5.0-x86_64-build-A/kernel/boot/vmlinuz-2.6.18-xen" ramdisk "/home/peter/xcp-convert/centos-5.0-x86_64-build-A/kernel/boot/initrd-2.6-xen.img" # Initial memory allocation (in megabytes) for the new domain. memory = 512 #---------------------------------------------------------------------------- # 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 = [ ''file:/home/peter/xcp-convert/2.1-centos-5.0-x86_64-build-A/disks/disk.img,sda1,w'',''file:/home/peter/xcp-convert/centos-5.0-x86_64-build-A/disks/swap.img,sda2,w'' ] # Sets runlevel. extra = "3" # A name for your domain. All domains must have different names. name = "centos-5.0-x86_64-build-A" # Number of network interfaces. Default is 1. nics=1 Then i runned the script, at it seemed to work: ~/Scripts/xcp-xva-convert/xva.py --config=xen.cfg --filename=converted.xva After a installation, and a succesfull import (+ copy like the echo told me to) i''m not able to start it: [root@box 80edf9c0-f0c3-11df-afb8-002185fade1c]# xe vm-start vm=centos-5.0-x86_64-build-A Error code: WARNING: /dev/xvda is not a disk image Error parameters: Traceback (most recent call last):, File "/usr/bin/pygrub", line 746, in ?, raise RuntimeError, "Unable to find partition containing kernel", RuntimeError: Unable to find partition containing kernel, [root@box 80edf9c0-f0c3-11df-afb8-002185fade1c]# I asked this on the normal mailing list but they pointed me to this direction. Hope you can help me, thanks, Peter _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
What filesystem is within the VM? On 15 November 2010 16:02, Peter den Hartog <peterdenhartog@gmail.com>wrote:> Hi, a small question.. > I''m trying to convert a .img from a xen system to a xva for my XCP system. > > I did the following -> > Somebody send me a local copy of the .img including all the needed files > (kernel/config). > I eddited the xen.conf to point to the correct locations of my files it now > looks like this: > > # Kernel image file. > kernel > "/home/peter/xcp-convert/centos-5.0-x86_64-build-A/kernel/boot/vmlinuz-2.6.18-xen" > ramdisk > "/home/peter/xcp-convert/centos-5.0-x86_64-build-A/kernel/boot/initrd-2.6-xen.img" > > # Initial memory allocation (in megabytes) for the new domain. > memory = 512 > > > #---------------------------------------------------------------------------- > # 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 = [ > ''file:/home/peter/xcp-convert/2.1-centos-5.0-x86_64-build-A/disks/disk.img,sda1,w'',''file:/home/peter/xcp-convert/centos-5.0-x86_64-build-A/disks/swap.img,sda2,w'' > ] > > # Sets runlevel. > extra = "3" > > # A name for your domain. All domains must have different names. > name = "centos-5.0-x86_64-build-A" > > # Number of network interfaces. Default is 1. > nics=1 > > > Then i runned the script, at it seemed to work: > ~/Scripts/xcp-xva-convert/xva.py --config=xen.cfg --filename=converted.xva > > After a installation, and a succesfull import (+ copy like the echo told > me to) i''m not able to start it: > > [root@box 80edf9c0-f0c3-11df-afb8-002185fade1c]# xe vm-start > vm=centos-5.0-x86_64-build-A > Error code: WARNING: /dev/xvda is not a disk image > Error parameters: Traceback (most recent call last):, File > "/usr/bin/pygrub", line 746, in ?, raise RuntimeError, "Unable to find > partition containing kernel", RuntimeError: Unable to find partition > containing kernel, > [root@box 80edf9c0-f0c3-11df-afb8-002185fade1c]# > > I asked this on the normal mailing list but they pointed me to this > direction. > > Hope you can help me, thanks, > Peter > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
It''s ext3 On Tue, Nov 16, 2010 at 10:44 AM, David Markey <admin@dmarkey.com> wrote:> What filesystem is within the VM? > > On 15 November 2010 16:02, Peter den Hartog <peterdenhartog@gmail.com>wrote: > >> Hi, a small question.. >> I''m trying to convert a .img from a xen system to a xva for my XCP system. >> >> I did the following -> >> Somebody send me a local copy of the .img including all the needed files >> (kernel/config). >> I eddited the xen.conf to point to the correct locations of my files it >> now looks like this: >> >> # Kernel image file. >> kernel >> "/home/peter/xcp-convert/centos-5.0-x86_64-build-A/kernel/boot/vmlinuz-2.6.18-xen" >> ramdisk >> "/home/peter/xcp-convert/centos-5.0-x86_64-build-A/kernel/boot/initrd-2.6-xen.img" >> >> # Initial memory allocation (in megabytes) for the new domain. >> memory = 512 >> >> >> #---------------------------------------------------------------------------- >> # 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 = [ >> ''file:/home/peter/xcp-convert/2.1-centos-5.0-x86_64-build-A/disks/disk.img,sda1,w'',''file:/home/peter/xcp-convert/centos-5.0-x86_64-build-A/disks/swap.img,sda2,w'' >> ] >> >> # Sets runlevel. >> extra = "3" >> >> # A name for your domain. All domains must have different names. >> name = "centos-5.0-x86_64-build-A" >> >> # Number of network interfaces. Default is 1. >> nics=1 >> >> >> Then i runned the script, at it seemed to work: >> ~/Scripts/xcp-xva-convert/xva.py --config=xen.cfg --filename=converted.xva >> >> After a installation, and a succesfull import (+ copy like the echo told >> me to) i''m not able to start it: >> >> [root@box 80edf9c0-f0c3-11df-afb8-002185fade1c]# xe vm-start >> vm=centos-5.0-x86_64-build-A >> Error code: WARNING: /dev/xvda is not a disk image >> Error parameters: Traceback (most recent call last):, File >> "/usr/bin/pygrub", line 746, in ?, raise RuntimeError, "Unable to find >> partition containing kernel", RuntimeError: Unable to find partition >> containing kernel, >> [root@box 80edf9c0-f0c3-11df-afb8-002185fade1c]# >> >> I asked this on the normal mailing list but they pointed me to this >> direction. >> >> Hope you can help me, thanks, >> Peter >> >> >> _______________________________________________ >> Xen-devel mailing list >> Xen-devel@lists.xensource.com >> http://lists.xensource.com/xen-devel >> >> >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Can I see a xe vm-list params=all uuid=<new vm uuid> On 16 November 2010 09:52, Peter den Hartog <peterdenhartog@gmail.com>wrote:> It''s ext3 > > > On Tue, Nov 16, 2010 at 10:44 AM, David Markey <admin@dmarkey.com> wrote: > >> What filesystem is within the VM? >> >> On 15 November 2010 16:02, Peter den Hartog <peterdenhartog@gmail.com>wrote: >> >>> Hi, a small question.. >>> I''m trying to convert a .img from a xen system to a xva for my XCP >>> system. >>> >>> I did the following -> >>> Somebody send me a local copy of the .img including all the needed files >>> (kernel/config). >>> I eddited the xen.conf to point to the correct locations of my files it >>> now looks like this: >>> >>> # Kernel image file. >>> kernel >>> "/home/peter/xcp-convert/centos-5.0-x86_64-build-A/kernel/boot/vmlinuz-2.6.18-xen" >>> ramdisk >>> "/home/peter/xcp-convert/centos-5.0-x86_64-build-A/kernel/boot/initrd-2.6-xen.img" >>> >>> # Initial memory allocation (in megabytes) for the new domain. >>> memory = 512 >>> >>> >>> #---------------------------------------------------------------------------- >>> # 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 = [ >>> ''file:/home/peter/xcp-convert/2.1-centos-5.0-x86_64-build-A/disks/disk.img,sda1,w'',''file:/home/peter/xcp-convert/centos-5.0-x86_64-build-A/disks/swap.img,sda2,w'' >>> ] >>> >>> # Sets runlevel. >>> extra = "3" >>> >>> # A name for your domain. All domains must have different names. >>> name = "centos-5.0-x86_64-build-A" >>> >>> # Number of network interfaces. Default is 1. >>> nics=1 >>> >>> >>> Then i runned the script, at it seemed to work: >>> ~/Scripts/xcp-xva-convert/xva.py --config=xen.cfg >>> --filename=converted.xva >>> >>> After a installation, and a succesfull import (+ copy like the echo told >>> me to) i''m not able to start it: >>> >>> [root@box 80edf9c0-f0c3-11df-afb8-002185fade1c]# xe vm-start >>> vm=centos-5.0-x86_64-build-A >>> Error code: WARNING: /dev/xvda is not a disk image >>> Error parameters: Traceback (most recent call last):, File >>> "/usr/bin/pygrub", line 746, in ?, raise RuntimeError, "Unable to find >>> partition containing kernel", RuntimeError: Unable to find partition >>> containing kernel, >>> [root@box 80edf9c0-f0c3-11df-afb8-002185fade1c]# >>> >>> I asked this on the normal mailing list but they pointed me to this >>> direction. >>> >>> Hope you can help me, thanks, >>> Peter >>> >>> >>> _______________________________________________ >>> Xen-devel mailing list >>> Xen-devel@lists.xensource.com >>> http://lists.xensource.com/xen-devel >>> >>> >> >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Sure thing: [root@noc ~]# xe vm-list params=all uuid=d7596836-675e-6e79-f927-7b852a691785 uuid ( RO) : d7596836-675e-6e79-f927-7b852a691785 name-label ( RW): centos-5.0-x86_64-build-A name-description ( RW): user-version ( RW): 1 is-a-template ( RW): false is-a-snapshot ( RO): false snapshot-of ( RO): <not in database> snapshots ( RO): snapshot-time ( RO): 19700101T00:00:00Z snapshot-info ( RO): parent ( RO): <not in database> children ( RO): is-control-domain ( RO): false power-state ( RO): halted memory-actual ( RO): 0 memory-target ( RO): <expensive field> memory-overhead ( RO): 1048576 memory-static-max ( RW): 536870912 memory-dynamic-max ( RW): 536870912 memory-dynamic-min ( RW): 536870912 memory-static-min ( RW): 16777216 suspend-VDI-uuid ( RO): <not in database> VCPUs-params (MRW): VCPUs-max ( RW): 1 VCPUs-at-startup ( RW): 1 actions-after-shutdown ( RW): Destroy actions-after-reboot ( RW): Restart actions-after-crash ( RW): Restart console-uuids (SRO): platform (MRW): nx: false; acpi: true; apic: true; pae: true; viridian: true allowed-operations (SRO): changing_dynamic_range; changing_static_range; make_into_template; destroy; export; start_on; start; clone; copy; snapshot current-operations (SRO): blocked-operations (MRW): allowed-VBD-devices (SRO): <expensive field> allowed-VIF-devices (SRO): <expensive field> possible-hosts ( RO): <expensive field> HVM-boot-policy ( RW): HVM-boot-params (MRW): order: dc HVM-shadow-multiplier ( RW): 1.000 PV-kernel ( RW): /boot/guest/80edf9c0-f0c3-11df-afb8-002185fade1c/vmlinuz PV-ramdisk ( RW): /boot/guest/80edf9c0-f0c3-11df-afb8-002185fade1c/initrd PV-args ( RW): root=/dev/sda1 ro selinux=0 3 PV-legacy-args ( RW): PV-bootloader ( RW): pygrub PV-bootloader-args ( RW): last-boot-CPU-flags ( RO): last-boot-record ( RO): <expensive field> resident-on ( RO): <not in database> affinity ( RW): <not in database> other-config (MRW): import_task: OpaqueRef:733508e8-adaf-748a-eb5d-5748cd8092bc; mac_seed: 396e5d3f-afee-4b58-f053-c94db4e2e0af; install-methods: cdrom dom-id ( RO): -1 recommendations ( RO): <restrictions><restriction field="memory-static-max" max="34359738368" /><restriction field="vcpus-max" max="8" /><restriction property="number-of-vbds" max="7" /><restriction property="number-of-vifs" max="7" /></restrictions> xenstore-data (MRW): ha-always-run ( RW): false ha-restart-priority ( RW): blobs ( RO): start-time ( RO): 19700101T00:00:00Z install-time ( RO): 19700101T00:00:00Z VCPUs-number ( RO): 0 VCPUs-utilisation (MRO): <expensive field> os-version (MRO): <not in database> PV-drivers-version (MRO): <not in database> PV-drivers-up-to-date ( RO): <not in database> memory (MRO): <not in database> disks (MRO): <not in database> networks (MRO): <not in database> other (MRO): <not in database> live ( RO): <not in database> guest-metrics-last-updated ( RO): <not in database> cooperative ( RO): <expensive field> [root@box ~]# On Tue, Nov 16, 2010 at 11:05 AM, David Markey <admin@dmarkey.com> wrote:> Can I see a xe vm-list params=all uuid=<new vm uuid> > > > On 16 November 2010 09:52, Peter den Hartog <peterdenhartog@gmail.com>wrote: > >> It''s ext3 >> >> >> On Tue, Nov 16, 2010 at 10:44 AM, David Markey <admin@dmarkey.com> wrote: >> >>> What filesystem is within the VM? >>> >>> On 15 November 2010 16:02, Peter den Hartog <peterdenhartog@gmail.com>wrote: >>> >>>> Hi, a small question.. >>>> I''m trying to convert a .img from a xen system to a xva for my XCP >>>> system. >>>> >>>> I did the following -> >>>> Somebody send me a local copy of the .img including all the needed files >>>> (kernel/config). >>>> I eddited the xen.conf to point to the correct locations of my files it >>>> now looks like this: >>>> >>>> # Kernel image file. >>>> kernel >>>> "/home/peter/xcp-convert/centos-5.0-x86_64-build-A/kernel/boot/vmlinuz-2.6.18-xen" >>>> ramdisk >>>> "/home/peter/xcp-convert/centos-5.0-x86_64-build-A/kernel/boot/initrd-2.6-xen.img" >>>> >>>> # Initial memory allocation (in megabytes) for the new domain. >>>> memory = 512 >>>> >>>> >>>> #---------------------------------------------------------------------------- >>>> # 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 = [ >>>> ''file:/home/peter/xcp-convert/2.1-centos-5.0-x86_64-build-A/disks/disk.img,sda1,w'',''file:/home/peter/xcp-convert/centos-5.0-x86_64-build-A/disks/swap.img,sda2,w'' >>>> ] >>>> >>>> # Sets runlevel. >>>> extra = "3" >>>> >>>> # A name for your domain. All domains must have different names. >>>> name = "centos-5.0-x86_64-build-A" >>>> >>>> # Number of network interfaces. Default is 1. >>>> nics=1 >>>> >>>> >>>> Then i runned the script, at it seemed to work: >>>> ~/Scripts/xcp-xva-convert/xva.py --config=xen.cfg >>>> --filename=converted.xva >>>> >>>> After a installation, and a succesfull import (+ copy like the echo >>>> told me to) i''m not able to start it: >>>> >>>> [root@box 80edf9c0-f0c3-11df-afb8-002185fade1c]# xe vm-start >>>> vm=centos-5.0-x86_64-build-A >>>> Error code: WARNING: /dev/xvda is not a disk image >>>> Error parameters: Traceback (most recent call last):, File >>>> "/usr/bin/pygrub", line 746, in ?, raise RuntimeError, "Unable to find >>>> partition containing kernel", RuntimeError: Unable to find partition >>>> containing kernel, >>>> [root@box 80edf9c0-f0c3-11df-afb8-002185fade1c]# >>>> >>>> I asked this on the normal mailing list but they pointed me to this >>>> direction. >>>> >>>> Hope you can help me, thanks, >>>> Peter >>>> >>>> >>>> _______________________________________________ >>>> Xen-devel mailing list >>>> Xen-devel@lists.xensource.com >>>> http://lists.xensource.com/xen-devel >>>> >>>> >>> >> >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
xe vm-param-set PV-bootloader= uuid=d7596836-675e-6e79-f927-7b852a691785 On 16 November 2010 12:31, Peter den Hartog <peterdenhartog@gmail.com>wrote:> PV-bootloader_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Thanks, that got me a bit further. It boots now, but after a couple of seconds i get a kernel panic. No info on booting up tho, and the console closes to fast :-). Any place where i can find the error message? Thanks, Peter On Tue, Nov 16, 2010 at 2:24 PM, David Markey <admin@dmarkey.com> wrote:> xe vm-param-set PV-bootloader= uuid=d7596836-675e-6e79-f927-7b852a691785 > > > On 16 November 2010 12:31, Peter den Hartog <peterdenhartog@gmail.com>wrote: > >> PV-bootloader > > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
try: xe vm-param-set PV-args="console=xvc0" or xe vm-param-set PV-args="console=hvc0" On 16 November 2010 13:36, Peter den Hartog <peterdenhartog@gmail.com>wrote:> Thanks, that got me a bit further. It boots now, but after a couple of > seconds i get a kernel panic. > No info on booting up tho, and the console closes to fast :-). > > Any place where i can find the error message? > > Thanks, > Peter > > > On Tue, Nov 16, 2010 at 2:24 PM, David Markey <admin@dmarkey.com> wrote: > >> xe vm-param-set PV-bootloader= uuid=d7596836-675e-6e79-f927-7b852a691785 >> >> >> On 16 November 2010 12:31, Peter den Hartog <peterdenhartog@gmail.com>wrote: >> >>> PV-bootloader >> >> >> >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
No luck, it boots to the same point: "Waiting for driver initializing.." Then i get a short kernel panic message but the console dies to fast to see what it is. Thanks, Peter On Tue, Nov 16, 2010 at 3:18 PM, David Markey <admin@dmarkey.com> wrote:> try: > > xe vm-param-set PV-args="console=xvc0" > > or > xe vm-param-set PV-args="console=hvc0" > > On 16 November 2010 13:36, Peter den Hartog <peterdenhartog@gmail.com>wrote: > >> Thanks, that got me a bit further. It boots now, but after a couple of >> seconds i get a kernel panic. >> No info on booting up tho, and the console closes to fast :-). >> >> Any place where i can find the error message? >> >> Thanks, >> Peter >> >> >> On Tue, Nov 16, 2010 at 2:24 PM, David Markey <admin@dmarkey.com> wrote: >> >>> xe vm-param-set PV-bootloader= uuid>>> d7596836-675e-6e79-f927-7b852a691785 >>> >>> >>> On 16 November 2010 12:31, Peter den Hartog <peterdenhartog@gmail.com>wrote: >>> >>>> PV-bootloader >>> >>> >>> >> >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Its possible you dont have xen-blockfnt in your initrd, can you check this? On 16 November 2010 14:31, Peter den Hartog <peterdenhartog@gmail.com>wrote:> No luck, it boots to the same point: > "Waiting for driver initializing.." > > Then i get a short kernel panic message but the console dies to fast to see > what it is. > > Thanks, > Peter > > > On Tue, Nov 16, 2010 at 3:18 PM, David Markey <admin@dmarkey.com> wrote: > >> try: >> >> xe vm-param-set PV-args="console=xvc0" >> >> or >> xe vm-param-set PV-args="console=hvc0" >> >> On 16 November 2010 13:36, Peter den Hartog <peterdenhartog@gmail.com>wrote: >> >>> Thanks, that got me a bit further. It boots now, but after a couple of >>> seconds i get a kernel panic. >>> No info on booting up tho, and the console closes to fast :-). >>> >>> Any place where i can find the error message? >>> >>> Thanks, >>> Peter >>> >>> >>> On Tue, Nov 16, 2010 at 2:24 PM, David Markey <admin@dmarkey.com> wrote: >>> >>>> xe vm-param-set PV-bootloader= uuid>>>> d7596836-675e-6e79-f927-7b852a691785 >>>> >>>> >>>> On 16 November 2010 12:31, Peter den Hartog <peterdenhartog@gmail.com>wrote: >>>> >>>>> PV-bootloader >>>> >>>> >>>> >>> >> >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Would love to check that, how do i do that, just mount it on my local machine? On Tue, Nov 16, 2010 at 3:37 PM, David Markey <admin@dmarkey.com> wrote:> Its possible you dont have xen-blockfnt in your initrd, can you check this? > > > On 16 November 2010 14:31, Peter den Hartog <peterdenhartog@gmail.com>wrote: > >> No luck, it boots to the same point: >> "Waiting for driver initializing.." >> >> Then i get a short kernel panic message but the console dies to fast to >> see what it is. >> >> Thanks, >> Peter >> >> >> On Tue, Nov 16, 2010 at 3:18 PM, David Markey <admin@dmarkey.com> wrote: >> >>> try: >>> >>> xe vm-param-set PV-args="console=xvc0" >>> >>> or >>> xe vm-param-set PV-args="console=hvc0" >>> >>> On 16 November 2010 13:36, Peter den Hartog <peterdenhartog@gmail.com>wrote: >>> >>>> Thanks, that got me a bit further. It boots now, but after a couple of >>>> seconds i get a kernel panic. >>>> No info on booting up tho, and the console closes to fast :-). >>>> >>>> Any place where i can find the error message? >>>> >>>> Thanks, >>>> Peter >>>> >>>> >>>> On Tue, Nov 16, 2010 at 2:24 PM, David Markey <admin@dmarkey.com>wrote: >>>> >>>>> xe vm-param-set PV-bootloader= uuid>>>>> d7596836-675e-6e79-f927-7b852a691785 >>>>> >>>>> >>>>> On 16 November 2010 12:31, Peter den Hartog <peterdenhartog@gmail.com>wrote: >>>>> >>>>>> PV-bootloader >>>>> >>>>> >>>>> >>>> >>> >> >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Look in: /boot/guest/80edf9c0-f0c3-11df-afb8-002185fade1c/initrd use gunzip and cpio. *BE CAREFUL WITH CPIO* On 17 November 2010 15:37, Peter den Hartog <peterdenhartog@gmail.com>wrote:> Would love to check that, how do i do that, just mount it on my local > machine? > > > On Tue, Nov 16, 2010 at 3:37 PM, David Markey <admin@dmarkey.com> wrote: > >> Its possible you dont have xen-blockfnt in your initrd, can you check >> this? >> >> >> On 16 November 2010 14:31, Peter den Hartog <peterdenhartog@gmail.com>wrote: >> >>> No luck, it boots to the same point: >>> "Waiting for driver initializing.." >>> >>> Then i get a short kernel panic message but the console dies to fast to >>> see what it is. >>> >>> Thanks, >>> Peter >>> >>> >>> On Tue, Nov 16, 2010 at 3:18 PM, David Markey <admin@dmarkey.com> wrote: >>> >>>> try: >>>> >>>> xe vm-param-set PV-args="console=xvc0" >>>> >>>> or >>>> xe vm-param-set PV-args="console=hvc0" >>>> >>>> On 16 November 2010 13:36, Peter den Hartog <peterdenhartog@gmail.com>wrote: >>>> >>>>> Thanks, that got me a bit further. It boots now, but after a couple of >>>>> seconds i get a kernel panic. >>>>> No info on booting up tho, and the console closes to fast :-). >>>>> >>>>> Any place where i can find the error message? >>>>> >>>>> Thanks, >>>>> Peter >>>>> >>>>> >>>>> On Tue, Nov 16, 2010 at 2:24 PM, David Markey <admin@dmarkey.com>wrote: >>>>> >>>>>> xe vm-param-set PV-bootloader= uuid>>>>>> d7596836-675e-6e79-f927-7b852a691785 >>>>>> >>>>>> >>>>>> On 16 November 2010 12:31, Peter den Hartog <peterdenhartog@gmail.com >>>>>> > wrote: >>>>>> >>>>>>> PV-bootloader >>>>>> >>>>>> >>>>>> >>>>> >>>> >>> >> >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Okay i did that, [root@box-netwerk 80edf9c0-f0c3-11df-afb8-002185fade1c]# ls bin dev etc init initrd lib proc sbin sys sysroot vmlinuz [root@box-netwerk 80edf9c0-f0c3-11df-afb8-002185fade1c]# find . -name "xen-blockfnt" [root@box-netwerk 80edf9c0-f0c3-11df-afb8-002185fade1c]# So it''s not there i''m afraid.. On Wed, Nov 17, 2010 at 4:47 PM, David Markey <admin@dmarkey.com> wrote:> > Look in: > > /boot/guest/80edf9c0-f0c3-11df-afb8-002185fade1c/initrd > > > use gunzip and cpio. *BE CAREFUL WITH CPIO* > > On 17 November 2010 15:37, Peter den Hartog <peterdenhartog@gmail.com>wrote: > >> Would love to check that, how do i do that, just mount it on my local >> machine? >> >> >> On Tue, Nov 16, 2010 at 3:37 PM, David Markey <admin@dmarkey.com> wrote: >> >>> Its possible you dont have xen-blockfnt in your initrd, can you check >>> this? >>> >>> >>> On 16 November 2010 14:31, Peter den Hartog <peterdenhartog@gmail.com>wrote: >>> >>>> No luck, it boots to the same point: >>>> "Waiting for driver initializing.." >>>> >>>> Then i get a short kernel panic message but the console dies to fast to >>>> see what it is. >>>> >>>> Thanks, >>>> Peter >>>> >>>> >>>> On Tue, Nov 16, 2010 at 3:18 PM, David Markey <admin@dmarkey.com>wrote: >>>> >>>>> try: >>>>> >>>>> xe vm-param-set PV-args="console=xvc0" >>>>> >>>>> or >>>>> xe vm-param-set PV-args="console=hvc0" >>>>> >>>>> On 16 November 2010 13:36, Peter den Hartog <peterdenhartog@gmail.com>wrote: >>>>> >>>>>> Thanks, that got me a bit further. It boots now, but after a couple of >>>>>> seconds i get a kernel panic. >>>>>> No info on booting up tho, and the console closes to fast :-). >>>>>> >>>>>> Any place where i can find the error message? >>>>>> >>>>>> Thanks, >>>>>> Peter >>>>>> >>>>>> >>>>>> On Tue, Nov 16, 2010 at 2:24 PM, David Markey <admin@dmarkey.com>wrote: >>>>>> >>>>>>> xe vm-param-set PV-bootloader= uuid>>>>>>> d7596836-675e-6e79-f927-7b852a691785 >>>>>>> >>>>>>> >>>>>>> On 16 November 2010 12:31, Peter den Hartog < >>>>>>> peterdenhartog@gmail.com> wrote: >>>>>>> >>>>>>>> PV-bootloader >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
sometimes the name of the module changes slightly. How about find . | grep -i xen On 17 November 2010 16:22, Peter den Hartog <peterdenhartog@gmail.com>wrote:> Okay i did that, > > [root@box-netwerk 80edf9c0-f0c3-11df-afb8-002185fade1c]# ls > bin dev etc init initrd lib proc sbin sys sysroot vmlinuz > [root@box-netwerk 80edf9c0-f0c3-11df-afb8-002185fade1c]# find . -name > "xen-blockfnt" > [root@box-netwerk 80edf9c0-f0c3-11df-afb8-002185fade1c]# > > > So it''s not there i''m afraid.. > > On Wed, Nov 17, 2010 at 4:47 PM, David Markey <admin@dmarkey.com> wrote: > >> >> Look in: >> >> /boot/guest/80edf9c0-f0c3-11df-afb8-002185fade1c/initrd >> >> >> use gunzip and cpio. *BE CAREFUL WITH CPIO* >> >> On 17 November 2010 15:37, Peter den Hartog <peterdenhartog@gmail.com>wrote: >> >>> Would love to check that, how do i do that, just mount it on my local >>> machine? >>> >>> >>> On Tue, Nov 16, 2010 at 3:37 PM, David Markey <admin@dmarkey.com> wrote: >>> >>>> Its possible you dont have xen-blockfnt in your initrd, can you check >>>> this? >>>> >>>> >>>> On 16 November 2010 14:31, Peter den Hartog <peterdenhartog@gmail.com>wrote: >>>> >>>>> No luck, it boots to the same point: >>>>> "Waiting for driver initializing.." >>>>> >>>>> Then i get a short kernel panic message but the console dies to fast to >>>>> see what it is. >>>>> >>>>> Thanks, >>>>> Peter >>>>> >>>>> >>>>> On Tue, Nov 16, 2010 at 3:18 PM, David Markey <admin@dmarkey.com>wrote: >>>>> >>>>>> try: >>>>>> >>>>>> xe vm-param-set PV-args="console=xvc0" >>>>>> >>>>>> or >>>>>> xe vm-param-set PV-args="console=hvc0" >>>>>> >>>>>> On 16 November 2010 13:36, Peter den Hartog <peterdenhartog@gmail.com >>>>>> > wrote: >>>>>> >>>>>>> Thanks, that got me a bit further. It boots now, but after a couple >>>>>>> of seconds i get a kernel panic. >>>>>>> No info on booting up tho, and the console closes to fast :-). >>>>>>> >>>>>>> Any place where i can find the error message? >>>>>>> >>>>>>> Thanks, >>>>>>> Peter >>>>>>> >>>>>>> >>>>>>> On Tue, Nov 16, 2010 at 2:24 PM, David Markey <admin@dmarkey.com>wrote: >>>>>>> >>>>>>>> xe vm-param-set PV-bootloader= uuid>>>>>>>> d7596836-675e-6e79-f927-7b852a691785 >>>>>>>> >>>>>>>> >>>>>>>> On 16 November 2010 12:31, Peter den Hartog < >>>>>>>> peterdenhartog@gmail.com> wrote: >>>>>>>> >>>>>>>>> PV-bootloader >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Hi, i have the same problem. Did you resolve it? if Yes, how? thank you so much. -- View this message in context: http://xen.1045712.n5.nabble.com/XCP-converting-a-img-to-xva-tp3265556p4662201.html Sent from the Xen - User mailing list archive at Nabble.com. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Carsten from Virtastic
2011-Aug-03 13:17 UTC
Re: [Xen-users] Re: [XCP] converting a .img to xva
Hi there,> Hi, i have the same problem. > Did you resolve it? if Yes, how?The xva format has got a bit awkward structure. Basically it''s a tar file that contains loads of numbered files of 1M size each, or an img file cut in stripes, if you will. For example, the tar file would contain: Ref:xxx/ 00000001 00000002 00000003 .... 00001029 If one of those stripes consists entirely of zero-bytes, it won''t be included in the xva. Names are always just numeric and 8 bytes in length, padded and filled with zeros as above. I''ve only done the reverse process myself, that is converting xva into img, for about 40 VMs. What I''ve done is: - unpack tar file - go into the Ref:xxx folder (xxx is numeric, no idea how that is determined) - run this very simple script: ===============#!/bin/bash dd if =/dev/zero of=blank bs=1024 count=1k test -f image.img && rm -f image.img touch image.img max=`ls ???????? | sort | tail -n1` for i in `seq 0 $max`; do fn=`printf "%08d" $i` echo -n "$fn of $max" if [ -f "$fn" ]; then echo " - appending chunk" cat $fn >> image.img else echo " - filling blank" cat blank >> image.img fi done rm -f blank echo "Done." ============= Then I end up with an img file, which works perfectly fine with open source Xen. Maybe that can help you reverse-engineer it :-) Cheers Carsten _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Just a bit of info for you all. There is a small bug in xva.py. If your VM has a kernel/initrd loaded from Dom0, the xva that is produced will still be set to boot with pygrub. In order to fix this, blank the PV-bootloader parameter on the VM: xe vm-param-set uuid=<VM UUID> PV-bootloader="" Regards, David On 3 August 2011 14:17, Carsten from Virtastic <carsten@virtastic.com>wrote:> Hi there, > > > Hi, i have the same problem. > > Did you resolve it? if Yes, how? > > The xva format has got a bit awkward structure. Basically it''s a tar file > that contains loads of numbered files of 1M size each, or an img file cut in > stripes, if you will. > > For example, the tar file would contain: > > Ref:xxx/ > 00000001 > 00000002 > 00000003 > .... > 00001029 > > > If one of those stripes consists entirely of zero-bytes, it won''t be > included in the xva. > Names are always just numeric and 8 bytes in length, padded and filled with > zeros as above. > > I''ve only done the reverse process myself, that is converting xva into img, > for about 40 VMs. What I''ve done is: > > - unpack tar file > - go into the Ref:xxx folder (xxx is numeric, no idea how that is > determined) > - run this very simple script: > > ===============> #!/bin/bash > > dd if =/dev/zero of=blank bs=1024 count=1k > test -f image.img && rm -f image.img > touch image.img > > max=`ls ???????? | sort | tail -n1` > > for i in `seq 0 $max`; do > > fn=`printf "%08d" $i` > echo -n "$fn of $max" > > if [ -f "$fn" ]; then > echo " - appending chunk" > cat $fn >> image.img > else > echo " - filling blank" > cat blank >> image.img > fi > done > > rm -f blank > > echo > "Done." > =============> > Then I end up with an img file, which works perfectly fine with open source > Xen. > Maybe that can help you reverse-engineer it :-) > > > > Cheers > Carsten > > > > > > > _______________________________________________ > 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