Mailing List Archive

[Bug 1773] new 3.0.0 kernel cannot connect to network, Device 0 (vif)
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1773


johneed@hotmail.com changed:

What |Removed |Added
----------------------------------------------------------------------------
Summary|new 3.0.0 kernel cannot |new 3.0.0 kernel cannot
|connect to network |connect to network, Device 0
| |(vif)




--
Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@lists.xensource.com
http://lists.xensource.com/xen-bugs
[Bug 1773] new 3.0.0 kernel cannot connect to network, Device 0 (vif) [ In reply to ]
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1773


johneed@hotmail.com changed:

What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |major




--
Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@lists.xensource.com
http://lists.xensource.com/xen-bugs
[Bug 1773] new 3.0.0 kernel cannot connect to network, Device 0 (vif) [ In reply to ]
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1773





------- Comment #1 from johneed@hotmail.com 2011-07-28 14:52 -------
Made this major category. vms cannot be run. Similar to
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1335 except he states he
can still run a guest..

On running a guest, the guest begins to run, but when the vif device fails to
appear or connect it times out and kills the vm.

Perhaps I just need the right tip tr adjust a kernel network setting, perhaps
network block devices or something???


--
Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@lists.xensource.com
http://lists.xensource.com/xen-bugs
[Bug 1773] new 3.0.0 kernel cannot connect to network, Device 0 (vif) [ In reply to ]
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1773





------- Comment #2 from johneed@hotmail.com 2011-07-28 14:54 -------
Created an attachment (id=1002)
--> (http://bugzilla.xensource.com/bugzilla/attachment.cgi?id=1002&action=view)
current xend.log state on triggering the flaw


--
Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@lists.xensource.com
http://lists.xensource.com/xen-bugs
[Bug 1773] new 3.0.0 kernel cannot connect to network, Device 0 (vif) [ In reply to ]
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1773





------- Comment #3 from konrad.wilk@oracle.com 2011-07-28 15:05 -------
Does the guest run if you don't have the vif in the config file?
Do you have tap/tun loaded?
What does your .config look like?
What does your guest config look like?


--
Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@lists.xensource.com
http://lists.xensource.com/xen-bugs
[Bug 1773] new 3.0.0 kernel cannot connect to network, Device 0 (vif) [ In reply to ]
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1773





------- Comment #4 from johneed@hotmail.com 2011-07-29 08:28 -------
Konrad. tell me is tun/tap one module or two? I believe it is just tun.

idella@gentoo64 ~/bin $ Error: Device 0 (vif) could not be connected. Hotplug
scripts not working.

idella@gentoo64 ~/bin $ uname -r
3.0.0-gentoo-amd64


idella@gentoo64 ~/bin $ lsmod
Module Size Used by
tun 21662 0
btrfs 847756 3
crc32c 3283 1
libcrc32c 1518 1 btrfs
ext3 199358 3
jbd 86140 1 ext3
reiserfs 346240 2
snd_hda_codec_realtek 334560 1
snd_hda_intel 31730 5
snd_hda_codec 102232 2 snd_hda_codec_realtek,snd_hda_intel
nouveau 916341 2
snd_hwdep 9769 1 snd_hda_codec
snd_pcm 122648 3 snd_hda_intel,snd_hda_codec
snd_timer 33458 2 snd_pcm
snd 99724 14
snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
ath5k 204327 0
ath 23697 1 ath5k
r8169 62385 0
ttm 96345 1 nouveau
drm_kms_helper 41722 1 nouveau
mxm_wmi 2336 1 nouveau
wmi 13045 1 mxm_wmi
sp5100_tco 7741 0
snd_page_alloc 12351 2 snd_hda_intel,snd_pcm
ohci_hcd 50991 0
xen_evtchn 8228 1

I have guests by the dozens. Only try it on a couple of them, try using two -
three methods.
1. import via virtinst in virt-manager some established vms.
Using the gentoo xenkernel, all works well.
Start the vm. The time-out period is a bout a minute or so. That might be set
in /etc/xen/xen-config.sxp; not sure.

2. Conventional idella@gentoo64 ~/bin $ sudo xm create Lenny.com.cfg
It is listed in virt-manager, I unpause it. It gets lost and doesn't find
grub.

3. idella@gentoo64 ~/bin $ sudo xm create -c Lenny.com.cfg
Using config file "/etc/xen/Lenny.com.cfg".
xenconsole: Could not read tty from store: No such file or directory


These last two are consistent. They are missing finding a console

Back to the first. Here is the standard err msg in the little window;

Error starting domain: POST operation failed: xend_post: error from xen daemon:
(xend.err 'Device 0 (vif) could not be connected. Hotplug scripts not
working.')

Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 45, in
cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/engine.py", line 959, in asyncfunc
vm.startup()
File "/usr/share/virt-manager/virtManager/domain.py", line 1118, in startup
self._backend.create()
File "/usr/lib64/python2.7/site-packages/libvirt.py", line 457, in create
if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: POST operation failed: xend_post: error from xen daemon:
(xend.err 'Device 0 (vif) could not be connected. Hotplug scripts not
working.')

Commenting out vif in Leny.com.cfg

idella@gentoo64 ~/Documents $ sudo xm create Lenny.com.cfg
Using config file "/etc/xen/Lenny.com.cfg".
Error: Device 51713 (vbd) could not be connected. Path closed or removed during
hotplug add: backend/vbd/17/51713 state: 1


Let's do a dump via virsh. I shall put it in an attachment.

Also the Lenny.com.cfg.

It appears there are two current deficits;

console and vif device.


Thanks for replying. Please keep it up.


--
Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@lists.xensource.com
http://lists.xensource.com/xen-bugs
[Bug 1773] new 3.0.0 kernel cannot connect to network, Device 0 (vif) [ In reply to ]
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1773





------- Comment #5 from johneed@hotmail.com 2011-07-29 08:34 -------
Created an attachment (id=1004)
--> (http://bugzilla.xensource.com/bugzilla/attachment.cgi?id=1004&action=view)
my emerge --info


--
Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@lists.xensource.com
http://lists.xensource.com/xen-bugs
[Bug 1773] new 3.0.0 kernel cannot connect to network, Device 0 (vif) [ In reply to ]
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1773





------- Comment #6 from johneed@hotmail.com 2011-07-29 08:36 -------
Created an attachment (id=1005)
--> (http://bugzilla.xensource.com/bugzilla/attachment.cgi?id=1005&action=view)
Lenny.com.cfg


--
Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@lists.xensource.com
http://lists.xensource.com/xen-bugs
[Bug 1773] new 3.0.0 kernel cannot connect to network, Device 0 (vif) [ In reply to ]
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1773





------- Comment #7 from johneed@hotmail.com 2011-07-29 08:39 -------
Created an attachment (id=1006)
--> (http://bugzilla.xensource.com/bugzilla/attachment.cgi?id=1006&action=view)
suse-11 dumpxml


--
Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@lists.xensource.com
http://lists.xensource.com/xen-bugs
[Bug 1773] new 3.0.0 kernel cannot connect to network, Device 0 (vif) [ In reply to ]
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1773





------- Comment #8 from johneed@hotmail.com 2011-07-29 08:42 -------
Created an attachment (id=1007)
--> (http://bugzilla.xensource.com/bugzilla/attachment.cgi?id=1007&action=view)
kernel config - 3.0.0


--
Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@lists.xensource.com
http://lists.xensource.com/xen-bugs
[Bug 1773] new 3.0.0 kernel cannot connect to network, Device 0 (vif) [ In reply to ]
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1773





------- Comment #9 from johneed@hotmail.com 2011-07-29 08:47 -------
p.s.
It has no excuse not to attach to a console;

extra = '2 console=hvc0'
unless something has changed


--
Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@lists.xensource.com
http://lists.xensource.com/xen-bugs
[Bug 1773] new 3.0.0 kernel cannot connect to network, Device 0 (vif) [ In reply to ]
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1773





------- Comment #10 from konrad.wilk@oracle.com 2011-07-29 09:02 -------
Pfff...

# CONFIG_XEN_BLKDEV_BACKEND is not set

Does the 'virbr0' interface exist? Do you see vifX.0 interface when you start
the guest?

You can also turn these off:
CONFIG_XEN_DEBUG_FS=y
CONFIG_XEN_DEBUG=y

Looking at your lsmod .. you are missing xen_netbk (or xen_netback - I keep on
forgetting the right name) loaded. You might just want to compile it in the
kernel.


--
Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@lists.xensource.com
http://lists.xensource.com/xen-bugs
[Bug 1773] new 3.0.0 kernel cannot connect to network, Device 0 (vif) [ In reply to ]
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1773





------- Comment #11 from johneed@hotmail.com 2011-07-29 09:46 -------
Konrad;

excellent excellent

there are two stray xen settings I initially missed; one was n network
settings, this is the other.
curiously the setting with xen included in the name was already set [*].
This setting is the one below it, just named a block device or whatever.

Maybe a year ago when I was compiling xen kernels I might have noted them.

The 3.0.0. kernel I kind of expected the xen settings to be neatly grouped.
However if you had not cited it for me like that I likely would just keep on
missing it, until closely gleaning and comparing more settings with the xen
patched kernel.

xen_netback was sitting there all along. well I have just added it to
/etc/conf.d/modules.

This should now fire up; well, work correctly in networking too.

"Do you see vifX.0 interface when you start
the guest?"
where should I see it?, in a console using xm create -c??
Would have to be...
The kernel is ready. Next to re-boot, return and perhaps re-post.


--
Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@lists.xensource.com
http://lists.xensource.com/xen-bugs
[Bug 1773] new 3.0.0 kernel cannot connect to network, Device 0 (vif) [ In reply to ]
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1773





------- Comment #12 from johneed@hotmail.com 2011-07-29 11:02 -------
Konrad;

new flaw.

On adjusting as you suggested, I get a completely different oddity. Never mind
about vif for the moment.
topic is memory management.

gentoo64 bin # /etc/init.d/xencommons start
Starting xenstored...
Setting domain 0 name...
Starting xenconsoled...
gentoo64 bin # /etc/init.d/xend start
gentoo64 bin # xm list
Name ID Mem VCPUs State Time(s)
Domain-0 0 7473 4 r----- 78.9
fed12 612 2 0.0
fedora9 450 2 0.0
squeeze 400 2 157.8

I have removed half of them already. Something in xen is killing the system.

My total ram is 8 gig. xen has allocated 7473 to dom0. However the other
dormant vms overstep that significantly. I mem-set dom0 to a few selected
sensible settings, and xen kills the system; cpu usage goes to 100%, some
runaway processes take over, no control in a console, unusable.
No choice but to hard reset the computer.

Now;

gentoo64 bin # xm create -c Lenny.com.cfg
Using config file "/etc/xen/Lenny.com.cfg".
Started domain lenny.com (id=1)
xenconsole: Could not read tty from store: No such file or directory
gentoo64 bin # xm list
Name ID Mem VCPUs State Time(s)
Domain-0 0 7473 4 r----- 129.7
fed12 612 2 0.0
fedora9 450 2 0.0
lenny.com 1 128 1 r----- 9.0
squeeze 400 2 157.8

Could not read tty from store: No such file or directory is a frustrating error
I encountered back in debian lenny kernel 2.6.26.

Why is the console not working??
idella@gentoo64 ~/bin $ ls /dev/pts/
0 1 2 3
'Please keep it up;


--
Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@lists.xensource.com
http://lists.xensource.com/xen-bugs
[Bug 1773] new 3.0.0 kernel cannot connect to network, Device 0 (vif) [ In reply to ]
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1773





------- Comment #13 from johneed@hotmail.com 2011-07-29 11:06 -------
This is completely new;

if I select a vm in virt-manager, the same list as xm list, to start, the entry
disappears from virt-manager, and yeilds

Error starting domain: 'NoneType' object has no attribute 'info'


--
Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@lists.xensource.com
http://lists.xensource.com/xen-bugs
[Bug 1773] new 3.0.0 kernel cannot connect to network, Device 0 (vif) [ In reply to ]
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1773





------- Comment #14 from konrad.wilk@oracle.com 2011-07-29 11:25 -------
(In reply to comment #12)
> Konrad;
>
> new flaw.
Then open a new bug. Don't pollute this bug.


--
Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@lists.xensource.com
http://lists.xensource.com/xen-bugs
[Bug 1773] new 3.0.0 kernel cannot connect to network, Device 0 (vif) [ In reply to ]
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1773





------- Comment #15 from konrad.wilk@oracle.com 2011-07-29 11:27 -------

> This should now fire up; well, work correctly in networking too.
>
> "Do you see vifX.0 interface when you start
> the guest?"
> where should I see it?, in a console using xm create -c??

ifconfig -a

The vifX.0 should be created then moment you launch the guest. The virtbr
should be there all along.


--
Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@lists.xensource.com
http://lists.xensource.com/xen-bugs
[Bug 1773] new 3.0.0 kernel cannot connect to network, Device 0 (vif) [ In reply to ]
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1773


johneed@hotmail.com changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED




------- Comment #16 from johneed@hotmail.com 2011-07-29 11:38 -------
Looks like it is sorted.

Adding a memory allocation entry kernel arg pulled it into shape


No vif errors, no memory errors, booted up a couple of vs


--
Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@lists.xensource.com
http://lists.xensource.com/xen-bugs
[Bug 1773] new 3.0.0 kernel cannot connect to network, Device 0 (vif) [ In reply to ]
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1773





------- Comment #17 from konrad.wilk@oracle.com 2011-07-29 12:25 -------
(In reply to comment #16)
> Looks like it is sorted.
>
> Adding a memory allocation entry kernel arg pulled it into shape
I am having a hard time parsing that. Can you explain it in a bit more detail
please?


--
Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@lists.xensource.com
http://lists.xensource.com/xen-bugs
[Bug 1773] new 3.0.0 kernel cannot connect to network, Device 0 (vif) [ In reply to ]
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1773





------- Comment #18 from johneed@hotmail.com 2011-07-29 13:02 -------
sure;
simply looked through the xend-config.sxp and found the kernel arg setting that
I hoped for.

Domain-0 0 7473 4 r----- 129.7

This is what I concluded was problematic. I have 8 gig of ram, but dom0 has
claimed 7.473 Gb.

Now booting the other kernel, didn't have this setting.
It seemed any attempt to invoke xm mem-set with this kernel resulted and the
system being overtaken by renegade xen processes, well processes anyway, having
to hard rest.

Having no control in bash or anything, seeking and killing processes was ruled
out.

So I nanoed xend-config.sxp; drew on

"
Additionally you should use dom0_mem = <-Value> as a parameter in
# xen kernel to reserve the memory for 32-bit paravirtual domains, default
# is "0" (0GB).
(total_available_memory 8GB)
"

So actually I changed two things
changed
(total_available_memory 0)
to
(total_available_memory 8GB)

and added

dom0_mem=1.5GB

initially to /boot/xen-version.gz, which was unhelpful, so added it to

module /boot/kernel-3.0.0-gentoo-amd64 root=/dev/sda3 ro console=tty0
which was where it belongs.

Memory settings is not my forte, but have had to adjust them in the past.
I guessed this
(total_available_memory 0)
was unhelpful.

> new flaw.
Then open a new bug. Don't pollute this bug.

I need not have entered that, should have left it out all together. It was
spurious.

Thanks heaps for the prompt assistance.

Is that clear enough?


--
Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@lists.xensource.com
http://lists.xensource.com/xen-bugs
[Bug 1773] new 3.0.0 kernel cannot connect to network, Device 0 (vif) [ In reply to ]
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1773


konrad.wilk@oracle.com changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |CLOSED




------- Comment #19 from konrad.wilk@oracle.com 2011-07-29 13:13 -------
Absolutely. Thanks for providing the resolution writeup.


--
Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@lists.xensource.com
http://lists.xensource.com/xen-bugs
[Bug 1773] new 3.0.0 kernel cannot connect to network, Device 0 (vif) [ In reply to ]
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1773





------- Comment #20 from johneed@hotmail.com 2011-07-29 13:20 -------
excellent; I think be prepared to hear from me again.
thanks again.


--
Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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