Re: SIGSEGV on xenguest-install.py
by Gianni Bassini - Provincia di Cremona
solved
i copied the entire dvd on the host disks into the html dir and used the
host httpd
Bye
Gianni
--
--
-----------------------------------------------------
ing. Gianni Bassini (MNE Cefriel 2001)
System Administrator - Webmaster Provincia di Cremona
C.so Vittorio Emanuele II, 17 - 26100 Cremona (CR)
tel 0372-406246 - gianni.bassini(a)provincia.cremona.it
-----------------------------------------------------
18 years, 1 month
RE: [Fedora-xen] no eth0 device
by You, Yongkang
Hi Smith,
I guess your NIC driver isn’t built into default Xen0 kernel or as Xen0 modules. If so, you have to rebuild your Xen kernel alone. :-(
Best Regards,
Yongkang (Kangkang) 永康
________________________________
From: fedora-xen-bounces(a)redhat.com [mailto:fedora-xen-bounces@redhat.com] On Behalf Of Eric Smith
Sent: 2006年4月4日 12:20
To: fedora-xen(a)redhat.com
Subject: [Fedora-xen] no eth0 device
Hi,
With clean FC5 install followed by yum upgrade, and after installing xen, kernel-xen0, and kernel-xenU:
I boot into kernel-xen0 ok, xend starts, things like xm list work, but my eth0 device is not found at boot time. Booting into the non-xen kernel and it works as expected. eth0 is Broadcom 4400 10/100BaseT Ethernet.
Perhaps I'm missing the main xen documentation, but I didn't see anything about this in the quickstart guide.
Thank you for your help,
Eric
18 years, 1 month
Xend requires a net connection?
by Brad Smith
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello,
I have finally gotten xen working on my FC5 system (the subject of a couple of prior emails to this
list). The reason xend kept hanging seems to be that it requires a net connection to start. If eth0
is down or has had an IP assigned but isn't actually connected to the network, xend just hangs while
starting. But if I connect to the network first everything works. I didn't see anything about this
on the wiki, so can someone please provide more information? Is it just trying to resolve a name or
something? If so, I'd like to know so I can configure my systems such that running xen while offline
is an option. I tried stracing it but haven't been able to figure out what's going on.
Thanks,
- --Brad
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFEMZhFDvp49DvQ8kcRAvAcAJ0cCohkp2eoPlDHN5mvC0hrjAkrqwCeJk3V
m0VchQ8IIhQhF7X1UmPJmZ4=
=beyc
-----END PGP SIGNATURE-----
18 years, 1 month
pygrub failed
by Jun OKAJIMA
Hello, FC5 Xen folks.
When I tried to install Xen3.0 on FC5, it has failed in making a guest OS image.
It seems to be because that pygrub.py can not recognize my dom0 menu.lst correctly.
Or, maybe it is wrong that I used LVM, but this is default of current FC5 (Why?).
BTW, I am testing FC5 Xen dom0 on VMware 5.5.1, and it runs, although
many guys have reported that it has a lot of trouble.
For me, the problem is not VMware or dom0, but installer of domU.
Any help?
--- Okajima, Jun. Tokyo, Japan.
---------------------------
[root@localhost ~]# xm list
Name ID Mem(MiB) VCPUs State Time(s)
Domain-0 0 164 1 r----- 427.8
[root@localhost ~]# xenguest-install.py
What is the name of your virtual machine? FC5_1
How much RAM should be allocated (in megabytes)? 256
What would you like to use as the disk (path)? /XEN/FC5_1.img
What is the install location? http://ring.sakura.ad.jp/archives/linux/fedora/linux/core/5/i386/os/
Starting install...
Using config file "/etc/xen/FC5_1".
Error: Error creating domain: The privileged domain did not balloon!
If your install has exited, you can restart your guest by running
'xm create -c FC5_1'. Otherwise, you can reconnect to the console
by running 'xm console FC5_1'
[root@localhost ~]# xm create -c FC5_1
Using config file "/etc/xen/FC5_1".
Traceback (most recent call last):
File "/usr/bin/pygrub", line 256, in ?
cf = get_config(file, isconfig)
File "/usr/bin/pygrub", line 139, in get_config
raise RuntimeError, "Unable to read filesystem"
RuntimeError: Unable to read filesystem
Error: Boot loader didn't return any data!
[root@localhost ~]# cat /etc/xen/
FC5_1 scripts/ xmexample.vti
auto/ xend-config.sxp xmexample1
qemu-ifup xmexample.hvm xmexample2
[root@localhost ~]# cat /etc/xen/FC5_1
# Automatically generated xen config file
name = "FC5_1"
memory = "256"
disk = [ 'file:/XEN/FC5_1.img,xvda,w' ]
vif = [ 'mac=00:16:3e:60:8f:ea' ]
bootloader="/usr/bin/pygrub"
on_reboot = 'restart'
on_crash = 'restart'
[root@localhost ~]# cat /boot/grub/menu.lst
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00
# initrd /initrd-version.img
#boot=/dev/hda
default=2
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Fedora Core (2.6.16-1.2080_FC5xenU)
root (hd0,0)
kernel /vmlinuz-2.6.16-1.2080_FC5xenU ro root=/dev/VolGroup00/LogVol00 rhgb quiet
initrd /initrd-2.6.16-1.2080_FC5xenU.img
title Fedora Core (2.6.16-1.2080_FC5xen0)
root (hd0,0)
kernel /xen.gz-2.6.16-1.2080_FC5
module /vmlinuz-2.6.16-1.2080_FC5xen0 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
module /initrd-2.6.16-1.2080_FC5xen0.img
title Fedora Core (2.6.16-1.2080_FC5)
root (hd0,0)
kernel /vmlinuz-2.6.16-1.2080_FC5 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
initrd /initrd-2.6.16-1.2080_FC5.img
title Fedora Core (2.6.15-1.2054_FC5)
root (hd0,0)
kernel /vmlinuz-2.6.15-1.2054_FC5 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
initrd /initrd-2.6.15-1.2054_FC5.img
[root@localhost ~]# cat /proc/partitions
major minor #blocks name
3 0 8388608 hda
3 1 104391 hda1
3 2 8281507 hda2
253 0 7831552 dm-0
253 1 393216 dm-1
[root@localhost ~]# xm dmesg
__ __ _____ ___ ___
\ \/ /___ _ __ |___ / / _ \ / _ \
\ // _ \ '_ \ |_ \| | | | | | |
/ \ __/ | | | ___) | |_| | |_| |
/_/\_\___|_| |_| |____(_)___(_)___/
http://www.cl.cam.ac.uk/netos/xen
University of Cambridge Computer Laboratory
Xen version 3.0.0 (bhcompile(a)build.redhat.com) (gcc version 4.1.0 20060304 (Red Hat 4.1.0-3)) Tue
Mar 28 03:35:03 EST 2006
Latest ChangeSet: unavailable
(XEN) Physical RAM map:
(XEN) 0000000000000000 - 000000000009f800 (usable)
(XEN) 000000000009f800 - 00000000000a0000 (reserved)
(XEN) 00000000000dc000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 000000000bef0000 (usable)
(XEN) 000000000bef0000 - 000000000befc000 (ACPI data)
(XEN) 000000000befc000 - 000000000bf00000 (ACPI NVS)
(XEN) 000000000bf00000 - 000000000c000000 (usable)
(XEN) 00000000fec00000 - 00000000fec10000 (reserved)
(XEN) 00000000fee00000 - 00000000fee01000 (reserved)
(XEN) 00000000fffe0000 - 0000000100000000 (reserved)
(XEN) System RAM: 191MB (196156kB)
(XEN) Xen heap: 10MB (10344kB)
(XEN) Using scheduler: Simple EDF Scheduler (sedf)
(XEN) PAE disabled.
(XEN) found SMP MP-table at 000f6ce0
(XEN) DMI present.
(XEN) Using APIC driver default
(XEN) ACPI: RSDP (v000 PTLTD ) @ 0x000f6c70
(XEN) ACPI: RSDT (v001 PTLTD RSDT 0x06040000 LTP 0x00000000) @ 0x0bef7c02
(XEN) ACPI: FADT (v001 INTEL 440BX 0x06040000 PTL 0x000f4240) @ 0x0befbf14
(XEN) ACPI: MADT (v001 PTLTD APIC 0x06040000 LTP 0x00000000) @ 0x0befbf88
(XEN) ACPI: BOOT (v001 PTLTD $SBFTBL$ 0x06040000 LTP 0x00000001) @ 0x0befbfd8
(XEN) ACPI: DSDT (v001 PTLTD Custom 0x06040000 MSFT 0x0100000d) @ 0x00000000
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
(XEN) Processor #0 15:12 APIC version 17
(XEN) ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
(XEN) ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 1, version 17, address 0xfec00000, GSI 0-23
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge)
(XEN) ACPI: IRQ0 used by override.
(XEN) ACPI: IRQ2 used by override.
(XEN) Enabling APIC mode: Flat. Using 1 I/O APICs
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) Initializing CPU#0
(XEN) Detected 1599.572 MHz processor.
(XEN) CPU0: AMD Flush Filter disabled
(XEN) CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
(XEN) CPU: L2 Cache: 128K (64 bytes/line)
(XEN) Intel machine check architecture supported.
(XEN) Intel machine check reporting enabled on CPU#0.
(XEN) CPU0: AMD Sempron(tm) Processor 2600+ stepping 02
(XEN) Total of 1 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN) ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
(XEN) Platform timer is 1.193MHz PIT
(XEN) Brought up 1 CPUs
(XEN) Machine check exception polling timer started.
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Domain 0 kernel supports features = { 0000001f }.
(XEN) Domain 0 kernel requires features = { 00000000 }.
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Dom0 alloc.: 0a000000->0b000000 (37859 pages to be allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: c0100000->c0455b7c
(XEN) Init. ramdisk: c0456000->c07e2200
(XEN) Phys-Mach map: c07e3000->c080bf8c
(XEN) Start info: c080c000->c080d000
(XEN) Page tables: c080d000->c0811000
(XEN) Boot stack: c0811000->c0812000
(XEN) TOTAL: c0000000->c0c00000
(XEN) ENTRY ADDRESS: c0100000
(XEN) Dom0 has maximum 1 VCPUs
(XEN) Initrd len 0x38c200, start at 0xc0456000
(XEN) Scrubbing Free RAM: ..done.
(XEN) Xen trace buffers: disabled
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen).
[root@localhost ~]# cat /etc/redhat-release
Fedora Core release 5 (Bordeaux)
[root@localhost ~]#
18 years, 1 month
Fwd: Problems with e1000 drivers with kernel 2.6.15...
by Thomas Uhl
FYI:
same problem with kernel-xen0-2.6.16-1.2080_FC5. Perhaps I should
mention that I am booting the 64 bit version.
Yours
Tom
On 3/29/06, Thomas Uhl <thomas.uhl(a)gmail.com> wrote:
> 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)
>
18 years, 1 month
HD corruption??
by Kwan Lowe
Not sure at this moment if it's the XenU kernel or something with LVM...
Yesterday I installed the Xen0 kernel on my primary desktop to try to test xen
migration. I built out a couple 4G logical volumes and ran a couple kickstart
installations. At one point I tried to expand my /home filesystem (it's on a
/dev/rootvg/home_lv LVM partition). It failed, and then my /home seems to have been
remounted as read-only. Long story short, on a reboot the fsck.ext3 informs that the
filesystem is larger than the disk and fsck just gives hundreds of errors. I'm going
to blow away that LV and try to rebuild it tomorrow, but just curious if anyone else
has seen any disk corruption?
--
* The Digital Hermit http://www.digitalhermit.com
* Unix and Linux Solutions kwan(a)digitalhermit.com
18 years, 1 month
"xm create" error: /usr/lib64/python2.4/site-packages/xen/xm/opts.py:452: DeprecationWarning: Non-ASCII character '\xeb'
by Aleksander Adamowski
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
18 years, 1 month
2.6.15-1.2054_FC5xen0 - no network for guest domains
by Aleksander Adamowski
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
18 years, 1 month
Re: [Fedora-xen] SIGSEGV on xenguest-install.py
by Gianni Bassini - Provincia di Cremona
I have the same problem...
--
--
-----------------------------------------------------
ing. Gianni Bassini (MNE Cefriel 2001)
System Administrator - Webmaster Provincia di Cremona
C.so Vittorio Emanuele II, 17 - 26100 Cremona (CR)
tel 0372-406246 - gianni.bassini(a)provincia.cremona.it
-----------------------------------------------------
18 years, 1 month
RE: Problem booting jailtime images
by Murat Işık
hello,
"I didn't try to use a xen0 kernel to boot xenU before. I am not sure if
it is okay.
But I think you can try vmlinuz-2.6.16-1.2080_FC5xenU which comes from
another Xen
RPMs."
thanks very much for the xenU - xen0 tip. a simple typo error costs so
many problems...
however, now when I run
xm create fedora.fc4.xen.cfg -c
the virtual machines boot freezes at:
...
md: ... autorun DONE.
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 132k freed
my /var/log/xend.log is:
[2006-04-03 16:45:08 xend.XendDomainInfo] DEBUG (XendDomainInfo:177)
XendDomainInfo.create(['vm', ['name', 'fedora.fc4'], ['memory', '128'],
['vcpus', '1'], ['image', ['linux', ['kernel',
'/boot/vmlinuz-2.6.16-1.2080_FC5xenU'], ['ip', ':1.2.3.4::::eth0:dhcp'],
['root', '/dev/sda1 ro']]], ['device', ['vbd', ['uname',
'file:/xen/fedora/fedora.fc4.img'], ['dev', 'sda1'], ['mode', 'w']]],
['device', ['vbd', ['uname', 'file:/xen/fedora/fedora.swap'], ['dev',
'sda2'], ['mode', 'w']]], ['device', ['vif']]])
[2006-04-03 16:45:08 xend.XendDomainInfo] DEBUG (XendDomainInfo:283)
parseConfig: config is ['vm', ['name', 'fedora.fc4'], ['memory', '128'],
['vcpus', '1'], ['image', ['linux', ['kernel',
'/boot/vmlinuz-2.6.16-1.2080_FC5xenU'], ['ip', ':1.2.3.4::::eth0:dhcp'],
['root', '/dev/sda1 ro']]], ['device', ['vbd', ['uname',
'file:/xen/fedora/fedora.fc4.img'], ['dev', 'sda1'], ['mode', 'w']]],
['device', ['vbd', ['uname', 'file:/xen/fedora/fedora.swap'], ['dev',
'sda2'], ['mode', 'w']]], ['device', ['vif']]]
[2006-04-03 16:45:08 xend.XendDomainInfo] DEBUG (XendDomainInfo:379)
parseConfig: result is {'ssidref': None, 'uuid': None, 'on_crash': None,
'on_reboot': None, 'image': ['linux', ['kernel',
'/boot/vmlinuz-2.6.16-1.2080_FC5xenU'], ['ip', ':1.2.3.4::::eth0:dhcp'],
['root', '/dev/sda1 ro']], 'on_poweroff': None, 'cpus': None, 'name':
'fedora.fc4', 'backend': [], 'vcpus': 1, 'cpu_weight': None, 'vcpu_avail':
None, 'memory': 128, 'device': [('vbd', ['vbd', ['uname',
'file:/xen/fedora/fedora.fc4.img'], ['dev', 'sda1'], ['mode', 'w']]),
('vbd', ['vbd', ['uname', 'file:/xen/fedora/fedora.swap'], ['dev',
'sda2'], ['mode', 'w']]), ('vif', ['vif'])], 'bootloader': None, 'cpu':
None, 'maxmem': None}
[2006-04-03 16:45:08 xend.XendDomainInfo] DEBUG (XendDomainInfo:1142)
XendDomainInfo.construct: None 0
[2006-04-03 16:45:08 xend.XendDomainInfo] DEBUG (XendDomainInfo:1174)
XendDomainInfo.initDomain: 1 1.0
[2006-04-03 16:45:08 xend] DEBUG (balloon:88) Balloon: free 30; need 129.
[2006-04-03 16:45:08 xend] DEBUG (balloon:97) Balloon: setting dom0 target
to 364.
[2006-04-03 16:45:08 xend.XendDomainInfo] DEBUG (XendDomainInfo:923)
Setting memory target of domain Domain-0 (0) to 364 MiB.
[2006-04-03 16:45:09 xend] DEBUG (balloon:84) Balloon: free 129; need 129;
done.
[2006-04-03 16:45:09 xend] INFO (image:135) buildDomain os=linux dom=1
vcpus=1
[2006-04-03 16:45:09 xend] DEBUG (image:173) dom = 1
[2006-04-03 16:45:09 xend] DEBUG (image:174) image =
/boot/vmlinuz-2.6.16-1.2080_FC5xenU
[2006-04-03 16:45:09 xend] DEBUG (image:175) store_evtchn = 1
[2006-04-03 16:45:09 xend] DEBUG (image:176) console_evtchn = 2
[2006-04-03 16:45:09 xend] DEBUG (image:177) cmdline =
ip=:1.2.3.4::::eth0:dhcp root=/dev/sda1 ro
[2006-04-03 16:45:09 xend] DEBUG (image:178) ramdisk =
[2006-04-03 16:45:09 xend] DEBUG (image:179) vcpus = 1
[2006-04-03 16:45:09 xend] DEBUG (image:180) features =
[2006-04-03 16:45:09 xend] DEBUG (blkif:24) exception looking up device
number for sda1: [Errno 2] No such file or directory: '/dev/sda1'
[2006-04-03 16:45:09 xend] DEBUG (DevController:103) DevController:
writing {'virtual-device': '2049', 'backend-id': '0', 'state': '1',
'backend': '/local/domain/0/backend/vbd/1/2049'} to
/local/domain/1/device/vbd/2049.
[2006-04-03 16:45:09 xend] DEBUG (DevController:105) DevController:
writing {'domain': 'fedora.fc4', 'frontend':
'/local/domain/1/device/vbd/2049', 'dev': 'sda1', 'state': '1', 'params':
'/xen/fedora/fedora.fc4.img', 'mode': 'w', 'frontend-id': '1', 'type':
'file'} to /local/domain/0/backend/vbd/1/2049.
[2006-04-03 16:45:09 xend] DEBUG (blkif:24) exception looking up device
number for sda2: [Errno 2] No such file or directory: '/dev/sda2'
[2006-04-03 16:45:09 xend] DEBUG (DevController:103) DevController:
writing {'virtual-device': '2050', 'backend-id': '0', 'state': '1',
'backend': '/local/domain/0/backend/vbd/1/2050'} to
/local/domain/1/device/vbd/2050.
[2006-04-03 16:45:09 xend] DEBUG (DevController:105) DevController:
writing {'domain': 'fedora.fc4', 'frontend':
'/local/domain/1/device/vbd/2050', 'dev': 'sda2', 'state': '1', 'params':
'/xen/fedora/fedora.swap', 'mode': 'w', 'frontend-id': '1', 'type':
'file'} to /local/domain/0/backend/vbd/1/2050.
[2006-04-03 16:45:09 xend] DEBUG (DevController:103) DevController:
writing {'backend-id': '0', 'mac': '00:16:3e:3d:ec:05', 'handle': '0',
'state': '1', 'backend': '/local/domain/0/backend/vif/1/0'} to
/local/domain/1/device/vif/0.
[2006-04-03 16:45:09 xend] DEBUG (DevController:105) DevController:
writing {'mac': '00:16:3e:3d:ec:05', 'state': '1', 'handle': '0',
'script': '/etc/xen/scripts/vif-bridge', 'frontend-id': '1', 'domain':
'fedora.fc4', 'frontend': '/local/domain/1/device/vif/0'} to
/local/domain/0/backend/vif/1/0.
[2006-04-03 16:45:09 xend.XendDomainInfo] DEBUG (XendDomainInfo:667)
Storing VM details: {'ssidref': '0', 'uuid':
'be967607-af8e-0d14-956f-42443528af54', 'on_reboot': 'restart',
'start_time': '1144071909.98', 'on_poweroff': 'destroy', 'name':
'fedora.fc4', 'vcpus': '1', 'vcpu_avail': '1', 'memory': '128',
'on_crash': 'restart', 'image': "(linux (kernel
/boot/vmlinuz-2.6.16-1.2080_FC5xenU) (ip :1.2.3.4::::eth0:dhcp) (root
'/dev/sda1 ro'))", 'maxmem': '128'}
[2006-04-03 16:45:09 xend.XendDomainInfo] DEBUG (XendDomainInfo:692)
Storing domain details: {'console/ring-ref': '27070', 'console/port': '2',
'name': 'fedora.fc4', 'console/limit': '1048576', 'vm':
'/vm/be967607-af8e-0d14-956f-42443528af54', 'domid': '1',
'cpu/0/availability': 'online', 'memory/target': '131072',
'store/ring-ref': '116136', 'store/port': '1'}
[2006-04-03 16:45:09 xend] DEBUG (DevController:132) Waiting for devices vif.
[2006-04-03 16:45:09 xend] DEBUG (DevController:138) Waiting for 0.
[2006-04-03 16:45:09 xend] DEBUG (DevController:403) hotplugStatusCallback
/local/domain/0/backend/vif/1/0/hotplug-status.
[2006-04-03 16:45:10 xend] DEBUG (DevController:403) hotplugStatusCallback
/local/domain/0/backend/vif/1/0/hotplug-status.
[2006-04-03 16:45:10 xend] DEBUG (DevController:417) hotplugStatusCallback 1.
[2006-04-03 16:45:10 xend] DEBUG (DevController:132) Waiting for devices usb.
[2006-04-03 16:45:10 xend] DEBUG (DevController:132) Waiting for devices vbd.
[2006-04-03 16:45:10 xend] DEBUG (DevController:138) Waiting for 2049.
[2006-04-03 16:45:10 xend] DEBUG (DevController:403) hotplugStatusCallback
/local/domain/0/backend/vbd/1/2049/hotplug-status.
[2006-04-03 16:45:11 xend] DEBUG (DevController:403) hotplugStatusCallback
/local/domain/0/backend/vbd/1/2049/hotplug-status.
[2006-04-03 16:45:11 xend] DEBUG (DevController:417) hotplugStatusCallback 1.
[2006-04-03 16:45:11 xend] DEBUG (DevController:138) Waiting for 2050.
[2006-04-03 16:45:11 xend] DEBUG (DevController:403) hotplugStatusCallback
/local/domain/0/backend/vbd/1/2050/hotplug-status.
[2006-04-03 16:45:12 xend] DEBUG (DevController:403) hotplugStatusCallback
/local/domain/0/backend/vbd/1/2050/hotplug-status.
[2006-04-03 16:45:12 xend] DEBUG (DevController:417) hotplugStatusCallback 1.
[2006-04-03 16:45:12 xend] DEBUG (DevController:132) Waiting for devices pci.
[2006-04-03 16:45:12 xend] DEBUG (DevController:132) Waiting for devices
ioports.
[2006-04-03 16:45:12 xend] DEBUG (DevController:132) Waiting for devices
vtpm.
[2006-04-03 16:45:12 xend] INFO (XendDomain:360) Domain fedora.fc4 (1)
unpaused.
my cfg is:
kernel = "/boot/vmlinuz-2.6.16-1.2080_FC5xenU"
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"
Any ideas? I guess I am missing something but I cant find. Thanks in advance.
have a nice day
--
Murat Isik
www.bilgiguvenlik.com
18 years, 1 month
