On Fri, Oct 23, 2009 at 04:06:59PM +0530, Fasiha Ashraf wrote:
> I have tried it after fstab entry but in vain.
Do you have the files under /proc/xen/ ? Do they have some content?
this is what i have in /proc/xen # ls
capabilities privcmd xenbus xsd_kva xsd_portbut
the virt-manger behaves same. How did Boris create paravirt imgz using virt-manager?
> An other problem started with it "low
> storage space". I dont know where does virt-manager keep those images and on which
> device it has mount the vm img. how can i free that storage space? that is in use of
> all those images i tried to install and fails to create.
>
They're stored under /var as a default.. iirc /var/lib/libvirt/images
Thanks a lot, it helps deleting extra images.
-- Pasi
> Regards
> Fasiha Ashraf
>
> --- On Fri, 23/10/09, Pasi Kärkkäinen <
pasik@xxxxxx> wrote:
>
> From: Pasi Kärkkäinen <
pasik@xxxxxx>
> Subject: Re: Fw: Re: [Xen-devel] vmx
problem
> To: "Fasiha Ashraf" <
feehapk@xxxxxxxxxxx>
> Cc: "xen" <
xen-devel@xxxxxxxxxxxxxxxxxxx>
> Date: Friday, 23 October, 2009, 1:43 PM
>
> On Fri, Oct 23, 2009 at 02:04:33PM +0530, Fasiha Ashraf wrote:
> > Sory forgot to attach file in previous email.
> >
>
> Maybe you don't have xenfs mounted so virt* stuff can't figure out the
> hypervisor info?
>
> Do you have /proc/xen ?
>
> Do you have this line in /etc/fstab:
> none
/proc/xen xenfs defaults 0 0
>
> Also, please update to 'xen/master' branch, and you'll get 2.6.31.4
> based pv_ops dom0 kernel.
>
> 2.6.30-rc6 you're running is not supported, and a lot of bugs has been
> fixed after that version.
>
> -- Pasi
>
> > Fasiha Ashraf
> >
> > --- On Fri, 23/10/09, Fasiha Ashraf <[1]
feehapk@xxxxxxxxxxx> wrote:
> >
> > From: Fasiha Ashraf <[2]
feehapk@xxxxxxxxxxx>
> > Subject: Re: [Xen-devel] vmx problem
> > To: "Pasi Kärkkäinen" <[3]
pasik@xxxxxx>
> > Cc: "Fajar A." <[4]
fajar@xxxxxxxxx>, [5]
xen-devel@xxxxxxxxxxxxxxxxxxx, "Mr.
> Teo En
> > Ming (Zhang Enming)" <[6]
space.time.universe@xxxxxxxxx>, "Keir Fraser"
> >
<[7]
keir.fraser@xxxxxxxxxxxxx>
> > Date: Friday, 23 October, 2009, 1:32 PM
> >
> > Yess xen is running, PFA virt-manager status screen shot.
> >
> > [root@Server1-FC11 init.d]# xm list
> > Name ID Mem VCPUs State
> > Time(s)
> > Domain-0
0 7555 8 r-----
> > 777.3
> > [root@Server1-FC11 init.d]# xm info
> > host : Server1-FC11
> > release : 2.6.30-rc6-tip
> > version : #1 SMP Thu Oct 22 12:48:59 PKST 2009
> > machine : x86_64
> > nr_cpus :
8
> > nr_nodes : 1
> > cores_per_socket : 4
> > threads_per_core : 1
> > cpu_mhz : 1995
> > hw_caps :
> > bfebfbff:20100800:00000000:00000140:000ce33d:00000000:00000001:00000000
> > virt_caps : hvm
> > total_memory :
8186
> > free_memory : 524
> > node_to_cpu : node0:0-7
> > node_to_memory : node0:524
> > xen_major : 3
> > xen_minor : 4
> > xen_extra : .1
> > xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
> > hvm-3.0-x86_32p
hvm-3.0-x86_64
> > xen_scheduler : credit
> > xen_pagesize : 4096
> > platform_params : virt_start=0xffff800000000000
> > xen_changeset : unavailable
> > cc_compiler : gcc version 4.4.1 20090725 (Red Hat 4.4.1-2) (GCC)
> > cc_compile_by : root
> > cc_compile_domain : (none)
> > cc_compile_date : Wed Oct
21 16:54:50 PKST 2009
> > xend_config_format : 4
> >
> > Fasiha Ashraf
> >
> > --- On Fri, 23/10/09, Pasi Kärkkäinen <[8]
pasik@xxxxxx> wrote:
> >
> > From: Pasi Kärkkäinen <[9]
pasik@xxxxxx>
> > Subject: Re: [Xen-devel] vmx problem
> > To: "Fasiha Ashraf" <[10]
feehapk@xxxxxxxxxxx>
> > Cc: "Fajar A." <[11]
fajar@xxxxxxxxx>, [12]
xen-devel@xxxxxxxxxxxxxxxxxxx,
> "Mr. Teo
> > En Ming (Zhang Enming)" <[13]
space.time.universe@xxxxxxxxx>, "Keir Fraser"
> > <[14]
keir.fraser@xxxxxxxxxxxxx>
> > Date: Friday, 23 October, 2009,
12:49 PM
> >
> > On Fri, Oct 23, 2009 at 11:30:47AM +0530, Fasiha Ashraf wrote:
> > > Yeah... I believe so till now. If this is true why my virt-manager
> > > behaving like this. PFA some screen shots of virt-manager, both virt
> > types
> > > para and fully are disabled. and it stops me from creating a VM.
> > >
> >
> > VMX is not needed for paravirtualized (PV) guests. VMX is only needed
> > for fully
virtualized (HVM) guests.
> >
> > Are you sure you're running Xen? What does "xm info" and "xm list" tell
> > you?
> >
> > -- Pasi
> >
> > > Regards,
> > > Fasiha Ashraf
> > >
> > > --- On Fri, 23/10/09, Mr. Teo En Ming (Zhang Enming)
> > > <[15]
space.time.universe@xxxxxxxxx> wrote:
> > >
> > > From: Mr. Teo En Ming (Zhang Enming)
> > <[16]
space.time.universe@xxxxxxxxx>
> > > Subject: Re: [Xen-devel] vmx problem
> > > To: "Fasiha Ashraf" <[17]
feehapk@xxxxxxxxxxx>
> > > Cc: "Keir Fraser" <[18]
keir.fraser@xxxxxxxxxxxxx>, "Pasi Kärkkäinen"
> > > <[19]
pasik@xxxxxx>, "Fajar A." <[20]
fajar@xxxxxxxxx>,
> > > [21]
xen-devel@xxxxxxxxxxxxxxxxxxx> > > Date: Friday, 23 October, 2009, 10:20 AM
> > >
> > > For
paravirtualized guests I don't think you need the hardware
> > > virtualization assist (VMX). You only need vmx when you want to
> > create
> > > HVM guests.
> > >
> > > --
> > > Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics)
> > BEng(Hons)(Mechanical
> > > Engineering)
> > > Alma
Maters:
> > > (1) Singapore Polytechnic
> > > (2) National University of Singapore
> > > Blog URL: [1][1][22]
http://teo-en-ming-aka-zhang-enming.blogspot.com> > > Email: [2][23]
space.time.universe@xxxxxxxxx> > > MSN: [3][24]
teoenming@xxxxxxxxxxx> >
> Mobile Phone: +65-9648-9798
> > > Street: Bedok Reservoir Road
> > > Republic of Singapore
> > >
> > > On Fri, Oct 23, 2009 at 1:15 PM, Fasiha Ashraf
> > <[4][25]
feehapk@xxxxxxxxxxx>
> > > wrote:
> > >
> > > >>Any plans for 'nested' VMX
support? KVM seems to have that.
> > > No i just need to enable virtualization flag on my intel xeon
> > quad
> > > core processor, so that i can create paravirt VMs in my set-up.
> > Which
> > > at this time virt-manager is not allowing me to do.
> > >
> > > Regards,
> > > Fasiha Ashraf
> >
>
> > > --- On Thu, 22/10/09, Pasi Kärkkäinen <[5][26]
pasik@xxxxxx> wrote:
> > >
> > > From: Pasi Kärkkäinen <[6][27]
pasik@xxxxxx>
> > > Subject: Re: [Xen-devel] vmx problem
> > > To: "Keir Fraser" <[7][28]
keir.fraser@xxxxxxxxxxxxx>
> > > Cc: "Fasiha Ashraf" <[8][29]
feehapk@xxxxxxxxxxx>, "Fajar A."
> > > <[9][30]
fajar@xxxxxxxxx>, "xen"
> <[10][31]
xen-devel@xxxxxxxxxxxxxxxxxxx>
> > > Date: Thursday, 22 October, 2009, 7:22 PM
> >
>
> > > On Thu, Oct 22, 2009 at 03:12:04PM +0100, Keir Fraser wrote:
> > > > VMX is hidden from guest kernels as it's not a feature they
> > > themselves can
> > > > make use of. Hence it does not appear in the guest's
> > > /proc/cpuinfo.
> > > >
> > >
> >
> Any plans for 'nested' VMX support? KVM seems to have that..
> > >
> > > -- Pasi
> > >
> > >
> > --------------------------------------------------------------------------
> > >
> > > Yahoo! India has a new look. [11]Take a sneak peek.
> > > _______________________________________________
> >
> Xen-devel mailing list
> > > [12][32]
Xen-devel@xxxxxxxxxxxxxxxxxxx> > > [13][2][33]
http://lists.xensource.com/xen-devel> > >
> > >
> > --------------------------------------------------------------------------
> > >
> > > From cricket scores to your friends.
Try the [14]Yahoo! India
> > Homepage!
> > >
> > > References
> > >
> > > Visible links
> > > 1. [3][34]
http://teo-en-ming-aka-zhang-enming.blogspot.com/> > > 2. file:///mc/compose?to=[35]
space.time.universe@xxxxxxxxx> > > 3.
file:///mc/compose?to=[36]
teoenming@xxxxxxxxxxx> > > 4. file:///mc/compose?to=[37]
feehapk@xxxxxxxxxxx> > > 5. file:///mc/compose?to=[38]
pasik@xxxxxx> > > 6. file:///mc/compose?to=[39]
pasik@xxxxxx> > > 7. file:///mc/compose?to=[40]
keir.fraser@xxxxxxxxxxxxx> > > 8. file:///mc/compose?to=[41]
feehapk@xxxxxxxxxxx> > > 9. file:///mc/compose?to=[42]
fajar@xxxxxxxxx> > > 10. file:///mc/compose?to=[43]
xen-devel@xxxxxxxxxxxxxxxxxxx> > > 11.
> > [4][44]
http://in.rd.yahoo.com/tagline_metro_2/*http:/in.yahoo.com/trynew> > > 12. file:///mc/compose?to=[45]
Xen-devel@xxxxxxxxxxxxxxxxxxx> > > 13. [5][46]
http://lists.xensource.com/xen-devel> > > 14.
> > [6][47]
http://in.rd.yahoo.com/tagline_metro_4/*http:/in.yahoo.com/trynew> >
> > _______________________________________________
> > Xen-devel mailing list
> > [48]
Xen-devel@xxxxxxxxxxxxxxxxxxx> > [7][49]
http://lists.xensource.com/xen-devel> >
> > ------------------------------------------------------------------------------
> >
> > From cricket scores to your friends. Try the
[8]Yahoo! India Homepage!
> >
> > --------------------------------------------------------------------------
> >
> > Now, send attachments up to 25MB with Yahoo! India Mail. [9]Learn how.
> >
> > References
> >
> > Visible links
> > 1. [50]
http://teo-en-ming-aka-zhang-enming.blogspot.com/> > 2. [51]
http://lists.xensource.com/xen-devel> > 3. [52]
http://teo-en-ming-aka-zhang-enming.blogspot.com/> > 4. [53]
http://in.rd.yahoo.com/tagline_metro_2/*http:/in.yahoo.com/trynew> > 5. [54]
http://lists.xensource.com/xen-devel> > 6. [55]
http://in.rd.yahoo.com/tagline_metro_4/*http:/in.yahoo.com/trynew> > 7. [56]
http://lists.xensource.com/xen-devel> > 8. [57]
http://in.rd.yahoo.com/tagline_metro_4/*http:/in.yahoo.com/trynew> > 9.
> [58]
http://in.rd.yahoo.com/tagline_galaxy_2/*http:/in.overview.mail.yahoo.com/photos>
> _______________________________________________
> Xen-devel mailing list
> [59]
Xen-devel@xxxxxxxxxxxxxxxxxxx> [60]
http://lists.xensource.com/xen-devel>
> --------------------------------------------------------------------------
>
> Connect more, do more and share more with Yahoo!
India Mail. [61]Learn
> more.
>
> References
>
> Visible links
> 1. file:///mc/compose?to=
feehapk@xxxxxxxxxxx> 2. file:///mc/compose?to=
feehapk@xxxxxxxxxxx> 3. file:///mc/compose?to=
pasik@xxxxxx> 4. file:///mc/compose?to=
fajar@xxxxxxxxx> 5. file:///mc/compose?to=
xen-devel@xxxxxxxxxxxxxxxxxxx> 6. file:///mc/compose?to=
space.time.universe@xxxxxxxxx> 7. file:///mc/compose?to=
keir.fraser@xxxxxxxxxxxxx> 8. file:///mc/compose?to=
pasik@xxxxxx> 9. file:///mc/compose?to=
pasik@xxxxxx> 10. file:///mc/compose?to=
feehapk@xxxxxxxxxxx> 11. file:///mc/compose?to=
fajar@xxxxxxxxx> 12. file:///mc/compose?to=
xen-devel@xxxxxxxxxxxxxxxxxxx> 13. file:///mc/compose?to=
space.time.universe@xxxxxxxxx> 14. file:///mc/compose?to=
keir.fraser@xxxxxxxxxxxxx> 15. file:///mc/compose?to=
space.time.universe@xxxxxxxxx> 16. file:///mc/compose?to=
space.time.universe@xxxxxxxxx> 17. file:///mc/compose?to=
feehapk@xxxxxxxxxxx> 18. file:///mc/compose?to=
keir.fraser@xxxxxxxxxxxxx> 19. file:///mc/compose?to=
pasik@xxxxxx> 20. file:///mc/compose?to=
fajar@xxxxxxxxx> 21. file:///mc/compose?to=
xen-devel@xxxxxxxxxxxxxxxxxxx> 22.
http://teo-en-ming-aka-zhang-enming.blogspot.com/> 23. file:///mc/compose?to=
space.time.universe@xxxxxxxxx> 24. file:///mc/compose?to=
teoenming@xxxxxxxxxxx> 25. file:///mc/compose?to=
feehapk@xxxxxxxxxxx> 26. file:///mc/compose?to=
pasik@xxxxxx> 27. file:///mc/compose?to=
pasik@xxxxxx> 28. file:///mc/compose?to=
keir.fraser@xxxxxxxxxxxxx> 29. file:///mc/compose?to=
feehapk@xxxxxxxxxxx> 30. file:///mc/compose?to=
fajar@xxxxxxxxx> 31. file:///mc/compose?to=
xen-devel@xxxxxxxxxxxxxxxxxxx> 32. file:///mc/compose?to=
Xen-devel@xxxxxxxxxxxxxxxxxxx> 33.
http://lists.xensource.com/xen-devel> 34.
http://teo-en-ming-aka-zhang-enming.blogspot.com/> 35. file:///mc/compose?to=
space.time.universe@xxxxxxxxx> 36. file:///mc/compose?to=
teoenming@xxxxxxxxxxx> 37. file:///mc/compose?to=
feehapk@xxxxxxxxxxx> 38. file:///mc/compose?to=
pasik@xxxxxx> 39. file:///mc/compose?to=
pasik@xxxxxx> 40. file:///mc/compose?to=
keir.fraser@xxxxxxxxxxxxx> 41. file:///mc/compose?to=
feehapk@xxxxxxxxxxx> 42. file:///mc/compose?to=
fajar@xxxxxxxxx> 43. file:///mc/compose?to=
xen-devel@xxxxxxxxxxxxxxxxxxx> 44.
http://in.rd.yahoo.com/tagline_metro_2/*http:/in.yahoo.com/trynew> 45. file:///mc/compose?to=
Xen-devel@xxxxxxxxxxxxxxxxxxx> 46.
http://lists.xensource.com/xen-devel> 47.
http://in.rd.yahoo.com/tagline_metro_4/*http:/in.yahoo.com/trynew> 48. file:///mc/compose?to=
Xen-devel@xxxxxxxxxxxxxxxxxxx> 49.
http://lists.xensource.com/xen-devel> 50.
http://teo-en-ming-aka-zhang-enming.blogspot.com/> 51.
http://lists.xensource.com/xen-devel> 52.
http://teo-en-ming-aka-zhang-enming.blogspot.com/> 53.
http://in.rd.yahoo.com/tagline_metro_2/*http:/in.yahoo.com/trynew> 54.
http://lists.xensource.com/xen-devel> 55.
http://in.rd.yahoo.com/tagline_metro_4/*http:/in.yahoo.com/trynew> 56.
http://lists.xensource.com/xen-devel> 57.
http://in.rd.yahoo.com/tagline_metro_4/*http:/in.yahoo.com/trynew> 58.
http://in.rd.yahoo.com/tagline_galaxy_2/*http:/in.overview.mail.yahoo.com/photos> 59. file:///mc/compose?to=
Xen-devel@xxxxxxxxxxxxxxxxxxx> 60.
http://lists.xensource.com/xen-devel> 61.
http://in.rd.yahoo.com/tagline_galaxy_3/*http:/in.overview.mail.yahoo.com/_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxhttp://lists.xensource.com/xen-devel