headers
Artur Linhart - Linux communication | 1 Mar 01:41

RE: How can be defined the order of the starting of DomUs linked into /etc/xen/auto?

Yes, I would guess too.... but it is not in the alpha order - at least in my
case... Yes, You ar right, I can look into the script and try to understand
it :-) It seems I will have no other chance :-))

	Thanx for pointer. I'll try.

		Archie

-----Original Message-----
From: Todd Deshane [mailto:deshantm <at> gmail.com] 
Sent: Friday, February 29, 2008 11:09 PM
To: Artur Linhart - Linux communication
Cc: Xen-Users
Subject: Re: [Xen-users] How can be defined the order of the starting of
DomUs linked into /etc/xen/auto?

Hi Archie,

On Fri, Feb 29, 2008 at 2:20 PM, Artur Linhart - Linux communication
<AL.LINUX <at> bcpraha.com> wrote:
>
>
>
>
> Hello,
>
>
>
>             I  use Xen 3.1.0 for longer time, but I still have one problem
-
(Continue reading)

Permalink | Reply | 0 comments |
headers
Akio Takebe | 1 Mar 06:14
Favicon

Re: xm dump-core and an XP HVM

Hi, Ryan

>That worked.  What causes the discrepancy between the value for nr_pages and
>max_memkb/4?  Also, if I wanted to add the code as a function named
HVM domain would have sparce memory, so you will need max pfn.
max_memkb/4 means (max_memkb*1024)/(PAGE_SIZE).
It is max pfn.
nr_pages means the number of pages passed from hypervisor.
max_memkb*1024 will be more than nrpages*PAGE_SIZE.

>xc_dump_physical() in xc_core.c and be able to call it from main.py, what
>intermediate files are involved?  I've tried to trace a call to dump-core to
>figure out the files that are involved, but I can only trace it to the call
>to server.xend.dump.core in main.py (I assume at this point it becomes an
>xml-rpc call?).  Basically, I need the chain of files from main.py to
>xc_core.c involved in an invocation of dump-core.
server.xend.dump.core is server.xend.domain.dump?
After server.xend.domain.dump, the request posts to xend.
xend get the request in xml-rpc, then
 domain_dump in tools/python/xen/xend/XendDomain.py
   --->  dumpCore() in tools/python/xen/xend/XendDomainInfo.py
      ---> xc_domain_dumpcore in libxc

You can add a entance for xc_dump_physical() in dumpCore.

Best Regards,

Akio Takebe
Permalink | Reply | 0 comments |
headers
SLB Xen Dev | 1 Mar 10:01

Re: Fw: Jailtime image problem - debian 4.0

It sounds like the Jailtime image is assuming that you have the xenblk driver built into the kernel instead of as a module.  On CentOS and Fedora that probably isn't the case, so you need to add the initrd, and it needs to point to an initrd that was loaded with the xenblk driver.  You can only use the dom0 initrd for domU if you have it load the pv modules as well as your normal ones (it shouldn't by default because your dom0 won't need them).  If you don't have one, you should be able to do ok by running something like:
mkinitrd -v -f --with=ext3 --with=xenblk /boot/2.6.whatever-xenU.img 2.6.whatever

On Sat, Mar 1, 2008 at 3:59 AM, Puer Triste <pmtriste <at> sadlittleboy.com> wrote:
It sounds like the Jailtime image is assuming that you have the xenblk driver built into the kernel instead of as a module.  On CentOS and Fedora that probably isn't the case, so you need to add the initrd, and it needs to point to an initrd that was loaded with the xenblk driver.  You can only use the dom0 initrd for domU if you have it load the pv modules as well as your normal ones (it shouldn't by default because your dom0 won't need them).  If you don't have one, you should be able to do ok by running something like:
mkinitrd -v -f --with=ext3 --with=xenblk /boot/2.6.whatever-xenU.img 2.6.whatever


On Fri, Feb 29, 2008 at 5:30 PM, Evan Lavelle <sa212+xen <at> cyconix.com> wrote:
The Centos 5.1 image from jailtime is identical - nothing in /boot,
'vmlinuz-2.6-xen' required on the Dom0. So, clearly jailtime thinks
there's something special about 'vmlinuz-2.6-xen', but the website says
nothing about it.

After some Googling, it looks like this kernel may be installed in the
dom0 /boot by one of the Xen RPMs, or by a download from XenSource. I'll
try to give this a go over the w/end.

Evan

_______________________________________________
Xen-users mailing list
Xen-users <at> lists.xensource.com
http://lists.xensource.com/xen-users



--
Puer Misellus Triste



--
Puer Misellus Triste 
_______________________________________________
Xen-users mailing list
Xen-users <at> lists.xensource.com
http://lists.xensource.com/xen-users
Permalink | Reply | 0 comments |
headers
--[ UxBoD ]-- | 1 Mar 10:57

sched-credit & reboots

Hi,

I wish to set the value higher for one of my VMs so that it gets a large slice of CPU processing, but what is the
correct way to do it so that it is persistent across reboots ?

Regards,

-- 
--[ UxBoD ]--
// PGP Key: "curl -s http://www.splatnix.net/uxbod.asc | gpg --import"
// Fingerprint: F57A 0CBD DD19 79E9 1FCC A612 CB36 D89D 2C5A 3A84
// Keyserver: www.keyserver.net Key-ID: 0x2C5A3A84
// Phone: +44 845 869 2749 SIP Phone: uxbod <at> sip.splatnix.net

--

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Permalink | Reply | 0 comments |
headers
Tim Harig | 1 Mar 11:00

ahci sata detection disparity between standalone and Dom0 kernels

What would cause a difference in drive detection between a similarly
configured standalone kernel and a Dom0 kernel?

The system in question is an ASUS M2N-SLI motherboad with an AMD AthlonX2
3600 micropcoprocessor and 4GB RAM.  Xen and the kernel are both compiled
to use PAE.  The chipset works fine under the AHCI kernel driver while
running standalone.  SCSI support and the AHCI drivers are built directly
into the kernel.

The drives are enumerated as follows:

> $ cat /proc/scsi/scsi 
> Attached devices:
> Host: scsi2 Channel: 00 Id: 00 Lun: 00
>   Vendor: PHILIPS  Model: SPD6104P         Rev: NP02
>   Type:   CD-ROM                           ANSI SCSI revision: 05
> Host: scsi3 Channel: 00 Id: 00 Lun: 00
>   Vendor: ATA      Model: ST3250410AS      Rev: 3.AA
>   Type:   Direct-Access                    ANSI SCSI revision: 05
> Host: scsi4 Channel: 00 Id: 00 Lun: 00
>   Vendor: ATA      Model: ST3250410AS      Rev: 3.AA
>   Type:   Direct-Access                    ANSI SCSI revision: 05
> Host: scsi5 Channel: 00 Id: 00 Lun: 00
>   Vendor: ATA      Model: ST3250410AS      Rev: 3.AA
>   Type:   Direct-Access                    ANSI SCSI revision: 05

Driver detection under the normal boot sequence looks like:

> ahci 0000:02:00.0: AHCI 0001.0000 32 slots 2 ports 3 Gbps 0x3 impl SATA
> mode
> ahci 0000:02:00.0: flags: 64bit ncq pm led clo pmp pio slum part 
> ata1: SATA max UDMA/133 cmd 0xF8820100 ctl 0x0 bmdma 0x0 irq 18
> ata2: SATA max UDMA/133 cmd 0xF8820180 ctl 0x0 bmdma 0x0 irq 18
> scsi0 : ahci
> ata1: SATA link down (SStatus 0 SControl 300)
> scsi1 : ahci
> ata2: SATA link down (SStatus 0 SControl 300)
> ACPI: PCI Interrupt Link [APSI] enabled at IRQ 21
> ACPI: PCI Interrupt 0000:00:05.0[A] -> Link [APSI] -> GSI 21 (level, low)
> -> IRQ 19
> ata3: SATA max UDMA/133 cmd 0x9F0 ctl 0xBF2 bmdma 0xDC00 irq 19
> ata4: SATA max UDMA/133 cmd 0x970 ctl 0xB72 bmdma 0xDC08 irq 19
> scsi2 : sata_nv
> ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata3.00: ATAPI, max UDMA/100
> ata3.00: configured for UDMA/100
> scsi3 : sata_nv
> ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata4.00: ATA-7, max UDMA/133, 488397168 sectors: LBA48 NCQ (depth 0/32)
> ata4.00: ata4: dev 0 multi count 1
> ata4.00: configured for UDMA/133
>   Vendor: PHILIPS   Model: SPD6104P          Rev: NP02
>   Type:   CD-ROM                             ANSI SCSI revision: 05
>   Vendor: ATA       Model: ST3250410AS       Rev: 3.AA
>   Type:   Direct-Access                      ANSI SCSI revision: 05
> ACPI: PCI Interrupt Link [APSJ] enabled at IRQ 20
> ACPI: PCI Interrupt 0000:00:05.1[B] -> Link [APSJ] -> GSI 20 (level, low)
> -> IRQ 20
> ata5: SATA max UDMA/133 cmd 0x9E0 ctl 0xBE2 bmdma 0xC800 irq 20
> ata6: SATA max UDMA/133 cmd 0x960 ctl 0xB62 bmdma 0xC808 irq 20
> scsi4 : sata_nv
> ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata5.00: ATA-7, max UDMA/133, 488397168 sectors: LBA48 NCQ (depth 0/32)
> ata5.00: ata5: dev 0 multi count 1
> ata5.00: configured for UDMA/133
> scsi5 : sata_nv
> ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata6.00: ATA-7, max UDMA/133, 488397168 sectors: LBA48 NCQ (depth 0/32)
> ata6.00: ata6: dev 0 multi count 1
> ata6.00: configured for UDMA/133
>   Vendor: ATA       Model: ST3250410AS       Rev: 3.AA
>   Type:   Direct-Access                      ANSI SCSI revision: 05
>   Vendor: ATA       Model: ST3250410AS       Rev: 3.AA
>   Type:   Direct-Access                      ANSI SCSI revision: 05
> ACPI: PCI Interrupt Link [ASA2] enabled at IRQ 23
> ACPI: PCI Interrupt 0000:00:05.2[C] -> Link [ASA2] -> GSI 23 (level, low)
> -> IRQ 16
> ata7: SATA max UDMA/133 cmd 0xC400 ctl 0xC002 bmdma 0xB400 irq 16
> ata8: SATA max UDMA/133 cmd 0xBC00 ctl 0xB802 bmdma 0xB408 irq 16
> scsi6 : sata_nv
> ata7: SATA link down (SStatus 0 SControl 300)
> ATA: abnormal status 0x7F on port 0xC407
> scsi7 : sata_nv
> ata8: SATA link down (SStatus 0 SControl 300)
> ATA: abnormal status 0x7F on port 0xBC07
> SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
> sda: Write Protect is off
> SCSI device sda: drive cache: write back
> SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
> sda: Write Protect is off
> SCSI device sda: drive cache: write back
>  sda: sda1 sda2
> sd 3:0:0:0: Attached scsi disk sda
> SCSI device sdb: 488397168 512-byte hdwr sectors (250059 MB)
> sdb: Write Protect is off
> SCSI device sdb: drive cache: write back
> SCSI device sdb: 488397168 512-byte hdwr sectors (250059 MB)
> sdb: Write Protect is off
> SCSI device sdb: drive cache: write back
>  sdb: sdb1 sdb2
> sd 4:0:0:0: Attached scsi disk sdb
> SCSI device sdc: 488397168 512-byte hdwr sectors (250059 MB)
> sdc: Write Protect is off
> SCSI device sdc: drive cache: write back
> SCSI device sdc: 488397168 512-byte hdwr sectors (250059 MB)
> sdc: Write Protect is off
> SCSI device sdc: drive cache: write back
>  sdc: sdc1 sdc2
> sd 5:0:0:0: Attached scsi disk sdc
> scsi 2:0:0:0: Attached scsi generic sg0 type 5
> sd 3:0:0:0: Attached scsi generic sg1 type 0
> sd 4:0:0:0: Attached scsi generic sg2 type 0
> sd 5:0:0:0: Attached scsi generic sg3 type 0

however, the boot log for the same configuration on the Dom0 kernel fails
to detect any of the buses containing drives:

> ahci 0000:02:00.0: AHCI 0001.0000 32 slots 2 ports 3 Gbps 0x3 impl SATA
> mode
> ahci 0000:02:00.0: flags: 64bit ncq pm led clo pmp pio slum part 
> ata1: SATA max UDMA/133 cmd 0xE1020100 ctl 0x0 bmdma 0x0 irq 18
> ata2: SATA max UDMA/133 cmd 0xE1020180 ctl 0x0 bmdma 0x0 irq 18
> scsi0 : ahci
> ata1: SATA link down (SStatus 0 SControl 300)
> scsi1 : ahci
> ata2: SATA link down (SStatus 0 SControl 300)

No further output concerning the SATA bus, the AHCI driver, or the SCSI
subsystem is provided.  Later, the Dom0 kernel panics because it is unable
to load the root filesystem which normally resides on /dev/sda1.

The dumps above reflect Xen 3.1.3 and Linux 2.6.18.8 but it doesn't seem to
be limited to that version alone.

I have been banging my head against this for a few weeks without much
gain and I am unsure of how to troubleshoot much further.  I am sure I am
missing something very simple but I have not yet been able to fathom what
it could be.  I am willing to post more information if necessary.  If
anybody could point me in the right direction, I would very much
appreciate it.

Thanks,
Tim Harig
Permalink | Reply | 0 comments |
headers
Tom Brown | 1 Mar 11:33

Re: Fw: Can I install domU without virt-manager?


>
> ----- Original Message ----
> From: Jeroen Torrekens <jeroen.torrekens <at> aserver.com>
> To: 전상일 <sijun <at> markany.com>; xen-users <at> lists.xensource.com
> Sent: Friday, February 29, 2008 3:12:53 AM
> Subject: RE: [Xen-users] Can I install domU without virt-manager?
>
> >I need your help.
>
> >
>
> >Can I install domU without virt-manager?
>
> >I want to install domU(CentOS5.1) without virt-manger.
>
> >If I can, then I want to know the way.
>
> >
>
> >My system:
>
> >OS: CentOS 5.1
>
> >Xen: 3.2.0
>
> >Xen kernel: 2.6.18.8
>
> >
>
> >
>
> >Thank you.
>

i install this but i use a combination of cobbler/koan - define the
machines using cobbler then use koan to create the VM -
I dont use X or anything like that so its very simple.
Permalink | Reply | 0 comments |
headers
Nico Kadel-Garcia | 1 Mar 12:08
Picon

Re: Xen on 32bit machine with 8GB of RAM

gorkhe wrote:
> I wanted to install Xen on 32bit processor with 8GB RAM. I am running 
> Debian on it.
> The general Kernel can only address ~4GB of RAM. So, Is it necessary 
> to install BigMEM kernel so that all the memory get addressed?  And 
> then install xen kernel.
>
> Or ?? Suggestions welcome.
>
> Thanks,
> gorkhe
>
You need PAE kernels: I assume for Debian, these are called bigmem 
kernels. You can install them in any order, you'll just need to do 
setting up of grub and reboots to activate the new kernels.
Permalink | Reply | 0 comments |
headers
Nico Kadel-Garcia | 1 Mar 12:17
Picon

Re: [Xen-devel] Fwd: Missing 3.2 binary install package

jim burns wrote:
> On Thursday 28 February 2008 09:56:41 am Ian Jackson wrote:
>   
>> Failing that, I would
>> suggest building the hypervisor or the kernel (whichever you don't
>> have) from the source tarballs on the xen.org website.  Vendors' dom0
>> kernels intended for 3.1 are generally useable with 3.2.
>>     
>
> What are the limits here? Would the xen.gz 3.0.3 compiled with the dom0 
> kernel, such as found with Centos, work with the xen 3.2 tarball? I would 
> assume the compatibility code would let it work, but what features would 
> be unsupported/not functional? Thanx.
>   
It should, it has for work I've done before. The DomU kernels are much 
more forward compatible with more recent Dom0 kernels than the reverse: 
it's not really suprising.
Permalink | Reply | 0 comments |
headers
Nico Kadel-Garcia | 1 Mar 12:19
Picon

Re: Can I install domU without virt-manager?

전상일 wrote:
>
> I need your help.
>
> Can I install domU without virt-manager?
>
> I want to install domU(CentOS5.1) without virt-manger.
>
> If I can, then I want to know the way.
>
> My system:
>
> OS: CentOS 5.1
>
> Xen: 3.2.0
>
> Xen kernel: 2.6.18.8
>
> Thank you.
>
Yes, you can use virt-install quite easily. It also makes options
available that are not available in virt-manager.
Permalink | Reply | 0 comments |
headers
Nico Kadel-Garcia | 1 Mar 12:21
Picon

Re: intel or amd?

Marco Strullato wrote:
> Hi all,
> I have to choose between intel and amd server to host about 10 guests
> with a mid-high load.
>
> Which one do you suggest? intel or amd? I heard that amd is not
> limited by front side bus as intel cpus.
>
>
> Thanks
>
> Marco
>
> _______________________________________________
> Xen-users mailing list
> Xen-users <at> lists.xensource.com
> http://lists.xensource.com/xen-users
>   
Well, Intel has working quad-core CPU's. AMD tends to be better 
performance at lower CPU speeds, and lower power consumption, and thus 
better cooling. Many big vendors sell either at similar prices, but 
having one CPU core to dedicate to each guest domain can be handy. I 
personally prefer AMD due to better support for their newest features in 
the Linux world, so it's a trade-off.
Permalink | Reply | 3 comments |

Gmane