RE: [Xen-users] How to setup a domain for DOS

["David Morris" <david.morris@xxxxxxxxxx>]

* Boot a domU from a floppy? (Can't tell you how to configure it, but I assume 
it's possible)
* I don't recall seeing a CD based dos/pcdos install .., but that would be an 
obvious choice
* Install DOS on a real machine, boot knoppix or dsl from CD and use 'dd' to 
copy the raw
  hard drive to the file/lvm based xen device.
* Create the appropriate config file ...

> -----Original Message-----
> From: Hu Jia Yi [mailto:jyhu@xxxxxxxxx]
> Sent: Thursday, September 06, 2007 9:20 PM
> To: xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: [Xen-users] How to setup a domain for DOS
> 
> 
> I am using virt-manager to start guest domain. I can install win xp
> using ISO and CD-ROM. 
> 
> Is it possible to install a guest domain for DOS and how?
> 
> Best regards,
> Hu Jia Yi
> Ext: 20430
> Tel: 65-67510430
> 
> -----Original Message-----
> From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
> [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of
> xen-users-request@xxxxxxxxxxxxxxxxxxx
> Sent: Thursday, September 06, 2007 10:54 PM
> To: xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: Xen-users Digest, Vol 31, Issue 19
> 
> Send Xen-users mailing list submissions to
>       xen-users@xxxxxxxxxxxxxxxxxxx
> 
> To subscribe or unsubscribe via the World Wide Web, visit
>       http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users
> or, via email, send a message with subject or body 'help' to
>       xen-users-request@xxxxxxxxxxxxxxxxxxx
> 
> You can reach the person managing the list at
>       xen-users-owner@xxxxxxxxxxxxxxxxxxx
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Xen-users digest..."
> 
> 
> Today's Topics:
> 
>    1. Re: How to change the default kernel of Guest_OS (vipinsagar)
>    2. Re: How to change the default kernel of Guest_OS (vipinsagar)
>    3. Ghost domain ??? (Marco Mililotti)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Thu, 6 Sep 2007 18:20:24 +0530
> From: vipinsagar <freakyzag@xxxxxxxxx>
> Subject: Re: [Xen-users] How to change the default kernel of Guest_OS
> To: "Nico Kadel-Garcia" <nkadel@xxxxxxxxx>
> Cc: Xen Users <xen-users@xxxxxxxxxxxxxxxxxxx>
> Message-ID:
>       <4ca85dfb0709060550r45a537d1p1067ecbe20f4bbf9@xxxxxxxxxxxxxx>
> Content-Type: text/plain; charset="windows-1252"
> 
> Thank you for your information.
> I have done an -ivh to my host machine and test the stability 
> and it was
> fine. Thats why I have gone for -Uvh
> 
> Thank you,
> 
> ~sagar
> 
> On 9/6/07, Nico Kadel-Garcia <nkadel@xxxxxxxxx> wrote:
> >
> > By the way, *DO NOT* use "rpm -U" for kernels, because any error can
> screw
> > up your ability to reboot successfully. Always use "rpm -i" for
> kernels.
> >
> > On 9/6/07, Nico Kadel-Garcia <nkadel@xxxxxxxxx> wrote:
> > >
> > > If you're using pygrub, you need to edit 
> /boot/grub/grub.conf in the
> > > DomU.
> > >
> > >  On 9/6/07, vipinsagar < freakyzag@xxxxxxxxx> wrote:
> > >
> > > >
> > > > Hello Everyone,
> > > >
> > > > Domain-0 OS:Centos5[final]
> > > > Guest OS: Centos5[Centos5[final]
> > > >
> > > > The virtualization [para] set up was working fine until I have
> done a
> > > > kernel upgrade from 2.6.18-8 to 2.6.18-8.1.8 at the guest OS
> level.
> > > >
> > > > My dom-0 is still working fine with the updated kernel. 
> I used the
> > > > same update package and -Uvh at my guest OS level and I changed
> the default
> > > > kernel-2.6.18-8.1.8.el5xen to kernel-2.6.18-8.1.8.el5 in Guest's
> > > > grub.conf [Before the Kernel update, I had only one 
> (xen)Kernel at
> > > > Guest_OS]
> > > >
> > > > then
> > > >
> > > > xm reboot cenos5v [Didn't came up]
> > > >
> > > > then tried
> > > >
> > > > # xm create /etc/xen/cenos5v
> > > >
> > > > Using config file "/etc/xen/cenos5v".
> > > > Going to boot CentOS (2.6.18-8.1.8.el5)
> > > >   kernel: /vmlinuz-2.6.18-8.1.8.el5
> > > >   initrd: /initrd-2.6.18-8.1.8.el5.img
> > > > Error: (22, 'Invalid argument')
> > > >
> > > > Querry:
> > > >
> > > > How do I change my guest's default bootable kernel back to
> xen-kernel.
> > > >
> > > > Please help me out and your suggestion would be appreciated.
> > > >
> > > >
> > > > Thank you All
> > > >
> > > >
> > > > --
> > > > ~O_0~
> > > > ~sagar
> > > > http://vipinsagar.net
> > > > ...i've to look back when I heard a gong! I could only 
> see a huge
> > > > cobweb and its shining, just got wonder, what the time it was...
> > > > _______________________________________________
> > > > Xen-users mailing list
> > > > Xen-users@xxxxxxxxxxxxxxxxxxx
> > > > http://lists.xensource.com/xen-users
> > > >
> > >
> > >
> >
> 
> 
> -- 
> ~O_0~
> ~sagar
> http://vipinsagar.net
> ...i've to look back when I heard a gong! I could only see a 
> huge cobweb
> and
> its shining, just got wonder, what the time it was...
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://lists.xensource.com/archives/html/xen-users/attachments
> /20070906/
> 5ee48b8a/attachment.htm
> 
> ------------------------------
> 
> Message: 2
> Date: Thu, 6 Sep 2007 18:27:46 +0530
> From: vipinsagar <freakyzag@xxxxxxxxx>
> Subject: Re: [Xen-users] How to change the default kernel of Guest_OS
> To: "Xen Users" <xen-users@xxxxxxxxxxxxxxxxxxx>
> Message-ID:
>       <4ca85dfb0709060557i3486cda2m46da05f61295348f@xxxxxxxxxxxxxx>
> Content-Type: text/plain; charset="windows-1252"
> 
> Hello Everyone,
> 
> I have resolved the issue. All I have done
> 
> mount my image
> [foobar@blxvirtual sagar]# lomount -diskimage
> /var/lib/xen/images/cenos5v.img -partition 1 /vipin
> 
> [foobar@blxvirtual sagar]# cd /vipin/grub/grub.conf
> 
> change default 1 to 0  :)
> 
> Happy Xenning around !!!
> 
> ~sagar
> 
> 
> On 9/6/07, vipinsagar <freakyzag@xxxxxxxxx> wrote:
> >
> > Hi Nico,
> >
> > I had tried:
> > /usr/bin/pygrub /var/lib/xen/images/cenos5v.img
> >
> > got the grub window and there I chose the XEN kernel and 
> tried to boot
> >
> > It throws:
> >
> > Going to boot CentOS (2.6.18-8.1.8.el5xen)
> >   kernel: /vmlinuz-2.6.18-8.1.8.el5xen
> >   initrd: /initrd-2.6.18-8.1.8.el5xen.img
> > linux (kernel /var/lib/xen/vmlinuz.nYT_lz)(ramdisk
> > /var/lib/xen/initrd.UYo3oU)(args 'ro root=/dev/VolGroup00/LogVol00
> > console=xvc0 rhgb quiet')
> > [fubar@blxvirtual ~]#
> >
> > Thank You All,
> >
> > ~sagar
> >
> >
> > On 9/6/07, Nico Kadel-Garcia <nkadel@xxxxxxxxx> wrote:
> > >
> > > If you're using pygrub, you need to edit 
> /boot/grub/grub.conf in the
> > > DomU.
> > >
> > > On 9/6/07, vipinsagar < freakyzag@xxxxxxxxx> wrote:
> > >
> > > >
> > > > Hello Everyone,
> > > >
> > > > Domain-0 OS:Centos5[final]
> > > > Guest OS: Centos5[Centos5[final]
> > > >
> > > > The virtualization [para] set up was working fine until I have
> done a
> > > > kernel upgrade from 2.6.18-8 to 2.6.18-8.1.8 at the guest OS
> level.
> > > >
> > > > My dom-0 is still working fine with the updated kernel. 
> I used the
> > > > same update package and -Uvh at my guest OS level and I changed
> the default
> > > > kernel-2.6.18-8.1.8.el5xen to kernel-2.6.18-8.1.8.el5 in Guest's
> > > > grub.conf [Before the Kernel update, I had only one 
> (xen)Kernel at
> > > > Guest_OS]
> > > >
> > > > then
> > > >
> > > > xm reboot cenos5v [Didn't came up]
> > > >
> > > > then tried
> > > >
> > > > # xm create /etc/xen/cenos5v
> > > >
> > > > Using config file "/etc/xen/cenos5v".
> > > > Going to boot CentOS (2.6.18-8.1.8.el5)
> > > >   kernel: /vmlinuz-2.6.18-8.1.8.el5
> > > >   initrd: /initrd-2.6.18-8.1.8.el5.img
> > > > Error: (22, 'Invalid argument')
> > > >
> > > > Querry:
> > > >
> > > > How do I change my guest's default bootable kernel back to
> xen-kernel.
> > > >
> > > > Please help me out and your suggestion would be appreciated.
> > > >
> > > >
> > > > Thank you All
> > > >
> > > >
> > > > --
> > > > ~O_0~
> > > > ~sagar
> > > >  http://vipinsagar.net
> > > > ...i've to look back when I heard a gong! I could only 
> see a huge
> > > > cobweb and its shining, just got wonder, what the time it was...
> > > > _______________________________________________
> > > > Xen-users mailing list
> > > > Xen-users@xxxxxxxxxxxxxxxxxxx
> > > > http://lists.xensource.com/xen-users
> > > >
> > >
> > >
> >
> >
> > --
> > ~O_0~
> > ~sagar
> > http://vipinsagar.net
> > ...i've to look back when I heard a gong! I could only see a huge
> cobweb
> > and its shining, just got wonder, what the time it was...
> >
> 
> 
> 
> -- 
> ~O_0~
> ~sagar
> http://vipinsagar.net
> ...i've to look back when I heard a gong! I could only see a 
> huge cobweb
> and
> its shining, just got wonder, what the time it was...
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://lists.xensource.com/archives/html/xen-users/attachments
> /20070906/
> 9ba4600e/attachment.html
> 
> ------------------------------
> 
> Message: 3
> Date: Thu, 6 Sep 2007 16:53:00 +0200
> From: "Marco Mililotti" <foobar.angus@xxxxxxxxx>
> Subject: [Xen-users] Ghost domain ???
> To: xen-users@xxxxxxxxxxxxxxxxxxx
> Message-ID:
>       <596ca7880709060753r285c40a3of8f198dc149af919@xxxxxxxxxxxxxx>
> Content-Type: text/plain; charset=ISO-8859-1
> 
> Hi,
> 
> I'm running Xen 3.0.4 with suse (kernel 2.6.16.46-0.12-xen). I've a
> problem with a "ghost" (paravirt) domain that appear in the output of
> xm list. As an example:
> # xm list
> Name                                      ID   Mem VCPUs      State
> Time(s)
> Domain-0                                   0  1024     4     r-----
> 29.0
> vm-xyz                                            512     1
> 0.0
> 
> As you can see the domain has no ID and no State. I cannot make any
> reference to it (to destroy it for example). I've a) removed any
> reference to cfg files and disk images for that domain, b) restarted
> the physical host ... but I get always the same output from  xm
> list!!!
> 
> Is there a method to clean up things? Where does xm list get its
> data??? Do I have to remove xen packages from the host and reinstall
> them? What else?
> Any help wellcome.
> 
> Here I append a snapshot from the output of xm list -l :
> 
> (domain
>     (on_crash destroy)
>     (memory 512)
>     (uuid 0c4bb267-9596-32ef-46af-d70f3d509e7b)
>     (bootloader_args 
> '--entry=xvda1:/boot/vmlinuz-xen,/boot/initrd-xen')
>     (name vm-xyz)
>     (maxmem 512)
>     (on_reboot restart)
>     (on_poweroff destroy)
>     (vcpus 1)
>     (bootloader /usr/lib/xen/boot/domUloader.py)
>     (shadow_memory 0)
>     (cpu_weight 256)
>     (cpu_cap 0)
>     (features )
>     (on_xend_start ignore)
>     (on_xend_stop ignore)
>     (start_time 1189070518.22)
>     (online_vcpus 1)
>     (image
>         (linux
>             (kernel /var/lib/xen/tmp/kernel.q0ajL7)
>             (ramdisk /var/lib/xen/tmp/ramdisk.fJgvZ8)
>             (args 'TERM=xterm xencons=tty ')
>         )
>     )
>     (status 0)
>     (memory_dynamic_min 512)
>     (memory_dynamic_max 512)
>     (device
>         (vif
>             (bridge vbr_lo)
>             (mac 00:16:3e:4c:7d:f7)
>             (backend 0)
>             (uuid 12bc4f60-2071-18a3-a09f-44c0cdc8f51a)
>             (script vif-bridge)
>         )
>     )
>     (device
>         (vbd
>             (uuid e600f181-cdb0-1ffa-e8dd-b834f94f56ac)
>             (driver paravirtualised)
>             (dev xvda:disk)
>             (uname file:/xenfs/images/vm-sles10snap/bootdisk)
>             (mode w)
>             (type disk)
>             (backend 0)
>         )
>     )
>     (device
>         (vbd
>             (uuid 95d3a30b-17c4-8ad8-b812-cb298aebb3d1)
>             (driver paravirtualised)
>             (dev xvdb:disk)
>             (uname file:/xenfs/images/vm-sles10snap/rootdisk)
>             (mode w)
>             (type disk)
>             (backend 0)
>         )
>     )
>     (device
>         (vbd
>             (uuid b6a8f396-4738-708f-a309-e288b63303a8)
>             (driver paravirtualised)
>             (dev xvdc:disk)
>             (uname file:/system/SLES10-AMD64-EM64T-DVD1.iso)
>             (mode r)
>             (type disk)
>             (backend 0)
>         )
>     )
> )
> 
> 
> Regards,
> -- Marco
> 
> 
> 
> ------------------------------
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
> 
> 
> End of Xen-users Digest, Vol 31, Issue 19
> *****************************************
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
> 

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