G Crowe
2013-Oct-13 11:46 UTC
First time xen install - Xen DomU runs, but can''t find "/dev/root"
I''m trying to get started with Xen and thought I''d do a simple install Fedora 18 as a DomU under a Fedora 18 Dom0. Unfortunately this is not working for me. It appears to boot the kernel fine, but then complains that it can''t find "/dev/root". I presume that this would be a specific root image for the Fedora installer? Can someone please let me know what I am doing wrong? (details of what I am trying are below). Also, I had to manually start "xend" to get this far. Is this normal? It didn''t appear in the services in /etc/rc.d/init.d. Thank you I created a 20GB logical volume /dev/fedora_dhcp1/xen1 I mounted the Fedora 18 installation ISO into /mnt/install (-t iso9660 -o loop,ro) I created the Xen DomU instance using the following command... # virt-install --paravirt --name xen1 --ram 256 --vcpus 1 -f /dev/fedora_dhcp1/xen1 --network bridge=br0 --location /mnt/install --graphics none The DomU seems to load the kernel fine (it comes up with all the usual kernel messages) but then drops to emergency mode saying that it could not boot. The last few lines from the console are as follows... [ 8.304193] Initialising Xen virtual ethernet driver. [ 8.358337] blkfront: xvda: flush diskcache: enabled [ 8.457020] xvda: unknown partition table [ OK ] Started Show Plymouth Boot Screen. [ OK ] Reached target Basic System. dracut-initqueue[276]: Warning: Could not boot. [ OK ] Started Show Plymouth Boot Screen. [ OK ] Reached target Basic System. dracut-initqueue[276]: Warning: Could not boot. dracut-initqueue[276]: Warning: /dev/root does not exist Entering emergency mode. Exit the shell to continue. Type "journalctl" to view system logs. dracut:/#
Ian Campbell
2013-Oct-14 11:59 UTC
Re: First time xen install - Xen DomU runs, but can''t find "/dev/root"
On Sun, 2013-10-13 at 22:46 +1100, G Crowe wrote:> I''m trying to get started with Xen and thought I''d do a simple install > Fedora 18 as a DomU under a Fedora 18 Dom0. Unfortunately this is not > working for me. > > It appears to boot the kernel fine, but then complains that it can''t > find "/dev/root". I presume that this would be a specific root image for > the Fedora installer?/dev/root is a device node which corresponds to whichever device contains the root filesystem. It''s a bit special but not specific to Fedora.> Can someone please let me know what I am doing wrong? (details of what I > am trying are below). > > Also, I had to manually start "xend" to get this far. Is this normal? It > didn''t appear in the services in /etc/rc.d/init.d. > > > Thank you > > > I created a 20GB logical volume /dev/fedora_dhcp1/xen1 > I mounted the Fedora 18 installation ISO into /mnt/install (-t iso9660 > -o loop,ro) > I created the Xen DomU instance using the following command... > # virt-install --paravirt --name xen1 --ram 256 --vcpus 1 -f > /dev/fedora_dhcp1/xen1 --network bridge=br0 --location /mnt/install > --graphics none > > The DomU seems to load the kernel fine (it comes up with all the usual > kernel messages) but then drops to emergency mode saying that it could > not boot. The last few lines from the console are as follows...It''s generally better to provide the entire log. There may be something useful in there.> > [ 8.304193] Initialising Xen virtual ethernet driver. > [ 8.358337] blkfront: xvda: flush diskcache: enabled > [ 8.457020] xvda: unknown partition table > [ OK ] Started Show Plymouth Boot Screen. > [ OK ] Reached target Basic System. > dracut-initqueue[276]: Warning: Could not boot. > [ OK ] Started Show Plymouth Boot Screen. > [ OK ] Reached target Basic System. > dracut-initqueue[276]: Warning: Could not boot. > dracut-initqueue[276]: Warning: /dev/root does not existWhat was your root= on the kernel command line?> > > Entering emergency mode. Exit the shell to continue. > Type "journalctl" to view system logs. > > dracut:/# > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users
G Crowe
2013-Oct-15 20:22 UTC
Re: First time xen install - Xen DomU runs, but can''t find "/dev/root"
Ian,
Thanks for your response, answers are below.
On 14/10/2013 10:59 PM, Ian Campbell wrote:> On Sun, 2013-10-13 at 22:46 +1100, G Crowe wrote:
> It''s generally better to provide the entire log. There may be
> something useful in there.
OK, the entire log is at the end of the email.> What was your root= on the kernel command line?
The logs have the following line, I presume it means that there was
nothing on the kernel command line...
[ 0.000000] Kernel command line:
I also tried "cat /proc/cmdline" from the emergency shell and it had
nothing.
I have no idea what should be here. I was under the impression that this
sort of thing should be taken care of by either the virt-install
program, or the Fedora18 DVD image that I was pointing it to.
Thank you
**** Full output below...
[root@dhcp1 ~]# virt-install --paravirt --name xen1 --ram 256 --vcpus 1
-f /dev/fedora_dhcp1/xen1 --network bridge=br0 --location /mnt/install
--graphics none
Starting install...
Retrieving file .treeinfo... | 2.4 kB 00:00:00 !!!
Retrieving file vmlinuz-PAE... | 9.3 MB 00:00:00 !!!
Retrieving file initrd-PAE.img... | 52 MB 00:00:00 !!!
Creating domain... | 0 B 00:00:01
Connected to domain xen1
Escape character is ^] [ 0.000000] Reserving virtual address space
above 0xf5800000
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 3.6.10-4.fc18.i686.PAE (mockbuild@) (gcc
version 4.7.2 20121109 (Red Hat 4.7.2-8) (GCC) ) #1 SMP Tue Dec 11
18:15:08 UTC 2012
[ 0.000000] ACPI in unprivileged domain disabled
[ 0.000000] e820: BIOS-provided physical RAM map:
[ 0.000000] Xen: [mem 0x0000000000000000-0x000000000009ffff] usable
[ 0.000000] Xen: [mem 0x00000000000a0000-0x00000000000fffff] reserved
[ 0.000000] Xen: [mem 0x0000000000100000-0x00000000107fffff] usable
[ 0.000000] NX (Execute Disable) protection: active
[ 0.000000] DMI not present or invalid.
[ 0.000000] e820: last_pfn = 0x10800 max_arch_pfn = 0x1000000
[ 0.000000] init_memory_mapping: [mem 0x00000000-0x107fffff]
[ 0.000000] RAMDISK: [mem 0x0102f000-0x02a6cfff]
[ 0.000000] 0MB HIGHMEM available.
[ 0.000000] 264MB LOWMEM available.
[ 0.000000] mapped low ram: 0 - 10800000
[ 0.000000] low ram: 0 - 10800000
[ 0.000000] Zone ranges:
[ 0.000000] DMA [mem 0x00010000-0x00ffffff]
[ 0.000000] Normal [mem 0x01000000-0x107fffff]
[ 0.000000] HighMem empty
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x00010000-0x0009ffff]
[ 0.000000] node 0: [mem 0x00100000-0x107fffff]
[ 0.000000] Using APIC driver default
[ 0.000000] SFI: Simple Firmware Interface v0.81
http://simplefirmware.org
[ 0.000000] smpboot: Allowing 1 CPUs, 0 hotplug CPUs
[ 0.000000] Local APIC disabled by BIOS -- you can enable it with
"lapic"
[ 0.000000] APIC: disable apic facility
[ 0.000000] APIC: switched to apic NOOP
[ 0.000000] PM: Registered nosave memory: 00000000000a0000 -
0000000000100000
[ 0.000000] e820: [mem 0x10800000-0xffffffff] available for PCI devices
[ 0.000000] Booting paravirtualized kernel on Xen
[ 0.000000] Xen version: 4.2.2 (preserve-AD)
[ 0.000000] setup_percpu: NR_CPUS:32 nr_cpumask_bits:32 nr_cpu_ids:1
nr_node_ids:1
[ 0.000000] PERCPU: Embedded 14 pages/cpu @cfdde000 s34880 r0 d22464
u57344
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on.
Total pages: 66944
[ 0.000000] Kernel command line:
[ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144
bytes)
[ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072
bytes)
[ 0.000000] __ex_table already sorted, skipping sort
[ 0.000000] Initializing CPU#0
[ 0.000000] allocated 540544 bytes of page_cgroup
[ 0.000000] please try ''cgroup_disable=memory'' option if
you don''t
want memory cgroups
[ 0.000000] Initializing HighMem for node 0 (00000000:00000000)
[ 0.000000] Memory: 220784k/270336k available (5639k kernel code,
49104k reserved, 2745k data, 656k init, 0k highmem)
[ 0.000000] virtual kernel memory layout:
[ 0.000000] fixmap : 0xf5296000 - 0xf57ff000 (5540 kB)
[ 0.000000] pkmap : 0xf4e00000 - 0xf5000000 (2048 kB)
[ 0.000000] vmalloc : 0xd1000000 - 0xf4dfe000 ( 573 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xd0800000 ( 264 MB)
[ 0.000000] .init : 0xc0c31000 - 0xc0cd5000 ( 656 kB)
[ 0.000000] .data : 0xc0981f81 - 0xc0c30640 (2745 kB)
[ 0.000000] .text : 0xc0400000 - 0xc0981f81 (5639 kB)
[ 0.000000] SLUB: Genslabs=15, HWalign=128, Order=0-3, MinObjects=0,
CPUs=1, Nodes=1
[ 0.000000] Hierarchical RCU implementation.
[ 0.000000] RCU restricting CPUs from NR_CPUS=32 to nr_cpu_ids=1.
[ 0.000000] NR_IRQS:2304 nr_irqs:256 16
[ 0.000000] Console: colour dummy device 80x25
[ 0.000000] console [tty0] enabled
[ 0.000000] console [hvc0] enabled
[ 0.000000] installing Xen timer for CPU 0
[ 0.000000] tsc: Detected 3192.140 MHz processor
[ 0.000999] Calibrating delay loop (skipped), value calculated using
timer frequency.. 6384.28 BogoMIPS (lpj=3192140)
[ 0.000999] pid_max: default: 32768 minimum: 301
[ 0.000999] Security Framework initialized
[ 0.000999] SELinux: Initializing.
[ 0.000999] Mount-cache hash table entries: 512
[ 0.000999] Initializing cgroup subsys cpuacct
[ 0.000999] Initializing cgroup subsys memory
[ 0.000999] Initializing cgroup subsys devices
[ 0.000999] Initializing cgroup subsys freezer
[ 0.000999] Initializing cgroup subsys net_cls
[ 0.000999] Initializing cgroup subsys blkio
[ 0.000999] Initializing cgroup subsys perf_event
[ 0.000999] CPU: Physical Processor ID: 0
[ 0.000999] CPU: Processor Core ID: 0
[ 0.000999] Last level iTLB entries: 4KB 64, 2MB 64, 4MB 64
[ 0.000999] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 64
[ 0.000999] tlb_flushall_shift is 0x6
[ 0.001032] SMP alternatives: switching to UP code
[ 0.081199] Freeing SMP alternatives: 24k freed
[ 0.081250] ftrace: allocating 23058 entries in 46 pages
[ 0.090144] Performance Events: unsupported Netburst CPU model 4 no
PMU driver, software events only.
[ 0.091214] NMI watchdog: disabled (cpu0): hardware events not enabled
[ 0.091321] Brought up 1 CPUs
[ 0.091630] devtmpfs: initialized
[ 0.093188] atomic64 test passed for i586+ platform with CX8 and with SSE
[ 0.093282] Grant tables using version 2 layout.
[ 0.093359] Grant table initialized
[ 0.111982] RTC time: 165:165:165, date: 165/165/65
[ 0.112096] NET: Registered protocol family 16
[ 0.113006] PCI: setting up Xen PCI frontend stub
[ 0.114351] bio: create slab <bio-0> at 0
[ 0.114467] ACPI: Interpreter disabled.
[ 0.114509] xen/balloon: Initialising balloon driver.
[ 0.116027] xen-balloon: Initialising balloon driver.
[ 0.116153] vgaarb: loaded
[ 0.116362] SCSI subsystem initialized
[ 0.116594] usbcore: registered new interface driver usbfs
[ 0.116620] usbcore: registered new interface driver hub
[ 0.117036] usbcore: registered new device driver usb
[ 0.117254] PCI: System does not support PCI
[ 0.117271] PCI: System does not support PCI
[ 0.117461] NetLabel: Initializing
[ 0.117473] NetLabel: domain hash size = 128
[ 0.117481] NetLabel: protocols = UNLABELED CIPSOv4
[ 0.117501] NetLabel: unlabeled traffic allowed by default
[ 0.117528] Switching to clocksource xen
[ 0.128867] pnp: PnP ACPI: disabled
[ 0.131836] NET: Registered protocol family 2
[ 0.132040] TCP established hash table entries: 16384 (order: 5,
131072 bytes)
[ 0.132148] TCP bind hash table entries: 16384 (order: 5, 131072 bytes)
[ 0.132223] TCP: Hash tables configured (established 16384 bind 16384)
[ 0.132256] TCP: reno registered
[ 0.132266] UDP hash table entries: 256 (order: 1, 8192 bytes)
[ 0.132280] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[ 0.132359] NET: Registered protocol family 1
[ 0.132609] Unpacking initramfs...
[ 5.400424] Freeing initrd memory: 26872k freed
[ 5.420100] platform rtc_cmos: registered platform RTC device (no PNP
device found)
[ 5.420423] apm: BIOS not found.
[ 5.420790] Initialise module verification
[ 5.420887] audit: initializing netlink socket (disabled)
[ 5.420926] type=2000 audit(1381867979.607:1): initialized
[ 5.443018] HugeTLB registered 2 MB page size, pre-allocated 0 pages
[ 5.445007] VFS: Disk quotas dquot_6.5.2
[ 5.445162] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 5.445893] msgmni has been set to 483
[ 5.447183] alg: No test for stdrng (krng)
[ 5.447213] NET: Registered protocol family 38
[ 5.447231] Key type asymmetric registered
[ 5.447245] Asymmetric key parser ''x509'' registered
[ 5.447349] Block layer SCSI generic (bsg) driver version 0.4 loaded
(major 252)
[ 5.447457] io scheduler noop registered
[ 5.447476] io scheduler deadline registered
[ 5.447512] io scheduler cfq registered (default)
[ 5.447736] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[ 5.447789] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
[ 5.447805] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
[ 5.448701] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[ 5.449418] Non-volatile memory driver v1.3
[ 5.449436] Linux agpgart interface v0.103
[ 5.450770] loop: module loaded
[ 5.451003] libphy: Fixed MDIO Bus: probed
[ 5.451195] ehci_hcd: USB 2.0 ''Enhanced'' Host Controller
(EHCI) Driver
[ 5.451245] ohci_hcd: USB 1.1 ''Open'' Host Controller (OHCI)
Driver
[ 5.451283] uhci_hcd: USB Universal Host Controller Interface driver
[ 5.451406] usbcore: registered new interface driver usbserial
[ 5.451447] usbcore: registered new interface driver usbserial_generic
[ 5.451483] USB Serial support registered for generic
[ 5.451500] usbserial: USB Serial Driver core
[ 5.451563] i8042: PNP: No PS/2 controller found. Probing ports directly.
[ 5.452551] mousedev: PS/2 mouse device common for all mice
[ 5.512978] rtc_cmos rtc_cmos: rtc core: registered rtc_cmos as rtc0
[ 5.513129] rtc_cmos: probe of rtc_cmos failed with error -38
[ 5.513270] device-mapper: uevent: version 1.0.3
[ 5.513381] device-mapper: ioctl: 4.23.0-ioctl (2012-07-25)
initialised: dm-devel@redhat.com
[ 5.513464] EFI Variables Facility v0.08 2004-May-17
[ 5.513641] usbcore: registered new interface driver usbhid
[ 5.513652] usbhid: USB HID core driver
[ 5.513686] drop_monitor: Initializing network drop monitor service
[ 5.513818] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 5.513897] TCP: cubic registered
[ 5.513907] Initializing XFRM netlink socket
[ 5.514097] NET: Registered protocol family 10
[ 5.514332] mip6: Mobile IPv6
[ 5.514343] NET: Registered protocol family 17
[ 5.514370] Using IPI No-Shortcut mode
[ 5.514529] Loading module verification certificates
[ 5.519112] MODSIGN: Loaded cert ''Fedora kernel signing key:
de2965de66714570abd7e5852342fe03dd0c1ba7''
[ 5.519152] registered taskstats version 1
[ 5.519178] XENBUS: Device with no driver: device/vbd/51712
[ 5.519189] XENBUS: Device with no driver: device/vif/0
[ 5.519272] Magic number: 1:252:3141
[ 5.519319] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[ 5.519873] Freeing unused kernel memory: 656k freed
[ 5.523151] Write protecting the kernel text: 5640k
[ 5.524299] Write protecting the kernel read-only data: 2212k
[ 5.524315] NX-protecting the kernel data: 4600k
[ 5.533912] systemd[1]: systemd 195 running in system mode. (+PAM
+LIBWRAP +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ;
fedora)
[ 5.534049] systemd[1]: Running in initial RAM disk.
Welcome to Fedora 18 (Spherical Cow) dracut-024-18.git20130102.fc18
(Initramfs)!
[ 5.534462] systemd[1]: No hostname configured.
[ 5.534488] systemd[1]: Set hostname to <localhost>.
[ 5.534651] systemd[1]: Initializing machine ID from random generator.
[ 5.561666] systemd[1]: Starting Encrypted Volumes.
[ OK ] Reached target Encrypted Volumes.
[ 5.601607] systemd[1]: Reached target Encrypted Volumes.
[ 5.601835] systemd[1]: Starting udev Kernel Socket.
[ OK ] Listening on udev Kernel Socket.
[ 5.602206] systemd[1]: Listening on udev Kernel Socket.
[ 5.602403] systemd[1]: Starting udev Control Socket.
[ OK ] Listening on udev Control Socket.
[ 5.602748] systemd[1]: Listening on udev Control Socket.
[ 5.602819] systemd[1]: Starting Journal Socket.
[ OK ] Listening on Journal Socket.
[ 5.603217] systemd[1]: Listening on Journal Socket.
[ 5.603297] systemd[1]: Starting dracut cmdline hook...
Starting dracut cmdline hook...
[ 5.605425] systemd[1]: Started Load Kernel Modules.
[ 5.605554] systemd[1]: Starting Journal Service...
Starting Journal Service...
[ OK ] Started Journal Service.
[ 5.648995] systemd[1]: Started Journal Service.
[ 5.651273] systemd[1]: Starting Sockets.
[ OK ] Reached target Sockets.
[ 5.651494] systemd[1]: Reached target Sockets.
[ 5.651570] systemd[1]: Starting Swap.
[ OK ] Reached target Swap.
[ 5.651769] systemd[1]: Reached target Swap.
[ 5.651850] systemd[1]: Starting Local File Systems.
[ OK ] Reached target Local File Systems.
[ 5.652027] systemd[1]: Reached target Local File Systems.
[ 6.009250] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
[ 6.009278] EDD information not available.
[ OK ] Started dracut cmdline hook.
Starting Setup Virtual Console...
Starting dracut pre-udev hook...
[ OK ] Started Setup Virtual Console.
[ OK ] Reached target System Initialization.
[ 6.726690] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 6.737807] Loading iSCSI transport class v2.0-870.
[ 6.754446] iscsi: registered transport (tcp)
[ 6.764264] alua: device handler registered
[ 6.773860] emc: device handler registered
[ 6.783584] hp_sw: device handler registered
[ 6.793520] rdac: device handler registered
[ 6.805629] Floppy drive(s): fd0 is unknown type 15 (usb?), fd1 is
unknown type 15 (usb?)
[ 6.805674] floppy0: Unable to grab IRQ6 for the floppy driver
[ 6.816022] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
[ 6.816054] EDD information not available.
[ 6.830877] No iBFT detected.
[ 6.840605] md: raid0 personality registered for level 0
[ 6.852284] md: raid1 personality registered for level 1
[ 6.862087] async_tx: api initialized (async)
[ 6.867605] xor: automatically using best checksumming function:
[ 6.877077] pIII_sse : 1932.000 MB/sec
[ 6.905090] raid6: mmxx1 1863 MB/s
[ 6.922093] raid6: mmxx2 2136 MB/s
[ 6.939094] raid6: sse1x1 1066 MB/s
[ 6.956097] raid6: sse1x2 2078 MB/s
[ 6.973082] raid6: sse2x1 2164 MB/s
[ 6.990076] raid6: sse2x2 3160 MB/s
[ 6.990093] raid6: using algorithm sse2x2 (3160 MB/s)
[ 6.990109] raid6: using intx1 recovery algorithm
[ 7.016396] md: raid6 personality registered for level 6
[ 7.016421] md: raid5 personality registered for level 5
[ 7.016438] md: raid4 personality registered for level 4
[ 7.037861] md: raid10 personality registered for level 10
[ 7.048264] md: linear personality registered for level -1
[ 7.076403] device-mapper: multipath: version 1.5.0 loaded
[ 7.086880] device-mapper: multipath round-robin: version 1.0.0 loaded
[ 7.229246] RPC: Registered named UNIX socket transport module.
[ 7.229270] RPC: Registered udp transport module.
[ 7.229279] RPC: Registered tcp transport module.
[ 7.229287] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ OK ] Started dracut pre-udev hook.
Starting udev Kernel Device Manager...
[ OK ] Started udev Kernel Device Manager.
Starting dracut pre-trigger hook...
[ 7.560135] systemd-udevd[225]: starting version 195
[ OK ] Started dracut pre-trigger hook.
Starting udev Coldplug all Devices...
[ OK ] Started udev Coldplug all Devices.
Starting Show Plymouth Boot Screen...
Starting dracut initqueue hook...
[ 8.228185] Disabling lock debugging due to kernel taint
[ 8.230621] Initialising Xen virtual ethernet driver.
[ 8.263474] blkfront: xvda: flush diskcache: enabled
[ 8.293282] xvda: unknown partition table
[ OK ] Started Show Plymouth Boot Screen.
[ OK ] Reached target Basic System.
dracut-initqueue[278]: Warning: Could not boot.
[ OK ] Started Show Plymouth Boot Screen.
[ OK ] Reached target Basic System.
dracut-initqueue[278]: Warning: Could not boot.
dracut-initqueue[278]: Warning: /dev/root does not exist
Entering emergency mode. Exit the shell to continue.
Type "journalctl" to view system logs.
dracut:/#
dracut:/# cat /proc/cmdline
dracut:/#
We failed to setup the serial port in the Xen full virtualization. Appreciate any suggestions or telling us how to correctly config Xen device or others. -SYZH
Niels Dettenbach (Syndicat.com)
2013-Oct-16 05:55 UTC
Re: Xen Full Virtualization Support Serial Port?
Yuzhong Sun <yuzhongsun@ict.ac.cn> schrieb:>We failed to setup the serial port in the Xen full virtualization.pls send your DomU and Dom0 config plus DomU /etc/inittab and log errors (if there are any) after a xm console yourdomu. Usually in 4.x versions it is enough to change the first serial console in your DomUs: - /etc/inittab to xvhc (or similiar) and to bring out early boot messages to the xenconsole you should have a - kernel parameter like console=xvhc (or similiar) i.e. in DomU config. Does not have it completely in mind att and i''m just on a phone, will check this back later if you send in your configs. And if im right from mind too, xenconsoled has to be running too. This may differ a bit from OS to OS. cheers, Niels. -- Niels Dettenbach Syndicat IT&Internet http://www.syndicat.com
Please don''t hijack existing thread. On Wed, Oct 16, 2013 at 11:29:06AM +0800, Yuzhong Sun wrote:> We failed to setup the serial port in the Xen full virtualization. > > Appreciate any suggestions or telling us how to correctly config Xen device or others. >You could find guide on how to setup serial console on wiki.xen.org Wei.> -SYZH > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users
Ian Campbell
2013-Oct-16 13:15 UTC
Re: First time xen install - Xen DomU runs, but can''t find "/dev/root"
On Wed, 2013-10-16 at 07:22 +1100, G Crowe wrote:> Ian, > Thanks for your response, answers are below. > > > On 14/10/2013 10:59 PM, Ian Campbell wrote: > > On Sun, 2013-10-13 at 22:46 +1100, G Crowe wrote: > > It''s generally better to provide the entire log. There may be > > something useful in there. > OK, the entire log is at the end of the email. > > What was your root= on the kernel command line? > The logs have the following line, I presume it means that there was > nothing on the kernel command line... > [ 0.000000] Kernel command line: > I also tried "cat /proc/cmdline" from the emergency shell and it had > nothing. > > I have no idea what should be here. I was under the impression that this > sort of thing should be taken care of by either the virt-install > program, or the Fedora18 DVD image that I was pointing it to.Me too, although I know almost nothing about either myself. With that in mind you might want to speak to the virt-install and/or Fedora18 people. IIRC there is a fedora-virt list where Xen questions are welcomed. I see from your log that your command line is empty, which doesn''t seem right. I''m afraid I don''t know what virt-install rune would fix that, or indeed if it should even be necessary. If you can figure out how to append "root=/dev/xvda" to the command line you may find that does the trick. Ian.
Dario Faggioli
2013-Oct-18 08:07 UTC
Re: First time xen install - Xen DomU runs, but can''t find "/dev/root"
On mer, 2013-10-16 at 14:15 +0100, Ian Campbell wrote:> On Wed, 2013-10-16 at 07:22 +1100, G Crowe wrote: > > I have no idea what should be here. I was under the impression that this > > sort of thing should be taken care of by either the virt-install > > program, or the Fedora18 DVD image that I was pointing it to. > > Me too, although I know almost nothing about either myself. With that in > mind you might want to speak to the virt-install and/or Fedora18 people. > IIRC there is a fedora-virt list where Xen questions are welcomed. >Hi, Sorry I''m replying only now (I''ve been ill for a couple of days). So, how''s this going? Any more luck? Can I point out to some resources we have that are related right to what you seem to be after? http://wiki.xen.org/wiki/Fedora_Host_Installation http://wiki.xenproject.org/wiki/DomU_Install_with_Virt-Install http://wiki.xen.org/wiki/Fedora_Test_Days http://blog.xen.org/index.php/2013/10/16/fedora-virtualization-test-day-report/ In particular, the last two links (Test Days and the blog post) are something I went through myself last week, so I''m quite sure they''re updated and accurate enough. In your first e-mail you say you did something like the following: # virt-install --paravirt --name xen1 --ram 256 --vcpus 1 -f /dev/fedora_dhcp1/xen1 --network bridge=br0 --location /mnt/install --graphics none after mounting the install ISO in /mnt/install. I''ve actually never done such a thing. If you wanted and HVM guest, I''d say to try providing virt-install with the ISO directly (something like ''--cdrom <xxx>.iso''. It''s probably not on the blog post, but I did it with a Fedora 20 install DVD image and it worked. For ''--paravirt'' I usually point ''--location'' to an URL from where it can fetch and perform a network install (and that _is_ in the blog post :-)), and it pretty much always worked. Can you do that?> I see from your log that your command line is empty, which doesn''t seem > right. I''m afraid I don''t know what virt-install rune would fix that, or > indeed if it should even be necessary. If you can figure out how to > append "root=/dev/xvda" to the command line you may find that does the > trick. >There''s a ''--extra-args'' switch which should, if used properly, do what''s needed here, but I''m not use how to set it up properly in this case (install iso mounted). Regards, Dario -- <<This happens because I choose it to happen!>> (Raistlin Majere) ----------------------------------------------------------------- Dario Faggioli, Ph.D, http://about.me/dario.faggioli Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK) _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
G Crowe
2013-Oct-21 05:15 UTC
Re: First time xen install - Xen DomU runs, but can''t find "/dev/root"
OK, I have managed to get it largely working, thank you for your assistance. - Virt-install using a CD image on a local filesystem loads the kernel and initrd correctly, but doesn''t load the /root correctly from the CD. I never figured out how to do this, but /dev/xvda was the virtual disc that I was trying to install onto (and therefore was empty and wouldn''t act as a root filesystem). It is possible that the --extra-args option may be used to fix this, but I have mine working now and am unlikely to spend too much more time trying. - I managed to install it by setting up a web server on another machine, and mounted the install CD into the web server''s /var/www/html/f18 directory. Thank you Dario for the references to the test day where all their installs were via the network (although they use PXE, which I have no experience in) - I tried this after noticing that the pros didn''t use the local filesystems for installs. - 256MB of RAM is insufficient to install F18 in text mode. I had to increase it to 512MB. With 256MB I was getting pages of out of memory errors and the install would fail. - One of the first things I tried was the --cdrom option, however this requires HVM which my current CPU does not support. - I am still having issues with the xl toolchain. Firstly, when used to install, it would bomb out with an error when it went to connect to the new console (immediately connecting to the console manually would work). Secondly it wouldn''t recognise DomUs as being deleted and would not allow me to recreate them "ERROR Guest name ''xen1'' is already in use.". If I manually started xend, both of these problems would disappear without changing the virt-install command. Maybe if I updated my software then this problem would go away (unfortunately this machine doesn''t have a direct connection to the internet - hence me using install DVD images rather than remote URLs). - For the record, the command I used to install successfully from the console was virt-install --paravirt --name xen1 --ram 512 --vcpus 1 -f /dev/fedora_dhcp1/xen1 --network bridge=br0 --location http://www.example.com/f18 --graphics none Thanks all for your help - you''ve now got me to a stage where I can ''fiddle'' around myself. Thank you Graham Crowe
Dario Faggioli
2013-Oct-21 06:28 UTC
Re: First time xen install - Xen DomU runs, but can''t find "/dev/root"
On lun, 2013-10-21 at 16:15 +1100, G Crowe wrote:> OK, I have managed to get it largely working, thank you for your assistance. >You''re welcome... Glad we helped.> - I managed to install it by setting up a web server on another machine, > and mounted the install CD into the web server''s /var/www/html/f18 > directory. Thank you Dario for the references to the test day where all > their installs were via the network (although they use PXE, which I have > no experience in) - I tried this after noticing that the pros didn''t use > the local filesystems for installs. >Well, yes, in the blog post I mention setting up a PXE server, but that is for _installing_ _Dom0_. For guests, you really don''t need one, you can just point your --location to an URL and that''s it! I recommend you trying... It at least look easier than using a local webserver, etc. Anyway, again, I''m glad the blog post was useful.> - I am still having issues with the xl toolchain. >Sorry, do you mean ''plain xl'' here (i.e., using xl directly by issuing `xl ...'' commands) or the libvirt libxl driver?> Firstly, when used to > install, it would bomb out with an error when it went to connect to the > new console (immediately connecting to the console manually would work). >Mmm... I don''t think I''ve ever seen that, can you be a little more specific? What is it that happens? When?> Secondly it wouldn''t recognise DomUs as being deleted and would not > allow me to recreate them "ERROR Guest name ''xen1'' is already in use.". >When doing what? I''m usually able to ''define'', ''creade'', ''shutdown'', ''undefine'' and ''create'' again. What is your issue with that?> Thanks all for your help - you''ve now got me to a stage where I can > ''fiddle'' around myself. >:-D Regards, Dario -- <<This happens because I choose it to happen!>> (Raistlin Majere) ----------------------------------------------------------------- Dario Faggioli, Ph.D, http://about.me/dario.faggioli Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK) _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
G Crowe
2013-Oct-22 12:03 UTC
Re: First time xen install - Xen DomU runs, but can''t find "/dev/root"
On 21/10/2013 5:28 PM, Dario Faggioli wrote:> Well, yes, in the blog post I mention setting up a PXE server, but that > is for _installing_ _Dom0_. For guests, you really don''t need one, you > can just point your --location to an URL and that''s it! > > I recommend you trying... It at least look easier than using a local > webserver, etc.Ooops, you are right about the PXE server. Sorry. As far as installinf from a URL, the machine I am trying this on does not have a direct connection to the internet, hence me trying to install from a DVD image. In order to use a URL to boot I had to create my own as there were none already available (that were accessible).> > When doing what? I''m usually able to ''define'', ''creade'', ''shutdown'', > ''undefine'' and ''create'' again. > > What is your issue with that? >This is probably just my ignorance , please see my output below... Note that "xl define" and "xl undefine" both return "command not implemented". ******************** Scenario 1, stopping and then restarting a DomU - I can shutdown a DomU with "xm", "xl", from within the DomU with "shutdown -r now", or by rebooting Dom0. - xl seems to lose any memory of the DomU at this point (well, I can''t figure out how to bring it back) and "xl list" doesn''t show it while it is stopped. - xm can remember it and restart it. "xm list" will still list the stopped DomU. - "xl create" seems to want a config file, which I don''t have. "xm start" just starts the DomU that has already been configured, without needing an additional config file. ******************** [root@dhcp1 ~]# xl list Name ID Mem VCPUs State Time(s) Domain-0 0 483 4 r----- 130.5 xen1 4 512 1 -b---- 12.5 [root@dhcp1 ~]# xm list Name ID Mem VCPUs State Time(s) Domain-0 0 483 4 r----- 130.8 xen1 4 512 1 -b---- 12.5 [root@dhcp1 ~]# xl shutdown xen1 [root@dhcp1 ~]# xl list Name ID Mem VCPUs State Time(s) Domain-0 0 483 4 r----- 133.9 [root@dhcp1 ~]# xm list Name ID Mem VCPUs State Time(s) Domain-0 0 483 4 r----- 134.2 xen1 512 1 13.1 [root@dhcp1 ~]# xl start xen1 command not implemented [root@dhcp1 ~]# xm start xen1 [root@dhcp1 ~]# xl list Name ID Mem VCPUs State Time(s) Domain-0 0 483 4 r----- 143.8 xen1 5 512 1 r----- 2.7 [root@dhcp1 ~]# xm list Name ID Mem VCPUs State Time(s) Domain-0 0 483 4 r----- 144.3 xen1 5 512 1 r----- 3.9 ******************** Scenario 2, deleting and then recreating a DomU - I can delete a DomU with "xm destroy xen2" then "xm delete xen2" - When trying "virt-install" - If xend is not running (it defaults to the xl toolchain?) then I cannot recreate xen2 with virt-install. - If xend is restarted, then the exact same virt-install command will recreate the xen2 DomU. ******************** [root@dhcp1 ~]# xl list Name ID Mem VCPUs State Time(s) Domain-0 0 483 4 r----- 165.2 [root@dhcp1 ~]# xm list Error: Unable to connect to xend: Connection refused. Is xend running? [root@dhcp1 ~]# virt-install --paravirt --name xen2 --ram 512 --vcpus 1 -f /dev/fedora_dhcp1/xen2 --network bridge=br0 --location http://gcrowe.crowie.net/f18 --graphics none ERROR Guest name ''xen2'' is already in use. [root@dhcp1 ~]# xend [root@dhcp1 ~]# virt-install --paravirt --name xen2 --ram 512 --vcpus 1 -f /dev/fedora_dhcp1/xen2 --network bridge=br0 --location http://gcrowe.crowie.net/f18 --graphics none Starting install... <Output truncated here, but the install proceeds normally.>
GC
2013-Oct-23 11:22 UTC
Re: First time xen install - Xen DomU runs, but can''t find "/dev/root"
Okay, I''ve done a bit of playing around and I think I''ve solved most of my issues... - xend keeps a record of its DomU domains in /var/lib/xend/domains/<UUID>/config.sxp - This is why it remembers them over reboots (and when the domains are stopped). - To convert these to a format that "xl create" can use, I used the following (note that I had to have xend running to do this). # virsh domxml-from-native xen-sxpr config.sxp > xen1.xml # virsh domxml-to-native xen-xm xen1.xml > xen1.cfg # xl create xen1.cfg - I can now start and stop my DomUs using xl (without xend running) :) - I have now found the "virsh undefine" command which has resolved my "DomU already in use error" (I had been using "xl" instead of "virsh"). My one remaining problem without xend running is that it bombs out when connecting to the console when using virt-install. Below is the output when I install with xend not running. If I run the exact same command with xend running then I don''t get the error message and it jumps straight into the console. This isn''t a major problem as I can simply connect to the console after it bombs out. [root@dhcp1 ~]# virt-install --paravirt --name xen2 --ram 512 --vcpus 1 -f /dev/fedora_dhcp1/xen2 --network bridge=br0 --location http://www.example.com/f18 --graphics none Starting install... Retrieving file .treeinfo... | 2.4 kB 00:00:00 !!! Retrieving file vmlinuz-PAE... | 9.3 MB 00:00:00 !!! Retrieving file initrd-PAE.img... | 52 MB 00:00:03 !!! Creating domain... | 0 B 00:00:13 Connected to domain xen2 Escape character is ^] error: this function is not supported by the connection driver: virDomainOpenConsole Domain installation still in progress. You can reconnect to the console to complete the installation process. [root@dhcp1 ~]# xl console xen2 [ 0.000000] Reserving virtual address space above 0xf5800000 < -- snip -- The console works as expected from here onwards >
Dario Faggioli
2013-Oct-23 13:59 UTC
Re: First time xen install - Xen DomU runs, but can''t find "/dev/root"
On mar, 2013-10-22 at 23:03 +1100, G Crowe wrote:> On 21/10/2013 5:28 PM, Dario Faggioli wrote: > > When doing what? I''m usually able to ''define'', ''creade'', ''shutdown'', > > ''undefine'' and ''create'' again. > > > > What is your issue with that? > > > This is probably just my ignorance , please see my output below... > Note that "xl define" and "xl undefine" both return "command not > implemented". >Uh, sorry, I probably explained myself bad. :-( Those "define" and "undefine" commands are from libvirt, so you have access to them via `virsh'', rather than `xl''.> ******************** > Scenario 1, stopping and then restarting a DomU > - I can shutdown a DomU with "xm", "xl", from within the DomU with > "shutdown -r now", or by rebooting Dom0. >Ok.> - xl seems to lose any memory of the DomU at this point (well, I can''t > figure out how to bring it back) and "xl list" doesn''t show it while it > is stopped. > - xm can remember it and restart it. "xm list" will still list the > stopped DomU. >Right, and that''s by design. One of the differences between xl and xm is that the latter remembers (you usually say ''manages'') domains even when they''re not running, while xl forgets about them. That happens because, together with xm, you have the xend daemon doing right that, while with xl there is no such thing (you always have daemons running, like xenstore, etc, but not for that purpose).> - "xl create" seems to want a config file, which I don''t have. "xm > start" just starts the DomU that has already been configured, without > needing an additional config file. >Right, because you created the DomU via virt-install, right? Well, ideally, there would be a "xen-xl" sub-command available for `virsh domxml-to-native", which would give you exactly the config file you''re looking for. This is quite a big issue (at least according to me) with the libxl libvirt driver... We''ll try to look into that ASAP!> ******************** > Scenario 2, deleting and then recreating a DomU > - I can delete a DomU with "xm destroy xen2" then "xm delete xen2" > - When trying "virt-install" - If xend is not running (it defaults to > the xl toolchain?) >Yes, that''s how libvirt works (defaults to the libxl driver if xend is not running), and virt-install does use libvirt.> then I cannot recreate xen2 with virt-install. >No, you can''t, but you should be able to start it with `virsh''. Try something like the following (after shutting down xen2): # virsh list --all it should list xen2, in a non-running (or stopped, or something like that) status. After that: # virsh start xen2 should bring it up. Finally, sorry for replying a bit late, but I''m traveling these days. Regards, Dario -- <<This happens because I choose it to happen!>> (Raistlin Majere) ----------------------------------------------------------------- Dario Faggioli, Ph.D, http://about.me/dario.faggioli Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK) _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
Dario Faggioli
2013-Oct-23 14:11 UTC
Re: First time xen install - Xen DomU runs, but can''t find "/dev/root"
On mer, 2013-10-23 at 22:22 +1100, GC wrote:> Okay, I''ve done a bit of playing around and I think I''ve solved most of > my issues... >:-)> - xend keeps a record of its DomU domains in > /var/lib/xend/domains/<UUID>/config.sxp - This is why it remembers them > over reboots (and when the domains are stopped). >Yep, that''s what I was also trying to say in my previous e-mail.> - To convert these to a format that "xl create" can use, I used the > following (note that I had to have xend running to do this). > # virsh domxml-from-native xen-sxpr config.sxp > xen1.xml > # virsh domxml-to-native xen-xm xen1.xml > xen1.cfg > # xl create xen1.cfg > - I can now start and stop my DomUs using xl (without xend running) :) >Ok. Well, yes, I appreciate that this does the trick. Since (I think) you have the domain managed by libvirt already (try `virsh list --all'' to verify that), you probably can do something like the following directly: # virsh domxml-to-native xen-xm xen1 > xen1.cfg This gives you a config file suitable for xm/xend, which, hopefully, is similar enough to the one you need for xl. So, I''m glad it work, but I nevertheless think we need something like "domxml-to-native xen-xl" in libvirt.> - I have now found the "virsh undefine" command which has resolved my > "DomU already in use error" (I had been using "xl" instead of "virsh"). >Right.> My one remaining problem without xend running is that it bombs out when > connecting to the console when using virt-install. Below is the output > when I install with xend not running. If I run the exact same command > with xend running then I don''t get the error message and it jumps > straight into the console. This isn''t a major problem as I can simply > connect to the console after it bombs out. > > > [root@dhcp1 ~]# virt-install --paravirt --name xen2 --ram 512 --vcpus 1 > -f /dev/fedora_dhcp1/xen2 --network bridge=br0 --location > http://www.example.com/f18 --graphics none > > Starting install... > Retrieving file .treeinfo... | 2.4 kB 00:00:00 !!! > Retrieving file vmlinuz-PAE... | 9.3 MB 00:00:00 !!! > Retrieving file initrd-PAE.img... | 52 MB 00:00:03 !!! > Creating domain... | 0 B 00:00:13 > Connected to domain xen2 > Escape character is ^] > error: this function is not supported by the connection driver: > virDomainOpenConsole >Mmm... Weird. Although I think there are some issues with console support in the libvirt libxl driver (which used to work, but still...), installation with ''--graphics none'' worked for me (as I wrote in the blog post). I''ll investigate more. Thanks and Regards, Dario -- <<This happens because I choose it to happen!>> (Raistlin Majere) ----------------------------------------------------------------- Dario Faggioli, Ph.D, http://about.me/dario.faggioli Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK) _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
G Crowe
2013-Nov-20 11:53 UTC
Re: First time xen install - Xen DomU runs, but can''t find "/dev/root"
On 24/10/2013 1:11 AM, Dario Faggioli wrote:> On mer, 2013-10-23 at 22:22 +1100, GC wrote: >> My one remaining problem without xend running is that it bombs out when >> connecting to the console when using virt-install. Below is the output >> when I install with xend not running. If I run the exact same command >> with xend running then I don''t get the error message and it jumps >> straight into the console. This isn''t a major problem as I can simply >> connect to the console after it bombs out. >> >> >> [root@dhcp1 ~]# virt-install --paravirt --name xen2 --ram 512 --vcpus 1 >> -f /dev/fedora_dhcp1/xen2 --network bridge=br0 --location >> http://www.example.com/f18 --graphics none >> >> Starting install... >> Retrieving file .treeinfo... | 2.4 kB 00:00:00 !!! >> Retrieving file vmlinuz-PAE... | 9.3 MB 00:00:00 !!! >> Retrieving file initrd-PAE.img... | 52 MB 00:00:03 !!! >> Creating domain... | 0 B 00:00:13 >> Connected to domain xen2 >> Escape character is ^] >> error: this function is not supported by the connection driver: >> virDomainOpenConsole >> > Mmm... Weird. Although I think there are some issues with console > support in the libvirt libxl driver (which used to work, but still...), > installation with ''--graphics none'' worked for me (as I wrote in the > blog post). > > I''ll investigate more.Did you find anything with your investigations? This is causing me grief at the moment. I have now bought a new server which supports hardware virtualisation and I am seeing the following results - Note, running Fedora 19 x64. The machine was temporarily connected to the internet and "yum update" was run, so the packages should be up-to-date. If I start a VM with "--paravirt" "xl console domU" works "virsh console domU" fails with "error: this function is not supported by the connection driver: virDomainOpenConsole" If I start a VM with "--hvm" "xl console domU" fails with "xenconsole: Could not read tty from store: No such file or directory" "virsh console domU" fails with "error: this function is not supported by the connection driver: virDomainOpenConsole" I am currently unable to install a domU using --hvm as I am not aware of any way to connect to the console. Thanks G Crowe