Hi, I am having troubles starting a domU. I run it with: xm create -c config_file. Then I can see the output and it seems as if everything is going well. Then, the output suddenly stops without any failures and there is nothing I can do. The cursor is blinking but not responding to any keyboard inputs. I even cannot kill the process with ctrl+c. When I run xen-list-images it shows the image: $ xen-list-images Name: virtualrouter1 Memory: 128 IP: 10.23.100.13 Here is the output of xm create: Using config file "./virtualrouter1.cfg". Started domain virtualrouter1 (id=2) Bootdata ok (command line is root=/dev/sda1 ro ) Linux version 2.6.18.8-xen (root@virtualrouter1) (gcc version 4.3.2 (Ubuntu 4.3.2-1ubuntu12) ) #2 SMP Wed Jun 24 14:11:03 CEST 2009 BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000010800000 (usable) No mptable found. Built 1 zonelists. Total pages: 66660 Kernel command line: root=/dev/sda1 ro Initializing CPU#0 PID hash table entries: 2048 (order: 11, 16384 bytes) Xen reported: 3000.680 MHz processor. Console: colour dummy device 80x25 Dentry cache hash table entries: 65536 (order: 7, 524288 bytes) Inode-cache hash table entries: 32768 (order: 6, 262144 bytes) Software IO TLB disabled Memory: 231424k/270336k available (2585k kernel code, 30416k reserved, 1122k data, 192k init) Calibrating delay using timer specific routine.. 6002.56 BogoMIPS (lpj=30012826) Security Framework v1.0.0 initialized Capability LSM initialized Mount-cache hash table entries: 256 CPU: L1 I cache: 32K, L1 D cache: 32K CPU: L2 cache: 6144K CPU: Physical Processor ID: 0 CPU: Processor Core ID: 0 SMP alternatives: switching to UP code Freeing SMP alternatives: 28k freed Brought up 1 CPUs migration_cost=0 checking if image is initramfs... it is Freeing initrd memory: 20068k freed NET: Registered protocol family 16 Brought up 1 CPUs PCI: setting up Xen PCI frontend stub ACPI: Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI: disabled suspend: event channel 6 xen_mem: Initialising balloon driver. SCSI subsystem initialized PCI: System does not support PCI PCI: System does not support PCI NET: Registered protocol family 2 IP route cache hash table entries: 4096 (order: 3, 32768 bytes) TCP established hash table entries: 16384 (order: 6, 262144 bytes) TCP bind hash table entries: 8192 (order: 5, 131072 bytes) TCP: Hash tables configured (established 16384 bind 8192) TCP reno registered IA-32 Microcode Update Driver: v1.14a-xen <tigran@veritas.com> audit: initializing netlink socket (disabled) audit(1246352198.193:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 512 (order 0, 4096 bytes) Initializing Cryptographic API io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) rtc: IRQ 8 is not free. Non-volatile memory driver v1.2 RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize loop: loaded (max 8 devices) e1000e: Intel(R) PRO/1000 Network Driver - 0.3.3.3-k4 e1000e: Copyright (c) 1999-2008 Intel Corporation. Intel(R) Gigabit Ethernet Network Driver - version 1.2.45-k2 Copyright (c) 2008 Intel Corporation. ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver - version 1.3.56.5-NAPI Copyright (c) 1999-2008 Intel Corporation. Xen virtual console successfully installed as xvc0 Event-channel device installed. blktap_device_init: blktap device major 254 blktap_ring_init: blktap ring major: 253 netfront: Initialising virtual ethernet driver. vif vif-0: 2 parsing device/vif/0/mac vif vif-1: 2 parsing device/vif/1/mac vif vif-2: 2 parsing device/vif/2/mac Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx st: Version 20050830, fixed bufsize 32768, s/g segs 256 osst :I: Tape driver with OnStream support version 0.99.4 osst :I: $Id: osst.c,v 1.73 2005/01/01 21:13:34 wriede Exp $ aoe: aoe_init: AoE v22 initialised. PNP: No PS/2 controller found. Probing ports directly. i8042.c: No controller found. mice: PS/2 mouse device common for all mice md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 md: bitmap version 4.39 NET: Registered protocol family 1 NET: Registered protocol family 17 PCI IO multiplexer device installed. XENBUS: Device with no driver: device/console/0 BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. Freeing unused kernel memory: 192k freed fuse init (API version 7.7) What could be the problem? Appreciate any help. Thank you, Elisabeth ______________________________________________________ GRATIS für alle WEB.DE-Nutzer: Die maxdome Movie-FLAT! Jetzt freischalten unter http://movieflat.web.de _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Check if "xm list" shows you a running state ("r" for
running or "b" for
booting, "p" often means that an error occurred). I guess you might
have
forgotten the line
extra = ''''xencons=tty"
so the domU seems to hang because it doesn''t show the login prompt on
the correct console.
Compare to this thread:
http://lists.xensource.com/archives/html/xen-users/2009-06/msg00409.html
elli_dberg@web.de wrote:> Hi,
>
> I am having troubles starting a domU. I run it with: xm create -c
config_file. Then I can see the output and it seems as if everything is going
well. Then, the output suddenly stops without any failures and there is nothing
I can do. The cursor is blinking but not responding to any keyboard inputs. I
even cannot kill the process with ctrl+c. When I run xen-list-images it shows
the image:
> $ xen-list-images
> Name: virtualrouter1
> Memory: 128
> IP: 10.23.100.13
>
> Here is the output of xm create:
>
> Using config file "./virtualrouter1.cfg".
> Started domain virtualrouter1 (id=2)
> Bootdata ok (command line is root=/dev/sda1 ro )
> Linux version 2.6.18.8-xen (root@virtualrouter1) (gcc version 4.3.2 (Ubuntu
4.3.2-1ubuntu12) ) #2 SMP Wed Jun 24 14:11:03 CEST 2009
> BIOS-provided physical RAM map:
> Xen: 0000000000000000 - 0000000010800000 (usable)
> No mptable found.
> Built 1 zonelists. Total pages: 66660
> Kernel command line: root=/dev/sda1 ro
> Initializing CPU#0
> PID hash table entries: 2048 (order: 11, 16384 bytes)
> Xen reported: 3000.680 MHz processor.
> Console: colour dummy device 80x25
> Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
> Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
> Software IO TLB disabled
> Memory: 231424k/270336k available (2585k kernel code, 30416k reserved,
1122k data, 192k init)
> Calibrating delay using timer specific routine.. 6002.56 BogoMIPS
(lpj=30012826)
> Security Framework v1.0.0 initialized
> Capability LSM initialized
> Mount-cache hash table entries: 256
> CPU: L1 I cache: 32K, L1 D cache: 32K
> CPU: L2 cache: 6144K
> CPU: Physical Processor ID: 0
> CPU: Processor Core ID: 0
> SMP alternatives: switching to UP code
> Freeing SMP alternatives: 28k freed
> Brought up 1 CPUs
> migration_cost=0
> checking if image is initramfs... it is
> Freeing initrd memory: 20068k freed
> NET: Registered protocol family 16
> Brought up 1 CPUs
> PCI: setting up Xen PCI frontend stub
> ACPI: Interpreter disabled.
> Linux Plug and Play Support v0.97 (c) Adam Belay
> pnp: PnP ACPI: disabled
> suspend: event channel 6
> xen_mem: Initialising balloon driver.
> SCSI subsystem initialized
> PCI: System does not support PCI
> PCI: System does not support PCI
> NET: Registered protocol family 2
> IP route cache hash table entries: 4096 (order: 3, 32768 bytes)
> TCP established hash table entries: 16384 (order: 6, 262144 bytes)
> TCP bind hash table entries: 8192 (order: 5, 131072 bytes)
> TCP: Hash tables configured (established 16384 bind 8192)
> TCP reno registered
> IA-32 Microcode Update Driver: v1.14a-xen <tigran@veritas.com>
> audit: initializing netlink socket (disabled)
> audit(1246352198.193:1): initialized
> VFS: Disk quotas dquot_6.5.1
> Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
> Initializing Cryptographic API
> io scheduler noop registered
> io scheduler anticipatory registered
> io scheduler deadline registered
> io scheduler cfq registered (default)
> rtc: IRQ 8 is not free.
> Non-volatile memory driver v1.2
> RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
> loop: loaded (max 8 devices)
> e1000e: Intel(R) PRO/1000 Network Driver - 0.3.3.3-k4
> e1000e: Copyright (c) 1999-2008 Intel Corporation.
> Intel(R) Gigabit Ethernet Network Driver - version 1.2.45-k2
> Copyright (c) 2008 Intel Corporation.
> ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver - version
1.3.56.5-NAPI
> Copyright (c) 1999-2008 Intel Corporation.
> Xen virtual console successfully installed as xvc0
> Event-channel device installed.
> blktap_device_init: blktap device major 254
> blktap_ring_init: blktap ring major: 253
> netfront: Initialising virtual ethernet driver.
> vif vif-0: 2 parsing device/vif/0/mac
> vif vif-1: 2 parsing device/vif/1/mac
> vif vif-2: 2 parsing device/vif/2/mac
> Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
> ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
> st: Version 20050830, fixed bufsize 32768, s/g segs 256
> osst :I: Tape driver with OnStream support version 0.99.4
> osst :I: $Id: osst.c,v 1.73 2005/01/01 21:13:34 wriede Exp $
> aoe: aoe_init: AoE v22 initialised.
> PNP: No PS/2 controller found. Probing ports directly.
> i8042.c: No controller found.
> mice: PS/2 mouse device common for all mice
> md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
> md: bitmap version 4.39
> NET: Registered protocol family 1
> NET: Registered protocol family 17
> PCI IO multiplexer device installed.
> XENBUS: Device with no driver: device/console/0
> BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
> EDD information not available.
> Freeing unused kernel memory: 192k freed
> fuse init (API version 7.7)
>
>
> What could be the problem? Appreciate any help.
>
> Thank you,
> Elisabeth
>
>
> ______________________________________________________
> GRATIS für alle WEB.DE-Nutzer: Die maxdome Movie-FLAT!
> Jetzt freischalten unter http://movieflat.web.de
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>
>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Hi Andreas,
here is the output of xm list:
Name ID Mem VCPUs State Time(s)
Domain-0 0 487 2 r----- 352.1
virtualrouter1 2 256 1 -b---- 0.9
I started the virtualrouter1 already today in the morning. Does it mean it is
still booting?
Thank you
Andreas Sommer <AndiDog@web.de> schrieb am 30.06.2009 12:53:02:
Check if "xm list" shows you a running state ("r" for
running or "b" for
booting, "p" often means that an error occurred). I guess you might
have
forgotten the line
extra = ''''xencons=tty"
so the domU seems to hang because it doesn''t show the login prompt on
the correct console.
Compare to this thread:
http://lists.xensource.com/archives/html/xen-users/2009-06/msg00409.html
elli_dberg@web.de wrote:> Hi,
>
> I am having troubles starting a domU. I run it with: xm create -c
config_file. Then I can see the output and it seems as if everything is going
well. Then, the output suddenly stops without any failures and there is nothing
I can do. The cursor is blinking but not responding to any keyboard inputs. I
even cannot kill the process with ctrl+c. When I run xen-list-images it shows
the image:
> $ xen-list-images
> Name: virtualrouter1
> Memory: 128
> IP: 10.23.100.13
>
> Here is the output of xm create:
>
> Using config file "./virtualrouter1.cfg".
> Started domain virtualrouter1 (id=2)
> Bootdata ok (command line is root=/dev/sda1 ro )
> Linux version 2.6.18.8-xen (root@virtualrouter1) (gcc version 4.3.2 (Ubuntu
4.3.2-1ubuntu12) ) #2 SMP Wed Jun 24 14:11:03 CEST 2009
> BIOS-provided physical RAM map:
> Xen: 0000000000000000 - 0000000010800000 (usable)
> No mptable found.
> Built 1 zonelists. Total pages: 66660
> Kernel command line: root=/dev/sda1 ro
> Initializing CPU#0
> PID hash table entries: 2048 (order: 11, 16384 bytes)
> Xen reported: 3000.680 MHz processor.
> Console: colour dummy device 80x25
> Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
> Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
> Software IO TLB disabled
> Memory: 231424k/270336k available (2585k kernel code, 30416k reserved,
1122k data, 192k init)
> Calibrating delay using timer specific routine.. 6002.56 BogoMIPS
(lpj=30012826)
> Security Framework v1.0.0 initialized
> Capability LSM initialized
> Mount-cache hash table entries: 256
> CPU: L1 I cache: 32K, L1 D cache: 32K
> CPU: L2 cache: 6144K
> CPU: Physical Processor ID: 0
> CPU: Processor Core ID: 0
> SMP alternatives: switching to UP code
> Freeing SMP alternatives: 28k freed
> Brought up 1 CPUs
> migration_cost=0
> checking if image is initramfs... it is
> Freeing initrd memory: 20068k freed
> NET: Registered protocol family 16
> Brought up 1 CPUs
> PCI: setting up Xen PCI frontend stub
> ACPI: Interpreter disabled.
> Linux Plug and Play Support v0.97 (c) Adam Belay
> pnp: PnP ACPI: disabled
> suspend: event channel 6
> xen_mem: Initialising balloon driver.
> SCSI subsystem initialized
> PCI: System does not support PCI
> PCI: System does not support PCI
> NET: Registered protocol family 2
> IP route cache hash table entries: 4096 (order: 3, 32768 bytes)
> TCP established hash table entries: 16384 (order: 6, 262144 bytes)
> TCP bind hash table entries: 8192 (order: 5, 131072 bytes)
> TCP: Hash tables configured (established 16384 bind 8192)
> TCP reno registered
> IA-32 Microcode Update Driver: v1.14a-xen <tigran@veritas.com>
> audit: initializing netlink socket (disabled)
> audit(1246352198.193:1): initialized
> VFS: Disk quotas dquot_6.5.1
> Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
> Initializing Cryptographic API
> io scheduler noop registered
> io scheduler anticipatory registered
> io scheduler deadline registered
> io scheduler cfq registered (default)
> rtc: IRQ 8 is not free.
> Non-volatile memory driver v1.2
> RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
> loop: loaded (max 8 devices)
> e1000e: Intel(R) PRO/1000 Network Driver - 0.3.3.3-k4
> e1000e: Copyright (c) 1999-2008 Intel Corporation.
> Intel(R) Gigabit Ethernet Network Driver - version 1.2.45-k2
> Copyright (c) 2008 Intel Corporation.
> ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver - version
1.3.56.5-NAPI
> Copyright (c) 1999-2008 Intel Corporation.
> Xen virtual console successfully installed as xvc0
> Event-channel device installed.
> blktap_device_init: blktap device major 254
> blktap_ring_init: blktap ring major: 253
> netfront: Initialising virtual ethernet driver.
> vif vif-0: 2 parsing device/vif/0/mac
> vif vif-1: 2 parsing device/vif/1/mac
> vif vif-2: 2 parsing device/vif/2/mac
> Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
> ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
> st: Version 20050830, fixed bufsize 32768, s/g segs 256
> osst :I: Tape driver with OnStream support version 0.99.4
> osst :I: $Id: osst.c,v 1.73 2005/01/01 21:13:34 wriede Exp $
> aoe: aoe_init: AoE v22 initialised.
> PNP: No PS/2 controller found. Probing ports directly.
> i8042.c: No controller found.
> mice: PS/2 mouse device common for all mice
> md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
> md: bitmap version 4.39
> NET: Registered protocol family 1
> NET: Registered protocol family 17
> PCI IO multiplexer device installed.
> XENBUS: Device with no driver: device/console/0
> BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
> EDD information not available.
> Freeing unused kernel memory: 192k freed
> fuse init (API version 7.7)
>
>
> What could be the problem? Appreciate any help.
>
> Thank you,
> Elisabeth
_________________________________________________________________
Neu: WEB.DE Doppel-FLAT mit Internet-Flatrate + Telefon-Flatrate
für nur 19,99 Euro/mtl.!* http://produkte.web.de/go/01/
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
elli_dberg@web.de schrieb:>> >> Andreas Sommer <AndiDog@web.de> schrieb am 30.06.2009 12:53:02: >> Check if "xm list" shows you a running state ("r" for running or "b" for >> booting, "p" often means that an error occurred). I guess you might have >> forgotten the line >> >> here is the output of xm list: > > Name ID Mem VCPUs State Time(s) Domain-0 0 487 2 r----- 352.1 > virtualrouter1 2 256 1 -b---- 0.9 > > I started the virtualrouter1 already today in the morning. Does it > mean it is still booting? >All my running DomUs have state "b"! Did i need any software in domU for state "r"? Regards Stefan Kuhne _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Stefan Kuhne:> All my running DomUs have state "b"! > Did i need any software in domU for state "r"?This is to be expected, especially on systems with a single CPU/core. While xm info is running in the Dom0 it uses the CPU - which means the DomUs cant use it in this very moment. -- Regards mks _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I don''t know how exactly Xen retrieves the state of operating systems. "r" and "b" usually means that the domU is running normally. As I said, you should try adding the line extra = "xencons=tty" to your configuration file to make sure that the login prompt will appear on your screen output. Then destroy your running machine with "xm destroy virtualrouter1" (afterwards it shouldn''t appear in "xm list" anymore!), edit the configuration and start it again with "xm create -c your_config_file". And by the way, you can send the "xm create" command to the background by pressing Ctrl+Shift+] (on a US keyboard, of course, don''t know about the German keyboard layout). elli_dberg@web.de wrote:> Hi Andreas, > > here is the output of xm list: > > Name ID Mem VCPUs State Time(s) > Domain-0 0 487 2 r----- 352.1 > virtualrouter1 2 256 1 -b---- 0.9 > > I started the virtualrouter1 already today in the morning. Does it mean it is still booting? > > Thank you > > Andreas Sommer <AndiDog@web.de> schrieb am 30.06.2009 12:53:02: > Check if "xm list" shows you a running state ("r" for running or "b" for > booting, "p" often means that an error occurred). I guess you might have > forgotten the line > > extra = ''''xencons=tty" > > so the domU seems to hang because it doesn''t show the login prompt on > the correct console. > > Compare to this thread: > http://lists.xensource.com/archives/html/xen-users/2009-06/msg00409.html > > > elli_dberg@web.de wrote: > >> Hi, >> >> I am having troubles starting a domU. I run it with: xm create -c config_file. Then I can see the output and it seems as if everything is going well. Then, the output suddenly stops without any failures and there is nothing I can do. The cursor is blinking but not responding to any keyboard inputs. I even cannot kill the process with ctrl+c. When I run xen-list-images it shows the image: >> $ xen-list-images >> Name: virtualrouter1 >> Memory: 128 >> IP: 10.23.100.13 >> >> Here is the output of xm create: >> >> Using config file "./virtualrouter1.cfg". >> Started domain virtualrouter1 (id=2) >> Bootdata ok (command line is root=/dev/sda1 ro ) >> Linux version 2.6.18.8-xen (root@virtualrouter1) (gcc version 4.3.2 (Ubuntu 4.3.2-1ubuntu12) ) #2 SMP Wed Jun 24 14:11:03 CEST 2009 >> BIOS-provided physical RAM map: >> Xen: 0000000000000000 - 0000000010800000 (usable) >> No mptable found. >> Built 1 zonelists. Total pages: 66660 >> Kernel command line: root=/dev/sda1 ro >> Initializing CPU#0 >> PID hash table entries: 2048 (order: 11, 16384 bytes) >> Xen reported: 3000.680 MHz processor. >> Console: colour dummy device 80x25 >> Dentry cache hash table entries: 65536 (order: 7, 524288 bytes) >> Inode-cache hash table entries: 32768 (order: 6, 262144 bytes) >> Software IO TLB disabled >> Memory: 231424k/270336k available (2585k kernel code, 30416k reserved, 1122k data, 192k init) >> Calibrating delay using timer specific routine.. 6002.56 BogoMIPS (lpj=30012826) >> Security Framework v1.0.0 initialized >> Capability LSM initialized >> Mount-cache hash table entries: 256 >> CPU: L1 I cache: 32K, L1 D cache: 32K >> CPU: L2 cache: 6144K >> CPU: Physical Processor ID: 0 >> CPU: Processor Core ID: 0 >> SMP alternatives: switching to UP code >> Freeing SMP alternatives: 28k freed >> Brought up 1 CPUs >> migration_cost=0 >> checking if image is initramfs... it is >> Freeing initrd memory: 20068k freed >> NET: Registered protocol family 16 >> Brought up 1 CPUs >> PCI: setting up Xen PCI frontend stub >> ACPI: Interpreter disabled. >> Linux Plug and Play Support v0.97 (c) Adam Belay >> pnp: PnP ACPI: disabled >> suspend: event channel 6 >> xen_mem: Initialising balloon driver. >> SCSI subsystem initialized >> PCI: System does not support PCI >> PCI: System does not support PCI >> NET: Registered protocol family 2 >> IP route cache hash table entries: 4096 (order: 3, 32768 bytes) >> TCP established hash table entries: 16384 (order: 6, 262144 bytes) >> TCP bind hash table entries: 8192 (order: 5, 131072 bytes) >> TCP: Hash tables configured (established 16384 bind 8192) >> TCP reno registered >> IA-32 Microcode Update Driver: v1.14a-xen <tigran@veritas.com> >> audit: initializing netlink socket (disabled) >> audit(1246352198.193:1): initialized >> VFS: Disk quotas dquot_6.5.1 >> Dquot-cache hash table entries: 512 (order 0, 4096 bytes) >> Initializing Cryptographic API >> io scheduler noop registered >> io scheduler anticipatory registered >> io scheduler deadline registered >> io scheduler cfq registered (default) >> rtc: IRQ 8 is not free. >> Non-volatile memory driver v1.2 >> RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize >> loop: loaded (max 8 devices) >> e1000e: Intel(R) PRO/1000 Network Driver - 0.3.3.3-k4 >> e1000e: Copyright (c) 1999-2008 Intel Corporation. >> Intel(R) Gigabit Ethernet Network Driver - version 1.2.45-k2 >> Copyright (c) 2008 Intel Corporation. >> ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver - version 1.3.56.5-NAPI >> Copyright (c) 1999-2008 Intel Corporation. >> Xen virtual console successfully installed as xvc0 >> Event-channel device installed. >> blktap_device_init: blktap device major 254 >> blktap_ring_init: blktap ring major: 253 >> netfront: Initialising virtual ethernet driver. >> vif vif-0: 2 parsing device/vif/0/mac >> vif vif-1: 2 parsing device/vif/1/mac >> vif vif-2: 2 parsing device/vif/2/mac >> Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 >> ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx >> st: Version 20050830, fixed bufsize 32768, s/g segs 256 >> osst :I: Tape driver with OnStream support version 0.99.4 >> osst :I: $Id: osst.c,v 1.73 2005/01/01 21:13:34 wriede Exp $ >> aoe: aoe_init: AoE v22 initialised. >> PNP: No PS/2 controller found. Probing ports directly. >> i8042.c: No controller found. >> mice: PS/2 mouse device common for all mice >> md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 >> md: bitmap version 4.39 >> NET: Registered protocol family 1 >> NET: Registered protocol family 17 >> PCI IO multiplexer device installed. >> XENBUS: Device with no driver: device/console/0 >> BIOS EDD facility v0.16 2004-Jun-25, 0 devices found >> EDD information not available. >> Freeing unused kernel memory: 192k freed >> fuse init (API version 7.7) >> >> >> What could be the problem? Appreciate any help. >> >> Thank you, >> Elisabeth >> > _________________________________________________________________ > Neu: WEB.DE Doppel-FLAT mit Internet-Flatrate + Telefon-Flatrate > für nur 19,99 Euro/mtl.!* http://produkte.web.de/go/01/ > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Andreas, and everyone,
I did as you said and I set extra= "xencons=tty". Now the boot precess
goes some more lines further but now there is another problem. These are the
last lines of the output of xm create -c ...
...
fuse init (API version 7.7)
Done.
Begin: Running /scripts/init-premount ...
Done.
Begin: Mounting root file system... ...
Begin: Running /scripts/local-top ...
Done.
Begin: Waiting for root file system... ...
Done.
chvt: can''t open console
chvt: VT_ACTIVATE: Bad file descriptor
Gave up waiting for root device. Common problems:
- Boot args (cat /proc/cmdline)
- Check rootdelay= (did the system wait long enough?)
- Check root= (did the system wait for the right device?)
- Missing modules (cat /proc/modules; ls /dev)
chvt: can''t open console
chvt: VT_ACTIVATE: Bad file descriptor
ALERT! /dev/sda1 does not exist. Dropping to a shell!
BusyBox v1.10.2 (Ubuntu 1:1.10.2-1ubuntu7) built-in shell (ash)
Enter ''help'' for a list of built-in commands.
(initramfs)
Does that mean that the virtual machine cannot recognize the file system? I have
a SATA hard drive and I am using the same kernel and setup as for dom0. I tried
also specifying the root device as its UUID but didn''t work neither.
Do have any idea?
Thank you
Andreas Sommer <AndiDog@web.de> schrieb am 30.06.2009 12:53:02:
Check if "xm list" shows you a running state ("r" for
running or "b" for
booting, "p" often means that an error occurred). I guess you might
have
forgotten the line
extra = ''''xencons=tty"
so the domU seems to hang because it doesn''t show the login prompt on
the correct console.
Compare to this thread:
http://lists.xensource.com/archives/html/xen-users/2009-06/msg00409.html
elli_dberg@web.de wrote:> Hi,
>
> I am having troubles starting a domU. I run it with: xm create -c
config_file. Then I can see the output and it seems as if everything is going
well. Then, the output suddenly stops without any failures and there is nothing
I can do. The cursor is blinking but not responding to any keyboard inputs. I
even cannot kill the process with ctrl+c. When I run xen-list-images it shows
the image:
> $ xen-list-images
> Name: virtualrouter1
> Memory: 128
> IP: 10.23.100.13
>
> Here is the output of xm create:
>
> Using config file "./virtualrouter1.cfg".
> Started domain virtualrouter1 (id=2)
> Bootdata ok (command line is root=/dev/sda1 ro )
> Linux version 2.6.18.8-xen (root@virtualrouter1) (gcc version 4.3.2 (Ubuntu
4.3.2-1ubuntu12) ) #2 SMP Wed Jun 24 14:11:03 CEST 2009
> BIOS-provided physical RAM map:
> Xen: 0000000000000000 - 0000000010800000 (usable)
> No mptable found.
> Built 1 zonelists. Total pages: 66660
> Kernel command line: root=/dev/sda1 ro
> Initializing CPU#0
> PID hash table entries: 2048 (order: 11, 16384 bytes)
> Xen reported: 3000.680 MHz processor.
> Console: colour dummy device 80x25
> Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
> Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
> Software IO TLB disabled
> Memory: 231424k/270336k available (2585k kernel code, 30416k reserved,
1122k data, 192k init)
> Calibrating delay using timer specific routine.. 6002.56 BogoMIPS
(lpj=30012826)
> Security Framework v1.0.0 initialized
> Capability LSM initialized
> Mount-cache hash table entries: 256
> CPU: L1 I cache: 32K, L1 D cache: 32K
> CPU: L2 cache: 6144K
> CPU: Physical Processor ID: 0
> CPU: Processor Core ID: 0
> SMP alternatives: switching to UP code
> Freeing SMP alternatives: 28k freed
> Brought up 1 CPUs
> migration_cost=0
> checking if image is initramfs... it is
> Freeing initrd memory: 20068k freed
> NET: Registered protocol family 16
> Brought up 1 CPUs
> PCI: setting up Xen PCI frontend stub
> ACPI: Interpreter disabled.
> Linux Plug and Play Support v0.97 (c) Adam Belay
> pnp: PnP ACPI: disabled
> suspend: event channel 6
> xen_mem: Initialising balloon driver.
> SCSI subsystem initialized
> PCI: System does not support PCI
> PCI: System does not support PCI
> NET: Registered protocol family 2
> IP route cache hash table entries: 4096 (order: 3, 32768 bytes)
> TCP established hash table entries: 16384 (order: 6, 262144 bytes)
> TCP bind hash table entries: 8192 (order: 5, 131072 bytes)
> TCP: Hash tables configured (established 16384 bind 8192)
> TCP reno registered
> IA-32 Microcode Update Driver: v1.14a-xen <tigran@veritas.com>
> audit: initializing netlink socket (disabled)
> audit(1246352198.193:1): initialized
> VFS: Disk quotas dquot_6.5.1
> Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
> Initializing Cryptographic API
> io scheduler noop registered
> io scheduler anticipatory registered
> io scheduler deadline registered
> io scheduler cfq registered (default)
> rtc: IRQ 8 is not free.
> Non-volatile memory driver v1.2
> RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
> loop: loaded (max 8 devices)
> e1000e: Intel(R) PRO/1000 Network Driver - 0.3.3.3-k4
> e1000e: Copyright (c) 1999-2008 Intel Corporation.
> Intel(R) Gigabit Ethernet Network Driver - version 1.2.45-k2
> Copyright (c) 2008 Intel Corporation.
> ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver - version
1.3.56.5-NAPI
> Copyright (c) 1999-2008 Intel Corporation.
> Xen virtual console successfully installed as xvc0
> Event-channel device installed.
> blktap_device_init: blktap device major 254
> blktap_ring_init: blktap ring major: 253
> netfront: Initialising virtual ethernet driver.
> vif vif-0: 2 parsing device/vif/0/mac
> vif vif-1: 2 parsing device/vif/1/mac
> vif vif-2: 2 parsing device/vif/2/mac
> Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
> ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
> st: Version 20050830, fixed bufsize 32768, s/g segs 256
> osst :I: Tape driver with OnStream support version 0.99.4
> osst :I: $Id: osst.c,v 1.73 2005/01/01 21:13:34 wriede Exp $
> aoe: aoe_init: AoE v22 initialised.
> PNP: No PS/2 controller found. Probing ports directly.
> i8042.c: No controller found.
> mice: PS/2 mouse device common for all mice
> md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
> md: bitmap version 4.39
> NET: Registered protocol family 1
> NET: Registered protocol family 17
> PCI IO multiplexer device installed.
> XENBUS: Device with no driver: device/console/0
> BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
> EDD information not available.
> Freeing unused kernel memory: 192k freed
> fuse init (API version 7.7)
>
>
> What could be the problem? Appreciate any help.
>
> Thank you,
> Elisabeth
______________________________________________________
GRATIS für alle WEB.DE-Nutzer: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://movieflat.web.de
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Looks like a bigger problem. Could you post your Xen version number and the domU configuration file please? /PS: I''m always getting two equivalent mails from you?!! Please just do a "Reply to all", meaning you send exactly one mail to me with "xen-users@lists.xensource.com" as CC./ elli_dberg@web.de wrote:> Hi Andreas, and everyone, > > I did as you said and I set extra= "xencons=tty". Now the boot precess goes some more lines further but now there is another problem. These are the last lines of the output of xm create -c ... > > ... > fuse init (API version 7.7) > Done. > Begin: Running /scripts/init-premount ... > Done. > Begin: Mounting root file system... ... > Begin: Running /scripts/local-top ... > Done. > Begin: Waiting for root file system... ... > Done. > chvt: can''t open console > chvt: VT_ACTIVATE: Bad file descriptor > Gave up waiting for root device. Common problems: > - Boot args (cat /proc/cmdline) > - Check rootdelay= (did the system wait long enough?) > - Check root= (did the system wait for the right device?) > - Missing modules (cat /proc/modules; ls /dev) > chvt: can''t open console > chvt: VT_ACTIVATE: Bad file descriptor > ALERT! /dev/sda1 does not exist. Dropping to a shell! > > > BusyBox v1.10.2 (Ubuntu 1:1.10.2-1ubuntu7) built-in shell (ash) > Enter ''help'' for a list of built-in commands. > > (initramfs) > > Does that mean that the virtual machine cannot recognize the file system? I have a SATA hard drive and I am using the same kernel and setup as for dom0. I tried also specifying the root device as its UUID but didn''t work neither. > Do have any idea? > > Thank you > > Andreas Sommer <AndiDog@web.de> schrieb am 30.06.2009 12:53:02: > Check if "xm list" shows you a running state ("r" for running or "b" for > booting, "p" often means that an error occurred). I guess you might have > forgotten the line > > extra = ''''xencons=tty" > > so the domU seems to hang because it doesn''t show the login prompt on > the correct console. > > Compare to this thread: > http://lists.xensource.com/archives/html/xen-users/2009-06/msg00409.html > > > elli_dberg@web.de wrote: > >> Hi, >> >> I am having troubles starting a domU. I run it with: xm create -c config_file. Then I can see the output and it seems as if everything is going well. Then, the output suddenly stops without any failures and there is nothing I can do. The cursor is blinking but not responding to any keyboard inputs. I even cannot kill the process with ctrl+c. When I run xen-list-images it shows the image: >> $ xen-list-images >> Name: virtualrouter1 >> Memory: 128 >> IP: 10.23.100.13 >> >> Here is the output of xm create: >> >> Using config file "./virtualrouter1.cfg". >> Started domain virtualrouter1 (id=2) >> Bootdata ok (command line is root=/dev/sda1 ro ) >> Linux version 2.6.18.8-xen (root@virtualrouter1) (gcc version 4.3.2 (Ubuntu 4.3.2-1ubuntu12) ) #2 SMP Wed Jun 24 14:11:03 CEST 2009 >> BIOS-provided physical RAM map: >> Xen: 0000000000000000 - 0000000010800000 (usable) >> No mptable found. >> Built 1 zonelists. Total pages: 66660 >> Kernel command line: root=/dev/sda1 ro >> Initializing CPU#0 >> PID hash table entries: 2048 (order: 11, 16384 bytes) >> Xen reported: 3000.680 MHz processor. >> Console: colour dummy device 80x25 >> Dentry cache hash table entries: 65536 (order: 7, 524288 bytes) >> Inode-cache hash table entries: 32768 (order: 6, 262144 bytes) >> Software IO TLB disabled >> Memory: 231424k/270336k available (2585k kernel code, 30416k reserved, 1122k data, 192k init) >> Calibrating delay using timer specific routine.. 6002.56 BogoMIPS (lpj=30012826) >> Security Framework v1.0.0 initialized >> Capability LSM initialized >> Mount-cache hash table entries: 256 >> CPU: L1 I cache: 32K, L1 D cache: 32K >> CPU: L2 cache: 6144K >> CPU: Physical Processor ID: 0 >> CPU: Processor Core ID: 0 >> SMP alternatives: switching to UP code >> Freeing SMP alternatives: 28k freed >> Brought up 1 CPUs >> migration_cost=0 >> checking if image is initramfs... it is >> Freeing initrd memory: 20068k freed >> NET: Registered protocol family 16 >> Brought up 1 CPUs >> PCI: setting up Xen PCI frontend stub >> ACPI: Interpreter disabled. >> Linux Plug and Play Support v0.97 (c) Adam Belay >> pnp: PnP ACPI: disabled >> suspend: event channel 6 >> xen_mem: Initialising balloon driver. >> SCSI subsystem initialized >> PCI: System does not support PCI >> PCI: System does not support PCI >> NET: Registered protocol family 2 >> IP route cache hash table entries: 4096 (order: 3, 32768 bytes) >> TCP established hash table entries: 16384 (order: 6, 262144 bytes) >> TCP bind hash table entries: 8192 (order: 5, 131072 bytes) >> TCP: Hash tables configured (established 16384 bind 8192) >> TCP reno registered >> IA-32 Microcode Update Driver: v1.14a-xen <tigran@veritas.com> >> audit: initializing netlink socket (disabled) >> audit(1246352198.193:1): initialized >> VFS: Disk quotas dquot_6.5.1 >> Dquot-cache hash table entries: 512 (order 0, 4096 bytes) >> Initializing Cryptographic API >> io scheduler noop registered >> io scheduler anticipatory registered >> io scheduler deadline registered >> io scheduler cfq registered (default) >> rtc: IRQ 8 is not free. >> Non-volatile memory driver v1.2 >> RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize >> loop: loaded (max 8 devices) >> e1000e: Intel(R) PRO/1000 Network Driver - 0.3.3.3-k4 >> e1000e: Copyright (c) 1999-2008 Intel Corporation. >> Intel(R) Gigabit Ethernet Network Driver - version 1.2.45-k2 >> Copyright (c) 2008 Intel Corporation. >> ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver - version 1.3.56.5-NAPI >> Copyright (c) 1999-2008 Intel Corporation. >> Xen virtual console successfully installed as xvc0 >> Event-channel device installed. >> blktap_device_init: blktap device major 254 >> blktap_ring_init: blktap ring major: 253 >> netfront: Initialising virtual ethernet driver. >> vif vif-0: 2 parsing device/vif/0/mac >> vif vif-1: 2 parsing device/vif/1/mac >> vif vif-2: 2 parsing device/vif/2/mac >> Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 >> ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx >> st: Version 20050830, fixed bufsize 32768, s/g segs 256 >> osst :I: Tape driver with OnStream support version 0.99.4 >> osst :I: $Id: osst.c,v 1.73 2005/01/01 21:13:34 wriede Exp $ >> aoe: aoe_init: AoE v22 initialised. >> PNP: No PS/2 controller found. Probing ports directly. >> i8042.c: No controller found. >> mice: PS/2 mouse device common for all mice >> md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 >> md: bitmap version 4.39 >> NET: Registered protocol family 1 >> NET: Registered protocol family 17 >> PCI IO multiplexer device installed. >> XENBUS: Device with no driver: device/console/0 >> BIOS EDD facility v0.16 2004-Jun-25, 0 devices found >> EDD information not available. >> Freeing unused kernel memory: 192k freed >> fuse init (API version 7.7) >> >> >> What could be the problem? Appreciate any help. >> >> Thank you, >> Elisabeth >> > ______________________________________________________ > GRATIS für alle WEB.DE-Nutzer: Die maxdome Movie-FLAT! > Jetzt freischalten unter http://movieflat.web.de > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Andreas,
I use xen 3.4.0 and here is the configuration file for my domU:
kernel = "/boot/vmlinuz-2.6.18.8-xen"
ramdisk = "/boot/initrd.img-2.6.18.8-xen"
memory = 128
name = "virtualrouter1"
vif = [ ''type=ioemu, mac=00:16:3e:70:00:00, bridge=xenbr1, ip=10.0.1.1,
script=vif-bridge'',
''type=ioemu, mac=00:16:3e:70:00:01, bridge=xenbr2, ip=10.0.2.1,
script=vif-bridge'',
''type=ioemu, mac=00:16:3e:70:00:02, bridge=xenbr3,
ip=10.23.100.13, script=vif-bridge'']
root = "UUID=94a89174-ddca-4b8c-894c-bb3b7e0c62fa ro"
extra = "xencons=tty"
on_poweroff = ''destroy''
on_reboot = ''restart''
on_crash = ''restart''
I created this domU using LVM.
Thank you
Andreas Sommer <AndiDog@web.de> schrieb am 30.06.2009 14:38:42:
Looks like a bigger problem. Could you post your Xen version number
and the domU configuration file please?
PS: I''m always getting two equivalent mails from you?!! Please just
do a "Reply to all", meaning you send exactly one mail to me with
"
xen-users@lists.xensource.com" as CC.
elli_dberg@web.de wrote:Hi Andreas, and everyone, I did as you said
and I set extra= "xencons=tty". Now the boot precess goes some more
lines further but now there is another problem. These are the last
lines of the output of xm create -c ... ... fuse init (API version 7.
7) Done. Begin: Running /scripts/init-premount ... Done. Begin:
Mounting root file system... ... Begin: Running /scripts/local-top ...
Done. Begin: Waiting for root file system... ... Done. chvt: can''t
open console chvt: VT_ACTIVATE: Bad file descriptor Gave up waiting
for root device. Common problems: - Boot args (cat /proc/cmdline) -
Check rootdelay= (did the system wait long enough?) - Check root= (
did the system wait for the right device?) - Missing modules (cat /
proc/modules; ls /dev) chvt: can''t open console chvt: VT_ACTIVATE:
Bad file descriptor ALERT! /dev/sda1 does not exist. Dropping to a
shell! BusyBox v1.10.2 (Ubuntu 1:1.10.2-1ubuntu7) built-in shell (ash)
Enter ''help'' for a list of built-in commands. (initramfs) Does
that
mean that the virtual machine cannot recognize the file system? I
have a SATA hard drive and I am using the same kernel and setup as
for dom0. I tried also specifying the root device as its UUID but
didn''t work neither. Do have any idea? Thank you Andreas Sommer <
AndiDog@web.de> schrieb am 30.06.2009 12:53:02: Check if "xm list"
shows you a running state ("r" for running or "b" for
booting, "p"
often means that an error occurred). I guess you might have forgotten
the line extra = ''''xencons=tty" so the domU seems to hang
because it
doesn''t show the login prompt on the correct console. Compare to this
thread: http://lists.xensource.com/archives/html/xen-users/2009-06/
msg00409.htmlelli_dberg@web.de wrote: Hi, I am having troubles
starting a domU. I run it with: xm create -c config_file. Then I can
see the output and it seems as if everything is going well. Then, the
output suddenly stops without any failures and there is nothing I can
do. The cursor is blinking but not responding to any keyboard inputs.
I even cannot kill the process with ctrl+c. When I run xen-list-
images it shows the image: $ xen-list-images Name: virtualrouter1
Memory: 128 IP: 10.23.100.13 Here is the output of xm create: Using
config file "./virtualrouter1.cfg". Started domain virtualrouter1
(id2) Bootdata ok (command line is root=/dev/sda1 ro ) Linux version 2.6.
18.8-xen (root@virtualrouter1) (gcc version 4.3.2 (Ubuntu 4.3.2-
1ubuntu12) ) #2 SMP Wed Jun 24 14:11:03 CEST 2009 BIOS-provided
physical RAM map: Xen: 0000000000000000 - 0000000010800000 (usable)
No mptable found. Built 1 zonelists. Total pages: 66660 Kernel
command line: root=/dev/sda1 ro Initializing CPU#0 PID hash table
entries: 2048 (order: 11, 16384 bytes) Xen reported: 3000.680 MHz
processor. Console: colour dummy device 80x25 Dentry cache hash table
entries: 65536 (order: 7, 524288 bytes) Inode-cache hash table
entries: 32768 (order: 6, 262144 bytes) Software IO TLB disabled
Memory: 231424k/270336k available (2585k kernel code, 30416k reserved,
1122k data, 192k init) Calibrating delay using timer specific routine.
. 6002.56 BogoMIPS (lpj=30012826) Security Framework v1.0.0
initialized Capability LSM initialized Mount-cache hash table entries:
256 CPU: L1 I cache: 32K, L1 D cache: 32K CPU: L2 cache: 6144K CPU:
Physical Processor ID: 0 CPU: Processor Core ID: 0 SMP alternatives:
switching to UP code Freeing SMP alternatives: 28k freed Brought up 1
CPUs migration_cost=0 checking if image is initramfs... it is Freeing
initrd memory: 20068k freed NET: Registered protocol family 16
Brought up 1 CPUs PCI: setting up Xen PCI frontend stub ACPI:
Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam
Belay pnp: PnP ACPI: disabled suspend: event channel 6 xen_mem:
Initialising balloon driver. SCSI subsystem initialized PCI: System
does not support PCI PCI: System does not support PCI NET: Registered
protocol family 2 IP route cache hash table entries: 4096 (order: 3,
32768 bytes) TCP established hash table entries: 16384 (order: 6,
262144 bytes) TCP bind hash table entries: 8192 (order: 5, 131072
bytes) TCP: Hash tables configured (established 16384 bind 8192) TCP
reno registered IA-32 Microcode Update Driver: v1.14a-xen <tigran@
veritas.com>audit: initializing netlink socket (disabled) audit(
1246352198.193:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-
cache hash table entries: 512 (order 0, 4096 bytes) Initializing
Cryptographic API io scheduler noop registered io scheduler
anticipatory registered io scheduler deadline registered io scheduler
cfq registered (default) rtc: IRQ 8 is not free. Non-volatile memory
driver v1.2 RAMDISK driver initialized: 16 RAM disks of 16384K size
1024 blocksize loop: loaded (max 8 devices) e1000e: Intel(R) PRO/1000
Network Driver - 0.3.3.3-k4 e1000e: Copyright (c) 1999-2008 Intel
Corporation. Intel(R) Gigabit Ethernet Network Driver - version 1.2.
45-k2 Copyright (c) 2008 Intel Corporation. ixgbe: Intel(R) 10
Gigabit PCI Express Network Driver - version 1.3.56.5-NAPI Copyright (
c) 1999-2008 Intel Corporation. Xen virtual console successfully
installed as xvc0 Event-channel device installed. blktap_device_init:
blktap device major 254 blktap_ring_init: blktap ring major: 253
netfront: Initialising virtual ethernet driver. vif vif-0: 2 parsing
device/vif/0/mac vif vif-1: 2 parsing device/vif/1/mac vif vif-2: 2
parsing device/vif/2/mac Uniform Multi-Platform E-IDE driver Revision:
7.00alpha2 ide: Assuming 50MHz system bus speed for PIO modes;
override with idebus=xx st: Version 20050830, fixed bufsize 32768, s/
g segs 256 osst :I: Tape driver with OnStream support version 0.99.4
osst :I: $Id: osst.c,v 1.73 2005/01/01 21:13:34 wriede Exp $ aoe: aoe_
init: AoE v22 initialised. PNP: No PS/2 controller found. Probing
ports directly. i8042.c: No controller found. mice: PS/2 mouse device
common for all mice md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS27 md:
bitmap version 4.39 NET: Registered protocol family 1 NET:
Registered protocol family 17 PCI IO multiplexer device installed.
XENBUS: Device with no driver: device/console/0 BIOS EDD facility v0.
16 2004-Jun-25, 0 devices found EDD information not available.
Freeing unused kernel memory: 192k freed fuse init (API version 7.7)
What could be the problem? Appreciate any help. Thank you, Elisabeth _
_____________________________________________________ GRATIS für alle
WEB.DE-Nutzer: Die maxdome Movie-FLAT! Jetzt freischalten unter http:/
/movieflat.web.de_______________________________________________ Xen-
users mailing listXen-users@lists.xensource.comhttp://lists.xensource.
com/xen-users_______________________________________________ Xen-
users mailing list Xen-users@lists.xensource.com http://lists.
xensource.com/xen-users
______________________________________________________
GRATIS für alle WEB.DE-Nutzer: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://movieflat.web.de
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Hi again, sorry but I don''t know anything about using real partitions with Xen guests. Maybe you should make sure that it is unmounted in dom0 ?! Furthermore the modules needed to load the file system must be provided for the domU kernel (and probably inside the initrd image). I think somebody else will have to help you on that problem... Best regards elli_dberg@web.de wrote:> Hi Andreas, > > I use xen 3.4.0 and here is the configuration file for my domU: > > kernel = "/boot/vmlinuz-2.6.18.8-xen" > ramdisk = "/boot/initrd.img-2.6.18.8-xen" > memory = 128 > name = "virtualrouter1" > vif = [ ''type=ioemu, mac=00:16:3e:70:00:00, bridge=xenbr1, ip=10.0.1.1, script=vif-bridge'', > ''type=ioemu, mac=00:16:3e:70:00:01, bridge=xenbr2, ip=10.0.2.1, script=vif-bridge'', > ''type=ioemu, mac=00:16:3e:70:00:02, bridge=xenbr3, ip=10.23.100.13, script=vif-bridge''] > root = "UUID=94a89174-ddca-4b8c-894c-bb3b7e0c62fa ro" > extra = "xencons=tty" > on_poweroff = ''destroy'' > on_reboot = ''restart'' > on_crash = ''restart'' > > I created this domU using LVM. > > Thank you_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Andreas, what do you mean by real partition? How do you create/configure your guest domains? I could change the configuration if necessary. Thanks Andreas Sommer <AndiDog@web.de> schrieb am 30.06.2009 15:20:03: Hi again, sorry but I don''t know anything about using real partitions with Xen guests. Maybe you should make sure that it is unmounted in dom0 ?! Furthermore the modules needed to load the file system must be provided for the domU kernel (and probably inside the initrd image). I think somebody else will have to help you on that problem... Best regards elli_dberg@web.de wrote:> Hi Andreas, > > I use xen 3.4.0 and here is the configuration file for my domU: > > kernel = "/boot/vmlinuz-2.6.18.8-xen" > ramdisk = "/boot/initrd.img-2.6.18.8-xen" > memory = 128 > name = "virtualrouter1" > vif = [ ''type=ioemu, mac=00:16:3e:70:00:00, bridge=xenbr1, ip=10.0.1.1, script=vif-bridge'', > ''type=ioemu, mac=00:16:3e:70:00:01, bridge=xenbr2, ip=10.0.2.1, script=vif-bridge'', > ''type=ioemu, mac=00:16:3e:70:00:02, bridge=xenbr3, ip=10.23.100.13, script=vif-bridge''] > root = "UUID=94a89174-ddca-4b8c-894c-bb3b7e0c62fa ro" > extra = "xencons=tty" > on_poweroff = ''destroy'' > on_reboot = ''restart'' > on_crash = ''restart'' > > I created this domU using LVM. > > Thank you______________________________________________________ GRATIS für alle WEB.DE-Nutzer: Die maxdome Movie-FLAT! Jetzt freischalten unter http://movieflat.web.de _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
From your configuration I guessed that your disk will be a real partition having the UUID 94a89174-ddca-4b8c-894c-bb3b7e0c62fa (even though I don''t think it would work like that). Have I been wrong with that assumption? In fact if you just want to use a flat disk image (= one file), you would have to add the lines disk = [''file:/path/to/your/disk.img,sda1,w''] root = "/dev/sda1 ro" You may want to look at the tutorial on http://www.option-c.com/xwiki/Create_a_Debian_VM_with_debootstrap which describes how to setup a basic domU. elli_dberg@web.de wrote:> Hi Andreas, > > what do you mean by real partition? How do you create/configure your guest domains? I could change the configuration if necessary. > > Thanks > > > Andreas Sommer <AndiDog@web.de> schrieb am 30.06.2009 15:20:03: > Hi again, > > sorry but I don''t know anything about using real partitions with Xen > guests. Maybe you should make sure that it is unmounted in dom0 ?! > Furthermore the modules needed to load the file system must be provided > for the domU kernel (and probably inside the initrd image). > I think somebody else will have to help you on that problem... > > Best regards > > > elli_dberg@web.de wrote: > >> Hi Andreas, >> >> I use xen 3.4.0 and here is the configuration file for my domU: >> >> kernel = "/boot/vmlinuz-2.6.18.8-xen" >> ramdisk = "/boot/initrd.img-2.6.18.8-xen" >> memory = 128 >> name = "virtualrouter1" >> vif = [ ''type=ioemu, mac=00:16:3e:70:00:00, bridge=xenbr1, ip=10.0.1.1, script=vif-bridge'', >> ''type=ioemu, mac=00:16:3e:70:00:01, bridge=xenbr2, ip=10.0.2.1, script=vif-bridge'', >> ''type=ioemu, mac=00:16:3e:70:00:02, bridge=xenbr3, ip=10.23.100.13, script=vif-bridge''] >> root = "UUID=94a89174-ddca-4b8c-894c-bb3b7e0c62fa ro" >> extra = "xencons=tty" >> on_poweroff = ''destroy'' >> on_reboot = ''restart'' >> on_crash = ''restart'' >> >> I created this domU using LVM. >> >> Thank you >> > ______________________________________________________ > GRATIS für alle WEB.DE-Nutzer: Die maxdome Movie-FLAT! > Jetzt freischalten unter http://movieflat.web.de > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
B means blocked not booting which is fine and should be how most of the dom Us look if the resources aren''t being consumed. R means running (using resources) -----Original Message----- From: xen-users-bounces@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Stefan Kuhne Sent: 30 June 2009 12:20 To: xen-users@lists.xensource.com Subject: Re: [Xen-users] problem with xm create elli_dberg@web.de schrieb:>> >> Andreas Sommer <AndiDog@web.de> schrieb am 30.06.2009 12:53:02: >> Check if "xm list" shows you a running state ("r" for running or "b" >> for booting, "p" often means that an error occurred). I guess you >> might have forgotten the line >> >> here is the output of xm list: > > Name ID Mem VCPUs State Time(s) Domain-0 0 487 2 r----- 352.1 > virtualrouter1 2 256 1 -b---- 0.9 > > I started the virtualrouter1 already today in the morning. Does it > mean it is still booting? >All my running DomUs have state "b"! Did i need any software in domU for state "r"? Regards Stefan Kuhne _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hello,
Did you set your dom u config to use a RAM disk or are the sata drivers complied
into the kernel?
-----Original Message-----
From: xen-users-bounces@lists.xensource.com
[mailto:xen-users-bounces@lists.xensource.com] On Behalf Of elli_dberg@web.de
Sent: 30 June 2009 13:02
To: Andreas Sommer
Cc: Xen-users@lists.xensource.com
Subject: Re: [Xen-users] problem with xm create
Hi Andreas, and everyone,
I did as you said and I set extra= "xencons=tty". Now the boot precess
goes some more lines further but now there is another problem. These are the
last lines of the output of xm create -c ...
...
fuse init (API version 7.7)
Done.
Begin: Running /scripts/init-premount ...
Done.
Begin: Mounting root file system... ...
Begin: Running /scripts/local-top ...
Done.
Begin: Waiting for root file system... ...
Done.
chvt: can''t open console
chvt: VT_ACTIVATE: Bad file descriptor
Gave up waiting for root device. Common problems:
- Boot args (cat /proc/cmdline)
- Check rootdelay= (did the system wait long enough?)
- Check root= (did the system wait for the right device?)
- Missing modules (cat /proc/modules; ls /dev)
chvt: can''t open console
chvt: VT_ACTIVATE: Bad file descriptor
ALERT! /dev/sda1 does not exist. Dropping to a shell!
BusyBox v1.10.2 (Ubuntu 1:1.10.2-1ubuntu7) built-in shell (ash)
Enter ''help'' for a list of built-in commands.
(initramfs)
Does that mean that the virtual machine cannot recognize the file system? I have
a SATA hard drive and I am using the same kernel and setup as for dom0. I tried
also specifying the root device as its UUID but didn''t work neither.
Do have any idea?
Thank you
Andreas Sommer <AndiDog@web.de> schrieb am 30.06.2009 12:53:02:
Check if "xm list" shows you a running state ("r" for
running or "b" for
booting, "p" often means that an error occurred). I guess you might
have
forgotten the line
extra = ''''xencons=tty"
so the domU seems to hang because it doesn''t show the login prompt on
the correct console.
Compare to this thread:
http://lists.xensource.com/archives/html/xen-users/2009-06/msg00409.html
elli_dberg@web.de wrote:> Hi,
>
> I am having troubles starting a domU. I run it with: xm create -c
config_file. Then I can see the output and it seems as if everything is going
well. Then, the output suddenly stops without any failures and there is nothing
I can do. The cursor is blinking but not responding to any keyboard inputs. I
even cannot kill the process with ctrl+c. When I run xen-list-images it shows
the image:
> $ xen-list-images
> Name: virtualrouter1
> Memory: 128
> IP: 10.23.100.13
>
> Here is the output of xm create:
>
> Using config file "./virtualrouter1.cfg".
> Started domain virtualrouter1 (id=2)
> Bootdata ok (command line is root=/dev/sda1 ro )
> Linux version 2.6.18.8-xen (root@virtualrouter1) (gcc version 4.3.2 (Ubuntu
4.3.2-1ubuntu12) ) #2 SMP Wed Jun 24 14:11:03 CEST 2009
> BIOS-provided physical RAM map:
> Xen: 0000000000000000 - 0000000010800000 (usable)
> No mptable found.
> Built 1 zonelists. Total pages: 66660
> Kernel command line: root=/dev/sda1 ro
> Initializing CPU#0
> PID hash table entries: 2048 (order: 11, 16384 bytes)
> Xen reported: 3000.680 MHz processor.
> Console: colour dummy device 80x25
> Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
> Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
> Software IO TLB disabled
> Memory: 231424k/270336k available (2585k kernel code, 30416k reserved,
1122k data, 192k init)
> Calibrating delay using timer specific routine.. 6002.56 BogoMIPS
(lpj=30012826)
> Security Framework v1.0.0 initialized
> Capability LSM initialized
> Mount-cache hash table entries: 256
> CPU: L1 I cache: 32K, L1 D cache: 32K
> CPU: L2 cache: 6144K
> CPU: Physical Processor ID: 0
> CPU: Processor Core ID: 0
> SMP alternatives: switching to UP code
> Freeing SMP alternatives: 28k freed
> Brought up 1 CPUs
> migration_cost=0
> checking if image is initramfs... it is
> Freeing initrd memory: 20068k freed
> NET: Registered protocol family 16
> Brought up 1 CPUs
> PCI: setting up Xen PCI frontend stub
> ACPI: Interpreter disabled.
> Linux Plug and Play Support v0.97 (c) Adam Belay
> pnp: PnP ACPI: disabled
> suspend: event channel 6
> xen_mem: Initialising balloon driver.
> SCSI subsystem initialized
> PCI: System does not support PCI
> PCI: System does not support PCI
> NET: Registered protocol family 2
> IP route cache hash table entries: 4096 (order: 3, 32768 bytes)
> TCP established hash table entries: 16384 (order: 6, 262144 bytes)
> TCP bind hash table entries: 8192 (order: 5, 131072 bytes)
> TCP: Hash tables configured (established 16384 bind 8192)
> TCP reno registered
> IA-32 Microcode Update Driver: v1.14a-xen <tigran@veritas.com>
> audit: initializing netlink socket (disabled)
> audit(1246352198.193:1): initialized
> VFS: Disk quotas dquot_6.5.1
> Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
> Initializing Cryptographic API
> io scheduler noop registered
> io scheduler anticipatory registered
> io scheduler deadline registered
> io scheduler cfq registered (default)
> rtc: IRQ 8 is not free.
> Non-volatile memory driver v1.2
> RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
> loop: loaded (max 8 devices)
> e1000e: Intel(R) PRO/1000 Network Driver - 0.3.3.3-k4
> e1000e: Copyright (c) 1999-2008 Intel Corporation.
> Intel(R) Gigabit Ethernet Network Driver - version 1.2.45-k2
> Copyright (c) 2008 Intel Corporation.
> ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver - version
1.3.56.5-NAPI
> Copyright (c) 1999-2008 Intel Corporation.
> Xen virtual console successfully installed as xvc0
> Event-channel device installed.
> blktap_device_init: blktap device major 254
> blktap_ring_init: blktap ring major: 253
> netfront: Initialising virtual ethernet driver.
> vif vif-0: 2 parsing device/vif/0/mac
> vif vif-1: 2 parsing device/vif/1/mac
> vif vif-2: 2 parsing device/vif/2/mac
> Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
> ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
> st: Version 20050830, fixed bufsize 32768, s/g segs 256
> osst :I: Tape driver with OnStream support version 0.99.4
> osst :I: $Id: osst.c,v 1.73 2005/01/01 21:13:34 wriede Exp $
> aoe: aoe_init: AoE v22 initialised.
> PNP: No PS/2 controller found. Probing ports directly.
> i8042.c: No controller found.
> mice: PS/2 mouse device common for all mice
> md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
> md: bitmap version 4.39
> NET: Registered protocol family 1
> NET: Registered protocol family 17
> PCI IO multiplexer device installed.
> XENBUS: Device with no driver: device/console/0
> BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
> EDD information not available.
> Freeing unused kernel memory: 192k freed
> fuse init (API version 7.7)
>
>
> What could be the problem? Appreciate any help.
>
> Thank you,
> Elisabeth
______________________________________________________
GRATIS für alle WEB.DE-Nutzer: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://movieflat.web.de
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
> kernel = "/boot/vmlinuz-2.6.18.8-xen" > ramdisk = "/boot/initrd.img-2.6.18.8-xen" > memory = 128 > name = "virtualrouter1" > vif = [ ''type=ioemu, mac=00:16:3e:70:00:00, bridge=xenbr1, ip=10.0.1.1, script=vif-bridge'', > ''type=ioemu, mac=00:16:3e:70:00:01, bridge=xenbr2, ip=10.0.2.1, script=vif-bridge'', > ''type=ioemu, mac=00:16:3e:70:00:02, bridge=xenbr3, ip=10.23.100.13, script=vif-bridge''] > root = "UUID=94a89174-ddca-4b8c-894c-bb3b7e0c62fa ro" > extra = "xencons=tty" > on_poweroff = ''destroy'' > on_reboot = ''restart'' > on_crash = ''restart'' >Hi, in your config the disk directive is missing. It tells the domu which disk it haves and so on. If you are using lvm in the backend, it would for example like this: If the logical volume should be recognized as a harddisk: disk = [ ''phy:/dev/volumegroup/volumename,hda,w'' ] And if the volume should be just a partition: disk = [ ''phy:/dev/volumegroup/volumename,hda1,w'' ] ^ HTH Regards, Jan _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi, If I could just add something to what Elisabeth says (and to avoid opening a new thread for similar issues), I have the same kind of problem when trying to create my domUs. Here is the error popping : Begin: Waiting for root file system... ... [ 0.495098] blkfront: xvda1: barriers enabled [ 1.500021] Clocksource tsc unstable (delta = 363108584 ns) Done. Gave up waiting for root device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Check root= (did the system wait for the right device?) - Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/sda1 does not exist. Dropping to a shell! Here is the config file I use : # -*- 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.27-7-generic" # Optional ramdisk. ramdisk = "/boot/initrd.img-2.6.27-7-generic" # The domain build function. Default is ''linux''. #builder=''linux'' # Initial memory allocation (in megabytes) for the new domain. # # WARNING: Creating a domain with insufficient memory may cause out of # memory errors. The domain needs enough memory to boot kernel # and modules. Allocating less than 32MBs is not recommended. memory = 256 # A name for your domain. All domains must have different names. name = "xmtest" # 128-bit UUID for the domain. The default behavior is to generate a new UUID # on each call to ''xm create''. uuid = "06ed00fe-1162-4fc4-b5d8-11993ee4a8b9" # 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" # all vcpus run on cpus 0,2,3,5 #cpus = ["2", "3"] # VCPU0 runs on CPU2, VCPU1 runs on CPU3 # 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:/etc/xen/Ubuntu-8.04.img,hda1,w'' ] #---------------------------------------------------------------------------- # Define frame buffer device. # # By default, no frame buffer device is configured. # # To create one using the SDL backend and sensible defaults: # # vfb = [ ''sdl=1'' ] # # This uses environment variables XAUTHORITY and DISPLAY. You # can override that: # # vfb = [ ''sdl=1,xauthority=/home/bozo/.Xauthority,display=:1'' ] # # To create one using the VNC backend and sensible defaults: # # vfb = [ ''vnc=1'' ] # # The backend listens on 127.0.0.1 port 5900+N by default, where N is # the domain ID. You can override both address and N: # # vfb = [ ''vnc=1,vnclisten=127.0.0.1,vncdisplay=1'' ] # # Or you can bind the first unused port above 5900: # # vfb = [ ''vnc=1,vnclisten=0.0.0.0,vncunused=1'' ] # # You can override the password: # # vfb = [ ''vnc=1,vncpasswd=MYPASSWD'' ] # # Empty password disables authentication. Defaults to the vncpasswd # configured in xend-config.sxp. #---------------------------------------------------------------------------- # 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 = ''192.0.2.1'' # 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. # # In the event a domain stops due to a crash, you have the additional options: # # "coredump-destroy", meaning dump the crashed domain''s core and then destroy; # "coredump-restart'', meaning dump the crashed domain''s core and the restart. # # 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'' #----------------------------------------------------------------------------- # Configure PVSCSI devices: # #vscsi=[ ''PDEV, VDEV'' ] # # PDEV gives physical SCSI device to be attached to specified guest # domain by one of the following identifier format. # - XX:XX:XX:XX (4-tuples with decimal notation which shows # "host:channel:target:lun") # - /dev/sdxx or sdx # - /dev/stxx or stx # - /dev/sgxx or sgx # - result of ''scsi_id -gu -s''. # ex. # scsi_id -gu -s /block/sdb # 36000b5d0006a0000006a0257004c0000 # # VDEV gives virtual SCSI device by 4-tuples (XX:XX:XX:XX) as # which the specified guest domain recognize. # #vscsi = [ ''/dev/sdx, 0:0:0:0'' ] #=========================================================================== extra = ''xencons=tty'' Many of those things are probably totally useless, but as I did not want to make any mistake, I just modified an example config file with my own information. Any idea on what I''m doing wrong in there ? Regards -- View this message in context: http://www.nabble.com/problem-with-xm-create-tp24269649p24286296.html Sent from the Xen - User mailing list archive at Nabble.com. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Ian,
the sata drivers are compiled into the kernel.
However, I fixed the problem and I can start the guest domain with xm create.
The problem was that I have messed up something with LVM so it wasn''t
working properly. I created a new guest domain instance with loopback image and
all is fine.
Thanks to the numerous answers and help.
"Ian Tobin" <itobin@tidyhosts.com> schrieb am 30.06.2009
19:02:12:
Hello,
Did you set your dom u config to use a RAM disk or are the sata drivers complied
into the kernel?
-----Original Message-----
From: xen-users-bounces@lists.xensource.com
[mailto:xen-users-bounces@lists.xensource.com] On Behalf Of elli_dberg@web.de
Sent: 30 June 2009 13:02
To: Andreas Sommer
Cc: Xen-users@lists.xensource.com
Subject: Re: [Xen-users] problem with xm create
Hi Andreas, and everyone,
I did as you said and I set extra= "xencons=tty". Now the boot precess
goes some more lines further but now there is another problem. These are the
last lines of the output of xm create -c ...
...
fuse init (API version 7.7)
Done.
Begin: Running /scripts/init-premount ...
Done.
Begin: Mounting root file system... ...
Begin: Running /scripts/local-top ...
Done.
Begin: Waiting for root file system... ...
Done.
chvt: can''t open console
chvt: VT_ACTIVATE: Bad file descriptor
Gave up waiting for root device. Common problems:
- Boot args (cat /proc/cmdline)
- Check rootdelay= (did the system wait long enough?)
- Check root= (did the system wait for the right device?)
- Missing modules (cat /proc/modules; ls /dev)
chvt: can''t open console
chvt: VT_ACTIVATE: Bad file descriptor
ALERT! /dev/sda1 does not exist. Dropping to a shell!
BusyBox v1.10.2 (Ubuntu 1:1.10.2-1ubuntu7) built-in shell (ash)
Enter ''help'' for a list of built-in commands.
(initramfs)
Does that mean that the virtual machine cannot recognize the file system? I have
a SATA hard drive and I am using the same kernel and setup as for dom0. I tried
also specifying the root device as its UUID but didn''t work neither.
Do have any idea?
Thank you
Andreas Sommer <AndiDog@web.de> schrieb am 30.06.2009 12:53:02:
Check if "xm list" shows you a running state ("r" for
running or "b" for
booting, "p" often means that an error occurred). I guess you might
have
forgotten the line
extra = ''''xencons=tty"
so the domU seems to hang because it doesn''t show the login prompt on
the correct console.
Compare to this thread:
http://lists.xensource.com/archives/html/xen-users/2009-06/msg00409.html
elli_dberg@web.de wrote:> Hi,
>
> I am having troubles starting a domU. I run it with: xm create -c
config_file. Then I can see the output and it seems as if everything is going
well. Then, the output suddenly stops without any failures and there is nothing
I can do. The cursor is blinking but not responding to any keyboard inputs. I
even cannot kill the process with ctrl+c. When I run xen-list-images it shows
the image:
> $ xen-list-images
> Name: virtualrouter1
> Memory: 128
> IP: 10.23.100.13
>
> Here is the output of xm create:
>
> Using config file "./virtualrouter1.cfg".
> Started domain virtualrouter1 (id=2)
> Bootdata ok (command line is root=/dev/sda1 ro )
> Linux version 2.6.18.8-xen (root@virtualrouter1) (gcc version 4.3.2 (Ubuntu
4.3.2-1ubuntu12) ) #2 SMP Wed Jun 24 14:11:03 CEST 2009
> BIOS-provided physical RAM map:
> Xen: 0000000000000000 - 0000000010800000 (usable)
> No mptable found.
> Built 1 zonelists. Total pages: 66660
> Kernel command line: root=/dev/sda1 ro
> Initializing CPU#0
> PID hash table entries: 2048 (order: 11, 16384 bytes)
> Xen reported: 3000.680 MHz processor.
> Console: colour dummy device 80x25
> Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
> Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
> Software IO TLB disabled
> Memory: 231424k/270336k available (2585k kernel code, 30416k reserved,
1122k data, 192k init)
> Calibrating delay using timer specific routine.. 6002.56 BogoMIPS
(lpj=30012826)
> Security Framework v1.0.0 initialized
> Capability LSM initialized
> Mount-cache hash table entries: 256
> CPU: L1 I cache: 32K, L1 D cache: 32K
> CPU: L2 cache: 6144K
> CPU: Physical Processor ID: 0
> CPU: Processor Core ID: 0
> SMP alternatives: switching to UP code
> Freeing SMP alternatives: 28k freed
> Brought up 1 CPUs
> migration_cost=0
> checking if image is initramfs... it is
> Freeing initrd memory: 20068k freed
> NET: Registered protocol family 16
> Brought up 1 CPUs
> PCI: setting up Xen PCI frontend stub
> ACPI: Interpreter disabled.
> Linux Plug and Play Support v0.97 (c) Adam Belay
> pnp: PnP ACPI: disabled
> suspend: event channel 6
> xen_mem: Initialising balloon driver.
> SCSI subsystem initialized
> PCI: System does not support PCI
> PCI: System does not support PCI
> NET: Registered protocol family 2
> IP route cache hash table entries: 4096 (order: 3, 32768 bytes)
> TCP established hash table entries: 16384 (order: 6, 262144 bytes)
> TCP bind hash table entries: 8192 (order: 5, 131072 bytes)
> TCP: Hash tables configured (established 16384 bind 8192)
> TCP reno registered
> IA-32 Microcode Update Driver: v1.14a-xen <tigran@veritas.com>
> audit: initializing netlink socket (disabled)
> audit(1246352198.193:1): initialized
> VFS: Disk quotas dquot_6.5.1
> Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
> Initializing Cryptographic API
> io scheduler noop registered
> io scheduler anticipatory registered
> io scheduler deadline registered
> io scheduler cfq registered (default)
> rtc: IRQ 8 is not free.
> Non-volatile memory driver v1.2
> RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
> loop: loaded (max 8 devices)
> e1000e: Intel(R) PRO/1000 Network Driver - 0.3.3.3-k4
> e1000e: Copyright (c) 1999-2008 Intel Corporation.
> Intel(R) Gigabit Ethernet Network Driver - version 1.2.45-k2
> Copyright (c) 2008 Intel Corporation.
> ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver - version
1.3.56.5-NAPI
> Copyright (c) 1999-2008 Intel Corporation.
> Xen virtual console successfully installed as xvc0
> Event-channel device installed.
> blktap_device_init: blktap device major 254
> blktap_ring_init: blktap ring major: 253
> netfront: Initialising virtual ethernet driver.
> vif vif-0: 2 parsing device/vif/0/mac
> vif vif-1: 2 parsing device/vif/1/mac
> vif vif-2: 2 parsing device/vif/2/mac
> Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
> ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
> st: Version 20050830, fixed bufsize 32768, s/g segs 256
> osst :I: Tape driver with OnStream support version 0.99.4
> osst :I: $Id: osst.c,v 1.73 2005/01/01 21:13:34 wriede Exp $
> aoe: aoe_init: AoE v22 initialised.
> PNP: No PS/2 controller found. Probing ports directly.
> i8042.c: No controller found.
> mice: PS/2 mouse device common for all mice
> md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
> md: bitmap version 4.39
> NET: Registered protocol family 1
> NET: Registered protocol family 17
> PCI IO multiplexer device installed.
> XENBUS: Device with no driver: device/console/0
> BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
> EDD information not available.
> Freeing unused kernel memory: 192k freed
> fuse init (API version 7.7)
>
>
> What could be the problem? Appreciate any help.
>
> Thank you,
> Elisabeth
______________________________________________________
GRATIS für alle WEB.DE-Nutzer: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://movieflat.web.de
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users