So what is the proposed fix? Just to find some way to warn when the
user isn't using the correct systemvm template (the new one required
for 4.2 has been based on Wheezy for awhile), other than nothing
working and them having to look in the logs? This is probably a good
idea, we can perhaps have a
Kawai-san,
commit 009da930580fba039b4b8a7532a8a6809d00ed02
+ patches/systemvm/debian/buildsystemvm.sh
The file under there is not used to build systemvm templates as recommended
anymore. The new way to build systemVMs is using veewee-vagrant definitions [1]
and the definition is based on a Debian
No I don't think we need to make such effort (sending emails) for devs,
I think we should fix the code itself (and comments in the codes)
because we're devs.
(2013/06/24 12:20), Marcus Sorensen wrote:
I personally thought it had been publicized pretty well on various threads
that there is a new
I personally thought it had been publicized pretty well on various threads
that there is a new system vm for master/4.2, but if you were unaware of
it, do you think more needs to be done to call it out and make it known to
the devs working on it?
On Jun 23, 2013 8:33 PM, "Hiroaki KAWAI" wrote:
>
Yes, I brought this up previously and was told that we require systemvm
upgrade between many versions and that it is nothing new. There are other
features in 4.2 as well that require the new system vm, so it will be made
known in the release notes and upgrade instructions.
On Jun 23, 2013 8:33 PM,
Current patch/systemvm/debian is based on debian squeeze,
which kernel is 2.6.32-5-686-bigmem. In that system vm,
cloud-early-config silently fails :
/etc/init.d/cloud-early-config: line 109: /dev/vport0p1: No such file or
directory
So I've upgraded to wheezy (which includes virtio-console.ko)
#
