[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [MirageOS-devel] CT 'xl create' - Loops and Device Model
Hi Ahmed, Have you tried reducing the domU memory usage to 256 MB? (and revert the rest of domU_test to the original from the article, including the original kernel) I don't know much about how Xen memory allocation works but given that dom0 has 512 MB it might be too optimistic to expect 512 MB to be available to a guest. Of course if that fixes your problem then the article should be updated (it might have been tested on the Cubietruck when it was written). Luke On 29 May 2015 at 19:09, Ahmed Ismail <a.m.ismail@xxxxxxxxxxxx> wrote: > Whoops! > Missed a few things. Sorry, it's been a long week. > 1- [1] is http://openmirage.org/wiki/xen-on-cubieboard2 > 2- The Xen Guest used in 1 was using a debootstrapped image on > vg0/linux-guest-1 to follow [1] precisely; I was also messing with a > debootstrapped .img file on /media/disk. > 3- The Xen Guest used in the second attempt was a debootstrapped image on > /media/disk with a formatted swap image, both of which were on /media/disk. > > Cheers, > > On Fri, May 29, 2015 at 1:01 PM, Ahmed Ismail <a.m.ismail@xxxxxxxxxxxx> > wrote: >> >> Hello, >> >> I hope you're all having a wonderful day. >> >> I was following the tutorial on openmirage, specifically at [1], when I >> faced a few problems at the Linux DomU part. >> The only differences between the tutorial and how I went about it is in my >> choice for some variables i.e. hostname, ssh settings, etc. >> 1- Using the "/root/dom0_kernel" zImage, running xl create causes it to >> enter an endless loop. All I get back is: >> ``` >> mirage@cubietruck:/media/disk$ sudo xl create domU_test -c >> Parsing config from domU_test >> ``` >> >> 'sudo xl list' shows that the guest is in a paused state. >> Unpausing it, the guest enters a sort of limbo (no state present, just >> dashes). >> ``` >> mirage@cubietruck:/media/disk$ sudo xl unpause Ubuntu-14.04 >> mirage@cubietruck:/media/disk$ sudo xl list >> Name ID Mem VCPUs State Time(s) >> (null) 0 512 2 r----- >> 18273.1 >> Ubuntu-14.04 21 512 2 ------ >> 4.4 >> ``` >> 2- Compiling the linux kernel seperately using gcc-4.9 on the CT, and >> changing the cfg file to use the zImage kernel instead I get the following >> error: >> ``` >> mirage@cubietruck:/media/disk$ sudo xl create -c XenGuest2.cfg >> Parsing config from XenGuest2.cfg >> libxl: error: libxl_dm.c:1388:device_model_spawn_outcome: domain 5 device >> model: spawn failed (rc=-3) >> libxl: error: libxl_create.c:1186:domcreate_devmodel_started: device model >> did not start: -3 >> libxl: error: libxl_dm.c:1492:kill_device_model: Device Model already >> exited >> ``` >> >> Currently, my cfg file looks like this: >> ``` >> device_model_version = "qemu-xen" >> device_model_override = "/usr/bin/qemu-arm-static" >> kernel = "/media/disk/zImage" >> memory = 512 >> name = "Test" >> vcpus = 2 >> serial="pty" >> disk = [ 'phy:/media/disk/XenGuest2.img,xvda1,w', >> 'phy:/media/disk/XenGuest2.swap,xvda2,w'] >> vif = ['bridge=xenbr0'] >> root = "/dev/xvda1 ro" >> #extra = 'console=hvc0 xencons=tty root=/dev/xvda1' >> ``` >> But I've messed with it quite a bit, changing the device_model_override >> value, disk and root/extra options. >> >> Has anyone successfully created Xen guests on the cubietruck? >> Care to share how you went about getting it to work? >> >> Note: The unikernels work fine. >> >> Thanks in advance. >> -- >> Ahmed > > > > > -- > Ahmed Ismail > MSc, Communications and Electronics Engineering Department > The American University in Cairo > Mobile: +2-0111-321-9234 > Mail: a.m.ismail@xxxxxxxxxxxx > Skype: ahmedm.ismail > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@xxxxxxxxxxxxxxxxxxxx > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > _______________________________________________ MirageOS-devel mailing list MirageOS-devel@xxxxxxxxxxxxxxxxxxxx http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |