xen May 2006

xen@lists.fedoraproject.org

69 participants
92 discussions

Re: [Fedora-xen] Fwd: No networking in DomU - Ubuntu
by Eric Jacobshagen 05 May '06

05 May '06

This may not help you, since I'm using FC5... but... I had to add the line: alias eth0 xennet to the modprobe.conf file in DomU to make eth0 available.

2 1

Fwd: No networking in DomU - Ubuntu
by Tom Bishop 04 May '06

04 May '06

Well where do I start...I have a domU (ubuntu) booting and appears well but I don't have an eth0 listed at all, dom) looks good. Dom0: eth0 Link encap:Ethernet HWaddr 00:06:5B:15:C5:0B inet addr: 10.99.99.5 Bcast:10.99.99.7 Mask:255.255.255.248 inet6 addr: fe80::206:5bff:fe15:c50b/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:3014 errors:0 dropped:0 overruns:0 frame:0 TX packets:2744 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2290550 (2.1 MiB) TX bytes:393169 ( 383.9 KiB) 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:2375 errors:0 dropped:0 overruns:0 frame:0 TX packets:2375 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2457201 (2.3 MiB) TX bytes:2457201 ( 2.3 MiB) peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1 RX packets:3011 errors:0 dropped:0 overruns:0 frame:0 TX packets:2773 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:2291324 (2.1 MiB) TX bytes:400425 (391.0 KiB) Interrupt:5 Base address:0x6800 vif0.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:2744 errors:0 dropped:0 overruns:0 frame:0 TX packets:3016 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:393169 (383.9 KiB) TX bytes:2290718 (2.1 MiB) vif9.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:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:13 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) 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:401 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:45491 (44.4 KiB) TX bytes:468 ( 468.0 b) ############DomU######################### bishop@ubuntu:~$ ifconfig lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:19 errors:0 dropped:0 overruns:0 frame:0 TX packets:19 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1119 (1.0 KiB) TX bytes:1119 ( 1.0 KiB) I've tried everything, static, DHCP, etc...but it's like it doesn't even see etho, even if I try ifconfig etho up, gives me an error. Any help appreciated. thanks.

1 0

Installing Xen Host
by James Gilliam 04 May '06

04 May '06

Hello All I've looked high and low for a set of instructions for installing a xen host from a Live CD distrobution. To make a long and complicated story short.. I have FC5 install in w/the xen kernel and what to install BackTrack 3.0 as the virtual system. Has anybody successfully accomplished this. Thanks James _________________________________________________________________ Express yourself instantly with MSN Messenger! Download today - it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/

1 0

Re: [Fedora-xen] Best Practice for backing up running Virtual Machines
by Christian Reiter 03 May '06

03 May '06

Hello Kwan! Kwan Lowe schrieb: > With LVMs you can do snapshot backups pretty easily. If you have databases running > you should shut them down first, or at least use a method that retains the database > consistency. Even a snapshot won't capture changes unless they're written to disk. > I'm surprised that you didn't get any filesystem errors after copying the > file-backed domU.... > > I think i will use a combination of traditional backup within my domU for the absolutely important files, e.g. /etc, databases and other data. In Addition i will take an LVM Snapshot or something similar. I've read (xensource mailinglists) that LVM Snapshots aren't ready for production use at this time. Mit freundlichen Grüßen, /// Kind Regards, Christian Reiter -- Christian Reiter ||| c.reiter(a)gmx.net

1 0

Re: [Fedora-xen] Need help for serial console..
by Matthias Bayer 03 May '06

03 May '06

hi, my grub file lokks like this and works perfect with ttywatch on the other side: title Fedora Core (2.6.16-1.2096_FC5xen0) root (hd0,1) kernel /xen.gz-2.6.16-1.2096_FC5 module /vmlinuz-2.6.16-1.2096_FC5xen0 ro root=LABEL=/ rhgb quiet console=ttyS0 console=tty pnpacpi=off module /initrd-2.6.16-1.2096_FC5xen0.img hope that helps, Matthias > -----Ursprüngliche Nachricht----- > Von: <thomas.vonsteiger(a)bluewin.ch> > Gesendet: 03.05.06 09:12:05 > An: Rafiq (HP)'" <rafiq.ahamed(a)hp.com> > CC: fedora-xen(a)redhat.com > Betreff: AW: [Fedora-xen] Need help for serial console.. > Hello Rafiq, > > Yes i try with "console=ttyS0 console=tty0" and "console=ttyS0 console=tty". > No way to get a char in the remote logfile from the xen server ? > Xen Server it's FC5 with 1 serial adapter and remote Node is FC4 with 2 > serial adapter and ttywatch. > > Current I have this grub config: > > title Fedora Core (2.6.16-1.2096_FC5xen0) > root (hd0,0) > kernel /xen.gz-2.6.16-1.2096_FC5 dom0_mem=512000 com1=38400,8n1 > sync_console > module /vmlinuz-2.6.16-1.2096_FC5xen0 ro root=/dev/fcvg/slash rhgb > quiet console=tty0 console=ttyS0 pnpacpi=off > module /initrd-2.6.16-1.2096_FC5xen0.img > > regards, > thomas > > > > > -----Ursprüngliche Nachricht----- > Von: Ahamed K, Rafiq (HP) [mailto:rafiq.ahamed@hp.com] > Gesendet: Dienstag, 2. Mai 2006 23:07 > An: thomas.vonsteiger(a)bluewin.ch > Betreff: RE: [Fedora-xen] Need help for serial console.. > > Did u try with console=ttyS0 console=tty0 . Xen manual says this syntax! > > Rafiq > > -----Original Message----- > From: fedora-xen-bounces(a)redhat.com > [mailto:fedora-xen-bounces@redhat.com] On Behalf Of > thomas.vonsteiger(a)bluewin.ch > Sent: Monday, May 01, 2006 2:06 PM > To: fedora-xen(a)redhat.com > Subject: [Fedora-xen] Need help for serial console.. > > Hello, > > I try to setup a serial console to a remote node with a null modem > cable. > Becose there is no char in the logfile on remotehost ? > > On remote Node I have install ttywatch. ttywatch is running as daemon > with > this option from /etc/ttywatch.conf: > > --name xen0 --port /dev/ttyS0 --bps 38400 --ipport 3001 > --name xen1 --port /dev/ttyS1 --bps 38400 --ipport 3002 > > I can telnet to port 3001 and 3002. > > On the Xen Node I have setup this grub.conf: > > title Fedora Core (2.6.16-1.2096_FC5xen0) > root (hd0,0) > kernel /xen.gz-2.6.16-1.2096_FC5 dom0_mem=512000 com1=38400,8n1 > sync_console > module /vmlinuz-2.6.16-1.2096_FC5xen0 ro root=/dev/fcvg/slash > vga=773 rhgb quiet console=ttyS0 console=tty pnpacpi=off > module /initrd-2.6.16-1.2096_FC5xen0.img > > > what's wrong ? > > regards, > Thomas > > -- > Fedora-xen mailing list > Fedora-xen(a)redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > > > -- > No virus found in this incoming message. > Checked by AVG Free Edition. > Version: 7.1.385 / Virus Database: 268.5.1/328 - Release Date: 01.05.2006 > > > -- > Fedora-xen mailing list > Fedora-xen(a)redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen _______________________________________________________________ SMS schreiben mit WEB.DE FreeMail - einfach, schnell und kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192

2 1

AW: [Fedora-xen] Need help for serial console..
by Thomas von Steiger 03 May '06

03 May '06

Hello Rafiq, Yes i try with "console=ttyS0 console=tty0" and "console=ttyS0 console=tty". No way to get a char in the remote logfile from the xen server ? Xen Server it's FC5 with 1 serial adapter and remote Node is FC4 with 2 serial adapter and ttywatch. Current I have this grub config: title Fedora Core (2.6.16-1.2096_FC5xen0) root (hd0,0) kernel /xen.gz-2.6.16-1.2096_FC5 dom0_mem=512000 com1=38400,8n1 sync_console module /vmlinuz-2.6.16-1.2096_FC5xen0 ro root=/dev/fcvg/slash rhgb quiet console=tty0 console=ttyS0 pnpacpi=off module /initrd-2.6.16-1.2096_FC5xen0.img regards, thomas -----Ursprüngliche Nachricht----- Von: Ahamed K, Rafiq (HP) [mailto:rafiq.ahamed@hp.com] Gesendet: Dienstag, 2. Mai 2006 23:07 An: thomas.vonsteiger(a)bluewin.ch Betreff: RE: [Fedora-xen] Need help for serial console.. Did u try with console=ttyS0 console=tty0 . Xen manual says this syntax! Rafiq -----Original Message----- From: fedora-xen-bounces(a)redhat.com [mailto:fedora-xen-bounces@redhat.com] On Behalf Of thomas.vonsteiger(a)bluewin.ch Sent: Monday, May 01, 2006 2:06 PM To: fedora-xen(a)redhat.com Subject: [Fedora-xen] Need help for serial console.. Hello, I try to setup a serial console to a remote node with a null modem cable. Becose there is no char in the logfile on remotehost ? On remote Node I have install ttywatch. ttywatch is running as daemon with this option from /etc/ttywatch.conf: --name xen0 --port /dev/ttyS0 --bps 38400 --ipport 3001 --name xen1 --port /dev/ttyS1 --bps 38400 --ipport 3002 I can telnet to port 3001 and 3002. On the Xen Node I have setup this grub.conf: title Fedora Core (2.6.16-1.2096_FC5xen0) root (hd0,0) kernel /xen.gz-2.6.16-1.2096_FC5 dom0_mem=512000 com1=38400,8n1 sync_console module /vmlinuz-2.6.16-1.2096_FC5xen0 ro root=/dev/fcvg/slash vga=773 rhgb quiet console=ttyS0 console=tty pnpacpi=off module /initrd-2.6.16-1.2096_FC5xen0.img what's wrong ? regards, Thomas -- Fedora-xen mailing list Fedora-xen(a)redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.385 / Virus Database: 268.5.1/328 - Release Date: 01.05.2006

1 0

Fedora 5 xen dom0 , trying to boot ubuntu 5.10 domU
by Tom Bishop 02 May '06

02 May '06

I'm starting to go nuts I have tried this several ways and can't get my domainU to boot up, I am using Fedora 5 as dom0 and trying to boot up ubuntu 5.10. I installed ubuntu to a seperate harddrive then mounted the harddrive and did a cp -ax to a new file for my domU filesystem edited the fstab. My fedora dom0 is using lvm and I am not in the ubuntu installation, here are my output of my domain file and error......, any help would be appreciated. My goasl is to load mutiple distros to play with which I think will be neat. THANKS. Domain:::: # -*- mode: python; -*- #============================= ============================== ================= # Python configuration setup for 'xm create'. # This script sets the parameters used when a domain is created using 'xm create'. # You use a separate script for each domain you want to create, or # you can set the parameters for the domain on the xm command line. #============================================================================ #---------------------------------------------------------------------------- # Kernel image file. kernel = "/boot/vmlinuz-2.6.16-1.2096_FC5xen0" # Optional ramdisk. #ramdisk = "/boot/initrd- 2.6.15-1.2054_FC5.img" # The domain build function. Default is 'linux'. #builder='linux' # Initial memory allocation (in megabytes) for the new domain. memory = 128 # A name for your domain. All domains must have different names. name = "Ubuntu1" # List of which CPUS this domain is allowed to use, default Xen picks #cpus = "" # leave to Xen to pick #cpus = "0" # all vcpus run on CPU0 #cpus = "0-3,5,^1" # run on cpus 0,2,3,5 # Number of Virtual CPUS to use, default is 1 #vcpus = 1 #---------------------------------------------------------------------------- # Define network interfaces. # By default, no network interfaces are configured. You may have one created # with sensible defaults using an empty vif clause: # # vif = [ '' ] # # or optionally override backend, bridge, ip, mac, script, type, or vifname: # vif = [ 'mac=00:16:3e:00:00:11, bridge=xenbr0' ] # # or more than one interface may be configured: # # vif = [ '', 'bridge=xenbr1' ] #vif = [ '' ] #---------------------------------------------------------------------------- # Define the disk devices you want the domain to have access to, and # what you want them accessible as. # Each disk entry is of the form phy:UNAME,DEV,MODE # where UNAME is the device, DEV is the device name the domain will see, # and MODE is r for read-only, w for read-write. disk = ['file:/xen-home/ubuntu/ubuntu.img,sda1,w', 'file:/xen-home/ubuntu/swap.img,sda5,w'] #---------------------------------------------------------------------------- # Define to which TPM instance the user domain should communicate. # The vtpm entry is of the form 'instance=INSTANCE,backend=DOM' # where INSTANCE indicates the instance number of the TPM the VM # should be talking to and DOM provides the domain where the backend # is located. # Note that no two virtual machines should try to connect to the same # TPM instance. The handling of all TPM instances does require # some management effort in so far that VM configration files (and thus # a VM) should be associated with a TPM instance throughout the lifetime # of the VM / VM configuration file. The instance number must be # greater or equal to 1. #vtpm = [ 'instance=1,backend=0' ] #---------------------------------------------------------------------------- # Set the kernel command line for the new domain. # You only need to define the IP parameters and hostname if the domain's # IP config doesn't, e.g. in ifcfg-eth0 or via DHCP. # You can use 'extra' to set the runlevel and custom environment # variables used by custom rc scripts (e.g. VMID=, usr= ). # Set if you want dhcp to allocate the IP address. dhcp="dhcp" # Set netmask. #netmask= # Set default gateway. #gateway= # Set the hostname. #hostname= "vm%d" % vmid # Set root device. root = '/dev/sda1 ro' # Root device for nfs. #root = "/dev/nfs" # The nfs server. #nfs_server = ' 169.254.1.0 ' # Root directory on the nfs server. #nfs_root = '/full/path/to/root/directory' # Sets runlevel 4. extra = "4" #---------------------------------------------------------------------------- # Configure the behaviour when a domain exits. There are three 'reasons' # for a domain to stop: poweroff, reboot, and crash. For each of these you # may specify: # # "destroy", meaning that the domain is cleaned up as normal; # "restart", meaning that a new domain is started in place of the old # one; # "preserve", meaning that no clean-up is done until the domain is # manually destroyed (using xm destroy, for example); or # "rename-restart", meaning that the old domain is not cleaned up, but is # renamed and a new domain started in its place. # # The default is # # on_poweroff = 'destroy' # on_reboot = 'restart' # on_crash = 'restart' # # For backwards compatibility we also support the deprecated option restart # # restart = 'onreboot' means on_poweroff = 'destroy' # on_reboot = 'restart' # on_crash = 'destroy' # # restart = 'always' means on_poweroff = 'restart' # on_reboot = 'restart' # on_crash = 'restart' # # restart = 'never' means on_poweroff = 'destroy' # on_reboot = 'destroy' # on_crash = 'destroy' #on_poweroff = 'destroy' #on_reboot = 'restart' #on_crash = 'restart' #============================================================================ error:::: Initializing IPsec netlink socket NET: Registered protocol family 1 NET: Registered protocol family 17 Using IPI No-Shortcut mode md: Autodetecting RAID arrays. md: autorun ... 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) [<c011c50c>] 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

2 1

Error creating domain: (22, 'Invalid argument')
by Philip Rhoades 02 May '06

02 May '06

People, This is apparently a known (big?) problem?: [root@prix ~]# xm create -c fc5 Using config file "/etc/xen/fc5". Error: Error creating domain: (22, 'Invalid argument') ie trying to run a FC5 VM on FC5 . . Thanks, Phil. -- Philip Rhoades Pricom Pty Limited (ACN 003 252 275 ABN 91 003 252 275) GPO Box 3411 Sydney NSW 2001 Australia Mobile: +61:(0)411-185-652 Fax: +61:(0)2-8221-9599 E-mail: phil(a)pricom.com.au

2 1

RE: [Fedora-xen] Unmodified 2003/2000/FC5 on XEN 3.0.2
by Ahamed K, Rafiq (HP) 01 May '06

01 May '06

Hi Yong, Yes! I have tried windows 2003 and windows 2000 also and same problem prevails "on both". In the unsafe mode I can see that the drivers load on Windows 2003/2000 SDL VM console until they load mup.sys. I am not able to connect the serial output. I have followed almost all the techniques given on the net for serial communication. This is my grub info. root (hd0,0) kernel /boot/xen.gz dom0_mem=1024096 com1=115200,8n1 sync_console module /boot/vmlinuz-2.6-xen0 ro root=/dev/sda1 console=ttyS0 console=tty0 pnpacpi=off module /boot/initrd-2.6.16-xen0.img Just to clarify, the serial output is basically connecting the serial port of the XEN system to remote host and capturing the output right? (the way we debug load time drivers??) And my xm info is system : Linux host : hwxentop release : 2.6.16-xen0 version : #1 Tue May 2 03:16:06 MDT 2006 machine : i686 nr_cpus : 8 nr_nodes : 1 sockets_per_node : 2 cores_per_socket : 2 threads_per_core : 2 cpu_mhz : 2666 hw_caps : bfebfbff:20100000:00000000:00000180:000064bd:00000000:00000001 total_memory : 5119 free_memory : 3551 xen_major : 3 xen_minor : 0 xen_extra : -unstable xen_caps : xen-3.0-x86_32p hvm-3.0-x86_32 platform_params : virt_start=0xf5800000 xen_changeset : Wed Apr 26 20:01:37 2006 +0100 9747:4d667a139318 cc_compiler : gcc version 4.1.0 20060304 (Red Hat 4.1.0-3) cc_compile_by : root cc_compile_domain : localdomain cc_compile_date : Tue May 2 03:04:27 MDT 2006 Any help would be greatly appriciated! Thanks R ________________________________ From: You, Yongkang [mailto:yongkang.you@intel.com] Sent: Thursday, April 20, 2006 8:14 AM To: Ahamed K, Rafiq (HP); fedora-xen(a)redhat.com Subject: RE: [Fedora-xen] Unmodified 2003/2000/FC5 on XEN 3.0.2 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

Need help for serial console..
by Thomas von Steiger 01 May '06

01 May '06

Hello, I try to setup a serial console to a remote node with a null modem cable. Becose there is no char in the logfile on remotehost ? On remote Node I have install ttywatch. ttywatch is running as daemon with this option from /etc/ttywatch.conf: --name xen0 --port /dev/ttyS0 --bps 38400 --ipport 3001 --name xen1 --port /dev/ttyS1 --bps 38400 --ipport 3002 I can telnet to port 3001 and 3002. On the Xen Node I have setup this grub.conf: title Fedora Core (2.6.16-1.2096_FC5xen0) root (hd0,0) kernel /xen.gz-2.6.16-1.2096_FC5 dom0_mem=512000 com1=38400,8n1 sync_console module /vmlinuz-2.6.16-1.2096_FC5xen0 ro root=/dev/fcvg/slash vga=773 rhgb quiet console=ttyS0 console=tty pnpacpi=off module /initrd-2.6.16-1.2096_FC5xen0.img what's wrong ? regards, Thomas

1 0

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xen May 2006