xen April 2006

xen@lists.fedoraproject.org

73 participants
127 discussions

FC5 - serial console - no characters received by host?
by Tony Clark 20 Apr '06

20 Apr '06

Hi there, I've been working with the FC5 Xen stuff for the past few weeks after trawling many options for building a redundant server farm; It's a great build and congratulations to all who put this together. I have a little issue with my serial console which is putting hte brakes on deployment though: I want to use the serial console on com2 (the default on the Intel mainboard I use) to give me the grub console, Xen console and Linux consoles. I've had this working fine on previous releases from SuSE and others and on the current hardware. When happens at the moment is that the machine boots, gives me the grub menu, where I can choose my boot system (so it's hearing my keystrokes) but once it proceeds into the Xen and ultimately Linux, it doesn't want to hear keystrokes from me any more: I can't CTRL-A (x3) and get the Xen console, nor the linux console which is configured in /etc/inittab. I see the boot messages go past and get a login prompt, but no keystrokes get through or can control the machine. It's making it tricky to send the box to co-lo as I can't get serial control if I take down the network, or Hypervisor control to reboot Dom0. My rpms are: kernel-xen0-2.6.16-1.2080_FC5 xen-3.0.1-4 and my grub.conf is: default=0 timeout=5 #splashimage=(hd0,0)/grub/splash.xpm.gz #hiddenmenu # serial --unit=1 --speed=9600 --word=8 --parity=no --stop=1 terminal --timeout=10 serial console # title Fedora Core (2.6.16-1.2080_FC5xen0) root (hd0,0) kernel /xen.gz-2.6.16-1.2080_FC5 dom0_mem=384000 com2=9600,8n1 console=com2,vga sync_console module /vmlinuz-2.6.16-1.2080_FC5xen0 ro root=/dev/ VolGroup00/LogVol00 rhgb selinux=0 module /initrd-2.6.16-1.2080_FC5xen0.img I'd appreciate any guidance on silly things I may have done here; I'm banging my head on this one. Many thanks, Tony tony clark director - tony.clark(a)rsp.com.au --------------------------------------------------------------- rising sun pictures - www.rsp.com.au redefining visual effects delivery --------------------------------------------------------------- address level 1 / 133 gouger street adelaide south australia 5000 --------------------------------------------------------------- adelaide ph +61 8 8400 6400 fax +61 8 8400 6401 sydney ph +61 2 9338 6400 fax +61 2 9338 6401 --------------------------------------------------------------- rising sun research - http://research.rsp.com.au ---------------------------------------------------------------

2 2

RE: [Fedora-xen] FC5 - serial console - no characters received by host?
by You, Yongkang 20 Apr '06

20 Apr '06

Hi Tony, There is a bug about this issue. Please have a look at https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=180126 If want to use serial port input, I have to disable SMP. Following is a workable grub config to enable serial out input, but the kernel will be UP. I am not sure if there is any better solution. title Fedora Core 5 root (hd0,0) kernel /boot/xen.gz-xxx_FC5 dom0_mem=262144 com0=115200,8n1 apci=off module /boot/vmlinuz-xxx_FC5hypervisor ro root=/dev/sda1 console=ttyS0 console=tty0 pci=noapci module /boot/initrd-xxx_FC5hypervisor.img Best Regards, Yongkang (Kangkang) 永康 ________________________________ From: fedora-xen-bounces(a)redhat.com [mailto:fedora-xen-bounces@redhat.com] On Behalf Of Tony Clark Sent: 2006年4月20日 22:05 To: fedora-xen(a)redhat.com Subject: [Fedora-xen] FC5 - serial console - no characters received by host? Hi there, I've been working with the FC5 Xen stuff for the past few weeks after trawling many options for building a redundant server farm; It's a great build and congratulations to all who put this together. I have a little issue with my serial console which is putting hte brakes on deployment though: I want to use the serial console on com2 (the default on the Intel mainboard I use) to give me the grub console, Xen console and Linux consoles. I've had this working fine on previous releases from SuSE and others and on the current hardware. When happens at the moment is that the machine boots, gives me the grub menu, where I can choose my boot system (so it's hearing my keystrokes) but once it proceeds into the Xen and ultimately Linux, it doesn't want to hear keystrokes from me any more: I can't CTRL-A (x3) and get the Xen console, nor the linux console which is configured in /etc/inittab. I see the boot messages go past and get a login prompt, but no keystrokes get through or can control the machine. It's making it tricky to send the box to co-lo as I can't get serial control if I take down the network, or Hypervisor control to reboot Dom0. My rpms are: kernel-xen0-2.6.16-1.2080_FC5 xen-3.0.1-4 and my grub.conf is: default=0 timeout=5 #splashimage=(hd0,0)/grub/splash.xpm.gz #hiddenmenu # serial --unit=1 --speed=9600 --word=8 --parity=no --stop=1 terminal --timeout=10 serial console # title Fedora Core (2.6.16-1.2080_FC5xen0) root (hd0,0) kernel /xen.gz-2.6.16-1.2080_FC5 dom0_mem=384000 com2=9600,8n1 console=com2,vga sync_console module /vmlinuz-2.6.16-1.2080_FC5xen0 ro root=/dev/VolGroup00/LogVol00 rhgb selinux=0 module /initrd-2.6.16-1.2080_FC5xen0.img I'd appreciate any guidance on silly things I may have done here; I'm banging my head on this one. Many thanks, Tony tony clark director - tony.clark(a)rsp.com.au --------------------------------------------------------------- rising sun pictures - www.rsp.com.au redefining visual effects delivery --------------------------------------------------------------- address level 1 / 133 gouger street adelaide south australia 5000 --------------------------------------------------------------- adelaide ph +61 8 8400 6400 fax +61 8 8400 6401 sydney ph +61 2 9338 6400 fax +61 2 9338 6401 --------------------------------------------------------------- rising sun research - http://research.rsp.com.au ---------------------------------------------------------------

1 0

RE: [Fedora-xen] Unmodified 2003/2000/FC5 on XEN 3.0.2
by You, Yongkang 20 Apr '06

20 Apr '06

Hi Rafig, So you have tried Windows 2003 and 2000? And they all hang with the same phenomena? Did you try to get the serial output when VMX hang? The qemu-log seemed okay. Could you tell more information such as Xen0 memory size and the VMX config you used? These could help developers to shoot the bug. And you can also report bugs to Xen directly. :-) I didn’t try them before. But I am sure someone has successful experience of creating Windows XP VMX with Xen 3.0.2/ Best Regards, Yongkang (Kangkang) 永康 ________________________________ From: fedora-xen-bounces(a)redhat.com [mailto:fedora-xen-bounces@redhat.com] On Behalf Of Ahamed K, Rafiq (HP) Sent: 2006年4月20日 13:35 To: fedora-xen(a)redhat.com Subject: [Fedora-xen] Unmodified 2003/2000/FC5 on XEN 3.0.2 I can see that Windows Loads in VM and when I run in safe mode it reaches until loading multi(0)\disk(0)\rdisk(0)\partition(1)\Windows\system32\drivers\Mup.sys After this it hangs.Attached is the qemulog. Note : These VM's are running out of a complete disk (/dev/sdb), which has working installation of Windows on it! I am running FC5 along with Xen 3.0.2 (tried unstable too) on Intel XEON VT-x server! Any help would be great! Rafiq

1 0

RE: [Fedora-xen] Device 2049 (vbd) could not be connected.
by You, Yongkang 20 Apr '06

20 Apr '06

I am not sure if it is related with loop device is occupied. Could you try "losetup /dev/loop0" to see if loop0 isn't released. If not, release it manually by "losetup -d /dev/loop0". Or try to change the disk config file to: disk = [ 'phy:/dev/loop0,...' ] I don't know if this bug is fixed by latest xen. Best Regards, Yongkang (Kangkang) 永康 >-----Original Message----- >From: fedora-xen-bounces(a)redhat.com >[mailto:fedora-xen-bounces@redhat.com] On Behalf Of Gregor Pirnaver >Sent: 2006年4月19日 20:41 >To: fedora-xen(a)redhat.com >Subject: [Fedora-xen] Device 2049 (vbd) could not be connected. > >DomainU starts only the first time. After running "xm shutdown ..." I get this >error: > > ># xm create webserver >Using config file "webserveer". >Error: Device 2049 (vbd) could not be connected. Hotplug scripts not working. > > >How can I fix this? > >____________________ >http://www.email.si/ > > >-- >Fedora-xen mailing list >Fedora-xen(a)redhat.com >https://www.redhat.com/mailman/listinfo/fedora-xen

1 0

RE: [Fedora-xen] running 32-bit paravirtualized DomU under 64-bit Dom0
by Matthias Bayer 20 Apr '06

20 Apr '06

that's what i thought but i was not sure :-) ok, thanks for this info yonkang ! Matthias > -----Ursprüngliche Nachricht----- > Von: "You, Yongkang" <yongkang.you(a)intel.com> > Gesendet: 20.04.06 09:59:52 > An: <fedora-xen(a)redhat.com> > Betreff: RE: [Fedora-xen] running 32-bit paravirtualized DomU under 64-bit Dom0 > Hi Matthias, > > The first step your trying is okay: either IA32 or X86_64(EM64T) full-virtualization VMX can run in X86_64 Host. > > But IA32 paravirtulization XenU can only run in IA32 Xen0. :) > > Best Regards, > Yongkang (Kangkang) ÓÀ¿µ > > >-----Original Message----- > >From: fedora-xen-bounces(a)redhat.com > >[mailto:fedora-xen-bounces@redhat.com] On Behalf Of Matthias Bayer > >Sent: 2006Äê4ÔÂ19ÈÕ 23:07 > >To: fedora-xen(a)redhat.com > >Subject: [Fedora-xen] running 32-bit paravirtualized DomU under 64-bit Dom0 > > > >Hi, > > > >i am running a x86_64 FC5 system (with VT) with xen-3.0.1-4 and > >kernel-xen0-2.6.16-1.2080_FC5. > >i have several paravirtualized and fully virtualized images from another xen > >system which was 'normal' 32 bit installation (same version). > > > >running the fully virtualized DomU images created under 32 bit Dom0 works > >fine after changing device_model = '/usr/lib/xen/bin/qemu-dm' to > >'device_model = '/usr/lib64/xen/bin/qemu-dm'. > >now i want to start my formerly created paravirtualized DomU systems (here > >one FC5 system) under the new 64-bit system but i get the following error > >when starting: > > > >[root@tuxine xen]# xm create FC5_messer > >Using config file "FC5_messer". > >Going to boot Fedora Core (2.6.16-1.2080_FC5xenU) > > kernel: /vmlinuz-2.6.16-1.2080_FC5xenU > > initrd: /initrd-2.6.16-1.2080_FC5xenU.img > >Error: Error creating domain: (22, 'Invalid argument') > > > >attached are the xend.log and xend-debug.log files. > > > >hope somebody can give me a hint what's wrong. > > > >regards, > >Matthias > >______________________________________________________________ > >_ > >SMS schreiben mit WEB.DE FreeMail - einfach, schnell und > >kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192 _______________________________________________________________ SMS schreiben mit WEB.DE FreeMail - einfach, schnell und kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192

1 0

RE: [Fedora-xen] running 32-bit paravirtualized DomU under 64-bit Dom0
by You, Yongkang 20 Apr '06

20 Apr '06

Hi Matthias, The first step your trying is okay: either IA32 or X86_64(EM64T) full-virtualization VMX can run in X86_64 Host. But IA32 paravirtulization XenU can only run in IA32 Xen0. :) Best Regards, Yongkang (Kangkang) 永康 >-----Original Message----- >From: fedora-xen-bounces(a)redhat.com >[mailto:fedora-xen-bounces@redhat.com] On Behalf Of Matthias Bayer >Sent: 2006年4月19日 23:07 >To: fedora-xen(a)redhat.com >Subject: [Fedora-xen] running 32-bit paravirtualized DomU under 64-bit Dom0 > >Hi, > >i am running a x86_64 FC5 system (with VT) with xen-3.0.1-4 and >kernel-xen0-2.6.16-1.2080_FC5. >i have several paravirtualized and fully virtualized images from another xen >system which was 'normal' 32 bit installation (same version). > >running the fully virtualized DomU images created under 32 bit Dom0 works >fine after changing device_model = '/usr/lib/xen/bin/qemu-dm' to >'device_model = '/usr/lib64/xen/bin/qemu-dm'. >now i want to start my formerly created paravirtualized DomU systems (here >one FC5 system) under the new 64-bit system but i get the following error >when starting: > >[root@tuxine xen]# xm create FC5_messer >Using config file "FC5_messer". >Going to boot Fedora Core (2.6.16-1.2080_FC5xenU) > kernel: /vmlinuz-2.6.16-1.2080_FC5xenU > initrd: /initrd-2.6.16-1.2080_FC5xenU.img >Error: Error creating domain: (22, 'Invalid argument') > >attached are the xend.log and xend-debug.log files. > >hope somebody can give me a hint what's wrong. > >regards, >Matthias >______________________________________________________________ >_ >SMS schreiben mit WEB.DE FreeMail - einfach, schnell und >kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192

1 0

Unmodified 2003/2000/FC5 on XEN 3.0.2
by Ahamed K, Rafiq (HP) 20 Apr '06

20 Apr '06

I can see that Windows Loads in VM and when I run in safe mode it reaches until loading multi(0)\disk(0)\rdisk(0)\partition(1)\Windows\system32\drivers\Mup.sys After this it hangs.Attached is the qemulog. Note : These VM's are running out of a complete disk (/dev/sdb), which has working installation of Windows on it! I am running FC5 along with Xen 3.0.2 (tried unstable too) on Intel XEON VT-x server! Any help would be great! Rafiq

1 0

running 32-bit paravirtualized DomU under 64-bit Dom0
by Matthias Bayer 19 Apr '06

19 Apr '06

Hi, i am running a x86_64 FC5 system (with VT) with xen-3.0.1-4 and kernel-xen0-2.6.16-1.2080_FC5. i have several paravirtualized and fully virtualized images from another xen system which was 'normal' 32 bit installation (same version). running the fully virtualized DomU images created under 32 bit Dom0 works fine after changing device_model = '/usr/lib/xen/bin/qemu-dm' to 'device_model = '/usr/lib64/xen/bin/qemu-dm'. now i want to start my formerly created paravirtualized DomU systems (here one FC5 system) under the new 64-bit system but i get the following error when starting: [root@tuxine xen]# xm create FC5_messer Using config file "FC5_messer". Going to boot Fedora Core (2.6.16-1.2080_FC5xenU) kernel: /vmlinuz-2.6.16-1.2080_FC5xenU initrd: /initrd-2.6.16-1.2080_FC5xenU.img Error: Error creating domain: (22, 'Invalid argument') attached are the xend.log and xend-debug.log files. hope somebody can give me a hint what's wrong. regards, Matthias _______________________________________________________________ SMS schreiben mit WEB.DE FreeMail - einfach, schnell und kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192

1 0

RE: [Fedora-xen] Running FC4 on FC5
by Robert Mortimer 19 Apr '06

19 Apr '06

I have the boot image (FC4 domU) in /boot And the modules in the modules dir I also have FC4 domU installed on the FC4 Guest -----Original Message----- From: Philipp Jäggi [mailto:philipp.jaggi@snct.lu] Sent: 19 April 2006 11:19 To: Robert Mortimer Subject: RE: [Fedora-xen] Running FC4 on FC5 You've got the FC4 Xen kernel installed in your dom0? bye Philipp =============================================== Philipp Jäggi SNCT Sandweiler bp 23 L-5230 Sandweiler +352 35'72'14'342 mailto: philipp.jaeggi(a)snct.lu "Robert Mortimer" <rmortimer(a)bluechiptechnology.co.uk> 04/19/2006 11:48 AM To Philipp Jäggi <philipp.jaggi(a)snct.lu> cc Subject RE: [Fedora-xen] Running FC4 on FC5 Yes -----Original Message----- From: Philipp Jäggi [mailto:philipp.jaggi@snct.lu] Sent: 19 April 2006 10:43 To: Robert Mortimer Subject: RE: [Fedora-xen] Running FC4 on FC5 You disabled SELinux and rebooted the machine? bye Philipp =============================================== Philipp Jäggi SNCT Sandweiler bp 23 L-5230 Sandweiler +352 35'72'14'342 mailto: philipp.jaeggi(a)snct.lu "Robert Mortimer" <rmortimer(a)bluechiptechnology.co.uk> Sent by: fedora-xen-bounces(a)redhat.com 04/19/2006 11:06 AM To Philipp Jäggi <philipp.jaggi(a)snct.lu> cc fedora-xen-bounces(a)redhat.com, fedora-xen(a)redhat.com Subject RE: [Fedora-xen] Running FC4 on FC5 Dear Robert First of all, I've had the same questions and problems as you have now. This style of none documentation by the fedora team is just a shame for the whole open source community! Probably Jeremy Katz is too busy by meeting his new board members friends, so that he has no more time to write just a little documentation with explanations, not just a unusable mini mini howto. What the big problem is behind the FC5 and Xen implementation is, that the xen guys at fedora have no idea what SELinux is doing. So, finally they made an implementation of xen and SELinux that is not usable. If you don't want to spend two weeks configuring your SELinux, you have to decide, if you use in future SELinux or Xen (By the way, the same issues you have with httpd and SELinux). So my personal proposal is, that you just disable SELinux wherever you find it on your FC5 installation. After disabling SELinux (you have to reboot so that everything works fine, => Oh I like this old nice M$ Win95 style of system management) you can use your xen config as you posted in your mail. With the xenguest-install.py script you can't install FC4 or another distribution, because the FC5 guys made an adaptation of the anaconda system installer. By the way, this is a nice feature, because you can now kickstart your FC5 installation. If you want to install a new non FC5 guest, do it in the old style. Create your devices with LVM and perform a yum groupinstall with --installdir=yourdevice. The Point is I have done this I have FC4 images. I have copied the fc4 domU kernel and modules to the Dom0 and still I can not find a config that boots As you can see, Fedora Core 5 is a typical example for bad IT Management. They tried to do a lot of thing in a short time. So several teams worked on different things and now, nothing really fits together. The whole implementation of the SELinux is a disaster. So for professional use, you have to go back to Fedora Core 4. Also because the oracle stuff is not working with the new glibc (it's not possible to start the listener... :-(). I by myself have to use FC5, because I need to kickstart my xen installation and need apache 2.2. If you don't need those features, use CentOS or the original RHES. Hope I gave you the right hints. bye Philipp =============================================== Philipp Jäggi SNCT Sandweiler bp 23 L-5230 Sandweiler +352 35'72'14'342 "Robert Mortimer" <rmortimer(a)bluechiptechnology.co.uk> Sent by: fedora-xen-bounces(a)redhat.com 04/18/2006 04:22 PM To <fedora-xen(a)redhat.com> cc Subject [Fedora-xen] Running FC4 on FC5 I am attempting to run an FC4 image on an FC5 machine I have prepped the image as per the FC4 quick start my xen config is as follows kernel ="/boot/vmlinuz-2.6.13-1.1532_FC4xenU" memory = 100 name = "vm01" vcpus = 1 vif= ['mac=FE:FD:25:63:74:49'] disk = [ 'file:/root/VM/fedora.img,sda1,w' ] root = "/dev/sda1" extra = "ro selinux=0 3" All I get is # xm create vm01 Using config file "vm01". Error: Error creating domain: (22, 'Invalid argument') Has anyone got a simple 1 NIC guest config for FC4 on FC5 I see that the new FC5 uses An init image as part of the boot A python based boot loader and a python based install script Is there any way to hack this lot to do an install like the FC5/FC5 one? How are the init images built? Will the new installer do other guest OS's in the future? Robert -- Fedora-xen mailing list Fedora-xen(a)redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen -- Fedora-xen mailing list Fedora-xen(a)redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen

1 0

Device 2049 (vbd) could not be connected.
by Gregor Pirnaver 19 Apr '06

19 Apr '06

DomainU starts only the first time. After running "xm shutdown ..." I get this error: # xm create webserver Using config file "webserveer". Error: Device 2049 (vbd) could not be connected. Hotplug scripts not working. How can I fix this? ____________________ http://www.email.si/

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xen April 2006