This is a follow-up to my old request "asms" problem when using virt-manager to
install Winxp. Prerequisite: your installation CD/DVD is healthy. I didn't try
ISO image.
Quick steps:
1. create a domain in virt-manager
2. If "asms file is needed" comes out, shut down the domain.
3. run command line "virsh dumpxml domainname > xmlfile.xml"
domainname is the string input in the virt manager installation dialog
xmlfile.xml can be any preferred name
4. edit xmlfile.xml by adding the following section in the disk part; then save
<disk type='block' device='cdrom'>
<driver name='phy' />
<source dev='/dev/cdrom' />
<target dev='hdc' />
<readonly />
</disk>
5. run command line "virsh define xmlfile.xml"
6. re-run the guest domain.
Note: virsh is a script. run "virsh help" for more helps
The detailed solution is in the following link. Other problems such as mouse
point can also be found in the following link or in xen3.0 user manual appendix.
http://skinetwork.org/mediawiki/index.php/Fedora-T61-Xen
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: Sunday, August 26, 2007 6:44 PM
To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Xen-users Digest, Vol 30, Issue 109
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. Linux 2.3.23-rc3 on Xen 3.1 fails in xen_write_cr4 (Bastian Blank)
2. Re: Linux 2.3.23-rc3 on Xen 3.1 fails in xen_write_cr4
(Bastian Blank)
3. vifX.X and vethX not showing (Bart Verwilst)
4. Re: One dedicated NIC per domU (Jordi Espasa Clofent)
5. Re: One dedicated NIC per domU (Emre Erenoglu)
6. Xen under vmware (snacktime)
7. Re: Live Demo CD (Christian Horn)
8. Re: Xen and serial port (Christian Horn)
9. Re: Debian Etch: Error: Device 0 (vif) could not be
connected. Hotplug scripts not working. (Dan Goscomb)
----------------------------------------------------------------------
Message: 1
Date: Sat, 25 Aug 2007 17:46:18 +0200
From: Bastian Blank <bastian@xxxxxxxxxxxx>
Subject: [Xen-users] Linux 2.3.23-rc3 on Xen 3.1 fails in
xen_write_cr4
To: xen-users@xxxxxxxxxxxxxxxxxxx
Message-ID: <20070825154617.GA27424@xxxxxxxxxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset="utf-8"
Hi folks
Linux 2.6.23-rc3 with xen enabled fails on Xen 3.1:
| (XEN) traps.c:1642:d4 Attempt to change CR4 flags.
| general protection fault: 0000 [#1]
[...]
| EIP is at xen_write_cr4+0x3/0x7
[...]
| Call Trace:
| [<c0318f2c>] stop_mce+0x21/0x22
Any suggestions? It seems that some parts of the kernel wants to mess
with CR4. Is it the MCE support?
The complete gpf:
| general protection fault: 0000 [#1]
| SMP
| Modules linked in:
| CPU: 0
| EIP: e019:[<c010191f>] Not tainted VLI
| EFLAGS: 00010202 (2.6.23-rc3-xen-686 #1)
| EIP is at xen_write_cr4+0x3/0x7
| eax: 00000620 ebx: c110a000 ecx: 078bc136 edx: 078bc136
| esi: c033ee2c edi: c1107e2c ebp: 00000020 esp: c030df9c
| ds: e021 es: e021 fs: 00d8 gs: 0000 ss: e021
| Process swapper (pid: 0, ti=c030c000 task=c02e4260 task.ti=c030c000)
| Stack: c0318f2c c0318846 c0318e03 0000e019 00010202 c110a000 c0311905
0000002c
| c03110e9 c030dff0 00009000 c0329ba0 c030dff0 00388000 c030dfe4
00000000
| c0316c27 00000000 078bc1f1 00000001 00000800 00000623 00000000
c0a24000
| Call Trace:
| [<c0318f2c>] stop_mce+0x21/0x22
| [<c0318846>] alternative_instructions+0xe/0x10c
| [<c0318e03>] check_bugs+0x90/0x130
| [<c0311905>] start_kernel+0x30a/0x317
| [<c03110e9>] unknown_bootoption+0x0/0x195
| [<c0316c27>] xen_start_kernel+0x162/0x169
| =======================
| Code: 5a 89 f0 5b 5e 5f 5d c3 c3 31 c0 c3 64 8b 15 08 80 33 c0 89 42 08 c3 64
a1 08 80 33 c0 8b 40 08 c3 64 a1 28 80 33 c0 c3 83 e0 fb <0f> 22 e0 c3 64 a1 0c
80 33 c0 c3 56 89 c6 53 bb 02 00 00 00 ff
| EIP: [<c010191f>] xen_write_cr4+0x3/0x7 SS:ESP e021:c030df9c
| Kernel panic - not syncing: Attempted to kill the idle task!
BAstian
--
Fascinating, a totally parochial attitude.
-- Spock, "Metamorphosis", stardate 3219.8
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
Url :
http://lists.xensource.com/archives/html/xen-users/attachments/20070825/14b87fea/attachment.pgp
------------------------------
Message: 2
Date: Sat, 25 Aug 2007 18:24:04 +0200
From: Bastian Blank <bastian@xxxxxxxxxxxx>
Subject: Re: [Xen-users] Linux 2.3.23-rc3 on Xen 3.1 fails in
xen_write_cr4
To: xen-users@xxxxxxxxxxxxxxxxxxx
Message-ID: <20070825162404.GA29648@xxxxxxxxxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset=utf-8
On Sat, Aug 25, 2007 at 05:46:18PM +0200, Bastian Blank wrote:
> Any suggestions? It seems that some parts of the kernel wants to mess
> with CR4. Is it the MCE support?
After disabling the MCE support, the kernel crashs:
| (XEN) domain_crash_sync called from entry.S (ff16f829)
| (XEN) Domain 1 (vcpu#0) crashed on cpu#0:
| (XEN) ----[ Xen-3.1.0 x86_32p debug=n Not tainted ]----
| (XEN) CPU: 0
| (XEN) EIP: 0061:[<c0107a20>]
| (XEN) EFLAGS: 00010286 CONTEXT: guest
| (XEN) eax: 00010061 ebx: 00010061 ecx: c027ac8c edx: 0000000d
| (XEN) esi: ffffffff edi: 00000000 ebp: 00000020 esp: c004000c
| (XEN) cr0: 80050033 cr4: 000006f0 cr3: 0bd89000 cr2: 00010061
| (XEN) ds: 007b es: 007b fs: 00d8 gs: 0000 ss: e021 cs: 0061
| (XEN) Guest stack trace from esp=c004000c:
| (XEN) c027abd0 00010061 00010086 00000002 c0107a20 00010061 00010086
c027abd0
| (XEN) 00010061 00010086 00000002 c0107a20 00010061 00010086 c027abd0
00010061
| (XEN) 00010086 00000002 c0107a20 00010061 00010086 c027abd0 00010061
00010086
| (XEN) 00000002 c0107a20 00010061 00010086 c027abd0 00010061 00010086
00000002
| (XEN) c0107a20 00010061 00010086 c027abd0 00010061 00010086 00000002
c0107a20
| (XEN) 00010061 00010086 c027abd0 00010061 00010086 00000002 c0107a20
00010061
| (XEN) 00010086 c027abd0 00010061 00010086 00000002 c0107a20 00010061
00010086
| (XEN) c027abd0 00010061 00010086 00000002 c0107a20 00010061 00010086
c027abd0
| (XEN) 00010061 00010086 00000002 c0107a20 00010061 00010086 c027abd0
00010061
| (XEN) 00010086 00000002 c0107a20 00010061 00010086 c027abd0 00010061
00010086
| (XEN) 00000002 c0107a20 00010061 00010086 c027abd0 00010061 00010086
00000002
| (XEN) c0107a20 00010061 00010086 c027abd0 00010061 00010086 00000002
c0107a20
| (XEN) 00010061 00010086 c027abd0 00010061 00010086 00000002 c0107a20
00010061
| (XEN) 00010086 c027abd0 00010061 00010086 00000002 c0107a20 00010061
00010086
| (XEN) c027abd0 00010061 00010086 00000002 c0107a20 00010061 00010086
c027abd0
| (XEN) 00010061 00010086 00000002 c0107a20 00010061 00010086 c027abd0
00010061
| (XEN) 00010086 00000002 c0107a20 00010061 00010086 c027abd0 00010061
00010086
| (XEN) 00000002 c0107a20 00010061 00010086 c027abd0 00010061 00010086
00000002
| (XEN) c0107a20 00010061 00010086 c027abd0 00010061 00010086 00000002
c0107a20
| (XEN) 00010061 00010086 c027abd0 00010061 00010086 00000002 c0107a20
00010061
There seems to be two code adresses in the trace:
| c027abd0 T page_fault
| c0107a20 T invalid_op
which are called in a loop.
Bastian
--
I'm a soldier, not a diplomat. I can only tell the truth.
-- Kirk, "Errand of Mercy", stardate 3198.9
------------------------------
Message: 3
Date: Sat, 25 Aug 2007 18:50:11 +0200 (CEST)
From: Bart Verwilst <lists@xxxxxxxxxxx>
Subject: [Xen-users] vifX.X and vethX not showing
To: xen-users@xxxxxxxxxxxxxxxxxxx
Cc: Chuck Short <zulcss@xxxxxxxxx>
Message-ID: <15995559.143841188060611359.JavaMail.root@zimbra01>
Content-Type: text/plain; charset=utf-8
Hi!
I have 2 xen enabled kernels. One is the official amd64 2.6.18-xen kernel from
xensource itself. When i boot with this one, i can see xenbr0, several vif's,
and several veth's. ( I already configured xend-config.sxp correctly. )
When i boot with gutsy's experimental amd64 2.6.22-xen kernel, it boots fine,
but i cannot seem to make the system show the vif's and veth's. I _know_ this
is an experimental kernel and OS, but it would be nice to flush out this bug
before it hits the streets :) The only thing "ip a" shows is the normal eth's
and xenbr0. Starting a vm doesn't work because it cannot find vif0.0.
I was just wondering if any of you guys would have an idea what difference in
these 2 kernels would make vif and peth on the ubuntu kernel fail.. A driver
that's not enabled? a bug?
Any of you had the same experience before?
Thanks a lot!
Kind regards,
Bart Verwilst
------------------------------
Message: 4
Date: Sat, 25 Aug 2007 20:03:06 +0200
From: Jordi Espasa Clofent <sistemes.llistes@xxxxxxxxxxxxx>
Subject: Re: [Xen-users] One dedicated NIC per domU
To: xen-users@xxxxxxxxxxxxxxxxxxx
Message-ID: <46D06EDA.6090605@xxxxxxxxxxxxx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Jordi Espasa Clofent escribió:
>> If each nic has its own PCI controller, why don't you just hide those
>> controllers from Dom0 and export them to each DomU accordingly?
>
> Not in this case. I'm talking about a device which has several gigabit
> eth connection in same PCIe. I'm searching the concrete
> manufacturer/model to show you.
http://www.intel.com/network/connectivity/products/pro1000pt_quad_server_adapter.htm
;)
--
Thanks,
Jordi Espasa Clofent
------------------------------
Message: 5
Date: Sun, 26 Aug 2007 03:06:10 +0200
From: "Emre Erenoglu" <erenoglu@xxxxxxxxx>
Subject: Re: [Xen-users] One dedicated NIC per domU
To: "Jordi Espasa Clofent" <sistemes.llistes@xxxxxxxxxxxxx>
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Message-ID:
<fe9771a80708251806q3857133en9783370049e7b161@xxxxxxxxxxxxxx>
Content-Type: text/plain; charset="iso-8859-1"
Well, as far as I know, you will just use bridged mode and have many xenbr
's around. You can then assign each to one DomU. Would this solve your
problem?
Emre
On 8/25/07, Jordi Espasa Clofent <sistemes.llistes@xxxxxxxxxxxxx> wrote:
>
> Jordi Espasa Clofent escribió:
> >> If each nic has its own PCI controller, why don't you just hide those
> >> controllers from Dom0 and export them to each DomU accordingly?
> >
> > Not in this case. I'm talking about a device which has several gigabit
> > eth connection in same PCIe. I'm searching the concrete
> > manufacturer/model to show you.
>
>
> http://www.intel.com/network/connectivity/products/pro1000pt_quad_server_adapter.htm
>
> ;)
>
> --
> Thanks,
> Jordi Espasa Clofent
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
>
--
Emre Erenoglu
erenoglu@xxxxxxxxx
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.xensource.com/archives/html/xen-users/attachments/20070826/dd2705dc/attachment.htm
------------------------------
Message: 6
Date: Sat, 25 Aug 2007 22:23:47 -0700
From: snacktime <snacktime@xxxxxxxxx>
Subject: [Xen-users] Xen under vmware
To: xen-users@xxxxxxxxxxxxxxxxxxx
Message-ID:
<1f060c4c0708252223m17d6d95fw71ace75c9a238e6b@xxxxxxxxxxxxxx>
Content-Type: text/plain; charset=ISO-8859-1
So today I was playing around with xen for the first time. I'm
running ubuntu feisty and the xen packages that come with it under
vmware 5. Everything seems to work great but the single DomU I have
runs extremely slow. Disk IO seems ok but anything that touches the
cpu just drags. Compiling takes 4-5 times as long.
Any idea what the problem might be? Not that I expected it to work
at all, but thought I would post anyways since I got this far.
Chris
------------------------------
Message: 7
Date: Sun, 26 Aug 2007 09:43:49 +0200
From: Christian Horn <chorn@xxxxxxxxxxxx>
Subject: Re: [Xen-users] Live Demo CD
To: Brian Lavender <brian@xxxxxxxx>
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Message-ID: <20070826074349.GA23536@xxxxxxxxxxxx>
Content-Type: text/plain; charset=us-ascii
On Mon, Aug 20, 2007 at 05:07:57PM -0700, Brian Lavender wrote:
>
> xen-3.0-demo-livecd-3.0.iso
xenoppix ( http://unit.aist.go.jp/itri/knoppix/xen/index-en.html ) at
least features xen 3.0.4.
Christian
------------------------------
Message: 8
Date: Sun, 26 Aug 2007 09:55:17 +0200
From: Christian Horn <chorn@xxxxxxxxxxxx>
Subject: Re: [Xen-users] Xen and serial port
To: shacky <shacky83@xxxxxxxxx>
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Message-ID: <20070826075517.GB23536@xxxxxxxxxxxx>
Content-Type: text/plain; charset=us-ascii
On Sat, Aug 25, 2007 at 11:33:44AM +0200, shacky wrote:
> How I can let a domU to use the physical /dev/ttyS0 serial port of the dom0?
> I used the PCI redirection, but I don't understand how to do this with
> the serial port.
Maybe you can set something up with socat, connecting the serial-port
from dom0 and domU via network.
Christian
------------------------------
Message: 9
Date: Sun, 26 Aug 2007 11:42:24 +0100
From: Dan Goscomb <dgoscomb@xxxxxxxxxxxxx>
Subject: Re: [Xen-users] Debian Etch: Error: Device 0 (vif) could not
be connected. Hotplug scripts not working.
To: xen-users@xxxxxxxxxxxxxxxxxxx
Message-ID: <1188124944.5790.25.camel@dang-laptop>
Content-Type: text/plain
does anyone have any more ideas on this? its causing a real headache and
happens on 3 different servers (all AMD64).
Cheers
Dan
On Fri, 2007-08-24 at 19:54 +0530, trilok nuwal wrote:
>
> you shoud put in yr config file then try.
>
> vif = [ 'bridge=xenbr2' ]
>
>
>
> On 8/24/07, Dan Goscomb <dgoscomb@xxxxxxxxxxxxx> wrote:
> Hi
>
> The bridges work for some DomU... as I said... the bridge is
> automatically created:
>
> vps2:~# brctl show
> bridge name bridge id STP enabled
> interfaces
> xenbr2 8000.feffffffffff no vif0.2
> peth2
> vif15.0
> vif2.0
> vif4.0
> vif11.0
> vif6.0
>
> vif13.0
> vif14.0
>
>
> Config file of one of the DomU:
>
> kernel = '/boot/vmlinuz-2.6.18-4-xen-amd64'
> ramdisk = '/boot/initrd.img-2.6.18-4-xen-amd64 '
> memory = '128'
> root = '/dev/sda1 ro'
> disk = [ 'phy:vg0/domu-disk,sda1,w',
> 'phy:vg0/domu-swap,sda2,w' ]
> name = 'domu'
> vif = [ 'ip=<IP_ADDRESS>' ]
> on_poweroff = 'destroy'
> on_reboot = 'restart'
> on_crash = 'restart'
>
>
> Cheers
>
> Dan
>
>
> On Fri, 2007-08-24 at 19:45 +0530, trilok nuwal wrote:
> > better post the config file as well as #ifconfig output in
> dom0.
> >
> > On 8/24/07, trilok nuwal <tc.nuwal@xxxxxxxxx > wrote:
> > Did you created bridges in dom0 whtever u r
> exporting to domU.
> >
> >
> >
> >
> > On 8/24/07, Dan Goscomb <dgoscomb@xxxxxxxxxxxxx>
> wrote:
> > Hi All
> >
> > We have an issue whereby after X number
> (where X can
> > change) DomU are
> > booted, subsequent ones fail with the error
> message in
> > the title.
> >
> > Is this a known issue? I have been unable to
> work out
> > why that error
> > message is appearing...
> >
> > Any hints would be appreciated!
> >
> > Cheers
> >
> > Dan
> >
> >
> >
> _______________________________________________
> > 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
------------------------------
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
End of Xen-users Digest, Vol 30, Issue 109
******************************************
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home