domU won't recognise my block devices

classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|

domU won't recognise my block devices

James Harper
With the following in my config file:

disk = [ 'phy:vg00/mail2-root,hda1,w', 'phy:vg00/mail2-swap,hda2,w' ]

root = "/dev/hda1 ro"

My domU says:

VFS: Cannot open root device "hda1" or unknown-block(3,1)

I am using a -xen kernel (not xen0 or xenU) with the as-shipped config
with the exception that I have AoE compiled as a module.

Any suggestions?

Thanks

James

_______________________________________________
Xen-devel mailing list
[hidden email]
http://lists.xensource.com/xen-devel
Reply | Threaded
Open this post in threaded view
|

RE: domU won't recognise my block devices

Ian Pratt
 > With the following in my config file:

>
> disk = [ 'phy:vg00/mail2-root,hda1,w', 'phy:vg00/mail2-swap,hda2,w' ]
>
> root = "/dev/hda1 ro"
>
> My domU says:
>
> VFS: Cannot open root device "hda1" or unknown-block(3,1)
>
> I am using a -xen kernel (not xen0 or xenU) with the
> as-shipped config with the exception that I have AoE compiled
> as a module.
>
> Any suggestions?

Please can you post the full boot messages from the domU. Is the AoE
module loaded (e.g. by an initrd?)

Ian

_______________________________________________
Xen-devel mailing list
[hidden email]
http://lists.xensource.com/xen-devel
Reply | Threaded
Open this post in threaded view
|

RE: domU won't recognise my block devices

James Harper
In reply to this post by James Harper
No initrd. AoE is only used by dom0. Boot messages follow:

Using config file "mail2".
Started domain mail2
Linux version 2.6.12.6-xen ([hidden email]) (gcc version
4.0.2 (Debian 4.0.2-2)) #1 SMP Wed Nov 30 19:24:27 EST 2005
BIOS-provided physical RAM map:
 Xen: 0000000000000000 - 0000000008000000 (usable)
0MB HIGHMEM available.
136MB LOWMEM available.
ACPI in unprivileged domain disabled
IRQ lockup detection disabled
Built 1 zonelists
Kernel command line:  root=/dev/hda1 ro  4 VMID=2
Initializing CPU#0
PID hash table entries: 1024 (order: 10, 16384 bytes)
Xen reported: 498.679 MHz processor.
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Software IO TLB disabled
vmalloc area: c9000000-fb7fe000, maxmem 34000000
Memory: 125244k/139264k available (2228k kernel code, 5472k reserved,
891k data, 192k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode...
Ok.
Security Framework v1.0.0 initialized
SELinux:  Disabled at boot.
Capability LSM initialized
Mount-cache hash table entries: 512
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 512K
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... disabled
Brought up 1 CPUs
NET: Registered protocol family 16
Enabling SMP...
Initializing CPU#1
Brought up 2 CPUs
ACPI: Subsystem revision 20050309
ACPI: Interpreter disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
xen_mem: Initialising balloon driver.
usbcore: registered new driver usbfs
usbcore: registered new driver hub
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a
report
PCI: System does not support PCI
PCI: System does not support PCI
Grant table initialized
IA-32 Microcode Update Driver: v1.14-xen <[hidden email]>
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
devfs: 2004-01-31 Richard Gooch ([hidden email])
devfs: boot_options: 0x0
Initializing Cryptographic API
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
PNP: No PS/2 controller found. Probing ports directly.
i8042.c: No controller found.
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
Xen virtual console successfully installed as tty1
Event-channel device installed.
netfront: Initialising virtual ethernet driver.
Registering block device major 3
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 50MHz system bus speed for PIO modes; override with
idebus=xx
ide-floppy driver 0.99.newide
mice: PS/2 mouse device common for all mice
NET: Registered protocol family 2
IP: routing cache hash table of 1024 buckets, 8Kbytes
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
NET: Registered protocol family 8
NET: Registered protocol family 20
VFS: Cannot open root device "hda1" or unknown-block(3,1)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(3,1)


> -----Original Message-----
> From: Ian Pratt [mailto:[hidden email]]
> Sent: Thursday, 1 December 2005 12:35
> To: James Harper; [hidden email]
> Cc: [hidden email]
> Subject: RE: [Xen-devel] domU won't recognise my block devices
>
>  > With the following in my config file:
> >
> > disk = [ 'phy:vg00/mail2-root,hda1,w', 'phy:vg00/mail2-swap,hda2,w'
]

> >
> > root = "/dev/hda1 ro"
> >
> > My domU says:
> >
> > VFS: Cannot open root device "hda1" or unknown-block(3,1)
> >
> > I am using a -xen kernel (not xen0 or xenU) with the
> > as-shipped config with the exception that I have AoE compiled
> > as a module.
> >
> > Any suggestions?
>
> Please can you post the full boot messages from the domU. Is the AoE
> module loaded (e.g. by an initrd?)
>
> Ian


_______________________________________________
Xen-devel mailing list
[hidden email]
http://lists.xensource.com/xen-devel
Reply | Threaded
Open this post in threaded view
|

RE: domU won't recognise my block devices

James Harper
In reply to this post by James Harper
And if it helps, here's the related output from xend.log:

[2005-12-01 13:05:01 xend.XendDomainInfo] DEBUG (XendDomainInfo:177)
XendDomainInfo.create(['vm', ['name', 'mail2'], ['memory', '128'],
['image', ['linux', ['kernel', '/boot/vmlinuz-2.6.12.6-xen'], ['root',
'/dev/hda1 ro'], ['args', ' 4 VMID=2'], ['vcpus', '2'], ['vcpus', '2'],
['boot', 'c']]], ['device', ['vbd', ['uname', 'phy:vg00/mail2-root'],
['dev', 'hda1'], ['mode', 'w']]], ['device', ['vbd', ['uname',
'phy:vg00/mail2-swap'], ['dev', 'hda2'], ['mode', 'w']]], ['device',
['vif', ['mac', 'FE:FD:01:00:02:01'], ['bridge', 'br1']]]])
[2005-12-01 13:05:01 xend.XendDomainInfo] DEBUG (XendDomainInfo:282)
parseConfig: config is ['vm', ['name', 'mail2'], ['memory', '128'],
['image', ['linux', ['kernel', '/boot/vmlinuz-2.6.12.6-xen'], ['root',
'/dev/hda1 ro'], ['args', ' 4 VMID=2'], ['vcpus', '2'], ['vcpus', '2'],
['boot', 'c']]], ['device', ['vbd', ['uname', 'phy:vg00/mail2-root'],
['dev', 'hda1'], ['mode', 'w']]], ['device', ['vbd', ['uname',
'phy:vg00/mail2-swap'], ['dev', 'hda2'], ['mode', 'w']]], ['device',
['vif', ['mac', 'FE:FD:01:00:02:01'], ['bridge', 'br1']]]]
[2005-12-01 13:05:01 xend.XendDomainInfo] DEBUG (XendDomainInfo:336)
parseConfig: result is {'ssidref': None, 'uuid': None, 'on_crash': None,
'on_reboot': None, 'image': ['linux', ['kernel',
'/boot/vmlinuz-2.6.12.6-xen'], ['root', '/dev/hda1 ro'], ['args', ' 4
VMID=2'], ['vcpus', '2'], ['vcpus', '2'], ['boot', 'c']], 'on_poweroff':
None, 'name': 'mail2', 'backend': [], 'vcpus': 2, 'cpu_weight': None,
'vcpu_avail': None, 'memory': 128, 'device': [('vbd', ['vbd', ['uname',
'phy:vg00/mail2-root'], ['dev', 'hda1'], ['mode', 'w']]), ('vbd',
['vbd', ['uname', 'phy:vg00/mail2-swap'], ['dev', 'hda2'], ['mode',
'w']]), ('vif', ['vif', ['mac', 'FE:FD:01:00:02:01'], ['bridge',
'br1']])], 'bootloader': None, 'cpu': None, 'maxmem': None}
[2005-12-01 13:05:01 xend.XendDomainInfo] DEBUG (XendDomainInfo:1064)
XendDomainInfo.construct: None 0
[2005-12-01 13:05:01 xend.XendDomainInfo] DEBUG (XendDomainInfo:1096)
XendDomainInfo.initDomain: 13 1.0
[2005-12-01 13:05:01 xend] INFO (image:132) buildDomain os=linux dom=13
vcpus=2
[2005-12-01 13:05:01 xend] DEBUG (image:170) dom            = 13
[2005-12-01 13:05:01 xend] DEBUG (image:171) image          =
/boot/vmlinuz-2.6.12.6-xen
[2005-12-01 13:05:01 xend] DEBUG (image:172) store_evtchn   = 1
[2005-12-01 13:05:01 xend] DEBUG (image:173) console_evtchn = 2
[2005-12-01 13:05:01 xend] DEBUG (image:174) cmdline        =
root=/dev/hda1 ro  4 VMID=2
[2005-12-01 13:05:01 xend] DEBUG (image:175) ramdisk        =
[2005-12-01 13:05:01 xend] DEBUG (image:176) vcpus          = 2
[2005-12-01 13:05:01 xend] DEBUG (DevController:101) DevController:
writing {'virtual-device': '769', 'backend-id': '0', 'state': '1',
'backend': '/local/domain/0/backend/vbd/13/769'} to
/local/domain/13/device/vbd/769.
[2005-12-01 13:05:01 xend] DEBUG (DevController:103) DevController:
writing {'domain': 'mail2', 'frontend':
'/local/domain/13/device/vbd/769', 'dev': 'hda1', 'state': '1',
'params': 'vg00/mail2-root', 'mode': 'w', 'frontend-id': '13', 'type':
'phy'} to /local/domain/0/backend/vbd/13/769.
[2005-12-01 13:05:01 xend] DEBUG (DevController:101) DevController:
writing {'virtual-device': '770', 'backend-id': '0', 'state': '1',
'backend': '/local/domain/0/backend/vbd/13/770'} to
/local/domain/13/device/vbd/770.
[2005-12-01 13:05:01 xend] DEBUG (DevController:103) DevController:
writing {'domain': 'mail2', 'frontend':
'/local/domain/13/device/vbd/770', 'dev': 'hda2', 'state': '1',
'params': 'vg00/mail2-swap', 'mode': 'w', 'frontend-id': '13', 'type':
'phy'} to /local/domain/0/backend/vbd/13/770.
[2005-12-01 13:05:01 xend] DEBUG (DevController:101) DevController:
writing {'backend-id': '0', 'mac': 'FE:FD:01:00:02:01', 'handle': '0',
'state': '1', 'backend': '/local/domain/0/backend/vif/13/0'} to
/local/domain/13/device/vif/0.
[2005-12-01 13:05:01 xend] DEBUG (DevController:103) DevController:
writing {'bridge': 'br1', 'domain': 'mail2', 'handle': '0', 'script':
'/etc/xen/scripts/vif-bridge', 'state': '1', 'frontend':
'/local/domain/13/device/vif/0', 'mac': 'FE:FD:01:00:02:01',
'frontend-id': '13'} to /local/domain/0/backend/vif/13/0.
[2005-12-01 13:05:01 xend.XendDomainInfo] DEBUG (XendDomainInfo:602)
Storing VM details: {'ssidref': '0', 'uuid':
'3f7de8a4-03e7dd27-ebf684b2-10d41b25', 'on_reboot': 'restart', 'image':
"(linux (kernel /boot/vmlinuz-2.6.12.6-xen) (root '/dev/hda1 ro') (args
' 4 VMID=2') (vcpus 2) (vcpus 2) (boot c))", 'on_poweroff': 'destroy',
'name': 'mail2', 'vcpus': '2', 'vcpu_avail': '3', 'memory': '128',
'on_crash': 'restart', 'start_time': '1133402701.87', 'maxmem': '128'}
[2005-12-01 13:05:01 xend.XendDomainInfo] DEBUG (XendDomainInfo:627)
Storing domain details: {'console/ring-ref': '60122', 'console/port':
'2', 'name': 'mail2', 'console/limit': '1048576', 'vm':
'/vm/3f7de8a4-03e7dd27-ebf684b2-10d41b25', 'domid': '13',
'cpu/0/availability': 'online', 'memory/target': '131072',
'store/ring-ref': '60123', 'cpu/1/availability': 'online', 'store/port':
'1'}
[2005-12-01 13:05:02 xend] DEBUG (DevController:119) Waiting for devices
vif.
[2005-12-01 13:05:02 xend] DEBUG (DevController:125) Waiting for 0.
[2005-12-01 13:05:02 xend] DEBUG (DevController:398)
hotplugStatusCallback /local/domain/0/backend/vif/13/0/hotplug-status.
[2005-12-01 13:05:02 xend] DEBUG (DevController:398)
hotplugStatusCallback /local/domain/0/backend/vif/13/0/hotplug-status.
[2005-12-01 13:05:02 xend] DEBUG (DevController:415)
hotplugStatusCallback 1.
[2005-12-01 13:05:02 xend] DEBUG (DevController:119) Waiting for devices
usb.
[2005-12-01 13:05:02 xend] DEBUG (DevController:119) Waiting for devices
vbd.
[2005-12-01 13:05:02 xend] DEBUG (DevController:125) Waiting for 769.
[2005-12-01 13:05:02 xend] DEBUG (DevController:398)
hotplugStatusCallback /local/domain/0/backend/vbd/13/769/hotplug-status.
[2005-12-01 13:05:02 xend] DEBUG (DevController:415)
hotplugStatusCallback 1.
[2005-12-01 13:05:02 xend] DEBUG (DevController:125) Waiting for 770.
[2005-12-01 13:05:02 xend] DEBUG (DevController:398)
hotplugStatusCallback /local/domain/0/backend/vbd/13/770/hotplug-status.
[2005-12-01 13:05:02 xend] DEBUG (DevController:415)
hotplugStatusCallback 1.
[2005-12-01 13:05:02 xend] DEBUG (DevController:119) Waiting for devices
pci.
[2005-12-01 13:05:02 xend] DEBUG (DevController:119) Waiting for devices
ioports.
[2005-12-01 13:05:02 xend] DEBUG (DevController:119) Waiting for devices
vtpm.
[2005-12-01 13:05:02 xend] INFO (XendDomain:353) Domain mail2 (13)
unpaused.
[2005-12-01 13:05:07 xend.XendDomainInfo] WARNING (XendDomainInfo:740)
Domain has crashed: name=mail2 id=13.
[2005-12-01 13:05:07 xend.XendDomainInfo] DEBUG (XendDomainInfo:1194)
XendDomainInfo.destroyDomain(13)
[2005-12-01 13:05:08 xend.XendDomainInfo] DEBUG (XendDomainInfo:177)
XendDomainInfo.create(['domain', ['domid', 13], ['uuid',
'3f7de8a4-03e7dd27-ebf684b2-10d41b25'], ['ssidref', 0], ['vcpus', 2],
['vcpu_avail', 3], ['cpu_weight', 1.0], ['memory', 128], ['maxmem',
128], ['name', 'mail2'], ['on_poweroff', 'destroy'], ['on_reboot',
'restart'], ['on_crash', 'restart'], ['image', ['linux', ['kernel',
'/boot/vmlinuz-2.6.12.6-xen'], ['root', '/dev/hda1 ro'], ['args', ' 4
VMID=2'], ['vcpus', '2'], ['vcpus', '2'], ['boot', 'c']]], ['device',
['vbd', ['uname', 'phy:vg00/mail2-root'], ['dev', 'hda1'], ['mode',
'w']]], ['device', ['vbd', ['uname', 'phy:vg00/mail2-swap'], ['dev',
'hda2'], ['mode', 'w']]], ['device', ['vif', ['mac',
'FE:FD:01:00:02:01'], ['bridge', 'br1']]], ['state', '----c-'],
['shutdown_reason', 'crash'], ['cpu_time', 1.1790098010000001],
['vcpus', 2], ['online_vcpus', 2], ['up_time', '6.00319099426'],
['start_time', '1133402701.87'], ['store_mfn', 60123], ['console_mfn',
60122]])
[2005-12-01 13:05:08 xend.XendDomainInfo] DEBUG (XendDomainInfo:282)
parseConfig: config is ['domain', ['domid', 13], ['uuid',
'3f7de8a4-03e7dd27-ebf684b2-10d41b25'], ['ssidref', 0], ['vcpus', 2],
['vcpu_avail', 3], ['cpu_weight', 1.0], ['memory', 128], ['maxmem',
128], ['name', 'mail2'], ['on_poweroff', 'destroy'], ['on_reboot',
'restart'], ['on_crash', 'restart'], ['image', ['linux', ['kernel',
'/boot/vmlinuz-2.6.12.6-xen'], ['root', '/dev/hda1 ro'], ['args', ' 4
VMID=2'], ['vcpus', '2'], ['vcpus', '2'], ['boot', 'c']]], ['device',
['vbd', ['uname', 'phy:vg00/mail2-root'], ['dev', 'hda1'], ['mode',
'w']]], ['device', ['vbd', ['uname', 'phy:vg00/mail2-swap'], ['dev',
'hda2'], ['mode', 'w']]], ['device', ['vif', ['mac',
'FE:FD:01:00:02:01'], ['bridge', 'br1']]], ['state', '----c-'],
['shutdown_reason', 'crash'], ['cpu_time', 1.1790098010000001],
['vcpus', 2], ['online_vcpus', 2], ['up_time', '6.00319099426'],
['start_time', '1133402701.87'], ['store_mfn', 60123], ['console_mfn',
60122]]
[2005-12-01 13:05:08 xend.XendDomainInfo] DEBUG (XendDomainInfo:336)
parseConfig: result is {'ssidref': 0, 'uuid':
'3f7de8a4-03e7dd27-ebf684b2-10d41b25', 'on_crash': 'restart',
'on_reboot': 'restart', 'image': ['linux', ['kernel',
'/boot/vmlinuz-2.6.12.6-xen'], ['root', '/dev/hda1 ro'], ['args', ' 4
VMID=2'], ['vcpus', '2'], ['vcpus', '2'], ['boot', 'c']], 'on_poweroff':
'destroy', 'name': 'mail2', 'backend': [], 'vcpus': 2, 'cpu_weight':
1.0, 'vcpu_avail': 3, 'memory': 128, 'device': [('vbd', ['vbd',
['uname', 'phy:vg00/mail2-root'], ['dev', 'hda1'], ['mode', 'w']]),
('vbd', ['vbd', ['uname', 'phy:vg00/mail2-swap'], ['dev', 'hda2'],
['mode', 'w']]), ('vif', ['vif', ['mac', 'FE:FD:01:00:02:01'],
['bridge', 'br1']])], 'bootloader': None, 'cpu': None, 'maxmem': 128}
[2005-12-01 13:05:08 xend.XendDomainInfo] DEBUG (XendDomainInfo:1064)
XendDomainInfo.construct: None 0
[2005-12-01 13:05:08 xend.XendDomainInfo] DEBUG (XendDomainInfo:1096)
XendDomainInfo.initDomain: 14 1.0
[2005-12-01 13:05:08 xend] INFO (image:132) buildDomain os=linux dom=14
vcpus=2
[2005-12-01 13:05:08 xend] DEBUG (image:170) dom            = 14
[2005-12-01 13:05:08 xend] DEBUG (image:171) image          =
/boot/vmlinuz-2.6.12.6-xen
[2005-12-01 13:05:08 xend] DEBUG (image:172) store_evtchn   = 1
[2005-12-01 13:05:08 xend] DEBUG (image:173) console_evtchn = 2
[2005-12-01 13:05:08 xend] DEBUG (image:174) cmdline        =
root=/dev/hda1 ro  4 VMID=2
[2005-12-01 13:05:08 xend] DEBUG (image:175) ramdisk        =
[2005-12-01 13:05:08 xend] DEBUG (image:176) vcpus          = 2
[2005-12-01 13:05:08 xend] DEBUG (DevController:101) DevController:
writing {'virtual-device': '769', 'backend-id': '0', 'state': '1',
'backend': '/local/domain/0/backend/vbd/14/769'} to
/local/domain/14/device/vbd/769.
[2005-12-01 13:05:08 xend] DEBUG (DevController:103) DevController:
writing {'domain': 'mail2', 'frontend':
'/local/domain/14/device/vbd/769', 'dev': 'hda1', 'state': '1',
'params': 'vg00/mail2-root', 'mode': 'w', 'frontend-id': '14', 'type':
'phy'} to /local/domain/0/backend/vbd/14/769.
[2005-12-01 13:05:08 xend] DEBUG (DevController:101) DevController:
writing {'virtual-device': '770', 'backend-id': '0', 'state': '1',
'backend': '/local/domain/0/backend/vbd/14/770'} to
/local/domain/14/device/vbd/770.
[2005-12-01 13:05:08 xend] DEBUG (DevController:103) DevController:
writing {'domain': 'mail2', 'frontend':
'/local/domain/14/device/vbd/770', 'dev': 'hda2', 'state': '1',
'params': 'vg00/mail2-swap', 'mode': 'w', 'frontend-id': '14', 'type':
'phy'} to /local/domain/0/backend/vbd/14/770.
[2005-12-01 13:05:09 xend] DEBUG (DevController:101) DevController:
writing {'virtual-device': '770', 'backend-id': '0', 'state': '1',
'backend': '/local/domain/0/backend/vbd/14/770'} to
/local/domain/14/device/vbd/770.
[2005-12-01 13:05:09 xend] DEBUG (DevController:103) DevController:
writing {'domain': 'mail2', 'frontend':
'/local/domain/14/device/vbd/770', 'dev': 'hda2', 'state': '1',
'params': 'vg00/mail2-swap', 'mode': 'w', 'frontend-id': '14', 'type':
'phy'} to /local/domain/0/backend/vbd/14/770.
[2005-12-01 13:05:09 xend] DEBUG (DevController:101) DevController:
writing {'backend-id': '0', 'mac': 'FE:FD:01:00:02:01', 'handle': '0',
'state': '1', 'backend': '/local/domain/0/backend/vif/14/0'} to
/local/domain/14/device/vif/0.
[2005-12-01 13:05:09 xend] DEBUG (DevController:103) DevController:
writing {'bridge': 'br1', 'domain': 'mail2', 'handle': '0', 'script':
'/etc/xen/scripts/vif-bridge', 'state': '1', 'frontend':
'/local/domain/14/device/vif/0', 'mac': 'FE:FD:01:00:02:01',
'frontend-id': '14'} to /local/domain/0/backend/vif/14/0.
[2005-12-01 13:05:09 xend] DEBUG (DevController:101) DevController:
writing {'backend-id': '0', 'mac': 'FE:FD:01:00:02:01', 'handle': '0',
'state': '1', 'backend': '/local/domain/0/backend/vif/14/0'} to
/local/domain/14/device/vif/0.
[2005-12-01 13:05:09 xend] DEBUG (DevController:103) DevController:
writing {'bridge': 'br1', 'domain': 'mail2', 'handle': '0', 'script':
'/etc/xen/scripts/vif-bridge', 'state': '1', 'frontend':
'/local/domain/14/device/vif/0', 'mac': 'FE:FD:01:00:02:01',
'frontend-id': '14'} to /local/domain/0/backend/vif/14/0.
[2005-12-01 13:05:09 xend] DEBUG (DevController:101) DevController:
writing {'backend-id': '0', 'mac': 'FE:FD:01:00:02:01', 'handle': '0',
'state': '1', 'backend': '/local/domain/0/backend/vif/14/0'} to
/local/domain/14/device/vif/0.
[2005-12-01 13:05:09 xend] DEBUG (DevController:103) DevController:
writing {'bridge': 'br1', 'domain': 'mail2', 'handle': '0', 'script':
'/etc/xen/scripts/vif-bridge', 'state': '1', 'frontend':
'/local/domain/14/device/vif/0', 'mac': 'FE:FD:01:00:02:01',
'frontend-id': '14'} to /local/domain/0/backend/vif/14/0.
[2005-12-01 13:05:09 xend] DEBUG (DevController:101) DevController:
writing {'backend-id': '0', 'mac': 'FE:FD:01:00:02:01', 'handle': '0',
'state': '1', 'backend': '/local/domain/0/backend/vif/14/0'} to
/local/domain/14/device/vif/0.
[2005-12-01 13:05:09 xend] DEBUG (DevController:103) DevController:
writing {'bridge': 'br1', 'domain': 'mail2', 'handle': '0', 'script':
'/etc/xen/scripts/vif-bridge', 'state': '1', 'frontend':
'/local/domain/14/device/vif/0', 'mac': 'FE:FD:01:00:02:01',
'frontend-id': '14'} to /local/domain/0/backend/vif/14/0.
[2005-12-01 13:05:09 xend] DEBUG (DevController:101) DevController:
writing {'backend-id': '0', 'mac': 'FE:FD:01:00:02:01', 'handle': '0',
'state': '1', 'backend': '/local/domain/0/backend/vif/14/0'} to
/local/domain/14/device/vif/0.
[2005-12-01 13:05:09 xend] DEBUG (DevController:103) DevController:
writing {'bridge': 'br1', 'domain': 'mail2', 'handle': '0', 'script':
'/etc/xen/scripts/vif-bridge', 'state': '1', 'frontend':
'/local/domain/14/device/vif/0', 'mac': 'FE:FD:01:00:02:01',
'frontend-id': '14'} to /local/domain/0/backend/vif/14/0.
[2005-12-01 13:05:09 xend] DEBUG (DevController:101) DevController:
writing {'backend-id': '0', 'mac': 'FE:FD:01:00:02:01', 'handle': '0',
'state': '1', 'backend': '/local/domain/0/backend/vif/14/0'} to
/local/domain/14/device/vif/0.
[2005-12-01 13:05:09 xend] DEBUG (DevController:103) DevController:
writing {'bridge': 'br1', 'domain': 'mail2', 'handle': '0', 'script':
'/etc/xen/scripts/vif-bridge', 'state': '1', 'frontend':
'/local/domain/14/device/vif/0', 'mac': 'FE:FD:01:00:02:01',
'frontend-id': '14'} to /local/domain/0/backend/vif/14/0.
[2005-12-01 13:05:10 xend] DEBUG (DevController:101) DevController:
writing {'backend-id': '0', 'mac': 'FE:FD:01:00:02:01', 'handle': '0',
'state': '1', 'backend': '/local/domain/0/backend/vif/14/0'} to
/local/domain/14/device/vif/0.
[2005-12-01 13:05:10 xend] DEBUG (DevController:103) DevController:
writing {'bridge': 'br1', 'domain': 'mail2', 'handle': '0', 'script':
'/etc/xen/scripts/vif-bridge', 'state': '1', 'frontend':
'/local/domain/14/device/vif/0', 'mac': 'FE:FD:01:00:02:01',
'frontend-id': '14'} to /local/domain/0/backend/vif/14/0.
[2005-12-01 13:05:10 xend.XendDomainInfo] DEBUG (XendDomainInfo:602)
Storing VM details: {'ssidref': '0', 'uuid':
'3f7de8a4-03e7dd27-ebf684b2-10d41b25', 'on_reboot': 'restart', 'image':
"(linux (kernel /boot/vmlinuz-2.6.12.6-xen) (root '/dev/hda1 ro') (args
' 4 VMID=2') (vcpus 2) (vcpus 2) (boot c))", 'on_poweroff': 'destroy',
'name': 'mail2', 'vcpus': '2', 'vcpu_avail': '3', 'memory': '128',
'on_crash': 'restart', 'start_time': '1133402710.04', 'maxmem': '128'}
[2005-12-01 13:05:10 xend.XendDomainInfo] DEBUG (XendDomainInfo:627)
Storing domain details: {'console/ring-ref': '33874', 'console/port':
'2', 'name': 'mail2', 'console/limit': '1048576', 'vm':
'/vm/3f7de8a4-03e7dd27-ebf684b2-10d41b25', 'domid': '14',
'cpu/0/availability': 'online', 'memory/target': '131072',
'store/ring-ref': '33875', 'cpu/1/availability': 'online', 'store/port':
'1'}
[2005-12-01 13:05:15 xend.XendDomainInfo] WARNING (XendDomainInfo:740)
Domain has crashed: name=mail2 id=14.
[2005-12-01 13:05:15 xend.XendDomainInfo] ERROR (XendDomainInfo:1326) VM
mail2 restarting too fast (7.641145 seconds since the last restart).
Refusing to restart to avoid loops.
[2005-12-01 13:05:15 xend.XendDomainInfo] DEBUG (XendDomainInfo:1186)
XendDomainInfo.destroy: domid=14
[2005-12-01 13:05:15 xend.XendDomainInfo] DEBUG (XendDomainInfo:1194)
XendDomainInfo.destroyDomain(14)


> -----Original Message-----
> From: Ian Pratt [mailto:[hidden email]]
> Sent: Thursday, 1 December 2005 12:35
> To: James Harper; [hidden email]
> Cc: [hidden email]
> Subject: RE: [Xen-devel] domU won't recognise my block devices
>
>  > With the following in my config file:
> >
> > disk = [ 'phy:vg00/mail2-root,hda1,w', 'phy:vg00/mail2-swap,hda2,w'
]

> >
> > root = "/dev/hda1 ro"
> >
> > My domU says:
> >
> > VFS: Cannot open root device "hda1" or unknown-block(3,1)
> >
> > I am using a -xen kernel (not xen0 or xenU) with the
> > as-shipped config with the exception that I have AoE compiled
> > as a module.
> >
> > Any suggestions?
>
> Please can you post the full boot messages from the domU. Is the AoE
> module loaded (e.g. by an initrd?)
>
> Ian


_______________________________________________
Xen-devel mailing list
[hidden email]
http://lists.xensource.com/xen-devel
Reply | Threaded
Open this post in threaded view
|

RE: domU won't recognise my block devices

Ian Pratt
In reply to this post by James Harper
> No initrd. AoE is only used by dom0. Boot messages follow:

It works for me... Are you sure you haven't borked your config?

Using 'sdX' or 'hdX' as the device to import a virtual disk as is rather
bad form these days anyhow. The preferred device is "xvdX".  e.g.
"xvda1"

Please can you try this (rememmer to update you root= and guest
/etc/fstab as well as the disk= stanza).

[You could try sda1 instead of hda1 too. If that still doesn't work,
have you tried importing a single device rather than two?]

Ian
 

> Using config file "mail2".
> Started domain mail2
> Linux version 2.6.12.6-xen ([hidden email]) (gcc version
> 4.0.2 (Debian 4.0.2-2)) #1 SMP Wed Nov 30 19:24:27 EST 2005
> BIOS-provided physical RAM map:
>  Xen: 0000000000000000 - 0000000008000000 (usable) 0MB
> HIGHMEM available.
> 136MB LOWMEM available.
> ACPI in unprivileged domain disabled
> IRQ lockup detection disabled
> Built 1 zonelists
> Kernel command line:  root=/dev/hda1 ro  4 VMID=2
> Initializing CPU#0 PID hash table entries: 1024 (order: 10,
> 16384 bytes) Xen reported: 498.679 MHz processor.
> Dentry cache hash table entries: 32768 (order: 5, 131072
> bytes) Inode-cache hash table entries: 16384 (order: 4, 65536
> bytes) Software IO TLB disabled vmalloc area:
> c9000000-fb7fe000, maxmem 34000000
> Memory: 125244k/139264k available (2228k kernel code, 5472k
> reserved, 891k data, 192k init, 0k highmem) Checking if this
> processor honours the WP bit even in supervisor mode...
> Ok.
> Security Framework v1.0.0 initialized
> SELinux:  Disabled at boot.
> Capability LSM initialized
> Mount-cache hash table entries: 512
> CPU: L1 I cache: 16K, L1 D cache: 16K
> CPU: L2 cache: 512K
> Enabling fast FPU save and restore... done.
> Enabling unmasked SIMD FPU exception support... done.
> Checking 'hlt' instruction... disabled
> Brought up 1 CPUs
> NET: Registered protocol family 16
> Enabling SMP...
> Initializing CPU#1
> Brought up 2 CPUs
> ACPI: Subsystem revision 20050309
> ACPI: Interpreter disabled.
> Linux Plug and Play Support v0.97 (c) Adam Belay
> xen_mem: Initialising balloon driver.
> usbcore: registered new driver usbfs
> usbcore: registered new driver hub
> PCI: Using ACPI for IRQ routing
> PCI: If a device doesn't work, try "pci=routeirq".  If it
> helps, post a report
> PCI: System does not support PCI
> PCI: System does not support PCI
> Grant table initialized
> IA-32 Microcode Update Driver: v1.14-xen <[hidden email]>
> VFS: Disk quotas dquot_6.5.1
> Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
> devfs: 2004-01-31 Richard Gooch ([hidden email])
> devfs: boot_options: 0x0
> Initializing Cryptographic API
> isapnp: Scanning for PnP cards...
> isapnp: No Plug & Play device found
> PNP: No PS/2 controller found. Probing ports directly.
> i8042.c: No controller found.
> io scheduler noop registered
> io scheduler anticipatory registered
> io scheduler deadline registered
> io scheduler cfq registered
> RAMDISK driver initialized: 16 RAM disks of 8192K size 1024
> blocksize Xen virtual console successfully installed as tty1
> Event-channel device installed.
> netfront: Initialising virtual ethernet driver.
> Registering block device major 3
> Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
> ide: Assuming 50MHz system bus speed for PIO modes; override
> with idebus=xx ide-floppy driver 0.99.newide
> mice: PS/2 mouse device common for all mice
> NET: Registered protocol family 2
> IP: routing cache hash table of 1024 buckets, 8Kbytes TCP
> established hash table entries: 8192 (order: 4, 65536 bytes)
> TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
> TCP: Hash tables configured (established 8192 bind 8192)
> NET: Registered protocol family 8
> NET: Registered protocol family 20
> VFS: Cannot open root device "hda1" or unknown-block(3,1)
> Please append a correct "root=" boot option Kernel panic -
> not syncing: VFS: Unable to mount root fs on
> unknown-block(3,1)
>
>
> > -----Original Message-----
> > From: Ian Pratt [mailto:[hidden email]]
> > Sent: Thursday, 1 December 2005 12:35
> > To: James Harper; [hidden email]
> > Cc: [hidden email]
> > Subject: RE: [Xen-devel] domU won't recognise my block devices
> >
> >  > With the following in my config file:
> > >
> > > disk = [ 'phy:vg00/mail2-root,hda1,w',
> 'phy:vg00/mail2-swap,hda2,w'
> ]
> > >
> > > root = "/dev/hda1 ro"
> > >
> > > My domU says:
> > >
> > > VFS: Cannot open root device "hda1" or unknown-block(3,1)
> > >
> > > I am using a -xen kernel (not xen0 or xenU) with the as-shipped
> > > config with the exception that I have AoE compiled as a module.
> > >
> > > Any suggestions?
> >
> > Please can you post the full boot messages from the domU.
> Is the AoE
> > module loaded (e.g. by an initrd?)
> >
> > Ian
>
>

_______________________________________________
Xen-devel mailing list
[hidden email]
http://lists.xensource.com/xen-devel
Reply | Threaded
Open this post in threaded view
|

RE: domU won't recognise my block devices

James Harper
In reply to this post by James Harper
Changing to xvda or sda doesn't fix anything, nor does only using one
block device.

Maybe I have some leftover cruft from a previous install or previous
debian package install... any suggestions as to the best place to start
looking?

Thanks

James



> -----Original Message-----
> From: Ian Pratt [mailto:[hidden email]]
> Sent: Thursday, 1 December 2005 13:20
> To: James Harper; [hidden email]
> Cc: [hidden email]; [hidden email]
> Subject: RE: [Xen-devel] domU won't recognise my block devices
>
> > No initrd. AoE is only used by dom0. Boot messages follow:
>
> It works for me... Are you sure you haven't borked your config?
>
> Using 'sdX' or 'hdX' as the device to import a virtual disk as is
rather

> bad form these days anyhow. The preferred device is "xvdX".  e.g.
> "xvda1"
>
> Please can you try this (rememmer to update you root= and guest
> /etc/fstab as well as the disk= stanza).
>
> [You could try sda1 instead of hda1 too. If that still doesn't work,
> have you tried importing a single device rather than two?]
>
> Ian
>
> > Using config file "mail2".
> > Started domain mail2
> > Linux version 2.6.12.6-xen ([hidden email]) (gcc version
> > 4.0.2 (Debian 4.0.2-2)) #1 SMP Wed Nov 30 19:24:27 EST 2005
> > BIOS-provided physical RAM map:
> >  Xen: 0000000000000000 - 0000000008000000 (usable) 0MB
> > HIGHMEM available.
> > 136MB LOWMEM available.
> > ACPI in unprivileged domain disabled
> > IRQ lockup detection disabled
> > Built 1 zonelists
> > Kernel command line:  root=/dev/hda1 ro  4 VMID=2
> > Initializing CPU#0 PID hash table entries: 1024 (order: 10,
> > 16384 bytes) Xen reported: 498.679 MHz processor.
> > Dentry cache hash table entries: 32768 (order: 5, 131072
> > bytes) Inode-cache hash table entries: 16384 (order: 4, 65536
> > bytes) Software IO TLB disabled vmalloc area:
> > c9000000-fb7fe000, maxmem 34000000
> > Memory: 125244k/139264k available (2228k kernel code, 5472k
> > reserved, 891k data, 192k init, 0k highmem) Checking if this
> > processor honours the WP bit even in supervisor mode...
> > Ok.
> > Security Framework v1.0.0 initialized
> > SELinux:  Disabled at boot.
> > Capability LSM initialized
> > Mount-cache hash table entries: 512
> > CPU: L1 I cache: 16K, L1 D cache: 16K
> > CPU: L2 cache: 512K
> > Enabling fast FPU save and restore... done.
> > Enabling unmasked SIMD FPU exception support... done.
> > Checking 'hlt' instruction... disabled
> > Brought up 1 CPUs
> > NET: Registered protocol family 16
> > Enabling SMP...
> > Initializing CPU#1
> > Brought up 2 CPUs
> > ACPI: Subsystem revision 20050309
> > ACPI: Interpreter disabled.
> > Linux Plug and Play Support v0.97 (c) Adam Belay
> > xen_mem: Initialising balloon driver.
> > usbcore: registered new driver usbfs
> > usbcore: registered new driver hub
> > PCI: Using ACPI for IRQ routing
> > PCI: If a device doesn't work, try "pci=routeirq".  If it
> > helps, post a report
> > PCI: System does not support PCI
> > PCI: System does not support PCI
> > Grant table initialized
> > IA-32 Microcode Update Driver: v1.14-xen <[hidden email]>
> > VFS: Disk quotas dquot_6.5.1
> > Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
> > devfs: 2004-01-31 Richard Gooch ([hidden email])
> > devfs: boot_options: 0x0
> > Initializing Cryptographic API
> > isapnp: Scanning for PnP cards...
> > isapnp: No Plug & Play device found
> > PNP: No PS/2 controller found. Probing ports directly.
> > i8042.c: No controller found.
> > io scheduler noop registered
> > io scheduler anticipatory registered
> > io scheduler deadline registered
> > io scheduler cfq registered
> > RAMDISK driver initialized: 16 RAM disks of 8192K size 1024
> > blocksize Xen virtual console successfully installed as tty1
> > Event-channel device installed.
> > netfront: Initialising virtual ethernet driver.
> > Registering block device major 3
> > Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
> > ide: Assuming 50MHz system bus speed for PIO modes; override
> > with idebus=xx ide-floppy driver 0.99.newide
> > mice: PS/2 mouse device common for all mice
> > NET: Registered protocol family 2
> > IP: routing cache hash table of 1024 buckets, 8Kbytes TCP
> > established hash table entries: 8192 (order: 4, 65536 bytes)
> > TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
> > TCP: Hash tables configured (established 8192 bind 8192)
> > NET: Registered protocol family 8
> > NET: Registered protocol family 20
> > VFS: Cannot open root device "hda1" or unknown-block(3,1)
> > Please append a correct "root=" boot option Kernel panic -
> > not syncing: VFS: Unable to mount root fs on
> > unknown-block(3,1)
> >
> >
> > > -----Original Message-----
> > > From: Ian Pratt [mailto:[hidden email]]
> > > Sent: Thursday, 1 December 2005 12:35
> > > To: James Harper; [hidden email]
> > > Cc: [hidden email]
> > > Subject: RE: [Xen-devel] domU won't recognise my block devices
> > >
> > >  > With the following in my config file:
> > > >
> > > > disk = [ 'phy:vg00/mail2-root,hda1,w',
> > 'phy:vg00/mail2-swap,hda2,w'
> > ]
> > > >
> > > > root = "/dev/hda1 ro"
> > > >
> > > > My domU says:
> > > >
> > > > VFS: Cannot open root device "hda1" or unknown-block(3,1)
> > > >
> > > > I am using a -xen kernel (not xen0 or xenU) with the as-shipped
> > > > config with the exception that I have AoE compiled as a module.
> > > >
> > > > Any suggestions?
> > >
> > > Please can you post the full boot messages from the domU.
> > Is the AoE
> > > module loaded (e.g. by an initrd?)
> > >
> > > Ian
> >
> >


_______________________________________________
Xen-devel mailing list
[hidden email]
http://lists.xensource.com/xen-devel
Reply | Threaded
Open this post in threaded view
|

RE: domU won't recognise my block devices

James Harper
In reply to this post by James Harper
> > No initrd. AoE is only used by dom0. Boot messages follow:
>
> It works for me... Are you sure you haven't borked your config?

What sort of config borking would be required?

I just tried using a file instead of an lvm device, but same error.

James

_______________________________________________
Xen-devel mailing list
[hidden email]
http://lists.xensource.com/xen-devel
Reply | Threaded
Open this post in threaded view
|

RE: domU won't recognise my block devices

James Harper
In reply to this post by James Harper
This thread
(http://lists.xensource.com/archives/html/xen-devel/2004-12/msg00536.htm
l) talks about getting the same error if devfs is compiled into the
kernel... does anyone know anything about that?

Thanks

James

> -----Original Message-----
> From: Ian Pratt [mailto:[hidden email]]
> Sent: Thursday, 1 December 2005 13:20
> To: James Harper; [hidden email]
> Cc: [hidden email]; [hidden email]
> Subject: RE: [Xen-devel] domU won't recognise my block devices
>
> > No initrd. AoE is only used by dom0. Boot messages follow:
>
> It works for me... Are you sure you haven't borked your config?
>
> Using 'sdX' or 'hdX' as the device to import a virtual disk as is
rather

> bad form these days anyhow. The preferred device is "xvdX".  e.g.
> "xvda1"
>
> Please can you try this (rememmer to update you root= and guest
> /etc/fstab as well as the disk= stanza).
>
> [You could try sda1 instead of hda1 too. If that still doesn't work,
> have you tried importing a single device rather than two?]
>
> Ian
>
> > Using config file "mail2".
> > Started domain mail2
> > Linux version 2.6.12.6-xen ([hidden email]) (gcc version
> > 4.0.2 (Debian 4.0.2-2)) #1 SMP Wed Nov 30 19:24:27 EST 2005
> > BIOS-provided physical RAM map:
> >  Xen: 0000000000000000 - 0000000008000000 (usable) 0MB
> > HIGHMEM available.
> > 136MB LOWMEM available.
> > ACPI in unprivileged domain disabled
> > IRQ lockup detection disabled
> > Built 1 zonelists
> > Kernel command line:  root=/dev/hda1 ro  4 VMID=2
> > Initializing CPU#0 PID hash table entries: 1024 (order: 10,
> > 16384 bytes) Xen reported: 498.679 MHz processor.
> > Dentry cache hash table entries: 32768 (order: 5, 131072
> > bytes) Inode-cache hash table entries: 16384 (order: 4, 65536
> > bytes) Software IO TLB disabled vmalloc area:
> > c9000000-fb7fe000, maxmem 34000000
> > Memory: 125244k/139264k available (2228k kernel code, 5472k
> > reserved, 891k data, 192k init, 0k highmem) Checking if this
> > processor honours the WP bit even in supervisor mode...
> > Ok.
> > Security Framework v1.0.0 initialized
> > SELinux:  Disabled at boot.
> > Capability LSM initialized
> > Mount-cache hash table entries: 512
> > CPU: L1 I cache: 16K, L1 D cache: 16K
> > CPU: L2 cache: 512K
> > Enabling fast FPU save and restore... done.
> > Enabling unmasked SIMD FPU exception support... done.
> > Checking 'hlt' instruction... disabled
> > Brought up 1 CPUs
> > NET: Registered protocol family 16
> > Enabling SMP...
> > Initializing CPU#1
> > Brought up 2 CPUs
> > ACPI: Subsystem revision 20050309
> > ACPI: Interpreter disabled.
> > Linux Plug and Play Support v0.97 (c) Adam Belay
> > xen_mem: Initialising balloon driver.
> > usbcore: registered new driver usbfs
> > usbcore: registered new driver hub
> > PCI: Using ACPI for IRQ routing
> > PCI: If a device doesn't work, try "pci=routeirq".  If it
> > helps, post a report
> > PCI: System does not support PCI
> > PCI: System does not support PCI
> > Grant table initialized
> > IA-32 Microcode Update Driver: v1.14-xen <[hidden email]>
> > VFS: Disk quotas dquot_6.5.1
> > Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
> > devfs: 2004-01-31 Richard Gooch ([hidden email])
> > devfs: boot_options: 0x0
> > Initializing Cryptographic API
> > isapnp: Scanning for PnP cards...
> > isapnp: No Plug & Play device found
> > PNP: No PS/2 controller found. Probing ports directly.
> > i8042.c: No controller found.
> > io scheduler noop registered
> > io scheduler anticipatory registered
> > io scheduler deadline registered
> > io scheduler cfq registered
> > RAMDISK driver initialized: 16 RAM disks of 8192K size 1024
> > blocksize Xen virtual console successfully installed as tty1
> > Event-channel device installed.
> > netfront: Initialising virtual ethernet driver.
> > Registering block device major 3
> > Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
> > ide: Assuming 50MHz system bus speed for PIO modes; override
> > with idebus=xx ide-floppy driver 0.99.newide
> > mice: PS/2 mouse device common for all mice
> > NET: Registered protocol family 2
> > IP: routing cache hash table of 1024 buckets, 8Kbytes TCP
> > established hash table entries: 8192 (order: 4, 65536 bytes)
> > TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
> > TCP: Hash tables configured (established 8192 bind 8192)
> > NET: Registered protocol family 8
> > NET: Registered protocol family 20
> > VFS: Cannot open root device "hda1" or unknown-block(3,1)
> > Please append a correct "root=" boot option Kernel panic -
> > not syncing: VFS: Unable to mount root fs on
> > unknown-block(3,1)
> >
> >
> > > -----Original Message-----
> > > From: Ian Pratt [mailto:[hidden email]]
> > > Sent: Thursday, 1 December 2005 12:35
> > > To: James Harper; [hidden email]
> > > Cc: [hidden email]
> > > Subject: RE: [Xen-devel] domU won't recognise my block devices
> > >
> > >  > With the following in my config file:
> > > >
> > > > disk = [ 'phy:vg00/mail2-root,hda1,w',
> > 'phy:vg00/mail2-swap,hda2,w'
> > ]
> > > >
> > > > root = "/dev/hda1 ro"
> > > >
> > > > My domU says:
> > > >
> > > > VFS: Cannot open root device "hda1" or unknown-block(3,1)
> > > >
> > > > I am using a -xen kernel (not xen0 or xenU) with the as-shipped
> > > > config with the exception that I have AoE compiled as a module.
> > > >
> > > > Any suggestions?
> > >
> > > Please can you post the full boot messages from the domU.
> > Is the AoE
> > > module loaded (e.g. by an initrd?)
> > >
> > > Ian
> >
> >


_______________________________________________
Xen-devel mailing list
[hidden email]
http://lists.xensource.com/xen-devel
Reply | Threaded
Open this post in threaded view
|

Re: domU won't recognise my block devices

Steven Hand
In reply to this post by James Harper

>> > No initrd. AoE is only used by dom0. Boot messages follow:
>>=20
>> It works for me... Are you sure you haven't borked your config?
>
>What sort of config borking would be required?
>
>I just tried using a file instead of an lvm device, but same error.

What cset are you using?

If it's fairly recent, can you try 'xen-bugtool'?
Otherwise can you just manually do 'xsls' and post the output?

cheers,

S.


_______________________________________________
Xen-devel mailing list
[hidden email]
http://lists.xensource.com/xen-devel
Reply | Threaded
Open this post in threaded view
|

RE: domU won't recognise my block devices

Mark Langsdorf
In reply to this post by James Harper
> > No initrd. AoE is only used by dom0. Boot messages follow:
>
> It works for me... Are you sure you haven't borked your config?

Ian, are you testing on Opterons in 64-bit mode or some other
hardware?  One of the common themes in these bug reports (see
also bugzilla #392) is 64-bit Opterons.  64-bit Intel Xeon
does not seem to be affected in the same way.

-Mark Langsdorf
AMD, Inc.


_______________________________________________
Xen-devel mailing list
[hidden email]
http://lists.xensource.com/xen-devel
Reply | Threaded
Open this post in threaded view
|

Re: domU won't recognise my block devices

James Bulpin-2
We're testing both 32 and 64 bit builds on a mixture of Xeon and
Opteron. Many of my colleagues use Opteron machines as their personal
test boxes as well. I've just fired off a test run explicitly on an
Opteron-based Sun V20z to make sure all is well: it it has booted and
started a guest just fine.

Regards,
James

Langsdorf, Mark wrote:

>>>No initrd. AoE is only used by dom0. Boot messages follow:
>>
>>It works for me... Are you sure you haven't borked your config?
>
>
> Ian, are you testing on Opterons in 64-bit mode or some other
> hardware?  One of the common themes in these bug reports (see
> also bugzilla #392) is 64-bit Opterons.  64-bit Intel Xeon
> does not seem to be affected in the same way.
>
> -Mark Langsdorf
> AMD, Inc.
>
>
> _______________________________________________
> Xen-devel mailing list
> [hidden email]
> http://lists.xensource.com/xen-devel

_______________________________________________
Xen-devel mailing list
[hidden email]
http://lists.xensource.com/xen-devel