Kitten not able to find guest image

[J]

Hi,

I am running Palacios/ Kitten on ubuntu.
Although the correct path of the guest image is given, 'make isoimage'
does not pickup the correct guest image.
Am I missing something that is not in the manual ?

Appreciate your help.
Thanks,
J.

[Patrick G. Bridges]

Without seeing your config file (for Kitten at a bare minimum) and the
output of the portion of "make V=1 isoimage" that deals with the
isoimage (where it makes hello_world_rawdata.o), it's hard to know
what's going on with enough detail to help you. Could you provide this
information so we can help you fix your problem?

> --
> You received this message because you are subscribed to the Google Groups "V3VEE Development" group.
> To post to this group, send email to v3vee-de...@googlegroups.com.
> To unsubscribe from this group, send email to v3vee-developm...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/v3vee-development?hl=en.
>
>

[joseph gerard]

Thanks for the help.
I reckon 'make isoimage works'. But the SVM doesnt get recognized.
Attaching the kitten config and 'make isoimage' output


serial.out has the following output:

SVM Not Available
palacios/src/palacios/vmm.c(68): CPU has no virtualization Extensions

I run AMD and the svm is turned up.

grep -E 'svm|vmx' /proc/cpuinfo
flags        : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nonstop_tsc extd_apicid pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a 3dnowprefetch osvw ibs skinit wdt nodeid_msr

[Peter Dinda]

You mentioned you are running Palacios/Kitten under Ubuntu. Does this
mean you are running Palacios/Kitten on QEMU? If so, then you need
to be sure to use a version of QEMU that has SVM support, and has it
enabled.

Peter

--
Dr. Peter A. Dinda
Associate Professor
Head, Computer Engineering and Systems Division
Department of Electrical Engineering and Computer Science
Northwestern University
2145 Sheridan Avenue
Evanston, IL 60208
847-467-7859 (voice)
http://www.eecs.northwestern.edu/~pdinda
pdi...@northwestern.edu

[Jack Lange]

Enabling SVM in qemu is done by disabling kqemu and/or the kvm accelerators.

I think its the -no-kqemu option, if I remember correctly.
--Jack
From my IPhone
Jack Lange ; [\] ; PITT-CS
[ jack...@cs.pitt.edu ]
http://www.cs.pitt.edu/~jacklange

[Patrick G. Bridges]

It's -no-kvm

-Patrick

[joseph gerard]

That works. Thanks.

Still not up and running yet.

This is my iso file entry in myconfig.xml

        <!-- List of binary files to include with configuration -->
        <!-- This is where you add disk images -->
        <files>
                <!-- The file 'id' is used as a reference for other configuration components -->
       <file id="boot-cd" filename="/Project/finnix-101.iso" />

        </files>


This is the error status in serial.out


palacios/src/palacios/vmm_mem.c(64): Could not allocate Guest memory
palacios/src/palacios/vmm_config.c(246): Could not initialize shadow map
palacios/src/palacios/vmm_config.c(356): Error in preconfiguration
palacios/src/palacios/vmm.c(118): Could not configure guest
<3>Could not create guest context


Thanks.

[Peter Dinda]

Try adding -m 2047 to your qemu options. Alternatively, reduce the
memory size in your guest configuration.

Palacios allocates physical memory to guests, so you need to have
enough available, after the host boots, to support your VM.

Peter

On Mar 8, 4:14 pm, joseph gerard <joseph.ger...@gmail.com> wrote:
> That works. Thanks.
>
> Still not up and running yet.
>
> This is my iso file entry in myconfig.xml

> *

>         <!-- List of binary files to include with configuration -->
>         <!-- This is where you add disk images -->
>         <files>
>                 <!-- The file 'id' is used as a reference for other
> configuration components -->
>        <file id="boot-cd" filename="/Project/finnix-101.iso" />
>

>         </files>*

>
> This is the error status in serial.out
>

> *

> palacios/src/palacios/vmm_mem.c(64): Could not allocate Guest memory
> palacios/src/palacios/vmm_config.c(246): Could not initialize shadow map
> palacios/src/palacios/vmm_config.c(356): Error in preconfiguration
> palacios/src/palacios/vmm.c(118): Could not configure guest
> <3>Could not create guest context

> *
> *
> *Thanks.

>
> On Tue, Mar 8, 2011 at 9:18 PM, Patrick G. Bridges <patrickb...@gmail.com>wrote:
>
>
>
>
>
>
>
> > It's -no-kvm
>
> > -Patrick
>

> > On Tue, Mar 8, 2011 at 11:31 AM, Jack Lange <jack.la...@gmail.com> wrote:
> > > Enabling SVM in qemu is done by disabling kqemu and/or the kvm
> > accelerators.
>
> > > I think its the -no-kqemu option, if I remember correctly.
> > > --Jack
> > > From my IPhone
> > > Jack Lange ; [\] ; PITT-CS

> > > [ jackla...@cs.pitt.edu ]

> > >http://www.cs.pitt.edu/~jacklange
>
> > > On Mar 8, 2011, at 11:05 AM, Peter Dinda <pdi...@northwestern.edu>
> > wrote:
>
> > >> You mentioned you are running Palacios/Kitten under Ubuntu.  Does this
> > >> mean you are running Palacios/Kitten on QEMU?   If so, then you need
> > >> to be sure to use a version of QEMU that has SVM support, and has it
> > >> enabled.
>
> > >> Peter
>

> > >> On Tue, Mar 8, 2011 at 12:09 PM, joseph gerard <joseph.ger...@gmail.com>

> > wrote:
> > >>> Thanks for the help.
> > >>> I reckon 'make isoimage works'. But the SVM doesnt get recognized.
> > >>> Attaching the kitten config and 'make isoimage' output
>
> > >>> serial.out has the following output:
>
> > >>> SVM Not Available
> > >>> palacios/src/palacios/vmm.c(68): CPU has no virtualization Extensions
>
> > >>> I run AMD and the svm is turned up.
>
> > >>> grep -E 'svm|vmx' /proc/cpuinfo
> > >>> flags        : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
> > cmov
> > >>> pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt
> > pdpe1gb
> > >>> rdtscp lm 3dnowext 3dnow constant_tsc rep_good nonstop_tsc extd_apicid
> > pni
> > >>> monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a
> > >>> 3dnowprefetch osvw ibs skinit wdt nodeid_msr
>
> > >>> On Tue, Mar 8, 2011 at 5:12 PM, Patrick G. Bridges <

> > patrickb...@gmail.com>

> > >>> wrote:
>
> > >>>> Without seeing your config file (for Kitten at a bare minimum) and the
> > >>>> output of the portion of "make V=1 isoimage" that deals with the
> > >>>> isoimage (where it makes hello_world_rawdata.o), it's hard to know
> > >>>> what's going on with enough detail to help you. Could you provide this
> > >>>> information so we can help you fix your problem?
>

>  serial.out
> 16KViewDownload
>
>  myconfig.xml
> 7KViewDownload
>
>  palaciosconfig
> 3KViewDownload

[joseph gerard]

Reduced the memory.

Now getting this.

configuring device LNX_VIRTIO_SYM
palacios/src/palacios/vmm_dev_mgr.c(130): Could not find device LNX_VIRTIO_SYM in master device table
palacios/src/palacios/vmm_config.c(439): Error creating device LNX_VIRTIO_SYM
palacios/src/palacios/vmm_config.c(313): Failed to setup devices
palacios/src/palacios/vmm_config.c(387): Error in postconfiguration

palacios/src/palacios/vmm.c(118): Could not configure guest

The 'make config' does not give an option on this device.
tried manually  changing .config of Palacios, since i got this Still not resolved.

Any pointers ? thanks.

[Peter Dinda]

That means you are trying to instantiate a device that you have not
include when you compiled palacios. This is one of the linux virtio-
compatible devices.

[Peter Dinda]

This one will appear if you enable experimental options and you turn
on symbiotic virtualization. I would suggest just removing it from
your config, though.

Peter