[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] question regarding booting custom guest kernel






On 27 September 2013 19:07, Wei Liu <wei.liu2@xxxxxxxxxx> wrote:
On Fri, Sep 27, 2013 at 07:03:48PM +0200, Aastha Mehta wrote:
> On 27 September 2013 18:53, Wei Liu <wei.liu2@xxxxxxxxxx> wrote:
>
> > On Fri, Sep 27, 2013 at 06:46:06PM +0200, Aastha Mehta wrote:
> > [...]
> > >
> > >
> > > This is successful and I have a config file that looks like this -
> > > <config>
> > > bootloader = '/usr/local/lib/xen/bin/pygrub'
> >
> > Why do you add this line? Why don't you just use the generated config
> > file? AIUI Pygrub expects a disk, while xen-create-image creates
> > partitions. No wonder you sees something like "unable to find partition
> > table".
> >
> > Wei.
> >
>
> Because, without mentioning this, I get the error that I need to provide
> either a path to the kernel image or a bootloader.
>

Then provide your modified kernel and initrd -- isn't that exactly what
you wanted?

You'd better have a look at some example configs.

> # xl create /etc/xen/precise-guest.cfg
> Parsing config from /etc/xen/precise-guest.cfg
> Neither kernel nor bootloader specified
>
>
> --
> Aastha Mehta
> MPI-SWS, Germany
> E-mail: aasthakm@xxxxxxxxxxx <aasthakm@xxxxxxxxx>

Sorry, I am going around in circles :(
As you suggested to first try with stock kernel, I was trying to create a baseline VM. And I am missing something somewhere.

I added path to modified kernel and initrd in the config file, and then this is what happens:

root@wks-40-33:/home/aasthakm/bin# xl create /etc/xen/precise-guest.cfg
Parsing config from /etc/xen/precise-guest.cfg
Daemon running with PID 32204

root@wks-40-33:/home/aasthakm/bin# xl list
Name                                        ID   Mem VCPUs      State   Time(s)
Domain-0                                     0  5221     4     r-----    2288.5
root@wks-40-33:/home/aasthakm/bin# xl list
Name                                        ID   Mem VCPUs      State   Time(s)
Domain-0                                     0  5221     4     r-----    2288.6
precise-guest                               21     0     0     --p---       0.0                <<<<<<<<
root@wks-40-33:/home/aasthakm/bin# xl list
Name                                        ID   Mem VCPUs      State   Time(s)
Domain-0                                     0  5221     4     r-----    2289.7
precise-guest                               21   512     0     --p---       0.0
root@wks-40-33:/home/aasthakm/bin# xl list
Name                                        ID   Mem VCPUs      State   Time(s)
Domain-0                                     0  5221     4     r-----    2291.0
precise-guest                               21   512     1     --p---       0.0
root@wks-40-33:/home/aasthakm/bin# xl list
Name                                        ID   Mem VCPUs      State   Time(s)
Domain-0                                     0  5221     4     r-----    2291.7
precise-guest                               21   512     1     --psc-       0.0
root@wks-40-33:/home/aasthakm/bin# xl list
Name                                        ID   Mem VCPUs      State   Time(s)
Domain-0                                     0  5221     4     r-----    2291.9
root@wks-40-33:/home/aasthakm/bin# xl list
Name                                        ID   Mem VCPUs      State   Time(s)
Domain-0                                     0  5221     4     r-----    2292.4
precise-guest                               22   512     0     --p---       0.0                   <<<<<<<<

And this is what the dmesg shows:
[74224.901083] xenbr0: port 3(vif20.0) entered disabled state
[74233.958830] IPv6: ADDRCONF(NETDEV_UP): vif21.0: link is not ready
[74233.964990] init: Failed to spawn network-interface (vif21.0) pre-start process: unable to change root directory: No such file or directory
[74233.985132] init: Failed to spawn network-interface-security (network-interface/vif21.0) pre-start process: unable to change root directory: No such file or directory
[74233.998930] init: Failed to spawn network-interface (vif21.0) post-stop process: unable to change root directory: No such file or directory
[74234.015448] device vif21.0 entered promiscuous mode
[74234.017308] IPv6: ADDRCONF(NETDEV_UP): vif21.0: link is not ready
[74234.073060] xenbr0: port 3(vif21.0) entered disabled state
[74234.073150] device vif21.0 left promiscuous mode
[74234.073155] xenbr0: port 3(vif21.0) entered disabled state
[74243.139149] IPv6: ADDRCONF(NETDEV_UP): vif22.0: link is not ready
[74243.140978] init: Failed to spawn network-interface (vif22.0) pre-start process: unable to change root directory: No such file or directory
[74243.157986] init: Failed to spawn network-interface-security (network-interface/vif22.0) pre-start process: unable to change root directory: No such file or directory
[74243.166838] init: Failed to spawn network-interface (vif22.0) post-stop process: unable to change root directory: No such file or directory
[74243.188519] device vif22.0 entered promiscuous mode
[74243.190556] IPv6: ADDRCONF(NETDEV_UP): vif22.0: link is not ready
[74243.251182] xenbr0: port 3(vif22.0) entered disabled state
[74243.251474] device vif22.0 left promiscuous mode
[74243.251486] xenbr0: port 3(vif22.0) entered disabled state




--
Aastha Mehta
MPI-SWS, Germany
E-mail: aasthakm@xxxxxxxxxxx

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.