[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Problem with tap:aio



First:

You could get more answers if you would send your responses to the mailing list.

Second:

I've backported the xen-utils-common package, which means really just a rebuild, but as it is really just some shell scripts you could simply install the squeeze version.

Good Luck!
and
Happy New Year!

Geza
Hi

As I said I'm using Debian Lenny which has xen-utils-common with 3.2.0-2 version... I saw 3.3.1-2 in sid... should I use sid?! After all, isn't here any Debian man who want to use tap:aio ? :(

On Mon, Dec 21, 2009 at 1:03 PM, Gémes Géza <geza@xxxxxxxxxxx <mailto:geza@xxxxxxxxxxx>> wrote:

    Mozafar Roshany írta:
    > Thanks for quick solution.
    >
    > I created two blktapctrl and tapdisk symlinks to point to
    > xen-utils-wrapper; So now have this:
    >
    > # file /usr/sbin/* | grep -i wrap
    > /usr/sbin/blktapctrl:          symbolic link to
    > `/usr/lib/xen-common/bin/xen-utils-wrapper'
    > /usr/sbin/cpuperf-perfcntr:    symbolic link to
    > `../lib/xen-common/bin/xen-utils-wrapper'
    > /usr/sbin/cpuperf-xen:         symbolic link to
    > `../lib/xen-common/bin/xen-utils-wrapper'
    > /usr/sbin/tapdisk:             symbolic link to
    > `/usr/lib/xen-common/bin/xen-utils-wrapper'
    > /usr/sbin/xend:                symbolic link to
    > `../lib/xen-common/bin/xen-utils-wrapper'
    > /usr/sbin/xenperf:             symbolic link to
    > `../lib/xen-common/bin/xen-utils-wrapper'
    > /usr/sbin/xentop:              symbolic link to
    > `../lib/xen-common/bin/xen-utils-wrapper'
    > /usr/sbin/xentrace:            symbolic link to
    > `../lib/xen-common/bin/xen-utils-wrapper'
    > /usr/sbin/xentrace_format:     symbolic link to
    > `../lib/xen-common/bin/xen-utils-wrapper'
    > /usr/sbin/xentrace_setmask:    symbolic link to
    > `../lib/xen-common/bin/xen-utils-wrapper'
    > /usr/sbin/xentrace_setsize:    symbolic link to
    > `../lib/xen-common/bin/xen-utils-wrapper'
    > /usr/sbin/xm:                  symbolic link to
    > `../lib/xen-common/bin/xen-utils-wrapper'
    >
    > But still does Not work :( . (I did restarted xend and domU).

    My versions:
    xen-utils-3.2-1
    xen-utils-common: 3.3.1-3
    could it be the reason?
    >
    > On Mon, Dec 21, 2009 at 9:57 AM, Gémes Géza <geza@xxxxxxxxxxx
    <mailto:geza@xxxxxxxxxxx>
    > <mailto:geza@xxxxxxxxxxx <mailto:geza@xxxxxxxxxxx>>> wrote:
    >
    >     Mozafar Roshany írta:
    >
    >         Hi
    >
    >         No, it did not work. I did: ln -s /usr/lib/xen-3.2-1/bin/*
    >         /usr/sbin/
    >         and restarted xend and that domU, but the same errors
    remain.
    >
    >         Thanks Gemes.
    >
    >
    >     Ok I've checked back how I did. I've modified the
    xen-utils-common
    >     package, to include symlinks for tapdisk and blktapctrl for
    >     ../lib/xen-common/bin/xen-utils-wrapper.
    >     So sorry for misinforming you at the first time, please modify
    >     your symlinks to point to:
    ../lib/xen-common/bin/xen-utils-wrapper
    >
    >     Good Luck!
    >
    >     Geza
    >
    >
    >         On Sun, Dec 20, 2009 at 6:02 PM, Gémes Géza
    <geza@xxxxxxxxxxx <mailto:geza@xxxxxxxxxxx>
    >         <mailto:geza@xxxxxxxxxxx <mailto:geza@xxxxxxxxxxx>>
    <mailto:geza@xxxxxxxxxxx <mailto:geza@xxxxxxxxxxx>
    >         <mailto:geza@xxxxxxxxxxx <mailto:geza@xxxxxxxxxxx>>>> wrote:
    >
    >            Mozafar Roshany írta:
    >
    >                Hi all
    >
    >                I was reading through Xen 3 user manual and saw this
    >         tap:aio
    >                should be used instead of loopback...
    >                Then I came to do that, but I can get it working with
    >                replacing `file' URI's with `tap:aio'.
    >
    >                My OS: Debian Lenny 2.6.26-2-xen-amd64
    >
    >                DomU Xen configuration file:
    >
    >                kernel      = '/boot/vmlinuz-2.6.26-2-xen-amd64'
    >                ramdisk     = '/boot/initrd.img-2.6.26-2-xen-amd64'
    >                memory      = '1024'
    >                root        = '/dev/xvda1 ro'
    >                disk        = [
    >
    >         'tap:aio:/xen/domains/test1/manu.img,xvda1,w',
    >
    >         'tap:aio:/xen/domains/test1/disk.img,xvda2,w',
    >                             ]
    >                name        = 'test1'
    >                vif         = [
    'ip=10.1.1.50,mac=00:16:3E:51:E4:AD' ]
    >                on_poweroff = 'destroy'
    >                on_reboot   = 'restart'
    >                on_crash    = 'restart'
    >
    >                The errors from console:
    >
    >                [    0.872134] Capability LSM initialized
    >                [    0.872151] Mount-cache hash table entries: 256
    >                [    0.872282] Initializing cgroup subsys ns
    >                [    0.872290] Initializing cgroup subsys cpuacct
    >                [    0.872295] Initializing cgroup subsys devices
    >                [    0.872326] CPU: L1 I cache: 32K, L1 D cache: 32K
    >                [    0.872333] CPU: L2 cache: 6144K
    >                [    0.872340] CPU: Physical Processor ID: 1
    >                [    0.872344] CPU: Processor Core ID: 3
    >                [    0.872356] SMP alternatives: switching to UP code
    >                [    0.879420] Freeing SMP alternatives: 21k freed
    >                [    0.879535] Brought up 1 CPUs
    >                [    0.881865] net_namespace: 1224 bytes
    >                [    0.882025] NET: Registered protocol family 16
    >                [    0.883053] Brought up 1 CPUs
    >                [    0.883068] PCI: Fatal: No config space access
    >         function found
    >                [    0.883075] PCI: setting up Xen PCI frontend stub
    >                [    0.883750] ACPI: Interpreter disabled.
    >                [    0.883758] Linux Plug and Play Support v0.97 (c)
    >         Adam Belay
    >                [    0.883790] pnp: PnP ACPI: disabled
    >                [    0.883979] suspend: event channel 7
    >                [    0.884329] xen_mem: Initialising balloon driver.
    >                [    0.885871] usbcore: registered new interface
    driver
    >         usbfs
    >                [    0.885931] usbcore: registered new interface
    driver hub
    >                [    0.885977] usbcore: registered new device
    driver usb
    >                [    0.886139] PCI: System does not support PCI
    >                [    0.886145] PCI: System does not support PCI
    >                [    0.898148] NET: Registered protocol family 2
    >                [    0.933769] IP route cache hash table entries:
    32768
    >                (order: 6, 262144 bytes)
    >                [    0.934013] TCP established hash table
    entries: 131072
    >                (order: 9, 2097152 bytes)
    >                [    0.934815] TCP bind hash table entries: 65536
    >         (order: 8,
    >                1048576 bytes)
    >                [    0.935207] TCP: Hash tables configured
    (established
    >         131072
    >                bind 65536)
    >                [    0.935213] TCP reno registered
    >                [    0.945775] NET: Registered protocol family 1
    >                [    0.945859] checking if image is initramfs...
    it is
    >                [    0.951155] Freeing initrd memory: 5252k freed
    >                [    0.952017] platform rtc_cmos: registered
    platform RTC
    >                device (no PNP device found)
    >                [    0.952017] audit: initializing netlink socket
    >         (disabled)
    >                [    0.952017] type=2000 audit(1261321342.173:1):
    >         initialized
    >                [    0.952017] VFS: Disk quotas dquot_6.5.1
    >                [    0.952017] Dquot-cache hash table entries: 512
    >         (order 0,
    >                4096 bytes)
    >                [    0.952017] msgmni has been set to 2058
    >                [    0.952017] Block layer SCSI generic (bsg) driver
    >         version
    >                0.4 loaded (major 253)
    >                [    0.952017] io scheduler noop registered
    >                [    0.952017] io scheduler anticipatory registered
    >                [    0.952017] io scheduler deadline registered
    >                [    0.952017] io scheduler cfq registered (default)
    >                [    0.953902] Linux agpgart interface v0.103
    >                [    0.953947] Serial: 8250/16550 driver $Revision:
    >         1.90 $ 4
    >                ports, IRQ sharing enabled
    >                [    0.955284] brd: module loaded
    >                [    0.955342] input: Macintosh mouse button
    emulation as
    >                /class/input/input0
    >                [    0.955404] Xen virtual console successfully
    >         installed as hvc0
    >                [    0.955451] Event-channel device installed.
    >                [    0.960690] netfront: Initialising virtual
    ethernet
    >         driver.
    >                [    0.961761] PNP: No PS/2 controller found.
    Probing ports
    >                directly.
    >                [    0.962588] i8042.c: No controller found.
    >                [    0.976078] mice: PS/2 mouse device common for
    all mice
    >                [    0.976184] rtc_cmos rtc_cmos: rtc core:
    registered
    >                rtc_cmos as rtc0
    >                [    0.976298] No iBFT detected.
    >                [    0.976641] TCP cubic registered
    >                [    0.976647] NET: Registered protocol family 17
    >                [    0.976739] registered taskstats version 1
    >                [    6.077230] XENBUS: Waiting for devices to
    initialise:
    >
> 295s...290s...285s...280s...275s...270s...265s...260s...255s...250s...245s...240s...235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...15s...10s...5s...0s...
    >                [  301.076163] XENBUS: Timeout connecting to device:
    >                device/vbd/2050 (local state 3, remote state 2)
    >                [  301.076173] XENBUS: Device not ready:
    device/vbd/2050
    >                [  301.076179] XENBUS: Device with no driver:
    >         device/console/0
    >                [  301.076186] drivers/rtc/hctosys.c: unable to
    open rtc
    >                device (rtc0)
    >                [  301.076209] Freeing unused kernel memory: 216k
    freed
    >                Loading, please wait...
    >                Begin: Loading essential drivers ... [
     301.123168] SCSI
    >                subsystem initialized
    >                [  301.124278] HP CISS Driver (v 3.6.20)
    >                done.
    >                Begin: Running /scripts/init-premount ... FATAL:
    Error
    >                inserting fan
    >
> (/lib/modules/2.6.26-2-xen-amd64/kernel/drivers/acpi/fan.ko):
    >                No such device
    >                WARNING: Error inserting processor
    >
> (/lib/modules/2.6.26-2-xen-amd64/kernel/drivers/acpi/processor.ko):
    >                No such device
    >                [  301.172668] thermal: Unknown symbol
    >                acpi_processor_set_thermal_limit
    >                FATAL: Error inserting thermal
    >
> (/lib/modules/2.6.26-2-xen-amd64/kernel/drivers/acpi/thermal.ko):
    >                Unknown symbol in module, or unknown parameter
    (see dmesg)
    >                done.
    >                Begin: Mounting root file system ... Begin: Running
    >                /scripts/local-top ... done.
    >                Begin: Waiting for root file system ...
    >                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/sda2 does not exist. Dropping to a shell!
    >
    >
    >                BusyBox v1.10.2 (Debian 1:1.10.2-2) built-in
    shell (ash)
    >                Enter 'help' for a list of built-in commands.
    >
    >                /bin/sh: can't access tty; job control turned off
    >                (initramfs)
    >                =========================================
    >
    >                I modprobed the xenblktap module and also
    googled, but
    >         no success.
    >
    >                Thanks for any comment.
    >
    >
    >
    >
    >
> ------------------------------------------------------------------------
    >
    >
    >
    >                _______________________________________________
    >                Xen-users mailing list
    >                Xen-users@xxxxxxxxxxxxxxxxxxx
    <mailto:Xen-users@xxxxxxxxxxxxxxxxxxx>
    >         <mailto:Xen-users@xxxxxxxxxxxxxxxxxxx
    <mailto:Xen-users@xxxxxxxxxxxxxxxxxxx>>
    >                <mailto:Xen-users@xxxxxxxxxxxxxxxxxxx
    <mailto:Xen-users@xxxxxxxxxxxxxxxxxxx>
    >         <mailto:Xen-users@xxxxxxxxxxxxxxxxxxx
    <mailto:Xen-users@xxxxxxxxxxxxxxxxxxx>>>
    >
    >                http://lists.xensource.com/xen-users
    >
    >            With stock lenny packages blktapctrl ad tapdisk are
    out of your
    >            PATH, you should try to symlink them from
    >         /usr/lib/xen-3.2-1/bin/
    >            to /usr/bin or /usr/sbin, may need to restart xend
    and then
    >         try to
    >            load that tap:aio domain again.
    >            Hope that helps.
    >
    >            Geza
    >
    >
    >
    >




_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.