WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

RE: [Xen-users] DomU

To: <linux@xxxxxxxxxxx>, <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-users] DomU
From: Achala Aryal <arya2595@xxxxxxxxxxxxxxxxxx>
Date: Sun, 17 Apr 2011 11:12:09 -0700
Cc:
Delivery-date: Sun, 17 Apr 2011 11:13:44 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
Importance: Normal
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx

How can I check libvirtd is running in dom0? my main goal is to try VT-d with xen hypervisor.
Does any of you have any idea or suggestion?
 what I did is I installed xen 4.0 in Ubuntu 10.04 LTS (64bits)  with kernel 2.6.32.15 and now I want to install window as a domU  which I am unable to do.  
To create domU, I used WindowXP cd and used dd command to create image and .iso file. 
Here is my .cfg file for domU: 
import os, re
> > arch = os.uname()[4]
> > if re.search ('64', arch):
> > arch_libdir = 'lib64'
> > else:
> > arch_libdir = 'lib'
> > kernel = "/usr/lib/xen/boot/hvmloader"
> > builder = "hvm"
> > memory = 1024
> > shadow_memory = 8
> > name = "Window2"
> > vif = [ 'type=ioemu, bridge=eth0' ]
> > #vif = [ 'mac=00:16:3e:36:a1:e9' ]
> > acpi = 1
> > apci = 1
> > cdrom =[ 'file:/etc/xen/window.iso']
> > disk = [ 'file:/etc/xen/window.img,sda,w', 'file:/etc/xen/window.iso,hdc:cdrom,r' ]
> > device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm'
> > boot='dc'
> > sdl = 0
> > vnc = 1
> > vncconsole = 1
> > vncpasswd = ''
> > serial = 'pty'
> > usbdevice = 'tablet'

this always return device (0) vif not connected. Holtplug Script not working.
I did brctl show to make sure for my vif and its correct, I have eth0.
Sometimes xm create .cfg returns
domain already exist.
in this case xm list shows that domU in pause state.
Any help will be appreciated.

Thank you





> Date: Sat, 16 Apr 2011 21:13:30 -0400
> From: linux@xxxxxxxxxxx
> To: todd.deshane@xxxxxxx
> Subject: Re: [Xen-users] DomU
> CC: xen-users@xxxxxxxxxxxxxxxxxxx; arya2595@xxxxxxxxxxxxxxxxxx
>
> On 04/16/2011 09:08 PM, Todd Deshane wrote:
> > On Fri, Apr 15, 2011 at 1:51 PM, Achala Aryal
> > <arya2595@xxxxxxxxxxxxxxxxxx> wrote:
> >> Now what I got is:
> >>
> >> xm list
> >> Domain-0 0 3199 8 r-----
> >> 1424.2
> >> Window2 24 1024 1 r-----
> >> 394.5
> >>
> >> Window2 was in p state and I xm unpause 24 it.
> >> but how do I connect with console to install window?
> >> when I do xm console 24 it does not return anything.
> >>
> >
> > Windows doesn't have a text-based console without having a serial
> > console and being invoked like as described in the debugging section
> > of http://wiki.xensource.com/xenwiki/XenWindowsGplPv
> >
> > Instead you should connect to the vnc console of the VM.
> >
> > Hope that helps.
> >
> > Thanks,
> > Todd
>
> To provide a specific option; If you have a relatively modern Linux
> workstation, you can use 'virt-manager' to connect to the domUs. Just
> make sure that the libvirtd daemon in running on the dom0.
>
> --
> Digimer
> E-Mail: digimer@xxxxxxxxxxx
> AN!Whitepapers: http://alteeve.com
> Node Assassin: http://nodeassassin.org
>
> _______________________________________________
> 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
<Prev in Thread] Current Thread [Next in Thread>