[kernel-xen] Converting from bad habits (still)

[Steven Haigh]

Ok, if you're installing EL6 on EL6, the easiest way is to use this method:
https://www.crc.id.au/xen-performance-guide/

Skip to Step 1 - and use that as a template. Then use dd to clone it 
onto new VMs.

If you're installing Debian, try a net install. You can get the kernel 
to boot from: http://www.debian.org/devel/debian-installer/

You'll need to use these which will then launch the installer.

If all that fails, you can install it as a HVM and boot from an ISO 
image - and then change it to PV after installation.


-- 
Steven Haigh

Email: netwiz at crc.id.au
Web: http://www.crc.id.au
Phone: (03) 9001 6090 - 0412 935 897
Fax: (03) 8338 0299

On 7/12/2012 4:23 AM, Steven Spencer wrote:
> List / Joe / All,
>
> I'm trying to take your advice and convert to a flat config file to
> install and run a DomU. I've googled, posted to the list, and made some
> progress, but I'm still not able to even do the install on the guest.
> Again, at this point I'm just trying to get the OS installed and then
> will revert (hopefully) to pygrub for the kernel and ramdisk lines. I'm
> trying to use a kickstart file too, but it isn't even getting that far
> at the moment:
>
> Connfig for install of guest:
> -----------------------------
> kernel="/boot/vmlinuz-2.6.32-279.14.1.el6.x86_64"
> ramdisk="/boot/initramfs-3.6.7-1.el6xen.x86_64.img"
> name = "vm_test"
> memory = 1024
> vcpus = 1
> disk = [ 'tap:aio:/virtual/vm_test.img,xvda,w' ]
> root = '/dev/xvda ro'
> extra="text ks=http://10.10.10.104/sample.ks.cfg"
> on_poweroff = 'destroy'
> on_reboot   = 'restart'
> on_crash    = 'restart'
> vif = [
> "ip=10.10.10.132,mac=00:16:36:35:35:97,bridge=br0,script=vif-bridge" ]
> # extra="(hd0)/boot/grub/grub.conf"
>
> I used dd to create a single disk image (vm_test.img above) with the
> idea that the partitioning section of the kickstart file would take care
> of creating the swap for me during build. Here is the kickstart file I'm
> attempting to use too, just in case that is a problem somewhere, though
> I don't see it loading yet in the startup:
>
> install
> url --url http://linux.mirrors.es.net/centos/6/os/x86_64/
> lang en_US.UTF-8
> keyboard us
> network --device eth0 --bootproto=static --ip=(removed from email)
> --netmask=255.255.255.0 --gateway=(removed from email) --nameserv
> er=(removed from email)
> # Bogus password, change to something sensible!
> rootpw [password removed from email]
> firewall --enabled --service=ssh
> authconfig --enableshadow --passalgo=sha512
> selinux --disabled
> timezone --utc America/North_Dakota/New_Salem
> bootloader --location=mbr --driveorder=xvda --append="console=xvc0"
>
> # Partitioning (change sizes and if allowed by installation, ext4
> instead of ext3)
> clearpart --all --initlabel --drives=xvda
> part / --fstype ext4 --size=20000 --ondisk=xvda
> part swap --size=1536 -ondisk=xvda
>
> %packages
> @core
> @base
> @server-platform
> @server-policy
> pax
> oddjob
> sgpio
> certmonger
> pam_krb5
> krb5-workstation
> perl-DBD-SQLite
> %end
>
> What I'm getting when I try to boot, is that xvda apparently is not
> recognised. Do I need to mount the disk image and then fdisk it so that
> it has the xvda device name? When I try to create the guest with the
> config, the process starts and then gets to this point and fails:
>
> XENBUS: Waiting for devices to initialise:
> 295s...290s...285s...280s...275s...270s...265s...260s...255s...250s...245s...240s...235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...115s...110s...105s...100s...
>
> dracut Warning: No root device "block:/dev/xvda" found
>
> dracut Warning: Boot has failed. To debug this issue add "rdshell" to
> the kernel command line.
>
>
> dracut Warning: Signal caught!
>
> dracut Warning: Boot has failed. To debug this issue add "rdshell" to
> the kernel command line.
> Kernel panic - not syncing: Attempted to kill init!
> Pid: 1, comm: init Not tainted 2.6.32-279.14.1.el6.x86_64 #1
> Call Trace:
>   [<ffffffff814fd98a>] ? panic+0xa0/0x168
>   [<ffffffff81070c42>] ? do_exit+0x862/0x870
>   [<ffffffff8117d0a5>] ? fput+0x25/0x30
>   [<ffffffff81070ca8>] ? do_group_exit+0x58/0xd0
>   [<ffffffff81070d37>] ? sys_exit_group+0x17/0x20
>   [<ffffffff8100b0f2>] ? system_call_fastpath+0x16/0x1b
> -----------------------
>
> On top of that, I can't seem to get the right combination in the kernel
> = line to add the rdshell for debug.
>
> Any help is appreciated.
>
> Thanks,

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4965 bytes
Desc: S/MIME Cryptographic Signature
URL: <https://lists.wireless.org.au/pipermail/kernel-xen/attachments/20121207/1b8fefd1/attachment-0001.p7s>