I have a xen system running on sles10sp2. xen version is 3.2.0_16718_18-0.3. I have a win2k3 domU that I want to try making an image of using portlock. I don''t know if portlock will work, but I can''t even get it to boot off the cdrom. Using virt-manager I tried adding a cdrom device. It''s listed when I look at the details of the domU, but win2k3 doesn''t see it. Then I tried saving the config, xm list -l > filename.conf. I then modified the conf file, made the cdrom bootable, and the hard drives not bootable. Saved the conf file. I deleted the domU from virt-manager. Lastly, I used xm new command to re-add the domU using the conf. It still did not see the cdrom nor did it boot from it. It still booted from the drives that should be not bootable in the config. Next I shutdown the domU and tried editing the config file found at /etc/xen/vm: I changed these lines(commented lines are originals): #boot="c" #disk=[ ''file:/images/pcalakvre-img/disk0,hda,w'', ''file:/images/test-img/disk1,hdb,w'', ] boot="d" disk=[ ''file:/images/test-img/disk0,hda,w'',''file:/xendata/images/ISOs/portlock336.iso,hdc:cdrom,r'', ''file:/images/test-img/disk1,hdb,w'', ] I restart virt-manager and then tried starting the domU. Same thing, still boots win2k3 and no cdrom on drive d. SO, what is the proper way of adding a cdrom? Once you get it added, how do you make the domU boot from it? Thanks, James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> James, > > I needed to restore a server from a ''dar'' backupset. What I did was to "copy" the server .cfg and make it a HVM setup. > > When started, I connected to the vnc server on port 5900 and did the usual stuff when working from a rescue cdrom. > > The config went like this (Debian Lenny Xen 3.2.1): > > # boot fra CD-ROM > kernel = ''/usr/lib/xen-3.2-1/boot/hvmloader'' > builder = ''hvm'' > boot = "d" > memory = ''512'' > > # > # Disk device(s). > # > root = ''/dev/hda ro'' > disk = [ > ''phy:/dev/vg01/balrog2.net-es.dk-disk,hda,w'', > ''phy:/dev/vg01/balrog2.net-es.dk-swap,hdb,w'', > ''phy:/dev/vg01/balrog-backup,hdc,r'', > ''phy:/usr/local/sysresccd.iso,hdd:cdrom,r'' > ] > > # > # Hostname > # > name = ''balrog2-hvm'' > > # > # Networking > # > vif = [ ''ip=192.168.2.11,mac=00:16:3E:32:38:D9'' ] > > # > # Behaviour > # > on_poweroff = ''destroy'' > on_reboot = ''restart'' > on_crash = ''restart'' > > > keymap="da" > > vnc=1 > vnclisten="0.0.0.0" > vncconsole=1Sorry, forgot to change "To" to the list.... Per, Thanks for the response, but I''m not seeing where this helps me. Thanks, James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
James Pifer skrev:>> James, >> >> I needed to restore a server from a ''dar'' backupset. What I did was to "copy" the server .cfg and make it a HVM setup. >> >> When started, I connected to the vnc server on port 5900 and did the usual stuff when working from a rescue cdrom. >> >> The config went like this (Debian Lenny Xen 3.2.1): >> >> # boot fra CD-ROM >> kernel = ''/usr/lib/xen-3.2-1/boot/hvmloader'' >> builder = ''hvm'' >> boot = "d" >> memory = ''512'' >> >> # >> # Disk device(s). >> # >> root = ''/dev/hda ro'' >> disk = [ >> ''phy:/dev/vg01/balrog2.net-es.dk-disk,hda,w'', >> ''phy:/dev/vg01/balrog2.net-es.dk-swap,hdb,w'', >> ''phy:/dev/vg01/balrog-backup,hdc,r'', >> ''phy:/usr/local/sysresccd.iso,hdd:cdrom,r'' >> ] >> >> # >> # Hostname >> # >> name = ''balrog2-hvm'' >> >> # >> # Networking >> # >> vif = [ ''ip=192.168.2.11,mac=00:16:3E:32:38:D9'' ] >> >> # >> # Behaviour >> # >> on_poweroff = ''destroy'' >> on_reboot = ''restart'' >> on_crash = ''restart'' >> >> >> keymap="da" >> >> vnc=1 >> vnclisten="0.0.0.0" >> vncconsole=1 > > Sorry, forgot to change "To" to the list.... > > Per, > > Thanks for the response, but I''m not seeing where this helps me. > > Thanks, > James > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-usersJames, Perhaps I misunderstood your problem. the problem I had was to boot my PV machine from a rescue cd, which can only be done in a ''hvm'' config (as I understand) The problem for me was to convert the PV config to a ''hvm'' type, particularly the disk layout. I thought my config could help you along. /Per -- ---------------------------------------------------------------------- Per Jensen http://www.net-es.dk/~pj FSF member #1516 ---------------------------------------------------------------------- _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> James, > > Perhaps I misunderstood your problem. the problem I had was to boot my > PV machine from a rescue cd, which can only be done in a ''hvm'' config > (as I understand) > > The problem for me was to convert the PV config to a ''hvm'' type, > particularly the disk layout. I thought my config could help you along. > > /Per >Mine is already a full virt win2k3 machine that I can''t get to recognize a cdrom. What I really want to do is boot off the domU off the CD. Thanks, James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> James Pifer skrev: > >> James, > >> > >> I needed to restore a server from a 'dar' backupset. What I did was > to "copy" the server .cfg and make it a HVM setup. > >> > >> When started, I connected to the vnc server on port 5900 and did the > usual stuff when working from a rescue cdrom. > >> > >> The config went like this (Debian Lenny Xen 3.2.1): > >> > >> # boot fra CD-ROM > >> kernel = '/usr/lib/xen-3.2-1/boot/hvmloader' > >> builder = 'hvm' > >> boot = "d" > >> memory = '512' > >> > >> # > >> # Disk device(s). > >> # > >> root = '/dev/hda ro' > >> disk = [ > >> 'phy:/dev/vg01/balrog2.net-es.dk-disk,hda,w', > >> 'phy:/dev/vg01/balrog2.net-es.dk-swap,hdb,w', > >> 'phy:/dev/vg01/balrog-backup,hdc,r', > >> 'phy:/usr/local/sysresccd.iso,hdd:cdrom,r' > >> ] > >> > >> # > >> # Hostname > >> # > >> name = 'balrog2-hvm' > >> > >> # > >> # Networking > >> # > >> vif = [ 'ip=192.168.2.11,mac=00:16:3E:32:38:D9' ] > >> > >> # > >> # Behaviour > >> # > >> on_poweroff = 'destroy' > >> on_reboot = 'restart' > >> on_crash = 'restart' > >> > >> > >> keymap="da" > >> > >> vnc=1 > >> vnclisten="0.0.0.0" > >> vncconsole=1 > > > > Sorry, forgot to change "To" to the list.... > > > > Per, > > > > Thanks for the response, but I'm not seeing where this helps me. > > > > Thanks, > > James > > > James, > > Perhaps I misunderstood your problem. the problem I had was to boot my > PV machine from a rescue cd, which can only be done in a 'hvm' > config > (as I understand) > > The problem for me was to convert the PV config to a 'hvm' type, > particularly the disk layout. I thought my config could help you along. > > /PerI have managed to boot Fedora11 and OpenSolaris 09.06 as PV domUs since my hardware can't do hvm. It is usually just a case of giving pygrub the correct boot arguments and making sure the .iso is the first line in the disk = [] stanza. e.g. Fedora 11: bootloader = "/usr/bin/pygrub" bootargs = "--kernel=/isolinux/vmlinuz --ramdisk=/isolinux/initrd.img" disk = [ 'file:/misc/iso/fedora/Fedora-11-x86_64-DVD.iso,xvdc:cdrom,r' ] OpenSolaris: bootloader = "/usr/bin/pygrub" bootargs = "--kernel=/platform/i86xpv/kernel/amd64/unix --ramdisk=/boot/amd64/x86.microroot" disk = [ 'file:/misc/iso/solaris/OpenSolaris/osol-0906-x86.iso,xvdc:cdrom,r' ] I haven't managed to get the livecd for FC11 to work as it seems the kernel on the disk doesn't have domU support. OpenSolaris doesn't seem to support the PV virtual fb yet so only command line mode. James This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at http://www.amdocs.com/email_disclaimer.asp _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> I have managed to boot Fedora11 and OpenSolaris 09.06 as PV domUs since my hardware can''t do hvm. It is usually just a case of giving pygrub the correct boot arguments and making sure the .iso is the first line in the disk = [] stanza. > > e.g. > > Fedora 11: > bootloader = "/usr/bin/pygrub" > bootargs = "--kernel=/isolinux/vmlinuz --ramdisk=/isolinux/initrd.img" > disk = [ ''file:/misc/iso/fedora/Fedora-11-x86_64-DVD.iso,xvdc:cdrom,r'' ] > > OpenSolaris: > bootloader = "/usr/bin/pygrub" > bootargs = "--kernel=/platform/i86xpv/kernel/amd64/unix --ramdisk=/boot/amd64/x86.microroot" > disk = [ ''file:/misc/iso/solaris/OpenSolaris/osol-0906-x86.iso,xvdc:cdrom,r'' ] > > I haven''t managed to get the livecd for FC11 to work as it seems the kernel on the disk doesn''t have domU support. OpenSolaris doesn''t seem to support the PV virtual fb yet so only command line mode. > > James > > This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, > you may review at http://www.amdocs.com/email_disclaimer.aspI still have not managed to get this to work. Just as a recap, I have a win2k3 hvm domU. I need to be able to boot this existing domU off an ISO boot cd. Not only can I NOT get it to boot, I can''t even get the domU to see the cdrom device that''s added to it. How can I get this working????? Thanks, James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Fri, 2009-09-04 at 10:26 -0700, Chris Andrews wrote:> Did you look in the donU config and make sure it''s set to boot from > cdrom firstYes, assuming I did it right. Explained in original post. James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users