|
xen-users
Re: [Xen-users] working with latest -xen kernel?
Hi,
Boris! i have installed and run virt-manager successfully. After i boot into my xen paravirt kernel I got,
[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 : 131
node_to_cpu : node0:0-7
node_to_memory :
node0:131
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
[root@Server1-FC11 init.d]# xm list
Name ID Mem VCPUs State Time(s)
Domain-0 0 7948
8 r----- 11313.5
[root@Server1-FC11 init.d]# ifconfig
eth0 Link encap:Ethernet HWaddr 00:1E:4F:3A:72:B1
inet addr:10.11.21.31 Bcast:10.11.21.255 Mask:255.255.254.0
inet6 addr: fe80::21e:4fff:fe3a:72b1/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:772889 errors:0 dropped:0 overruns:0 frame:0
TX packets:384416 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1109703046 (1.0 GiB) TX bytes:38290313 (36.5 MiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:54105050 errors:0 dropped:0 overruns:0 frame:0
TX packets:54105050 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:651622265675 (606.8 GiB) TX bytes:651622265675 (606.8
GiB)
peth0 Link encap:Ethernet HWaddr 00:1E:4F:3A:72:B1
inet6 addr: fe80::21e:4fff:fe3a:72b1/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:773940 errors:0 dropped:0 overruns:0 frame:0
TX packets:387413 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1123688923 (1.0 GiB) TX bytes:40033135 (38.1 MiB)
Interrupt:16 Memory:d6000000-d6012700
virbr0 Link encap:Ethernet HWaddr FE:92:5A:81:A9:CD
inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:11 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:3463 (3.3 KiB)
[root@Server1-FC11 init.d]# brctl show
bridge name bridge id STP enabled interfaces
eth0
8000.001e4f3a72b1 yes peth0
pan0 8000.000000000000 no
Now I want to install paravirt xen guests. PFA, different screen shots of virt-manager while creating a VM. But the paravirt option is disabled and i am unable to select it. Why is that so?
Regards,
Fasiha Ashraf
--- On Fri, 16/10/09, Boris Derzhavets <bderzhavets@xxxxxxxxx> wrote:
From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
Subject: Re: [Xen-users] working with latest -xen kernel?
To: "Fajar A. Nugraha" <fajar@xxxxxxxxx>, "Fasiha Ashraf" <feehapk@xxxxxxxxxxx>
Cc:
xen-users@xxxxxxxxxxxxxxxxxxx
Date: Friday, 16 October, 2009, 11:24 PM
Did you also read his update on that post, linking to
http://bderzhavets.wordpress.com/2009/08/20/setup-libvirt-0-7-0-6-xen-3-4-1-dom0-on-to-fedora-11-64-bit/
?
> Yes
I did, but i have a question about it as well, Since i have compiled
xen with this kernel >version, Do i need to install it from rpm as well?
YES
# cd xen-3.4.1
# make uninstall
# rpm -iv xen-3.4.1-4.src.rpm
# cd rpmbuild/SPEC
# rpmbuild -ba ./xen.spec
. . . . . . . .
> or just i should skip that step and start installing libvirt?
NO
When xen 3.4.1 and tools are installed via generated rpms proceed with libvirt install
as suggested.
> Also tell
me should it be done from my dom0 or from the base kernel(nonexen)?
From base kernel environment.
Then install pvops ( or xenified kernel) , create grub entry and reboot.
Currently , 2.6.31.4 (pvops) is running in Dom0 on top of F11 in my environment.
Random xend crashes take place, service xend start to recover.
Boris.
--- On Fri, 10/16/09, Fasiha Ashraf <feehapk@xxxxxxxxxxx> wrote:
From: Fasiha Ashraf <feehapk@xxxxxxxxxxx>
Subject: Re: [Xen-users] working with latest -xen kernel?
To: "Fajar A. Nugraha" <fajar@xxxxxxxxx>
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Date: Friday, October 16, 2009, 3:33 AM
On Fri, Oct 16, 2009 at 11:54 AM, Fasiha Ashraf <feehapk@xxxxxxxxxxx> wrote:
>
> Hi,
>
I have noticed that you have build
xen-3-4-1-dom0-kernel-2-6-30-rc6-tip-on-top-of-fedora-11. Please help
in creating VMs it this case. my virt-manager and virt-install are not
working. and I am following this link to create xen DomUs http://bderzhavets.wordpress.com/2009/06/10/setup-fedora-11-pv-domu-at-xen-3-4-1-dom0-kernel-2-6-30-rc6-tip-on-top-of-fedora-11/#comment-618
Did you also read his update on that post, linking to
http://bderzhavets.wordpress.com/2009/08/20/setup-libvirt-0-7-0-6-xen-3-4-1-dom0-on-to-fedora-11-64-bit/
?
Yes I did, but i have a question about it as well, Since i have compiled xen with this kernel version, Do i need to install it from rpm as well? or just i should skip that step and start installing
libvirt?Also tell me should it be
done from my dom0 or from the base kernel(nonexen)?
>
> this error while running #vncviewer localhost:0
>
> Copyright (C) 2002-2005 RealVNC Ltd.
> Copyright (C) 2000-2006 TightVNC Group
> Copyright (C) 2004-2009 Peter Astrand for Cendio AB
> See http://www.tigervnc.org for information on TigerVNC.
> vncviewer: unable to open display “”
I'd start with running "xm list" and see if your domU is actually
running or not. After that, do something like
I am getting dom0 with running status
[root@Server1-FC11 xendoms]# xm list
Name
ID
Mem VCPUs State Time(s)
Domain-0 0 7077 8 r----- 64.9
F11-G1S1 1 500 1 -b---- 1.1
F11-G2S1
2 500 1 -b---- 1.1
netstat -anp | egrep "(:59)(.+)(LISTEN)"
[root@Server1-FC11 xendoms]# netstat -anp | egrep "(:59)(.+)(LISTEN)"
tcp 0 0 127.0.0.1:5900 0.0.0.0:* LISTEN 2490/qemu-dm
tcp 0
0 127.0.0.1:5901 0.0.0.0:* LISTEN 2623/qemu-dm
to see if there's any process listening on port 5900+. If a domU was
started and it has a vnc GUI, there should be some qemu-dm process
shown there.
>
> Also i have some confusion about disk specs what i use are:
> disk = [ 'phy:/dev/loop0,xvda,w' ]
> Cause i am not using lvm. Here is my
Where does loop0 come from? If you're using disk/partition as domU
storage you can simply specify the block device (e.g. /dev/sdb,
/dev/sda4, etc.). If you're using file you can directly use tap:aio.
[root@Server1-FC11 xendoms]# fdisk -l
Disk /dev/sda: 438.4 GB, 438489317376 bytes
255 heads, 63 sectors/track, 53309 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000080
Device Boot Start End Blocks Id System
/dev/sda1 1 13 104391 83 Linux
/dev/sda2 14 2180 17406427+ 82 Linux swap / Solaris
/dev/sda3 2181 42776 326087370 83 Linux
/dev/sda4 42777 53309 84606322+ 5 Extended
/dev/sda5 * 42777 53309 84606291 83 Linux
>
> my disk specs are right or not? Any suggestions??
I'm guessing you specified the wrong disk and domU didn't start at all.
I am not using LVM partitions. when i specified one dom disk as /dev/sda i have nothing for next dom. In such situation is it good to use file? like u suggest.
--
Fajar
_______________________________________________
Xen-users
mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users |
Yahoo! India has a new look. Take a sneak peek.
-----Inline Attachment Follows-----
|
-----Inline Attachment Follows-----
|
Yahoo! India has a new look. Take a sneak peek._______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
Home