xen March 2006

xen@lists.fedoraproject.org

35 participants
62 discussions

initscripts, xen and bonding
by Axel Thimm 04 Mar '07

04 Mar '07

Hi, I'm having a hard time getting bonding to work on FC5t3. It looks like the bond0 interface bond0 is renamed to pbond0 by xen [*] and the enslaving does not work anymore then. It works if I log on the terminal and ifenslave the devices to pbond0 instead of bond0 after the boot process has finished. But I want this to be handled automatically during reboots, so I tried assigning the bonding slaves to pbond0 as a master in the ifcfg-eth{0,1} scripts, but that doesn't work. What is causing the bond0 rename and should this renaming be considered by initscript? Is this a user error or should I file this against bugzilla? xen or initscripts? Thanks! [*] The only reference I found was a Japanese site and google's translation of it. http://translate.google.com/translate?hl=en&sl=ja&u=http://hoop.euqset.org/… -- Axel.Thimm at ATrpms.net

3 8

Simple testing results for Xen and VMX on FC5-test2.
by You, Yongkang 12 Jan '07

12 Jan '07

Hi all, I have done a simple checking for Xen and VMX on FC5-test2. Basically, I can create VMX on FC5-test2 IA32. But FC5-test2 IA32e (x86-64) doesn't provide Xen and Xen0 kernel, so didn't do Xen and VMX testing for it. Beside of testing Xen and VMX, I also found some issues about installation, which I have updated the bug #179078 as a NB. The following is the testing results only for Xen and VMX. ========================= 1. *** IA32E hasn't RPMS about Xen hypervisor and Xen0/XenU kernels. __FAIL__ 2. *** In order to boot up IA32 Xen0, I have to add pci=noacpi as the boot parameters of Xen0 kernel, or system will hang when initial PCI. I don't know if it is only related to my Machine. __FAIL__ 3. After install IA32 Xen RPMs, I can see /boot/grub/grub.conf has been changed with Xen kernels. __PASS__ 4. *** /usr/lib/xen/boot/vmxloader isn't in the RPM package, so VMX Guest couldn't be created. I suspected build system hasn't bcc, it is from DEV86 package. __FAIL__ 5. After copy a useable vmxloader to the destination, IA32 VMX Guest can be created successfully! __PASS__ 6. VMX has good network connection and Xwindows started. __PASS__ 7. XenU can be created and works well. __PASS__ 8. Couldn't get Xen Changeset by "xm info" or "xm dmesg". 9. The new kernel names of Xen/Xen0/XenU seemed a little confused. E.g. the Xen0 name is like vmlinuz-2.6.15-1.29_FC5hypervisor. I thought hypervisor is for Xen.gz. Xen0 is the Service OS. ========================== Any comments please let me know. But I will have 8 days holiday from tomorrow, so emails reply might be slow and occasional. [FYI] We are planning to do more testing for FC5-test3. Best Regards, Yongkang (Kangkang) 永康

4 4

Problems with Xen + FC5 + Thinkpad
by Brad Smith 04 Apr '06

04 Apr '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello all, I recently upgraded from FC4 to FC5 on my Thinkpad T30 laptop and am looking forward to playing with Xen. However, I've hit a few stumbling blocks along the way. Following the instructions at http://www.fedoraproject.org/wiki/FedoraXenQuickstartFC5 I installed the Xen0 kernel and booted my system with it. However it hangs, seemingly forever, at the "Starting xend" stage. The OS seems ok as keypresses are still printed to the screen, but because the daemon never completes its startup process the boot sequence never finishes. Upon rebooting I noticed an error that gets printed while the kernel is loading, which says that it could not bind IRQ2 to guest because it is in use by cascade. This happens consistently, so I wonder if it's a hardware problem? I booted the system into single user mode and chkconfig'd xend off, booted normally and attempted to start the daemon post-boot. It printed a message about starting the Bridged Firewall, which I had not seen during bootup, but still seemed to hang indefinitely. Oh, and SELinux is loaded but not enforcing. Should that be sufficient? Does anyone have suggestions for how I might further troubleshoot this? Thanks, - --Brad -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFEKrcaDvp49DvQ8kcRAv8yAJ0cHBQsP3KwEGb+x9GZTXga6e24/ACeIQG6 MCywwa529LxnXECf2YLo4SI= =Z3wj -----END PGP SIGNATURE-----

4 4

"xm create" error: /usr/lib64/python2.4/site-packages/xen/xm/opts.py:452: DeprecationWarning: Non-ASCII character '\xeb'
by Aleksander Adamowski 03 Apr '06

03 Apr '06

Introduction: when one installs a Xen guest using xenguest-install.py, at the end of the installation the guest is shutdown and xenguest-install.py prints out instructions to start it up with "xm create -c GUEST_NAME". The instructions are wrong - the parameter to "-c" switch is a file name, so a full path is needed. So the instructions should read "xm create -c /etc/xen/GUEST_NAME" instead. If one proceeds according to the instructions, and the current working directory isn't /etc/xen, an unhelpful error will occur: --- SNIP ---- [root@domzero2 xen]# xm create -c svn Using config file "svn". /usr/lib64/python2.4/site-packages/xen/xm/opts.py:452: DeprecationWarning: Non-ASCII character '\xeb' in file svn on line 1, but no encoding declared; see http://www.python.org/peps/pep-0263.html for details execfile(defconfig, globs, locs) Error: invalid syntax (svn, line 1) [root@domzero2 xen]# hexdump -C /etc/xen/svn 00000000 23 20 41 75 74 6f 6d 61 74 69 63 61 6c 6c 79 20 |# Automatically | 00000010 67 65 6e 65 72 61 74 65 64 20 78 65 6e 20 63 6f |generated xen co| 00000020 6e 66 69 67 20 66 69 6c 65 0a 6e 61 6d 65 20 3d |nfig file.name =| 00000030 20 22 73 76 6e 22 0a 6d 65 6d 6f 72 79 20 3d 20 | "svn".memory = | 00000040 22 35 31 32 22 0a 64 69 73 6b 20 3d 20 5b 20 27 |"512".disk = [ '| 00000050 66 69 6c 65 3a 2f 76 61 72 2f 78 65 6e 2f 73 76 |file:/var/xen/sv| 00000060 6e 2c 78 76 64 61 2c 77 27 20 5d 0a 76 69 66 20 |n,xvda,w' ].vif | 00000070 3d 20 5b 20 27 6d 61 63 3d 30 30 3a 31 36 3a 33 |= [ 'mac=00:16:3| 00000080 65 3a 33 62 3a 38 65 3a 34 63 27 20 5d 0a 62 6f |e:3b:8e:4c' ].bo| 00000090 6f 74 6c 6f 61 64 65 72 3d 22 2f 75 73 72 2f 62 |otloader="/usr/b| 000000a0 69 6e 2f 70 79 67 72 75 62 22 0a 0a 6f 6e 5f 72 |in/pygrub"..on_r| 000000b0 65 62 6f 6f 74 20 20 20 3d 20 27 72 65 73 74 61 |eboot = 'resta| 000000c0 72 74 27 0a 6f 6e 5f 63 72 61 73 68 20 20 20 20 |rt'.on_crash | 000000d0 3d 20 27 72 65 73 74 61 72 74 27 0a |= 'restart'.| 000000dc --- SNIP ---- Of course, there's no "EB" byte in this guest config file, as can be seen on the hexdump! When starting the guest using a full path all is OK: --- SNIP ---- [root@domzero2 xen]# xm create -c /etc/xen/svn pyGRUB version 0.3 ┌──────────────────────── │ Fedora Core (2.6.15-1.2054_FC5xenU) │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ └───────────────────────── Use the - and . keys to select which entry is highlighted. Press enter to boot the selected OS. 'e' to edit the commands before booting, 'a' to modify the kernel arguments before booting, or 'c' for a command line. Will boot selected entry in 1 seconds Going to boot Fedora Core (2.6.15-1.2054_FC5xenU) kernel: /boot/vmlinuz-2.6.15-1.2054_FC5xenU initrd: /boot/initrd-2.6.15-1.2054_FC5xenU.img Started domain svn Bootdata ok (command line is ro root=LABEL=/) Linux version 2.6.15-1.2054_FC5xenU (bhcompile(a)hs20-bc1-7.build.redhat.com) (gcc version 4.1.0 20060304 (Red Hat 4.1.0-3)) #1 SMP Tue Mar 14 16:18:03 EST 2006 Built 1 zonelists Kernel command line: ro root=LABEL=/ Initializing CPU#0 PID hash table entries: 4096 (order: 12, 131072 bytes) Xen reported: 1804.087 MHz processor. Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes) Inode-cache hash table entries: 65536 (order: 7, 524288 bytes) Software IO TLB disabled Memory: 507260k/532480k available (1891k kernel code, 24560k reserved, 720k data, 116k init) Calibrating delay using timer specific routine.. 4512.41 BogoMIPS (lpj=9024823) Security Framework v1.0.0 initialized SELinux: Initializing. SELinux: Starting in permissive mode selinux_register_security: Registering secondary module capability Capability LSM initialized as secondary Mount-cache hash table entries: 256 CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 1024K (64 bytes/line) Brought up 1 CPUs 0 checking if image is initramfs... it is Freeing initrd memory: 1890k freed DMI not present or invalid. Grant table initialized ..... --- SNIP ---- -- Best Regards, Aleksander Adamowski GG#: 274614 ICQ UIN: 19780575 http://olo.ab.altkom.pl

2 1

2.6.15-1.2054_FC5xen0 - no network for guest domains
by Aleksander Adamowski 03 Apr '06

03 Apr '06

Hi! I'm using xenguest-install.py to install a guest domain on x86_64. The anaconda installer start up fine, but when I configure the network for the guest domain (be it DHCP or static IP), after trying to contact installation FTP server, I discover that the guest domain has no network connectivity at all - it cannot resolve the FTP server's hostname, or connect to it directly by its IP address; I cannot ping from other hosts or from dom0 to the guest domain. The physical network controller is a Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet using the tg3 driver. The virtual network devices are created by Xen on domain 0: # ifconfig eth0 Link encap:Ethernet HWaddr 00:15:60:0B:ED:88 inet addr:192.168.254.208 Bcast:192.168.254.255 Mask:255.255.255.0 inet6 addr: fe80::215:60ff:fe0b:ed88/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:475078 errors:0 dropped:0 overruns:0 frame:0 TX packets:601247 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:99094177 (94.5 MiB) TX bytes:322269097 (307.3 MiB) Interrupt:17 eth0:0 Link encap:Ethernet HWaddr 00:15:60:0B:ED:88 inet addr:192.168.254.4 Bcast:192.168.254.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:17 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:80137 errors:0 dropped:0 overruns:0 frame:0 TX packets:80137 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:288852189 (275.4 MiB) TX bytes:288852189 (275.4 MiB) vif1.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:99 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:6 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:4158 (4.0 KiB) TX bytes:0 (0.0 b) xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:99 errors:0 dropped:0 overruns:0 frame:0 TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2772 (2.7 KiB) TX bytes:468 (468.0 b) I suspect that this may have something to do with x86_64 architecture and the tg3 driver. Any ideas? -- Best Regards, Aleksander Adamowski GG#: 274614 ICQ UIN: 19780575 http://olo.ab.altkom.pl

2 4

Disk problems on FC5
by Brad Smith 01 Apr '06

01 Apr '06

Hi folks, I set up Xen on a freshly-installed FC5 system, configured the guest using xenguest-install.py and then began an installation via VNC. However, as soon as I got to the partitioning phase I received an error that the partition table for my disk couldn't be read. I opted to ignore this as I've seen that error even on real systems and have proceeded without incident. However, the installer continued to produce errors about not being able to find the disk, being unable to read the partition table, etc and eventually just died. Looking at the disk file I told Xen to create (I gave it 4096 as the size) it appears to have a size of 0. Is that the way it should be? Any further advice for troubleshooting? Thanks, --Brad

3 2

Problems with e1000 drivers with kernel 2.6.15...
by Thomas Uhl 31 Mar '06

31 Mar '06

Hi! I am testing xen on a preproduction Intel box. The standard kernel of FC5 (2.6.15-1.2054) does not detect the embedded e1000 NICs in my setup. So I tried kernel 2.6.16-1.2102 from rawhide. It worked. When will we see a "xenified" 2.6.16 kernel in rawhide? Yours Tom Here the dmesg output with kernel 2.6.16... Intel(R) PRO/1000 Network Driver - version 7.0.33-k2-NAPI Copyright (c) 1999-2005 Intel Corporation. ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 18 (level, low) -> IRQ 19 PCI: Setting latency timer of device 0000:05:00.0 to 64 e1000: 0000:05:00.0: e1000_probe: (PCI Express:2.5Gb/s:Width x4)

2 1

RE: [Fedora-xen] Problem booting jailtime images
by Murat Işık 31 Mar '06

31 Mar '06

Hello, thanks for the reply. actually here is what I have/did: [root@muratisik ~]# cd /xen/fedora/ [root@muratisik fedora]# ls fedora.fc4.img fedora.fc4.xen.cfg fedora.swap [root@muratisik fedora]# cat fedora.fc4.xen.cfg kernel = "/boot/vmlinuz-2.6.16-1.2080_FC5xen0" memory = 128 name = "fedora.fc4" nics = 1 dhcp = "dhcp" disk = ['file:/xen/fedora/fedora.fc4.img,sda1,w', 'file:/xen/fedora/fedora.swap,sda2,w'] root = "/dev/sda1 ro" [root@muratisik fedora]# mount -o loop fedora.fc4.img /mnt/ [root@muratisik fedora]# cat /mnt/etc/fstab # This file is edited by fstab-sync - see 'man fstab-sync' for details /dev/sda1 / ext3 defaults 1 1 /dev/sda2 none swap sw 0 0 none /dev/pts devpts gid=5,mode=620 0 0 none /dev/shm tmpfs defaults 0 0 none /proc proc defaults 0 0 none /sys sysfs defaults 0 0 [root@muratisik fedora]# umount /mnt/ [root@muratisik fedora]# xm create fedora.fc4.xen.cfg -c and the error appears: ... md: ... autorun DONE. VFS: Cannot open root device "sda1" or unknown-block(0,0) Please append a correct "root=" boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [<c011c42c>] panic+0x3c/0x190 [<c03c6a5c>] mount_block_root+0x19c/0x1aa [<c03c6ab3>] mount_root+0x49/0x4e [<c03c6b78>] prepare_namespace+0xc0/0xf1 [<c0102267>] init+0x23e/0x2fe [<c0102029>] init+0x0/0x2fe [<c01029ad>] kernel_thread_helper+0x5/0xb Then I changed both image's fstab to hda1 and hda2 , also editted cfg to match hdas. and I get the same error. any ideas? is there any more information (log, config, debug vs.) I can supply? have a nice day. >> >>Hello, >> >>After installing a fresh fc5, I followed >>fedoraproject.org/wiki/FedoraXenQuickstartFC5 up until >> xenguest-install.py >>part. After that point for a quick try I downloaded both fc4 and debian >>prebuilt images from jailtime.org . However both images, as I boot them >>with xm create -c {related one}.cfg , crash with this error: >> >>VFS: Cannot open root device "sda1" or unknown-block(0,0) >>Please append a correct "root=" boot option >>Kernel panic - not syncing: VFS: Unable to mount root fs on >>unknown-block(0,0) >> >>I did extensive googling and mounted the images, cheking their fstab and >>so on. Everything looks fine. But the problem is unresolved. > > Did you use the '/dev/sda1' as the root boot option in xenU config? > And the xenU fstab also used sda1? > Change they to /dev/hda1 and have a try. > >> >>Does anybody have any experiences with jailtime images? any suggestions? >>BTW my host fc5 has LVM partitioning. Very unlikely but can this have an >>effect? >> >>Have a nice day. >> >> >>-- >>Murat Isik >>www.bilgiguvenlik.com >> >>-- > > > Best Regards, > Yongkang (Kangkang) ÓÀ¿µ >

1 0

Problems to hide pci appliance
by Victor Mihalik 31 Mar '06

31 Mar '06

Hi People, I've problems when I want to use a pci device within a guest machine. I try modify grub.conf and put physdev_dom0_hide and pciback.hide in the line of kernel and module but it does not happen anything. Somebody knows the way to make this? Thanks a lot Victor :-)

1 0

RE: [Fedora-xen] Problem booting jailtime images
by You, Yongkang 30 Mar '06

30 Mar '06

>-----Original Message----- >From: fedora-xen-bounces(a)redhat.com >[mailto:fedora-xen-bounces@redhat.com] On Behalf Of Murat I??k >Sent: 2006年3月31日 6:23 >To: fedora-xen(a)redhat.com >Subject: [Fedora-xen] Problem booting jailtime images > >Hello, > >After installing a fresh fc5, I followed >fedoraproject.org/wiki/FedoraXenQuickstartFC5 up until xenguest-install.py >part. After that point for a quick try I downloaded both fc4 and debian >prebuilt images from jailtime.org . However both images, as I boot them >with xm create -c {related one}.cfg , crash with this error: > >VFS: Cannot open root device "sda1" or unknown-block(0,0) >Please append a correct "root=" boot option >Kernel panic - not syncing: VFS: Unable to mount root fs on >unknown-block(0,0) > >I did extensive googling and mounted the images, cheking their fstab and >so on. Everything looks fine. But the problem is unresolved. Did you use the '/dev/sda1' as the root boot option in xenU config? And the xenU fstab also used sda1? Change they to /dev/hda1 and have a try. > >Does anybody have any experiences with jailtime images? any suggestions? >BTW my host fc5 has LVM partitioning. Very unlikely but can this have an >effect? > >Have a nice day. > > >-- >Murat Isik >www.bilgiguvenlik.com > >-- Best Regards, Yongkang (Kangkang) 永康

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xen March 2006