[Fedora-xen] VNC session Fedora 16 (TC) running as PV domU doesn't grab mouse pointer
Xen 4.1.2 with pygrub gpt patches back ported installed on top of Ubuntu 11.10. Virt-install'ed F16 PV guest. After domain gets created VNC login screen shows up. Mouse should be kept always inside VNC screen. Otherwise , it will disappear. Start F16 domU via virsh and connection via vncviewer gives working mouse pointer, which looks like dot in VNC session, but gets grabbed. Boris. -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Virt-install hangs installing F16 (TC) with --nographics option
Did that exact line of arguments work with F15? Yes, works fine Why are you using '--nographics' without the 'serial text' argument? Please, point to an exact syntax. It was never required before. Does it work if you do not use '--nographics'? Yes. --vnc works as earlier. No problems Boris. --- On Mon, 10/24/11, Konrad Rzeszutek Wilk konrad.w...@oracle.com wrote: From: Konrad Rzeszutek Wilk konrad.w...@oracle.com Subject: Re: [Fedora-xen] Virt-install hangs installing F16 (TC) with --nographics option To: Boris Derzhavets bderzhav...@yahoo.com Cc: xen@lists.fedoraproject.org Date: Monday, October 24, 2011, 10:29 AM On Mon, Oct 24, 2011 at 06:00:30AM -0700, Boris Derzhavets wrote: virt-install --connect xen:/// --debug -n VF16PV --nographics -p -r 2048\ --vcpus=2 -f /dev/sdb8 -l -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] 2.6.38-rc dom0 kernel and xen 4.1.0-rc2
Attempt to create F14 DomU : name=VF14 memory=2048 disk = ['file:/tmp/disk1.img,xvda,w' ] vif = [ 'bridge=br0' ] # vfb = [ 'type=vnc,vncunused=1'] kernel = /home/boris/fedora/vmlinuz ramdisk = /home/boris/fedora/initrd.img vcpus=2 on_reboot = 'restart' on_crash = 'restart' # xl create -c f14.install Parsing config file f14.install Daemon running with PID 3311 [ 0.00] Initializing cgroup subsys cpuset [ 0.00] Initializing cgroup subsys cpu [ 0.00] Linux version 2.6.35.6-45.fc14.x86_64 (mockbu...@x86-02.phx2.fedoraproject.org) (gcc version 4.5.1 20100924 (Red Hat 4.5.1-4) (GCC) ) #1 SMP Mon Oct 18 23:57:44 UTC 2010 [ 0.00] Command line: [ 0.00] ACPI in unprivileged domain disabled [ 0.00] BIOS-provided physical RAM map: [ 0.00] Xen: - 000a (usable) [ 0.00] Xen: 000a - 0010 (reserved) [ 0.00] Xen: 0010 - 8000 (usable) [ 0.00] NX (Execute Disable) protection: active [ 0.00] DMI not present or invalid. [ 0.00] No AGP bridge found [ 0.00] last_pfn = 0x8 max_arch_pfn = 0x4 [ 0.00] init_memory_mapping: -8000 [ 0.00] RAMDISK: 01e63000 - 058c [ 0.00] No NUMA configuration found [ 0.00] Faking a node at -8000 [ 0.00] Initmem setup node 0 -8000 [ 0.00] NODE_DATA [01e42880 - 01e5687f] [ 0.00] bootmap [05cf6000 - 05d05fff] pages 10 [ 0.00] (9/32 early reservations) == bootmem [00 - 008000] [ 0.00] #0 [0005cc3000 - 0005cf6000] XEN PAGETABLES == [0005cc3000 - 0005cf6000] [ 0.00] #1 [000100 - 0001e42878] TEXT DATA BSS == [000100 - 0001e42878] [ 0.00] #2 [0001e63000 - 00058c] RAMDISK == [0001e63000 - 00058c] [ 0.00] #3 [00058c - 0005cc3000] XEN START INFO == [00058c - 0005cc3000] [ 0.00] #4 [001000 - 003000] TRAMPOLINE == [001000 - 003000] [ 0.00] #5 [003000 - 007000] ACPI WAKEUP == [003000 - 007000] [ 0.00] #6 [10 - 4cd000] PGTABLE == [10 - 4cd000] [ 0.00] #7 [0001e42880 - 0001e56880] NODE_DATA == [0001e42880 - 0001e56880] [ 0.00] #8 [0005cf6000 - 0005d06000] BOOTMAP == [0005cf6000 - 0005d06000] [ 0.00] Zone PFN ranges: [ 0.00] DMA 0x0001 - 0x1000 [ 0.00] DMA32 0x1000 - 0x0010 [ 0.00] Normal empty [ 0.00] Movable zone start PFN for each node [ 0.00] early_node_map[2] active PFN ranges [ 0.00] 0: 0x0001 - 0x00a0 [ 0.00] 0: 0x0100 - 0x0008 [ 0.00] SFI: Simple Firmware Interface v0.81 http://simplefirmware.org [ 0.00] SMP: Allowing 2 CPUs, 0 hotplug CPUs [ 0.00] No local APIC present [ 0.00] APIC: disable apic facility [ 0.00] APIC: switched to apic NOOP [ 0.00] PM: Registered nosave memory: 000a - 0010 [ 0.00] Allocating PCI resources starting at 8000 (gap: 8000:8000) [ 0.00] Booting paravirtualized kernel on Xen [ 0.00] Xen version: 4.1.0-rc2 (preserve-AD) [ 0.00] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:2 nr_node_ids:1 [ 0.00] PERCPU: Embedded 30 pages/cpu @880005d3c000 s90496 r8192 d24192 u122880 [ 0.00] pcpu-alloc: s90496 r8192 d24192 u122880 alloc=30*4096 [ 0.00] pcpu-alloc: [0] 0 [0] 1 [ 0.00] Xen: using vcpu_info placement [ 0.00] Built 1 zonelists in Node order, mobility grouping on. Total pages: 516044 [ 0.00] Policy zone: DMA32 [ 0.00] Kernel command line: [ 0.00] PID hash table entries: 4096 (order: 3, 32768 bytes) [ 0.00] Checking aperture... [ 0.00] No AGP bridge found [ 0.00] Memory: 1984848k/2097152k available (4548k kernel code, 388k absent, 111916k reserved, 7261k data, 944k init) [ 0.00] SLUB: Genslabs=14, HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1 [ 0.00] Hierarchical RCU implementation. [ 0.00] RCU dyntick-idle grace-period acceleration is enabled. [ 0.00] RCU-based detection of stalled CPUs is disabled. [ 0.00] Verbose stalled-CPUs detection is disabled. [ 0.00] NR_IRQS:16640 nr_irqs:288 [ 0.00] Console: colour dummy device 80x25 [ 0.00] console [tty0] enabled [ 0.00] console [hvc0] enabled [ 0.00] allocated 20971520 bytes of page_cgroup [ 0.00] please try 'cgroup_disable=memory' option if you don't want memory cgroups [ 0.00] installing Xen timer for CPU 0 [ 0.00] Detected 2833.086 MHz processor. [ 0.000999] Calibrating delay loop (skipped), value
Re: [Fedora-xen] 2.6.37-rc1 dom0 kernel
I've tested the most recent kernel from Michael Young http://koji.fedoraproject.org/koji/taskinfo?taskID=2598434 kernel vmlinuz-2.6.37-0.1.rc1.git8.xendom0.fc14.x86_64(rc1.git8 + xen-next.patch) as Dom0 kernel under Xen 4.0.1 on top of F14. Attempt to work with NFS remote folder results kernel crash again - unable to handle paging request and stack trace. Kernel works OK only as vanilla. Boris. P.S. Same issue is in place for PV DomU running kernel vmlinuz-2.6.37-0.1.rc1.git8.xendom0.fc14.x86_64 -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] [fedora-virt] Dom0 xen support in Fedora 15?
Config (.config) might be different for pvops kernel running as vanilla or under xen. Boris. --- On Wed, 11/10/10, Daniel P. Berrange berra...@redhat.com wrote: From: Daniel P. Berrange berra...@redhat.com Subject: Re: [fedora-virt] [Fedora-xen] Dom0 xen support in Fedora 15? To: Richard W.M. Jones rjo...@redhat.com Cc: Boris Derzhavets bderzhav...@yahoo.com, Bill Davidsen david...@tmr.com, xen@lists.fedoraproject.org, v...@lists.fedoraproject.org Date: Wednesday, November 10, 2010, 5:30 AM On Wed, Nov 10, 2010 at 09:55:19AM +, Richard W.M. Jones wrote: On Tue, Nov 09, 2010 at 10:40:10AM -0800, Boris Derzhavets wrote: And I would hope that the installer would be clever enough to see if KVM is supported and offer xen if not. Doesn't need to be default, available is fine. What if i don't want KVM install no matter of hardware ? I will want Xen on icore7 + ASUS P6TDT+ 16 GB RAM , Dell PowerEdge and so on ... I guess you will have to manually yum install kernel-xen. We can't magically know your preference, but it makes sense to default to KVM (by which I am really saying default to a plain Linux kernel) because that is far less intrusive for users. NB, there is no kernel-xen anymore with pvops dom0. To enable xen you just need to yum install xen-hypervisor and update grub to boot the kernel under the hypervisor Regards, Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://deltacloud.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] [fedora-virt] Dom0 xen support in Fedora 15?
Exactly, i only need on Fedora :) # yum install kernel-xen Boris. --- On Wed, 11/10/10, Richard W.M. Jones rjo...@redhat.com wrote: From: Richard W.M. Jones rjo...@redhat.com Subject: Re: [fedora-virt] [Fedora-xen] Dom0 xen support in Fedora 15? To: Boris Derzhavets bderzhav...@yahoo.com Cc: Daniel P. Berrange berra...@redhat.com, Bill Davidsen david...@tmr.com, xen@lists.fedoraproject.org, v...@lists.fedoraproject.org Date: Wednesday, November 10, 2010, 4:55 AM On Tue, Nov 09, 2010 at 10:40:10AM -0800, Boris Derzhavets wrote: And I would hope that the installer would be clever enough to see if KVM is supported and offer xen if not. Doesn't need to be default, available is fine. What if i don't want KVM install no matter of hardware ? I will want Xen on icore7 + ASUS P6TDT+ 16 GB RAM , Dell PowerEdge and so on ... I guess you will have to manually yum install kernel-xen. We can't magically know your preference, but it makes sense to default to KVM (by which I am really saying default to a plain Linux kernel) because that is far less intrusive for users. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming blog: http://rwmj.wordpress.com Fedora now supports 80 OCaml packages (the OPEN alternative to F#) http://cocan.org/getting_started_with_ocaml_on_red_hat_and_fedora -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] [Xen-users] Re: 2.6.37-rc1 dom0 kernel
I've again tried to adjust kernel.spec from kernel-2.6.37-0.1.rc1.git0.xendom0.fc15.src.rpm to rcrev=1 ; gitrev=5 and build started OK. Boris. --- On Sun, 11/7/10, Boris Derzhavets bderzhav...@yahoo.com wrote: From: Boris Derzhavets bderzhav...@yahoo.com Subject: [Xen-users] Re: [Fedora-xen] 2.6.37-rc1 dom0 kernel To: M A Young m.a.yo...@durham.ac.uk Cc: xen@lists.fedoraproject.org, xen-users xen-us...@lists.xensource.com Date: Sunday, November 7, 2010, 8:43 AM I've tried to adjust kernel.spec from kernel-2.6.37-0.1.rc0.git13.xendom0.fc15.src.rpm to rcrevision = 1, gitrevision =5 . # The rc snapshot level %define rcrev 1 # The git snapshot level %define gitrev 5 . Files patch-2.6.37-rc1.bz2, patch-2.6.37-rc1-git5.bz2 have been copied to SOURCES I get an error when attempt to build :- # rpmbuild -bb ./kernel.spec ... Patch161: linux-2.6-i386-nx-emulation.patch + case $patch in + patch -p1 -F1 -s + ApplyPatch linux-2.6-32bit-mmap-exec-randomization.patch + local patch=linux-2.6-32bit-mmap-exec-randomization.patch + shift + '[' '!' -f /root/rpmbuild/SOURCES/linux-2.6-32bit-mmap-exec-randomization.patch ']' Patch160: linux-2.6-32bit-mmap-exec-randomization.patch + case $patch in + patch -p1 -F1 -s 1 out of 5 hunks FAILED -- saving rejects to file mm/mmap.c.rej error: Bad exit status from /var/tmp/rpm-tmp.FmT4Fy (%prep) Boris. P.S. I've also tried to adjust kernel.spec from kernel-2.6.37-0.1.rc1.git0.xendom0.fc15.src.rpm with results even worse then above:- Patch32: linux-2.6-utrace-ptrace.patch failed to apply. --- On Sat, 11/6/10, M A Young m.a.yo...@durham.ac.uk wrote: From: M A Young m.a.yo...@durham.ac.uk Subject: Re: [Fedora-xen] 2.6.37-rc1 dom0 kernel To: Boris Derzhavets bderzhav...@yahoo.com Cc: xen@lists.fedoraproject.org, xen-users xen-us...@lists.xensource.com Date: Saturday, November 6, 2010, 9:29 AM On Sat, 6 Nov 2010, Boris Derzhavets wrote: ... [ 42.140012] Call Trace: [ 42.140012] [810807a8] ? print_irqtrace_events+0xa0/0xa4 [ 42.140012] [81043256] __might_sleep+0x103/0x108 [ 42.140012] [814b0512] mutex_lock_nested+0x25/0x43 [ 42.140012] [8125ae02] percpu_counter_destroy+0x3c/0x66 [ 42.140012] [8125ae42] percpu_counter_fixup_free+0x16/0x32 [ 42.140012] [8125723b] debug_object_fixup+0x1e/0x2b [ 42.140012] [81257c54] debug_check_no_obj_freed+0xce/0x18a ... This is probably a result of a percpu_counter bug in an IPv6 patch. As a temporary measure you can disable IPv6 (if you don't need it), eg. as suggested at http://fedorasolved.org/network-solutions/disable-ipv6 It was patched after rc1 http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6-stable.git;a=commit;h=41bb78b4b9adb21cf2c395b6b880aaae99c788b7 so should be fixed when I next do a build of 2.6.37 . Michael Young -Inline Attachment Follows- ___ Xen-users mailing list xen-us...@lists.xensource.com http://lists.xensource.com/xen-users -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] [Xen-users] Re: 2.6.37-rc1 dom0 kernel
Done . . . . . . . Wrote: /root/rpmbuild/RPMS/x86_64/kernel-2.6.37-0.1.rc1.git5.xendom0.fc14.x86_64.rpm Wrote: /root/rpmbuild/RPMS/x86_64/kernel-headers-2.6.37-0.1.rc1.git5.xendom0.fc14.x86_64.rpm Wrote: /root/rpmbuild/RPMS/x86_64/kernel-debuginfo-common-x86_64-2.6.37-0.1.rc1.git5.xendom0.fc14.x86_64.rpm Wrote: /root/rpmbuild/RPMS/x86_64/perf-2.6.37-0.1.rc1.git5.xendom0.fc14.x86_64.rpm Wrote: /root/rpmbuild/RPMS/x86_64/kernel-devel-2.6.37-0.1.rc1.git5.xendom0.fc14.x86_64.rpm Wrote: /root/rpmbuild/RPMS/x86_64/kernel-debuginfo-2.6.37-0.1.rc1.git5.xendom0.fc14.x86_64.rpm Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.vzYwPP + umask 022 + cd /root/rpmbuild/BUILD + cd kernel-2.6.36.fc14 + rm -rf /root/rpmbuild/BUILDROOT/kernel-2.6.37-0.1.rc1.git5.xendom0.fc14.x86_64 + exit 0 --- On Sun, 11/7/10, Boris Derzhavets bderzhav...@yahoo.com wrote: From: Boris Derzhavets bderzhav...@yahoo.com Subject: Re: [Xen-users] Re: [Fedora-xen] 2.6.37-rc1 dom0 kernel To: M A Young m.a.yo...@durham.ac.uk Cc: xen@lists.fedoraproject.org, xen-users xen-us...@lists.xensource.com Date: Sunday, November 7, 2010, 9:28 AM I've again tried to adjust kernel.spec from kernel-2.6.37-0.1.rc1.git0.xendom0.fc15.src.rpm to rcrev=1 ; gitrev=5 and build started OK. Boris. --- On Sun, 11/7/10, Boris Derzhavets bderzhav...@yahoo.com wrote: From: Boris Derzhavets bderzhav...@yahoo.com Subject: [Xen-users] Re: [Fedora-xen] 2.6.37-rc1 dom0 kernel To: M A Young m.a.yo...@durham.ac.uk Cc: xen@lists.fedoraproject.org, xen-users xen-us...@lists.xensource.com Date: Sunday, November 7, 2010, 8:43 AM I've tried to adjust kernel.spec from kernel-2.6.37-0.1.rc0.git13.xendom0.fc15.src.rpm to rcrevision = 1, gitrevision =5 . # The rc snapshot level %define rcrev 1 # The git snapshot level %define gitrev 5 . Files patch-2.6.37-rc1.bz2, patch-2.6.37-rc1-git5.bz2 have been copied to SOURCES I get an error when attempt to build :- # rpmbuild -bb ./kernel.spec ... Patch161: linux-2.6-i386-nx-emulation.patch + case $patch in + patch -p1 -F1 -s + ApplyPatch linux-2.6-32bit-mmap-exec-randomization.patch + local patch=linux-2.6-32bit-mmap-exec-randomization.patch + shift + '[' '!' -f /root/rpmbuild/SOURCES/linux-2.6-32bit-mmap-exec-randomization.patch ']' Patch160: linux-2.6-32bit-mmap-exec-randomization.patch + case $patch in + patch -p1 -F1 -s 1 out of 5 hunks FAILED -- saving rejects to file mm/mmap.c.rej error: Bad exit status from /var/tmp/rpm-tmp.FmT4Fy (%prep) Boris. P.S. I've also tried to adjust kernel.spec from kernel-2.6.37-0.1.rc1.git0.xendom0.fc15.src.rpm with results even worse then above:- Patch32: linux-2.6-utrace-ptrace.patch failed to apply. --- On Sat, 11/6/10, M A Young m.a.yo...@durham.ac.uk wrote: From: M A Young m.a.yo...@durham.ac.uk Subject: Re: [Fedora-xen] 2.6.37-rc1 dom0 kernel To: Boris Derzhavets bderzhav...@yahoo.com Cc: xen@lists.fedoraproject.org, xen-users xen-us...@lists.xensource.com Date: Saturday, November 6, 2010, 9:29 AM On Sat, 6 Nov 2010, Boris Derzhavets wrote: ... [ 42.140012] Call Trace: [ 42.140012] [810807a8] ? print_irqtrace_events+0xa0/0xa4 [ 42.140012] [81043256] __might_sleep+0x103/0x108 [ 42.140012] [814b0512] mutex_lock_nested+0x25/0x43 [ 42.140012] [8125ae02] percpu_counter_destroy+0x3c/0x66 [ 42.140012] [8125ae42] percpu_counter_fixup_free+0x16/0x32 [ 42.140012] [8125723b] debug_object_fixup+0x1e/0x2b [ 42.140012] [81257c54] debug_check_no_obj_freed+0xce/0x18a ... This is probably a result of a percpu_counter bug in an IPv6 patch. As a temporary measure you can disable IPv6 (if you don't need it), eg. as suggested at http://fedorasolved.org/network-solutions/disable-ipv6 It was patched after rc1 http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6-stable.git;a=commit;h=41bb78b4b9adb21cf2c395b6b880aaae99c788b7 so should be fixed when I next do a build of 2.6.37 . Michael Young -Inline Attachment Follows- ___ Xen-users mailing list xen-us...@lists.xensource.com http://lists.xensource.com/xen-users -Inline Attachment Follows- ___ Xen-users mailing list xen-us...@lists.xensource.com http://lists.xensource.com/xen-users -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] xen and dom0 kernel builds
Are you planning to get xen-4.0.1-3.fc14 to F14 before it goes GA? That would be good.. The most recent yum update installs xen-4.0.1-4.fc14 on F14 ( rawhide) Boris. --- On Sun, 10/3/10, Pasi Kärkkäinen pa...@iki.fi wrote: From: Pasi Kärkkäinen pa...@iki.fi Subject: Re: [Fedora-xen] xen and dom0 kernel builds To: M A Young m.a.yo...@durham.ac.uk Cc: xen@lists.fedoraproject.org Date: Sunday, October 3, 2010, 11:59 AM On Fri, Sep 24, 2010 at 11:02:00PM +0100, M A Young wrote: I have built a new kernel (kernel-2.6.32.21-168.xendom0.fc12) at http://koji.fedoraproject.org/koji/taskinfo?taskID=2477887 or at the repository http://repos.fedorapeople.org/repos/myoung/dom0-kernel/ It includes fixes for the recent x86_64 local root exploit. There are also some new builds of xen. The Fedora packages xen-4.0.1-3.fc15 and xen-4.0.1-3.fc14 available via http://koji.fedoraproject.org/koji/packageinfo?packageID=7 have some IRQ fixes that solve a problem I was having with a keyboard and mouse and the patch that disables xsave which was causing problems with HVM (both these are from 4.0.2-rc1-pre). It also creates a symbolic link for qemu-dm from the place it was in 3.4.x to where it is in 4.0.x for compatibility. Are you planning to get xen-4.0.1-3.fc14 to F14 before it goes GA? That would be good.. It seems the current F14 tree still has xen-4.0.1-1.fc14.src.rpm. I also have a temporary test build xen-4.0.1-1.fc13.1 for Fedora 13 at http://koji.fedoraproject.org/koji/taskinfo?taskID=2478501 . This is slightly misnamed as it is actually of 4.0.2-rc1-pre and includes the fixes above. Note that he build system will delete those RPMs automatically after a week or so. Could you upload xen-4.0.1-1.fc13.1 src.rpm somewhere? I'd like to mirror it, some people might want to get it also now when it's removed from that koji page.. -- Pasi -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] [Xen-devel] Re: [Xen-users] Step-by-step tutorial: Installing Xen 4.0.1 rpms on Fedora 13 with pvops Linux 2.6.32.x dom0 kernel
Note about disk partitioning: Make /boot partition the primary (first) partition and choose the filesystem type as ext3 (not ext4 - which is the default) It was written concerning Dom0 set-up on top F13 not DomU Boris. --- On Mon, 9/6/10, Jeremy Fitzhardinge jer...@goop.org wrote: From: Jeremy Fitzhardinge jer...@goop.org Subject: Re: [Xen-devel] Re: [Xen-users] Step-by-step tutorial: Installing Xen 4.0.1 rpms on Fedora 13 with pvops Linux 2.6.32.x dom0 kernel To: Pasi Kärkkäinen pa...@iki.fi Cc: xen@lists.fedoraproject.org, Boris Derzhavets bderzhav...@yahoo.com, xen-de...@lists.xensource.com, v...@lists.fedoraproject.org, xen-us...@lists.xensource.com Date: Monday, September 6, 2010, 8:57 PM On 09/05/2010 10:20 PM, Pasi Kärkkäinen wrote: On Sun, Sep 05, 2010 at 05:18:07AM -0700, Boris Derzhavets wrote: Note about disk partitioning: Make /boot partition the primary (first) partition and choose the filesystem type as ext3 (not ext4 - which is the default) Could you , please , explain why ? It's just in case. It's not really required. I prefer making sure every tool out there can read /boot partition to avoid problems :) pvgrub can't handle ext4 partitions, and does so in a non-obvious way (often by just going into a spin loop...). J ___ Xen-users mailing list xen-us...@lists.xensource.com http://lists.xensource.com/xen-users -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Xen Dom0 and Fedora 14
/usr/lib64/python2.7/site-packages/xen/util/pci.py stays untouched Dmesg log attached [r...@fedora14 ~]# xm info Traceback (most recent call last): File /usr/sbin/xm, line 5, in module from xen.xm import main File /usr/lib64/python2.7/site-packages/xen/xm/main.py, line 41, in module from xen.util.pci import * File /usr/lib64/python2.7/site-packages/xen/util/pci.py, line 937 pos = 0 ^ IndentationError: expected an indented block Convert /usr/lib64/python2.7/site-packages/xen/util/pci.py back as it was [r...@fedora14 ~]# vi /usr/lib64/python2.7/site-packages/xen/util/pci.py [r...@fedora14 ~]# service xend start Starting xend daemon: [ OK ] [r...@fedora14 ~]# service xenconsoled start Starting xenconsoled daemon: [ OK ] [r...@fedora14 ~]# xm info host : fedora14 release : 2.6.32.19-xen version : #4 SMP Fri Sep 3 22:10:56 MSD 2010 machine : x86_64 nr_cpus : 4 nr_nodes : 1 cores_per_socket : 4 threads_per_core : 1 cpu_mhz : 2833 hw_caps : bfebfbff:20100800::0940:0408e3fd::0001: virt_caps : hvm total_memory : 8190 free_memory : 1671 node_to_cpu : node0:0-3 node_to_memory : node0:1671 node_to_dma32_mem : node0:841 max_node_id : 0 xen_major : 4 xen_minor : 0 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=0x8000 xen_changeset : unavailable xen_commandline : cc_compiler : gcc version 4.5.1 20100812 (Red Hat 4.5.1-1) (GCC) cc_compile_by : root cc_compile_domain : cc_compile_date : Fri Sep 3 21:16:54 MSD 2010 xend_config_format : 4 Boris. --- On Wed, 9/1/10, W. Michael Petullo m...@flyn.org wrote: From: W. Michael Petullo m...@flyn.org Subject: [Fedora-xen] Xen Dom0 and Fedora 14 To: xen@lists.fedoraproject.org Date: Wednesday, September 1, 2010, 2:42 PM I have been investigating the use of Xen with a Fedora 14 (devel)-based Dom0. Until now, I have always used Michael Young's Dom0 kernels. The first thing I did was try to build the current Fedora 14 kernel with Xen Dom0 support. I began porting Michael's RPM specification to the Fedora 14 specification. What I found was that the Xen pvops work seems to be targeting 2.6.32 and possibly 2.6.36. As a result, I was unable to find a straightforward way to create a patch for 2.6.35.4. Am I missing something here? Is building a 2.6.35.4-based kernel difficult in this way? Next, I tried to use Michael's latest Fedora 12 kernel on Fedora 14. Of course, Fedora 14 uses some features that are not available in this kernel. Most notably, I had to provide the kernel with the init=/sbin/upstart option to avoid the use of systemd. Once I booted the system, I found that xend would not start because it did not find what it expected in /sys/bus/pci/devices/\:00\:03.2/config: [...] File /usr/lib/python2.7/site-packages/xen/util/pci.py, line 1050, in detect_dev_info pos = self.find_cap_offset(PCI_CAP_ID_EXP) File /usr/lib/python2.7/site-packages/xen/util/pci.py, line 933, in find_cap_offset id = ord(os.read(fd, 1)) TypeError: ord() expected a character, but string of length 0 found I fixed this by editing pci.py and changing: id = ord(os.read(fd, 1)) to: try: id = ord(os.read(fd, 1)) except: pos = 0 break; Of course, this might not be a good fix, but it was quick and it allowed me to continue and experiment. Does anyone know what is going on here? At this point, I was able to boot a DomU image, although I need to do a lot more testing. Has anyone else experimented with Fedora 14? What is your experience? I am especially interested in hearing about Fedora 14 Dom0 kernels. -- Mike :wq -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen dmesgXen401@F14.log.gz Description: GNU Zip compressed data -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Move from Fedora 8 dom0s to F12/F13 dom0s with Xen 4.0.x questions
With 2.6.32.13 RH's PV guests (F13,RHL6 Beta tested) do detect NAT interface and can smoothly installed via virt-manager ( virt-install). However, Ubuntu Lucid Official xenified installer is still failing with NAT and requires old style network bridging, OSOL 134 behaves same way. Boris. --- On Tue, 5/18/10, Boris Derzhavets bderzhav...@yahoo.com wrote: From: Boris Derzhavets bderzhav...@yahoo.com Subject: Re: [Fedora-xen] Move from Fedora 8 dom0s to F12/F13 dom0s with Xen 4.0.x questions To: xen@lists.fedoraproject.org, fcxen user fc...@itsbeen.sent.com Date: Tuesday, May 18, 2010, 2:11 AM So, installed Xen 4.0 via MY's src.rpm on top F13 i had to set up manually br0 for PV Guests, HVM seems to be OK with NAT ( or br0 no matter) # chkconfig NetworkManager off # chkconfig network on Reboot VNC console doesn't get launched for virt-installs of PV guests , referencing br0. Virt-install should run in nographics mode with VNC setup at DomU for Fedoras,CentOS guests. I might did something wrong, but at the moment Xen 4.0 / Virt-managerVirt-install regression vs F12 is taken place. Boris. --- On Mon, 5/17/10, Boris Derzhavets bderzhav...@yahoo.com wrote: From: Boris Derzhavets bderzhav...@yahoo.com Subject: Re: [Fedora-xen] Move from Fedora 8 dom0s to F12/F13 dom0s with Xen 4.0.x questions To: xen@lists.fedoraproject.org, fcxen user fc...@itsbeen.sent.com Date: Monday, May 17, 2010, 11:49 PM I had to disable Xen bridging and setup bridge manually to be able to work with PV guests . In other words all xen bridged networking has to be commented out on F13 and at the same time PV guest cannot obtain IP via virbr0 It doesn't happen on F12. --- On Mon, 5/17/10, Boris Derzhavets bderzhav...@yahoo.com wrote: From: Boris Derzhavets bderzhav...@yahoo.com Subject: Re: [Fedora-xen] Move from Fedora 8 dom0s to F12/F13 dom0s with Xen 4.0.x questions To: xen@lists.fedoraproject.org, fcxen user fc...@itsbeen.sent.com Date: Monday, May 17, 2010, 1:44 PM What i am not sure about is libvirt,virtinst,... behavior when working with Xen 4.0 on F13 Libvirt 0.7.7 and all related stuff (virsh,virt-manager,virt-install) seem to work fine at Xen 4.0 Dom0 ( pvops 2.6.31.13) on top of F13. Even HVM install now could be performed via virt-manager. Auto detecting Xen Hypervisor and several attempts suggesting KVM answered negative make strong impression. I thought it would ask me to install KVM every time at virt-manager start. [r...@fedorasrv ~]# virsh version Compiled against library: libvir 0.7.7 Using library: libvir 0.7.7 Using API: Xen 3.0.1 Running hypervisor: Xen 4.0.0 Boris. --- On Sun, 5/16/10, Boris Derzhavets bderzhav...@yahoo.com wrote: From: Boris Derzhavets bderzhav...@yahoo.com Subject: Re: [Fedora-xen] Move from Fedora 8 dom0s to F12/F13 dom0s with Xen 4.0.x questions To: xen@lists.fedoraproject.org, fcxen user fc...@itsbeen.sent.com Date: Sunday, May 16, 2010, 12:35 AM * I use virsh define to create the VM configurations using virsh xml, and I assume that virsh/libvirtd won't work on a recent 2.6.32/33/3x kernel and Xen 4.0.0 * Although Pasi, Michael, Dale and others have been very generous with their information, testing and development, I am not completely clear on all the steps required to get a working F12/F13/ Xen 4.0.X dom0 with 2.6.32/33/3x kernel starting from a base F12/F13 system install. If someone can point out where to find different parts I would be grateful and would be willing to consolidate them into a single blob if that doesn't already exist. Responding both questions (for F12) :- http://www.linuxtoday.com/high_performance/2010041500635OSSV What i am not sure about is libvirt,virtinst,... behavior when working with Xen 4.0 on F13 Boris. -Inline Attachment Follows- -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen -Inline Attachment Follows- -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen -Inline Attachment Follows- -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen -Inline Attachment Follows- -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Move from Fedora 8 dom0s to F12/F13 dom0s with Xen 4.0.x questions
I had to disable Xen bridging and setup bridge manually to be able to work with PV guests . In other words all xen bridged networking has to be commented out on F13 and at the same time PV guest cannot obtain IP via virbr0 It doesn't happen on F12. --- On Mon, 5/17/10, Boris Derzhavets bderzhav...@yahoo.com wrote: From: Boris Derzhavets bderzhav...@yahoo.com Subject: Re: [Fedora-xen] Move from Fedora 8 dom0s to F12/F13 dom0s with Xen 4.0.x questions To: xen@lists.fedoraproject.org, fcxen user fc...@itsbeen.sent.com Date: Monday, May 17, 2010, 1:44 PM What i am not sure about is libvirt,virtinst,... behavior when working with Xen 4.0 on F13 Libvirt 0.7.7 and all related stuff (virsh,virt-manager,virt-install) seem to work fine at Xen 4.0 Dom0 ( pvops 2.6.31.13) on top of F13. Even HVM install now could be performed via virt-manager. Auto detecting Xen Hypervisor and several attempts suggesting KVM answered negative make strong impression. I thought it would ask me to install KVM every time at virt-manager start. [r...@fedorasrv ~]# virsh version Compiled against library: libvir 0.7.7 Using library: libvir 0.7.7 Using API: Xen 3.0.1 Running hypervisor: Xen 4.0.0 Boris. --- On Sun, 5/16/10, Boris Derzhavets bderzhav...@yahoo.com wrote: From: Boris Derzhavets bderzhav...@yahoo.com Subject: Re: [Fedora-xen] Move from Fedora 8 dom0s to F12/F13 dom0s with Xen 4.0.x questions To: xen@lists.fedoraproject.org, fcxen user fc...@itsbeen.sent.com Date: Sunday, May 16, 2010, 12:35 AM * I use virsh define to create the VM configurations using virsh xml, and I assume that virsh/libvirtd won't work on a recent 2.6.32/33/3x kernel and Xen 4.0.0 * Although Pasi, Michael, Dale and others have been very generous with their information, testing and development, I am not completely clear on all the steps required to get a working F12/F13/ Xen 4.0.X dom0 with 2.6.32/33/3x kernel starting from a base F12/F13 system install. If someone can point out where to find different parts I would be grateful and would be willing to consolidate them into a single blob if that doesn't already exist. Responding both questions (for F12) :- http://www.linuxtoday.com/high_performance/2010041500635OSSV What i am not sure about is libvirt,virtinst,... behavior when working with Xen 4.0 on F13 Boris. -Inline Attachment Follows- -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen -Inline Attachment Follows- -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
