Hello there, I have some issues regarding xend domU migration to XCP VM. I try to migrate my old xend domU''s to my xen Could using the xva.py script. All seems to work quite ok, the migration process doesn''t throw any errors, i get a .xva file with a proper Size. When importing that file, immidiately the VG and LV is created, and VM properties are assigned correctly. But when I try to start the VM I get the following Error: [root@xen2 ~]# xe vm-start vm=stream1 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, The old domU''s are LVM Based, xen-4.0, pv_ops(), i think it''s not bootable in Terms of an MBR in the LV. Any Idea what''s wrong there? so long, mephisto _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
1. What filesystem is in DomU? 2. What version of grub? 3. What is the filesystem layout On 28 February 2011 16:10, Bastian Mäuser <mephisto@mephis.to> wrote:> Hello there, > > I have some issues regarding xend domU migration to XCP VM. > > I try to migrate my old xend domU''s to my xen Could using the xva.py > script. All seems to work quite ok, the migration process doesn''t throw > any errors, i get a .xva file with a proper Size. > > When importing that file, immidiately the VG and LV is created, and VM > properties are assigned correctly. But when I try to start the VM I get > the following Error: > > [root@xen2 ~]# xe vm-start vm=stream1 > 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, > > The old domU''s are LVM Based, xen-4.0, pv_ops(), i think it''s not > bootable in Terms of an MBR in the LV. > > Any Idea what''s wrong there? > > so long, > mephisto > > > > _______________________________________________ > 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
Hi, first of all, thanks for answering. The Filesystem in domU is ext3, there''s no grub in the domU, coz it''s paravirtualized. The Layout - it''s just one partition in one LV + one Swap. And i copied the kernel images which were referred in the domU Config into the image into /boot... Grub isn''t installed at all in the domU - it was debootstrapped with xen-tools on a xend dom0. greetings, Bastian Am 28.02.2011 18:36, schrieb David Markey:> 1. What filesystem is in DomU? > 2. What version of grub? > 3. What is the filesystem layout > > On 28 February 2011 16:10, Bastian Mäuser <mephisto@mephis.to > <mailto:mephisto@mephis.to>> wrote: > > Hello there, > > I have some issues regarding xend domU migration to XCP VM. > > I try to migrate my old xend domU''s to my xen Could using the xva.py > script. All seems to work quite ok, the migration process doesn''t > throw > any errors, i get a .xva file with a proper Size. > > When importing that file, immidiately the VG and LV is created, and VM > properties are assigned correctly. But when I try to start the VM > I get > the following Error: > > [root@xen2 ~]# xe vm-start vm=stream1 > 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, > > The old domU''s are LVM Based, xen-4.0, pv_ops(), i think it''s not > bootable in Terms of an MBR in the LV. > > Any Idea what''s wrong there? > > so long, > mephisto > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com <mailto: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
what does "xe vm-list uuid=<vm-uuid> params=all" say On 28 February 2011 18:48, Bastian Mäuser <mephisto@mephis.to> wrote:> Hi, > > first of all, thanks for answering. > > The Filesystem in domU is ext3, there''s no grub in the domU, coz it''s > paravirtualized. > > The Layout - it''s just one partition in one LV + one Swap. > > And i copied the kernel images which were referred in the domU Config into > the image into /boot... > > Grub isn''t installed at all in the domU - it was debootstrapped with > xen-tools on a xend dom0. > > greetings, > Bastian > > > Am 28.02.2011 18:36, schrieb David Markey: > > 1. What filesystem is in DomU? > 2. What version of grub? > 3. What is the filesystem layout > > On 28 February 2011 16:10, Bastian Mäuser <mephisto@mephis.to> wrote: > >> Hello there, >> >> I have some issues regarding xend domU migration to XCP VM. >> >> I try to migrate my old xend domU''s to my xen Could using the xva.py >> script. All seems to work quite ok, the migration process doesn''t throw >> any errors, i get a .xva file with a proper Size. >> >> When importing that file, immidiately the VG and LV is created, and VM >> properties are assigned correctly. But when I try to start the VM I get >> the following Error: >> >> [root@xen2 ~]# xe vm-start vm=stream1 >> 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, >> >> The old domU''s are LVM Based, xen-4.0, pv_ops(), i think it''s not >> bootable in Terms of an MBR in the LV. >> >> Any Idea what''s wrong there? >> >> so long, >> mephisto >> >> >> >> _______________________________________________ >> 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
Here we go:
[root@xen2 ~]# xe vm-list uuid=3622d765-0767-fae6-1444-250d0fd3ca2f
params=all
uuid ( RO) : 3622d765-0767-fae6-1444-250d0fd3ca2f
name-label ( RW): stream1
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): 4194304
memory-static-max ( RW): 268435456
memory-dynamic-max ( RW): 268435456
memory-dynamic-min ( RW): 268435456
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/e71ebede-412a-11e0-97ba-002481df30f6/vmlinuz
PV-ramdisk ( RW):
/boot/guest/e71ebede-412a-11e0-97ba-002481df30f6/initrd
PV-args ( RW):
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:f97447a3-23d1-5669-7cec-d21137944eac; mac_seed:
e99892ae-ea62-bf1e-6f7c-91faee395261; 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>
protection-policy ( RW): <not in database>
is-snapshot-from-vmpp ( RO): false
tags (SRW):
On 02/28/2011 10:46 PM, David Markey wrote:> what does "xe vm-list uuid=<vm-uuid> params=all" say
>
> On 28 February 2011 18:48, Bastian Mäuser <mephisto@mephis.to
> <mailto:mephisto@mephis.to>> wrote:
>
> Hi,
>
> first of all, thanks for answering.
>
> The Filesystem in domU is ext3, there''s no grub in the domU,
coz
> it''s paravirtualized.
>
> The Layout - it''s just one partition in one LV + one Swap.
>
> And i copied the kernel images which were referred in the domU
> Config into the image into /boot...
>
> Grub isn''t installed at all in the domU - it was
debootstrapped
> with xen-tools on a xend dom0.
>
> greetings,
> Bastian
>
>
> Am 28.02.2011 18:36, schrieb David Markey:
>> 1. What filesystem is in DomU?
>> 2. What version of grub?
>> 3. What is the filesystem layout
>>
>> On 28 February 2011 16:10, Bastian Mäuser <mephisto@mephis.to
>> <mailto:mephisto@mephis.to>> wrote:
>>
>> Hello there,
>>
>> I have some issues regarding xend domU migration to XCP VM.
>>
>> I try to migrate my old xend domU''s to my xen Could
using the
>> xva.py
>> script. All seems to work quite ok, the migration process
>> doesn''t throw
>> any errors, i get a .xva file with a proper Size.
>>
>> When importing that file, immidiately the VG and LV is
>> created, and VM
>> properties are assigned correctly. But when I try to start
>> the VM I get
>> the following Error:
>>
>> [root@xen2 ~]# xe vm-start vm=stream1
>> 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,
>>
>> The old domU''s are LVM Based, xen-4.0, pv_ops(), i
think it''s not
>> bootable in Terms of an MBR in the LV.
>>
>> Any Idea what''s wrong there?
>>
>> so long,
>> mephisto
>>
>>
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@lists.xensource.com
>> <mailto: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
does /boot/guest/e71ebede-412a-11e0-97ba-002481df30f6/vmlinuz and /boot/guest/e71ebede-412a-11e0-97ba-002481df30f6/initrd exist? also try xe vm-param-set uuid=<vm-uuid> PV-bootloader On 1 March 2011 08:43, Bastian Mäuser <mephisto@mephis.to> wrote:> PV-kernel ( RW): > /boot/guest/e71ebede-412a-11e0-97ba-002481df30f6/vmlinuz > PV-ramdisk ( RW): > /boot/guest/e71ebede-412a-11e0-97ba-002481df30f6/initrd >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi there, i got it booting now. I set PV-bootloader to NULL and PV-kernel and PV-ramdisk to something inside /boot/guest (and copied my domU kernel + initrd there). Now the machine is booting. Ok, Now I got the isssue, that the Kernel boots, but "xvda: unknown partition table" is spit out. any guess? On 03/01/2011 10:20 AM, David Markey wrote:> does /boot/guest/e71ebede-412a-11e0-97ba-002481df30f6/vmlinuz and > /boot/guest/e71ebede-412a-11e0-97ba-002481df30f6/initrd exist? > > also try xe vm-param-set uuid=<vm-uuid> PV-bootloader= > > > > On 1 March 2011 08:43, Bastian Mäuser <mephisto@mephis.to > <mailto:mephisto@mephis.to>> wrote: > > PV-kernel ( RW): > /boot/guest/e71ebede-412a-11e0-97ba-002481df30f6/vmlinuz > PV-ramdisk ( RW): > /boot/guest/e71ebede-412a-11e0-97ba-002481df30f6/initrd > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
PV-args should be something like root=/dev/xvda On 1 March 2011 09:51, Bastian Mäuser <mephisto@mephis.to> wrote:> Hi there, > > i got it booting now. I set PV-bootloader to NULL and PV-kernel and > PV-ramdisk to something inside /boot/guest (and copied my domU kernel + > initrd there). Now the machine is booting. > > Ok, Now I got the isssue, that the Kernel boots, but "xvda: unknown > partition table" is spit out. > > any guess? > > > On 03/01/2011 10:20 AM, David Markey wrote: > > does /boot/guest/e71ebede-412a-11e0-97ba-002481df30f6/vmlinuz and > /boot/guest/e71ebede-412a-11e0-97ba-002481df30f6/initrd exist? > > also try xe vm-param-set uuid=<vm-uuid> PV-bootloader> > > > On 1 March 2011 08:43, Bastian Mäuser <mephisto@mephis.to> wrote: > >> PV-kernel ( RW): >> /boot/guest/e71ebede-412a-11e0-97ba-002481df30f6/vmlinuz >> PV-ramdisk ( RW): >> /boot/guest/e71ebede-412a-11e0-97ba-002481df30f6/initrd >> > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users