Skip to contentSkip to conversation

stubdom questions

PATCH In review Lu, Guanqun 2 participants 4 messages Sep 9, 2008 – Sep 10, 2008

lore
Share & tools
lore
#0 lore raw

Hi list,

1. There's an inconsistency between the newly modified code (changeset 18226) and the stubdom README file. Lines:
Create /etc/xen/stubdom-hvmconfig (where "hvmconfig" is the name of your HVM guest) with

should be "/etc/xen/hvmconfig-dm", and of course all the occurrences should be substituted.

2. in order to boot hvm in the stubdom way, should i use dom0_mem= option in the grub or should i not?

Thanks.

--
Guanqun

_______________________________________________
Xen-devel mailing list
[email protected]
http://lists.xensource.com/xen-devel

#1 lore raw

PATCH 1/1 stubdom questions

Hello,

Quoted 6 lines · Lu, Guanqun, le Tue 09 Sep 2008 12:43:23 +0800, a écrit :

1. There's an inconsistency between the newly modified code (changeset 18226) and the stubdom README file. Lines:
Create /etc/xen/stubdom-hvmconfig (where "hvmconfig" is the name of your HVM guest) with

should be "/etc/xen/hvmconfig-dm", and of course all the occurrences should be substituted.

Oops, indeed, patch below.

Quoted 1 line

2. in order to boot hvm in the stubdom way, should i use dom0_mem= option in the grub or should i not?

Well, I thought the paragraph I added at the beginning of "General Configuration" would be clear: yes you need it. How could that paragraph be made clearer?

Samuel

stubdom/README +4 -4
diff -r c9db93b0660a stubdom/README
@@ -27,7 +27,7 @@
 - disable anything related to dom0, like pty serial assignments
 
 
-Create /etc/xen/stubdom-hvmconfig (where "hvmconfig" is the name of your HVM
+Create /etc/xen/hvmconfig-dm (where "hvmconfig" is the name of your HVM
 guest) with
 
 kernel = "/usr/lib/xen/boot/ioemu-stubdom.gz"
@@ -52,7 +52,7 @@
 vnc = 0
 sdl = 0
 
-  - In stubdom-hvmconfig, set an sdl vfb:
+  - In hvmconfig-dm, set an sdl vfb:
 
 vfb = [ 'type=sdl' ]
 
@@ -65,7 +65,7 @@
 vnc = 1
 vnclisten = "172.30.206.1"
 
-  - In stubdom-hvmconfig, fill the reserved vif with the same IP, for instance:
+  - In hvmconfig-dm, fill the reserved vif with the same IP, for instance:
 
 vif = [ 'ip=172.30.206.1', 'ip=10.0.1.1,mac=aa:00:00:12:23:34']
 
@@ -76,7 +76,7 @@
 vnc = 0
 sdl = 0
 
-  - In stubdom-hvmconfig, set a vnc vfb:
+  - In hvmconfig-dm, set a vnc vfb:
 
 vfb = [ 'type=vnc' ]
 
#2 lore raw

Bonjour,

Quoted 20 lines

-----Original Message-----
From: Samuel Thibault [mailto:[email protected]]
Sent: Wednesday, September 10, 2008 6:00 AM
To: Lu, Guanqun
Cc: [email protected]
Subject: [PATCH] stubdom questions

Hello,

Quoted 1 line · Lu, Guanqun, le Tue 09 Sep 2008 12:43:23 +0800, a écrit :

1. There's an inconsistency between the newly modified code

(changeset 18226) and the stubdom README file.

Quoted 2 lines

Lines:
Create /etc/xen/stubdom-hvmconfig (where "hvmconfig" is

the name of your HVM

Quoted 3 lines

guest) with

should be "/etc/xen/hvmconfig-dm", and of course all the

occurrences should be substituted.

Quoted 8 lines

Oops, indeed, patch below.

Quoted 1 line

2. in order to boot hvm in the stubdom way, should i use

dom0_mem= option in the grub or should i not?

Well, I thought the paragraph I added at the beginning of "General Configuration" would be clear: yes you need it. How could that paragraph be made clearer?

Yes, it's clear.
I read this paragraph, but I failed several times and don't know the exact reason, thus I have to check whether I'm on the steady ground.

/etc/xen/xmexample.hvm-dm has the line below:
vif = [ '', 'type=ioemu, bridge=xenbr0' ]
And I would like to know whether you booted successfully with such configuration, I've never succeedded until I change the vif configuration to the simple one:
vif = [ '', 'ip=127.0.0.1, mac=aa:00:00:12:23:34' ]
(and the corresponding vif line in hvmconfig is changed as well.)

Do you encounter such a problem?

Merci.

Quoted 46 lines

Samuel

diff -r c9db93b0660a stubdom/README

stubdom/README +0 -2
@@ -27,7 +27,7 @@
- disable anything related to dom0, like pty serial assignments
 
 
-Create /etc/xen/stubdom-hvmconfig (where "hvmconfig" is the 

name of your HVM
+Create /etc/xen/hvmconfig-dm (where "hvmconfig" is the name of your HVM
guest) with

kernel = "/usr/lib/xen/boot/ioemu-stubdom.gz"

stubdom/README +0 -0
@@ -52,7 +52,7 @@

vnc = 0
sdl = 0

stubdom/README +1 -1
-  - In stubdom-hvmconfig, set an sdl vfb:
+  - In hvmconfig-dm, set an sdl vfb:

vfb = [ 'type=sdl' ]

stubdom/README +0 -0
@@ -65,7 +65,7 @@

vnc = 1
vnclisten = "172.30.206.1"

- - In stubdom-hvmconfig, fill the reserved vif with the same IP, for instance:
+ - In hvmconfig-dm, fill the reserved vif with the same IP, for instance:

vif = [ 'ip=172.30.206.1', 'ip=10.0.1.1,mac=aa:00:00:12:23:34']

stubdom/README +0 -0
@@ -76,7 +76,7 @@

vnc = 0
sdl = 0

stubdom/README +1 -1
-  - In stubdom-hvmconfig, set a vnc vfb:
+  - In hvmconfig-dm, set a vnc vfb:
Quoted 3 lines

vfb = [ 'type=vnc' ]

--
Guanqun

#3 lore raw

Hello,

Quoted 5 lines · Lu, Guanqun, le Wed 10 Sep 2008 09:05:54 +0800, a écrit :

/etc/xen/xmexample.hvm-dm has the line below:
vif = [ '', 'type=ioemu, bridge=xenbr0' ]
And I would like to know whether you booted successfully with such configuration, I've never succeedded until I change the vif configuration to the simple one:
vif = [ '', 'ip=127.0.0.1, mac=aa:00:00:12:23:34' ]

Well, it depends on your network configuration, whether you are using a bridge, etc. In that regard, the problem is the same as for xmexample.hvm. In any case, you most probably don't want to give 127.0.0.1 to your domain :)

Quoted 1 line

Do you encounter such a problem?

I'm not using a bridge, so I don't use the configuration above, but it should work when using a bridge.

Samuel