Hey folks, I tried this with both CentOS 5.8 and Ubuntu 12.04 (beta2) and same behavior. Use virt-manager to create my VM. I had previously used the virsh commands to create an iSCSI pool (I think that is the right term) and so my iSCSI disk shows up fine in virt-manager and I can add it to the VM. The install goes well the disk is there - I can either choose to partition it manually or let it go automatic. During the install from the Ubuntu live CD I can open a shell and see the disk mounted and stuff being installed to it. After the install I can reboot from the Ubuntu live CD and I see the iSCSI disk there. I can mount stuff and look at it - looks like the install went fine. But I reboot and try to boot from the HD and it says : Boot from Hard Disk failed: could not read the boot disk FATAL: No bootable device What''s up with that? thanks, -Alan
Oh I should mention that dom0 is RHEL5.7 [root@solexa1 xen]# rpm -qa | grep -i xen xen-3.0.3-135.el5_8.2 kernel-xen-devel-2.6.18-128.el5 xen-libs-3.0.3-135.el5_8.2 kernel-xen-devel-2.6.18-308.1.1.el5 kernel-xen-2.6.18-128.el5 xen-libs-3.0.3-135.el5_8.2 kernel-xen-devel-2.6.18-274.12.1.el5 kernel-xen-2.6.18-274.12.1.el5 kernel-xen-2.6.18-308.1.1.el5 [root@solexa1 xen]# uname -a Linux solexa1 2.6.18-274.12.1.el5xen #1 SMP Tue Nov 8 21:46:04 EST 2011 x86_64 x86_64 x86_64 GNU/Linux _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
On Fri, Apr 13, 2012 at 9:31 AM, Alan McKay <alan.mckay+xen@gmail.com>wrote:> Oh I should mention that dom0 is RHEL5.7 >Ahem, sorry, 5.8 _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
anyone? anyone? Buehler? On Fri, Apr 13, 2012 at 9:29 AM, Alan McKay <alan.mckay+xen@gmail.com>wrote:> Hey folks, > > I tried this with both CentOS 5.8 and Ubuntu 12.04 (beta2) and same > behavior. > > Use virt-manager to create my VM. I had previously used the virsh > commands to create an iSCSI pool (I think that is the right term) and > so my iSCSI disk shows up fine in virt-manager and I can add it to the > VM. > > The install goes well the disk is there - I can either choose to > partition it manually or let it go automatic. During the install from > the Ubuntu live CD I can open a shell and see the disk mounted and > stuff being installed to it. > > After the install I can reboot from the Ubuntu live CD and I see the > iSCSI disk there. I can mount stuff and look at it - looks like the > install went fine. > > But I reboot and try to boot from the HD and it says : > > Boot from Hard Disk failed: could not read the boot disk > FATAL: No bootable device > > What''s up with that? > > thanks, > -Alan >_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
... tumbleweeds blow by ... :-) I''ve been getting some response on the virt-manager list and someone just told me the following, which has me a bit confused : Quote : "So to boot from iSCSI you need to use an iSCSI software initiator. Like gPXE or so. " What has me confused is that this worked fine with VirtualBox without any extra bits and pieces. Does that mean that VirtualBox has the initiator built in but Xen does not? And if not, then how is it I am able to connect the iSCSI disk to the VM (in virt-manager) in the first place? I thought the mere fact that I can connected it requires that there is an initiator on one end ( xen / virt-manager ) and target on the other end (my iSCSI server) thanks, -Alan On Fri, Apr 13, 2012 at 9:29 AM, Alan McKay <alan.mckay+xen@gmail.com>wrote:> Hey folks, > > I tried this with both CentOS 5.8 and Ubuntu 12.04 (beta2) and same > behavior. > > Use virt-manager to create my VM. I had previously used the virsh > commands to create an iSCSI pool (I think that is the right term) and > so my iSCSI disk shows up fine in virt-manager and I can add it to the > VM. > > The install goes well the disk is there - I can either choose to > partition it manually or let it go automatic. During the install from > the Ubuntu live CD I can open a shell and see the disk mounted and > stuff being installed to it. > > After the install I can reboot from the Ubuntu live CD and I see the > iSCSI disk there. I can mount stuff and look at it - looks like the > install went fine. > > But I reboot and try to boot from the HD and it says : > > Boot from Hard Disk failed: could not read the boot disk > FATAL: No bootable device > > What''s up with that? > > thanks, > -Alan >_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
On Wed, Apr 18, 2012 at 1:31 AM, Alan McKay <alan.mckay+xen@gmail.com> wrote:> ... tumbleweeds blow by ... :-) > > I''ve been getting some response on the virt-manager list and someone just > told me the following, which has me a bit confused : > > Quote : "So to boot from iSCSI you need to use an iSCSI software initiator. > Like gPXE or so. " > > What has me confused is that this worked fine with VirtualBox without any > extra bits and pieces. Does that mean that VirtualBox has the initiator > built in but Xen does not? And if not, then how is it I am able to connect > the iSCSI disk to the VM (in virt-manager) in the first place? I thought > the mere fact that I can connected it requires that there is an initiator on > one end ( xen / virt-manager ) and target on the other end (my iSCSI server)There are more than one way to use iscsi disk in xen. The easiest way, and also the one with best performance in Xen, is to import the iscsi disk in dom0 (i.e., your host). You then use it like any other disk (e.g. /dev/sda, /dev/sdb, etc. Or use /dev/disk/by-id or by-path for persistence). I''m GUESSing you import the iscsi disk using the OS installer, AND you use PV domU, which results in the disk (along with the kernel and initrd) not accesible during domU boot. If you don''t understand what I''m saying on this paragraph, just forget it, and ONLY read the previous paragraph :) -- Fajar
On Tue, Apr 17, 2012 at 9:04 PM, Fajar A. Nugraha <list@fajar.net> wrote:> The easiest way, and also the one with best performance in Xen, is to > import the iscsi disk in dom0 (i.e., your host). You then use it like > any other disk (e.g. /dev/sda, /dev/sdb, etc. Or use /dev/disk/by-id > or by-path for persistence). >That''s what I''m doing. I had to create an XML file in dom0 and made a pool which loads my iSCSI disks into /dev/disk/by-path. Then for the OS installer in domU it just shows up like a regular disk and nothing special was required. That''s the part that has me stumped. It worked just fine during the install - just during the boot is when it went awry. But the fellow on the virt-manager list says that I cannot boot from iSCSI without in initiator.> I''m GUESSing you import the iscsi disk using the OS installer, AND you > use PV domU, which results in the disk (along with the kernel and > initrd) not accesible during domU boot. >No it is fully virtualized and see above. So I dunno what to think at this point. I''m ready to just give up and go back to VirtualBox to be honest. Especially because since I started this project I only found out afterwards that Red Hat dumped Xen for 6.0 anyway.> If you don''t understand what > I''m saying on this paragraph, just forget it, and ONLY read the > previous paragraph :) >No I understood. Ubuntu installer did not even have an option for importanting the iSCSI disk, but the CentOS installer did when I tried it. BUt that''s not what I used - as mentioned it just showed up like a regular disk since I''d imported it in dom0 So how do I go about debugging this? I''d really like to get it going. As much as I"m tempted to just go back to VirtualBox, I like the idea of Xen better. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
Here is a dump of the xend.log entries which get created when I try to
start the domU in question. I see it complains about /dev/hda and /dev/hdc
(CDROM and HD)
[2012-04-18 11:11:54 xend.XendDomainInfo 28917] DEBUG (XendDomainInfo:261)
XendDomainInfo.create([''vm'', [''name'',
''UbuntuServerS1''], [''memory'',
''4096''], [''maxmem'',
''4096''], [''vcpus'', ''2''],
[''uuid'',
''dcc3a34e-b9d2-4b63-b169-cfa9213330e0''],
[''on_poweroff'', ''destroy''],
[''on_reboot'', ''destroy''],
[''on_crash'', ''destroy''],
[''image'', [''hvm'',
[''kernel'', ''/usr/lib/xen/boot/hvmloader''],
[''vcpus'', ''2''], [''boot'',
''cc''],
[''acpi'', ''1''], [''apic'',
''1''], [''pae'', ''1''],
[''usb'', ''1''], [''parallel'',
''none''], [''serial'',
''pty''], [''device_model'',
''/usr/lib64/xen/bin/qemu-dm''],
[''vnc'', ''1''],
[''vncunused'', ''1''],
[''vnclisten'', ''0.0.0.0''],
[''keymap'',
''en-us'']]], [''device'',
[''vbd'', [''dev'',
''hda:disk''], [''uname'',
''phy:/dev/disk/by-path/ip-192.168.160.250:3260-iscsi-iqn.1986-03.com.sun:02:f4f32db3-53b1-422c-c979-c568b1e6227b-lun-1''],
[''mode'', ''w'']]],
[''device'', [''vbd'', [''dev'',
''hdc:cdrom''], [''uname'',
''file:/data/iso/ubuntu-12.04-beta2-desktop-amd64.iso''],
[''mode'', ''r'']]],
[''device'', [''vif'', [''mac'',
''00:16:3e:20:95:39''], [''bridge'',
''xenbr1''],
[''script'', ''vif-bridge'']]],
[''device'', [''vif'', [''mac'',
''00:16:3e:4e:92:c4''], [''bridge'',
''xenbr0''], [''script'',
''vif-bridge'']]]])
[2012-04-18 11:11:54 xend.XendDomainInfo 28917] DEBUG (XendDomainInfo:383)
parseConfig: config is [''vm'', [''name'',
''UbuntuServerS1''], [''memory'',
''4096''], [''maxmem'',
''4096''], [''vcpus'', ''2''],
[''uuid'',
''dcc3a34e-b9d2-4b63-b169-cfa9213330e0''],
[''on_poweroff'', ''destroy''],
[''on_reboot'', ''destroy''],
[''on_crash'', ''destroy''],
[''image'', [''hvm'',
[''kernel'', ''/usr/lib/xen/boot/hvmloader''],
[''vcpus'', ''2''], [''boot'',
''cc''],
[''acpi'', ''1''], [''apic'',
''1''], [''pae'', ''1''],
[''usb'', ''1''], [''parallel'',
''none''], [''serial'',
''pty''], [''device_model'',
''/usr/lib64/xen/bin/qemu-dm''],
[''vnc'', ''1''],
[''vncunused'', ''1''],
[''vnclisten'', ''0.0.0.0''],
[''keymap'',
''en-us'']]], [''device'',
[''vbd'', [''dev'',
''hda:disk''], [''uname'',
''phy:/dev/disk/by-path/ip-192.168.160.250:3260-iscsi-iqn.1986-03.com.sun:02:f4f32db3-53b1-422c-c979-c568b1e6227b-lun-1''],
[''mode'', ''w'']]],
[''device'', [''vbd'', [''dev'',
''hdc:cdrom''], [''uname'',
''file:/data/iso/ubuntu-12.04-beta2-desktop-amd64.iso''],
[''mode'', ''r'']]],
[''device'', [''vif'', [''mac'',
''00:16:3e:20:95:39''], [''bridge'',
''xenbr1''],
[''script'', ''vif-bridge'']]],
[''device'', [''vif'', [''mac'',
''00:16:3e:4e:92:c4''], [''bridge'',
''xenbr0''], [''script'',
''vif-bridge'']]]]
[2012-04-18 11:11:54 xend.XendDomainInfo 28917] DEBUG (XendDomainInfo:507)
parseConfig: result is {''features'': None,
''hpet'': None, ''image'':
[''hvm'',
[''kernel'', ''/usr/lib/xen/boot/hvmloader''],
[''vcpus'', ''2''], [''boot'',
''cc''],
[''acpi'', ''1''], [''apic'',
''1''], [''pae'', ''1''],
[''usb'', ''1''], [''parallel'',
''none''], [''serial'',
''pty''], [''device_model'',
''/usr/lib64/xen/bin/qemu-dm''],
[''vnc'', ''1''],
[''vncunused'', ''1''],
[''vnclisten'', ''0.0.0.0''],
[''keymap'',
''en-us'']], ''cpus'': None,
''vcpu_avail'': None, ''backend'': [],
''uuid'':
''dcc3a34e-b9d2-4b63-b169-cfa9213330e0'',
''on_reboot'': ''destroy'',
''cpu_weight'': None, ''memory'': 4096,
''cpu_cap'': None, ''localtime'': None,
''timer_mode'': None, ''start_time'': None,
''on_poweroff'': ''destroy'',
''on_crash'': ''destroy'',
''device'': [(''vbd'', [''vbd'',
[''dev'', ''hda:disk''],
[''uname'',
''phy:/dev/disk/by-path/ip-192.168.160.250:3260-iscsi-iqn.1986-03.com.sun:02:f4f32db3-53b1-422c-c979-c568b1e6227b-lun-1''],
[''mode'', ''w'']]), (''vbd'',
[''vbd'', [''dev'',
''hdc:cdrom''], [''uname'',
''file:/data/iso/ubuntu-12.04-beta2-desktop-amd64.iso''],
[''mode'', ''r'']]),
(''vif'', [''vif'', [''mac'',
''00:16:3e:20:95:39''], [''bridge'',
''xenbr1''],
[''script'', ''vif-bridge'']]),
(''vif'', [''vif'', [''mac'',
''00:16:3e:4e:92:c4''],
[''bridge'', ''xenbr0''],
[''script'', ''vif-bridge'']])],
''bootloader'': None,
''maxmem'': 4096, ''shadow_memory'': None,
''name'': ''UbuntuServerS1'',
''bootloader_args'': None, ''vcpus'': 2,
''cpu'': None}
[2012-04-18 11:11:54 xend.XendDomainInfo 28917] DEBUG (XendDomainInfo:1975)
XendDomainInfo.construct: None
[2012-04-18 11:11:54 xend 28917] DEBUG (balloon:146) Balloon: 8476076 KiB
free; need 4096; done.
[2012-04-18 11:11:54 xend.XendDomainInfo 28917] DEBUG (XendDomainInfo:2150)
XendDomainInfo.initDomain: 72 256
[2012-04-18 11:11:54 xend 28917] DEBUG (image:347) args: boot, val: cc
[2012-04-18 11:11:54 xend 28917] DEBUG (image:347) args: fda, val: None
[2012-04-18 11:11:54 xend 28917] DEBUG (image:347) args: fdb, val: None
[2012-04-18 11:11:54 xend 28917] DEBUG (image:347) args: soundhw, val: None
[2012-04-18 11:11:54 xend 28917] DEBUG (image:347) args: localtime, val:
None
[2012-04-18 11:11:54 xend 28917] DEBUG (image:347) args: serial, val: pty
[2012-04-18 11:11:54 xend 28917] DEBUG (image:347) args: std-vga, val: None
[2012-04-18 11:11:54 xend 28917] DEBUG (image:347) args: isa, val: None
[2012-04-18 11:11:54 xend 28917] DEBUG (image:347) args: vcpus, val: 2
[2012-04-18 11:11:54 xend 28917] DEBUG (image:347) args: acpi, val: 1
[2012-04-18 11:11:54 xend 28917] DEBUG (image:347) args: usb, val: 1
[2012-04-18 11:11:54 xend 28917] DEBUG (image:347) args: usbdevice, val:
None
[2012-04-18 11:11:54 xend 28917] DEBUG (image:347) args: k, val: en-us
[2012-04-18 11:11:54 xend 28917] DEBUG (image:407) No VNC passwd configured
for vfb access
[2012-04-18 11:11:54 xend.XendDomainInfo 28917] DEBUG (XendDomainInfo:2191)
_initDomain:shadow_memory=0x0, maxmem=0x1000, memory=0x1000.
[2012-04-18 11:11:54 xend 28917] DEBUG (balloon:146) Balloon: 8475036 KiB
free; need 4237312; done.
[2012-04-18 11:11:54 xend 28917] INFO (image:139) buildDomain os=None
dom=72 vcpus=2
[2012-04-18 11:11:54 xend 28917] DEBUG (image:275) domid = 72
[2012-04-18 11:11:54 xend 28917] DEBUG (image:276) image
/usr/lib/xen/boot/hvmloader
[2012-04-18 11:11:54 xend 28917] DEBUG (image:277) store_evtchn = 3
[2012-04-18 11:11:54 xend 28917] DEBUG (image:278) memsize = 4096
[2012-04-18 11:11:54 xend 28917] DEBUG (image:279) vcpus = 2
[2012-04-18 11:11:54 xend 28917] DEBUG (image:280) pae = 1
[2012-04-18 11:11:54 xend 28917] DEBUG (image:281) acpi = 1
[2012-04-18 11:11:54 xend 28917] DEBUG (image:282) apic = 1
[2012-04-18 11:11:55 xend.XendDomainInfo 28917] DEBUG (XendDomainInfo:677)
Checking for duplicate for uname:
f4f32db3-53b1-422c-c979-c568b1e6227b-lun-1
[phy:/dev/disk/by-path/ip-192.168.160.250:3260-iscsi-iqn.1986-03.com.sun:02:f4f32db3-53b1-422c-c979-c568b1e6227b-lun-1],
dev: hda, mode: w
[2012-04-18 11:11:55 xend 28917] DEBUG (blkif:27) exception looking up
device number for hda: [Errno 2] No such file or directory:
''/dev/hda''
[2012-04-18 11:11:55 xend 28917] DEBUG (blkif:27) exception looking up
device number for hdc: [Errno 2] No such file or directory:
''/dev/hdc''
[2012-04-18 11:11:55 xend 28917] DEBUG (blkif:27) exception looking up
device number for hda: [Errno 2] No such file or directory:
''/dev/hda''
[2012-04-18 11:11:55 xend 28917] DEBUG (DevController:133) DevController:
writing {''backend-id'': ''0'',
''virtual-device'': ''768'',
''device-type'': ''disk'',
''state'': ''1'', ''backend'':
''/local/domain/0/backend/vbd/72/768''} to
/local/domain/72/device/vbd/768.
[2012-04-18 11:11:55 xend 28917] DEBUG (DevController:135) DevController:
writing {''domain'': ''UbuntuServerS1'',
''frontend'':
''/local/domain/72/device/vbd/768'', ''format'':
''/dev/disk/by-path/ip-192.168.160.250'',
''dev'': ''hda'', ''state'':
''1'',
''params'':
''/dev/disk/by-path/ip-192.168.160.250:3260-iscsi-iqn.1986-03.com.sun:02:f4f32db3-53b1-422c-c979-c568b1e6227b-lun-1'',
''mode'': ''w'', ''online'':
''1'', ''frontend-id'': ''72'',
''type'': ''phy''} to
/local/domain/0/backend/vbd/72/768.
[2012-04-18 11:11:55 xend.XendDomainInfo 28917] DEBUG (XendDomainInfo:677)
Checking for duplicate for uname:
/data/iso/ubuntu-12.04-beta2-desktop-amd64.iso
[file:/data/iso/ubuntu-12.04-beta2-desktop-amd64.iso], dev: hdc, mode: r
[2012-04-18 11:11:55 xend 28917] DEBUG (blkif:27) exception looking up
device number for hdc: [Errno 2] No such file or directory:
''/dev/hdc''
[2012-04-18 11:11:55 xend 28917] DEBUG (blkif:27) exception looking up
device number for hda: [Errno 2] No such file or directory:
''/dev/hda''
[2012-04-18 11:11:55 xend 28917] DEBUG (blkif:27) exception looking up
device number for hdc: [Errno 2] No such file or directory:
''/dev/hdc''
[2012-04-18 11:11:55 xend 28917] DEBUG (DevController:133) DevController:
writing {''backend-id'': ''0'',
''virtual-device'': ''5632'',
''device-type'':
''cdrom'', ''state'': ''1'',
''backend'':
''/local/domain/0/backend/vbd/72/5632''} to
/local/domain/72/device/vbd/5632.
[2012-04-18 11:11:55 xend 28917] DEBUG (DevController:135) DevController:
writing {''domain'': ''UbuntuServerS1'',
''frontend'':
''/local/domain/72/device/vbd/5632'',
''format'': ''raw'', ''dev'':
''hdc'', ''state'':
''1'', ''params'':
''/data/iso/ubuntu-12.04-beta2-desktop-amd64.iso'',
''mode'':
''r'', ''online'': ''1'',
''frontend-id'': ''72'',
''type'': ''file''} to
/local/domain/0/backend/vbd/72/5632.
[2012-04-18 11:11:55 xend 28917] DEBUG (DevController:133) DevController:
writing {''backend-id'': ''0'',
''mac'': ''00:16:3e:20:95:39'',
''handle'': ''0'',
''state'': ''1'', ''backend'':
''/local/domain/0/backend/vif/72/0''} to
/local/domain/72/device/vif/0.
[2012-04-18 11:11:55 xend 28917] DEBUG (DevController:135) DevController:
writing {''bridge'': ''xenbr1'',
''domain'': ''UbuntuServerS1'',
''handle'': ''0'',
''script'': ''/etc/xen/scripts/vif-bridge'',
''state'': ''1'', ''front
end'': ''/local/domain/72/device/vif/0'',
''mac'': ''00:16:3e:20:95:39'',
''online'': ''1'',
''frontend-id'': ''72''} to
/local/domain/0/backend/vif/72/0.
[2012-04-18 11:11:55 xend 28917] DEBUG (DevController:133) DevController:
writing {''backend-id'': ''0'',
''mac'': ''00:16:3e:4e:92:c4'',
''handle'': ''1'',
''state'': ''1'', ''backend'':
''/local/domain/0/backend/vif/72/1''} to
/local/domain/72/device/vif/1.
[2012-04-18 11:11:55 xend 28917] DEBUG (DevController:135) DevController:
writing {''bridge'': ''xenbr0'',
''domain'': ''UbuntuServerS1'',
''handle'': ''1'',
''script'': ''/etc/xen/scripts/vif-bridge'',
''state'': ''1'', ''frontend'':
''/local/domain/72/device/vif/1'', ''mac'':
''00:16:3e:4e:92:c4'', ''online'':
''1'',
''frontend-id'': ''72''} to
/local/domain/0/backend/vif/72/1.
[2012-04-18 11:11:55 xend 28917] INFO (image:453) spawning device models:
/usr/lib64/xen/bin/qemu-dm [''/usr/lib64/xen/bin/qemu-dm'',
''-d'', ''72'', ''-m'',
''4096'', ''-boot'', ''cc'',
''-serial'', ''pty'',
''-vcpus'', ''2'', ''-acpi'',
''-usb'',
''-k'', ''en-us'',
''-domain-name'', ''UbuntuServerS1'',
''-net'',
''nic,vlan=1,macaddr=00:16:3e:20:95:39,model=rtl8139'',
''-net'',
''tap,vlan=1,bridge=xenbr1'', ''-net'',
''nic,vlan=2,macaddr=00:16:3e:4e:92:c4,model=rtl8139'',
''-net'',
''tap,vlan=2,bridge=xenbr0'', ''-vnc'',
''0.0.0.0:72'', ''-vncunused'']
[2012-04-18 11:11:55 xend 28917] INFO (image:456) device model pid: 5855
[2012-04-18 11:11:55 xend.XendDomainInfo 28917] DEBUG (XendDomainInfo:1072)
Storing VM details: {''shadow_memory'': ''34'',
''uuid'':
''dcc3a34e-b9d2-4b63-b169-cfa9213330e0'',
''on_reboot'': ''destroy'',
''start_time'': ''1334761915.42'',
''on_poweroff'': ''destroy'',
''name'':
''UbuntuServerS1'', ''xend/restart_count'':
''0'', ''vcpus'': ''2'',
''vcpu_avail'':
''3'', ''memory'': ''4096'',
''on_crash'': ''destroy'',
''image'': ''(hvm (kernel
/usr/lib/xen/boot/hvmloader) (vcpus 2) (boot cc) (acpi 1) (apic 1) (pae 1)
(usb 1) (parallel none) (serial pty) (device_model
/usr/lib64/xen/bin/qemu-dm) (vnc 1) (vncunused 1) (vnclisten 0.0.0.0)
(keymap en-us))'', ''maxmem'': ''4096''}
[2012-04-18 11:11:55 xend.XendDomainInfo 28917] DEBUG (XendDomainInfo:1107)
Storing domain details: {''console/port'':
''4'', ''name'':
''UbuntuServerS1'',
''console/limit'': ''1048576'',
''vm'':
''/vm/dcc3a34e-b9d2-4b63-b169-cfa9213330e0'',
''domid'': ''72'',
''cpu/0/availability'': ''online'',
''memory/target'': ''4194304'',
''store/ring-ref'': ''983038'',
''cpu/1/availability'': ''online'',
''store/port'':
''3''}
[2012-04-18 11:11:55 xend.XendDomainInfo 28917] DEBUG (XendDomainInfo:1335)
XendDomainInfo.handleShutdownWatch
[2012-04-18 11:11:55 xend 28917] DEBUG (DevController:179) Waiting for
devices vif.
[2012-04-18 11:11:55 xend 28917] DEBUG (DevController:184) Waiting for 0.
[2012-04-18 11:11:55 xend 28917] DEBUG (DevController:571)
hotplugStatusCallback /local/domain/0/backend/vif/72/0/hotplug-status.
[2012-04-18 11:11:55 xend 28917] DEBUG (DevController:571)
hotplugStatusCallback /local/domain/0/backend/vif/72/0/hotplug-status.
[2012-04-18 11:11:55 xend 28917] DEBUG (DevController:585)
hotplugStatusCallback 1.
[2012-04-18 11:11:55 xend 28917] DEBUG (DevController:94) Lock released
[2012-04-18 11:11:55 xend 28917] DEBUG (DevController:184) Waiting for 1.
[2012-04-18 11:11:55 xend 28917] DEBUG (DevController:571)
hotplugStatusCallback /local/domain/0/backend/vif/72/1/hotplug-status.
[2012-04-18 11:11:55 xend 28917] DEBUG (DevController:585)
hotplugStatusCallback 1.
[2012-04-18 11:11:55 xend 28917] DEBUG (DevController:94) Lock released
[2012-04-18 11:11:55 xend 28917] DEBUG (DevController:179) Waiting for
devices usb.
[2012-04-18 11:11:55 xend 28917] DEBUG (DevController:179) Waiting for
devices vbd.
[2012-04-18 11:11:55 xend 28917] DEBUG (DevController:184) Waiting for 768.
[2012-04-18 11:11:55 xend 28917] DEBUG (DevController:571)
hotplugStatusCallback /local/domain/0/backend/vbd/72/768/hotplug-status.
[2012-04-18 11:11:55 xend 28917] DEBUG (DevController:585)
hotplugStatusCallback 1.
[2012-04-18 11:11:55 xend 28917] DEBUG (DevController:94) Lock released
[2012-04-18 11:11:55 xend 28917] DEBUG (DevController:184) Waiting for 5632.
[2012-04-18 11:11:55 xend 28917] DEBUG (DevController:571)
hotplugStatusCallback /local/domain/0/backend/vbd/72/5632/hotplug-status.
[2012-04-18 11:11:55 xend 28917] DEBUG (DevController:585)
hotplugStatusCallback 1.
[2012-04-18 11:11:55 xend 28917] DEBUG (DevController:94) Lock released
[2012-04-18 11:11:55 xend 28917] DEBUG (DevController:179) Waiting for
devices irq.
[2012-04-18 11:11:55 xend 28917] DEBUG (DevController:179) Waiting for
devices vkbd.
[2012-04-18 11:11:55 xend 28917] DEBUG (DevController:179) Waiting for
devices vfb.
[2012-04-18 11:11:55 xend 28917] DEBUG (DevController:179) Waiting for
devices pci.
[2012-04-18 11:11:55 xend 28917] DEBUG (DevController:179) Waiting for
devices ioports.
[2012-04-18 11:11:55 xend 28917] DEBUG (DevController:179) Waiting for
devices tap.
[2012-04-18 11:11:55 xend 28917] DEBUG (DevController:179) Waiting for
devices vtpm.
[2012-04-18 11:11:55 xend 28917] INFO (XendDomain:388) Domain
UbuntuServerS1 (72) unpaused.
_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
OK, if any of you are in Ottawa I''ll give you my work address so you can line up to boot my in the arse for my stupidity. When I add the disk from virt-manager it has to be type "Virtual Disk" in order to boot from it. You can install to it if it is IDE or SCSI, but cannot boot from it. Sorry folks and thanks for all the help. On the upside I did learn A LOT about Xen and iSCSI in the process _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
On Wed, Apr 18, 2012 at 12:41 PM, Alan McKay <alan.mckay+xen@gmail.com>wrote:> When I add the disk from virt-manager it has to be type "Virtual Disk" in > order to boot from it. You can install to it if it is IDE or SCSI, but > cannot boot from it. >Well, I''m sad to report that was a false alarm - it was booting from the Live CD even though I had "HD" marked in the GUI So back to square one. Though I''m going to redo the install as a virtual disk and see what happens from there - I have a feeling it might do the trick. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
Well I tried all 3 ways - adding a storage device "block device" as type IDE, SCSI and Virtual, and they all add fine via virt-manager and I can do the install into them and the install goes fine, but when I boot from it it does not see the disk _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
On Wed, Apr 18, 2012 at 10:27 PM, Alan McKay <alan.mckay+xen@gmail.com> wrote:> Here is a dump of the xend.log entries which get created when I try to start > the domU in question. I see it complains about /dev/hda and /dev/hdc (CDROM > and HD)> [2012-04-18 11:11:55 xend 28917] DEBUG (blkif:27) exception looking up > device number for hda: [Errno 2] No such file or directory: ''/dev/hda''I''m curious, have you tried creating a domU backed by a disk image or local partition/LVM? That error looks like something stupid that happens when your dom0 does not actualy have "hda", which should not happen. At least not in newer versions of xen. Does your dom0 have a /dev/hda? If not, try "mknod /dev/hda b 3 0", "mknod /dev/hdc b 22 0", and try again. -- Fajar
On Wed, Apr 18, 2012 at 5:52 PM, Fajar A. Nugraha <list@fajar.net> wrote:> I''m curious, have you tried creating a domU backed by a disk image or > local partition/LVM? >Yes, I did one with disk image and it works fine> > That error looks like something stupid that happens when your dom0 > does not actualy have "hda", which should not happen. At least not in > newer versions of xen. >Hmmm> > Does your dom0 have a /dev/hda? If not, try "mknod /dev/hda b 3 0", > "mknod /dev/hdc b 22 0", and try again. >I will try that at work tomorrow - thanks so much for your continued help here! I''m so puzzled by this I can''t even begin to think what is next. thanks, -Alan _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
On Thu, 2012-04-19 at 00:58 +0100, Alan McKay wrote:> I will try that at work tomorrow - thanks so much for your continued > help here! I''m so puzzled by this I can''t even begin to think what is > next.I don''t know much about virt-manager so don''t really have anything helpful to suggest directly but have you tried the virt-manager lists in case this is an issue at that level? Ian.
On Thu, Apr 19, 2012 at 2:37 AM, Ian Campbell <Ian.Campbell@citrix.com>wrote:> I don''t know much about virt-manager so don''t really have anything > helpful to suggest directly but have you tried the virt-manager lists in > case this is an issue at that level? >Yup I have the same thread going on there. thanks, -Alan _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
On Wed, Apr 18, 2012 at 5:52 PM, Fajar A. Nugraha <list@fajar.net> wrote:> That error looks like something stupid that happens when your dom0 > does not actualy have "hda", which should not happen. At least not in > newer versions of xen. > > Does your dom0 have a /dev/hda? >Nope, it does not> If not, try "mknod /dev/hda b 3 0", > "mknod /dev/hdc b 22 0", and try again. >Oh I had really high hopes for this one when I saw it at home last night - but sadly it still does not work :-( Are there updated packages available for RHEL5.8? I just did a "yum update" and got a slightly newer kernel that I will try, but I mean the latest and greatest - is there somewhere I can get that for RHEL5.8? I now have this : [root@solexa1 xen]# rpm -qa | grep -i xen xen-3.0.3-135.el5_8.2 xen-libs-3.0.3-135.el5_8.2 kernel-xen-devel-2.6.18-308.1.1.el5 kernel-xen-devel-2.6.18-308.4.1.el5 xen-libs-3.0.3-135.el5_8.2 kernel-xen-2.6.18-308.4.1.el5 kernel-xen-devel-2.6.18-274.12.1.el5 kernel-xen-2.6.18-274.12.1.el5 kernel-xen-2.6.18-308.1.1.el5 thanks, -Alan _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
On Thu, Apr 19, 2012 at 8:12 PM, Alan McKay <alan.mckay+xen@gmail.com> wrote:> On Wed, Apr 18, 2012 at 5:52 PM, Fajar A. Nugraha <list@fajar.net> wrote: >> >> That error looks like something stupid that happens when your dom0 >> does not actualy have "hda", which should not happen. At least not in >> newer versions of xen. >> >> Does your dom0 have a /dev/hda? > > > Nope, it does not > >> >> If not, try "mknod /dev/hda b 3 0", >> "mknod /dev/hdc b 22 0", and try again. > > > Oh I had really high hopes for this one when I saw it at home last night - > but sadly it still does not work :-( > > Are there updated packages available for RHEL5.8?This is probably a good time to file support ticket in RHN.> I just did a "yum update" and got a slightly newer kernel that I will try, > but I mean the latest and greatest - is there somewhere I can get that for > RHEL5.8?gitco should have newer xen packages which should work with RHEL''s kernel-xen, but they''re unofficial and will void your RHEL support: http://www.gitco.de/repo/ You could also probably mix them with latest vanilla kernel (again, unofficial, unsupported), which can also function as dom0: http://elrepo.org/tiki/kernel-ml , https://blogs.oracle.com/linux/entry/oracle_unbreakable_enterprise_kernel_release -- Fajar
On Thu, Apr 19, 2012 at 9:20 AM, Fajar A. Nugraha <list@fajar.net> wrote:> > Are there updated packages available for RHEL5.8? > > This is probably a good time to file support ticket in RHN.Yeah I was thinking that - one of the good points of going with RHEL versus one of the re-spun ones. I''ll figure out how to do that. Does this list get logged to a URL somewhere that I could post a link to this thread in my report? Thanks again for everyone''s help on this. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
One final FYI ... I rebooted with the new kernel I just updated to, and still have the problem :-( _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users