June 2010 - openSUSE Virtual - openSUSE Mailing Lists

[opensuse-virtual] a 'marketing' question ...
by 0bo0 01 Jul '10

01 Jul '10

i'll be the 1st to admit I don't always see eye-to-eye with the Suse, Opensuse & Virtualization efforts' actions, directions, etc. but in the end, it's, imo, the only solid distro-supported Xen/Virtualization solution out there. modern kernel, Xen4, PCI/USB/etc-Passthrough, etc are all there (I won't start re: PV_Grub), and, although docs can be at times ... challenging ... it works. In production. Under heavy load. As do others, I follow progress in Xen channels/mailing lists/etc. I find *many* HowTo questions that arise there would be readily handled by simply using current (or OBS repos') *Suse/Xen. That said, there seems to be a tangible ... lack of interest in, if not disdain for ... Suse+Xen. Yet the flailings about of how to get things done in Centos, Debian, etc ... continue. That's certainly fine. I'm curious: (1) Why does this tension exist? Or, in your opinion(s), does it? (2) What can be done differently in *Suse to further adoption for Virtualization? The latter question, in particular, is a purely mercenary concern for me -- the bigger/stronger the community of users, the better off my deployments are/will be. Not trolling, just interested. -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-virtual+help(a)opensuse.org

6 7

[opensuse-virtual] Question about KVM
by Sascha 'saigkill' Manns 29 Jun '10

29 Jun '10

Hello Mates, today i've tried to make a new virtual Machine with KVM in YaST. But sadly i'm getting the Error: "internal error: No <source> 'bridge' attribute specified with <interface type=''bridge'/> . Maybe anyone knows what is to do? P.S: I've a Screenshot under http://saschamanns.de/kvm.png -- Sincerely yours Sascha Manns open-slx GmbH openSUSE Community & Support Agent openSUSE Marketing Team Blog: http://saigkill.wordpress.com Web: http://www.open-slx.de (openSUSE Box Support German) Web: http://www.open-slx.com (openSUSE Box Support English)

3 2

Re: [opensuse-virtual] Question about KVM
by Sascha 'saigkill' Manns 26 Jun '10

26 Jun '10

Hello Chuck, hello List, i've found the Hint. We have in our Wiki a excellent Article http://en.opensuse.org/KVM. That Article explains, how to fix my issue. Thanks for helping :-) -- Sincerely yours Sascha Manns open-slx GmbH openSUSE Community & Support Agent openSUSE Marketing Team Blog: http://saigkill.wordpress.com Web: http://www.open-slx.de (openSUSE Box Support German) Web: http://www.open-slx.com (openSUSE Box Support English)

2 1

[opensuse-virtual] reproducible panic @ 'new' 2.6.34-1-xen domU boot on pvgrub host
by 0bo0 23 Jun '10

23 Jun '10

with the migration of Kernel:/HEAD repos to 2.6.35x branch, i'm testing a dropback of DomU boot from 2.6.34-49.1-xen @ .../Kernel:/HEAD/openSUSE_11.2 to the 'new' repo @ .../Kernel:/openSUSE-11.3/openSUSE_11.2, w/ 2.6.31-1-xen. atm, (1) boot on an OpenSuse 11.2 Dom0 host (atm, still 2.6.34-49.1-xen) with either 2.6.34-49.1-xen or 2.6.31-1-xen DomU seems OK. (2) boot on a PV-GRUB host (@ Linode), which had been working fine w/ DomU earlier 2.6.34-X-xen, X ~< 35 (? iirc?) was, previously, OK. (3) boot on a PV-GRUB host (@ Linode), with either 2.6.34-49.1-xen or 2.6.31-1-xen, however, now Panics. here's the logview for DomU v=2.6.34.1-xen on PV-GRUB host: [ 0.000000] Reserving virtual address space above 0xf5800000 [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Linux version 2.6.34-1-xen (geeko@buildhost) (gcc version 4.4.1 [gcc-4_4-branch revision 150839] (SUSE Linux) ) #1 SMP 2010-06-21 21:12:08 +0200 [ 0.000000] Xen-provided physical RAM map: [ 0.000000] Xen: 0000000000000000 - 0000000030800000 (usable) [ 0.000000] NX (Execute Disable) protection: active [ 0.000000] last_pfn = 0x30800 max_arch_pfn = 0x10000000 [ 0.000000] init_memory_mapping: 0000000000000000-000000002cffe000 [ 0.000000] RAMDISK: 00717000 - 011f7000 [ 0.000000] ACPI in unprivileged domain disabled [ 0.000000] 56MB HIGHMEM available. [ 0.000000] 719MB LOWMEM available. [ 0.000000] mapped low ram: 0 - 2cffe000 [ 0.000000] low ram: 0 - 2cffe000 [ 0.000000] Zone PFN ranges: [ 0.000000] DMA 0x00000000 -> 0x00001000 [ 0.000000] Normal 0x00001000 -> 0x0002cffe [ 0.000000] HighMem 0x0002cffe -> 0x00030800 [ 0.000000] Movable zone start PFN for each node [ 0.000000] early_node_map[2] active PFN ranges [ 0.000000] 0: 0x00000000 -> 0x00030000 [ 0.000000] 0: 0x00030800 -> 0x00030800 [ 0.000000] setup_percpu: NR_CPUS:32 nr_cpumask_bits:32 nr_cpu_ids:4 nr_node_ids:1 [ 0.000000] PERCPU: Embedded 10 pages/cpu @c11fb000 s19732 r0 d21228 u65536 [ 0.000000] pcpu-alloc: s19732 r0 d21228 u65536 alloc=16*4096 [ 0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [ 0.000000] Swapping MFNs for PFN 643 and 11fc (MFN 90f252 and 8f2e7a) [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 195055 [ 0.000000] Kernel command line: root=/dev/xvdc resume=/dev/xvdb xencons=hvc0 kbdtype=us text nofb selinux=0 apparmor=0 edd=off splash=silent noshell showopts [ 0.000000] bootsplash: silent mode. [ 0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes) [ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) [ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) [ 0.000000] Enabling fast FPU save and restore... done. [ 0.000000] Enabling unmasked SIMD FPU exception support... done. [ 0.000000] Initializing CPU#0 [ 0.000000] Software IO TLB disabled [ 0.000000] Subtract (33 early reservations) [ 0.000000] #1 [0000002000 - 00006f6ac4] TEXT DATA BSS [ 0.000000] #2 [0000717000 - 00011f7000] Xen provided [ 0.000000] #3 [00012c6000 - 00012c7000] INITMAP [ 0.000000] #4 [00012c7000 - 0001426000] PGTABLE [ 0.000000] #5 [0001426000 - 0001427000] BOOTMEM [ 0.000000] #6 [0001427000 - 0001a37000] BOOTMEM [ 0.000000] #7 [0001a37000 - 0001a37004] BOOTMEM [ 0.000000] #8 [0001a37040 - 0001a37100] BOOTMEM [ 0.000000] #9 [0001a37100 - 0001a37144] BOOTMEM [ 0.000000] #10 [0001a37180 - 0001a3a180] BOOTMEM [ 0.000000] #11 [0001a3a180 - 0001a3a188] BOOTMEM [ 0.000000] #12 [0001a3a1c0 - 0001a3a4c0] BOOTMEM [ 0.000000] #13 [0001a3b000 - 0001afd000] BOOTMEM [ 0.000000] #14 [00012b7000 - 00012c6000] Xen provided [ 0.000000] #15 [00011f7000 - 00011f7008] BOOTMEM [ 0.000000] #16 [00011f7040 - 00011f7044] BOOTMEM [ 0.000000] #17 [00011f8000 - 00011f9000] BOOTMEM [ 0.000000] #18 [00011f7080 - 00011f70fe] BOOTMEM [ 0.000000] #19 [00011f7100 - 00011f717e] BOOTMEM [ 0.000000] #20 [00011fb000 - 0001205000] BOOTMEM [ 0.000000] #21 [000120b000 - 0001215000] BOOTMEM [ 0.000000] #22 [000121b000 - 0001225000] BOOTMEM [ 0.000000] #23 [000122b000 - 0001235000] BOOTMEM [ 0.000000] #24 [00011f7180 - 00011f7184] BOOTMEM [ 0.000000] #25 [00011f71c0 - 00011f71c4] BOOTMEM [ 0.000000] #26 [00011f7200 - 00011f7210] BOOTMEM [ 0.000000] #27 [00011f7240 - 00011f7250] BOOTMEM [ 0.000000] #28 [00011f7280 - 00011f7300] BOOTMEM [ 0.000000] #29 [00011f7300 - 00011f732c] BOOTMEM [ 0.000000] #30 [0001205000 - 0001209000] BOOTMEM [ 0.000000] #31 [0001235000 - 00012b5000] BOOTMEM [ 0.000000] #32 [0001afd000 - 0001b3d000] BOOTMEM [ 0.000000] Initializing HighMem for node 0 (0002cffe:00030800) [ 0.000000] Memory: 758748k/794624k available (3696k kernel code, 27684k reserved, 2395k data, 324k init, 49160k highmem) [ 0.000000] virtual kernel memory layout: [ 0.000000] fixmap : 0xf5476000 - 0xf57ff000 (3620 kB) [ 0.000000] pkmap : 0xf5000000 - 0xf5200000 (2048 kB) [ 0.000000] vmalloc : 0xed7fe000 - 0xf4ffe000 ( 120 MB) [ 0.000000] lowmem : 0xc0000000 - 0xecffe000 ( 719 MB) [ 0.000000] .init : 0xc05f6000 - 0xc0647000 ( 324 kB) [ 0.000000] .data : 0xc039e341 - 0xc05f50c8 (2395 kB) [ 0.000000] .text : 0xc0002000 - 0xc039e341 (3696 kB) [ 0.000000] Checking if this processor honours the WP bit even in supervisor mode...Ok. [ 0.000000] Hierarchical RCU implementation. [ 0.000000] NR_IRQS:2624 nr_irqs:624 [ 0.000000] Xen reported: 2266.746 MHz processor. [ 0.000000] Console: colour dummy device 80x25 [ 0.000000] console [tty0] enabled [ 0.000000] console [hvc0] enabled [ 0.080004] Calibrating delay using timer specific routine.. 4542.82 BogoMIPS (lpj=9085640) [ 0.080055] Security Framework initialized [ 0.080066] AppArmor: AppArmor disabled by boot time parameter [ 0.080066] [ 0.080082] Mount-cache hash table entries: 512 [ 0.080166] Initializing cgroup subsys ns [ 0.080176] Initializing cgroup subsys cpuacct [ 0.080191] Initializing cgroup subsys memory [ 0.080199] Initializing cgroup subsys devices [ 0.080203] Initializing cgroup subsys freezer [ 0.080206] Initializing cgroup subsys net_cls [ 0.080210] Initializing cgroup subsys blkio [ 0.080255] Checking 'hlt' instruction... OK. [ 0.080848] SMP alternatives: switching to UP code [ 0.105224] Unpacking initramfs... [ 0.105273] ------------[ cut here ]------------ [ 0.105278] kernel BUG at /usr/src/packages/BUILD/kernel-xen-2.6.34/linux-2.6.34/arch/x86/mm/highmem_32-xen.c:45! [ 0.105284] invalid opcode: 0000 [#1] SMP [ 0.105289] last sysfs file: [ 0.105292] Modules linked in: [ 0.105296] [ 0.105299] Pid: 0, comm: swapper Not tainted 2.6.34-1-xen #1 / [ 0.105303] EIP: e019:[<c00202ab>] EFLAGS: 00010282 CPU: 0 [ 0.105311] EIP is at kmap_atomic_prot+0x16b/0x190 [ 0.105314] EAX: c1a1f020 EBX: 80000000 ECX: c14257b0 EDX: c3c1b06b [ 0.105318] ESI: 80000000 EDI: 00000063 EBP: 00000000 ESP: c05bfee8 [ 0.105322] DS: e021 ES: e021 FS: 00d8 GS: 0000 SS: e021 [ 0.105326] Process swapper (pid: 0, ti=c05be000 task=c05c0d00 task.ti=c05be000) [ 0.105330] Stack: [ 0.105333] 00000002 f57ff000 c14257b0 00000003 80000000 00000000 00000000 00000000 [ 0.105342] <0> c00202ec 00000063 80000000 00001000 c0004620 00000000 00000000 00001000 [ 0.105353] <0> 00000001 c05bff64 c05bff60 00000000 00000000 ec4013b8 ec8327c0 00000001 [ 0.105365] Call Trace: [ 0.105373] [<c00202ec>] kmap_atomic+0x1c/0x30 [ 0.105379] [<c0004620>] initramfs_file_write+0xe0/0x190 [ 0.105385] [<c0004714>] initramfs_write+0x44/0x80 [ 0.105391] [<c05f8813>] do_copy+0x24/0xb8 [ 0.105397] [<c05f7e32>] unpack_to_rootfs+0x1c2/0x36f [ 0.105402] [<c05f8754>] populate_rootfs+0x52/0xed [ 0.105407] [<c05f6bdb>] start_kernel+0x2d4/0x2e8 [ 0.105411] Code: 04 75 30 8b 5c 24 04 89 f9 89 ea 31 f6 e8 2e 2f fe ff 85 c0 74 09 8b 54 24 08 89 6a 04 89 3a 8b 44 24 04 83 c4 10 5b 5e 5f 5d c3 <0f> 0b eb fe 0f 0b eb fe 8b 44 24 04 89 fa 89 e9 c7 04 24 00 00 [ 0.105482] EIP: [<c00202ab>] kmap_atomic_prot+0x16b/0x190 SS:ESP e021:c05bfee8 [ 0.105503] ---[ end trace 4eaa2a86a8e2da22 ]--- [ 0.105507] Kernel panic - not syncing: Attempted to kill the idle task! [ 0.105513] Pid: 0, comm: swapper Tainted: G D 2.6.34-1-xen #1 [ 0.105516] Call Trace: [ 0.105522] [<c0009d2b>] try_stack_unwind+0x14b/0x170 [ 0.105528] [<c000815f>] dump_trace+0x3f/0xf0 [ 0.105533] [<c000993b>] show_trace_log_lvl+0x4b/0x60 [ 0.105538] [<c0009968>] show_trace+0x18/0x20 [ 0.105544] [<c039486c>] dump_stack+0x6d/0x72 [ 0.105548] [<c03948b2>] panic+0x41/0xd9 [ 0.105553] [<c003d7ad>] do_exit+0x31d/0x340 [ 0.105561] [<c0398763>] oops_end+0xb3/0x110 [ 0.105566] [<c00074c7>] do_invalid_op+0x97/0xb0 [ 0.105571] [<c0397d58>] error_code+0x30/0x38 [ 0.105577] [<c00202ab>] kmap_atomic_prot+0x16b/0x190 [ 0.105587] [<c00202ec>] kmap_atomic+0x1c/0x30 [ 0.105599] [<c0004620>] initramfs_file_write+0xe0/0x190 [ 0.105604] [<c0004714>] initramfs_write+0x44/0x80 [ 0.105609] [<c05f8813>] do_copy+0x24/0xb8 [ 0.105614] [<c05f7e32>] unpack_to_rootfs+0x1c2/0x36f [ 0.105619] [<c05f8754>] populate_rootfs+0x52/0xed [ 0.105624] [<c05f6bdb>] start_kernel+0x2d4/0x2e8 dropping back to a DomU -xen kernel from .../Kernel:/openSUSE-11.2/openSUSE_11.2, v = 2.6.31.13-18.1, again boots fine on the PV-GRUB host -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-virtual+help(a)opensuse.org

2 1

[opensuse-virtual] blktap2 on 11.2
by mailing lists 21 Jun '10

21 Jun '10

Hello, I'm a bit confused about using blktap2 on OpenSuSE 11.2. blktap2 is available in xen 4.0 but it seems that it was backported to xen 3.4. However I am unable to make it work. Does anyone have any experience with blktap2?? # xm create -c director01 Using config file "/etc/xen/vm/director01". Error: Device 51952 (tap) could not be connected. Setting up the backend failed. See the log files in /var/log/xen/ for details [2010-06-21 11:03:00 3331] DEBUG (XendDomainInfo:2324) XendDomainInfo.constructDomain [2010-06-21 11:03:00 3331] DEBUG (balloon:185) Balloon: 1053548 KiB free; need 4096; done. [2010-06-21 11:03:00 3331] DEBUG (XendDomain:453) Adding Domain: 9 [2010-06-21 11:03:00 3331] DEBUG (XendDomainInfo:2525) XendDomainInfo.initDomain: 9 256 [2010-06-21 11:03:00 3331] INFO (XendDomainInfo:2948) Mounting vhd:/mnt/director01 on /dev/xvdp. [2010-06-21 11:03:00 3331] DEBUG (DevController:95) DevController: writing {'backend-id': '0', 'virtual-device': '51952', 'device-type': 'disk', 'state': '1', 'backend': '/local/domain/0/backend/tap/0/51952'} to /local/domain/0/device/vbd/51952. [2010-06-21 11:03:00 3331] DEBUG (DevController:97) DevController: writing {'domain': 'Domain-0', 'frontend': '/local/domain/0/device/vbd/51952', 'uuid': '31e7d05f-eb49-9e8a-715b-e7f4568e8bfe', 'bootable': '0', 'dev': '/dev/xvdp', 'state': '1', 'params': 'tapdisk:vhd:/mnt/director01', 'mode': 'w', 'online': '1', 'frontend-id': '0', 'type': 'tap'} to /local/domain/0/backend/tap/0/51952. [2010-06-21 11:03:00 3331] DEBUG (DevController:144) Waiting for 51952. [2010-06-21 11:03:00 3331] DEBUG (DevController:654) hotplugStatusCallback /local/domain/0/backend/tap/0/51952/hotplug-status. [2010-06-21 11:03:00 3331] DEBUG (DevController:668) hotplugStatusCallback 2. [2010-06-21 11:03:00 3331] ERROR (XendDomainInfo:3662) Device 51952 (tap) could not be connected. Setting up the backend failed. See the log files in /var/log/xen/ for details. # xm list director01 -l [.....] (device (tap (bootable 1) (uname tap:tapdisk:vhd:/mnt/director01) (mode w) (dev xvda) (uuid f362c77e-e721-c6ee-4f88-f323678fa9e9) ) ) # cat /etc/xen/vm/director01 name="director01" uuid="5a54cbb9-8fd5-5d5a-fa89-31303086bfc1" memory=1024 maxmem=1024 vcpus=1 on_poweroff="destroy" on_reboot="restart" on_crash="destroy" localtime=0 keymap="es" builder="linux" bootloader="/usr/lib/xen/boot/domUloader.py" bootargs="--entry=xvda2:/boot/vmlinuz-xen,/boot/initrd-xen" extra=" " disk=[ 'tap:tapdisk:vhd:/mnt/director01,xvda,w' ] vif=[ 'vifname=vif1.1, mac=00:16:3e:45:e7:11, bridge=xenbr0' ] -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-virtual+help(a)opensuse.org

2 1

[opensuse-virtual] status of Xen4 for OS 11.2
by 0bo0 16 Jun '10

16 Jun '10

has any decision been taken about the fate of this repo: https://build.opensuse.org/package/live_build_log?arch=x86_64&package=xen&p… last exchanges here suggested that it might be best to disable it. atm, it's still not building. chance of a timely fix? or should we plan to abandon its use? thanks. -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-virtual+help(a)opensuse.org

2 2

[opensuse-virtual] Problem Passing SR-IOV Virtual Function to a PV domU
by Chris Reeves 14 Jun '10

14 Jun '10

Hi, I have an SR-IOV network card (Intel 82576), and I'm trying to pass a virtual function through to a PV domU. I can attach the function without error (xm pci-attach <domU> 0000:09:10.0). However, in the domU, all I see is the following: [ 1.001725] pcifront pci-0: Installing PCI frontend [ 1.001853] pcifront pci-0: Creating PCI Frontend Bus 0000:00 [ 1.051244] pci-stub: invalid id string "" or [ 342.002602] pcifront pci-0: Rescanning PCI Frontend Bus 0000:00 if I attach a second device. The device never shows up in an lspci, and loading the driver manually never picks it up (probably to be expected if it doesn't show up on PCI). Does anyone have any experience with this? Is it possible? I know that I have passthrough set up correctly because I can successfully pass through a non SR-IOV nic. I'm running kernel 2.6.31.12-0.1-xen for my dom0 and domU. I've tried 2.6.34-45-xen as a domU kernel, with the same results. I wasn't able to successfully run 2.6.34 as my dom0 kernel (could be an issue on my end). I'm running xen 4.0. Thanks in advance for any insight anyone has. Chris -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-virtual+help(a)opensuse.org

1 0

Re: [opensuse-virtual] help launching a Centos 5.5 Xen PV guest on an OpenSuse 11.2 Dom0 host ?
by Jan Beulich 07 Jun '10

07 Jun '10

>>> 0bo0 <0.bugs.only.0(a)gmail.com> 06/04/10 6:50 PM >>> >On Fri, Jun 4, 2010 at 12:10 AM, Jan Beulich wrote: >> This certainly isn't with the 11.2 kernel, is it? On the HEAD (Factory) >> one we did such a change, but there still is no need to load the driver >> through /etc/sysconfig/kernel (as that would result in also attempting >> to load the [non-existing] driver on native boots). Instead, the proper >> place is in xend's startup script, as was also done by us in preparation >> to that kernel side change. > >heh. i'm getting lost as to what's been (not) done where ... I wuld think that we can expect you to know what you have installed on your system. >*I* currently have > >uname -a >Linux server 2.6.34-42-xen #1 SMP 2010-06-01 15:17:00 +0200 x86_64 >x86_64 x86_64 GNU/Linux As expected, this is not the 11.2 kernel. >... >where, > >grep -i base Kernel_112.repo XEN4.repo >Kernel_112.repo:baseurl=http://download.opensuse.org/repositories/Kernel:/H… >XEN4.repo:baseurl=http://download.opensuse.org/repositories/Virtualization/… Nor would this (assuming XEN4 implies Xen 4.0.0) be the 11.2 hypervisor/tools. I don't think we guarantee consistency at any point in time between Xen and kernel; I would expect them to be consistent at Milestone points (and then only in Factory or whatever tree upcoming OpenSuSE releases get built from). I have no clue if/when/how synchronization happens between Factory and other repos like the one you use. Jan -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-virtual+help(a)opensuse.org

3 2

Re: [opensuse-virtual] help launching a Centos 5.5 Xen PV guest on an OpenSuse 11.2 Dom0 host ?
by Jan Beulich 04 Jun '10

04 Jun '10

>>> 0bo0 <0.bugs.only.0(a)gmail.com> 06/03/10 7:23 AM >>> >p.s. Unrelated, but worth mentioning -- at some point in the last few >weeks' (maybe longer) of system/kernel/xen upgrades, service "xend" >stopped launching on boot. a bit of digging about led me to an >apparently NEW requirement, the need for: > >lsmod | grep evt >evtchn 38288 4 > >for whatever reason, not getting auto-added to initrd @ kernel upgrades/ > >adding that module to /etc/sysconfig/kernel cures the problem. This certainly isn't with the 11.2 kernel, is it? On the HEAD (Factory) one we did such a change, but there still is no need to load the driver through /etc/sysconfig/kernel (as that would result in also attempting to load the [non-existing] driver on native boots). Instead, the proper place is in xend's startup script, as was also done by us in preparation to that kernel side change. Jan -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-virtual+help(a)opensuse.org

3 3

[opensuse-virtual] help launching a Centos 5.5 Xen PV guest on an OpenSuse 11.2 Dom0 host ?
by 0bo0 03 Jun '10

03 Jun '10

i've Opensuse 11.2 Xen Dom0, lsb_release -dr Description: openSUSE 11.2 (x86_64) Release: 11.2 uname -a Linux server 2.6.34-42-xen #1 SMP 2010-06-01 15:17:00 +0200 x86_64 x86_64 x86_64 GNU/Linux rpm -qa | grep -i xen xen-libs-4.0.0_21087_01-38.1.x86_64 kernel-xen-devel-2.6.34-42.1.x86_64 xen-tools-4.0.0_21087_01-38.1.x86_64 kernel-xen-2.6.34-42.1.x86_64 xen-4.0.0_21087_01-38.1.x86_64 I build & run numerous OpenSuse DomUs -- no issues. I need to netinstall a Centos 5.5 PV'd DomU Guest on this host. Using the procedure & config below, it starts to boot -- then hangs, with not much useful debugging info ... at least, not to my eye, where/how I'm looking. If someone could once-over the following, and make any suggestions/hints as to what's up, it'd be appreciated! Here's the current step-by-step: lvcreate -n vm_boot -L 160M /dev/VG0 lvcreate -n vm_swap -L 512M /dev/VG0 lvcreate -n vm_root -L 8G /dev/VG0 mkdir -p /home/xen/centos55/xenboot/ setenv DL "http://mirrors.kernel.org/centos/5.5" cd /home/xen/centos55 wget $DL/isos/x86_64/CentOS-5.5-x86_64-netinstall.iso cd ./xenboot/ wget $DL/os/x86_64/images/xen/initrd.img wget $DL/os/x86_64/images/xen/vmlinuz vi /home/xen/centos_install.cfg --------------------------------------------- name = 'centos' builder = 'linux' kernel = "/home/xen/centos55/xenboot/vmlinuz" ramdisk = "/home/xen/centos55/xenboot/initrd.img" disk = [ 'phy:/dev/VG0/vm_boot,xvda,w', 'phy:/dev/VG0/vm_swap,xvdb,w', 'phy:/dev/VG0/vm_root,xvdc,w', 'file:/home/xen/centos55/CentOS-5.5-x86_64-netinstall.iso,hdc:cdrom,r', ] boot = 'd' vif = [ 'mac=00:16:3E:01:06:00, bridge=brA, vifname=vif.A' ] vfb = [ 'type=vnc, vncdisplay=106, vnclisten=127.0.0.1' ] extra = 'textmode=1 xencons=xvc0 elevator=noop lang=en_US.UTF-8 keyboard=us timezone=America/Los_Angeles bootproto=static ip=192.168.1.155 gateway=192.168.1.1 nameserver=192.168.1.1 method=http://mirrors.kernel.org/centos/5.5/os/x86_64' maxmem = 1024 memory = 1024 vcpus = 4 cpu_cap = 100 cpu_weight = 256 localtime = 0 netif = 'yes' on_shutdown = 'destroy' on_reboot = 'restart' on_crash = 'destroy' --------------------------------------------- @ xm create -c /home/xen/centos_install.cfg starts ok, but then hangs, --------------------------------------------- Using config file "/home/xen/centos_install.cfg". Started domain centos (id=5) Bootdata ok (command line is textmode=1 xencons=xvc0 elevator=noop lang=en_US.UTF-8 keyboard=us timezone=America/Los_Angeles bootproto=static ip=192.168.1.155 gateway=192.168.1.1 nameserver=192.168.1.1 method=http://mirrors.kernel.org/centos/5.5/os/x86_64) Linux version 2.6.18-194.el5xen (mockbuild(a)builder10.centos.org) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-48)) #1 SMP Fri Apr 2 15:34:40 EDT 2010 ... XENBUS: Device with no driver: device/vif/1 XENBUS: Device with no driver: device/vif/2 XENBUS: Device with no driver: device/vif/3 XENBUS: Device with no driver: device/console/0 Initalizing network drop monitor service Write protecting the kernel read-only data: 483k ( ... HANGS HERE ...) --------------------------------------------- and, tail -f /var/logl/xen/* --------------------------------------------- ... [2010-06-02 19:46:17 4832] DEBUG (DevController:653) hotplugStatusCallback /local/domain/0/backend/vbd/5/51744/hotplug-status. [2010-06-02 19:46:17 4832] DEBUG (DevController:667) hotplugStatusCallback 1. [2010-06-02 19:46:17 4832] DEBUG (DevController:144) Waiting for 5632. [2010-06-02 19:46:17 4832] DEBUG (DevController:653) hotplugStatusCallback /local/domain/0/backend/vbd/5/5632/hotplug-status. [2010-06-02 19:46:17 4832] DEBUG (DevController:667) hotplugStatusCallback 1. [2010-06-02 19:46:18 4832] DEBUG (DevController:139) Waiting for devices irq. [2010-06-02 19:46:18 4832] DEBUG (DevController:139) Waiting for devices vfb. [2010-06-02 19:46:18 4832] DEBUG (DevController:139) Waiting for devices pci. [2010-06-02 19:46:18 4832] DEBUG (DevController:139) Waiting for devices vusb. [2010-06-02 19:46:18 4832] DEBUG (DevController:139) Waiting for devices vtpm. [2010-06-02 19:46:18 4832] INFO (XendDomain:1207) Domain centos (5) unpaused. ( ... HANGS HERE ...) --------------------------------------------- -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-virtual+help(a)opensuse.org

2 5