Hi, Does Xen 4.1 support port forwarding? I have a VM and the interface in th VM can be dynamically configured with an IP. How do I ssh to this VM from Dom0? I was thinking of port forwarding, does xen support it? Thanks, Dhanesh.
On Thu, 2013-10-03 at 09:46 +0530, Jaya Dhanesh wrote:> Hi, > > > Does Xen 4.1 support port forwarding? I have a VM and the interface in > th VM can be dynamically > configured with an IP. How do I ssh to this VM from Dom0? I was thinking > of port forwarding, does > xen support it?This is not really a function of Xen but of your dom0 operating system and or a guest agent type thing. You''d need to expose some way to get the IP address out of the guest and into dom0 -- perhaps an initscript which writes it to xenstore on boot. From there if you want to ssh only from dom0 you could script up something to read that IP address from xenstore and invoke ssh. If you wanted to do something more clever you could have a process in dom0 which configured a tunnel etc. Or you could deploy NAT on the host, which would give you control of the IPs given to VMs but at the expense of them not being visible external to the host. Of course you can also use all the techniques you would use on a physical system, e.g. configure your DHCP server to use static addresses or to update a static domain name with the dynamic address, or use a dynamic IP provider (the one I use has recently gotten overly commercial so I''m not going to recommend them here, ddclient seems to support a bunch of them though). Ian.
On Thu, Oct 03, 2013 at 09:46:43AM +0530, Jaya Dhanesh wrote:> Hi, > > > Does Xen 4.1 support port forwarding? I have a VM and the interface > in th VM can be dynamically > configured with an IP. How do I ssh to this VM from Dom0? I was > thinking of port forwarding, does > xen support it? >I don''t think this is Xen-related. You should check out iptables on port forwarding. SSH from Dom0 to DomU is just the same as ssh from any other host to DomU -- you need to know the IP address / domain name of DomU. This requires you to setup infrastructure such as DHCP / DNS correctly and has nothing to do with Xen (the hypervisor and the toolstack). Wei.> Thanks, > Dhanesh. > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users
Hi, I am trying tobring up a SLES SP2 as a VM on Xen 4.1.2. When I do a console to the vm, I see the following logs: FATAL: Error inserting xen_vnif (/lib/modules/3.0.13-0.27-default/updates/netfront/xen-vnif.ko): No such device rying manual resume from /dev/hda1 resume device /dev/hda1 not found (ignoring) Trying manual resume from /dev/hda1 resume device /dev/hda1 not found (ignoring) Waiting for device /dev/hda2 to appear: [ 1.876217] input: ImExPS/2 Generic Explorer Mouse as /devices/platform/i8042/serio1/input/input1 [ 2.068106] Refined TSC clocksource calibration: 2400.083 MHz. [ 2.071086] Switching to clocksource tsc ..............................Could not find /dev/hda2. Want me to fall back to /dev/hda2? (Y/n) Any idea what the problem may be. The same thing works on another system. Thanks, Dhanesh. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
On Fri, Nov 08, 2013 at 03:48:59PM +0530, Jaya Dhanesh wrote:> Hi, > > I am trying tobring up a SLES SP2 as a VM on Xen 4.1.2. When I do a > console to the vm, I see the following logs: > > FATAL: Error inserting xen_vnif > (/lib/modules/3.0.13-0.27-default/updates/netfront/xen-vnif.ko): No > such device > rying manual resume from /dev/hda1 > > resume device /dev/hda1 not found (ignoring) > > Trying manual resume from /dev/hda1 > > resume device /dev/hda1 not found (ignoring) > > Waiting for device /dev/hda2 to appear: [ 1.876217] input: > ImExPS/2 Generic Explorer Mouse as > /devices/platform/i8042/serio1/input/input1 > > [ 2.068106] Refined TSC clocksource calibration: 2400.083 MHz. > > [ 2.071086] Switching to clocksource tsc > > ..............................Could not find /dev/hda2. > > Want me to fall back to /dev/hda2? (Y/n) > > Any idea what the problem may be. The same thing works on another system. >Could you use xm create -c config and attach the full output here. Do you see any thing like xvda* in log? Wei.> Thanks, > Dhanesh.> _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users
I do not see any xvda in the console log. plfm-app-sim-03:~/vmmgr/hvmmgr/.hvmmgrd/vms # xm create ttool2.cfg Using config file "./ttool2.cfg". Started domain ttool2 (id=288) plfm-app-sim-03:~/vmmgr/hvmmgr/.hvmmgrd/vms # xm console ttool2 [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Linux version 3.0.13-0.27-default (geeko@buildhost) (gcc version 4.3.4 [gcc-4_3-branch revision 152973] (SUSE Linux) ) #1 SMP Wed Feb 15 13:33:49 UTC 2012 (d73692b) [ 0.000000] Command line: root=/dev/hda2 console=ttyS0,115200 resume=/dev/hda1 splash=silent crashkernel=256M-:128M showopts [ 0.000000] BIOS-provided physical RAM map: [ 0.000000] BIOS-e820: 0000000000000000 - 000000000009e000 (usable) [ 0.000000] BIOS-e820: 000000000009e000 - 00000000000a0000 (reserved) [ 0.000000] BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved) [ 0.000000] BIOS-e820: 0000000000100000 - 00000000f0000000 (usable) [ 0.000000] BIOS-e820: 00000000fc000000 - 0000000100000000 (reserved) [ 0.000000] BIOS-e820: 0000000100000000 - 0000000110000000 (usable) [ 0.000000] NX (Execute Disable) protection: active [ 0.000000] DMI 2.4 present. [ 0.000000] No AGP bridge found [ 0.000000] last_pfn = 0x110000 max_arch_pfn = 0x400000000 [ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106 [ 0.000000] last_pfn = 0xf0000 max_arch_pfn = 0x400000000 [ 0.000000] found SMP MP-table at [ffff8800000fbc90] fbc90 [ 0.000000] init_memory_mapping: 0000000000000000-00000000f0000000 [ 0.000000] init_memory_mapping: 0000000100000000-0000000110000000 [ 0.000000] RAMDISK: 37925000 - 37ff0000 [ 0.000000] Reserving 128MB of memory at 752MB for crashkernel (System RAM: 4352MB) [ 0.000000] ACPI: RSDP 00000000000ea020 00024 (v02 Xen) [ 0.000000] ACPI: XSDT 00000000fc00eaa0 00034 (v01 Xen HVM 00000000 HVML 00000000) [ 0.000000] ACPI: FACP 00000000fc00e8c0 000F4 (v04 Xen HVM 00000000 HVML 00000000) [ 0.000000] ACPI: DSDT 00000000fc002c40 0BBF1 (v02 Xen HVM 00000000 INTL 20081031) [ 0.000000] ACPI: FACS 00000000fc002c00 00040 [ 0.000000] ACPI: APIC 00000000fc00e9c0 000D8 (v02 Xen HVM 00000000 HVML 00000000) [ 0.000000] No NUMA configuration found [ 0.000000] Faking a node at 0000000000000000-0000000110000000 [ 0.000000] Initmem setup node 0 0000000000000000-0000000110000000 [ 0.000000] NODE_DATA [000000010ffd9000 - 000000010fffffff] [ 0.000000] Zone PFN ranges: [ 0.000000] DMA 0x00000010 -> 0x00001000 [ 0.000000] DMA32 0x00001000 -> 0x00100000 [ 0.000000] Normal 0x00100000 -> 0x00110000 [ 0.000000] Movable zone start PFN for each node [ 0.000000] early_node_map[3] active PFN ranges [ 0.000000] 0: 0x00000010 -> 0x0000009e [ 0.000000] 0: 0x00000100 -> 0x000f0000 [ 0.000000] 0: 0x00100000 -> 0x00110000 [ 0.000000] ACPI: PM-Timer IO Port: 0xb008 [ 0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x02] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x04] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x06] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x08] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x05] lapic_id[0x0a] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x06] lapic_id[0x0c] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x07] lapic_id[0x0e] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x10] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x12] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x14] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x16] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x0c] lapic_id[0x18] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x0d] lapic_id[0x1a] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x0e] lapic_id[0x1c] disabled) [ 0.000000] ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0]) [ 0.000000] IOAPIC[0]: apic_id 1, version 17, address 0xfec00000, GSI 0-47 [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 5 global_irq 5 low level) [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 10 global_irq 10 low level) [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 11 global_irq 11 low level) [ 0.000000] Using ACPI (MADT) for SMP configuration information [ 0.000000] SMP: Allowing 15 CPUs, 13 hotplug CPUs [ 0.000000] PM: Registered nosave memory: 000000000009e000 - 00000000000a0000 [ 0.000000] PM: Registered nosave memory: 00000000000a0000 - 00000000000e0000 [ 0.000000] PM: Registered nosave memory: 00000000000e0000 - 0000000000100000 [ 0.000000] PM: Registered nosave memory: 00000000f0000000 - 00000000fc000000 [ 0.000000] PM: Registered nosave memory: 00000000fc000000 - 0000000100000000 [ 0.000000] Allocating PCI resources starting at f0000000 (gap: f0000000:c000000) [ 0.000000] Booting paravirtualized kernel on bare hardware [ 0.000000] setup_percpu: NR_CPUS:4096 nr_cpumask_bits:15 nr_cpu_ids:15 nr_node_ids:1 [ 0.000000] PERCPU: Embedded 26 pages/cpu @ffff88010fc00000 s74880 r8192 d23424 u131072 [ 0.000000] Built 1 zonelists in Node order, mobility grouping on. Total pages: 1033225 [ 0.000000] Policy zone: Normal [ 0.000000] Kernel command line: root=/dev/hda2 console=ttyS0,115200 resume=/dev/hda1 splash=silent crashkernel=256M-:128M showopts [ 0.000000] bootsplash: silent mode. [ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes) [ 0.000000] Checking aperture... [ 0.000000] No AGP bridge found [ 0.000000] Memory: 3912040k/4456448k available (4405k kernel code, 262600k absent, 281808k reserved, 7781k data, 1356k init) [ 0.000000] Hierarchical RCU implementation. [ 0.000000] RCU dyntick-idle grace-period acceleration is enabled. [ 0.000000] NR_IRQS:262400 nr_irqs:1208 16 [ 0.000000] Console: colour VGA+ 80x25 [ 0.000000] console [ttyS0] enabled [ 0.000000] allocated 33554432 bytes of page_cgroup [ 0.000000] please try ''cgroup_disable=memory'' option if you don''t want memory cgroups [ 0.000000] Fast TSC calibration using PIT [ 0.000000] Detected 2400.567 MHz processor. [ 0.012005] Calibrating delay loop (skipped), value calculated using timer frequency.. 4801.13 BogoMIPS (lpj=9602268) [ 0.021896] pid_max: default: 32768 minimum: 301 [ 0.024201] kdb version 4.4 by Keith Owens, Scott Lurndal. Copyright SGI, All Rights Reserved kdb_cmd[0]: defcmd archkdb "" "First line arch debugging" kdb_cmd[8]: defcmd archkdbcpu "" "archkdb with only tasks on cpus" kdb_cmd[15]: defcmd archkdbshort "" "archkdb with less detailed backtrace" kdb_cmd[22]: defcmd archkdbcommon "" "Common arch debugging" [ 0.044157] Security Framework initialized [ 0.048020] AppArmor: AppArmor initialized [ 0.052309] Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes) [ 0.056799] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes) [ 0.060354] Mount-cache hash table entries: 256 [ 0.064132] Initializing cgroup subsys cpuacct [ 0.068009] Initializing cgroup subsys memory [ 0.072021] Initializing cgroup subsys devices [ 0.074990] Initializing cgroup subsys freezer [ 0.076007] Initializing cgroup subsys net_cls [ 0.080006] Initializing cgroup subsys blkio [ 0.084011] Initializing cgroup subsys perf_event [ 0.087217] CPU: Physical Processor ID: 0 [ 0.088007] CPU: Processor Core ID: 0 [ 0.092008] mce: CPU supports 9 MCE banks [ 0.098189] ACPI: Core revision 20110413 [ 0.106673] Enabling x2apic [ 0.108005] Enabled x2apic [ 0.108009] Switched APIC routing to physical x2apic. [ 0.113724] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=0 pin2=0 [ 0.159472] CPU0: Intel(R) Xeon(R) CPU E5645 @ 2.40GHz stepping 02 [ 0.168009] Performance Events: unsupported p6 CPU model 44 no PMU driver, software events only. [ 0.168115] NMI watchdog disabled (cpu0): hardware events not enabled [ 0.172127] Booting Node 0, Processors #1 [ 0.208026] NMI watchdog disabled (cpu1): hardware events not enabled [ 0.212083] Brought up 2 CPUs [ 0.216015] Total of 2 processors activated (9602.26 BogoMIPS). [ 0.220389] devtmpfs: initialized [ 0.228993] print_constraints: dummy: [ 0.232050] Time: 9:26:29 Date: 11/08/13 [ 0.236236] NET: Registered protocol family 16 [ 0.240175] ACPI: bus type pci registered [ 0.244054] PCI: Using configuration type 1 for base access [ 0.248596] bio: create slab <bio-0> at 0 [ 0.262531] ACPI: Interpreter enabled [ 0.264019] ACPI: (supports S0 S5) [ 0.268622] ACPI: Using IOAPIC for interrupt routing [ 0.335247] ACPI: No dock devices found. [ 0.336024] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug [ 0.344111] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff]) [ 0.352113] pci_root PNP0A03:00: host bridge window [io 0x0000-0x0cf7] [ 0.356025] pci_root PNP0A03:00: host bridge window [io 0x0d00-0xffff] [ 0.364025] pci_root PNP0A03:00: host bridge window [mem 0x000a0000-0x000bffff] [ 0.372025] pci_root PNP0A03:00: host bridge window [mem 0xf0000000-0xfbffffff] [ 0.387626] * Found PM-Timer Bug on the chipset. Due to workarounds for a bug, [ 0.387628] * this clock source is slow. Consider trying other clock sources [ 0.404902] pci 0000:00:01.3: quirk: [io 0xb000-0xb03f] claimed by PIIX4 ACPI [ 0.439426] pci0000:00: Unable to request _OSC control (_OSC support mask: 0x1e) [ 0.712599] ACPI: PCI Interrupt Link [LNKA] (IRQs *5 10 11) [ 0.717484] ACPI: PCI Interrupt Link [LNKB] (IRQs 5 *10 11) [ 0.721426] ACPI: PCI Interrupt Link [LNKC] (IRQs 5 10 *11) [ 0.728913] ACPI: PCI Interrupt Link [LNKD] (IRQs *5 10 11) [ 0.733597] vgaarb: device added: PCI:0000:00:02.0,decodes=io+mem,owns=io+mem,locks=none [ 0.740051] vgaarb: loaded [ 0.744181] PCI: Using ACPI for IRQ routing [ 0.748926] NetLabel: Initializing [ 0.752048] NetLabel: domain hash size = 128 [ 0.756047] NetLabel: protocols = UNLABELED CIPSOv4 [ 0.760059] NetLabel: unlabeled traffic allowed by default [ 0.769501] AppArmor: AppArmor Filesystem Enabled [ 0.772066] pnp: PnP ACPI init [ 0.776059] ACPI: bus type pnp registered [ 0.780103] system 00:00: [mem 0x00000000-0x0009ffff] could not be reserved [ 0.788221] system 00:02: [io 0x10c0-0x1141] has been reserved [ 0.792052] system 00:02: [io 0xb044-0xb047] has been reserved [ 0.796167] system 00:03: [io 0x08a0-0x08a3] has been reserved [ 0.804053] system 00:03: [io 0x0cc0-0x0ccf] has been reserved [ 0.808052] system 00:03: [io 0x04d0-0x04d1] has been reserved [ 0.837911] pnp: PnP ACPI: found 12 devices [ 0.840053] ACPI: ACPI bus type pnp unregistered [ 0.852470] Switching to clocksource acpi_pm [ 0.856287] NET: Registered protocol family 2 [ 0.859241] Switched to NOHz mode on CPU #0 [ 0.864241] Switched to NOHz mode on CPU #1 [ 0.868136] IP route cache hash table entries: 131072 (order: 8, 1048576 bytes) [ 0.875651] TCP established hash table entries: 524288 (order: 11, 8388608 bytes) [ 0.883577] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes) [ 0.889431] TCP: Hash tables configured (established 524288 bind 65536) [ 0.894811] TCP reno registered [ 0.897437] UDP hash table entries: 2048 (order: 4, 65536 bytes) [ 0.902349] UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes) [ 0.907819] NET: Registered protocol family 1 [ 0.911385] pci 0000:00:00.0: Limiting direct PCI/PCI transfers [ 0.916285] pci 0000:00:01.0: PIIX3: Enabling Passive Release [ 0.921100] pci 0000:00:01.0: Activating ISA DMA hang workarounds [ 0.926530] Unpacking initramfs... [ 1.087804] Freeing initrd memory: 6956k freed [ 1.095232] PCI-DMA: Using software bounce buffering for IO (SWIOTLB) [ 1.103487] Placing 64MB software IO TLB between ffff8800ebffa000 - ffff8800efffa000 [ 1.113632] software IO TLB at phys 0xebffa000 - 0xefffa000 [ 1.121469] audit: initializing netlink socket (disabled) [ 1.128467] type=2000 audit(1383902790.128:1): initialized [ 1.166444] HugeTLB registered 2 MB page size, pre-allocated 0 pages [ 1.175658] VFS: Disk quotas dquot_6.5.2 [ 1.180758] Dquot-cache hash table entries: 512 (order 0, 4096 bytes) [ 1.189100] msgmni has been set to 1913 [ 1.194298] alg: No test for stdrng (krng) [ 1.199607] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253) [ 1.209128] io scheduler noop registered [ 1.214150] io scheduler deadline registered [ 1.219691] io scheduler cfq registered (default) [ 1.226105] Serial: 8250/16550 driver, 8 ports, IRQ sharing disabled [ 1.235613] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A [ 1.285363] 00:0a: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A [ 1.296315] Non-volatile memory driver v1.3 [ 1.301750] Linux agpgart interface v0.103 [ 1.307057] Fixed MDIO Bus: probed [ 1.311077] i8042: PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12 [ 1.323945] serio: i8042 KBD port at 0x60,0x64 irq 1 [ 1.330397] serio: i8042 AUX port at 0x60,0x64 irq 12 [ 1.337314] mousedev: PS/2 mouse device common for all mice [ 1.345744] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0 [ 1.358284] cpuidle: using governor ladder [ 1.363613] cpuidle: using governor menu [ 1.368781] EFI Variables Facility v0.08 2004-May-17 [ 1.375463] TCP cubic registered [ 1.379727] Registering the dns_resolver key type [ 1.386146] registered taskstats version 1 [ 1.393051] Magic number: 5:957:423 [ 1.402070] Freeing unused kernel memory: 1356k freed [ 1.522730] SCSI subsystem initialized [ 1.554774] scsi0 : ata_piix [ 1.558904] scsi1 : ata_piix [ 1.562690] ata1: PATA max MWDMA2 cmd 0x1f0 ctl 0x3f6 bmdma 0xc200 irq 14 [ 1.571372] ata2: PATA max MWDMA2 cmd 0x170 ctl 0x376 bmdma 0xc208 irq 15 [ 1.741495] ata1.00: ATA-7: QEMU HARDDISK, 0.10.2, max UDMA/100 [ 1.745790] ata1.00: 16777216 sectors, multi 16: LBA48 [ 1.751101] ata1.00: configured for MWDMA2 [ 1.754127] scsi 0:0:0:0: Direct-Access ATA QEMU HARDDISK 0.10 PQ: 0 ANSI: 5 FATAL: Error inserting xen_vnif (/lib/modules/3.0.13-0.27-default/updates/netfront/xen-vnif.ko): No such device [ 1.792354] rdac: device handler registered [ 1.801072] hp_sw: device handler registered [ 1.809619] alua: device handler registered [ 1.818093] emc: device handler registered Creating device nodes with udev [ 1.826564] udev: starting version 147 [ 1.859781] sd 0:0:0:0: [sda] 16777216 512-byte logical blocks: (8.58 GB/8.00 GiB) [ 1.865438] sd 0:0:0:0: [sda] Write Protect is off [ 1.889443] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn''t support DPO or FUA [ 1.899648] sda: sda1 sda2 [ 1.902157] sd 0:0:0:0: [sda] Attached SCSI disk [ 2.093978] input: ImExPS/2 Generic Explorer Mouse as /devices/platform/i8042/serio1/input/input1 mount: devpts already mounted or /dev/pts busy mount: according to mtab, devpts is already mounted on /dev/pts [ 2.164109] Refined TSC clocksource calibration: 2400.084 MHz. [ 2.169016] Switching to clocksource tsc Boot logging started on /dev/ttyS0(/dev/console) at Fri Nov 8 04:26:31 2013 Trying manual resume from /dev/hda1 resume device /dev/hda1 not found (ignoring) Trying manual resume from /dev/hda1 resume device /dev/hda1 not found (ignoring) Waiting for device /dev/hda2 to appear: ..............................Could not find /dev/hda2. Want me to fall back to /dev/hda2? (Y/n) Thanks, Dhanesh. On 11/08/2013 04:33 PM, Wei Liu wrote:> On Fri, Nov 08, 2013 at 03:48:59PM +0530, Jaya Dhanesh wrote: >> Hi, >> >> I am trying tobring up a SLES SP2 as a VM on Xen 4.1.2. When I do a >> console to the vm, I see the following logs: >> >> FATAL: Error inserting xen_vnif >> (/lib/modules/3.0.13-0.27-default/updates/netfront/xen-vnif.ko): No >> such device >> rying manual resume from /dev/hda1 >> >> resume device /dev/hda1 not found (ignoring) >> >> Trying manual resume from /dev/hda1 >> >> resume device /dev/hda1 not found (ignoring) >> >> Waiting for device /dev/hda2 to appear: [ 1.876217] input: >> ImExPS/2 Generic Explorer Mouse as >> /devices/platform/i8042/serio1/input/input1 >> >> [ 2.068106] Refined TSC clocksource calibration: 2400.083 MHz. >> >> [ 2.071086] Switching to clocksource tsc >> >> ..............................Could not find /dev/hda2. >> >> Want me to fall back to /dev/hda2? (Y/n) >> >> Any idea what the problem may be. The same thing works on another system. >> > Could you use xm create -c config and attach the full output here. > > Do you see any thing like xvda* in log? > > Wei. > >> Thanks, >> Dhanesh. >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xen.org >> http://lists.xen.org/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
On Fri, Nov 08, 2013 at 05:33:14PM +0530, Jaya Dhanesh wrote: [...]> [ 1.859781] sd 0:0:0:0: [sda] 16777216 512-byte logical blocks: > (8.58 GB/8.00 GiB) > [ 1.865438] sd 0:0:0:0: [sda] Write Protect is off > [ 1.889443] sd 0:0:0:0: [sda] Write cache: disabled, read cache: > enabled, doesn''t support DPO or FUA > [ 1.899648] sda: sda1 sda2 > [ 1.902157] sd 0:0:0:0: [sda] Attached SCSI disksda1 it is Wei.
Yes, but the same image on another system finds hda and is able to come up. On 11/08/2013 05:45 PM, Wei Liu wrote:> On Fri, Nov 08, 2013 at 05:33:14PM +0530, Jaya Dhanesh wrote: > [...] >> [ 1.859781] sd 0:0:0:0: [sda] 16777216 512-byte logical blocks: >> (8.58 GB/8.00 GiB) >> [ 1.865438] sd 0:0:0:0: [sda] Write Protect is off >> [ 1.889443] sd 0:0:0:0: [sda] Write cache: disabled, read cache: >> enabled, doesn''t support DPO or FUA >> [ 1.899648] sda: sda1 sda2 >> [ 1.902157] sd 0:0:0:0: [sda] Attached SCSI disk > sda1 it is > > Wei.
On Fri, Nov 08, 2013 at 05:50:52PM +0530, Jaya Dhanesh wrote:> Yes, but the same image on another system finds hda and is able to come up.Are you using the exact same version of Xen? Are you using the exact same config file in both places? Wei.> On 11/08/2013 05:45 PM, Wei Liu wrote: > >On Fri, Nov 08, 2013 at 05:33:14PM +0530, Jaya Dhanesh wrote: > >[...] > >>[ 1.859781] sd 0:0:0:0: [sda] 16777216 512-byte logical blocks: > >>(8.58 GB/8.00 GiB) > >>[ 1.865438] sd 0:0:0:0: [sda] Write Protect is off > >>[ 1.889443] sd 0:0:0:0: [sda] Write cache: disabled, read cache: > >>enabled, doesn''t support DPO or FUA > >>[ 1.899648] sda: sda1 sda2 > >>[ 1.902157] sd 0:0:0:0: [sda] Attached SCSI disk > >sda1 it is > > > >Wei. >
Yes On 11/08/2013 06:05 PM, Wei Liu wrote:> On Fri, Nov 08, 2013 at 05:50:52PM +0530, Jaya Dhanesh wrote: >> Yes, but the same image on another system finds hda and is able to come up. > Are you using the exact same version of Xen? Are you using the exact > same config file in both places? > > Wei. > >> On 11/08/2013 05:45 PM, Wei Liu wrote: >>> On Fri, Nov 08, 2013 at 05:33:14PM +0530, Jaya Dhanesh wrote: >>> [...] >>>> [ 1.859781] sd 0:0:0:0: [sda] 16777216 512-byte logical blocks: >>>> (8.58 GB/8.00 GiB) >>>> [ 1.865438] sd 0:0:0:0: [sda] Write Protect is off >>>> [ 1.889443] sd 0:0:0:0: [sda] Write cache: disabled, read cache: >>>> enabled, doesn''t support DPO or FUA >>>> [ 1.899648] sda: sda1 sda2 >>>> [ 1.902157] sd 0:0:0:0: [sda] Attached SCSI disk >>> sda1 it is >>> >>> Wei.
On Fri, Nov 08, 2013 at 06:07:23PM +0530, Jaya Dhanesh wrote:> YesThen probably ''ps aux | grep qemu'' and logs from qemu are useful.> On 11/08/2013 06:05 PM, Wei Liu wrote: > >On Fri, Nov 08, 2013 at 05:50:52PM +0530, Jaya Dhanesh wrote: > >>Yes, but the same image on another system finds hda and is able to come up. > >Are you using the exact same version of Xen? Are you using the exact > >same config file in both places? > > > >Wei. > > > >>On 11/08/2013 05:45 PM, Wei Liu wrote: > >>>On Fri, Nov 08, 2013 at 05:33:14PM +0530, Jaya Dhanesh wrote: > >>>[...] > >>>>[ 1.859781] sd 0:0:0:0: [sda] 16777216 512-byte logical blocks: > >>>>(8.58 GB/8.00 GiB) > >>>>[ 1.865438] sd 0:0:0:0: [sda] Write Protect is off > >>>>[ 1.889443] sd 0:0:0:0: [sda] Write cache: disabled, read cache: > >>>>enabled, doesn''t support DPO or FUA > >>>>[ 1.899648] sda: sda1 sda2 > >>>>[ 1.902157] sd 0:0:0:0: [sda] Attached SCSI disk > >>>sda1 it is > >>> > >>>Wei. >
In the qemu logs, one msg that I see in the case the vm came up is: /Register xen platform. Done register platform. / Thanks, Dhanesh. On 11/08/2013 07:47 PM, Wei Liu wrote:> On Fri, Nov 08, 2013 at 06:07:23PM +0530, Jaya Dhanesh wrote: >> Yes > Then probably ''ps aux | grep qemu'' and logs from qemu are useful. > >> On 11/08/2013 06:05 PM, Wei Liu wrote: >>> On Fri, Nov 08, 2013 at 05:50:52PM +0530, Jaya Dhanesh wrote: >>>> Yes, but the same image on another system finds hda and is able to come up. >>> Are you using the exact same version of Xen? Are you using the exact >>> same config file in both places? >>> >>> Wei. >>> >>>> On 11/08/2013 05:45 PM, Wei Liu wrote: >>>>> On Fri, Nov 08, 2013 at 05:33:14PM +0530, Jaya Dhanesh wrote: >>>>> [...] >>>>>> [ 1.859781] sd 0:0:0:0: [sda] 16777216 512-byte logical blocks: >>>>>> (8.58 GB/8.00 GiB) >>>>>> [ 1.865438] sd 0:0:0:0: [sda] Write Protect is off >>>>>> [ 1.889443] sd 0:0:0:0: [sda] Write cache: disabled, read cache: >>>>>> enabled, doesn''t support DPO or FUA >>>>>> [ 1.899648] sda: sda1 sda2 >>>>>> [ 1.902157] sd 0:0:0:0: [sda] Attached SCSI disk >>>>> sda1 it is >>>>> >>>>> Wei._______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
On Mon, Nov 11, 2013 at 12:36:15PM +0530, Jaya Dhanesh wrote:> I have attached the qemu logs here. > ps aux did not have an entry for the vm I created. >There should be a qemu process for your VM. Grepping for qemu doesn''t give you anything? It would be interesting to know the exact command line of qemu process. If qemu process crashes then there will not be one. But I cannot tell from the log whether they crashed. The main difference, as you stated in another email is that the working VM has successfully registered Xen platform device. But the reason why former one does register remains unknown. Failing to register Xen platform device makes it impossible to disconnect the emulated devices (disk, net, etc). That''s why you''re seeing hda in working VM. If would be better if you can provide more infomation such as VM config file. Wei.> Thanks, > Dhanesh. > On 11/08/2013 07:47 PM, Wei Liu wrote: > >On Fri, Nov 08, 2013 at 06:07:23PM +0530, Jaya Dhanesh wrote: > >>Yes > >Then probably ''ps aux | grep qemu'' and logs from qemu are useful. > > > >>On 11/08/2013 06:05 PM, Wei Liu wrote: > >>>On Fri, Nov 08, 2013 at 05:50:52PM +0530, Jaya Dhanesh wrote: > >>>>Yes, but the same image on another system finds hda and is able to come up. > >>>Are you using the exact same version of Xen? Are you using the exact > >>>same config file in both places? > >>> > >>>Wei. > >>> > >>>>On 11/08/2013 05:45 PM, Wei Liu wrote: > >>>>>On Fri, Nov 08, 2013 at 05:33:14PM +0530, Jaya Dhanesh wrote: > >>>>>[...] > >>>>>>[ 1.859781] sd 0:0:0:0: [sda] 16777216 512-byte logical blocks: > >>>>>>(8.58 GB/8.00 GiB) > >>>>>>[ 1.865438] sd 0:0:0:0: [sda] Write Protect is off > >>>>>>[ 1.889443] sd 0:0:0:0: [sda] Write cache: disabled, read cache: > >>>>>>enabled, doesn''t support DPO or FUA > >>>>>>[ 1.899648] sda: sda1 sda2 > >>>>>>[ 1.902157] sd 0:0:0:0: [sda] Attached SCSI disk > >>>>>sda1 it is > >>>>> > >>>>>Wei. > >> domid: 327 > config qemu network with xen bridge for tap327.0 intnet_tt.100 > config qemu network with xen bridge for tap327.1 intnet_tt.100 > config qemu network with xen bridge for tap327.2 intnet_tt.100 > config qemu network with xen bridge for tap327.3 intnet_tt.100 > config qemu network with xen bridge for tap327.4 intnet_tt.100 > config qemu network with xen bridge for tap327.5 intnet_tt.100 > config qemu network with xen bridge for tap327.6 intnet_tt.100 > config qemu network with xen bridge for tap327.7 dbg_tt.100 > Using file /root/psv-plfm-app-sim-03/vsv-#ssrsim#SSR_SIM/sobj-tt1 in read-write mode > Watching /local/domain/0/device-model/327/logdirty/cmd > Watching /local/domain/0/device-model/327/command > Watching /local/domain/327/cpu > char device redirected to /dev/pts/13 > qemu_map_cache_init nr_buckets = 10000 size 4194304 > /usr/src/packages/BUILD/xen-4.1.2-testing/tools/ioemu-dir/hw/xen_blktap.c:704: Init blktap pipes > shared page at pfn feffd > buffered io page at pfn feffb > Guest uuid = 94785e16-3f5d-2577-a8bb-695fa39b6119 > Time offset set 0 > populating video RAM at ff000000 > mapping video RAM from ff000000 > xs_read(/local/domain/0/device-model/327/xen_extended_power_mgmt): read error > xs_read(): vncpasswd get error. /vm/94785e16-3f5d-2577-a8bb-695fa39b6119/vncpasswd. > Log-dirty: no command yet. > I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 > I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 > vcpu-set: watch node error. > char device redirected to /dev/pts/17 > xen be: console-0: xen be: console-0: initialise() failed > initialise() failed > xen be: console-0: xen be: console-0: initialise() failed > initialise() failed > xen be: console-0: xen be: console-0: initialise() failed > initialise() failed > xen be: console-0: xen be: console-0: initialise() failed > initialise() failed > xen be: console-0: xen be: console-0: initialise() failed > initialise() failed > xen be: console-0: xen be: console-0: initialise() failed > initialise() failed > xen be: console-0: xen be: console-0: initialise() failed > initialise() failed > xen be: console-0: xen be: console-0: initialise() failed > initialise() failed > xen be: console-0: xen be: console-0: initialise() failed > initialise() failed > xen be: console-0: xen be: console-0: initialise() failed > initialise() failed > xen be: console-0: xen be: console-0: initialise() failed > initialise() failed > xen be: console-0: xen be: console-0: initialise() failed > initialise() failed > cirrus vga map change while on lfb mode > mapping vram to f0000000 - f0400000 >> domid: 8 > config qemu network with xen bridge for tap8.0 intnet_tt.100 > config qemu network with xen bridge for tap8.1 intnet_tt.100 > config qemu network with xen bridge for tap8.2 intnet_tt.100 > config qemu network with xen bridge for tap8.3 intnet_tt.100 > config qemu network with xen bridge for tap8.4 intnet_tt.100 > config qemu network with xen bridge for tap8.5 intnet_tt.100 > config qemu network with xen bridge for tap8.6 intnet_tt.100 > config qemu network with xen bridge for tap8.7 dbg_tt.100 > Using file /root/psv-linux-fzeq/vsv-#root#xen#13.2.79_image/sobj-ttool1 in read-write mode > Watching /local/domain/0/device-model/8/logdirty/cmd > Watching /local/domain/0/device-model/8/command > Watching /local/domain/8/cpu > char device redirected to /dev/pts/6 > qemu_map_cache_init nr_buckets = 10000 size 4194304 > /usr/src/packages/BUILD/xen-4.1.2-testing/tools/ioemu-dir/hw/xen_blktap.c:704: Init blktap pipes > shared page at pfn feffd > buffered io page at pfn feffb > Guest uuid = 157e1ddb-3393-8364-ec5e-67e4ecc5e510 > Time offset set 0 > char device redirected to /dev/pts/7 > xen be: console-0: xen be: console-0: initialise() failed > initialise() failed > populating video RAM at ff000000 > mapping video RAM from ff000000 > Register xen platform. > Done register platform. > platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. > xs_read(/local/domain/0/device-model/8/xen_extended_power_mgmt): read error > xs_read(): vncpasswd get error. /vm/157e1ddb-3393-8364-ec5e-67e4ecc5e510/vncpasswd. > Log-dirty: no command yet. > I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 > I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 > vcpu-set: watch node error. > xen be: console-0: xen be: console-0: initialise() failed > initialise() failed > xs_read(/local/domain/8/log-throttling): read error > qemu: ignoring not-understood drive `/local/domain/8/log-throttling'' > medium change watch on `/local/domain/8/log-throttling'' - unknown device, ignored > xen be: console-0: xen be: console-0: initialise() failed > initialise() failed > xen be: console-0: xen be: console-0: initialise() failed > initialise() failed > cirrus vga map change while on lfb mode > mapping vram to f0000000 - f0400000 > platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. > platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro state. > Disconnect IDE hard disk... > Disconnect SCSI hard disk... > Disconnect netifs... > region type 0 at [f3000000,f3020000). > squash iomem [f3000000, f3020000). > region type 1 at [c100,c140). > region type 0 at [f3020000,f3040000). > squash iomem [f3020000, f3040000). > region type 1 at [c140,c180). > region type 0 at [f3040000,f3060000). > squash iomem [f3040000, f3060000). > region type 1 at [c180,c1c0). > region type 0 at [f3060000,f3080000). > squash iomem [f3060000, f3080000). > region type 1 at [c1c0,c200). > region type 0 at [f3080000,f30a0000). > squash iomem [f3080000, f30a0000). > region type 1 at [c200,c240). > region type 0 at [f30a0000,f30c0000). > squash iomem [f30a0000, f30c0000). > region type 1 at [c240,c280). > region type 0 at [f30c0000,f30e0000). > squash iomem [f30c0000, f30e0000). > region type 1 at [c280,c2c0). > region type 0 at [f30e0000,f3100000). > squash iomem [f30e0000, f3100000). > region type 1 at [c2c0,c300). > Shutdown taps... > Done. > Unknown PV product 65535 loaded in guest > PV driver build 50334976 >
The config file is show below: name = "ttj" boot = "c" memory = 4096 vcpus = 2 disk = [ ''file:/root/psv-plfm-app-sim-03/vsv-#ssrsim#SSR_SIM/sobj-ttj,hda,w'' ] vif = [ ''model=e1000, mac=02:00:20:ee:64:01, bridge=intnet_tt.100'', ''model=e1000, mac=02:00:20:ee:64:02, bridge=intnet_tt.100'', ''model=e1000, mac=02:00:20:ee:64:07, bridge=intnet_tt.100''] kernel = "hvmloader" builder = "hvm" device_model = "qemu-dm" # Enable ACPI support acpi = 1# Enable serial console serial = "pty" # Enable VNC vnc = 1 vnclisten = "0.0.0.0" # Disable MSI for PCI passthrough devices pci_msitranslate = 0 # Default behavior for following events on_reboot = "destroy" # Disable Xen Platform PCI device xen_platform_pci=0 Thanks, Dhanesh. On 11/11/2013 04:00 PM, Wei Liu wrote:> On Mon, Nov 11, 2013 at 12:36:15PM +0530, Jaya Dhanesh wrote: >> I have attached the qemu logs here. >> ps aux did not have an entry for the vm I created. >> > There should be a qemu process for your VM. Grepping for qemu doesn''t > give you anything? It would be interesting to know the exact command > line of qemu process. > > If qemu process crashes then there will not be one. But I cannot tell > from the log whether they crashed. > > The main difference, as you stated in another email is that the working > VM has successfully registered Xen platform device. But the reason why > former one does register remains unknown. > > Failing to register Xen platform device makes it impossible to > disconnect the emulated devices (disk, net, etc). That''s why you''re > seeing hda in working VM. > > If would be better if you can provide more infomation such as VM config > file. > > Wei. > >> Thanks, >> Dhanesh. >> On 11/08/2013 07:47 PM, Wei Liu wrote: >>> On Fri, Nov 08, 2013 at 06:07:23PM +0530, Jaya Dhanesh wrote: >>>> Yes >>> Then probably ''ps aux | grep qemu'' and logs from qemu are useful. >>> >>>> On 11/08/2013 06:05 PM, Wei Liu wrote: >>>>> On Fri, Nov 08, 2013 at 05:50:52PM +0530, Jaya Dhanesh wrote: >>>>>> Yes, but the same image on another system finds hda and is able to come up. >>>>> Are you using the exact same version of Xen? Are you using the exact >>>>> same config file in both places? >>>>> >>>>> Wei. >>>>> >>>>>> On 11/08/2013 05:45 PM, Wei Liu wrote: >>>>>>> On Fri, Nov 08, 2013 at 05:33:14PM +0530, Jaya Dhanesh wrote: >>>>>>> [...] >>>>>>>> [ 1.859781] sd 0:0:0:0: [sda] 16777216 512-byte logical blocks: >>>>>>>> (8.58 GB/8.00 GiB) >>>>>>>> [ 1.865438] sd 0:0:0:0: [sda] Write Protect is off >>>>>>>> [ 1.889443] sd 0:0:0:0: [sda] Write cache: disabled, read cache: >>>>>>>> enabled, doesn''t support DPO or FUA >>>>>>>> [ 1.899648] sda: sda1 sda2 >>>>>>>> [ 1.902157] sd 0:0:0:0: [sda] Attached SCSI disk >>>>>>> sda1 it is >>>>>>> >>>>>>> Wei. >> >> domid: 327 >> config qemu network with xen bridge for tap327.0 intnet_tt.100 >> config qemu network with xen bridge for tap327.1 intnet_tt.100 >> config qemu network with xen bridge for tap327.2 intnet_tt.100 >> config qemu network with xen bridge for tap327.3 intnet_tt.100 >> config qemu network with xen bridge for tap327.4 intnet_tt.100 >> config qemu network with xen bridge for tap327.5 intnet_tt.100 >> config qemu network with xen bridge for tap327.6 intnet_tt.100 >> config qemu network with xen bridge for tap327.7 dbg_tt.100 >> Using file /root/psv-plfm-app-sim-03/vsv-#ssrsim#SSR_SIM/sobj-tt1 in read-write mode >> Watching /local/domain/0/device-model/327/logdirty/cmd >> Watching /local/domain/0/device-model/327/command >> Watching /local/domain/327/cpu >> char device redirected to /dev/pts/13 >> qemu_map_cache_init nr_buckets = 10000 size 4194304 >> /usr/src/packages/BUILD/xen-4.1.2-testing/tools/ioemu-dir/hw/xen_blktap.c:704: Init blktap pipes >> shared page at pfn feffd >> buffered io page at pfn feffb >> Guest uuid = 94785e16-3f5d-2577-a8bb-695fa39b6119 >> Time offset set 0 >> populating video RAM at ff000000 >> mapping video RAM from ff000000 >> xs_read(/local/domain/0/device-model/327/xen_extended_power_mgmt): read error >> xs_read(): vncpasswd get error. /vm/94785e16-3f5d-2577-a8bb-695fa39b6119/vncpasswd. >> Log-dirty: no command yet. >> I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 >> I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 >> vcpu-set: watch node error. >> char device redirected to /dev/pts/17 >> xen be: console-0: xen be: console-0: initialise() failed >> initialise() failed >> xen be: console-0: xen be: console-0: initialise() failed >> initialise() failed >> xen be: console-0: xen be: console-0: initialise() failed >> initialise() failed >> xen be: console-0: xen be: console-0: initialise() failed >> initialise() failed >> xen be: console-0: xen be: console-0: initialise() failed >> initialise() failed >> xen be: console-0: xen be: console-0: initialise() failed >> initialise() failed >> xen be: console-0: xen be: console-0: initialise() failed >> initialise() failed >> xen be: console-0: xen be: console-0: initialise() failed >> initialise() failed >> xen be: console-0: xen be: console-0: initialise() failed >> initialise() failed >> xen be: console-0: xen be: console-0: initialise() failed >> initialise() failed >> xen be: console-0: xen be: console-0: initialise() failed >> initialise() failed >> xen be: console-0: xen be: console-0: initialise() failed >> initialise() failed >> cirrus vga map change while on lfb mode >> mapping vram to f0000000 - f0400000 >> >> domid: 8 >> config qemu network with xen bridge for tap8.0 intnet_tt.100 >> config qemu network with xen bridge for tap8.1 intnet_tt.100 >> config qemu network with xen bridge for tap8.2 intnet_tt.100 >> config qemu network with xen bridge for tap8.3 intnet_tt.100 >> config qemu network with xen bridge for tap8.4 intnet_tt.100 >> config qemu network with xen bridge for tap8.5 intnet_tt.100 >> config qemu network with xen bridge for tap8.6 intnet_tt.100 >> config qemu network with xen bridge for tap8.7 dbg_tt.100 >> Using file /root/psv-linux-fzeq/vsv-#root#xen#13.2.79_image/sobj-ttool1 in read-write mode >> Watching /local/domain/0/device-model/8/logdirty/cmd >> Watching /local/domain/0/device-model/8/command >> Watching /local/domain/8/cpu >> char device redirected to /dev/pts/6 >> qemu_map_cache_init nr_buckets = 10000 size 4194304 >> /usr/src/packages/BUILD/xen-4.1.2-testing/tools/ioemu-dir/hw/xen_blktap.c:704: Init blktap pipes >> shared page at pfn feffd >> buffered io page at pfn feffb >> Guest uuid = 157e1ddb-3393-8364-ec5e-67e4ecc5e510 >> Time offset set 0 >> char device redirected to /dev/pts/7 >> xen be: console-0: xen be: console-0: initialise() failed >> initialise() failed >> populating video RAM at ff000000 >> mapping video RAM from ff000000 >> Register xen platform. >> Done register platform. >> platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. >> xs_read(/local/domain/0/device-model/8/xen_extended_power_mgmt): read error >> xs_read(): vncpasswd get error. /vm/157e1ddb-3393-8364-ec5e-67e4ecc5e510/vncpasswd. >> Log-dirty: no command yet. >> I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 >> I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 >> vcpu-set: watch node error. >> xen be: console-0: xen be: console-0: initialise() failed >> initialise() failed >> xs_read(/local/domain/8/log-throttling): read error >> qemu: ignoring not-understood drive `/local/domain/8/log-throttling'' >> medium change watch on `/local/domain/8/log-throttling'' - unknown device, ignored >> xen be: console-0: xen be: console-0: initialise() failed >> initialise() failed >> xen be: console-0: xen be: console-0: initialise() failed >> initialise() failed >> cirrus vga map change while on lfb mode >> mapping vram to f0000000 - f0400000 >> platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. >> platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro state. >> Disconnect IDE hard disk... >> Disconnect SCSI hard disk... >> Disconnect netifs... >> region type 0 at [f3000000,f3020000). >> squash iomem [f3000000, f3020000). >> region type 1 at [c100,c140). >> region type 0 at [f3020000,f3040000). >> squash iomem [f3020000, f3040000). >> region type 1 at [c140,c180). >> region type 0 at [f3040000,f3060000). >> squash iomem [f3040000, f3060000). >> region type 1 at [c180,c1c0). >> region type 0 at [f3060000,f3080000). >> squash iomem [f3060000, f3080000). >> region type 1 at [c1c0,c200). >> region type 0 at [f3080000,f30a0000). >> squash iomem [f3080000, f30a0000). >> region type 1 at [c200,c240). >> region type 0 at [f30a0000,f30c0000). >> squash iomem [f30a0000, f30c0000). >> region type 1 at [c240,c280). >> region type 0 at [f30c0000,f30e0000). >> squash iomem [f30c0000, f30e0000). >> region type 1 at [c280,c2c0). >> region type 0 at [f30e0000,f3100000). >> squash iomem [f30e0000, f3100000). >> region type 1 at [c2c0,c300). >> Shutdown taps... >> Done. >> Unknown PV product 65535 loaded in guest >> PV driver build 50334976 >>_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
Hi Wei, This is my ps output: root@plfm-app-sim-02#ps ax | grep qemu | grep ttj 21621 ? SLl 0:06 /usr/lib/xen/bin/qemu-dm -d 223 -domain-name ttj -videoram 4 -vnc 0.0.0.0:0 -vncunused -vcpus 2 -vcpu_avail 0x3 -boot c -serial pty -acpi -watchdog-action reset -net nic,vlan=1,macaddr=02:00:20:ee:64:01,model=e1000,bridge=intnet_tt.101 -net tap,vlan=1,ifname=tap223.0,bridge=intnet_tt.101 -net nic,vlan=2,macaddr=02:00:20:ee:64:02,model=e1000,bridge=intnet_tt.101 -net tap,vlan=2,ifname=tap223.1,bridge=intnet_tt.101 -net nic,vlan=7,macaddr=02:00:20:ee:64:07,model=e1000,bridge=intnet_tt.101 -net tap,vlan=7,ifname=tap223.6,bridge=intnet_tt.101 -M xenfv Thanks, Dhanesh. On 11/11/2013 04:00 PM, Wei Liu wrote:> On Mon, Nov 11, 2013 at 12:36:15PM +0530, Jaya Dhanesh wrote: >> I have attached the qemu logs here. >> ps aux did not have an entry for the vm I created. >> > There should be a qemu process for your VM. Grepping for qemu doesn''t > give you anything? It would be interesting to know the exact command > line of qemu process. > > If qemu process crashes then there will not be one. But I cannot tell > from the log whether they crashed. > > The main difference, as you stated in another email is that the working > VM has successfully registered Xen platform device. But the reason why > former one does register remains unknown. > > Failing to register Xen platform device makes it impossible to > disconnect the emulated devices (disk, net, etc). That''s why you''re > seeing hda in working VM. > > If would be better if you can provide more infomation such as VM config > file. > > Wei. > >> Thanks, >> Dhanesh. >> On 11/08/2013 07:47 PM, Wei Liu wrote: >>> On Fri, Nov 08, 2013 at 06:07:23PM +0530, Jaya Dhanesh wrote: >>>> Yes >>> Then probably ''ps aux | grep qemu'' and logs from qemu are useful. >>> >>>> On 11/08/2013 06:05 PM, Wei Liu wrote: >>>>> On Fri, Nov 08, 2013 at 05:50:52PM +0530, Jaya Dhanesh wrote: >>>>>> Yes, but the same image on another system finds hda and is able to come up. >>>>> Are you using the exact same version of Xen? Are you using the exact >>>>> same config file in both places? >>>>> >>>>> Wei. >>>>> >>>>>> On 11/08/2013 05:45 PM, Wei Liu wrote: >>>>>>> On Fri, Nov 08, 2013 at 05:33:14PM +0530, Jaya Dhanesh wrote: >>>>>>> [...] >>>>>>>> [ 1.859781] sd 0:0:0:0: [sda] 16777216 512-byte logical blocks: >>>>>>>> (8.58 GB/8.00 GiB) >>>>>>>> [ 1.865438] sd 0:0:0:0: [sda] Write Protect is off >>>>>>>> [ 1.889443] sd 0:0:0:0: [sda] Write cache: disabled, read cache: >>>>>>>> enabled, doesn''t support DPO or FUA >>>>>>>> [ 1.899648] sda: sda1 sda2 >>>>>>>> [ 1.902157] sd 0:0:0:0: [sda] Attached SCSI disk >>>>>>> sda1 it is >>>>>>> >>>>>>> Wei. >> >> domid: 327 >> config qemu network with xen bridge for tap327.0 intnet_tt.100 >> config qemu network with xen bridge for tap327.1 intnet_tt.100 >> config qemu network with xen bridge for tap327.2 intnet_tt.100 >> config qemu network with xen bridge for tap327.3 intnet_tt.100 >> config qemu network with xen bridge for tap327.4 intnet_tt.100 >> config qemu network with xen bridge for tap327.5 intnet_tt.100 >> config qemu network with xen bridge for tap327.6 intnet_tt.100 >> config qemu network with xen bridge for tap327.7 dbg_tt.100 >> Using file /root/psv-plfm-app-sim-03/vsv-#ssrsim#SSR_SIM/sobj-tt1 in read-write mode >> Watching /local/domain/0/device-model/327/logdirty/cmd >> Watching /local/domain/0/device-model/327/command >> Watching /local/domain/327/cpu >> char device redirected to /dev/pts/13 >> qemu_map_cache_init nr_buckets = 10000 size 4194304 >> /usr/src/packages/BUILD/xen-4.1.2-testing/tools/ioemu-dir/hw/xen_blktap.c:704: Init blktap pipes >> shared page at pfn feffd >> buffered io page at pfn feffb >> Guest uuid = 94785e16-3f5d-2577-a8bb-695fa39b6119 >> Time offset set 0 >> populating video RAM at ff000000 >> mapping video RAM from ff000000 >> xs_read(/local/domain/0/device-model/327/xen_extended_power_mgmt): read error >> xs_read(): vncpasswd get error. /vm/94785e16-3f5d-2577-a8bb-695fa39b6119/vncpasswd. >> Log-dirty: no command yet. >> I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 >> I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 >> vcpu-set: watch node error. >> char device redirected to /dev/pts/17 >> xen be: console-0: xen be: console-0: initialise() failed >> initialise() failed >> xen be: console-0: xen be: console-0: initialise() failed >> initialise() failed >> xen be: console-0: xen be: console-0: initialise() failed >> initialise() failed >> xen be: console-0: xen be: console-0: initialise() failed >> initialise() failed >> xen be: console-0: xen be: console-0: initialise() failed >> initialise() failed >> xen be: console-0: xen be: console-0: initialise() failed >> initialise() failed >> xen be: console-0: xen be: console-0: initialise() failed >> initialise() failed >> xen be: console-0: xen be: console-0: initialise() failed >> initialise() failed >> xen be: console-0: xen be: console-0: initialise() failed >> initialise() failed >> xen be: console-0: xen be: console-0: initialise() failed >> initialise() failed >> xen be: console-0: xen be: console-0: initialise() failed >> initialise() failed >> xen be: console-0: xen be: console-0: initialise() failed >> initialise() failed >> cirrus vga map change while on lfb mode >> mapping vram to f0000000 - f0400000 >> >> domid: 8 >> config qemu network with xen bridge for tap8.0 intnet_tt.100 >> config qemu network with xen bridge for tap8.1 intnet_tt.100 >> config qemu network with xen bridge for tap8.2 intnet_tt.100 >> config qemu network with xen bridge for tap8.3 intnet_tt.100 >> config qemu network with xen bridge for tap8.4 intnet_tt.100 >> config qemu network with xen bridge for tap8.5 intnet_tt.100 >> config qemu network with xen bridge for tap8.6 intnet_tt.100 >> config qemu network with xen bridge for tap8.7 dbg_tt.100 >> Using file /root/psv-linux-fzeq/vsv-#root#xen#13.2.79_image/sobj-ttool1 in read-write mode >> Watching /local/domain/0/device-model/8/logdirty/cmd >> Watching /local/domain/0/device-model/8/command >> Watching /local/domain/8/cpu >> char device redirected to /dev/pts/6 >> qemu_map_cache_init nr_buckets = 10000 size 4194304 >> /usr/src/packages/BUILD/xen-4.1.2-testing/tools/ioemu-dir/hw/xen_blktap.c:704: Init blktap pipes >> shared page at pfn feffd >> buffered io page at pfn feffb >> Guest uuid = 157e1ddb-3393-8364-ec5e-67e4ecc5e510 >> Time offset set 0 >> char device redirected to /dev/pts/7 >> xen be: console-0: xen be: console-0: initialise() failed >> initialise() failed >> populating video RAM at ff000000 >> mapping video RAM from ff000000 >> Register xen platform. >> Done register platform. >> platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. >> xs_read(/local/domain/0/device-model/8/xen_extended_power_mgmt): read error >> xs_read(): vncpasswd get error. /vm/157e1ddb-3393-8364-ec5e-67e4ecc5e510/vncpasswd. >> Log-dirty: no command yet. >> I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 >> I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 >> vcpu-set: watch node error. >> xen be: console-0: xen be: console-0: initialise() failed >> initialise() failed >> xs_read(/local/domain/8/log-throttling): read error >> qemu: ignoring not-understood drive `/local/domain/8/log-throttling'' >> medium change watch on `/local/domain/8/log-throttling'' - unknown device, ignored >> xen be: console-0: xen be: console-0: initialise() failed >> initialise() failed >> xen be: console-0: xen be: console-0: initialise() failed >> initialise() failed >> cirrus vga map change while on lfb mode >> mapping vram to f0000000 - f0400000 >> platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. >> platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro state. >> Disconnect IDE hard disk... >> Disconnect SCSI hard disk... >> Disconnect netifs... >> region type 0 at [f3000000,f3020000). >> squash iomem [f3000000, f3020000). >> region type 1 at [c100,c140). >> region type 0 at [f3020000,f3040000). >> squash iomem [f3020000, f3040000). >> region type 1 at [c140,c180). >> region type 0 at [f3040000,f3060000). >> squash iomem [f3040000, f3060000). >> region type 1 at [c180,c1c0). >> region type 0 at [f3060000,f3080000). >> squash iomem [f3060000, f3080000). >> region type 1 at [c1c0,c200). >> region type 0 at [f3080000,f30a0000). >> squash iomem [f3080000, f30a0000). >> region type 1 at [c200,c240). >> region type 0 at [f30a0000,f30c0000). >> squash iomem [f30a0000, f30c0000). >> region type 1 at [c240,c280). >> region type 0 at [f30c0000,f30e0000). >> squash iomem [f30c0000, f30e0000). >> region type 1 at [c280,c2c0). >> region type 0 at [f30e0000,f3100000). >> squash iomem [f30e0000, f3100000). >> region type 1 at [c2c0,c300). >> Shutdown taps... >> Done. >> Unknown PV product 65535 loaded in guest >> PV driver build 50334976 >>_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
On Tue, Nov 12, 2013 at 04:32:49PM +0530, Jaya Dhanesh wrote:> Hi Wei, > > This is my ps output: > > root@plfm-app-sim-02#ps ax | grep qemu | grep ttj > 21621 ? SLl 0:06 /usr/lib/xen/bin/qemu-dm -d 223 > -domain-name ttj -videoram 4 -vnc 0.0.0.0:0 -vncunused -vcpus 2 > -vcpu_avail 0x3 -boot c -serial pty -acpi -watchdog-action reset > -net > nic,vlan=1,macaddr=02:00:20:ee:64:01,model=e1000,bridge=intnet_tt.101 > -net tap,vlan=1,ifname=tap223.0,bridge=intnet_tt.101 -net > nic,vlan=2,macaddr=02:00:20:ee:64:02,model=e1000,bridge=intnet_tt.101 > -net tap,vlan=2,ifname=tap223.1,bridge=intnet_tt.101 -net > nic,vlan=7,macaddr=02:00:20:ee:64:07,model=e1000,bridge=intnet_tt.101 > -net tap,vlan=7,ifname=tap223.6,bridge=intnet_tt.101 -M xenfv >You have two VMs so you should have two qemu processes, right? Or are you saying they look identical apart from domain name? Wei.
On Tue, Nov 12, 2013 at 11:16:46AM +0530, Jaya Dhanesh wrote:> The config file is show below: > > name = "ttj" > boot = "c" > memory = 4096 > vcpus = 2 > disk = [ > ''file:/root/psv-plfm-app-sim-03/vsv-#ssrsim#SSR_SIM/sobj-ttj,hda,w'' > ] > vif = [ ''model=e1000, mac=02:00:20:ee:64:01, bridge=intnet_tt.100'', > ''model=e1000, mac=02:00:20:ee:64:02, bridge=intnet_tt.100'', > ''model=e1000, mac=02:00:20:ee:64:07, bridge=intnet_tt.100''] > > kernel = "hvmloader" > builder = "hvm" > device_model = "qemu-dm" > > # Enable ACPI support > acpi = 1# Enable serial console > serial = "pty" > > # Enable VNC > vnc = 1 > vnclisten = "0.0.0.0" > > # Disable MSI for PCI passthrough devices > pci_msitranslate = 0 > > # Default behavior for following events > on_reboot = "destroy" > > # Disable Xen Platform PCI device > xen_platform_pci=0 >Any reason to do this? AIUI 1) if you disable xen_platform_pci then you won''t unplug emulated devices, that''s why you''re seeing hda; 2) this config option is not working at the moment in qemu-upstream, I can speak for qemu-trad though. TBH I still don''t have clue why it works on one machine while not the other. It would be help to do a checksum for all binaries and libraries to see if they match. Wei.
Will a Xen reinstall work? On 11/12/2013 05:19 PM, Wei Liu wrote:> On Tue, Nov 12, 2013 at 11:16:46AM +0530, Jaya Dhanesh wrote: >> The config file is show below: >> >> name = "ttj" >> boot = "c" >> memory = 4096 >> vcpus = 2 >> disk = [ >> ''file:/root/psv-plfm-app-sim-03/vsv-#ssrsim#SSR_SIM/sobj-ttj,hda,w'' >> ] >> vif = [ ''model=e1000, mac=02:00:20:ee:64:01, bridge=intnet_tt.100'', >> ''model=e1000, mac=02:00:20:ee:64:02, bridge=intnet_tt.100'', >> ''model=e1000, mac=02:00:20:ee:64:07, bridge=intnet_tt.100''] >> >> kernel = "hvmloader" >> builder = "hvm" >> device_model = "qemu-dm" >> >> # Enable ACPI support >> acpi = 1# Enable serial console >> serial = "pty" >> >> # Enable VNC >> vnc = 1 >> vnclisten = "0.0.0.0" >> >> # Disable MSI for PCI passthrough devices >> pci_msitranslate = 0 >> >> # Default behavior for following events >> on_reboot = "destroy" >> >> # Disable Xen Platform PCI device >> xen_platform_pci=0 >> > Any reason to do this? > > AIUI 1) if you disable xen_platform_pci then you won''t unplug emulated > devices, that''s why you''re seeing hda; 2) this config option is not > working at the moment in qemu-upstream, I can speak for qemu-trad > though. > > TBH I still don''t have clue why it works on one machine while not the > other. It would be help to do a checksum for all binaries and libraries > to see if they match. > > Wei.
Hi Wei, By disabling xen_platform_pci=0, the vm came up fine. Not sure why this is not causing a problem on the other system. Thanks, Dhanesh. On 11/12/2013 05:16 PM, Wei Liu wrote:> On Tue, Nov 12, 2013 at 04:32:49PM +0530, Jaya Dhanesh wrote: >> Hi Wei, >> >> This is my ps output: >> >> root@plfm-app-sim-02#ps ax | grep qemu | grep ttj >> 21621 ? SLl 0:06 /usr/lib/xen/bin/qemu-dm -d 223 >> -domain-name ttj -videoram 4 -vnc 0.0.0.0:0 -vncunused -vcpus 2 >> -vcpu_avail 0x3 -boot c -serial pty -acpi -watchdog-action reset >> -net >> nic,vlan=1,macaddr=02:00:20:ee:64:01,model=e1000,bridge=intnet_tt.101 >> -net tap,vlan=1,ifname=tap223.0,bridge=intnet_tt.101 -net >> nic,vlan=2,macaddr=02:00:20:ee:64:02,model=e1000,bridge=intnet_tt.101 >> -net tap,vlan=2,ifname=tap223.1,bridge=intnet_tt.101 -net >> nic,vlan=7,macaddr=02:00:20:ee:64:07,model=e1000,bridge=intnet_tt.101 >> -net tap,vlan=7,ifname=tap223.6,bridge=intnet_tt.101 -M xenfv >> > You have two VMs so you should have two qemu processes, right? Or are > you saying they look identical apart from domain name? > > Wei.
On Wed, Nov 13, 2013 at 03:52:57PM +0530, Jaya Dhanesh wrote:> Hi Wei, > > By disabling xen_platform_pci=0, the vm came up fine. Not sure why > this is not causing > a problem on the other system. >Then as I said, you probably need to double check if everything is really identical. Wei.> Thanks, > Dhanesh. > On 11/12/2013 05:16 PM, Wei Liu wrote: > >On Tue, Nov 12, 2013 at 04:32:49PM +0530, Jaya Dhanesh wrote: > >>Hi Wei, > >> > >>This is my ps output: > >> > >>root@plfm-app-sim-02#ps ax | grep qemu | grep ttj > >>21621 ? SLl 0:06 /usr/lib/xen/bin/qemu-dm -d 223 > >>-domain-name ttj -videoram 4 -vnc 0.0.0.0:0 -vncunused -vcpus 2 > >>-vcpu_avail 0x3 -boot c -serial pty -acpi -watchdog-action reset > >>-net > >>nic,vlan=1,macaddr=02:00:20:ee:64:01,model=e1000,bridge=intnet_tt.101 > >>-net tap,vlan=1,ifname=tap223.0,bridge=intnet_tt.101 -net > >>nic,vlan=2,macaddr=02:00:20:ee:64:02,model=e1000,bridge=intnet_tt.101 > >>-net tap,vlan=2,ifname=tap223.1,bridge=intnet_tt.101 -net > >>nic,vlan=7,macaddr=02:00:20:ee:64:07,model=e1000,bridge=intnet_tt.101 > >>-net tap,vlan=7,ifname=tap223.6,bridge=intnet_tt.101 -M xenfv > >> > >You have two VMs so you should have two qemu processes, right? Or are > >you saying they look identical apart from domain name? > > > >Wei. >
On Wed, Nov 13, 2013 at 02:05:06PM +0530, Jaya Dhanesh wrote:> Will a Xen reinstall work?If all you need is to make it work instead of debugging the system, reinstallation might help, but you need to make sure there''s no stale binaries in the system. Wei.> On 11/12/2013 05:19 PM, Wei Liu wrote: > >On Tue, Nov 12, 2013 at 11:16:46AM +0530, Jaya Dhanesh wrote: > >>The config file is show below: > >> > >>name = "ttj" > >>boot = "c" > >>memory = 4096 > >>vcpus = 2 > >>disk = [ > >>''file:/root/psv-plfm-app-sim-03/vsv-#ssrsim#SSR_SIM/sobj-ttj,hda,w'' > >>] > >>vif = [ ''model=e1000, mac=02:00:20:ee:64:01, bridge=intnet_tt.100'', > >>''model=e1000, mac=02:00:20:ee:64:02, bridge=intnet_tt.100'', > >>''model=e1000, mac=02:00:20:ee:64:07, bridge=intnet_tt.100''] > >> > >>kernel = "hvmloader" > >>builder = "hvm" > >>device_model = "qemu-dm" > >> > >># Enable ACPI support > >>acpi = 1# Enable serial console > >>serial = "pty" > >> > >># Enable VNC > >>vnc = 1 > >>vnclisten = "0.0.0.0" > >> > >># Disable MSI for PCI passthrough devices > >>pci_msitranslate = 0 > >> > >># Default behavior for following events > >>on_reboot = "destroy" > >> > >># Disable Xen Platform PCI device > >>xen_platform_pci=0 > >> > >Any reason to do this? > > > >AIUI 1) if you disable xen_platform_pci then you won''t unplug emulated > >devices, that''s why you''re seeing hda; 2) this config option is not > >working at the moment in qemu-upstream, I can speak for qemu-trad > >though. > > > >TBH I still don''t have clue why it works on one machine while not the > >other. It would be help to do a checksum for all binaries and libraries > >to see if they match. > > > >Wei. >